dib3000mb dvb-t with kernel 2.6.32-rc3 do not work

Hi there,

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

grep DVB .config says (no chaanges between 2.6.30.8 and 2.6.32-rc3):
CONFIG_DVB_CORE=m
CONFIG_DVB_MAX_ADAPTERS=8
CONFIG_DVB_CAPTURE_DRIVERS=y
CONFIG_DVB_USB=m
CONFIG_DVB_USB_DIBUSB_MB=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_PLL=m

lsmod |grep dvb
dvb_usb_dibusb_mb 16715 0
dvb_usb_dibusb_common 3559 1 dvb_usb_dibusb_mb

dvb_pll                 8604  1 dvb_usb_dibusb_mb
dib3000mb              10969  1 dvb_usb_dibusb_mb
dvb_usb                13737  2 dvb_usb_dibusb_mb,dvb_usb_dibusb_common
dvb_core               85727  1 dvb_usb

tzap arte -r
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/grafrotz/.tzap/channels.conf' tuning to 602000000 Hz
video pid 0x00c9, audio pid 0x00ca

status 00 | signal 0000 | snr 0000 | ber 001fffff | unc 0000ffff | 
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 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 | 
status 04 | 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 | 

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.

kaffeine DVB says:
Using DVB device 0:0 "DiBcom 3000M-B DVB-T"
tuning DVB-T to 602000000 Hz
inv:2 bw:0 fecH:2 fecL:9 mod:1 tm:1 gi:3 hier:0
................

Not able to lock to the signal on the given frequency Frontend closed
Tuning delay: 2611 ms

mplayer dvb://arte says:
MPlayer SVN-r29699-4.4.1 (C) 2000-2009 MPlayer Team

Spiele dvb://arte.
dvb_tune Freq: 602000000
Not able to lock to the signal on the given frequency, timeout: 30 dvb_tune, TUNING FAILED
ERROR, COULDN'T SET CHANNEL 13: Konnte 'dvb://arte' nicht öffnen.

Beenden... (Dateiende erreicht)

Greetings
Mario

Hi Mario,

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/

Am Mon, 5 Oct 2009 15:50:13 +0200 (CEST) schrieb Patrick Boettcher <[email protected]>:

i think the cause must be here:
/usr/src/linux-2.6.32-rc3/drivers/media/dvb/dvb-usb/dibusb-common.c line 136 to line 146

i changed this hole section to the version of 2.6.30.8:

		if (i+1 < num && (msg[i+1].flags & I2C_M_RD)) {
			if (dibusb_i2c_msg(d, msg[i].addr,
		msg[i].buf,msg[i].len,
						msg[i+1].buf,msg[i+1].len)
		< 0)
				break;
			i++;
		} else
			if (dibusb_i2c_msg(d, msg[i].addr,
		msg[i].buf,msg[i].len,NULL,0) < 0)
				break;

and it works again. my posted part is inside the
"for (i = 0; i < num; i++) { ... }" -Section !

Mario

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 <[email protected]>: