USB Wintv HVR-900 Hauppauge
Hello,
I am trying to set up the dvb-t device in my ubuntu 9.04.
As far as i can see , this device has tm6000 chipset but I don't get it works. I have followed the guide of tvlinux.org:
http://www.linuxtv.org/wiki/index.php/Trident_TM6000#TM6000_based_Devices
I have compile v4l-dvb, make, and make install and it seems that the modules are loaded:
em28xx 90668 0 ir_common 57732 1 em28xx v4l2_common 25600 1 em28xx videobuf_vmalloc 14724 1 em28xx videobuf_core 26244 2 em28xx,videobuf_vmalloc tveeprom 20228 1 em28xx videodev 44832 3 em28xx,v4l2_common,uvcvideo
But by the moment, I don't know which driver I should you. Actually, when I switch the usb wintv on , my so doesn't recognize it:
[11107.449900] usb 1-3: new high speed USB device using ehci_hcd and address 8 [11107.593094] usb 1-3: configuration #1 chosen from 1 choice
how can I get this device run?
thank you in advance.
Miguel
Quoted 29 lines · Miguel
Hello,
I am trying to set up the dvb-t device in my ubuntu 9.04.
As far as i can see , this device has tm6000 chipset but I don't get it works. I have followed the guide of tvlinux.org:
http://www.linuxtv.org/wiki/index.php/Trident_TM6000#TM6000_based_DevicesI have compile v4l-dvb, make, and make install and it seems that the modules are loaded:
em28xx 90668 0
ir_common57732 1 em28xxv4l2_common25600 1 em28xxvideobuf_vmalloc14724 1 em28xxvideobuf_core26244 2 em28xx,videobuf_vmalloc tveeprom 20228 1 em28xx
videodev 44832 3 em28xx,v4l2_common,uvcvideoBut by the moment, I don't know which driver I should you. Actually, when I switch the usb wintv on , my so doesn't recognize it:
[11107.449900] usb 1-3: new high speed USB device using ehci_hcd and address 8 [11107.593094] usb 1-3: configuration #1 chosen from 1 choice
Quoted 5 lines
how can I get this device run?
thank you in advance.
Miguel
Hello Miguel,
Can you confirm the exact model number of the device (or provide the USB ID)? I suspect you probably have what is often referred to as an HVR-900 R2, which is not currently supported under Linux.
I've got it working here but still need to write the firmware extract script so I can release it, but the work has been delayed due to other priorities.
Cheers,
Devin
Signature · 2 lines
Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com
A message that is not in the archive (sent off-list or not yet received): 1250701340.14727.28.camel@McM
Quoted 8 lines · Miguel
oh, what a shame, :-s
The USB id is:
Bus 001 Device 011: ID 2040:6600 Hauppauge
is this the version you commented that is not supported?
Ah, ok. So you really do have an HVR-900H and not an HVR-900 (either R1 or R2). Since this is the case, your device really is TM6000 based, but that development tree has not been worked on in a very long time and is known to be broken.
Unfortunately, it is not clear when/if Mauro will ever get back to getting that bridge to a supported state (it hasn't had any active development in over nine months).
Devin
Signature · 2 lines
Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com
A message that is not in the archive (sent off-list or not yet received): 1250761934.6730.2.camel@McM
Quoted 16 lines · Miguel
hi again Devin,
In this case, the guide :
http://www.linuxtv.org/wiki/index.php/Trident_TM6000#TM6000_based_Devices
should be work ?I get some errors applying the patch:
mcm@McM:~/opt/hvr900/v4l-dvb$ patch -p1 < tm6000-makefile-dvb-tree.patch patching file linux/drivers/media/video/Kconfig Hunk #1 succeeded at 914 with fuzz 2 (offset 218 lines). patching file linux/drivers/media/video/Makefile Hunk #1 FAILED at 67. 1 out of 1 hunk FAILED -- saving rejects to file linux/drivers/media/video/Makefile.rej
Quoted 1 line
could it be my problem here?
No, that guide will not work for your device. The HVR-900H uses the TM6010, not the TM6000, and as the Wiki states, the driver is completely broken:
http://www.linuxtv.org/wiki/index.php/Trident_TM6000#TM6010_based_Devices
Devin
Signature · 2 lines
Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com
Em Wed, 19 Aug 2009 13:16:23 -0400
Devin Heitmueller <[email protected]> escreveu:
Quoted 3 lines
Unfortunately, it is not clear when/if Mauro will ever get back to getting that bridge to a supported state (it hasn't had any active development in over nine months).
This is a recorrent question, already discussed at the ML. Probably, I should update the wiki.
The driver is still on my TODO list. I intend to return back to it, but this is not on my current top priorities. Those chips are very buggy and they behave badly if the driver doesn't do exactly the same thing as the original one (it starts to loose frames). I suspect that this is a firmware bug at tm6000/tm6010, although I'm not sure. Maybe the conversion of the driver to the new i2c approach could help to fix this issue, since this will avoid sending probing packets at i2c bus. Also, on all tests we've done so far, it can't reliably read data from an i2c device. This prevents that tools like scan to properly detect the signal strength of a channel. You can't even be sure if xc3028 firmware were successfully loaded on this device, due to this issue.
It is important to notice that the vendor (Trident) doesn't seem to want helping with open source development. I tried during 2007 and 2008 to get their help by opening docs to me, via Linux Foundation NDA program, without success. Currently, they are refusing so far to help with their demod DRX-K line that they acquired from Micronas (as pointed at http://linux.terratec.de/tv_en.html).
In brief, while I want to fix the driver issues, I recommend to avoid buying any devices with tm5600/tm6000/tm6010 (and DRX demod) chips. There are other offers at the market with drivers that work properly, including some nice HVR devices that are fully supported.
Cheers,
Mauro
Quoted 4 lines · Mauro Carvalho Chehab
In brief, while I want to fix the driver issues, I recommend to avoid buying any devices with tm5600/tm6000/tm6010 (and DRX demod) chips. There are other offers at the market with drivers that work properly, including some nice HVR devices that are fully supported.
The more I think about it, the more I think we should setup something along the lines of a "Wall of Shame" on the LinuxTV wiki, so that people will be better informed exactly which products they should not buy because of the chipset vendor's behavior.
Devin
Signature · 2 lines
Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com
Quoted 7 lines · Devin Heitmueller
Quoted 4 lines · Mauro Carvalho Chehab
In brief, while I want to fix the driver issues, I recommend to avoid buying any devices with tm5600/tm6000/tm6010 (and DRX demod) chips. There are other offers at the market with drivers that work properly, including some nice HVR devices that are fully supported.
Quoted 5 lines
The more I think about it, the more I think we should setup something along the lines of a "Wall of Shame" on the LinuxTV wiki, so that people will be better informed exactly which products they should not buy because of the chipset vendor's behavior.
I doubt that this will help, it will moreover scare them off and also put a bad light on Linux we already have a list of supported devices on linuxtv.org if people buy the wrong devices it's their fault in the end.
Better support the available devices properly so that everyone can easily use them... "everyone" is the highest burden at this time...
James
Quoted 10 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Em Fri, 21 Aug 2009 18:27:30 +0200
James Peters <[email protected]> escreveu:
Quoted 14 lines
Quoted 11 lines · Devin Heitmueller
Quoted 4 lines · Mauro Carvalho Chehab
In brief, while I want to fix the driver issues, I recommend to avoid buying any devices with tm5600/tm6000/tm6010 (and DRX demod) chips. There are other offers at the market with drivers that work properly, including some nice HVR devices that are fully supported.
The more I think about it, the more I think we should setup something along the lines of a "Wall of Shame" on the LinuxTV wiki, so that people will be better informed exactly which products they should not buy because of the chipset vendor's behavior.
Quoted 7 lines
I doubt that this will help, it will moreover scare them off and also put a bad light on Linux we already have a list of supported devices on linuxtv.org if people buy the wrong devices it's their fault in the end.
Better support the available devices properly so that everyone can easily use them... "everyone" is the highest burden at this time...
I sort of agree with you both. From one side, IMO, it is very badly documented, currently, what are the manufacturers that helps the project, and on what level, and what are the ones that refuses to help.
On the other hand, just blaming the manufacturer won't solve. There are even some cases where the rights for certain parts of their hardware belongs to a third party, so, even if they want to help, maybe they can't on some cases. Unfortunately, I've seen some cases where the hardware and binary distribution rights were transferred from one company to the other, but, apparently, the source code and/or development datasheet rights were not transferred.
Maybe we could create a search engine at linuxtv with the info we have about each board, that could report some specific troubles we're having with some board/vendor info, reporting also if the vendor helped with some driver.
Cheers,
Mauro
Quoted 17 lines · Devin Heitmueller
Quoted 8 lines · Miguel
Hello,
I am trying to set up the dvb-t device in my ubuntu 9.04.
As far as i can see , this device has tm6000 chipset but I don't get it works. I have followed the guide of tvlinux.org:
http://www.linuxtv.org/wiki/index.php/Trident_TM6000#TM6000_based_DevicesQuoted 5 lines
how can I get this device run?
thank you in advance.
Miguel
Hello Miguel,
Quoted 8 lines
Can you confirm the exact model number of the device (or provide the USB ID)? I suspect you probably have what is often referred to as an HVR-900 R2, which is not currently supported under Linux.
I've got it working here but still need to write the firmware extract script so I can release it, but the work has been delayed due to other priorities.
Hello Devin,
I own a HVR-900 R2 and if you need help in testing i'd be more than happy to help.
It's nice to see that for this device could there finally be light at the end of the tunnel.
Signature · 3 lines
Thank you, regards, dedioste
Quoted 6 lines · Stefano De Dionigi
Hello Devin,
I own a HVR-900 R2 and if you need help in testing i'd be more than happy to help.
It's nice to see that for this device could there finally be light at the end of the tunnel.
Hello Dedioste,
Fortunately, in this case I have the device pretty well tested using the generator. I just have to get the firmware extract script written so that the changes can actually be released.
Keep an eye on the Kernellabs blog (http://www.kernellabs.com/blog),
since when I have a tree setup I will likely put out a call for testers before the changes go upstream into the v4l-dvb mainline.
Cheers,
Devin
Signature · 2 lines
Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com