Hi Patrick, I tried linux-2.6.31.4 and tuning still does not work. $ tzap $sender -r status 00 | signal 0000 | snr 0000 | ber 001fffff | unc 0000ffff | status 04 | signal 0000 | snr 0000 | ber 001fffff | unc 0000ffff | status 04 | signal 0000 | snr 0000 | ber 001fffff | unc 0000ffff | status 04 | signal 00b2 | snr 0000 | ber 001fffff | unc 0000ffff | status 04 | signal 0000 | snr 0000 | ber 001fffff | unc 0000ffff | status 04 | signal 0000 | snr 0000 | ber 001fffff | unc 0000ffff | Did you read my other email? The problem must in this file : /usr/src/linux/drivers/media/dvb/dvb-usb/dibusb-common.c line 136 to line 146 i am not familar with the v4l-dvb-hg-repository. I do not know, which patch exactly causes the problem. Greetings Mario Am Mon, 5 Oct 2009 15:50:13 +0200 (CEST) schrieb Patrick Boettcher <pboettcher@xxxxxxxxxxxxxx>: > Hi Mario, > > On Mon, 5 Oct 2009, Mario Bachmann wrote: > > with kernel 2.6.30.8 my "TwinhanDTV USB-Ter USB1.1 / Magic Box I" > > worked. > > > > Now with kernel 2.6.32-rc3 (and 2.6.31.1) the modules seems to be > > loaded fine, but tzap/kaffeine/mplayer can not tune to a channel: > > > > dmesg says: > > dvb-usb: found a 'TwinhanDTV USB-Ter USB1.1 / Magic Box I / HAMA > > USB1.1 DVB-T device' in warm state. dvb-usb: will use the device's > > hardware PID filter (table count: 16). DVB: registering new adapter > > (TwinhanDTV USB-Ter USB1.1 / Magic Box I / HAMA USB1.1 DVB-T > > device) DVB: registering adapter 0 frontend 0 (DiBcom 3000M-B > > DVB-T)... dibusb: This device has the Thomson Cable onboard. Which > > is default. input: IR-receiver inside an USB DVB receiver > > as /devices/pci0000:00/0000:00:04.0/usb4/4-2/input/input5 dvb-usb: > > schedule remote query interval to 150 msecs. dvb-usb: TwinhanDTV > > USB-Ter USB1.1 / Magic Box I / HAMA USB1.1 DVB-T device > > successfully initialized and connected. usbcore: registered new > > interface driver dvb_usb_dibusb_mb > > > > [..] > > and so on. The signal-values are zero or near zero, but when i boot > > the old kernel 2.6.30.8, t can tune without problems. > > In a personal email to me you are saying that the differences between > dibusb-common.c in 2.6.30.8 and 2.6.32-rc3 are the main cause for the > problem. > > Is it possible for you find out which exact change is causing the > trouble? > > With the v4l-dvb-hg-repository it is possible to get each intemediate > version of this file. Afaics, there is only 3 modifications for the > timeframe we are talking about. > > best regards, > > -- > > Patrick Boettcher - Kernel Labs > http://www.kernellabs.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
