Do you have lm_sensors installed? A kernel module named "eeprom" may have been loaded before tveeprom was.
I had this issue after installing/enabling lm_sensors. You can check if lm_sensors is running: $ chkconfig --list lm_sensors If so, $ chkconfig lm_sensors off Regards, Quentin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Williams Sent: Tuesday, January 25, 2005 5:25 AM To: [email protected] Subject: Re: [ivtv-devel] Error -19 reading Hauppauge eeprom On Tue, 25 Jan 2005 01:40:17 -0500, Daniel Milani <[EMAIL PROTECTED]> wrote: > Running FC3 with a Hauppauge 250 > > I have a type 50 tuner. All I am getting is static. I am trying to > figure out my next steps. I think I need to upgrade modutils or > something but I couldn't find the details in the archives. > > My /var/log/message tells me repeatly that my tuner is not set > > It looks like this: > > localhost kernel: ivtv: ==================== START INIT IVTV > ==================== localhost kernel: ivtv: version 0.1.10 > (0.1.10-49_pre2_ck100zz.rhfc3.at) loading > localhost kernel: ivtv: Linux version: 2.6.10-1.741_FC3 586 REGPARM > 4KSTACKS gcc-3.4 > localhost kernel: ivtv: In case of problems please include the debug > info > localhost kernel: ivtv: between the START INIT IVTV and END INIT IVTV > lines when > localhost kernel: ivtv: mailing the ivtv-devel mailinglist. > localhost kernel: ivtv: Autodetected WinTV PVR 250 card > localhost kernel: ivtv: Found an iTVC16 based chip > localhost kernel: PCI: Found IRQ 11 for device 0000:00:0b.0 > localhost kernel: PCI: Sharing IRQ 11 with 0000:00:07.2 > localhost kernel: PCI: Sharing IRQ 11 with 0000:00:07.3 > localhost kernel: ivtv: pci: VIA detected device: 0x0501 vendor: 0x1106 > localhost kernel: ivtv: i2c client addr: 0x50 not found! > localhost kernel: ivtv: Error -19 reading Hauppauge eeprom. > localhost kernel: ivtv: Possible causes: the tveeprom module was not > loaded, or > localhost hald[3615]: Timed out waiting for hotplug event 595. > Rebasing to 605 > localhost kernel: ivtv: the eeprom kernel module was loaded before the > tveeprom module. > localhost kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c > driver #0 > localhost kernel: ivtv: i2c attach [client=(tuner unset),ok] > localhost kernel: saa7115: Ignoring new-style parameters in presence > of obsolete ones > localhost kernel: saa7115: starting probe for adapter ivtv i2c driver > #0 (0x10005) > localhost kernel: saa7115: detecting saa7115 client on address 0x42 > localhost kernel: saa7115: writing init values > localhost kernel: ivtv: i2c attach [client=saa7115[0],ok] > localhost kernel: saa7115: status: (1E) 0x48, (1F) 0xc0 > localhost kernel: msp34xx: init: chip=MSP3445G-B8 +nicam +simple > +simpler +radio mode=simple > localhost kernel: msp3410: daemon started > localhost kernel: ivtv: i2c attach [client=MSP3445G-B8,ok] localhost > kernel: ivtv: Encoder revision: 0x02040024 localhost kernel: ivtv: > Configuring WinTV PVR 250 card with 4 streams localhost kernel: ivtv: > Create DMA stream 0 using 128 buffers of size 32768 > localhost kernel: ivtv: Create DMA stream 1 using 128 buffers of size > 32768 > localhost kernel: ivtv: Create stream 2 using 128 buffers of size 52224 > localhost kernel: ivtv: Create DMA stream 3 using 128 buffers of size > 32768 > localhost kernel: ivtv: Could not detect tuner standard, defaulting to > NTSC. > localhost kernel: ivtv: Setting audio matrix to input 3, output 1 > localhost kernel: ivtv: Switching standard to NTSC. > localhost kernel: tuner: tuner type not set > localhost kernel: saa7115: decoder set norm NTSC > localhost kernel: saa7115: set audio: 0x01 > localhost kernel: ivtv: Initialized WinTV PVR 250, card #0 > localhost kernel: ivtv: ==================== END INIT IVTV > ==================== > I had the same problem yesterday. I finally fixed it by adding a line to modules.conf just under all the other load ivtv stuff that says alias tveeprom tveeprom-ivtv Don't ask why because I don't understand it. Something to do with the tveeprom being named incorrectly or something maybe. Give it a shot a let us know. Igot my answer from a post on this list about the PVR-350 a few days ago. So if that line doesn't work read further back in the list. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
