Re: Call for Testers - dib0700 IR improvements
Hi, Thanks for working on improving the Nova T 500 performance, it is much appreciated, and let me know if you need further help with debugging it. I tried your dib0700-ir tree. My problems with the Nova T 500 and the 1.20 firmware have been warm reboots. Before your patch a warm reboot would give I2C errors in dmesg log with the 1.20 FW, hence I have only used my machine with cold boots since my upgrade this xmas. With the 1.10 FW and Ubuntu 7.04 + v4l tip sometime in 2008 the system have run without much problems including frequent warm reboots for 2 years. Sorry to say this patch does not solve the problem to have a working IR after a warm reboot see dmesg logs below. I have not seen any problems with high load before, so can't give any info on that matter more than it is certainly low now. The I2C errors I saw before your patch come shortly after a warm reboot (see last dmesg log included), but have not had any problems after cold boots for the past week the system have been recording. I run on: Linux hgu 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux Motherboard: ABIT IL-90MV 945GT Mobile S478 HDMI mATX CPU: Intel Core 2 Duo Mobile T5600 1.83GHz 2M DVB-T cards: Hauppauge WinTV Nova-T 500 DVB-T Twinhan VisionPlus DVB-T In a bad reception area (the Twinhan can't acceptably receive all the channels the Hauppauge can) /Harald dmesg logs: Warm reboot (after ubuntu 9.10 2.6.31-16 standard modules) got non-working remote but working video [8.282314] dib0700: loaded with support for 14 different device-types [8.282568] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [8.282615] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [8.282798] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [8.311479] DVB: registering new adapter (bttv0) [8.396083] DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)... [8.509562] usbcore: registered new interface driver snd-usb-audio [8.578470] MT2060: successfully identified (IF1 = 1228) [9.107028] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [9.107285] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [9.113153] DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... [9.119744] MT2060: successfully identified (IF1 = 1235) [9.490288] dst(0) dst_get_device_id: Recognise [DTTDIG] [9.490294] DST type flags : 0x10 firmware version = 2 [9.531093] dst(0) dst_get_mac: MAC Address=[00:08:ca:30:10:39] [9.531103] DVB: registering adapter 1 frontend 0 (DST DVB-T)... [9.684982] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1e.0/:03:06.2/usb2/2-1/input/input6 [9.685059] dvb-usb: schedule remote query interval to 50 msecs. [9.685066] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [9.685327] dib0700: rc submit urb failed Cold boot (directly after the previous) got working remote and video [ 19.445048] dib0700: loaded with support for 14 different device-types [ 19.445747] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware [ 19.445754] usb 2-1: firmware: requesting dvb-usb-dib0700-1.20.fw [ 19.498041] usbcore: registered new interface driver snd-usb-audio [ 19.508086] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 19.508115] HDA Intel :00:1b.0: setting latency timer to 64 [ 19.547850] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 19.586410] hda_codec: Unknown model for ALC882, trying auto-probe from BIOS... [ 19.586598] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input5 [ 19.699301] dst(0) dst_get_device_id: Recognise [DTTDIG] [ 19.699310] DST type flags : 0x10 firmware version = 2 [ 19.741032] dst(0) dst_get_mac: MAC Address=[00:08:ca:30:10:39] [ 19.741042] DVB: registering adapter 0 frontend 0 (DST DVB-T)... [ 19.848324] e1000e :02:00.0: irq 26 for MSI/MSI-X [ 19.904203] e1000e :02:00.0: irq 26 for MSI/MSI-X [ 19.904842] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 19.917288] dib0700: firmware started successfully. [ 19.945541] kjournald starting. Commit interval 5 seconds [ 19.946387] EXT3 FS on sda1, internal journal [ 19.946397] EXT3-fs: mounted filesystem with writeback data mode. [ 20.019719] __ratelimit: 9 callbacks suppressed [ 20.019723] type=1505 audit(1262768018.239:14): operation=profile_replace pid=1011 name=/usr/share/gdm/guest-session/Xsession [ 20.021747] type=1505 audit(1262768018.243:15): operation=profile_replace pid=1013 name=/sbin/dhclient3 [ 20.022550] type=1505 audit(1262768018.243:16): operation=profile_replace pid=1013 name=/usr/lib/NetworkManager/nm-dhcp-client.action [ 20.022984] type=1505 audit(1262768018.243:17): operation=profile_replace pid=1013 name=/usr/lib/connman/scripts/dhclient-script [
Re: Call for Testers - dib0700 IR improvements
On Wed, Jan 6, 2010 at 5:00 AM, Harald Gustafsson hgu1...@gmail.com wrote: Hi, Thanks for working on improving the Nova T 500 performance, it is much appreciated, and let me know if you need further help with debugging it. I tried your dib0700-ir tree. My problems with the Nova T 500 and the 1.20 firmware have been warm reboots. Before your patch a warm reboot would give I2C errors in dmesg log with the 1.20 FW, hence I have only used my machine with cold boots since my upgrade this xmas. With the 1.10 FW and Ubuntu 7.04 + v4l tip sometime in 2008 the system have run without much problems including frequent warm reboots for 2 years. Sorry to say this patch does not solve the problem to have a working IR after a warm reboot see dmesg logs below. I have not seen any problems with high load before, so can't give any info on that matter more than it is certainly low now. The I2C errors I saw before your patch come shortly after a warm reboot (see last dmesg log included), but have not had any problems after cold boots for the past week the system have been recording. Hi Harald, Thanks for taking the time to test and provide feedback. Just to be clear, this patch does *not* address the warm reboot problem. I am continuing to work that issue, but there should be no expectation that this patch allows the device to survive a warm reboot. It should address concerns people were seeing where the system load would be between 0.50 and 1.0 just by having the device connected, and *may* help in cases where you start to see mt2060 errors after several hours of operation. Cheers, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Call for Testers - dib0700 IR improvements
Hello, On Wed, 2010-01-06 at 09:36 -0500, Devin Heitmueller wrote: Just to be clear, this patch does *not* address the warm reboot problem. I am continuing to work that issue, but there should be no expectation that this patch allows the device to survive a warm reboot. That one would be cool. It should address concerns people were seeing where the system load would be between 0.50 and 1.0 just by having the device connected, and *may* help in cases where you start to see mt2060 errors after several hours of operation. hmmm... 32 days uptime, no mt2060 error from my NovaT500, outside of a failed read at startup. regarding the load, I'm not sure I am experiencing it, or it is shadowed by MythTV's frontend idling at 15% cpu... I'll stop the frontend during the night and look at the load in the morning. I may be able to provide a graph from munin, as I have multiple recordings, some concurrent, of the kids shows in the morning. If I have the load thing, I'll test the patch, otherwise I'll keep the WAF, and KAF, as I would not be a proper guinea pig anyway. Nico -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
