Here you go. Thanks for looking into this. ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.8.1 (tagged release) loading ivtv: Linux version: 2.6.18-gentoo-r3 mod_unload 586 gcc-4.1 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected Hauppauge card (cx23416 based) ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 17 (level, low) -> IRQ 21 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) Zapata Telephony Interface Registered on major 196 Zaptel Version: 1.2.9.1 Echo Canceller: KB1 ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 16 (level, low) -> IRQ 22 Failed to initailize DAA, giving up... wcfxo: probe of 0000:00:08.0 failed with error -5 nvidia: module license 'NVIDIA' taints kernel. Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0) tuner 0-0060: TEA5767 detected. tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0) tuner 0-0060: type set to 62 (Philips TEA5767HN FM Radio) tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) usbcore: registered new driver hiddev hiddev96: USB HID v1.10 Device [APC Back-UPS ES 500 FW:801.e6.D USB FW:e6] on usb-0000:00:10.1-2 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes) tveeprom 0-0050: Hauppauge model 23552, rev D587, serial# 8857532 tveeprom 0-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70) tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 0-0050: audio processor is CX25843 (idx 37) tveeprom 0-0050: decoder processor is CX25843 (idx 30) tveeprom 0-0050: has radio, has no IR remote ivtv0: Autodetected WinTV PVR 500 (unit #1) ivtv0: Encoder revision: 0x02050032 ivtv0: Registered device video0 for encoder MPEG ivtv0: Registered device video32 for encoder YUV ivtv0: Registered device vbi0 for encoder VBI ivtv0: Registered device video24 for encoder PCM audio ivtv0: Registered device radio0 for encoder radio tuner 0-0061: type set to 70 (Samsung TCPN 2121P30A) ivtv0: Initialized WinTV PVR 500 (unit #1), card #0 ivtv: ====================== NEXT CARD ====================== ivtv1: Autodetected Hauppauge card (cx23416 based) ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 18 (level, low) -> IRQ 17 ivtv1: Unreasonably low latency timer, setting to 64 (was 32) ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1) tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1) cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1) cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes) tveeprom 1-0050: Hauppauge model 23552, rev D587, serial# 8857532 tveeprom 1-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70) tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 1-0050: audio processor is CX25843 (idx 37) tveeprom 1-0050: decoder processor is CX25843 (idx 30) tveeprom 1-0050: has radio, has no IR remote ivtv1: Correcting tveeprom data: no radio present on second unit ivtv1: Autodetected WinTV PVR 500 (unit #2) ivtv1: Encoder revision: 0x02050032 ivtv1: Registered device video1 for encoder MPEG ivtv1: Registered device video33 for encoder YUV ivtv1: Registered device vbi1 for encoder VBI ivtv1: Registered device video25 for encoder PCM audio tuner 1-0061: type set to 70 (Samsung TCPN 2121P30A) ivtv1: Initialized WinTV PVR 500 (unit #2), card #1 ivtv: ==================== END INIT IVTV ====================
- Haavar On Dec 2, 2006, at 2:38 PM, Hans Verkuil wrote: > Please post the INIT IVTV messages your kernel log. There can be > various > reasons for this but I need that info first. > > Hans > > On Saturday 02 December 2006 23:30, Haavar Valeur wrote: >> I got a PVR-500, and I'm having some problems with the picture >> quality. I think my signal is pretty strong from the cable provider. >> When I turn off the internal amplifier on the card (in the kernel), I >> get a snowy picture on some channels and a pretty good on others. >> When I leave the amp on, I get distortion lines on some channels >> others are fine. It seems to me the problem could be solved here, but >> there is a lot of tuning and recompiling the kernel to be done. >> >> Are you sure that some cards are more sensitive than others, and >> it's not that peoples cable signal is different? If there is a chance >> I could get a better card, I could return this and get another one. >> >> I'm getting the best PQ on most channels by padding the cable with a >> 3 way slitter and leaving the internal amp on (as it is in the 2.6.18 >> kernel). I padded my signal by connecting my cable from the wall into >> the output of a 3 way splitter and connected my computer to another >> output (nothing on the input). I've ordered actual signal pads >> (attenuators) and a ground breaker to see if this helps. >> >> Does anyone have a tip how to get a better PQ with this card? >> Is there any tuning that can be done via the driver to improve the >> signal? Like turning on or off the amp. >> >> - Haavar >> >> On Nov 28, 2006, at 5:28 AM, John Drescher wrote: >>> I currently have a PVR-150 with ivtv-0.8.1 and kernel-2.6.18 and >>> I'm happy with the quality of the picture. I'm thinking about >>> returning the PVR-150 and getting a PVR-500 instead of getting a >>> second PVR-150 to save a PCI slot. Is the difference in quality >>> between the cards still noticeable? >>> >>> If you are unlucky and buy a card that does not like a strong >>> signal the answer is yes. There is no >>> quality difference in patched kernels. The main difference is the >>> patch is in 2.6.18 kernels so you >>> automatically get it with ivtv-0.8.X and not applied in lower >>> versions of the kernel. >> >> _______________________________________________ >> ivtv-users mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-users > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
