On Wednesday 20 February 2008 22:33:00 Tim wrote:
> > Close, but no cigar :-) I need the tveeprom output. If you grep
> > for 'tveeprom' then you should see it.
>
> Heh, that figures.
>
> Ok, so this line certainly does look suspicious:
>
> 2008-02-12_01:03:01.89876 kern.warn: tveeprom 2-0050: Encountered bad
> packet header [ff]. Corrupt or not a Hauppauge eeprom.
>
>
> ideas?
Well, that probably explains your problems: if it can't read the eeprom,
then it cannot find the right tuner to use. Luckily you can pass the
tuner manually as well: add the ivtv module option 'tuner=47' and it
should work again.
Is it possible to figure out when the eeprom troubles started? Did they
start suddenly (suggests a hardware problem) or after a kernel/driver
update?
Regards,
Hans
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
