I had a similar issue with my PVR 250 after issuing an errant ivtvctl command. The PVR 350 installed in the same computer worked fine and nothing else had changed. I believe I tried switching to a non-existant input on the PVR 250 using ivtvctl and that may have caused my problem. Afterwards, I got
ivtv: Error -19 reading Hauppauge eeprom. ivtv: Possible causes: the tveeprom module was not loaded, or ivtv: the eeprom kernel module was loaded before the tveeprom module. when trying to initialize the PVR 250. I tried cold-booting and unplugging the computer from the wall and neither of those corrected the issue. I finally simply removed the PVR 250 from it's PCI slot, rebooted without it and then re-installed the PVR 250 and all was fine. On Fri, Jul 01, 2005 at 10:35:41PM +0200, Walter Haidinger wrote: > Hii > > Just in case somebody else has a similar problem: > I've got rid of the following error messages: > > > Jun 29 20:15:02 banshee kernel: msp34xx: I/O error #1 (write 0x12/0x00) > > Jun 29 20:15:04 banshee kernel: msp34xx: I/O error #2 (write 0x12/0x00) > > Jun 29 20:15:06 banshee kernel: msp34xx: I/O error #3 (write 0x12/0x00) > > Jun 29 20:15:06 banshee kernel: msp34xx: giving up, reseting chip. Sound > > will go off, sorry folks :-| > > Jun 29 20:15:06 banshee kernel: i2c_adapter i2c-3: sendbytes: error - > > bailout. > > They actually came from a bad/corrupted eeprom on my PVR 350. > Trying different ivtv-versions and debug levels turned up this: > > ivtv: Error -19 reading Hauppauge eeprom. > ivtv: Possible causes: the tveeprom module was not loaded, or > ivtv: the eeprom kernel module was loaded before the tveeprom module. > > followed by i2c errors like: > > ivtv: i2c client addr: 0x40 not found! > ivtv: i2c client addr: 0x40 not found! > ivtv: i2c client addr: 0x40 not found! > ivtv: Switching standard to PAL. > ivtv: i2c client id: 0x02 not found! > > However, the eeprom module was definitely not loaded and the tveeprom > module loaded without problems. > > Other messages from tveeprom included (to give some searches for this post > a chance ;-): > > tveeprom: Encountered bad packet header [f0]. > Corrupt or not a Hauppauge eeprom. > > This actually made me think. How do you fix a corrupted eeprom? There > is no tool for this coming with ivtv package, right? > Because I could not think of anything better, I removed the PVR 350 and put > it into a PC running Windows XP, installed the Hauppauge drivers and TV2000 > from the original CD. Did not turn up any problem. Could switch channels > and record MPEGs. So the card wasn't broken after all. > > Well, after putting the card back into my Linux machine, the errors > above were gone too. It's my (wild) guess that the original Hauppauge > drivers for Windows rewrote the eeprom contents. > > Anyways, it worked for me and I hope that it works for somebody else! ;-) > > Regards, Walter > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
