Re: Hauppauge HVR900H don't work with kernel 3.*
Hi, Try with 2.6.39 and it work but I've some freezes. I've try copying tm6000 directory from 2.6.39 to 3.0 and it as work sometimes. This is not an issue because this produce kernels panics. So for me there are 2 problems: - 2.6.38 dvb-t work good - 2.6.39, dvb-t work but sometime freeze the computer - 3.* dvb-t don't work I'm trying to apply all the patchs from a 2.6.38 to obtain the same files as a 3.0 to find what patch causes the problem but I've a lot of errors. Thanks On 17 November 2011 19:35, Esteban Tarroni a écrit : Norret Thierry tnorret at yahoo.com writes: Hello, I have this card http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-900H and use gentoo id 2040:6600 Since I upgrade my kernel from 2.6.38 to 3.* scan for channel doesn't work and channels can't be lock The modules (tm6000) are load, the firmware (xc3028L-v36.fw) is copied to /lib/firmware, the signal is good but no channels found with w_scan/vlc/mplayer/kaffeineI don't see any error in dmesg. I've try last distros (ubuntu 11.10, fedora 16) with kernel 3.* and same results. The last git sources from v4l/dvb don't resolve the problem. Thanks # dmesg [ 81.132653] IR NEC protocol handler initialized [ 81.158229] tm6000: module is from the staging directory, the quality is unknown, you have been warned. [ 81.158801] tm6000 v4l2 driver version 0.0.2 loaded [ 81.160885] tm6000: alt 0, interface 0, class 255 [ 81.160890] tm6000: alt 0, interface 0, class 255 [ 81.160895] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes) [ 81.160899] tm6000: alt 0, interface 0, class 255 [ 81.160903] tm6000: alt 1, interface 0, class 255 [ 81.160907] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes) [ 81.160911] tm6000: alt 1, interface 0, class 255 [ 81.160914] tm6000: alt 1, interface 0, class 255 [ 81.160918] tm6000: INT IN endpoint: 0x83 (max size=4 bytes) [ 81.160922] tm6000: alt 2, interface 0, class 255 [ 81.160925] tm6000: alt 2, interface 0, class 255 [ 81.160929] tm6000: alt 2, interface 0, class 255 [ 81.160932] tm6000: alt 3, interface 0, class 255 [ 81.160936] tm6000: alt 3, interface 0, class 255 [ 81.160939] tm6000: alt 3, interface 0, class 255 [ 81.160943] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0) [ 81.160947] tm6000: Found Hauppauge WinTV HVR-900H / WinTV USB2-Stick [ 81.167856] Found tm6010 [ 81.176973] IR RC5(x) protocol handler initialized [ 81.183409] IR RC6 protocol handler initialized [ 81.185159] IR JVC protocol handler initialized [ 81.187524] IR Sony protocol handler initialized [ 81.201304] lirc_dev: IR Remote Control driver registered, major 250 [ 81.206121] IR LIRC bridge handler initialized [ 81.964984] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00 00 40 40 20 00 66 .YTE...@@ .f [ 82.076933] tm6000 #0: i2c eeprom 10: 69 00 10 20 40 01 02 03 48 00 79 00 62 00 72 00 i.. @...H.y.b.r. [ 82.188834] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff ff ff ff ff ff ff ..d. [ 82.300725] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.412622] tm6000 #0: i2c eeprom 40: 10 03 48 00 56 00 52 00 39 00 30 00 30 00 48 00 ..H.V.R.9.0.0.H. [ 82.524561] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.636402] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff 0a 03 32 00 2e 00 0...2... [ 82.748303] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?... [ 82.860197] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.972092] tm6000 #0: i2c eeprom 90: 32 ff ff ff 16 03 34 00 30 00 33 00 32 00 31 00 2.4.0.3.2.1. [ 83.083977] tm6000 #0: i2c eeprom a0: 33 00 34 00 39 00 30 00 32 00 00 00 00 00 ff ff 3.4.9.0.2... [ 83.195871] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.307773] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.419666] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.531535] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.643448] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.801012] i2c-core: driver [tuner] using legacy suspend method [ 83.801017] i2c-core: driver [tuner] using legacy resume method [ 83.801303] tuner 1-0061: Tuner -1 found with type(s) Radio TV. [ 83.801309] xc2028 1-0061: creating new instance [ 83.801311] xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner [ 83.801313] Setting firmware parameters for
Re: Hauppauge HVR900H don't work with kernel 3.*
Norret Thierry tnorret at yahoo.com writes: Hello, I have this card http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-900H and use gentoo Since I upgrade my kernel from 2.6.38 to 3.* scan for channel doesn't work and channels can't be lock The modules (tm6000) are load, the firmware (xc3028L-v36.fw) is copied to /lib/firmware, the signal is good but no channels found with w_scan/vlc/mplayer/kaffeineI don't see any error in dmesg. I've try last distros (ubuntu 11.10, fedora 16) with kernel 3.* and same results. The last git sources from v4l/dvb don't resolve the problem. Thanks # dmesg [ 81.132653] IR NEC protocol handler initialized [ 81.158229] tm6000: module is from the staging directory, the quality is unknown, you have been warned. [ 81.158801] tm6000 v4l2 driver version 0.0.2 loaded [ 81.160885] tm6000: alt 0, interface 0, class 255 [ 81.160890] tm6000: alt 0, interface 0, class 255 [ 81.160895] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes) [ 81.160899] tm6000: alt 0, interface 0, class 255 [ 81.160903] tm6000: alt 1, interface 0, class 255 [ 81.160907] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes) [ 81.160911] tm6000: alt 1, interface 0, class 255 [ 81.160914] tm6000: alt 1, interface 0, class 255 [ 81.160918] tm6000: INT IN endpoint: 0x83 (max size=4 bytes) [ 81.160922] tm6000: alt 2, interface 0, class 255 [ 81.160925] tm6000: alt 2, interface 0, class 255 [ 81.160929] tm6000: alt 2, interface 0, class 255 [ 81.160932] tm6000: alt 3, interface 0, class 255 [ 81.160936] tm6000: alt 3, interface 0, class 255 [ 81.160939] tm6000: alt 3, interface 0, class 255 [ 81.160943] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0) [ 81.160947] tm6000: Found Hauppauge WinTV HVR-900H / WinTV USB2-Stick [ 81.167856] Found tm6010 [ 81.176973] IR RC5(x) protocol handler initialized [ 81.183409] IR RC6 protocol handler initialized [ 81.185159] IR JVC protocol handler initialized [ 81.187524] IR Sony protocol handler initialized [ 81.201304] lirc_dev: IR Remote Control driver registered, major 250 [ 81.206121] IR LIRC bridge handler initialized [ 81.964984] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00 00 40 40 20 00 66 .YTE...@@ .f [ 82.076933] tm6000 #0: i2c eeprom 10: 69 00 10 20 40 01 02 03 48 00 79 00 62 00 72 00 i.. @...H.y.b.r. [ 82.188834] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff ff ff ff ff ff ff ..d. [ 82.300725] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.412622] tm6000 #0: i2c eeprom 40: 10 03 48 00 56 00 52 00 39 00 30 00 30 00 48 00 ..H.V.R.9.0.0.H. [ 82.524561] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.636402] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff 0a 03 32 00 2e 00 0...2... [ 82.748303] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?... [ 82.860197] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.972092] tm6000 #0: i2c eeprom 90: 32 ff ff ff 16 03 34 00 30 00 33 00 32 00 31 00 2.4.0.3.2.1. [ 83.083977] tm6000 #0: i2c eeprom a0: 33 00 34 00 39 00 30 00 32 00 00 00 00 00 ff ff 3.4.9.0.2... [ 83.195871] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.307773] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.419666] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.531535] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.643448] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.801012] i2c-core: driver [tuner] using legacy suspend method [ 83.801017] i2c-core: driver [tuner] using legacy resume method [ 83.801303] tuner 1-0061: Tuner -1 found with type(s) Radio TV. [ 83.801309] xc2028 1-0061: creating new instance [ 83.801311] xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner [ 83.801313] Setting firmware parameters for xc2028 [ 83.804849] xc2028 1-0061: Loading 81 firmware images from xc3028L-v36.fw, type: xc2028 firmware, ver 3.6 [ 84.021087] xc2028 1-0061: Loading firmware for type=BASE (1), id . [ 109.684698] xc2028 1-0061: Loading firmware for type=(0), id b700. [ 110.118322] SCODE (2000), id b700: [ 110.118331] xc2028 1-0061: Loading SCODE for type=MONO SCODE HAS_IF_4320 (60008000), id 8000. [ 110.733824] tm6000 #0: registered device video1 [ 110.733831] Trident TVMaster TM5600/TM6000/TM6010 USB2 board (Load status: 0) [ 110.733865] usbcore: registered new interface driver tm6000 [ 110.735587]
Re: Hauppauge HVR900H don't work with kernel 3.*
Same problem here since upgrade to ubuntu 11.10 I've found these topics but no solutions http://forum.ubuntuusers.de/topic/dvb-t-stick-wird-nicht-erkannt http://forum.ubuntu-it.org/index.php/topic,59926.160.html http://forums.gentoo.org/viewtopic-t-900714.html -- 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: Hauppauge HVR900H don't work with kernel 3.*
i dont know about digital, but to me it crashes the USB probe after connect-disconnect-reconnect. after that, it doesnt notice any changes in connected USB devices and need to restart. it may be possible, that there is some module hanging in there, because i get the same problem when i have femon running and then disconnect the dvb device (no matter which one - volarHD in my case), because it is stuck as femon uses the driver. when i kill femon, everything runns again. so my theory is, that there is somewhat stuck in there. and it doesnt help to remove the DVB driver. so it is definitely something with the analogue part (and analog is what i need, because there are not many devices that do analog any more). On Wed, 9 Nov 2011 21:08:59 + (GMT) Norret Thierry tnor...@yahoo.com wrote: Hello, I have this card http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-900H and use gentoo Since I upgrade my kernel from 2.6.38 to 3.* scan for channel doesn't work and channels can't be lock The modules (tm6000) are load, the firmware (xc3028L-v36.fw) is copied to /lib/firmware, the signal is good but no channels found with w_scan/vlc/mplayer/kaffeineI don't see any error in dmesg. I've try last distros (ubuntu 11.10, fedora 16) with kernel 3.* and same results. The last git sources from v4l/dvb don't resolve the problem. Thanks # dmesg [ 81.132653] IR NEC protocol handler initialized [ 81.158229] tm6000: module is from the staging directory, the quality is unknown, you have been warned. [ 81.158801] tm6000 v4l2 driver version 0.0.2 loaded [ 81.160885] tm6000: alt 0, interface 0, class 255 [ 81.160890] tm6000: alt 0, interface 0, class 255 [ 81.160895] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes) [ 81.160899] tm6000: alt 0, interface 0, class 255 [ 81.160903] tm6000: alt 1, interface 0, class 255 [ 81.160907] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes) [ 81.160911] tm6000: alt 1, interface 0, class 255 [ 81.160914] tm6000: alt 1, interface 0, class 255 [ 81.160918] tm6000: INT IN endpoint: 0x83 (max size=4 bytes) [ 81.160922] tm6000: alt 2, interface 0, class 255 [ 81.160925] tm6000: alt 2, interface 0, class 255 [ 81.160929] tm6000: alt 2, interface 0, class 255 [ 81.160932] tm6000: alt 3, interface 0, class 255 [ 81.160936] tm6000: alt 3, interface 0, class 255 [ 81.160939] tm6000: alt 3, interface 0, class 255 [ 81.160943] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0) [ 81.160947] tm6000: Found Hauppauge WinTV HVR-900H / WinTV USB2-Stick [ 81.167856] Found tm6010 [ 81.176973] IR RC5(x) protocol handler initialized [ 81.183409] IR RC6 protocol handler initialized [ 81.185159] IR JVC protocol handler initialized [ 81.187524] IR Sony protocol handler initialized [ 81.201304] lirc_dev: IR Remote Control driver registered, major 250 [ 81.206121] IR LIRC bridge handler initialized [ 81.964984] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00 00 40 40 20 00 66 .YTE...@@ .f [ 82.076933] tm6000 #0: i2c eeprom 10: 69 00 10 20 40 01 02 03 48 00 79 00 62 00 72 00 i.. @...H.y.b.r. [ 82.188834] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff ff ff ff ff ff ff ..d. [ 82.300725] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.412622] tm6000 #0: i2c eeprom 40: 10 03 48 00 56 00 52 00 39 00 30 00 30 00 48 00 ..H.V.R.9.0.0.H. [ 82.524561] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.636402] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff 0a 03 32 00 2e 00 0...2... [ 82.748303] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?... [ 82.860197] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 82.972092] tm6000 #0: i2c eeprom 90: 32 ff ff ff 16 03 34 00 30 00 33 00 32 00 31 00 2.4.0.3.2.1. [ 83.083977] tm6000 #0: i2c eeprom a0: 33 00 34 00 39 00 30 00 32 00 00 00 00 00 ff ff 3.4.9.0.2... [ 83.195871] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.307773] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.419666] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.531535] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.643448] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 83.801012] i2c-core: driver [tuner] using legacy suspend method [ 83.801017] i2c-core: driver [tuner] using legacy resume method [ 83.801303] tuner 1-0061: Tuner -1 found with type(s) Radio TV. [ 83.801309] xc2028 1-0061: creating new instance [ 83.801311] xc2028 1-0061: type
