Nova/dib0700/i2C write failed
Just to provide a bit more info on what seems to be an ongoing issue with these devices, I updated my kernel (2.6.26) dvb drivers with a snapshot from here on 19/11/08 (v4l-dvb-5dc4a6b381f6), it has marginally improved the behaviour but only slightly. Previously, sporadic 'usb 1-4:
USB disconnect, address 2' followed by 'mt2060 I2C write failed' cropping up generally put the khubd into a spin with repeated messages of the form:
Nov 22 20:12:13 fridge kernel: usb 1-4: USB disconnect, address 2 Nov 22 20:12:13 fridge kernel: mt2060 I2C write failed
...
Nov 22 20:14:22 fridge kernel: INFO: task khubd:1823 blocked for more than 120 seconds. Nov 22 20:14:22 fridge kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 22 20:14:22 fridge kernel: khubd D f7f5d000 0 1823 2 Nov 22 20:14:22 fridge kernel: f74c8740 00000046 f7dfe000 f7f5d000 f74a0dc0 f74a0dc0 f7cc0e00 f768f360 Nov 22 20:14:22 fridge kernel: 00000001 f7cc0f8c f7cc0e00 f7f39e58 f7f39e6c 00000001 f896724d 00000000 Nov 22 20:14:22 fridge kernel: f74a0dc0 c0124fde f7f39e64 f7f39e64 f7c0b200 c0186c21 f7f39ea4 00000000 Nov 22 20:14:22 fridge kernel: Call Trace: Nov 22 20:14:22 fridge kernel: [<f896724d>] dvb_unregister_frontend+0xa3/0xda [dvb_core] Nov 22 20:14:22 fridge kernel: [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d Nov 22 20:14:22 fridge kernel: [<c0124fde>] autoremove_wake_function+0x0/0x2d Nov 22 20:14:22 fridge kernel: [sysfs_ilookup_test+0/13]
sysfs_ilookup_test+0x0/0xd
requiring a complete shutdown and reboot to recover even after killing of any dvb applications.
With the latest drivers, this lock of khubd still occurs but only for the lifetime of the active dvb application - it then partially recovers as follows:
Nov 22 21:02:36 fridge kernel: dvb-usb: error while stopping stream. Nov 22 21:02:36 fridge kernel: dvb-usb: Hauppauge Nova-T Stick successfully deinitialized and disconnected. Nov 22 21:02:36 fridge kernel: usb 1-4: new high speed USB device using ehci_hcd and address 3 Nov 22 21:02:36 fridge /USR/SBIN/CRON[8929]: (wwwrun) MAIL (mailed 947 bytes of output but got status 0xffffffff ) Nov 22 21:02:51 fridge kernel: hub 1-0:1.0: unable to enumerate USB device on port 4 Nov 22 21:02:51 fridge kernel: usb 3-2: new full speed USB device using uhci_hcd and address 2 Nov 22 21:02:52 fridge kernel: usb 3-2: not running at top speed; connect to a high speed hub Nov 22 21:02:52 fridge kernel: usb 3-2: configuration #1 chosen from 1 choice Nov 22 21:02:52 fridge kernel: dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. Nov 22 21:02:52 fridge kernel: dvb-usb: This USB2.0 device cannot be run on a USB1.1 port. (it lacks a hardware PID filter) Nov 22 21:02:52 fridge kernel: dvb-usb: Hauppauge Nova-T Stick error while loading driver (-19) Nov 22 21:02:52 fridge kernel: usb 3-2: New USB device found, idVendor=2040, idProduct=7060 Nov 22 21:02:52 fridge kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 22 21:02:52 fridge kernel: usb 3-2: Product: Nova-T Stick Nov 22 21:02:52 fridge kernel: usb 3-2: Manufacturer: Hauppauge Nov 22 21:02:52 fridge kernel: usb 3-2: SerialNumber: 4030521095
Physically disconnecting and reconnecting the device has the same effect. So it looks like the driver is recovering but the USB2 hub has been stuffed in some way.
Signature · 10 lines
== jon bird - software engineer == <reply to address _may_ be invalid, real mail below> == <reduce rsi, stop using the shift key> == posted as: news 'at' onastick 'dot' clara.co.uk _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hi,
Quoted 7 lines · jon bird
Just to provide a bit more info on what seems to be an ongoing issue with these devices, I updated my kernel (2.6.26) dvb drivers with a snapshot from here on 19/11/08 (v4l-dvb-5dc4a6b381f6), it has marginally improved the behaviour but only slightly. Previously, sporadic 'usb 1-4: USB disconnect, address 2' followed by 'mt2060 I2C write failed' cropping up generally put the khubd into a spin with repeated messages of the form:
... are you sure that it is not a problem of the usb ports?
I got an MB with SB700 Chipset and it seems to have the same problems as the SB600 with the USB ports (disconnects here and then).
I use a
http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_DT_USB_XS_Diversity
which is nearly the same as the Nova.
Now my system got a NEC-Chip USB PCIcard and everything works fine with the Cinergy connected there.
Iam using Debian 2.6.26-1 on lenny with v4l out of the hg.
The Board is an Asrock Fulldisplayport.
It didnt work with the onboard USB last time i checked about 4 days ago.
Signature · 6 lines
+ Contact? => http://site.rusch.name/ + _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
In article <[email protected]>, Holger Rusch <[email protected]> writes
Quoted 11 lines
Hi,
Quoted 7 lines · jon bird
Just to provide a bit more info on what seems to be an ongoing issue with these devices, I updated my kernel (2.6.26) dvb drivers with a snapshot from here on 19/11/08 (v4l-dvb-5dc4a6b381f6), it has marginally improved the behaviour but only slightly. Previously, sporadic 'usb 1-4: USB disconnect, address 2' followed by 'mt2060 I2C write failed' cropping up generally put the khubd into a spin with repeated messages of the form:
Quoted 5 lines
... are you sure that it is not a problem of the usb ports?
I got an MB with SB700 Chipset and it seems to have the same problems as the SB600 with the USB ports (disconnects here and then).
[...]
could be although on perusing the mailing list archives this seemed to be a recurring problem of which various attempts have been made to investigate/fix but there didn't seem to be a conclusion to it all. Hence I just thought I'd see what the latest state of play was and report back anything potentially useful.....
Don't know what the USB chipset is, though it's a VIA m/board so could well be one of their own.
j.
Signature · 10 lines
== jon bird - software engineer == <reply to address _may_ be invalid, real mail below> == <reduce rsi, stop using the shift key> == posted as: news 'at' onastick 'dot' clara.co.uk _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 6 lines · jon bird
could be although on perusing the mailing list archives this seemed to
be a recurring problem of which various attempts have been made to investigate/fix but there didn't seem to be a conclusion to it all. Hence I just thought I'd see what the latest state of play was and report back anything potentially useful.....
Well, this has normally been solved. Your report is the first one in a long time.
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hi,
Quoted 10 lines · Nicolas Will
Quoted 6 lines · jon bird
could be although on perusing the mailing list archives this seemed to
be a recurring problem of which various attempts have been made to investigate/fix but there didn't seem to be a conclusion to it all. Hence I just thought I'd see what the latest state of play was and report back anything potentially useful.....Well, this has normally been solved. Your report is the first one in a long time.
I'll second the report. Also with a VIA motherboard, so the USB ports could be the
culprit. Running Mythbuntu with kernel 2.6.24 and using the new firmware still gives
i2c errors.
Richard
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 11 lines · Richard Palmer
Hi,
Quoted 8 lines · Nicolas Will
Quoted 6 lines · jon bird
could be although on perusing the mailing list archives this seemed to
be a recurring problem of which various attempts have been made to investigate/fix but there didn't seem to be a conclusion to it all. Hence I just thought I'd see what the latest state of play was and report back anything potentially useful.....
Quoted 9 lines
Quoted 2 lines
Well, this has normally been solved. Your report is the first one in a long time.
I'll second the report. Also with a VIA motherboard, so the USB ports could be the
culprit. Running Mythbuntu with kernel 2.6.24 and using the new firmware still gives
i2c errors.
I've found Unbuntu 2.6.24-21-386 worked reasonable well with errors requiring a shut down and cold start once or twice a week.
After an upgrade, I found 2.6.27-7-generic fails within seconds of starting to record on two tuners.
dvb-usb: error while enabling fifo.
The current v4l-dvb drivers have the same issue.
I also occasionally get
dib0700: firmware download failed at 17248 with -110
My PC's got ATI's IXP SB400 USB2 Host Controllers.
Rob Watkins
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 29 lines · Robert Watkins
Quoted 11 lines · Richard Palmer
Hi,
Quoted 8 lines · Nicolas Will
Quoted 6 lines · jon bird
could be although on perusing the mailing list archives this seemed to
be a recurring problem of which various attempts have been made to investigate/fix but there didn't seem to be a conclusion to it all. Hence I just thought I'd see what the latest state of play was and report back anything potentially useful.....Quoted 9 lines
Quoted 2 lines
Well, this has normally been solved. Your report is the first one in a long time.
I'll second the report. Also with a VIA motherboard, so the USB ports could be the
culprit. Running Mythbuntu with kernel 2.6.24 and using the new firmware still gives
i2c errors.I've found Unbuntu 2.6.24-21-386 worked reasonable well with errors requiring a shut down and cold start once or twice a week.
After an upgrade, I found 2.6.27-7-generic fails within seconds of starting to record on two tuners.
dvb-usb: error while enabling fifo.
Quoted 8 lines
The current v4l-dvb drivers have the same issue.
I also occasionally get
dib0700: firmware download failed at 17248 with -110My PC's got ATI's IXP SB400 USB2 Host Controllers.
Rob Watkins
Hello Robert,
Are you running dib0700 firmware version 1.10 or 1.20?
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hi,
Quoted 8 lines · Devin Heitmueller
Quoted 4 lines
I also occasionally get
dib0700: firmware download failed at 17248 with -110
My PC's got ATI's IXP SB400 USB2 Host Controllers. Rob WatkinsHello Robert,
Are you running dib0700 firmware version 1.10 or 1.20? Devin
As written before.
I got an MB with SB700 USB Chipset and it seems to have the same problems as the SB600 with the USB ports (disconnects here and then). The SB400 seems to have them also?
I use a
http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_DT_USB_XS_Diversity
which is nearly the same as the Nova.
Now my system got a NEC-Chip USB PCIcard and everything works fine with the Cinergy connected there.
Iam using Debian 2.6.26-1 on lenny with v4l out of the hg.
The Board is an Asrock Fulldisplayport.
Last v4l hg checkout and compile time: 23.11. 18:31
storage:~# cat /etc/debian_version lenny/sid
storage:~# uname -a Linux storage 2.6.26-1-amd64 #1 SMP Sat Nov 8 20:31:23 UTC 2008 x86_64 GNU/Linux
storage:~# lspci -vv | grep -i usb
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0
Controller (prog-if 10 [OHCI])
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
(prog-if 10 [OHCI])
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI
Controller (prog-if 20 [EHCI])
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0
Controller (prog-if 10 [OHCI])
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
(prog-if 10 [OHCI])
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI
Controller (prog-if 20 [EHCI])
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2
Controller (prog-if 10 [OHCI])
05:06.0 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: NEC Corporation Hama USB 2.0 CardBus
05:06.1 USB Controller: NEC Corporation USB (rev 41) (prog-if 10 [OHCI])
Subsystem: NEC Corporation Hama USB 2.0 CardBus
05:06.2 USB Controller: NEC Corporation USB 2.0 (rev 02) (prog-if 20 [EHCI])Signature · 6 lines
+ Contact? => http://site.rusch.name/ + _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 18 lines · Holger Rusch
Hi,
Quoted 8 lines · Devin Heitmueller
Quoted 4 lines
I also occasionally get
dib0700: firmware download failed at 17248 with -110
My PC's got ATI's IXP SB400 USB2 Host Controllers. Rob WatkinsHello Robert,
Are you running dib0700 firmware version 1.10 or 1.20? DevinAs written before.
I got an MB with SB700 USB Chipset and it seems to have the same problems as the SB600 with the USB ports (disconnects here and then). The SB400 seems to have them also?
Quoted 6 lines
I use a
http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_DT_USB_XS_Diversity
which is nearly the same as the Nova.Now my system got a NEC-Chip USB PCIcard and everything works fine with the Cinergy connected there.
My Hauppauge Nova-T 500 Dual DVB-T is a PCI card with built in VIA USB controller.
watkins@watkins-desktop:~$ lspci -vv | grep -i usb 00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI]) 00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI]) 00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80) (prog-if 20 [EHCI]) 02:01.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller 02:01.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller 02:01.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0
The WinTV Nova-DT is connected to the USB 2.0 VIA Hub. The USB 1.1 VIA hubs don't appear to have devices connected to them.
Regards,
Rob
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
In article <1227819747.7014.58.camel@watkins-desktop>, Robert Watkins <[email protected]> writes
Quoted 7 lines · Holger Rusch
As written before.
I got an MB with SB700 USB Chipset and it seems to have the same problems as the SB600 with the USB ports (disconnects here and then).
The SB400 seems to have them also?
[...]
Quoted 20 lines
My Hauppauge Nova-T 500 Dual DVB-T is a PCI card with built in VIA USB controller.
watkins@watkins-desktop:~$ lspci -vv | grep -i usb 00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI]) 00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI]) 00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80) (prog-if 20 [EHCI]) 02:01.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller 02:01.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller 02:01.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0
Here's mine:
/usr/local/sbin/lspci -v | grep -i usb
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
so could be the same chipset as on your PCI card but it's not an SBxxx chipset. If it *is* the controller mind you would expect it to be susceptible to all sorts of USB devices not just this one.
Signature · 10 lines
== jon bird - software engineer == <reply to address _may_ be invalid, real mail below> == <reduce rsi, stop using the shift key> == posted as: news 'at' onastick 'dot' clara.co.uk _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 6 lines · jon bird
Quoted 6 lines · Holger Rusch
As written before.
I got an MB with SB700 USB Chipset and it seems to have the same problems as the SB600 with the USB ports (disconnects here and then).
The SB400 seems to have them also?
....
Quoted 3 lines
so could be the same chipset as on your PCI card but it's not an SBxxx chipset. If it *is* the controller mind you would expect it to be susceptible to all sorts of USB devices not just this one.
There are reviews of my MB (Asrock Displayport) which write about slow speed results for the usb ports. Maybe there are other problems, i didnt see any when using an external USB HD but the speed, which is not on the top possible end.
Signature · 6 lines
+ Contact? => http://site.rusch.name/ + _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 35 lines · Devin Heitmueller
Quoted 34 lines · Robert Watkins
Quoted 11 lines · Richard Palmer
Hi,
Quoted 8 lines · Nicolas Will
Quoted 6 lines · jon bird
could be although on perusing the mailing list archives this seemed to
be a recurring problem of which various attempts have been made to investigate/fix but there didn't seem to be a conclusion to it all. Hence I just thought I'd see what the latest state of play was and report back anything potentially useful.....Quoted 9 lines
Quoted 2 lines
Well, this has normally been solved. Your report is the first one in a long time.
I'll second the report. Also with a VIA motherboard, so the USB ports could be the
culprit. Running Mythbuntu with kernel 2.6.24 and using the new firmware still gives
i2c errors.I've found Unbuntu 2.6.24-21-386 worked reasonable well with errors requiring a shut down and cold start once or twice a week.
After an upgrade, I found 2.6.27-7-generic fails within seconds of starting to record on two tuners.
dvb-usb: error while enabling fifo.The current v4l-dvb drivers have the same issue.
I also occasionally get
dib0700: firmware download failed at 17248 with -110
Quoted 7 lines
Quoted 3 lines
My PC's got ATI's IXP SB400 USB2 Host Controllers.
Rob Watkins
Hello Robert,
Are you running dib0700 firmware version 1.10 or 1.20?
Hello Devin,
I switched to 1.10 after having problems with the 1.20 firmware. I swapped the files back yesterday, and tried running with the current drivers and the 1.20 firmware after a cold boot. You are right. The 1.20 firmware is significantly better than 1.10.
A one point the 1.20 firmware ran for almost 2 hours before I noticed problems. I shut down and restarted a couple of times after that, and got errors within minutes.
The number the firmware download fails at changed each time but the "with -110" was the same.
Best Wishes,
Rob
<snip>
[ 23.538141] dib0700: loaded with support for 8 different device-types [ 23.539042] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware [ 23.539051] firmware: requesting dvb-usb-dib0700-1.20.fw [ 24.890408] lirc_dev: IR Remote Control driver registered, major 61 [ 25.090680] Linux video capture interface: v2.00 [ 25.214298] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 26.368174] dib0700: firmware download failed at 20146 with -110 [ 26.368380] usbcore: registered new interface driver dvb_usb_dib0700
<snip>
[ 76.840589] usbcore: deregistering interface driver dvb_usb_dib0700 [ 76.949087] dib0700: loaded with support for 8 different device-types [ 76.951065] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware [ 76.951079] firmware: requesting dvb-usb-dib0700-1.20.fw [ 76.955490] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 77.166854] dib0700: firmware started successfully. [ 77.668057] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 77.668149] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 77.668495] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 77.800034] DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)... [ 77.888529] MT2060: successfully identified (IF1 = 1229) [ 78.383196] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 78.383469] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 78.390786] DVB: registering adapter 1 frontend 0 (DiBcom 3000MC/P)... [ 78.417569] MT2060: successfully identified (IF1 = 1217) [ 78.974397] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [ 78.977954] usbcore: registered new interface driver dvb_usb_dib0700 [ 230.456120] dvb-usb: error while enabling fifo. [ 1958.525133] dvb-usb: error while stopping stream. [ 1976.092180] mt2060 I2C write failed [ 2281.908116] mt2060 I2C write failed [ 2676.912186] mt2060 I2C write failed [ 2806.924148] mt2060 I2C write failed (len=2) [ 2811.924179] mt2060 I2C write failed (len=6) [ 2816.924849] mt2060 I2C read failed [ 2821.932136] mt2060 I2C read failed [ 2826.940180] mt2060 I2C read failed [ 2831.949212] mt2060 I2C read failed [ 2836.957124] mt2060 I2C read failed [ 2841.968042] mt2060 I2C read failed [ 2846.976207] mt2060 I2C read failed [ 2851.985868] mt2060 I2C read failed [ 2856.993026] mt2060 I2C read failed [ 2862.000703] mt2060 I2C read failed
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
In article <1227556939.16187.0.camel@youkaida>, Nicolas Will <[email protected]> writes
Quoted 8 lines · jon bird
Quoted 6 lines
could be although on perusing the mailing list archives this seemed to
be a recurring problem of which various attempts have been made to investigate/fix but there didn't seem to be a conclusion to it all. Hence I just thought I'd see what the latest state of play was and report back anything potentially useful.....
Quoted 4 lines
Well, this has normally been solved. Your report is the first one in a long time.
Nico
well unless I missed something, this still seemed to be an issue in August this year and the result of the investigation there seemed to be still "up in the air" from what I could make out.
I'll have a look into getting another usb card for the machine, although I have a horrible suspicion I don't have any free PCI slots left in the beast....
Signature · 10 lines
== jon bird - software engineer == <reply to address _may_ be invalid, real mail below> == <reduce rsi, stop using the shift key> == posted as: news 'at' onastick 'dot' clara.co.uk _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb