> > Thanks for the suggestion, I'll see on the next reboot if it helps. > > You said you *had* this problem for a while... What was your solution?
After weeks of instability, suspecting the gcc version, suspecting i2c-bus loading problems and various ivtv versions, it turned out I had a bad card. It was brand new, but bad. The IR chip also wouldn't detect. Sometimes it would cold-boot ok, but most of the time it had "ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!" and "'tveeprom 1-0050: Huh, no eeprom present (err=-121)?" errors. In the end, I rang Hauppage directly in New York and they replaced the card for me. Since then - all happy for 6 weeks now.... > I have noticed that when the system *does* boot, it produces the errors > listed below (firmware not found). If I then do an rmmod ivtv_fb; rmmod > ivtv followed by a modprobe ivtv, everything starts. I found that the modprobe of ivtv was taking too long and udev was timing out. The new card takes about 3 seconds to modprobe. > To me this indicates some kind of timing problem when udev tries to load > ivtv. Perhaps it is still too early in the boot process for ivtv to start > reliably. Confirmed the original card fault my sticking it in a Windows machine and loading all the latest patched and updates from Hauppauge (yuk). > > regards, > stanley. > > >> I had this problem for a while. >> >> add: >> blacklist ivtv >> to: >> /etc/modprobe.d/blacklist >> >> and diagnose your ivtv problems manually >> _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
