On Sun, 2008-09-14 at 01:33 -0400, test wrote: > I have 2 Ubuntu systems which are not identicle. > I installed the Hauppauge HVR 1600 in system A (my testing system). I > followed the info from the Ubuntu forum. The card was detected. So I > performed the same steps on system B ( my working system). Again, the > card was detected. >
> > Now, I have the card detected on system B where I want to use it. So for > further testing I reinstalled Ubuntu on system A and reinstalled the > card. dmesg | grep cx18 now gives a differant result. Here is the result... > > [EMAIL PROTECTED]:~$ dmesg | grep cx18 > [ 35.337116] cx18: Start initialization, version 1.0.0 > [ 35.337183] cx18-0: Initializing card #0 > [ 35.337186] cx18-0: Autodetected Hauppauge card > [ 35.337538] cx18-0: Unreasonably low latency timer, setting to 64 > (was 32) > [ 35.338747] cx18-0: cx23418 revision ffffffff (A) PCI bus errors on reads return 0xffffffff > [ 35.494047] cx18-0: Invalid EEPROM > [ 35.494049] cx18-0: VBI is not yet supported > [ 35.725689] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) > [ 35.727388] cx18-0: Disabled encoder IDX device > [ 35.727420] cx18-0: Registered device video0 for encoder MPEG (2 MB) > [ 35.727422] DVB: registering new adapter (cx18) > [ 35.886616] cx18-0: frontend initialization failed > [ 35.886795] cx18-0: DVB failed to register > [ 35.886828] cx18-0: Registered device video32 for encoder YUV (2 MB) > [ 35.886844] cx18-0: Registered device video24 for encoder PCM audio > (1 MB) > [ 35.886861] cx18-0: Registered device radio0 for encoder radio > [ 35.887115] cx18-0: Error -12 registering devices > [ 35.888619] cx18-0: Error -12 on initialization > [ 35.888639] cx18: probe of 0000:01:06.0 failed with error -12 > [ 35.888665] cx18: End initialization > > > What does this new dmesg result indicate and what should I do to correct it? It means you were lucky on system A and your motherboard chipset help correct things when the CX23418 didn't respond properly to IO from the host CPU. Here's how to fix assuming you've got the latest version from the v4l-dvb repository at linuxtv.org: # modprobe -r cx18 # modprobe cx18 mmio_ndelay=31 or use a value of 61, 91, 121, 152 or some higher multiple of 30.3 ns until the CX23418 always responds reliably. (The lowest value that works at first may not be reliable; then again, it might,) > I want to perfect it on the testing system before I do any more > configuring on the working system, and therefore I must understand the > problem. The problem is that the CX23418, under certain circumstances doesn't properly respond to back to back accesses by the CPU. I have a general feel for the conditions but not the exact circumstances. The initial solution is to throttle all CPU accesses to the CX23418 by some multiple of a PCI bus clock (30.3 ns) until the CX23418 always responds properly. This isn't a big deal since the CPU to CX23418 IO is essentially command and control of the CX23418; DMA of the video stream is done by a different mechanism. HTH. Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
