[EMAIL PROTECTED] wrote:
All,
I've searched using google and looked on the IVTV site. I will also send email
to the ivtv mailing list, but I want to see if anyone here has seen this.
I am running FC4 following Jarod's install w/ latest Myth SVN 7644. I do not
have selinux enabled. If I reboot the machine (warm), the ivtv drivers do not
correctly detect the cards and there's also other badness in the logs:
Nov 3 16:34:15 baavo kernel: ivtv: ==================== START INIT IVTV
====================
Nov 3 16:34:15 xyz kernel: ivtv: version 0.4.0 (tagged release) loading
Nov 3 16:34:15 xyz kernel: ivtv: Linux version: 2.6.13-1.1532_FC4 686 REGPARM
4KSTACKS gcc-4.0
Nov 3 16:34:15 xyz kernel: ivtv: In case of problems please include the debug
info
Nov 3 16:34:16 xyz kernel: ivtv: between the START INIT IVTV and END INIT IVTV
lines when
Nov 3 16:34:16 xyz kernel: ivtv: mailing the ivtv-devel mailinglist.
Nov 3 16:34:16 xyz kernel: ivtv0: Autodetected WinTV PVR 150 card (iTVC16
based)
and then lots of this:
Nov 3 16:34:16 xyz kernel: ivtv0 warning: i2c client addr: 0x44 not found for
command 0x40046404!
Nov 3 16:34:16 xyz kernel: ivtv0 warning: i2c client addr: 0x1b not found for
command 0x40047764!
If I do a *cold* reboot, everything works as expected.
Ideas?
Yes, known behaviour of the cards.....
Not even the manufacturer manages to write a (windows) driver that
correctly handles the warm boot case in all situations.
Rudy
Thanks,
Brian
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users