Myth setup can't find PVR-350

[snowrodeo]

I have a 350 that used to work with 2.2 until 1/24/2010. Now when I attempt to add this device (/dev/video0) as a IVTV capture card the setup program "can't open /dev/video0 to probe..."

I can successfully cat /dev/video0 > some_file.mpg and get a nice clear stream so I know the card is working. IVTV seems to be working as well. Here is the info from dmesg

[ 19.764660] ivtv0: Initializing card 0
[ 19.764665] ivtv0: Autodetected Hauppauge card (cx23415 based)
[ 19.764716] ivtv 0000:06:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 19.764726] ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
[ 19.781273] lp0: using parport0 (interrupt-driven).
[ 19.821476] tveeprom 1-0050: Hauppauge model 48132, rev J323, serial# 7112718
[ 19.821480] tveeprom 1-0050: tuner model is Philips FM1236 (idx 23, type 2)
[ 19.821483] tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x0
[ 19.821486] tveeprom 1-0050: audio processor is MSP4448 (idx 27)
[ 19.821488] tveeprom 1-0050: decoder processor is SAA7115 (idx 19)
[ 19.821490] tveeprom 1-0050: has radio, has IR receiver, has no IR transmitter
[ 19.821494] ivtv0: Autodetected Hauppauge WinTV PVR-350
[ 19.832316] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 19.832369] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 19.889675] saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
[ 20.021447] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
[ 20.030245] saa7127 1-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)
[ 20.074737] msp3400 1-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
[ 20.074740] msp3400 1-0040: msp3400 supports radio, mode is autodetect and autoselect
[ 20.085746] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 20.245990] tuner-simple 1-0061: creating new instance
[ 20.245993] tuner-simple 1-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
[ 20.258549] IRQ 21/ivtv0: IRQF_DISABLED is not guaranteed on shared IRQs
[ 20.265052] ivtv0: Registered device video0 for encoder MPG (4096 kB)
[ 20.265080] ivtv0: Registered device video32 for encoder YUV (2048 kB)
[ 20.265104] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
[ 20.265131] ivtv0: Registered device video24 for encoder PCM (320 kB)
[ 20.265155] ivtv0: Registered device radio0 for encoder radio
[ 20.265178] ivtv0: Registered device video16 for decoder MPG (1024 kB)
[ 20.265200] ivtv0: Registered device vbi8 for decoder VBI (64 kB)
[ 20.265225] ivtv0: Registered device vbi16 for decoder VOUT
[ 20.265246] ivtv0: Registered device video48 for decoder YUV (1024 kB)
[ 20.265248] ivtv0: Initialized card: Hauppauge WinTV PVR-350
[ 20.265299] ivtv: End initialization

I am running ubuntu server 9.10. Any ideas on how to start debugging this?

-Snowrodeo

[fromans4]

You might try setting the card up as a V4L device instead of IVTV. I know in my case I use a PVR-500 card and it changed from IVTV to V4L a while ago.

[wagnerrp]

Originally Posted by fromans4

I know in my case I use a PVR-500 card and it changed from IVTV to V4L a while ago.

That doesn't make any sense. The only reason such a card would fail to function as an IVTV card, and start operating as a V4L card would be if the encoder chip failed. Even then, you would have to use video24 to hit the framegrabber directly, rather than the encoder on video0. If he can 'cat' the node to a valid mpeg file, that's obviously not the case here anyway.

Is it possible the user you're running MythTV as does not have file permissions to access that node? Also, '2.2' of what program are you referring to?