On Sat, 2009-10-31 at 18:14 -0400, Jacob Michael van Wessem wrote: > (removing long previous text, let me know if you'd like me to keep > including this) > > Is there anything else I can try to get the driver to work?
>From what I understood you took it to a different machine and tested it under window there, correct? So you have eliminated the possibility of a defective card. What's left could be a PCI bus problem or a firmware image problem. (I think - I'm a bit tired right now.) I believe in the first mail I gave you a few other things to try related to simple PCI bus troubleshooting. Please try those. You should also verify your firmwre images - please use the ones from ivtvdriver.org - those are what the driver is developed against: http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz > How do the firmware images work? Does the cx-18 driver upload these to > the WinTV card, then have it bootstrap from these, or is it something > that runs on the main cpu? 1. APU firmware is uploaded to the CX23418 2. CPU firmware is uploaded to the CX23418 3. CPU firmware is started which will also start the APU firmware 4. A PEEK command is issued to the CPU to see if it is alive and the APU is issued a RESETAI command to avoid audio problems (superstition) 5. Steps 1-4 are repeated to overcome a TS stream bug and analog audio encoding bug. 6. Digitizer firmware is loaded later when the digitizer is first configured. 7. The digitizer firmware load is read back and verified. 8. The digitizer firmware is started. As I recall from your previous logs, it looked like the APU in your CX23418 was not running/responding to the RESETAI command. That's bad. Is there anything in your dmesg or /var/log/messages about interrupts being ignored or disabled because "nobody cared"? You should try loading the cx18 module with the debug=255 parameter to see if anything interesting shows up in dmesg or /var/log/messages. > Again, the card works under Windows. I understand this does not mean > there are no hardware issues under Windows - could be that the Windows > driver is more capable to deal with faulty hardware, no? No, Windows doesn't hammer on the PCI bus like Linux does. In more recent kernels, Linux has gotten more agressive on PCI accesses, especially at boot. This causes flaky buses or buses with bad connections or quirky bridge chips to error out on some PCI bus communications. It is very much a function of you motherboard chipset, all the cards plugged into the PCI bus, all the linux driver modules for those devices and whatever other parts of Linux starts hammering on devices early on. Regards, Andy > Thank you, > > Michiel van Wessem _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
