On Friday 11 March 2005 08:16, Scott Carr wrote: > Ok please find attached the dmesg output after loading the drivers and > running a cat /dev/video0 > test.mpg. > > Hope this helps you help me. ;-) Thanks
I don't have a clue what the 'i2c client addr: 0x44 not found!' business is about. Anyone else? Only thing that really stands out that I have a clue about is this: ivtv: Encoder revision: 0x02040011 I know ivtv gives a warning about newer encoder firmwares being buggy, but that needs to be updated, its not correct anymore. My 150 (and all other ivtv cards I have, for that matter) is currently functioning perfectly using the 0x02040024 encoder revision, which you can get out of here: ftp://ftp.shspvr.com/download/wintv-pvr_250-350/inf/pvr_1.18.21.22168_inf.zip Worth a shot, anyhow. Just to be certain, you don't have any other capture cards in this machine, i.e., and analog card that might actually be getting /dev/video0, do you? -- Jarod Wilson [EMAIL PROTECTED]
pgpuvBLsqfXg5.pgp
Description: PGP signature
