I had the same problem until I forced the card type. Here's part of my modprobe.conf. Just add the last line to yours.
alias char-major-81 videodev alias char-major-81-0 ivtv alias tveeprom tveeprom-ivtv alias msp3400 msp3400-ivtv options ivtv cardtype=2 On Apr 10, 2005 11:57 AM, Charles Waddell <[EMAIL PROTECTED]> wrote: > Today I tried upgrading to the 0.3.2 version of ivtv but I get the same > messages. > > rpm -qa ivtv > ivtv-0.3.2q-78.rhfc3.at > > The tveeprom does not recognise the card as a PVR-250 thinks it is an > "Unknown Card" even though I had been going strong on the 0.1.10 version for > 6+ months. Here is dmesg with the new driver: > > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.3.2 (q) loading > ivtv: Linux version: 2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4 > ivtv: In case of problems please include the debug info > ivtv: between the START INIT IVTV and END INIT IVTV lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv: Unknown card: vendor/device: 4444/0016, subsystem vendor/device: > 0070/0009 > ivtv: Defaulting to WinTV PVR 150 card > ivtv: Please mail the vendor/device and subsystem vendor/device IDs and what > kind of > ivtv: card you have to the ivtv-devel mailinglist: > http://sourceforge.net/projects/ivtv > ivtv: Prefix your subject line with [UNKNOWN CARD]. > ivtv: Found an iTVC16 based chip > ACPI: PCI interrupt 0000:05:04.0[A] -> GSI 5 (level, low) -> IRQ 5 > ivtv: XXX PCI device: 0x2560 vendor: 0x8086 > tveeprom: Hauppauge: model = 32032, rev = B326, serial# = 7193410 > tveeprom: tuner = Temic 4036FY5 (idx = 26, type = 8) > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) > tveeprom: audio_processor = MSP3440 (type = 11) > ivtv: i2c attach [client=tveeprom[0],ok] > ivtv: Tuner Type 8, Tuner formats 0x00001000, Radio: yes, Model 0x00893496, > Revision 0x00000000 > ivtv: NTSC tuner detected > ivtv: Radio detected > ivtv: i2c attach [client=(tuner unset),ok] > tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) > ivtv: Encoder revision: 0x02040024 > ivtv: Encoder Firmware may be buggy, use version 0x02040011 > ivtv: Configuring WinTV PVR 150 card with 5 streams > ivtv: Registered v4l2 device, streamtype 0 minor 0 > ivtv: Create DMA stream 0 using 1024 16384 byte buffers 0 kbytes total > ivtv: Allocate DMA stream 0 using 1024 16384 byte buffers 16777216 kbytes > total > ivtv: Registered v4l2 device, streamtype 1 minor 32 > ivtv: Create DMA stream 1 > ivtv: Allocate DMA stream 1 > ivtv: Registered v4l2 device, streamtype 2 minor 224 > ivtv: Create stream 2 using 40 52224 byte buffers 0 kbytes total > ivtv: Allocate stream 2 using 40 52224 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 3 minor 24 > ivtv: Create DMA stream 3 using 455 4608 byte buffers 0 kbytes total > ivtv: Allocate DMA stream 3 using 455 4608 byte buffers 2097152 kbytes > total > ivtv: Registered v4l2 device, streamtype 4 minor 64 > ivtv: Create stream 4 > ivtv: Allocate stream 4 > ivtv: Setting Tuner 8 > tuner 0-0061: type set to 8 (Temic NTSC (4036 FY5)) > ivtv: i2c client addr: 0x44 not found! > ivtv: Switching standard to NTSC. > ivtv: i2c client addr: 0x44 not found! > ivtv: Initialized WinTV PVR 150, card #0 > ivtv: ==================== END INIT IVTV ==================== > > here is what I get if I try to access the video device: > > ivtv: i2c client addr: 0x44 not found! > ivtv: i2c client addr: 0x44 not found! > ivtv: i2c client addr: 0x44 not found! > ivtv: i2c client addr: 0x44 not found! > > ----Original Message Follows---- > From: "Charles Waddell" > RE: [ivtv-devel] [UNKNOWN CARD] after upgrade to 0.2.0 > > Reading back through past entries to the ivtv-devel list, I found 2 other > people with the same problem. i.e. formerly identified PVR-250's that after > the update found that their cards were no longer being recognised, they both > had different types. Mine is recognised as a tuner type=8 which is correct, > but it says that it is "unknown". I would like to add that I added: > > alias tveeprom tveeprom-ivtv > > to my modprobe.conf thinking that the ivtv version would be able to > correctly identify the card, but it was to no avail. Any help is greatly > appreciated. > > Thanks again, > C Daniel > > ----Original Message Follows---- > From: "Charles Waddell" > Subject: [ivtv-devel] [UNKNOWN CARD] after upgrade to 0.2.0 > > Everything has been fine with ivtv for the last 6 months or so until I > updated to the newer version of ivtv. (Recommended by Jarod). > > # rpm -qa ivtv > ivtv-0.2.0-66_rc3i.rhfc3.at > > now I get an unknown card type. My card is a PVR-250 although ivtv defaults > to a PVR-150. Here is dmesg between the IVTV sections: > > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.2.0 (rc3i) loading > ivtv: Linux version: 2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4 > ivtv: In case of problems please include the debug info > ivtv: between the START INIT IVTV and END INIT IVTV lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv: Unknown card: vendor/device: 4444/0016, subsystem vendor/device: > 0070/0009 > ivtv: Defaulting to WinTV PVR 150 card > ivtv: Please mail the vendor/device and subsystem vendor/device IDs and what > kind of > ivtv: card you have to the ivtv-devel mailinglist: > http://sourceforge.net/projects/ivtv > ivtv: Prefix your subject line with [UNKNOWN CARD]. > ivtv: Found an iTVC16 based chip > ACPI: PCI interrupt 0000:05:04.0[A] -> GSI 5 (level, low) -> IRQ 5 > ivtv: XXX PCI device: 0x2560 vendor: 0x8086 > ivtv: i2c attach [client=tveeprom,ok] > ivtv: i2c attach [client=(tuner unset),ok] > tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) > tveeprom: Hauppauge: model = 32032, rev = B326, serial# = 7193410 > tveeprom: tuner = Temic 4036FY5 (idx = 26, type = 8) > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) > tveeprom: audio_processor = MSP3440 (type = 11) > ivtv: Tuner Type 8, Tuner formats 0x00001000, Radio: yes, Model 0x00893496, > Revision 0xd0b1cf04 > ivtv: NTSC tuner detected > ivtv: Radio detected > ivtv: Encoder revision: 0x02040024 > ivtv: Encoder Firmware may be buggy, use version 0x02040011 > ivtv: Configuring WinTV PVR 150 card with 5 streams > ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total > ivtv: Registered v4l2 device, streamtype 0 minor 0 > ivtv: Create DMA stream 1 > ivtv: Registered v4l2 device, streamtype 1 minor 32 > ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 2 minor 224 > ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 3 minor 24 > ivtv: Create stream 4 > ivtv: Registered v4l2 device, streamtype 4 minor 64 > ivtv: Setting Tuner 8 > tuner 0-0061: type set to 8 (Temic NTSC (4036 FY5)) > ivtv: i2c client addr: 0x44 not found! > ivtv: Switching standard to NTSC. > ivtv: i2c client addr: 0x44 not found! > ivtv: Initialized WinTV PVR 150, card #0 > ivtv: ==================== END INIT IVTV ==================== > > The video devices are there but if I try to access them I get the following > from dmesg: > > ivtv: i2c client addr: 0x44 not found! > ivtv: i2c client addr: 0x44 not found! > ivtv: i2c client addr: 0x44 not found! > ivtv: ENC: User stopped capture. > > Should I roll back to a previous version? or does anyone have any > suggestions. > > Thanks in advance, > C Daniel Waddell > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
