My DVB-card is flooding the consol with "recv bulk message failed"
To add another data-point, I am also getting this error with the same board ... as far as I have been able to test, it's something that was OK in 2.6.27, regressed in 2.6.28 and is still a problem in 2.6.30.
Note that this is the rev.1 DViCO
lsb_release -rd
Description: Ubuntu karmic (development branch) Release: 9.10
uname -a
Linux nina 2.6.30-8-generic #9-Ubuntu SMP Wed Jun 3 15:23:55 UTC 2009 i686 GNU/Linux
I get spammed by this console message every 1 second and the board does not operate:
[ 375.385180] dvb-usb: bulk message failed: -110 (4/0)
I see the same problem with mythbuntu-9.04 (2.6.28)
So I put in a new disc and installed Fedora-10 (2.6.27) with the same
firmware: /lib/firmware/xc3028-v27.fw
... and it's working fine now.
Earlier history: It was working fine on Ubuntu Hardy (it was an earlier kernel (2.6.20??) with the v4l-dvb drivers downloaded with hg and compiled locally). Ubuntu Intrepid was also OK.
I also tried powering off, removing the power cable and taking the board out of the machine before re-trying in a different PCI slot - it made no difference.
lsusb gives:
Bus 002 Device 002: ID 0fe9:db78 DVICO FusionHDTV DVB-T Dual Digital 4 (ZL10353+xc2028/xc302 (initialized) Bus 002 Device 003: ID 0fe9:db78 DVICO FusionHDTV DVB-T Dual Digital 4 (ZL10353+xc2028/xc302 (initialized)
Quoted 1 line
From
/var/log/messages, it seems to be loading the firmware but then running into problems with writing to the zl10353:
Jun 13 15:01:45 nina kernel: [ 26.488234] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. Jun 13 15:01:45 nina kernel: [ 26.488611] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Jun 13 15:01:45 nina kernel: [ 26.519611] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual Digital 4) Jun 13 15:01:45 nina kernel: [ 26.937373] cxusb: No IR receiver detected on this device. Jun 13 15:01:45 nina kernel: [ 26.937383] DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)... Jun 13 15:01:45 nina kernel: [ 27.057256] xc2028 2-0061: creating new instance Jun 13 15:01:45 nina kernel: [ 27.057262] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner Jun 13 15:01:45 nina kernel: [ 27.057887] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. Jun 13 15:01:45 nina kernel: [ 27.057913] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. Jun 13 15:01:45 nina kernel: [ 27.058049] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Jun 13 15:01:45 nina kernel: [ 27.089208] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual Digital 4) Jun 13 15:01:45 nina kernel: [ 27.136536] cxusb: No IR receiver detected on this device. Jun 13 15:01:45 nina kernel: [ 27.136545] DVB: registering adapter 1 frontend 0 (Zarlink ZL10353 DVB-T)... Jun 13 15:01:45 nina kernel: [ 27.136737] xc2028 3-0061: creating new instance Jun 13 15:01:45 nina kernel: [ 27.136741] xc2028 3-0061: type set to XCeive xc2028/xc3028 tuner Jun 13 15:01:45 nina kernel: [ 27.137404] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. . . . Jun 13 15:02:25 nina kernel: [ 118.801333] i2c-adapter i2c-2: firmware: requesting xc3028-v27.fw Jun 13 15:02:25 nina kernel: [ 118.922171] xc2028 2-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 Jun 13 15:02:25 nina kernel: [ 118.932344] xc2028 2-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000. Jun 13 15:02:27 nina kernel: [ 120.659451] xc2028 2-0061: Loading firmware for type=D2633 DTV7 (90), id 0000000000000000. Jun 13 15:02:27 nina kernel: [ 120.685823] xc2028 2-0061: Loading SCODE for type=DTV6 QAM DTV7 DTV78 DTV8 ZARLINK456 SCODE HAS_IF_4760 (620003e0), id 0000000000000000. Jun 13 15:02:27 nina kernel: [ 120.989117] i2c-adapter i2c-3: firmware: requesting xc3028-v27.fw Jun 13 15:02:27 nina kernel: [ 120.993890] xc2028 3-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7 Jun 13 15:02:27 nina kernel: [ 121.004235] xc2028 3-0061: Loading firmware for type=BASE F8MHZ (3), id 0000000000000000. Jun 13 15:02:29 nina kernel: [ 122.735596] xc2028 3-0061: Loading firmware for type=D2633 DTV7 (90), id 0000000000000000. Jun 13 15:02:29 nina kernel: [ 122.762090] xc2028 3-0061: Loading SCODE for type=DTV6 QAM DTV7 DTV78 DTV8 ZARLINK456 SCODE HAS_IF_4760 (620003e0), id 0000000000000000. Jun 13 15:02:30 nina kernel: [ 123.853864] usbcore: registered new interface driver hiddev Jun 13 15:02:30 nina kernel: [ 123.853884] usbcore: registered new interface driver usbhid Jun 13 15:02:30 nina kernel: [ 123.853887] usbhid: v2.6:USB HID core driver Jun 13 15:02:30 nina kernel: [ 123.868170] zl10353: write to reg 62 failed (err = -121)! Jun 13 15:02:32 nina kernel: [ 125.868184] zl10353: write to reg 50 failed (err = -121)! Jun 13 15:03:03 nina kernel: [ 157.456355] IRQ 16/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs Jun 13 15:03:03 nina kernel: [ 157.522631] agpgart-nvidia 0000:00:00.0: AGP 2.0 bridge Jun 13 15:03:03 nina kernel: [ 157.522647] agpgart-nvidia 0000:00:00.0: putting AGP V2 device into 4x mode Jun 13 15:03:03 nina kernel: [ 157.522712] nvidia 0000:02:00.0: putting AGP V2 device into 4x mode Jun 13 15:03:20 nina kernel: [ 174.112106] zl10353_read_register: readreg error (reg=80, ret==-121) Jun 13 15:03:22 nina kernel: [ 176.112111] zl10353: write to reg 50 failed (err = -121)! Jun 13 15:03:24 nina kernel: [ 178.116116] zl10353: write to reg 55 failed (err = -121)! Jun 13 15:03:26 nina kernel: [ 180.116129] zl10353: write to reg ea failed (err = -121)!
Signature · 2 lines
Bob Hepple <[email protected]> ph: 07-5584-5908 Fx: 07-5575-9550
Re: DViCO FusionHDTV DVB-T Dual Digital 4 gives "bulk message failed"
Quoted 13 lines · On Mon, 15 Jun 2009 11:33:15 +1000 Bob Hepple <[email protected]> wrote:
To add another data-point, I am also getting this error with the same board ... as far as I have been able to test, it's something that was OK in 2.6.27, regressed in 2.6.28 and is still a problem in 2.6.30.
Note that this is the rev.1 DViCO
lsb_release-rdDescription: Ubuntu karmic (development branch) Release: 9.10uname -a
Linux nina 2.6.30-8-generic #9-Ubuntu SMP Wed Jun 3 15:23:55 UTC 2009 i686 GNU/Linux
Quoted 9 lines
I get spammed by this console message every 1 second and the board does not operate:
[ 375.385180] dvb-usb: bulk message failed: -110 (4/0)I see the same problem with mythbuntu-9.04 (2.6.28)
So I put in a new disc and installed Fedora-10 (2.6.27) with the same
firmware:/lib/firmware/xc3028-v27.fw
... and it's working fine now.
Slight update:
I tried again this past weekend with a fresh hg clone of v4l-dvb on 2.6.27 but had the same "bulk message failed" messages even after a cold start (ie remove power cord).
Has anyone else seen/fixed this? Is it possible that the gold version of these drivers need merging to the head?
I was able to revert to the default 2.6.27 drivers and it works again although there is a remaining problems - mythtv isn't able to tune some channels - particularly channel 7 here in Brisbane.
scandvd and tzap run fine - although the channels.conf file needs a hand-edit as documented in the livetv wiki for missing audio PIDs.
I have been able to import the channels.conf file into mythtv and then all is well there. Hope that helps someone else struggling with this!!
So I'm able to work with 2.6.27 fedora-10 kernel for now but fear for the future of the driver ... and this will hit others trying to use this popular card with more up-to-date kernels.
Thanks
Bob
Signature · 2 lines
Bob Hepple <[email protected]> ph: 07-5584-5908 Fx: 07-5575-9550
Re: DViCO FusionHDTV DVB-T Dual Digital 4 gives "bulk message failed"
Quoted 2 lines · On Mon, 20 Jul 2009 09:49:03 +1000 Bob Hepple <[email protected]> wrote:
I have been able to import the channels.conf file into mythtv and then all is well there. Hope that helps someone else struggling with this!!
Actually, that's not quite accurate - with the 2.6.27 drivers and scandvb's channels.conf file, mythtv still can't tune the second tuner. So as a nasty workaround, on every boot (in /etc/rc.local) I need to use tzap to tune both tuners to _something_ for a few seconds and then exit. Only then is mythtv happy - but it's very happy on both tuners! Weird.
Bob
Signature · 2 lines
Bob Hepple <[email protected]> ph: 07-5584-5908 Fx: 07-5575-9550
Re: My DVB-card is flooding the consol with
In reply to Bob HeppleQuoted 5 lines · Bob Hepple <bhepple <at> promptu.com> writes:
To add another data-point, I am also getting this error with the same board ... as far as I have been able to test, it's something that was OK in 2.6.27, regressed in 2.6.28 and is still a problem in 2.6.30.
Note that this is the rev.1 DViCO
...
Quoted 3 lines
I get spammed by this console message every 1 second and the board does not operate:
[ 375.385180] dvb-usb: bulk message failed: -110 (4/0)
...
Quoted 3 lines
So I put in a new disc and installed Fedora-10 (2.6.27) with the same
firmware:/lib/firmware/xc3028-v27.fw
... and it's working fine now.
Same here. I hadn't touched my kernel for some time for fear of breaking things (getting it working was a trial). Recently tried with a new kernel on a different drive and the card didn't work.
Working on: 2.6.22 (Gentoo) with patches by Michael Krufky and Australian firmware by Chris Pascoe.
Not working on: 2.6.28 (Mythbuntu 9.04) both stock and built from the v4l-dvb repo.
I also tried a 2.6.30 kernel and an earlier 2.6.28 kernel with both the stock driver and built from the v4l-dvb repo - none worked. Also tried going back to older v4l-dvb revisions, but this was hit and miss as they often wouldn't build (the few successful builds didn't work). Unfortunately I can't easily try a 2.6.27 kernel, but if it comes to that I can probably re-install with an older distro.
Bob, I'd agree that it seems the DViCO Dual Digital 4 rev.1 was working in 2.6.27, regressed in 2.6.28, and still not working in 2.6.30.
I'd like to hear from anyone who has a DD4 rev.1 working in 2.6.30 or later. I'm also in Australia, but this time I don't think that is a factor (unlike the firmware shenanigans several years ago). Just a hunch though.
For the record, my dmesg shows:
----
[ 178.599125] xc2028 2-0061: Loading 80 firmware images from xc3028-v27.fw, t ype: xc2028 firmware, ver 2.7 [ 178.609325] xc2028 2-0061: Loading firmware for type=BASE F8MHZ (3), id 000 0000000000000. [ 183.165027] xc2028 2-0061: Loading firmware for type=D2633 DTV7 (90), id 00 00000000000000. [ 183.245019] xc2028 2-0061: Loading SCODE for type=SCODE HAS_IF_5260 (600000 00), id 0000000000000000. [ 185.400150] dvb-usb: recv bulk message failed: -110 [ 185.400162] zl10353: write to reg 62 failed (err = -121)! [ 187.400099] dvb-usb: bulk message failed: -110 (5/0) [ 187.400112] zl10353: write to reg 50 failed (err = -121)! [ 189.411540] dvb-usb: bulk message failed: -110 (2/0) [ 191.408114] dvb-usb: bulk message failed: -110 (4/0) [ 191.408124] cxusb: i2c read failed [ 193.508151] dvb-usb: bulk message failed: -110 (4/0) [ 193.508160] cxusb: i2c read failed
----
(last 2 lines repeating)
- Tom