[SOLVED] Hauppauge WinTV-PVR 150 MCE setup for MythTV - Debian

[trilarian]

I'm venturing out into my first MythTV setup now that my server has more storage capacity and I've maxed transfer speeds(anyone reading my previous post will see the progression). Anyway, I have followed a few HowTo's but can't seem to get access to the card itself. Everything appears to be loaded correctly, but I can not access the card. Giving examples may be the best way to communicate what I mean here...

Kernel can see the card:
Debian-Server:/home/trilarian# dmesg | grep Initialized
ivtv0: Initialized card #0: Hauppauge WinTV PVR-150


Modules appear to be loaded(removed the obviously irrelevant output):
Debian-Server:/home/trilarian# lsmod
Module Size Used by
wm8775 11020 0
cx25840 30608 0
tuner 48032 0
tea5767 10500 1 tuner
tda8290 16388 1 tuner
tuner_simple 12680 1 tuner
mt20xx 16776 1 tuner
tea5761 9732 1 tuner
ivtv 140096 0
firmware_class 15232 2 cx25840,ivtv
i2c_algo_bit 11012 1 ivtv
cx2341x 16644 1 ivtv
tveeprom 22288 1 ivtv
videodev 32256 1 ivtv
v4l2_common 24320 6 wm8775,cx25840,tuner,ivtv,cx2341x,videodev
v4l1_compat 16388 2 ivtv,videodev
wm8775,cx25840,tuner,tea5767,tda8290,tuner_simple, mt20xx,tea5761,ivtv,i2c_algo_bit,tveeprom,i2c_piix 4


/dev/video0 exist, but does not seem to have anything pointing to it(maybe this is the source of the problem?):
Debian-Server:/home/trilarian# ll /dev/video?
crw-rw---- 1 root video 81, 0 2008-02-10 23:25 /dev/video0


If the card is setup properly, I should get output from this...
Debian-Server:/home/trilarian# v4l2-ctl -n
Failed to open /dev/video0: No such device or address


Any advice is appreciated. Also, will mention I have done depmod -a then modprobe ivtv to no changes.

[trilarian]

Meh, ignore me...

Solved it, though I found the solution odd as it reminds me of winblows. I copied over the firmware binaries to /lib/firmware during the install process, but apparently you have to actually reboot your machine to pick up these new firmware options. At least, that was suggested elsewhere and I tried it. Now I get output like this:

Debian-Server:/home/trilarian# v4l2-ctl -n
ioctl: VIDIOC_ENUMINPUT
Input : 0
Name : Tuner 1
Type : 0x00000001
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000001000 ( NTSC )
Status : 0

Input : 1
Name : S-Video 1
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

Input : 2
Name : Composite 1
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

Input : 3
Name : S-Video 2
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0

Input : 4
Name : Composite 2
Type : 0x00000002
Audioset: 0x00000007
Tuner : 0x00000000
Standard: 0x0000000000FFFFFF ( PAL NTSC SECAM )
Status : 0


So, moving on along... At work now, but I'll post back results or problems as they go.

[bwkaz]

I copied over the firmware binaries to /lib/firmware during the install process, but apparently you have to actually reboot your machine to pick up these new firmware options. Nah, you can just run udevtrigger (you'll have to be root) to have the driver request the firmware again. :)

(The reason it didn't do any good is that -- I suspect anyway -- the driver loaded once, before the firmware was present. Now that the firmware is present, you need to make the driver ask again. Although I suppose it's possible that udevtrigger alone may not be enough to do that; if not, you can try to modprobe -r ivtv and rerun udevtrigger. Not that it matters much anymore, but for others in the future... :))

[trilarian]

Nah, you can just run udevtrigger (you'll have to be root) to have the driver request the firmware again. :)

Thanks, I'll try and make a mental note of that. I'm almost inclined to make an account to post on that forum where I got the solution to reboot. That is the first time in my many years of Linux that a program actually required(well, at least was told to me to require) a reboot that does not involve the kernel.

At any rate, I've got MythTV working perfectly! Once I get some more time I'll play with the transcoding. Apparently it has an UPnP function, so I'm hoping I can tweak it to work with my PS3... then I'd be in heaven(and it didn't cost a Tivo to get there!).

Here is a screen of me looking at what to record from work.:cool:

3438