On Wed, 2008-09-17 at 22:13 -0400, Oystein Thorsen wrote: > Hi, > I bought the HVR-1600 card about a week ago, but I've been unable to get > it working on my mythtv server. I've tried it on a different computer > where it worked in Vista. It also worked on Fedora 9 (same as the mythtv > server) with the same drivers as on the mythtv server. I also have a > PVR-150 card in the mythtv server from before. The PVR-150 been working > the whole time while I've been playing around with the HVR-1600. > > I'm using the latest v4l-dvb drivers (from the official mercurial > repository). > > Initially I had problems detecting the card, but it looks like the > mmio_ndelay setting (152) corrected that:
All, I'm trying to figure out a good value for the driver to use as a default for this parameter, so I can stop repeating the mmio_ndelay answer on the list :) . I'm sure users expect the driver to "just work" out of the box and I'd certainly like to make it that way. So far various people have reported that 91, 121, and 152 fix their respective problems. So that means I'll need to check in a value of 152 as a default. Has anyone else found they need to use a even higher value for correct operation? > cx18-0: Initializing card #0 > cx18-0: Autodetected Hauppauge card > ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 21 (level, low) -> IRQ 21 > cx18-0: cx23418 revision 01010000 (B) > tveeprom 4-0050: Hauppauge model 74541, rev C6B6, serial# 3484150 > tveeprom 4-0050: MAC address is 00-0D-FE-35-29-F6 > tveeprom 4-0050: tuner model is Philips FM1236 MK5 (idx 116, type 43) > tveeprom 4-0050: TV standards NTSC(M) (eeprom 0x08) > tveeprom 4-0050: audio processor is CX23418 (idx 38) > tveeprom 4-0050: decoder processor is CX23418 (idx 31) > tveeprom 4-0050: has radio > cx18-0: Autodetected Hauppauge HVR-1600 > cx18-0: VBI is not yet supported > tuner 5-0043: chip found @ 0x86 (cx18 i2c driver #0-1) > tda9887 5-0043: creating new instance > tda9887 5-0043: tda988[5/6/7] found > tuner 5-0061: chip found @ 0xc2 (cx18 i2c driver #0-1) > cs5345 4-004c: chip found @ 0x98 (cx18 i2c driver #0-0) > tuner-simple 5-0061: creating new instance > tuner-simple 5-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or > FM1236/F)) > cx18-0: Disabled encoder IDX device > cx18-0: Registered device video0 for encoder MPEG (2 MB) > DVB: registering new adapter (cx18) > firmware: requesting v4l-cx23418-apu.fw > MXL5005S: Attached at address 0x63 > DVB: registering frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)... > cx18-0: DVB Frontend registered > cx18-0: Registered device video32 for encoder YUV (2 MB) > cx18-0: Registered device video24 for encoder PCM audio (1 MB) > cx18-0: Registered device radio0 for encoder radio > cx18-0: Initialized card #0: Hauppauge HVR-1600 > cx18: End initialization > cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes) > firmware: requesting v4l-cx23418-cpu.fw > cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes) > cx18-0: FW version: 0.0.74.0 (Release 2007/03/12) > firmware: requesting v4l-cx23418-apu.fw > firmware: requesting v4l-cx23418-cpu.fw > firmware: requesting v4l-cx23418-dig.fw > cx18-0: loaded v4l-cx23418-dig.fw firmware (16382 bytes) > > When I try to capture some data (cat /dev/video0 > test.mpg) I get > nothing (filesize is 0). The same happens if I try to record something > on mythtv (The PVR-150 still records fine). > > Let me know if there is any other information that would be useful. Look in /proc/interrupts and see what devices are sharing IRQ lines with ivtv and cx18, and look in dmesg or /var/log/messages for any messages about the kernel disabling/ignoring IRQ lines (i.e. "nobody cared"). Use the cx18 debug module parameter to turn on Warning, Info, Mailbox/API, and IRQ debug messages. See what gets logged especially when you try to do a capture. If nothing jumps out at you, also turn on the high volume debug flag. Regards, Andy > Thanks, > > Oystein Thorsen _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
