I might have a similar problem. I have a 150, and sometimes it is autodetected as a 250. Also, sometimes the picture quality is good even though it is seen as a 250, and sometimes picture quality is bad even when seen as a 150. Usually I can get good picture by removing and reloading the modules. Sometimes I need to turn the machine off in order to get the card autodetected as a 150. Really weird...
Haven't checked /proc/bus/pci/01, but will do that when I get the time. However, one difference I have seen in /var/log/messages between "good picture" and "bad picture" is that when bad "kernel: ivtv: Unreasonably low latency timer, setting to 64 (was 32)" is displayed in /var/log/messages. Maybe something to do with latency settings in BIOS? Regards, /jon > I've been working with Mark Knecht tracking down his problem with his > cards not initializing properly every boot. We're using the PCI > subsystem information to say "card 0 is a 250", but when we map the io > and start chatting on the I2C, we've obviously got a 150. We detect > card 1 as a 150, but it is clearly a 250 once we talk to it. Mark's > been really great about providing me information. Finally I've hit a > brick wall with this bit of information: > > --- WORKING BOOUP --- > cat /proc/bus/pci/01/01.0 | od -Ax -t x1 > 000000 44 44 16 00 06 00 10 02 01 00 00 04 08 40 00 00 > 000010 08 00 00 f0 00 00 00 00 00 00 00 00 00 00 00 00 > 000020 00 00 00 00 00 00 00 00 00 00 00 00 70 00 03 80 > 000030 00 00 00 00 44 00 00 00 00 00 00 00 05 01 80 08 > cat /proc/bus/pci/01/02.0 | od -Ax -t x1 > 000000 44 44 16 00 06 00 10 02 01 00 00 04 08 40 00 00 > 000010 08 00 00 f4 00 00 00 00 00 00 00 00 00 00 00 00 > 000020 00 00 00 00 00 00 00 00 00 00 00 00 70 00 09 40 > 000030 00 00 00 00 44 00 00 00 00 00 00 00 03 01 80 08 > > --- BUSTED BOOTUP --- > cat /proc/bus/pci/01/01.0 | od -Ax -t x1 > 000000 44 44 16 00 06 00 10 02 01 00 00 04 08 40 00 00 > 000010 08 00 00 f0 00 00 00 00 00 00 00 00 00 00 00 00 > 000020 00 00 00 00 00 00 00 00 00 00 00 00 70 00 03 00 > 000030 00 00 00 00 44 00 00 00 00 00 00 00 05 01 80 08 > cat /proc/bus/pci/01/02.0 | od -Ax -t x1 > 000000 44 44 16 00 06 00 10 02 01 00 00 04 08 40 00 00 > 000010 08 00 00 f4 00 00 00 00 00 00 00 00 00 00 00 00 > 000020 00 00 00 00 00 00 00 00 00 00 00 00 70 00 09 00 > 000030 00 00 00 00 44 00 00 00 00 00 00 00 03 01 80 08 > > Note that the difference between the two is that the PCI subsystem > device field statring at 0x2e is cleared in the non-working system. > This throws off our autodetection and causes us to set up wrong, as that > byte is significant: > device 00 03 -> PVR250 > device 80 03 -> PVR150 > device 00 09 -> PVR150 > device 40 09 -> PVR250 > > Has anyone ever seen this behavior? How in the heck can this be > happening? It is rather consistent, and only that one byte gets messed > up! > > > ------------------------------------------------------- > 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
