Re: [linux-dvb] DiB0700 firmware problems
Hi, On Tue, 6 Nov 2007, Nicolas Will wrote: On Wed, 2007-09-26 at 11:42 +0200, Patrick Boettcher wrote: Hi all, it seems that there still problems related to USB with the latest firmware. In order to figure out what is the problem I would like to gather some information about the affected systems: Can everyone (people who still have the disconnects and the ones who don't) please reply directly to this email giving the following information: 1) system (uname -a) 2) lspci-output 3) DiB0700 device name (USB Stick, Nova-T 500) 4) Application using the device (MythTV, VDR etc) 5) Symptoms (unusable, disconnect after x days, no problem) Please make sure that you are using the latest firmware (version 1.10) . Patrick, devs, Life has been pretty good recently with my Nova-T-500, but it still hick-ups once in a while, and of course at the worst possible moment for my wife... Nothing new from the firmware side, sorry. I will keep the list up-to-date when there is something new, worth testing. Patrick. PS: I can understand your wife. I'm experiencing similar issues. The solution is quite easy. I'm just taking her to the closest big electronic shops from time to time. Then I'm showing her the prices of the devices which even cannot do half the things my VDR can do (the combination of DVB-T and DVB-S as an example) and she realizes, that there is not alternative. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
On Wed, 2007-09-26 at 11:42 +0200, Patrick Boettcher wrote: Hi all, it seems that there still problems related to USB with the latest firmware. In order to figure out what is the problem I would like to gather some information about the affected systems: Can everyone (people who still have the disconnects and the ones who don't) please reply directly to this email giving the following information: 1) system (uname -a) 2) lspci-output 3) DiB0700 device name (USB Stick, Nova-T 500) 4) Application using the device (MythTV, VDR etc) 5) Symptoms (unusable, disconnect after x days, no problem) Please make sure that you are using the latest firmware (version 1.10) . Patrick, devs, Life has been pretty good recently with my Nova-T-500, but it still hick-ups once in a while, and of course at the worst possible moment for my wife... Has there been any progress made in that regards? I'm still game for any kind of testing, reporting and documenting. Nico http://www.youplala.net/linux/home-theater-pc ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB0700 firmware problems
Hopefully this is the right info 1) Linux andy-mediabox 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64 GNU/Linux 2)00:00.0 Host bridge: Intel Corporation Unknown device 29c0 (rev 02) 00:01.0 PCI bridge: Intel Corporation Unknown device 29c1 (rev 02) 00:1a.0 USB Controller: Intel Corporation Unknown device 2937 (rev 02) 00:1a.1 USB Controller: Intel Corporation Unknown device 2938 (rev 02) 00:1a.2 USB Controller: Intel Corporation Unknown device 2939 (rev 02) 00:1a.7 USB Controller: Intel Corporation Unknown device 293c (rev 02) 00:1b.0 Audio device: Intel Corporation Unknown device 293e (rev 02) 00:1c.0 PCI bridge: Intel Corporation Unknown device 2940 (rev 02) 00: 1c.1 PCI bridge: Intel Corporation Unknown device 2942 (rev 02) 00:1c.2 PCI bridge: Intel Corporation Unknown device 2944 (rev 02) 00:1d.0 USB Controller: Intel Corporation Unknown device 2934 (rev 02) 00:1d.1 USB Controller: Intel Corporation Unknown device 2935 (rev 02) 00:1d.2 USB Controller: Intel Corporation Unknown device 2936 (rev 02) 00:1d.7 USB Controller: Intel Corporation Unknown device 293a (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00: 1f.0 ISA bridge: Intel Corporation Unknown device 2916 (rev 02) 00:1f.2 IDE interface: Intel Corporation Unknown device 2920 (rev 02) 00:1f.3 SMBus: Intel Corporation Unknown device 2930 (rev 02) 00:1f.5 IDE interface: Intel Corporation Unknown device 2926 (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation GeForce 7300 GS (rev a1) 03:00.0 IDE interface: JMicron Technologies, Inc. Unknown device 2368 04:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364 (rev 13) 05:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 05:03.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 62) 05:03.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 62) 05:03.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) 3) DiB0700 device name ; Nova-T 500 4)MythTV 5)Has been staying up much longer since the new firmware but now I get the USB disconnects after about 6 days but it does vary, we do have reception issues sometimes due to our location if that may be related? Mythbackend Log shows this 2007-10-21 16:49:16.324 DVBSignalMonitor(0)::constructor(1,Warning, can not measure Signal Strength): No such device 2007-10-21 16:49:17.575 DVBSignalMonitor(0)::constructor(1,Warning, can not measure S/N): No such device 2007-10-21 16:49:18.127 DVBSignalMonitor(0)::constructor(1,Warning, can not measure Bit Error Rate): No such device 2007-10-21 16:49:18.349 DVBSignalMonitor(0)::constructor(1,Warning, can not count Uncorrected Blocks): No such device 2007-10-21 16:49:18.352 DVBSignalMonitor(0)::constructor(1,Error, can not read status!): No such device 2007-10-21 16:49:18.360 EITScanner: Now looking for EIT data on multiplex of channel 18 At the same time the OS log shows this Oct 21 16:29:45 andy-mediabox -- MARK -- Oct 21 16:49:16 andy-mediabox kernel: [600573.530016] mt2060 I2C write failed (len=2) Oct 21 16:49:16 andy-mediabox kernel: [600573.530270] mt2060 I2C write failed (len=6) Oct 21 16:49:16 andy-mediabox kernel: [600573.530515] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.536510] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.544375] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.552365] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.560359] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.568350] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.576343] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.584333] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.592323] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.600314] mt2060 I2C read failed Oct 21 16:49:16 andy-mediabox kernel: [600573.680192] usb 7-1: USB disconnect, address 2 Oct 21 16:49:16 andy-mediabox kernel: [600573.748118 ] mt2060 I2C write failed Oct 21 16:49:16 andy-mediabox kernel: [600573.841437] hald-addon-keyb[5184] general protection rip:2ba86da0721b rsp:7fff3d787f30 error:0 Oct 21 16:49:32 andy-mediabox kernel: [600590.083365 ] mt2060 I2C write failed (len=2) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
On 9/26/07, Patrick Boettcher [EMAIL PROTECTED] wrote: Hi all, it seems that there still problems related to USB with the latest firmware. In order to figure out what is the problem I would like to gather some information about the affected systems: Can everyone (people who still have the disconnects and the ones who don't) please reply directly to this email giving the following information: I grep-ed for keywords to try to figure out when my last nova-t failure occured, and it seems to have been sometime in august-september. I do not know what happend then, as I have made a lo of small changes (improved reception, the broadcaster has changed frequencies). But it seems to be quite stable at least. Is there any good keywords to grep for? I have tried: m2060 I2C Oops EIP and the last problem seems to have been th 14th of august. ... A little research shows that i upgraded my kernel to 2.6.22-gentoo-r2that date, (probably hg dvb-modules), and have not had any problem scince! firmware is dvb-usb-dib0700-03-pre1.fw //Simon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
Typo! I am on the latest firmware, although I listed the wrong one below :-/. Now I am getting usb disconnects without the I2C errors too. On 15 Oct 2007, at 21:14, Nicolas Will wrote: On Mon, 2007-10-15 at 20:36 +0100, David Harvey wrote: After recently saying that I had a week of clear operation... I rebooted yesterday, for my usb stick to hang the usb bus again after very little time. I've just rebuilt the latest hg source after having had a kernel upgrade (after the inital reboot/hang). Symptoms are the mt2060 I2C read and write failures. Latest firmware: dvb-usb-dib0700-01.fw. Is this a typo ? The latest firmware is dvb-usb-dib0700-1.10.fw http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
Now I have another dmesg output shortly before disconnect, this is seriously strange considering the length of smooth running before utter chaos now! dib0700: RC Query Failed dvb-usb: error while querying for an remote control event. . :-/ On 15 Oct 2007, at 21:14, Nicolas Will wrote: On Mon, 2007-10-15 at 20:36 +0100, David Harvey wrote: After recently saying that I had a week of clear operation... I rebooted yesterday, for my usb stick to hang the usb bus again after very little time. I've just rebuilt the latest hg source after having had a kernel upgrade (after the inital reboot/hang). Symptoms are the mt2060 I2C read and write failures. Latest firmware: dvb-usb-dib0700-01.fw. Is this a typo ? The latest firmware is dvb-usb-dib0700-1.10.fw http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
On 16/10/2007, at 8:21 PM, Henrik Beckman wrote: My guess is reception Yep, I can now confirm reception is a problem. I had almost 2 weeks of non-stop goodness until the wind and rain picked up here recently (Melbourne, Australia) and I've now had recordings lost on 2 out of the last 4 days. It seems that bad reception will trigger problems, VERY bad reception will trigger immediate problems. I can recreate this by turning down the amplifier on my antenna and then turning it back up. As soon as I do this, the Nova-T 500 (PCI) will crash. Dan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
On Wed, 2007-10-17 at 14:45 +1000, Dan Harper wrote: On 16/10/2007, at 8:21 PM, Henrik Beckman wrote: My guess is reception Yep, I can now confirm reception is a problem. I had almost 2 weeks of non-stop goodness until the wind and rain picked up here recently (Melbourne, Australia) and I've now had recordings lost on 2 out of the last 4 days. It seems that bad reception will trigger problems, VERY bad reception will trigger immediate problems. I can recreate this by turning down the amplifier on my antenna and then turning it back up. As soon as I do this, the Nova-T 500 (PCI) will crash. My experience goes along yours. Stability of the driver has been much better since I improved the cabling here. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
After recently saying that I had a week of clear operation... I rebooted yesterday, for my usb stick to hang the usb bus again after very little time. I've just rebuilt the latest hg source after having had a kernel upgrade (after the inital reboot/hang). Symptoms are the mt2060 I2C read and write failures. Latest firmware: dvb-usb-dib0700-01.fw. Hope this helps, I've been trying to experiment with achieveing again the great week of stability I enjoyed! dh On Thursday 27 September 2007 21:02:34 you wrote: On Thursday 27 September 2007 11:00:02 [EMAIL PROTECTED] wrote: Re: [linux-dvb] DiB0700 firmware problems Hi, I'm experiencing disconnects in a matter of hours with mythtv . Details are as follows kernel(Ubuntu Feisty): Linux frontroom 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux [EMAIL PROTECTED]:~$ lsusb Bus 004 Device 005: ID 2040:7060 Hauppauge Device: Wintv Nova-T usb App: Mythtv Symptoms: Disconnects after anything between a couple of hours or days. Using the latest firmware and hg-src of the same date as the firmware was released. Thanks for your efforts. Happy to help if I can do anything further. dh ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
My findings... 1) system (uname -a) Linux vdr-tng 2.6.20-rc6 #1 PREEMPT Tue Jan 30 10:27:20 GMT 2007 i686 GNU/Linux (This is with DVB drivers checked out from mercurial repository on 28/09/07.) System is a Via Epia MII-12000 with a 1200 MHz Via Nehemiah processor. 2) lspci-output 00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 00:14.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:14.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:14.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03) Output of lsusb: Bus 003 Device 001: ID : Bus 007 Device 002: ID 2040:9950 Hauppauge Bus 007 Device 001: ID : Bus 006 Device 004: ID 2040:9301 Hauppauge Hauppauge WinTV NOVA-T USB2 (warm) Bus 006 Device 001: ID : Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 001 Device 003: ID 0a81:0101 Chesen Electronics Corp. Keyboard Bus 001 Device 001: ID : Bus 002 Device 001: ID : 3) DiB0700 device name (USB Stick, Nova-T 500) Nova-T 500 in the only PCI slot and a Nova-T USB2 plugged into a USB port. I have no remote connected to the Nova-T 500 and I'm using options dvb-usb disable_rc_polling=1 with the dvb-usb module to disable them (I'm using a LIRC remote on a serial port.) I'm also using options dvb_usb_dib0700 force_lna_activation=1 to enable the amplifiers, although I've not really tested to see whether I need to or not. 4) Application using the device (MythTV, VDR etc) Vdr-1.5.9, using hardware MPEG-2 decoding with softdevice. The system runs 24 h a day because it doesn't always power itself off fully for some reason so I can't use nvram-wakeup. 5) Symptoms (unusable, disconnect after x days, no problem) When I was using the DVB drivers from this kernel (built back in January, I think) the system would work fine for a few days and then I would see a USB disconnect followed by lots of dib-usb (I think: they've now rotated out of my logs!) error messages because there was no data. These disconnects seemed to be mainly the Nova-T USB2, i.e. the external USB device, and would be accompanied by the LED going out. The only way to get it going again was to reboot: presumably it was in a warm state and there was no firmware upload (dvb-usb-nova-t-usb2-01.fw). These disconnects seemed to happen pretty randomly: sometimes it would work for a few hours, sometimes for a week or so. I have a cron job running which tests to see if it's disconnected and reboots it if so. (I have a second Nova-T USB2 but the disconnects seemed to occur much more frequently with two of them connected.) If anything, the disconnects tended to happen a few minutes after a timed recording had started, i.e. possibly after tuning to a different MUX but I can't be certain of this. I updated to the more recent drivers a few days back and I'm now using the dvb-usb-dib0700-1.10.fw firmware. Since updating, I haven't seen any of the USB disconnects but it has hung totally a few times. On a couple of occasions it ran perfectly for about a day or two and then hung; another time it only worked for about 30 minutes before it hung. Each time it has hung there has been nothing in any log files but the LED on the external USB device is still illuminated, unlike when it was disconnecting with the older drivers + firmware. I'll keep monitoring this...might try with two external USB devices too! Cheers, Laz ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
On Thursday 04 October 2007 10:09, Laz wrote: My findings... When I was using the DVB drivers from this kernel (built back in January, I think) the system would work fine for a few days and then I would see a USB disconnect followed by lots of dib-usb (I think: they've now rotated out of my logs!) error messages because there was no data. These disconnects seemed to be mainly the Nova-T USB2, i.e. the external USB device, and would be accompanied by the LED going out. The only way to get it going again was to reboot: presumably it was in a warm state and there was no firmware upload (dvb-usb-nova-t-usb2-01.fw). I've just experienced a USB disconnect from the external Nova-T USB2 with the new firmware: the LED went out but the system didn't hang. syslog contained: Oct 4 20:28:59 vdr-tng kernel: hub 6-0:1.0: state 7 ports 6 chg evt 0002 Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: GetStatus port 1 status 00100a POWER sig=se0 PEC CSC Oct 4 20:28:59 vdr-tng kernel: hub 6-0:1.0: port 1, status 0100, change 0003, 12 Mb/s Oct 4 20:28:59 vdr-tng kernel: usb 6-1: USB disconnect, address 4 Oct 4 20:28:59 vdr-tng kernel: usb 6-1: unregistering device Oct 4 20:28:59 vdr-tng kernel: usb 6-1: usb_disable_device nuking all URBs Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202180 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202420 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202480 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202300 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb2022a0 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb202240 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: ehci_hcd :00:10.3: shutdown urb cb2021e0 pipe c0030480 ep6in-bulk Oct 4 20:28:59 vdr-tng kernel: dvb-usb: bulk message failed: -22 (6/2) ^- lots of this last one interspersed with blocks of similar messages with the final number replaced by -1072586294, -996626800, -863886798, -862828572, 402659331, 0, -22, 52, etc. in a variety of orders until I rebooted. (This is pretty much what I was seeing with the old driver + firmware but more often.) Cheers, Laz ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB0700 firmware problems
Sorry for the report delay, I've been without internet connection for some days. Here it goes: 1) system (uname -a) Linux mediacenter 2.6.22-sabayon #1 SMP Wed Jul 11 18:56:46 CEST 2007 i686 AMD Athlon(tm) 64 Processor 3800+ AuthenticAMD GNU/Linux Using the lastest firmware and drivers compiled from HG repository. The date of the dvb-usb-dib0700.ko module (that is, when I pulled the code from HG) is Sept. 11. I also manually added the patch that prevents the repeating of the error messages in dmesg whenever you use another IR control. No other patches were applied. 2) lspci-output 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev c0) 01:0e.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 61) 01:0e.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 61) 01:0e.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) 3) DiB0700 device name (USB Stick, Nova-T 500) Nova-T 500, including its remote. No other DVB or video capture devices present. 4) Application using the device (MythTV, VDR etc) MythTV exclusively (lastest stable version - 0.20.2 - from Gentoo portage). 5) Symptoms (unusable, disconnect after x days, no problem) Mostly stable up to date. I usually have good tunning from both tuners, and the IR is working pretty well. However I keep experiencing ocasional minor but annoying issues like these: - MythTV backend sometimes hang when exploring for EIT data when idle. No error messages appear on dmesg, just it hangs. The last line displayed into /var/log/mythtv/mythbackend.log reads somethink like Now looking for EIT data in multiplex for channel x Whenever this happens the MythTV backend is completely hanged so frontend is unable to connect to it. Restarting the backend usually solves the problem, so I really don't know who must I blame, the card or MythTV itself. - Occasional, isolated, mt2060 read / write errors in dmesg. No problems in MythTV when this happens, thought. - Occasional failed tunnings (yesterday, i.e.). There were no errors displayed in dmesg, but MythTV was unable to acquire a lock on the channel for LiveTV view. I needed to restart the mythbackend a couple of times before it started working fine again. Briefly: it works nearly perfect since lastest firmware release. I'm currently using the remote, which it was completely impossible before because the system hanged very often when I used the TV remote (and when I say hanged I mean hanged: it was something like a total collapse of the USB subsystem, so even the keyboard was responding slowly, about 3-4 sec delay per keypress), needing a complete powercycle of the computer to render it operative again. I'd like to note that, even despite the problems mentioned before, I've had NO USB disconnects since the firmware release. I mean that for any of the problems above (MythTV backend hanging, mt2060 read / write error, etc...) there was no USB disconnect message in dmesg. So for my part this issue seems to be fixed. Anyway: as other times before, let me thank you again for the big amount of work you guys are putting into this. Best
Re: [linux-dvb] DiB0700 firmware problems
I demand that Eduard Huguet may or may not have written... [snip] Briefly: it works nearly perfect since lastest firmware release. I'm currently using the remote, which it was completely impossible before because the system hanged very often when I used the TV remote (and when I say hanged I mean hanged: That'd be remote control as executioner, then... ;-) (Hint: you mean hung.) [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Burn less waste. Use less packaging. Waste less. USE FEWER RESOURCES. Don't vote - it only encourages them! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
Hmm, It seems like it only happens while recording on both tuners. I´ll dig some more and see if there is any pattern with MUXes or other. /Henrik On 9/26/07, Patrick Boettcher [EMAIL PROTECTED] wrote: Hi all, it seems that there still problems related to USB with the latest firmware. In order to figure out what is the problem I would like to gather some information about the affected systems: Can everyone (people who still have the disconnects and the ones who don't) please reply directly to this email giving the following information: 1) system (uname -a) 2) lspci-output 3) DiB0700 device name (USB Stick, Nova-T 500) 4) Application using the device (MythTV, VDR etc) 5) Symptoms (unusable, disconnect after x days, no problem) Please make sure that you are using the latest firmware (version 1.10) . thanks and regards, Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
On Thursday 27 September 2007 11:00:02 [EMAIL PROTECTED] wrote: Re: [linux-dvb] DiB0700 firmware problems Hi, I'm experiencing disconnects in a matter of hours with mythtv . Details are as follows kernel(Ubuntu Feisty): Linux frontroom 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux [EMAIL PROTECTED]:~$ lsusb Bus 004 Device 005: ID 2040:7060 Hauppauge Device: Wintv Nova-T usb App: Mythtv Symptoms: Disconnects after anything between a couple of hours or days. Using the latest firmware and hg-src of the same date as the firmware was released. Thanks for your efforts. Happy to help if I can do anything further. dh ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiB0700 firmware problems
Hi all, it seems that there still problems related to USB with the latest firmware. In order to figure out what is the problem I would like to gather some information about the affected systems: Can everyone (people who still have the disconnects and the ones who don't) please reply directly to this email giving the following information: 1) system (uname -a) 2) lspci-output 3) DiB0700 device name (USB Stick, Nova-T 500) 4) Application using the device (MythTV, VDR etc) 5) Symptoms (unusable, disconnect after x days, no problem) Please make sure that you are using the latest firmware (version 1.10) . thanks and regards, Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
Dne st 26. září 2007 Patrick Boettcher napsal(a): Hi all, Hi Patrick, it seems that there still problems related to USB with the latest firmware. In order to figure out what is the problem I would like to gather some information about the affected systems: Can everyone (people who still have the disconnects and the ones who don't) please reply directly to this email giving the following information: 1) system (uname -a) 2.6.22.5, i386, Pentium M, intel USB 2.0 uhci/ehci 2) lspci-output 3) DiB0700 device name (USB Stick, Nova-T 500) Leadtek WinFast DTV Dongle 4) Application using the device (MythTV, VDR etc) kaffeine 5) Symptoms (unusable, disconnect after x days, no problem) With latest svn snapshoot and 1.10 firmware during sw suspend to disk I see tons of key pressed (but it is not true, keypad doesn't return any keypresses in normal state and I press nothing) and it won't suspend. With same kernel patch and pre3 firmware I see same messages, but it suspends and resume well. Irda doesn't work for me - no numbers returns to terminal pressing 1-9 etc, but let blinks on the dongle, so possibly it recognizes somethink. Kaffeine application is always killed/closed before suspending. Please make sure that you are using the latest firmware (version 1.10) . Yes I am, but without suspend it is not usable for me. thanks and regards, Patrick. See ya! Hope this will help! Michal -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
