Hauppauge WinTV-HVR-1110

From LinuxMCE
Jump to: navigation, search
Version Status Date Updated Updated By
710 Unknown N/A N/A
810 Unknown N/A N/A
1004 Unknown N/A N/A
1204 Unknown N/A N/A
Usage Information

Installation

Plug the card in an available PCI slot, and connect the antenna cable.

Kernel Configuration

This only needs to be done once (but it doesn't hurt to do more times):

  1. create a config file to tell the kernel driver which card it actually is
  2. remove any existing instances of saa7134_dvb from the modules list
  3. add saa7134_dvb (again) to the list of modules to start at boot-time
  4. restart the system

In other words:

sudo echo 'options saa7134 card=104' >/etc/modprobe.d/saa7134
sudo sed -e '/^[^#]*saa7134_dvb/d' -i /etc/modules
sudo echo 'saa7134_dvb' >>/etc/modules
sudo reboot

Now the card should be properly recognized (sample from dmesg):

saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 20 (level, low) -> IRQ 22
saa7133[0]: found at 0000:03:05.0, rev: 209, irq: 22, latency: 64, mmio: 0xfdeff000
saa7133[0]: subsystem: 0070:6700, board: Hauppauge WinTV-HVR1110 DVB-T/Hybrid [card=104,insmod option]
saa7133[0]: board init: gpio is 400000
saa7133[0]: i2c eeprom 00: 70 00 00 67 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: ff ff ff 08 ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 32 32 01 01 33 88 ff 00 a3 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 15 60 ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
saa7133[0]: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
saa7133[0]: i2c eeprom 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tuner 0-004b: setting tuner address to 61
tuner 0-004b: type set to tda8290+75a
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
saa7134 ALSA driver for DMA sound loaded
saa7133[0]/alsa: saa7133[0] at 0xfdeff000 irq 22 registered as card -2
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)...

The devices are in place as well:

ls -l /dev/dvb/adapter0/
crw-rw---- 1 root video 212, 4 2007-08-06 06:52 demux0
crw-rw---- 1 root video 212, 5 2007-08-06 06:52 dvr0
crw-rw---- 1 root video 212, 3 2007-08-06 06:52 frontend0
crw-rw---- 1 root video 212, 7 2007-08-06 06:52 net0


MythTV Configuration

Now it can be configured with the MythTV setup option from the Computing screen in LinuxMCE.

  • Card type: DVB DTV capture card (v3.x)

See also



And that's about as far as I got. Unfortunately I don't see any channels (they're all black) and having never received DVB-T before I'm not even sure if I can get a signal. Maybe I just need a better antenna but MythTV doesn't seem entirely stable either.

To be continued... -- Zaerc 00:00, 6 August 2007 (MST)


Both my hunches seem right, as it turns out the instability is MythTV not agreeing with the graphics chipset drivers of my mainboard. Starting TV on another Media Director informs me that:

You should have gotten a channel lock
by now. You can continue to wait for
a signal, or you can change the
channels with Up and Down, change 
input's (C), capture cards (Y), etc.

(in large and friendly letters). Up and Down do indeed change the channels and I see the program information on what should be playing. So I guess the last hurdle is to get a signal and lock onto a channel...

Stay tuned... -- Zaerc 15:10, 6 August 2007 (MST)


After some extensive messing around I have improved the instructions a bit, the firmware part turned out not to be necessary, and a kernel-module needed for dvb is now added to /etc/modules. Once I figure out how to configure MythTV (properly) I'll describe that too. And then to think that I don't even like watching TV, oh well it comes with the package. ;^)

-- Zaerc 05:36, 25 August 2007 (MST)