Using tm6010 for Haupauge WinTV-HVR 900H

Using tm6010 for Haupauge WinTV-HVR 900H

[David Woitkowski]

[Reposted from linux-dvb because mailman told me linux-dvb is to be 
replaced with linux-media. If you've already read this, just skip.]




Hi out there

I'm in the unfortunate position of having bought a 900H instead of a 900
and now I'm fiddling with the driver.

Details:
$ lsusb | grep Hauppauge
Bus 008 Device 004: ID 2040:6600 Hauppauge

My machine is running Ubuntu 8.10 with a 2.6.27-11-generic kernel. The
correct kernel-headers are installed.

As far as I've read there is (limited) support for the device with the
tm6010 driver. Putting together some info from the web I did the following:

$ hg clone http://linuxtv.org/hg/v4l-dvb
$ cd v4l-dvb
$ hg pull -u http://linuxtv.org/hg/~mchehab/tm6010

Inserted into v4l-dvb/v4l/.config three lines:
CONFIG_VIDEO_TM6000_ALSA=m
CONFIG_VIDEO_TM6000=m
CONFIG_VIDEO_TM6000_DVB=m

$ hg merge
$ make

and as root:
# make install

This far everything worked without error.

Then I got the Firmware the card was requesting in the dmesg-output from
http://steventoth.net/linux/hvr1400/xc3028L-v36.fw and copied it to /lib
/firmware

Since there is no Module tm6000 I did
# modprobe -v tm6000
insmod
/lib/modules/2.6.27-11-generic/kernel/drivers/media/video/videobuf-core.ko
insmod
/lib/modules/2.6.27-11-generic/kernel/drivers/media/video/videobuf-vmalloc.ko 


insmod /lib/modules/2.6.27-11-generic/kernel/drivers/i2c/i2c-core.ko
insmod
/lib/modules/2.6.27-11-generic/kernel/drivers/media/video/tm6000/tm6000.ko

$ dmesg
[  187.646908] tm6000 v4l2 driver version 0.0.1 loaded
[  187.647898] usbcore: registered new interface driver tm6000

(tail /var/log/messages gives the same info)

Now - as I hope the module is loaded correctly - I attacht the USB-Device:

$ dmesg
[  373.881042] usb 8-1: new high speed USB device using ehci_hcd and
address 3
[  374.019648] usb 8-1: configuration #1 chosen from 1 choice
[  374.023090] tm6000: alt 0, interface 0, class 255
[  374.023102] tm6000: alt 0, interface 0, class 255
[  374.023107] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes)
[  374.023111] tm6000: alt 0, interface 0, class 255
[  374.023116] tm6000: alt 1, interface 0, class 255
[  374.023120] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes)
[  374.023125] tm6000: alt 1, interface 0, class 255
[  374.023129] tm6000: alt 1, interface 0, class 255
[  374.023133] tm6000: alt 2, interface 0, class 255
[  374.023137] tm6000: alt 2, interface 0, class 255
[  374.023141] tm6000: alt 2, interface 0, class 255
[  374.023145] tm6000: alt 3, interface 0, class 255
[  374.023149] tm6000: alt 3, interface 0, class 255
[  374.023153] tm6000: alt 3, interface 0, class 255
[  374.023158] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0)
[  374.023162] tm6000: Found Hauppauge HVR-900H
[  374.884058] Error -32 while retrieving board version
[  375.184050] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00
00 40 40 20 00 66  .YTE.......@@ .f
[  375.380112] 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.
[  375.572058] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff
ff ff ff ff ff ff  ..d.............
[  375.764038] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  375.956103] 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.
[  376.148062] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  376.344055] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff
0a 03 32 00 2e 00  0...........2...
[  376.536039] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ?...............
[  376.728041] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  376.920041] tm6000 #0: i2c eeprom 90: 35 ff ff ff 16 03 34 00 30 00
33 00 32 00 31 00  5.....4.0.3.2.1.
[  377.112039] tm6000 #0: i2c eeprom a0: 33 00 35 00 33 00 39 00 39 00
00 00 00 00 ff ff  3.5.3.9.9.......
[  377.308054] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  377.500046] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  377.692053] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  377.885037] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  378.076042] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  378.260374]   ................
[  378.260531] Trident TVMaster TM5600/TM6000 USB2 board (Load status: 0)
[  378.320709] Hack: enabling device at addr 0xc2
[  378.320722] tuner' 0-0061: chip found @ 0xc2 (tm6000 #0)
[  378.362555] xc2028 0-0061: creating new instance
[  378.362566] xc2028 0-0061: type set to XCeive xc2028/xc3028 tuner
[  378.362817] Setting firmware parameters for xc2028
[  378.362834] firmware: requesting xc3028L-v36.fw
[  378.395756] xc2028 0-0061: Loading 81 firmware images from
xc3028L-v36.fw, type: xc2028 firmware, ver 3.6
[  378.692036] xc2028 0-0061: Loading firmware for type=BASE MTS (5), id
0000000000000000.


The device itself does not show any affection (LEDs stay dark), there is
no directory /dev/dvb created and MeTV tells me it's not finding any
reciever.

What am I missing? Did I oversee anything conserning the
driver-compilation? Or am I using the wrong firmware?

Comments appreciated,
David

Using tm6010 for Haupauge WinTV-HVR 900H

[David Woitkowski]

[Reposted from linux-dvb because mailman told me linux-dvb is to be
replaced with linux-media. If you've already read this, just skip.]




Hi out there

I'm in the unfortunate position of having bought a 900H instead of a 900
and now I'm fiddling with the driver.

Details:
$ lsusb | grep Hauppauge
Bus 008 Device 004: ID 2040:6600 Hauppauge

My machine is running Ubuntu 8.10 with a 2.6.27-11-generic kernel. The
correct kernel-headers are installed.

As far as I've read there is (limited) support for the device with the
tm6010 driver. Putting together some info from the web I did the following:

$ hg clone http://linuxtv.org/hg/v4l-dvb
$ cd v4l-dvb
$ hg pull -u http://linuxtv.org/hg/~mchehab/tm6010

Inserted into v4l-dvb/v4l/.config three lines:
CONFIG_VIDEO_TM6000_ALSA=m
CONFIG_VIDEO_TM6000=m
CONFIG_VIDEO_TM6000_DVB=m

$ hg merge
$ make

and as root:
# make install

This far everything worked without error.

Then I got the Firmware the card was requesting in the dmesg-output from
http://steventoth.net/linux/hvr1400/xc3028L-v36.fw and copied it to /lib
/firmware

Since there is no Module tm6000 I did
# modprobe -v tm6000
insmod
/lib/modules/2.6.27-11-generic/kernel/drivers/media/video/videobuf-core.ko
insmod
/lib/modules/2.6.27-11-generic/kernel/drivers/media/video/videobuf-vmalloc.ko 



insmod /lib/modules/2.6.27-11-generic/kernel/drivers/i2c/i2c-core.ko
insmod
/lib/modules/2.6.27-11-generic/kernel/drivers/media/video/tm6000/tm6000.ko

$ dmesg
[  187.646908] tm6000 v4l2 driver version 0.0.1 loaded
[  187.647898] usbcore: registered new interface driver tm6000

(tail /var/log/messages gives the same info)

Now - as I hope the module is loaded correctly - I attacht the USB-Device:

$ dmesg
[  373.881042] usb 8-1: new high speed USB device using ehci_hcd and
address 3
[  374.019648] usb 8-1: configuration #1 chosen from 1 choice
[  374.023090] tm6000: alt 0, interface 0, class 255
[  374.023102] tm6000: alt 0, interface 0, class 255
[  374.023107] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes)
[  374.023111] tm6000: alt 0, interface 0, class 255
[  374.023116] tm6000: alt 1, interface 0, class 255
[  374.023120] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes)
[  374.023125] tm6000: alt 1, interface 0, class 255
[  374.023129] tm6000: alt 1, interface 0, class 255
[  374.023133] tm6000: alt 2, interface 0, class 255
[  374.023137] tm6000: alt 2, interface 0, class 255
[  374.023141] tm6000: alt 2, interface 0, class 255
[  374.023145] tm6000: alt 3, interface 0, class 255
[  374.023149] tm6000: alt 3, interface 0, class 255
[  374.023153] tm6000: alt 3, interface 0, class 255
[  374.023158] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0)
[  374.023162] tm6000: Found Hauppauge HVR-900H
[  374.884058] Error -32 while retrieving board version
[  375.184050] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00
00 40 40 20 00 66  .YTE.......@@ .f
[  375.380112] 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.
[  375.572058] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff
ff ff ff ff ff ff  ..d.............
[  375.764038] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  375.956103] 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.
[  376.148062] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  376.344055] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff
0a 03 32 00 2e 00  0...........2...
[  376.536039] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ?...............
[  376.728041] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  376.920041] tm6000 #0: i2c eeprom 90: 35 ff ff ff 16 03 34 00 30 00
33 00 32 00 31 00  5.....4.0.3.2.1.
[  377.112039] tm6000 #0: i2c eeprom a0: 33 00 35 00 33 00 39 00 39 00
00 00 00 00 ff ff  3.5.3.9.9.......
[  377.308054] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  377.500046] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  377.692053] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  377.885037] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  378.076042] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff  ................
[  378.260374]   ................
[  378.260531] Trident TVMaster TM5600/TM6000 USB2 board (Load status: 0)
[  378.320709] Hack: enabling device at addr 0xc2
[  378.320722] tuner' 0-0061: chip found @ 0xc2 (tm6000 #0)
[  378.362555] xc2028 0-0061: creating new instance
[  378.362566] xc2028 0-0061: type set to XCeive xc2028/xc3028 tuner
[  378.362817] Setting firmware parameters for xc2028
[  378.362834] firmware: requesting xc3028L-v36.fw
[  378.395756] xc2028 0-0061: Loading 81 firmware images from
xc3028L-v36.fw, type: xc2028 firmware, ver 3.6
[  378.692036] xc2028 0-0061: Loading firmware for type=BASE MTS (5), id
0000000000000000.


The device itself does not show any affection (LEDs stay dark), there is
no directory /dev/dvb created and MeTV tells me it's not finding any
reciever.

What am I missing? Did I oversee anything conserning the
driver-compilation? Or am I using the wrong firmware?

Comments appreciated,
David

Re: Using tm6010 for Haupauge WinTV-HVR 900H

[Helge Nert]

I'm also interested in the status of the tm6010 driver (and getting it 
to work).

 From googling the net I can see that we are quite a few people who are 
frustrated with Hauppauge's change to the 900H model and dealers 
unknowingly shipping the 900H model as if it was the 900 model which 
isn't available anymore.

Mauro: Is there any way that we can help in developing the driver?

I hope it doesn't require a Windows environment (which I haven't). In 
any case I'm willing to test the driver in different environments 
(64bit, 32bit, Intel (Atom), AMD and VIA processors).

Thanks,

- Helge

David Woitkowski wrote:
> [Reposted from linux-dvb because mailman told me linux-dvb is to be 
> replaced with linux-media. If you've already read this, just skip.]
>
>
>
>
> Hi out there
>
> I'm in the unfortunate position of having bought a 900H instead of a 900
> and now I'm fiddling with the driver.
>

Re: Using tm6010 for Haupauge WinTV-HVR 900H

[David Woitkowski]

Hi,

Helge Nert schrieb:
> I'm also interested in the status of the tm6010 driver (and getting it 
> to work).
> 
> Mauro: Is there any way that we can help in developing the driver?

I researched a bit more and discovered that the driver activates a
video-device at /dev/video1 (video0 is a webcam).

Now I tried a bit xawtv with this device:

$ xawtv -c /dev/video1
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.27-11-generic)
xinerama 0: 1280x800+0+0
Segmentation fault
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video1: Permission denied
v4l2: open /dev/video1: Permission denied
v4l: open /dev/video1: Permission denied
no video grabber device available

$ xawtv -c /dev/video1 -v 2
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.27-11-generic)
visual: id=0x21 class=4 (TrueColor), depth=24
visual: id=0x22 class=5 (DirectColor), depth=24
visual: id=0x54 class=4 (TrueColor), depth=32
x11: color depth: 24 bits, 3 bytes - pixmap: 4 bytes
x11: color masks: red=0x00ff0000 green=0x0000ff00 blue=0x000000ff
x11: server byte order: little endian
x11: client byte order: little endian
check if the X-Server is local ... * ok (unix socket)
main: dga extention...
DGA version 2.0
main: xinerama extention...
xinerama 0: 1280x800+0+0
main: xvideo extention [video]...
main: xvideo extention [image]...
blit: xv: 0x32595559 (YUY2) packed [ok: 16 bit YUV 4:2:2 (packed, YUYV)]
blit: xv: 0x32315659 (YV12) planar
blit: xv: 0x30323449 (I420) planar [ok: 12 bit YUV 4:2:0 (planar)]
blit: xv: 0x59565955 (UYVY) packed [ok: 16 bit YUV 4:2:2 (packed, UYVY)]
blit: xv: 0x434d5658 (XVMC) planar
main: init main window...
main: install signal handlers...
main thread [pid=10908]
main: open grabber device...
x11: 1280x800, 32 bit/pixel, 12800 byte/scanline, DGA
v4l-conf: using X11 display :0.0
dga: version 2.0
mode: 1280x800, depth=24, bpp=32, bpl=12800, base=0xd0300000
Segmentation fault
got sigchild
waitpid: No child processes
v4l-conf had some trouble, trying to continue anyway
vid-open: trying: v4l2-old...
v4l2: open /dev/video1: Permission denied
vid-open: failed: v4l2-old
vid-open: trying: v4l2...
v4l2: open /dev/video1: Permission denied
vid-open: failed: v4l2
vid-open: trying: v4l...
v4l: open /dev/video1: Permission denied
vid-open: failed: v4l
no video grabber device available

$ xawtv -hwscan
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.27-11-generic)
looking for available devices
port 66-81
     type : Xvideo, image scaler
     name : Intel(R) Textured Video

/dev/video0: OK                         [ -device /dev/video0 ]
     type : v4l2
     name : Lenovo EasyCamera
     flags:  capture

/dev/video1: Permission denied


And every time I try accessing /dev/video1 there is
$ dmesg
[12604.332127] BUG: unable to handle kernel NULL pointer dereference at
000000e8
[12604.332134] IP: [<f95ac39d>] :tm6000:tm6000_poll+0x1d/0xa0
[12604.332143] *pde = 00000000
[12604.332147] Oops: 0000 [#7] SMP
[12604.332151] Modules linked in: tuner_xc2028 tuner v4l2_common tm6000
i2c_core videobuf_vmalloc videobuf_core af_packet i915 drm binfmt_misc
rfcomm sco bridge stp bnep l2cap ipv6 vboxnetflt vboxdrv ppdev
acpi_cpufreq cpufreq_powersave cpufreq_userspace cpufreq_stats
cpufreq_ondemand cpufreq_conservative freq_table sbs pci_slot wmi sbshc
container iptable_filter ip_tables x_tables parport_pc lp parport loop
joydev serio_raw arc4 uvcvideo psmouse evdev ecb crypto_blkcipher
videodev usblp v4l1_compat iwlagn btusb iwlcore rfkill led_class
bluetooth snd_hda_intel mac80211 snd_pcm_oss snd_mixer_oss cfg80211
snd_pcm sdhci_pci sdhci mmc_core snd_seq_dummy snd_seq_oss battery
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq ac video output
snd_timer snd_seq_device snd button soundcore shpchp snd_page_alloc
pci_hotplug intel_agp agpgart ext3 jbd mbcache usbhid hid sr_mod cdrom
sd_mod crc_t10dif sg ahci libata tg3 libphy scsi_mod dock ehci_hcd
uhci_hcd usbcore thermal processor fan fbcon tileblit font bitblit
softcursor fuse
[12604.332255]
[12604.332258] Pid: 10913, comm: v4l-conf Tainted: G      D
(2.6.27-11-generic #1)
[12604.332260] EIP: 0060:[<f95ac39d>] EFLAGS: 00210246 CPU: 1
[12604.332265] EIP is at tm6000_poll+0x1d/0xa0 [tm6000]
[12604.332268] EAX: edd26900 EBX: 00000000 ECX: f8e63930 EDX: f95b1000
[12604.332270] ESI: edd26900 EDI: f95b1000 EBP: eb4b5e44 ESP: eb4b5e38
[12604.332272]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[12604.332275] Process v4l-conf (pid: 10913, ti=eb4b4000 task=eb5b8c90
task.ti=eb4b4000)
[12604.332277] Stack: f59ab200 edd26900 f59ab204 eb4b5e58 f8e639b3
00000000 eccf5780 00000000
[12604.332286]        eb4b5e80 c01b5035 edd26900 edf5dc60 eb4b5e70
c05ac8a0 eb4b5e80 edd26900
[12604.332294]        00000000 edf5dc60 eb4b5e9c c01b049c f6b29a00
e8cd7b28 edd26900 eb4b5f04
[12604.332301] Call Trace:
[12604.332305]  [<f8e639b3>] ? v4l2_open+0x83/0xa0 [videodev]
[12604.332312]  [<c01b5035>] ? chrdev_open+0xd5/0x1b0
[12604.332320]  [<c01b049c>] ? __dentry_open+0xbc/0x260
[12604.332324]  [<c01b0717>] ? nameidata_to_filp+0x47/0x60
[12604.332329]  [<c01b4f60>] ? chrdev_open+0x0/0x1b0
[12604.332333]  [<c01bddbd>] ? do_filp_open+0x1bd/0x790
[12604.332337]  [<c02a904f>] ? pty_write+0x3f/0x60
[12604.332343]  [<c01e244e>] ? inotify_inode_queue_event+0xe/0xe0
[12604.332348]  [<c02a8bda>] ? tty_ldisc_deref+0x5a/0x80
[12604.332352]  [<c01c98f9>] ? expand_files+0x9/0x60
[12604.332356]  [<c01c9a30>] ? alloc_fd+0xe0/0x100
[12604.332360]  [<c01b0295>] ? do_sys_open+0x65/0x100
[12604.332364]  [<c01b039e>] ? sys_open+0x2e/0x40
[12604.332367]  [<c0103f7b>] ? sysenter_do_call+0x12/0x2f
[12604.332372]  [<c0370000>] ? enable_nonboot_cpus+0x60/0xc0
[12604.332377]  =======================
[12604.332379] Code: ff 5d c3 8d 74 26 00 8d bc 27 00 00 00 00 55 89 e5
83 ec 0c 89 1c 24 89 74 24 04 89 7c 24 08 e8 0a 8f b5 c6 8b 58 70 89 c6
89 d7 <83> bb e8 00 00 00 01 74 1a b8 08 00 00 00 8b 1c 24 8b 74 24 04
[12604.332422] EIP: [<f95ac39d>] tm6000_poll+0x1d/0xa0 [tm6000] SS:ESP
0068:eb4b5e38
[12604.332430] ---[ end trace 2c9a251a17248d49 ]---


And just to cover the "Permission dienied"s. Doing these steps as
superuser gives the same results. The permissions are set as follows:
$ ls -l /dev/video*
crw-rw----+ 1 root video 81, 0 2009-03-02 13:45 /dev/video0
crw-rw----  1 root video 81, 1 2009-03-02 17:01 /dev/video1



> I hope it doesn't require a Windows environment (which I haven't). In
> any case I'm willing to test the driver in different environments
> (64bit, 32bit, Intel (Atom), AMD and VIA processors).

Speaking about Windows: I tried the device inside VirtualBox-PUEL 2.1.4.
The device is recognised correctly, can scan for channels and play
sound. The guys at forums.virtualbox.org told me the USB-support is
probably too slow to handle the video.
Full thread at http://forums.virtualbox.org/viewtopic.php?p=62194#62194

Buy,
David