Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: users

Insertion erros when installing cx18

 

 

ivtv users RSS feed   Index | Next | Previous | View Threaded


sofasurferlinux at charter

Oct 11, 2008, 11:11 PM

Post #1 of 16 (3680 views)
Permalink
Insertion erros when installing cx18

I followed the instructions at http://www.ivtvdriver.org/index.php/Cx18.
I obtained the driver and performed these... Unpack, 'make menuconfig',
'make', 'make install' (as root), 'make unload' (as root) and run
'modprobe cx18'.

All went well except modprobe. Do I run that as root or not. As root it
returned nothing. When run as not root it returned the following...

daryl [at] daryl-deskto:~/v4l-dvb-1e7e0b56d97b$ modprobe cx18
WARNING: Error inserting tveeprom
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/tveeprom.ko):
Operation not permitted
WARNING: Error inserting v4l2_common
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/v4l2-common.ko):
Operation not permitted
WARNING: Error inserting cx2341x
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx2341x.ko):
Operation not permitted
WARNING: Error inserting i2c_algo_bit
(/lib/modules/2.6.24-21-generic/kernel/drivers/i2c/algos/i2c-algo-bit.ko):
Operation not permitted
WARNING: Error inserting v4l1_compat
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/v4l1-compat.ko):
Operation not permitted
WARNING: Error inserting videodev
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/videodev.ko):
Operation not permitted
WARNING: Error inserting compat_ioctl32
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/compat_ioctl32.ko):
Operation not permitted
WARNING: Error inserting dvb_core
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/dvb/dvb-core/dvb-core.ko):
Operation not permitted
FATAL: Error inserting cx18
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx18/cx18.ko):
Operation not permitted

I have just reinstalled Hardy from a live cd and did a update and
upgrade. Nothing else performed on system.

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


rich.ayotte at gmail

Oct 12, 2008, 4:20 AM

Post #2 of 16 (3485 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

Run modprobe as root and then run dmesg|grep cx18 to see if the module
loaded.

--
Richard


On Sun, Oct 12, 2008 at 2:11 AM, daryl <sofasurferlinux [at] charter> wrote:

> I followed the instructions at http://www.ivtvdriver.org/index.php/Cx18.
> I obtained the driver and performed these... Unpack, 'make menuconfig',
> 'make', 'make install' (as root), 'make unload' (as root) and run
> 'modprobe cx18'.
>
> All went well except modprobe. Do I run that as root or not. As root it
> returned nothing. When run as not root it returned the following...
>
> daryl [at] daryl-deskto:~/v4l-dvb-1e7e0b56d97b$ modprobe cx18
> WARNING: Error inserting tveeprom
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/tveeprom.ko):
> Operation not permitted
> WARNING: Error inserting v4l2_common
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/v4l2-common.ko):
> Operation not permitted
> WARNING: Error inserting cx2341x
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx2341x.ko):
> Operation not permitted
> WARNING: Error inserting i2c_algo_bit
> (/lib/modules/2.6.24-21-generic/kernel/drivers/i2c/algos/i2c-algo-bit.ko):
> Operation not permitted
> WARNING: Error inserting v4l1_compat
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/v4l1-compat.ko):
> Operation not permitted
> WARNING: Error inserting videodev
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/videodev.ko):
> Operation not permitted
> WARNING: Error inserting compat_ioctl32
>
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/compat_ioctl32.ko):
> Operation not permitted
> WARNING: Error inserting dvb_core
>
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/dvb/dvb-core/dvb-core.ko):
> Operation not permitted
> FATAL: Error inserting cx18
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx18/cx18.ko):
> Operation not permitted
>
> I have just reinstalled Hardy from a live cd and did a update and
> upgrade. Nothing else performed on system.
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>


sofasurferlinux at charter

Oct 12, 2008, 7:01 AM

Post #3 of 16 (3475 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

I ran "sudo modprobe cx18" and dmesg | grep cx18. Here is my result...

daryl [at] daryl-deskto:~$ sudo modprobe cx18
[sudo] password for daryl:
daryl [at] daryl-deskto:~$ dmesg|grep cx18
[ 38.585719] cx18: Start initialization, version 1.0.1
[ 38.585782] cx18-0: Initializing card #0
[ 38.585786] cx18-0: Autodetected Hauppauge card
[ 38.586104] cx18-0: Unreasonably low latency timer, setting to 64
(was 32)
[ 38.587202] cx18-0: cx23418 revision 01010000 (B)
[ 38.766722] cx18-0: Invalid EEPROM
[ 38.766725] cx18-0: VBI is not yet supported
[ 38.994788] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 38.998714] cx18-0: Disabled encoder IDX device
[ 38.998753] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 38.998757] DVB: registering new adapter (cx18)
[ 39.035929] cx18-0: frontend initialization failed
[ 39.036078] cx18-0: DVB failed to register
[ 39.036106] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 39.036122] cx18-0: Registered device video24 for encoder PCM audio
(1 MB)
[ 39.036141] cx18-0: Registered device radio0 for encoder radio
[ 39.036331] cx18-0: Error -12 registering devices
[ 39.037826] cx18-0: Error -12 on initialization
[ 39.037846] cx18: probe of 0000:01:06.0 failed with error -12
[ 39.037873] cx18: End initialization

I have come to this point before and learned about using these 2 commands...

/sudo modprobe -r cx18
sudo //modprobe cx18 mmio_ndelay=31 (optional values 31,61,91,121,152)
/

I ran these commands and this is the result...

daryl [at] daryl-deskto:~$ sudo modprobe cx18 mnio_ndelay=31
FATAL: Error inserting cx18
(/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx18/cx18.ko):
Unknown symbol in module, or unknown parameter (see dmesg).

Any ideas? "FATAL" sounds like a bad thing :-)


Richard Ayotte wrote:
> Run modprobe as root and then run dmesg|grep cx18 to see if the module
> loaded.
>
> --
> Richard
>
>
> On Sun, Oct 12, 2008 at 2:11 AM, daryl <sofasurferlinux [at] charter
> <mailto:sofasurferlinux [at] charter>> wrote:
>
> I followed the instructions at
> http://www.ivtvdriver.org/index.php/Cx18.
> I obtained the driver and performed these... Unpack, 'make
> menuconfig',
> 'make', 'make install' (as root), 'make unload' (as root) and run
> 'modprobe cx18'.
>
> All went well except modprobe. Do I run that as root or not. As
> root it
> returned nothing. When run as not root it returned the following...
>
> daryl [at] daryl-deskto:~/v4l-dvb-1e7e0b56d97b$ modprobe cx18
> WARNING: Error inserting tveeprom
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/tveeprom.ko):
> Operation not permitted
> WARNING: Error inserting v4l2_common
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/v4l2-common.ko):
> Operation not permitted
> WARNING: Error inserting cx2341x
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx2341x.ko):
> Operation not permitted
> WARNING: Error inserting i2c_algo_bit
> (/lib/modules/2.6.24-21-generic/kernel/drivers/i2c/algos/i2c-algo-bit.ko):
> Operation not permitted
> WARNING: Error inserting v4l1_compat
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/v4l1-compat.ko):
> Operation not permitted
> WARNING: Error inserting videodev
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/videodev.ko):
> Operation not permitted
> WARNING: Error inserting compat_ioctl32
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/compat_ioctl32.ko):
> Operation not permitted
> WARNING: Error inserting dvb_core
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/dvb/dvb-core/dvb-core.ko):
> Operation not permitted
> FATAL: Error inserting cx18
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx18/cx18.ko):
> Operation not permitted
>
> I have just reinstalled Hardy from a live cd and did a update and
> upgrade. Nothing else performed on system.
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver <mailto:ivtv-users [at] ivtvdriver>
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


rich.ayotte at gmail

Oct 12, 2008, 8:12 AM

Post #4 of 16 (3473 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

> I ran these commands and this is the result...
>
> daryl [at] daryl-deskto:~$ sudo modprobe cx18 mnio_ndelay=31
> FATAL: Error inserting cx18
> (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx18/cx18.ko):
> Unknown symbol in module, or unknown parameter (see dmesg).
>
> Any ideas? "FATAL" sounds like a bad thing :-)



Looks like you misspelled mnio_ndelay. I should be mmio_ndelay.

Rich


sofasurferlinux at charter

Oct 12, 2008, 11:41 AM

Post #5 of 16 (3468 views)
Permalink
Insertion erros when installing cx18 [In reply to]

You are right Rich. I misspelled mmio. Sorry.

OK. I ran...
sudo modprobe -r cx18
sudo //modprobe cx18 mmio_ndelay=31,61 and 91

Here is the new results from dmesg | grep cx18. Note that the last result of mmio_ndelay=91 gives "FATAL: Module cx18 is in use."...

daryl [at] daryl-deskto:~$ sudo modprobe -r cx18
daryl [at] daryl-deskto:~$ sudo modprobe cx18 mmio_ndelay=31
daryl [at] daryl-deskto:~$ dmesg | grep cx18
[ 828.234512] cx18: Start initialization, version 1.0.1
[ 828.234561] cx18-0: Initializing card #0
[ 828.234565] cx18-0: Autodetected Hauppauge card
[ 828.234907] cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
[ 828.236032] cx18-0: cx23418 revision 01010000 (B)
[ 828.318913] cx18-0: Invalid EEPROM
[ 828.318915] cx18-0: VBI is not yet supported
[ 828.365193] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 828.367391] cx18-0: Disabled encoder IDX device
[ 828.367616] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 828.367736] DVB: registering new adapter (cx18)
[ 828.379379] cx18-0: frontend initialization failed
[ 828.379533] cx18-0: DVB failed to register
[ 828.379558] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 828.379575] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 828.379590] cx18-0: Registered device radio0 for encoder radio
[ 828.379753] cx18-0: Error -12 registering devices
[ 828.381154] cx18-0: Error -12 on initialization
[ 828.381182] cx18: probe of 0000:01:06.0 failed with error -12
[ 828.381201] cx18: End initialization
[ 995.972056] cx18: Start initialization, version 1.0.1
[ 995.972111] cx18-0: Initializing card #0
[ 995.972114] cx18-0: Autodetected Hauppauge card
[ 995.973258] cx18-0: cx23418 revision ffffffff (A)
[ 996.117695] cx18-0: Invalid EEPROM
[ 996.117698] cx18-0: VBI is not yet supported
[ 996.162359] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 996.164625] cx18-0: Disabled encoder IDX device
[ 996.164792] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 996.164906] DVB: registering new adapter (cx18)
[ 996.165904] cx18-0: frontend initialization failed
[ 996.166184] cx18-0: DVB failed to register
[ 996.166296] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 996.166423] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 996.166551] cx18-0: Registered device radio0 for encoder radio
[ 996.166798] cx18-0: Error -12 registering devices
[ 996.168296] cx18-0: Error -12 on initialization
[ 996.174179] cx18: probe of 0000:01:06.0 failed with error -12
[ 996.174490] cx18: End initialization
daryl [at] daryl-deskto:~$ sudo modprobe -r cx18
daryl [at] daryl-deskto:~$ sudo modprobe cx18 mmio_ndelay=61
daryl [at] daryl-deskto:~$ dmesg | grep cx18
[ 828.234512] cx18: Start initialization, version 1.0.1
[ 828.234561] cx18-0: Initializing card #0
[ 828.234565] cx18-0: Autodetected Hauppauge card
[ 828.234907] cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
[ 828.236032] cx18-0: cx23418 revision 01010000 (B)
[ 828.318913] cx18-0: Invalid EEPROM
[ 828.318915] cx18-0: VBI is not yet supported
[ 828.365193] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 828.367391] cx18-0: Disabled encoder IDX device
[ 828.367616] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 828.367736] DVB: registering new adapter (cx18)
[ 828.379379] cx18-0: frontend initialization failed
[ 828.379533] cx18-0: DVB failed to register
[ 828.379558] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 828.379575] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 828.379590] cx18-0: Registered device radio0 for encoder radio
[ 828.379753] cx18-0: Error -12 registering devices
[ 828.381154] cx18-0: Error -12 on initialization
[ 828.381182] cx18: probe of 0000:01:06.0 failed with error -12
[ 828.381201] cx18: End initialization
[ 995.972056] cx18: Start initialization, version 1.0.1
[ 995.972111] cx18-0: Initializing card #0
[ 995.972114] cx18-0: Autodetected Hauppauge card
[ 995.973258] cx18-0: cx23418 revision ffffffff (A)
[ 996.117695] cx18-0: Invalid EEPROM
[ 996.117698] cx18-0: VBI is not yet supported
[ 996.162359] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 996.164625] cx18-0: Disabled encoder IDX device
[ 996.164792] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 996.164906] DVB: registering new adapter (cx18)
[ 996.165904] cx18-0: frontend initialization failed
[ 996.166184] cx18-0: DVB failed to register
[ 996.166296] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 996.166423] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 996.166551] cx18-0: Registered device radio0 for encoder radio
[ 996.166798] cx18-0: Error -12 registering devices
[ 996.168296] cx18-0: Error -12 on initialization
[ 996.174179] cx18: probe of 0000:01:06.0 failed with error -12
[ 996.174490] cx18: End initialization
[ 1010.965409] cx18: Start initialization, version 1.0.1
[ 1010.965463] cx18-0: Initializing card #0
[ 1010.965466] cx18-0: Autodetected Hauppauge card
[ 1010.966636] cx18-0: cx23418 revision ffffffff (A)
[ 1011.112193] cx18-0: Invalid EEPROM
[ 1011.112196] cx18-0: VBI is not yet supported
[ 1011.157222] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 1011.159540] cx18-0: Disabled encoder IDX device
[ 1011.159668] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 1011.159781] DVB: registering new adapter (cx18)
[ 1011.160801] cx18-0: frontend initialization failed
[ 1011.161113] cx18-0: DVB failed to register
[ 1011.161223] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 1011.161351] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 1011.161506] cx18-0: Registered device radio0 for encoder radio
[ 1011.161757] cx18-0: Error -12 registering devices
[ 1011.163231] cx18-0: Error -12 on initialization
[ 1011.169969] cx18: probe of 0000:01:06.0 failed with error -12
[ 1011.170175] cx18: End initialization
daryl [at] daryl-deskto:~$ sudo modprobe -r cx18
daryl [at] daryl-deskto:~$ sudo modprobe cx18 mmio_ndelay=91
daryl [at] daryl-deskto:~$ dmesg | grep cx18
[ 828.234512] cx18: Start initialization, version 1.0.1
[ 828.234561] cx18-0: Initializing card #0
[ 828.234565] cx18-0: Autodetected Hauppauge card
[ 828.234907] cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
[ 828.236032] cx18-0: cx23418 revision 01010000 (B)
[ 828.318913] cx18-0: Invalid EEPROM
[ 828.318915] cx18-0: VBI is not yet supported
[ 828.365193] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 828.367391] cx18-0: Disabled encoder IDX device
[ 828.367616] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 828.367736] DVB: registering new adapter (cx18)
[ 828.379379] cx18-0: frontend initialization failed
[ 828.379533] cx18-0: DVB failed to register
[ 828.379558] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 828.379575] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 828.379590] cx18-0: Registered device radio0 for encoder radio
[ 828.379753] cx18-0: Error -12 registering devices
[ 828.381154] cx18-0: Error -12 on initialization
[ 828.381182] cx18: probe of 0000:01:06.0 failed with error -12
[ 828.381201] cx18: End initialization
[ 995.972056] cx18: Start initialization, version 1.0.1
[ 995.972111] cx18-0: Initializing card #0
[ 995.972114] cx18-0: Autodetected Hauppauge card
[ 995.973258] cx18-0: cx23418 revision ffffffff (A)
[ 996.117695] cx18-0: Invalid EEPROM
[ 996.117698] cx18-0: VBI is not yet supported
[ 996.162359] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 996.164625] cx18-0: Disabled encoder IDX device
[ 996.164792] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 996.164906] DVB: registering new adapter (cx18)
[ 996.165904] cx18-0: frontend initialization failed
[ 996.166184] cx18-0: DVB failed to register
[ 996.166296] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 996.166423] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 996.166551] cx18-0: Registered device radio0 for encoder radio
[ 996.166798] cx18-0: Error -12 registering devices
[ 996.168296] cx18-0: Error -12 on initialization
[ 996.174179] cx18: probe of 0000:01:06.0 failed with error -12
[ 996.174490] cx18: End initialization
[ 1010.965409] cx18: Start initialization, version 1.0.1
[ 1010.965463] cx18-0: Initializing card #0
[ 1010.965466] cx18-0: Autodetected Hauppauge card
[ 1010.966636] cx18-0: cx23418 revision ffffffff (A)
[ 1011.112193] cx18-0: Invalid EEPROM
[ 1011.112196] cx18-0: VBI is not yet supported
[ 1011.157222] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 1011.159540] cx18-0: Disabled encoder IDX device
[ 1011.159668] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 1011.159781] DVB: registering new adapter (cx18)
[ 1011.160801] cx18-0: frontend initialization failed
[ 1011.161113] cx18-0: DVB failed to register
[ 1011.161223] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 1011.161351] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 1011.161506] cx18-0: Registered device radio0 for encoder radio
[ 1011.161757] cx18-0: Error -12 registering devices
[ 1011.163231] cx18-0: Error -12 on initialization
[ 1011.169969] cx18: probe of 0000:01:06.0 failed with error -12
[ 1011.170175] cx18: End initialization
[ 1020.684787] cx18: Start initialization, version 1.0.1
[ 1020.684849] cx18-0: Initializing card #0
[ 1020.684853] cx18-0: Autodetected Hauppauge card
[ 1020.686204] cx18-0: cx23418 revision ffffffff (A)
[ 1020.832048] cx18-0: Invalid EEPROM
[ 1020.832050] cx18-0: VBI is not yet supported
[ 1020.876499] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 1020.882583] cx18-0: Disabled encoder IDX device
[ 1020.882629] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 1020.882632] DVB: registering new adapter (cx18)
[ 1020.886489] cx18-0: frontend initialization failed
[ 1020.886585] cx18-0: DVB failed to register
[ 1020.886609] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 1020.886625] cx18-0: Registered device video24 for encoder PCM audio (1 MB)
[ 1020.886639] cx18-0: Registered device radio0 for encoder radio
[ 1020.886804] cx18-0: Error -12 registering devices
[ 1020.888188] cx18-0: Error -12 on initialization
[ 1020.888391] cx18: probe of 0000:01:06.0 failed with error -12
[ 1020.889199] cx18: End initialization
[ 1020.904608] cx18-0: unable to open firmware v4l-cx23418-apu.fw
[ 1020.904614] cx18-0: did you put the firmware in the hotplug firmware directory?
[ 1020.904640] [<ffffffff8844caab>] :cx18:cx18_writel_retry+0x2b/0x80
[ 1020.904661] Modules linked in: cx18 dvb_core compat_ioctl32 i2c_algo_bit cx2341x tveeprom s5h1409 cs5345 tuner videodev v4l1_compat v4l2_common ipv6 aes_x86_64 aes_generic af_packet rfcomm l2cap bluetooth ppdev powernow_k8 cpufreq_stats cpufreq_conservative cpufreq_ondemand freq_table cpufreq_userspace cpufreq_powersave sbs dock video output sbshc container battery iptable_filter ip_tables x_tables ac lp snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_hwdep evdev snd_seq_dummy arc4 ecb blkcipher snd_seq_oss snd_seq_midi rt61pci rt2x00pci rt2x00lib rfkill input_polldev crc_itu_t snd_rawmidi mac80211 snd_seq_midi_event snd_seq cfg80211 snd_timer snd_seq_device serio_raw eeprom_93cx6 button parport_pc parport snd shpchp k8temp i2c_nforce2 pci_hotplug soundcore psmouse pcspkr i2c_core ext3 jbd mbcache sg sr_mod cdrom sd_mod pata_amd sata_nv pata_acpi ata_generic ohci_hcd ehci_hcd forcedeth libata scsi_mod usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse
[ 1020.904745] RIP: 0010:[<ffffffff8844caab>] [<ffffffff8844caab>] :cx18:cx18_writel_retry+0x2b/0x80
[ 1020.904806] [<ffffffff88440500>] :cx18:cx18_firmware_init+0x730/0xa10
[ 1020.904830] [<ffffffff8843c3cb>] :cx18:cx18_init_on_first_open+0x6b/0x180
[ 1020.904854] [<ffffffff88442813>] :cx18:cx18_v4l2_open+0xa3/0x230
[ 1020.904930] RIP [<ffffffff8844caab>] :cx18:cx18_writel_retry+0x2b/0x80
daryl [at] daryl-deskto:~$ sudo modprobe -r cx18
FATAL: Module cx18 is in use.
daryl [at] daryl-deskto:~$ sudo modprobe cx18 mmio_ndelay=91





>/ I ran these commands and this is the result...
/>/
/>/ daryl at daryl-desktop <http://ivtvdriver.org/mailman/listinfo/ivtv-users>:~$ sudo modprobe cx18 mnio_ndelay=31
/>/ FATAL: Error inserting cx18
/>/ (/lib/modules/2.6.24-21-generic/kernel/drivers/media/video/cx18/cx18.ko):
/>/ Unknown symbol in module, or unknown parameter (see dmesg).
/>/
/>/ Any ideas? "FATAL" sounds like a bad thing :-)
/


>Looks like you misspelled mnio_ndelay. I should be mmio_ndelay.

>Rich



_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at radix

Oct 12, 2008, 4:43 PM

Post #6 of 16 (3464 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

Daryl,

Sorry to reply to this part of the thread instead of your latest message
- email logistics problems. Anyway...

OK, you have obvious PCI bus communications problems. The CX23418 could
be the cause or something else in your system could be the cause.
Recent experience leads me to believe it's likely the CX23418.

The good news is you are using the '1.0.1' version of the cx18 driver
that does PCI retries to get reliable communications to the CX23418.
The bad news is, it doesn't appear to work for you.

So here's some things to do:

1. Don't use the 'mmio_ndelay' module parameter. With the new
'retry_mmio' module parameter enabled (which is the default),
'mmio_ndelay' has a statistically insignificant effect, if any at all.



2. You've got a memory shortage of some sort (error -12 is -ENOMEM).
This may be related to vmalloc address space or actual memory pages to
allocate. To check Vmalloc space

$ cat /proc/meminfo | grep -i vmalloc
VmallocTotal: 34359738367 kB
VmallocUsed: 76476 kB
VmallocChunk: 34359661291 kB

if Total-Used is < 64 MB or Chunk is < 64 MB, you'll need to add a
'vmalloc=nnnM' option to your kernel command line. If adding the
vmalloc kernel command line option, use a value 128 MB greater than your
current total.

If your vmalloc space is OK, as a workaround you can use module
parameters to reduce the memory required by the driver.

$ su - root
# modprobe cx18 enc_mpg_buffers=1 enc_ts_buffers=0 \
enc_yuv_buffers=0 enc_pcm_buffers=0



3. The version '1.0.1' cx18 driver logs statistics about PCI mmio
retires. If you do this

$ su - root
# modprobe cx18 debug=3
# modprobe -r cx18

Then even if the driver fails to initialize the card, it should dump
statistics to dmesg when it is removed. They look something like this:

cx18-0 info: retried_write[0] = 3715891
cx18-0 info: retried_write[1] = 51
cx18-0 info: retried_write[2] = 11
cx18-0 info: retried_write[3] = 9
cx18-0 info: retried_write[4] = 3
cx18-0 info: retried_write[5] = 9
cx18-0 info: retried_write[6] = 14
cx18-0 info: retried_write[7] = 12
cx18-0 info: retried_write[8] = 16
cx18-0 info: retried_write[9] = 15
cx18-0 info: retried_write[10] = 593956
cx18-0 info: retried_read[0] = 10376734
cx18-0 info: retried_read[1] = 0
cx18-0 info: retried_read[2] = 0
cx18-0 info: retried_read[3] = 0
cx18-0 info: retried_read[4] = 0
cx18-0 info: retried_read[5] = 0
cx18-0 info: retried_read[6] = 0
cx18-0 info: retried_read[7] = 0
cx18-0 info: retried_read[8] = 0
cx18-0 info: retried_read[9] = 0
cx18-0 info: retried_read[10] = 456

'retried_write[10]' and 'retried_read[10]' are the count of accesses
that absolutely failed.

'retried_write[0]' and 'retried_read[0]' are the count of accesses that
succeeded on the first try.

Indices 1-9 log the number of access that succeeded on 1-9 retries.

Could you provide the statistics from you driver?


4. Could you provide the output of

# lspci -nnvv

run as root on your system? I'm specifically looking for the setting of
the latency timer of the bridges the CX23418 is behind, also for the PCI
Status flags, and for the specific Southbridge chipset you have.


5. Could you provide the full lines of the cx18-driver Oops that
happened in you last log (don't grep on cx18 please)?


6. Don't load and unload the cx18 driver too many times in a row without
being prepared to deal with a kernel oops or hang. There's a memory
leak in the driver that only happens when a card fails to initialize.
(Sorry, I know I need to fix it.)


7. Can you test the same card under Windows in the same machine
(ideally) or a different machine?


Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


sofasurferlinux at charter

Oct 12, 2008, 7:05 PM

Post #7 of 16 (3443 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

Andy Walls wrote:
> Daryl,

First, I want to apologize for dumping all of this on you. Its such a
lot that I feel guilty.

>
> Sorry to reply to this part of the thread instead of your latest message
> - email logistics problems. Anyway...
>
> OK, you have obvious PCI bus communications problems. The CX23418 could
> be the cause or something else in your system could be the cause.
> Recent experience leads me to believe it's likely the CX23418.
>
> The good news is you are using the '1.0.1' version of the cx18 driver
> that does PCI retries to get reliable communications to the CX23418.
> The bad news is, it doesn't appear to work for you.
>
> So here's some things to do:
>
> 1. Don't use the 'mmio_ndelay' module parameter. With the new
> 'retry_mmio' module parameter enabled (which is the default),
> 'mmio_ndelay' has a statistically insignificant effect, if any at all.
>
>
>
> 2. You've got a memory shortage of some sort (error -12 is -ENOMEM).
> This may be related to vmalloc address space or actual memory pages to
> allocate. To check Vmalloc space
>
> $ cat /proc/meminfo | grep -i vmalloc
> VmallocTotal: 34359738367 kB
> VmallocUsed: 76476 kB
> VmallocChunk: 34359661291 kB

Here is my result...

daryl [at] daryl-deskto:~$ cat /proc/meminfo | grep -i vmalloc
VmallocTotal: 34359738367 kB
VmallocUsed: 6592 kB
VmallocChunk: 34359731751 kB

If I am understanding this correctly, "total used" is 6.4375 MB (way to
low) and "chunk" is 33554425.53809 MB? Is that possible?


>
> if Total-Used is < 64 MB or Chunk is < 64 MB, you'll need to add a
> 'vmalloc=nnnM' option to your kernel command line. If adding the
> vmalloc kernel command line option, use a value 128 MB greater than your
> current total.

Are you saying to add 128 MB to 34359738367 kB? That would be
33554553.53809 MB. I am sure I am wrong about this, aren't I?

I beleive the "kernel command line" is found in boot/grub/menu.lst and I
have listed it...

title Ubuntu 8.04.1, kernel 2.6.24-21-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-21-generic
root=UUID=ca07ba3c-44d2-47a0-81ee-e709258ac5aa ro quiet splash
initrd /boot/initrd.img-2.6.24-21-generic
quiet

If I am correct so far, please edit it the way you think it should be,
as I am feeling a little unsure of the process.


>
> If your vmalloc space is OK, as a workaround you can use module
> parameters to reduce the memory required by the driver.
>
> $ su - root
> # modprobe cx18 enc_mpg_buffers=1 enc_ts_buffers=0 \
> enc_yuv_buffers=0 enc_pcm_buffers=0
>
>
>
> 3. The version '1.0.1' cx18 driver logs statistics about PCI mmio
> retires. If you do this
>
> $ su - root
> # modprobe cx18 debug=3
> # modprobe -r cx18


su - root doesn't work. So I did the following...

daryl [at] daryl-deskto:~$ sudo modprobe cx18 debug=3
daryl [at] daryl-deskto:~$ sudo modprobe -r cx18
daryl [at] daryl-deskto:~$

Both gave no result.

>
> Then even if the driver fails to initialize the card, it should dump
> statistics to dmesg when it is removed. They look something like this:
>
> cx18-0 info: retried_write[0] = 3715891
> cx18-0 info: retried_write[1] = 51
> cx18-0 info: retried_write[2] = 11
> cx18-0 info: retried_write[3] = 9
> cx18-0 info: retried_write[4] = 3
> cx18-0 info: retried_write[5] = 9
> cx18-0 info: retried_write[6] = 14
> cx18-0 info: retried_write[7] = 12
> cx18-0 info: retried_write[8] = 16
> cx18-0 info: retried_write[9] = 15
> cx18-0 info: retried_write[10] = 593956
> cx18-0 info: retried_read[0] = 10376734
> cx18-0 info: retried_read[1] = 0
> cx18-0 info: retried_read[2] = 0
> cx18-0 info: retried_read[3] = 0
> cx18-0 info: retried_read[4] = 0
> cx18-0 info: retried_read[5] = 0
> cx18-0 info: retried_read[6] = 0
> cx18-0 info: retried_read[7] = 0
> cx18-0 info: retried_read[8] = 0
> cx18-0 info: retried_read[9] = 0
> cx18-0 info: retried_read[10] = 456
>
> 'retried_write[10]' and 'retried_read[10]' are the count of accesses
> that absolutely failed.
>
> 'retried_write[0]' and 'retried_read[0]' are the count of accesses that
> succeeded on the first try.
>
> Indices 1-9 log the number of access that succeeded on 1-9 retries.
>
> Could you provide the statistics from you driver?
>
>
> 4. Could you provide the output of
>
> # lspci -nnvv

daryl [at] daryl-deskto:~$ sudo lspci -nnvv
00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller
[10de:03ea] (rev a1)
Subsystem: Giga-byte Technology Unknown device [1458:5001]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Command: BaseUnitID=0 UnitCnt=17 MastHost- DefDir- DUL-
Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO-
<CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit
DwFcInEn- LWO=16bit DwFcOutEn-
Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+
<CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
Link Config 1: MLWI=8bit DwFcIn- MLWO=8bit DwFcOut- LWI=8bit
DwFcInEn- LWO=8bit DwFcOutEn-
Revision ID: 1.03
Link Frequency 0: 1.0GHz
Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
Link Frequency Capability 0: 200MHz+ 300MHz+ 400MHz+ 500MHz+
600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
Feature Capability: IsocFC+ LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD-
Link Frequency 1: 200MHz
Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
Link Frequency Capability 1: 200MHz- 300MHz- 400MHz- 500MHz-
600MHz- 800MHz- 1.0GHz- 1.2GHz- 1.4GHz- 1.6GHz- Vend-
Error Handling: PFlE+ OFlE+ PFE- OFE- EOCFE- RFE- CRCFE- SERRFE-
CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
Prefetchable memory behind bridge Upper: 00-00
Bus Number: 00
Capabilities: [dc] HyperTransport: MSI Mapping

00:01.0 ISA bridge [0601]: nVidia Corporation MCP61 LPC Bridge
[10de:03e0] (rev a2)
Subsystem: Giga-byte Technology Unknown device [1458:0c11]
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0

00:01.1 SMBus [0c05]: nVidia Corporation MCP61 SMBus [10de:03eb] (rev a2)
Subsystem: Giga-byte Technology Unknown device [1458:0c11]
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at c000 [size=64]
Region 4: I/O ports at 1c00 [size=64]
Region 5: I/O ports at c800 [size=64]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.2 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller
[10de:03f5] (rev a2)
Subsystem: Giga-byte Technology Unknown device [1458:0c11]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

00:02.0 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller
[10de:03f1] (rev a3) (prog-if 10 [OHCI])
Subsystem: Giga-byte Technology Unknown device [1458:5004]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 21
Region 0: Memory at f3006000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller
[10de:03f2] (rev a3) (prog-if 20 [EHCI])
Subsystem: Giga-byte Technology Unknown device [1458:5004]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin B routed to IRQ 22
Region 0: Memory at f3007000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Debug port
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+

00:04.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI bridge
[10de:03f3] (rev a1) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
Memory behind bridge: e8000000-efffffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: [b8] Subsystem: Giga-byte Technology Unknown device
[1458:026f]
Capabilities: [8c] HyperTransport: MSI Mapping

00:05.0 Audio device [0403]: nVidia Corporation MCP61 High Definition
Audio [10de:03f0] (rev a2)
Subsystem: Giga-byte Technology Unknown device [1458:a002]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin B routed to IRQ 23
Region 0: Memory at f3000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [6c] HyperTransport: MSI Mapping

00:06.0 IDE interface [0101]: nVidia Corporation MCP61 IDE [10de:03ec]
(rev a2) (prog-if 8a [Master SecP PriP])
Subsystem: Unknown device [f458:5002]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable)
[disabled] [size=8]
Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable)
[disabled] [size=1]
Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable)
[disabled] [size=8]
Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable)
[disabled] [size=1]
Region 4: I/O ports at f000 [size=16]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef]
(rev a2)
Subsystem: Giga-byte Technology Unknown device [1458:e000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 510
Region 0: Memory at f3004000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at cc00 [size=8]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/3 Enable+
Address: 00000000fee0300c Data: 4181
Masking: 000000fe Pending: 00000000
Capabilities: [6c] HyperTransport: MSI Mapping

00:08.0 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller
[10de:03f6] (rev a2) (prog-if 85 [Master SecO PriO])
Subsystem: Giga-byte Technology Unknown device [1458:b002]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 20
Region 0: I/O ports at 09f0 [size=8]
Region 1: I/O ports at 0bf0 [size=4]
Region 2: I/O ports at 0970 [size=8]
Region 3: I/O ports at 0b70 [size=4]
Region 4: I/O ports at e000 [size=16]
Region 5: Memory at f3005000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+
Queue=0/2 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [cc] HyperTransport: MSI Mapping

00:09.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge
[10de:03e8] (rev a2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Memory behind bridge: f0000000-f2ffffff
Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
Capabilities: [40] Subsystem: nVidia Corporation Unknown device
[10de:0000]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Queue=0/1 Enable+
Address: 00000000fee0300c Data: 4149
Capabilities: [60] HyperTransport: MSI Mapping
Capabilities: [80] Express Root Port (Slot+) IRQ 0
Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <64ns, L1 <1us
Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
Link: Latency L0s <512ns, L1 <4us
Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x8
Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise-
Slot: Number 1, PowerLimit 75.000000
Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
Slot: AttnInd Off, PwrInd On, Power-
Root: Correctable- Non-Fatal- Fatal- PME-

00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Capabilities: [80] HyperTransport: Host or Secondary Interface
!!! Possibly incomplete decoding
Command: WarmRst+ DblEnd-
Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
Link Config: MLWI=16bit MLWO=16bit LWI=16bit LWO=16bit
Revision ID: 1.02

00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Address Map [1022:1101]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] DRAM Controller [1022:1102]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Miscellaneous Control [1022:1103]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Capabilities: [f0] #0f [0010]

01:06.0 Multimedia video controller [0400]: Conexant CX23418 Single-Chip
MPEG-2 Encoder with Integrated Analog Video/Broadcast Audio Decoder
[14f1:5b7a]
Subsystem: Hauppauge computer works Inc. Unknown device [0070:7444]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (500ns min, 50000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e8000000 (32-bit, non-prefetchable) [size=64M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:07.0 Network controller [0280]: RaLink RT2561/RT61 802.11g PCI
[1814:0301]
Subsystem: Linksys WMP54G ver 4.1 [1737:0055]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at ec000000 (32-bit, non-prefetchable) [size=32K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

02:00.0 VGA compatible controller [0300]: nVidia Corporation G72
[GeForce 7300 SE] [10de:01d3] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Unknown device [3842:c428]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at f0000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at f1000000 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at f2000000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <256ns, L1 <4us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
Link: Latency L0s <256ns, L1 <4us
Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x8

daryl [at] daryl-deskto:~$


>
> run as root on your system? I'm specifically looking for the setting of
> the latency timer of the bridges the CX23418 is behind, also for the PCI
> Status flags, and for the specific Southbridge chipset you have.
>
>
> 5. Could you provide the full lines of the cx18-driver Oops that
> happened in you last log (don't grep on cx18 please)?

[ 0.000000] Processor #1
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] ACPI: IRQ14 used by override.
[ 0.000000] ACPI: IRQ15 used by override.
[ 0.000000] Setting APIC routing to flat
[ 0.000000] ACPI: HPET id: 0x10de8201 base: 0xfeff0000
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] swsusp: Registered nosave memory region: 000000000009f000
- 00000000000a0000
[ 0.000000] swsusp: Registered nosave memory region: 00000000000a0000
- 00000000000f0000
[ 0.000000] swsusp: Registered nosave memory region: 00000000000f0000
- 0000000000100000
[ 0.000000] Allocating PCI resources starting at 50000000 (gap:
40000000:a0000000)
[ 0.000000] SMP: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] PERCPU: Allocating 34656 bytes of per cpu data
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on.
Total pages: 257229
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line:
root=UUID=ca07ba3c-44d2-47a0-81ee-e709258ac5aa ro quiet splash
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
[ 0.000000] hpet clockevent registered
[ 0.000000] TSC calibrated against HPET
[ 19.524421] Marking TSC unstable due to TSCs unsynchronized
[ 19.524423] time.c: Detected 2210.051 MHz processor.
[ 19.526745] Console: colour VGA+ 80x25
[ 19.526748] console [tty0] enabled
[ 19.526763] Checking aperture...
[ 19.526766] CPU 0: aperture @ fbac000000 size 32 MB
[ 19.526767] Aperture too small (32 MB)
[ 19.532657] No AGP bridge found
[ 19.543538] Memory: 1021108k/1048512k available (2490k kernel code,
27016k reserved, 1318k data, 320k init)
[ 19.543575] SLUB: Genslabs=12, HWalign=64, Order=0-1, MinObjects=4,
CPUs=4, Nodes=1
[ 19.622336] Calibrating delay using timer specific routine.. 4424.34
BogoMIPS (lpj=8848685)
[ 19.622368] Security Framework initialized
[ 19.622375] SELinux: Disabled at boot.
[ 19.622387] AppArmor: AppArmor initialized
[ 19.622391] Failure registering capabilities with primary security
module.
[ 19.622474] Dentry cache hash table entries: 131072 (order: 8,
1048576 bytes)
[ 19.623196] Inode-cache hash table entries: 65536 (order: 7, 524288
bytes)
[ 19.623543] Mount-cache hash table entries: 256
[ 19.623668] Initializing cgroup subsys ns
[ 19.623671] Initializing cgroup subsys cpuacct
[ 19.623683] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[ 19.623685] CPU: L2 Cache: 512K (64 bytes/line)
[ 19.623687] CPU 0/0 -> Node 0
[ 19.623689] CPU: Physical Processor ID: 0
[ 19.623691] CPU: Processor Core ID: 0
[ 19.623712] SMP alternatives: switching to UP code
[ 19.624272] Early unpacking initramfs... done
[ 19.901277] ACPI: Core revision 20070126
[ 19.901321] ACPI: Looking for DSDT in initramfs... error, file
/DSDT.aml not found.
[ 19.945071] Using local APIC timer interrupts.
[ 19.990289] APIC timer calibration result 12557106
[ 19.990291] Detected 12.557 MHz APIC timer.
[ 19.990378] SMP alternatives: switching to SMP code
[ 19.990847] Booting processor 1/2 APIC 0x1
[ 20.001450] Initializing CPU#1
[ 20.078774] Calibrating delay using timer specific routine.. 4420.13
BogoMIPS (lpj=8840260)
[ 20.078780] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[ 20.078781] CPU: L2 Cache: 512K (64 bytes/line)
[ 20.078784] CPU 1/1 -> Node 0
[ 20.078785] CPU: Physical Processor ID: 0
[ 20.078786] CPU: Processor Core ID: 1
[ 20.078860] AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 02
[ 20.078402] Brought up 2 CPUs
[ 20.078494] CPU0 attaching sched-domain:
[ 20.078496] domain 0: span 03
[ 20.078498] groups: 01 02
[ 20.078500] domain 1: span 03
[ 20.078502] groups: 03
[ 20.078503] CPU1 attaching sched-domain:
[ 20.078505] domain 0: span 03
[ 20.078506] groups: 02 01
[ 20.078508] domain 1: span 03
[ 20.078509] groups: 03
[ 20.078721] net_namespace: 120 bytes
[ 20.079094] Time: 22:49:01 Date: 10/12/08
[ 20.079127] NET: Registered protocol family 16
[ 20.079292] ACPI: bus type pci registered
[ 20.079353] PCI: Using configuration type 1
[ 20.080444] ACPI: EC: Look up EC in DSDT
[ 20.085656] ACPI: Interpreter enabled
[ 20.085658] ACPI: (supports S0 S1 S4 S5)
[ 20.085671] ACPI: Using IOAPIC for interrupt routing
[ 20.093308] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 20.093877] PCI: Transparent bridge - 0000:00:04.0
[ 20.093969] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 20.094170] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[ 20.121271] ACPI: PCI Interrupt Link [LNK1] (IRQs 5 7 9 10 *11 14 15)
[ 20.121408] ACPI: PCI Interrupt Link [LNK2] (IRQs *5 7 9 10 11 14 15)
[ 20.121542] ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.121676] ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.121810] ACPI: PCI Interrupt Link [LNK5] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.121943] ACPI: PCI Interrupt Link [LNK6] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.122077] ACPI: PCI Interrupt Link [LNK7] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.122219] ACPI: PCI Interrupt Link [LNK8] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.122353] ACPI: PCI Interrupt Link [LIGP] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.122487] ACPI: PCI Interrupt Link [LP2P] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.122622] ACPI: PCI Interrupt Link [LUBA] (IRQs 5 7 9 10 *11 14 15)
[ 20.122757] ACPI: PCI Interrupt Link [LMAC] (IRQs 5 7 9 *10 11 14 15)
[ 20.122891] ACPI: PCI Interrupt Link [LAZA] (IRQs 5 7 9 *10 11 14 15)
[ 20.123025] ACPI: PCI Interrupt Link [LPMU] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.123160] ACPI: PCI Interrupt Link [LSMB] (IRQs 5 7 9 *10 11 14 15)
[ 20.123295] ACPI: PCI Interrupt Link [LUB2] (IRQs *5 7 9 10 11 14 15)
[ 20.123428] ACPI: PCI Interrupt Link [LIDE] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.123564] ACPI: PCI Interrupt Link [LSID] (IRQs 5 7 9 10 *11 14 15)
[ 20.123698] ACPI: PCI Interrupt Link [LFID] (IRQs 5 7 9 10 11 14 15)
*0, disabled.
[ 20.123867] ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0
[ 20.124029] ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0
[ 20.124189] ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
[ 20.124352] ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
[ 20.124512] ACPI: PCI Interrupt Link [APC5] (IRQs 16) *0, disabled.
[ 20.124670] ACPI: PCI Interrupt Link [APC6] (IRQs 16) *0, disabled.
[ 20.124828] ACPI: PCI Interrupt Link [APC7] (IRQs 16) *0, disabled.
[ 20.124987] ACPI: PCI Interrupt Link [APC8] (IRQs 16) *0, disabled.
[ 20.125146] ACPI: PCI Interrupt Link [AIGP] (IRQs 20 21 22 23) *0,
disabled.
[ 20.125305] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0
[ 20.125465] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0
[ 20.125624] ACPI: PCI Interrupt Link [APMU] (IRQs 20 21 22 23) *0,
disabled.
[ 20.125784] ACPI: PCI Interrupt Link [AAZA] (IRQs 20 21 22 23) *0
[ 20.125943] ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0
[ 20.126102] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0
[ 20.126263] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0,
disabled.
[ 20.126423] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0,
disabled.
[ 20.126583] ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0
[ 20.126742] ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0,
disabled.
[ 20.126853] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 20.126877] pnp: PnP ACPI init
[ 20.126885] ACPI: bus type pnp registered
[ 20.130870] pnp: PnP ACPI: found 15 devices
[ 20.130872] ACPI: ACPI bus type pnp unregistered
[ 20.131080] PCI: Using ACPI for IRQ routing
[ 20.131083] PCI: If a device doesn't work, try "pci=routeirq". If it
helps, post a report
[ 20.142226] NET: Registered protocol family 8
[ 20.142228] NET: Registered protocol family 20
[ 20.142298] hpet0: at MMIO 0xfeff0000, IRQs 2, 8, 31
[ 20.142302] hpet0: 3 32-bit timers, 25000000 Hz
[ 20.143345] AppArmor: AppArmor Filesystem Enabled
[ 20.146183] Time: hpet clocksource has been installed.
[ 20.146194] Switched to high resolution mode on CPU 0
[ 20.146834] Switched to high resolution mode on CPU 1
[ 20.154179] system 00:01: ioport range 0x1000-0x107f has been reserved
[ 20.154182] system 00:01: ioport range 0x1080-0x10ff has been reserved
[ 20.154185] system 00:01: ioport range 0x1400-0x147f has been reserved
[ 20.154187] system 00:01: ioport range 0x1480-0x14ff has been reserved
[ 20.154190] system 00:01: ioport range 0x1800-0x187f has been reserved
[ 20.154192] system 00:01: ioport range 0x1880-0x18ff has been reserved
[ 20.154196] system 00:01: iomem range 0xfefe0000-0xfefe01ff has been
reserved
[ 20.154198] system 00:01: iomem range 0xfefe1000-0xfefe10ff has been
reserved
[ 20.154201] system 00:01: iomem range 0x0-0x0 could not be reserved
[ 20.154207] system 00:02: ioport range 0x4d0-0x4d1 has been reserved
[ 20.154209] system 00:02: ioport range 0x800-0x87f has been reserved
[ 20.154212] system 00:02: ioport range 0x295-0x314 has been reserved
[ 20.154214] system 00:02: ioport range 0x290-0x294 has been reserved
[ 20.154225] system 00:0d: iomem range 0xe0000000-0xe7ffffff could not
be reserved
[ 20.154230] system 00:0e: iomem range 0xce200-0xcffff has been reserved
[ 20.154233] system 00:0e: iomem range 0xf0000-0xf7fff could not be
reserved
[ 20.154235] system 00:0e: iomem range 0xf8000-0xfbfff could not be
reserved
[ 20.154238] system 00:0e: iomem range 0xfc000-0xfffff could not be
reserved
[ 20.154241] system 00:0e: iomem range 0x3fff0000-0x3fffffff could not
be reserved
[ 20.154243] system 00:0e: iomem range 0xffff0000-0xffffffff has been
reserved
[ 20.154246] system 00:0e: iomem range 0x0-0x9ffff could not be reserved
[ 20.154249] system 00:0e: iomem range 0x100000-0x3ffeffff could not
be reserved
[ 20.154251] system 00:0e: iomem range 0x0-0x0 could not be reserved
[ 20.154254] system 00:0e: iomem range 0xfec00000-0xfec00fff has been
reserved
[ 20.154257] system 00:0e: iomem range 0xfee00000-0xfee00fff could not
be reserved
[ 20.154602] PCI: Bridge: 0000:00:04.0
[ 20.154603] IO window: disabled.
[ 20.154606] MEM window: e8000000-efffffff
[ 20.154608] PREFETCH window: disabled.
[ 20.154613] PCI: Bridge: 0000:00:09.0
[ 20.154614] IO window: disabled.
[ 20.154616] MEM window: f0000000-f2ffffff
[ 20.154618] PREFETCH window: d0000000-dfffffff
[ 20.154627] PCI: Setting latency timer of device 0000:00:04.0 to 64
[ 20.154637] PCI: Setting latency timer of device 0000:00:09.0 to 64
[ 20.154646] NET: Registered protocol family 2
[ 20.190205] IP route cache hash table entries: 32768 (order: 6,
262144 bytes)
[ 20.190634] TCP established hash table entries: 131072 (order: 9,
2097152 bytes)
[ 20.192120] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 20.192811] TCP: Hash tables configured (established 131072 bind 65536)
[ 20.192814] TCP reno registered
[ 20.202272] checking if image is initramfs... it is
[ 20.747699] Freeing initrd memory: 7553k freed
[ 20.753596] audit: initializing netlink socket (disabled)
[ 20.753608] audit(1223851741.188:1): initialized
[ 20.755312] VFS: Disk quotas dquot_6.5.1
[ 20.755375] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 20.755496] io scheduler noop registered
[ 20.755497] io scheduler anticipatory registered
[ 20.755499] io scheduler deadline registered
[ 20.755584] io scheduler cfq registered (default)
[ 20.755612] pci 0000:00:00.0: Enabling HT MSI Mapping
[ 20.756235] pci 0000:00:04.0: Enabling HT MSI Mapping
[ 20.756253] pci 0000:00:05.0: Enabling HT MSI Mapping
[ 20.756276] pci 0000:00:07.0: Enabling HT MSI Mapping
[ 20.756288] pci 0000:00:08.0: Enabling HT MSI Mapping
[ 20.756300] pci 0000:00:09.0: Enabling HT MSI Mapping
[ 20.756319] Boot video device is 0000:02:00.0
[ 20.756457] PCI: Setting latency timer of device 0000:00:09.0 to 64
[ 20.756476] assign_interrupt_mode Found MSI capability
[ 20.756493] Allocate Port Service[0000:00:09.0:pcie00]
[ 20.779813] Real Time Clock Driver v1.12ac
[ 20.779985] hpet_resources: 0xfeff0000 is busy
[ 20.780019] Linux agpgart interface v0.102
[ 20.780021] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ
sharing enabled
[ 20.780138] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 20.780256] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 20.780689] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 20.780928] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 20.781554] RAMDISK driver initialized: 16 RAM disks of 65536K size
1024 blocksize
[ 20.781611] input: Macintosh mouse button emulation as
/devices/virtual/input/input0
[ 20.782014] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at
0x60,0x64 irq 1,12
[ 20.782376] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 20.782379] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 20.797735] mice: PS/2 mouse device common for all mice
[ 20.797769] cpuidle: using governor ladder
[ 20.797771] cpuidle: using governor menu
[ 20.797917] NET: Registered protocol family 1
[ 20.798007] registered taskstats version 1
[ 20.798116] Magic number: 12:49:856
[ 20.798193] hash matches device ptyv8
[ 20.798202] hash matches device ptysb
[ 20.798248] /build/buildd/linux-2.6.24/drivers/rtc/hctosys.c: unable
to open rtc device (rtc0)
[ 20.798251] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 20.798253] EDD information not available.
[ 20.798260] Freeing unused kernel memory: 320k freed
[ 20.818724] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input1
[ 21.996858] fuse init (API version 7.9)
[ 22.020980] ACPI Exception (processor_core-0822): AE_NOT_FOUND,
Processor Device is not present [20070126]
[ 22.020992] ACPI Exception (processor_core-0822): AE_NOT_FOUND,
Processor Device is not present [20070126]
[ 22.341794] forcedeth: Reverse Engineered nForce ethernet driver.
Version 0.61.
[ 22.342124] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23
[ 22.342134] ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [APCH] -> GSI
23 (level, low) -> IRQ 23
[ 22.342139] PCI: Setting latency timer of device 0000:00:07.0 to 64
[ 22.353240] usbcore: registered new interface driver usbfs
[ 22.353260] usbcore: registered new interface driver hub
[ 22.357759] SCSI subsystem initialized
[ 22.368451] usbcore: registered new device driver usb
[ 22.389109] libata version 3.00 loaded.
[ 22.389177] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller
(OHCI) Driver
[ 22.861533] forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x20 @ 1,
addr 00:1d:7d:2b:a1:df
[ 22.861538] forcedeth 0000:00:07.0: highdma pwrctl mgmt timirq lnktim
msi desc-v3
[ 22.861407] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
[ 22.861416] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI
22 (level, low) -> IRQ 22
[ 22.861613] PCI: Setting latency timer of device 0000:00:02.1 to 64
[ 22.861619] ehci_hcd 0000:00:02.1: EHCI Host Controller
[ 22.861840] ehci_hcd 0000:00:02.1: new USB bus registered, assigned
bus number 1
[ 22.861868] ehci_hcd 0000:00:02.1: debug port 1
[ 22.861871] PCI: cache line size of 64 is not supported by device
0000:00:02.1
[ 22.861880] ehci_hcd 0000:00:02.1: irq 22, io mem 0xf3007000
[ 22.876057] ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[ 22.876171] usb usb1: configuration #1 chosen from 1 choice
[ 22.876193] hub 1-0:1.0: USB hub found
[ 22.876203] hub 1-0:1.0: 8 ports detected
[ 22.976939] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
[ 22.976948] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI
21 (level, low) -> IRQ 21
[ 22.977144] PCI: Setting latency timer of device 0000:00:02.0 to 64
[ 22.977151] ohci_hcd 0000:00:02.0: OHCI Host Controller
[ 22.977209] ohci_hcd 0000:00:02.0: new USB bus registered, assigned
bus number 2
[ 22.977231] ohci_hcd 0000:00:02.0: irq 21, io mem 0xf3006000
[ 23.034559] usb usb2: configuration #1 chosen from 1 choice
[ 23.034579] hub 2-0:1.0: USB hub found
[ 23.034586] hub 2-0:1.0: 8 ports detected
[ 23.136171] PCI: Setting latency timer of device 0000:00:06.0 to 64
[ 23.136513] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20
[ 23.136520] ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSI] -> GSI
20 (level, low) -> IRQ 20
[ 23.136535] PCI: Setting latency timer of device 0000:00:08.0 to 64
[ 23.136541] ACPI: PCI interrupt for device 0000:00:08.0 disabled
[ 23.137114] sata_nv 0000:00:08.0: version 3.5
[ 23.137129] ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSI] -> GSI
20 (level, low) -> IRQ 20
[ 23.137378] PCI: Setting latency timer of device 0000:00:08.0 to 64
[ 23.140354] scsi0 : sata_nv
[ 23.141578] scsi1 : sata_nv
[ 23.141728] ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xe000
irq 20
[ 23.141730] ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xe008
irq 20
[ 23.607493] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 23.637624] ata1.00: ATA-7: WDC WD2500YS-01SHB1, 20.06C06, max UDMA/133
[ 23.637628] ata1.00: 490234752 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 23.644634] ata1.00: configured for UDMA/133
[ 24.111099] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 24.291048] ata2.00: ATAPI: PHILIPS SPD2513P, MP03, max UDMA/100
[ 24.478903] ata2.00: configured for UDMA/100
[ 24.479544] scsi 0:0:0:0: Direct-Access ATA WDC WD2500YS-01S
20.0 PQ: 0 ANSI: 5
[ 24.480677] scsi 1:0:0:0: CD-ROM PHILIPS SPD2513P
MP03 PQ: 0 ANSI: 5
[ 24.480380] pata_amd 0000:00:06.0: version 0.3.10
[ 24.480423] PCI: Setting latency timer of device 0000:00:06.0 to 64
[ 24.480494] scsi2 : pata_amd
[ 24.480653] scsi3 : pata_amd
[ 24.481178] ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000
irq 14
[ 24.481181] ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008
irq 15
[ 24.488476] Driver 'sd' needs updating - please use bus_type methods
[ 24.488559] sd 0:0:0:0: [sda] 490234752 512-byte hardware sectors
(251000 MB)
[ 24.488569] sd 0:0:0:0: [sda] Write Protect is off
[ 24.488572] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 24.488584] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 24.488641] sd 0:0:0:0: [sda] 490234752 512-byte hardware sectors
(251000 MB)
[ 24.488649] sd 0:0:0:0: [sda] Write Protect is off
[ 24.488651] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 24.488663] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 24.488666] sda:<4>Driver 'sr' needs updating - please use bus_type
methods
[ 24.494379] sda1 sda2 < sda5 >
[ 24.519892] sd 0:0:0:0: [sda] Attached SCSI disk
[ 24.523617] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 24.523634] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 24.536043] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw
xa/form2 cdda tray
[ 24.536048] Uniform CD-ROM driver Revision: 3.20
[ 24.536096] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 24.672000] ata3.00: HPA unlocked: 625140335 -> 625142448, native
625142448
[ 24.672006] ata3.00: ATA-8: WDC WD3200AAJB-22WGA0, 00.02C01, max UDMA/100
[ 24.672009] ata3.00: 625142448 sectors, multi 16: LBA48
[ 24.672020] ata3.00: limited to UDMA/33 due to 40-wire cable
[ 24.688486] ata3.00: configured for UDMA/33
[ 24.687988] ata4: port disabled. ignoring.
[ 24.688097] scsi 2:0:0:0: Direct-Access ATA WDC WD3200AAJB-2
00.0 PQ: 0 ANSI: 5
[ 24.688174] sd 2:0:0:0: [sdb] 625142448 512-byte hardware sectors
(320073 MB)
[ 24.688184] sd 2:0:0:0: [sdb] Write Protect is off
[ 24.688186] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 24.688199] sd 2:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 24.688237] sd 2:0:0:0: [sdb] 625142448 512-byte hardware sectors
(320073 MB)
[ 24.688245] sd 2:0:0:0: [sdb] Write Protect is off
[ 24.688247] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 24.688261] sd 2:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 24.688265] sdb: sdb1 < sdb5 > sdb2 sdb3
[ 24.695293] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 24.695332] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 24.941269] Attempting manual resume
[ 24.941272] swsusp: Resume From Partition 8:5
[ 24.941274] PM: Checking swsusp image.
[ 24.941463] PM: Resume from disk failed.
[ 24.978782] kjournald starting. Commit interval 5 seconds
[ 24.979329] EXT3-fs: mounted filesystem with ordered data mode.
[ 32.908419] input: PC Speaker as /devices/platform/pcspkr/input/input2
[ 32.948361] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 32.956455] logips2pp: Detected unknown logitech mouse model 127
[ 32.990746] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 33.143609] input: Power Button (FF) as /devices/virtual/input/input3
[ 33.165180] ACPI: Power Button (FF) [PWRF]
[ 33.165281] input: Power Button (CM) as /devices/virtual/input/input4
[ 33.204904] ACPI: Power Button (CM) [PWRB]
[ 33.205527] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x1c00
[ 33.205543] i2c-adapter i2c-1: nForce2 SMBus adapter at 0xc800
[ 33.417109] input: ImExPS/2 Logitech Explorer Mouse as
/devices/platform/i8042/serio1/input/input5
[ 33.433881] Linux video capture interface: v2.00
[ 33.491016] parport_pc 00:0a: reported by Plug and Play ACPI
[ 33.491063] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 33.617718] cx18: Start initialization, version 1.0.1
[ 33.617784] cx18-0: Initializing card #0
[ 33.617787] cx18-0: Autodetected Hauppauge card
[ 33.618101] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[ 33.618109] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC1] -> GSI
16 (level, low) -> IRQ 16
[ 33.618118] cx18-0: Unreasonably low latency timer, setting to 64
(was 32)
[ 33.619391] cx18-0: cx23418 revision 01010000 (B)
[ 33.801941] tveeprom 2-0050: Huh, no eeprom present (err=-121)?
[ 33.801945] tveeprom 2-0050: Encountered bad packet header [c0].
Corrupt or not a Hauppauge eeprom.
[ 33.801948] cx18-0: Invalid EEPROM
[ 33.801950] cx18-0: VBI is not yet supported
[ 33.987866] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 33.991783] cx18-0: Disabled encoder IDX device
[ 33.991817] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 33.991820] DVB: registering new adapter (cx18)
[ 34.035216] s5h1409_readreg: readreg error (ret == -121)
[ 34.035242] cx18-0: frontend initialization failed
[ 34.035428] cx18-0: DVB failed to register
[ 34.035464] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 34.035481] cx18-0: Registered device video24 for encoder PCM audio
(1 MB)
[ 34.035498] cx18-0: Registered device radio0 for encoder radio
[ 34.035660] cx18-0: Error -12 registering devices
[ 34.037110] cx18-0: Error -12 on initialization
[ 34.037128] cx18: probe of 0000:01:06.0 failed with error -12
[ 34.037190] cx18: End initialization
[ 34.038092] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[ 34.038102] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI
17 (level, low) -> IRQ 17
[ 34.044923] phy0: Selected rate control algorithm 'simple'
[ 34.103360] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 23
[ 34.103365] ACPI: PCI Interrupt 0000:00:05.0[B] -> Link [AAZA] -> GSI
23 (level, low) -> IRQ 23
[ 34.103546] PCI: Setting latency timer of device 0000:00:05.0 to 64
[ 36.071064] lp0: using parport0 (interrupt-driven).
[ 36.149285] Adding 3012148k swap on /dev/sda5. Priority:-1 extents:1
across:3012148k
[ 36.705138] EXT3 FS on sda1, internal journal
[ 36.857284] device-mapper: uevent: version 1.0.3
[ 36.857327] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02)
initialised: dm-devel [at] redhat
[ 37.996244] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 38.355799] No dock devices found.
[ 38.572803] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core
Processor 4200+ processors (2 cpu cores) (version 2.20.00)
[ 38.572386] powernow-k8: 0 : fid 0xe (2200 MHz), vid 0xc
[ 38.572390] powernow-k8: 1 : fid 0xc (2000 MHz), vid 0xe
[ 38.572392] powernow-k8: 2 : fid 0xa (1800 MHz), vid 0x10
[ 38.572394] powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x12
[ 39.393291] ppdev: user-space parallel port driver
[ 39.516162] audit(1223851760.525:2): type=1503
operation="inode_permission" requested_mask="a::" denied_mask="a::"
name="/dev/tty" pid=5239 profile="/usr/sbin/cupsd" namespace="default"
[ 40.158227] eth0: no link during initialization.
[ 40.242351] Bluetooth: Core ver 2.11
[ 40.242788] NET: Registered protocol family 31
[ 40.242792] Bluetooth: HCI device and connection manager initialized
[ 40.242796] Bluetooth: HCI socket layer initialized
[ 40.259725] Bluetooth: L2CAP ver 2.9
[ 40.259731] Bluetooth: L2CAP socket layer initialized
[ 40.316277] Bluetooth: RFCOMM socket layer initialized
[ 40.316292] Bluetooth: RFCOMM TTY layer initialized
[ 40.316294] Bluetooth: RFCOMM ver 1.8
[ 40.910232] Clocksource tsc unstable (delta = -90932944 ns)
[ 48.388253] NET: Registered protocol family 17
[ 48.612397] NET: Registered protocol family 10
[ 48.612633] lo: Disabled Privacy Extensions
[ 48.613032] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 48.613425] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 48.796690] wlan0: Initial auth_alg=0
[ 48.796699] wlan0: authenticate with AP 00:17:3f:f1:1a:2c
[ 48.797384] wlan0: RX authentication from 00:17:3f:f1:1a:2c (alg=0
transaction=2 status=0)
[ 48.797388] wlan0: authenticated
[ 48.797390] wlan0: associate with AP 00:17:3f:f1:1a:2c
[ 48.798655] wlan0: RX AssocResp from 00:17:3f:f1:1a:2c (capab=0x431
status=0 aid=1)
[ 48.798659] wlan0: associated
[ 48.798662] wlan0: switched to short barker preamble
(BSSID=00:17:3f:f1:1a:2c)
[ 48.799557] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 56.835399] wlan0: no IPv6 routers present
daryl [at] daryl-deskto:~$


>
>
> 6. Don't load and unload the cx18 driver too many times in a row without
> being prepared to deal with a kernel oops or hang. There's a memory
> leak in the driver that only happens when a card fails to initialize.
> (Sorry, I know I need to fix it.)
>
>
> 7. Can you test the same card under Windows in the same machine
> (ideally) or a different machine?

I can give you results on a WindowsXP setup on a differant hard drive if
I know what you want me to supply.

>
>
> Regards,
> Andy

Thanks for your dedication.
Daryl

>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at radix

Oct 13, 2008, 2:45 PM

Post #8 of 16 (3431 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

On Sun, 2008-10-12 at 22:05 -0400, daryl wrote:
> Andy Walls wrote:
> > Daryl,
>
> First, I want to apologize for dumping all of this on you. Its such a
> lot that I feel guilty.

No, big deal. This particular problem (PCI mmio access errors to the
CX23418) has dogged me for a few months. I thought I had it fixed for
good with driver version 1.0.1. I guess it'll just be my White
Whale... :)


> > OK, you have obvious PCI bus communications problems. The CX23418 could
> > be the cause or something else in your system could be the cause.
> > Recent experience leads me to believe it's likely the CX23418.


OK. Let's forget the big list of things to do. Your vmalloc
allocations looked fine, so let's do this:


1. Blacklist the cx18 driver if you can, so that it doesn't
automatically load on boot. (On Fedora it means adding an entry
in /etc/modporbe.d/blacklist.)

2. Reboot and execute the following commands:

$ sudo modprobe -r cx18
$ sudo modprobe cx18 debug=67 retry_mmio=1 enc_mpg_buffers=1 enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0

3a. If the driver appears to load OK do this

$ v4l2-ctl -d /dev/video0 --log-status

3b. If it does not load OK, do this

$ sudo modprobe -r cx18


4. Send all output cx18 related out logged to dmesg
(or /var/log/messages)



Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


sofasurferlinux at charter

Oct 14, 2008, 8:20 AM

Post #9 of 16 (3403 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

I have enclosed attachments of dmesg and var/log/messages files.


Andy Walls wrote:
> On Sun, 2008-10-12 at 22:05 -0400, daryl wrote:
>
>> Andy Walls wrote:
>> > Daryl,
>>
>> First, I want to apologize for dumping all of this on you. Its such a
>> lot that I feel guilty.
>>
>
> No, big deal. This particular problem (PCI mmio access errors to the
> CX23418) has dogged me for a few months. I thought I had it fixed for
> good with driver version 1.0.1. I guess it'll just be my White
> Whale... :)
>
>
>
>> > OK, you have obvious PCI bus communications problems. The CX23418 could
>> > be the cause or something else in your system could be the cause.
>> > Recent experience leads me to believe it's likely the CX23418.
>>
>
>
> OK. Let's forget the big list of things to do. Your vmalloc
> allocations looked fine, so let's do this:
>
>
> 1. Blacklist the cx18 driver if you can, so that it doesn't
> automatically load on boot. (On Fedora it means adding an entry
> in /etc/modporbe.d/blacklist.)
>
> 2. Reboot and execute the following commands:
>
> $ sudo modprobe -r cx18
> $ sudo modprobe cx18 debug=67 retry_mmio=1 enc_mpg_buffers=1 enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0
>
> 3a. If the driver appears to load OK do this
>
> $ v4l2-ctl -d /dev/video0 --log-status
>
> 3b. If it does not load OK, do this
>
> $ sudo modprobe -r cx18
>
>
> 4. Send all output cx18 related out logged to dmesg
> (or /var/log/messages)
>
>
>
> Regards,
> Andy
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
Attachments: var-log-messages-1.tar.gz (26.2 KB)
  entire-var-log-messages.tar.gz (96.1 KB)
  greped dmesg.tar.gz (1.91 KB)
  entire-dmesg.tar.gz (8.17 KB)


sofasurferlinux at charter

Oct 15, 2008, 8:34 AM

Post #10 of 16 (3378 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

Andy.
I just realized that my responses to some of your requests were not
included in my last letter.

I did include my log messages, etc but I did not mention that..

1. I did blacklist the cx18 driver byI editing /etc/modprobe.d/blacklist
and adding "blacklist cx18" to the bottom of the file.

2. I ran
$ sudo modprobe -r cx18
$ sudo modprobe cx18 debug=67 retry_mmio=1 enc_mpg_buffers=1
enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0

3. The driver did not load ok so I ran...
$ sudo modprobe -r cx18

4. I then sent you the output messages.

Sorry for the delay.




daryl wrote:
> I have enclosed attachments of dmesg and var/log/messages files.
>
>
> Andy Walls wrote:
>> On Sun, 2008-10-12 at 22:05 -0400, daryl wrote:
>>
>>> Andy Walls wrote:
>>> > Daryl,
>>>
>>> First, I want to apologize for dumping all of this on you. Its such
>>> a lot that I feel guilty.
>>>
>>
>> No, big deal. This particular problem (PCI mmio access errors to the
>> CX23418) has dogged me for a few months. I thought I had it fixed for
>> good with driver version 1.0.1. I guess it'll just be my White
>> Whale... :)
>>
>>
>>
>>> > OK, you have obvious PCI bus communications problems. The
>>> CX23418 could
>>> > be the cause or something else in your system could be the cause.
>>> > Recent experience leads me to believe it's likely the CX23418.
>>>
>>
>>
>> OK. Let's forget the big list of things to do. Your vmalloc
>> allocations looked fine, so let's do this:
>>
>>
>> 1. Blacklist the cx18 driver if you can, so that it doesn't
>> automatically load on boot. (On Fedora it means adding an entry
>> in /etc/modporbe.d/blacklist.)
>>
>> 2. Reboot and execute the following commands:
>>
>> $ sudo modprobe -r cx18
>> $ sudo modprobe cx18 debug=67 retry_mmio=1 enc_mpg_buffers=1
>> enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0
>>
>> 3a. If the driver appears to load OK do this
>>
>> $ v4l2-ctl -d /dev/video0 --log-status
>>
>> 3b. If it does not load OK, do this
>>
>> $ sudo modprobe -r cx18
>>
>>
>> 4. Send all output cx18 related out logged to dmesg
>> (or /var/log/messages)
>>
>>
>>
>> Regards,
>> Andy
>>
>>
>> _______________________________________________
>> ivtv-users mailing list
>> ivtv-users [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>
>>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at radix

Oct 15, 2008, 7:43 PM

Post #11 of 16 (3383 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

On Wed, 2008-10-15 at 11:34 -0400, daryl wrote:
> Andy.
> I just realized that my responses to some of your requests were not
> included in my last letter.
>
> I did include my log messages, etc but I did not mention that..
>
> 1. I did blacklist the cx18 driver byI editing /etc/modprobe.d/blacklist
> and adding "blacklist cx18" to the bottom of the file.
>
> 2. I ran
> $ sudo modprobe -r cx18
> $ sudo modprobe cx18 debug=67 retry_mmio=1 enc_mpg_buffers=1
> enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0
>
> 3. The driver did not load ok so I ran...
> $ sudo modprobe -r cx18
>
> 4. I then sent you the output messages.
>
> Sorry for the delay.

Well, I've been busy just trying to keep up with the trouble cx18
reports (plus my real life work, family, home,.etc.) so delays don't
bug me. In fact I didn't even notice. :)

Anyway, here's what I was looking for:

Oct 13 21:31:01 daryl-desktop kernel: [ 138.852294] cx18: Start initialization, version 1.0.1
[snip]
Oct 13 21:31:01 daryl-desktop kernel: [ 138.899506] cx18-0 info: GPIO initial dir: 0000ffff/0000ffff out: 00000000/00000000

Likely PCI bus read errors (PCI bus read errors return 0xffffffff)

Oct 13 21:31:01 daryl-desktop kernel: [ 138.899525] cx18-0 info: activating i2c...
Oct 13 21:31:01 daryl-desktop kernel: [ 138.899528] cx18-0 i2c: i2c init
Oct 13 21:31:01 daryl-desktop kernel: [ 138.936302] cx18-0 info: Active card count: 1.
Oct 13 21:31:01 daryl-desktop kernel: [ 138.936866] tveeprom 2-0050: Huh, no eeprom present (err=-121)?
Oct 13 21:31:01 daryl-desktop kernel: [ 138.936870] tveeprom 2-0050: Encountered bad packet header [c0]. Corrupt or not a Hauppauge eeprom.

Likely more PCI bus errors

[snip]
Oct 13 21:31:01 daryl-desktop kernel: [ 138.989744] cx18-0 info: Allocate encoder MPEG stream: 32 x 32768 buffers (1024kB total)
Oct 13 21:31:01 daryl-desktop kernel: [ 138.989924] cx18-0: Disabled TS device
Oct 13 21:31:01 daryl-desktop kernel: [ 138.989927] cx18-0: Disabled encoder YUV device
Oct 13 21:31:01 daryl-desktop kernel: [ 138.989928] cx18-0: Disabled encoder PCM audio device
Oct 13 21:31:01 daryl-desktop kernel: [ 138.989930] cx18-0: Disabled encoder IDX device
Oct 13 21:31:01 daryl-desktop kernel: [ 138.990263] cx18-0: Registered device video0 for encoder MPEG (1 MB)

Using as little memory as possible. OK.

Oct 13 21:31:01 daryl-desktop kernel: [ 138.990382] DVB: registering new adapter (cx18)
Oct 13 21:31:01 daryl-desktop kernel: [ 139.000221] cx18-0: Unexpected mailbox command ffffffff
Oct 13 21:31:01 daryl-desktop kernel: [ 139.000227] cx18-0: Unexpected interrupt ffffffff
Oct 13 21:31:01 daryl-desktop kernel: [ 139.017268] s5h1409_readreg: readreg error (ret == -121)

Likely yet more PCI bus errors.



Oct 13 21:31:01 daryl-desktop kernel: [ 139.017472] cx18-0: Registered device radio0 for encoder radio
Oct 13 21:31:01 daryl-desktop kernel: [ 139.017542] cx18-0 i2c: i2c exit
Oct 13 21:31:01 daryl-desktop kernel: [ 139.017606] cx18-0 info: releasing enc_mem
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018934] cx18-0 info: retried_write[0] = 281
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018935] cx18-0 info: retried_write[1] = 16933
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018938] cx18-0 info: retried_write[2] = 96
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018939] cx18-0 info: retried_write[3] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018940] cx18-0 info: retried_write[4] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018942] cx18-0 info: retried_write[5] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018943] cx18-0 info: retried_write[6] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018944] cx18-0 info: retried_write[7] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018945] cx18-0 info: retried_write[8] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018947] cx18-0 info: retried_write[9] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018948] cx18-0 info: retried_write[10] = 264
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018950] cx18-0 info: retried_read[0] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018951] cx18-0 info: retried_read[1] = 1226
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018953] cx18-0 info: retried_read[2] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018955] cx18-0 info: retried_read[3] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018956] cx18-0 info: retried_read[4] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018958] cx18-0 info: retried_read[5] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018959] cx18-0 info: retried_read[6] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018961] cx18-0 info: retried_read[7] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018962] cx18-0 info: retried_read[8] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018964] cx18-0 info: retried_read[9] = 0
Oct 13 21:31:02 daryl-desktop kernel: [ 139.018965] cx18-0 info: retried_read[10] = 1233

OK. These are really odd histograms for PCI MMIO access retires to the
CX23418. Every read PCI mmio read of the CX23418 fails on the first try
(retried_read[0] = 0), and over half of the read accesses completely
fail (retried_read[10] = 1233). Since the retried writes are done based
on being able to read things back properly over the PCI bus, they're
like being skewed by the high rate of PCI bus read errors when accessing
the CX23418.

That's really atypical compared to the three machines and cards I have.
The problem can't be all the CX23418. I would expect the number of
completely failed reads to only be around 400 after initialization.

There's something about your PCI bus that's causing problems, but at the
moment I can't see what.



Oct 13 21:31:02 daryl-desktop kernel: [ 139.018984] cx18: probe of 0000:01:06.0 failed with error -12
Oct 13 21:31:02 daryl-desktop kernel: [ 139.019001] cx18: End initialization

-12 is -ENOMEM. That's even after the cx18 asks for a low amount of
memory for buffers. I checked the driver and found that when DVB
registration doesn't succeed, the driver can gripe -ENOMEM even if
memory wasn't the problem. So you may not have a memory problem.



So there's not much specific advice I can give at this point. Only some
general advice:

1. You can try loading the module also specifying the mmio_ndelay
parameter. It may not help (actually it shouldn't), but it's easy
enough to try:

$ sudo modprobe -r cx18
$ sudo modprobe cx18 debug=67 retry_mmio=1 mmio_ndelay=243 enc_mpg_buffers=1 enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0


2. If that doesn't help with the PCI MMIO read errors, then you need to
start experimenting to find out what on the PCI bus is causing all the
read errors: a particular card, device driver, or latency timer on a
bridge are the things I would check. I might also try to disable
message signaled interrupts, if that's feasible.

Alternatively, can you try the card in another system and see if you get
the same sort of behavior?


3. If you can resolve the PCI bus read errors, and the DVB frontend
appears to register, and you still get -ENOMEM being returned, only then
concentrate on trying to free up memory.


Regards,
Andy


> daryl wrote:
> > I have enclosed attachments of dmesg and var/log/messages files.
> >
> >
> > Andy Walls wrote:
> >> On Sun, 2008-10-12 at 22:05 -0400, daryl wrote:
> >>
> >>> Andy Walls wrote:
> >>> > Daryl,
> >>>
> >>> First, I want to apologize for dumping all of this on you. Its such
> >>> a lot that I feel guilty.
> >>>
> >>
> >> No, big deal. This particular problem (PCI mmio access errors to the
> >> CX23418) has dogged me for a few months. I thought I had it fixed for
> >> good with driver version 1.0.1. I guess it'll just be my White
> >> Whale... :)
> >>
> >>
> >>
> >>> > OK, you have obvious PCI bus communications problems. The
> >>> CX23418 could
> >>> > be the cause or something else in your system could be the cause.
> >>> > Recent experience leads me to believe it's likely the CX23418.
> >>>
> >>
> >>
> >> OK. Let's forget the big list of things to do. Your vmalloc
> >> allocations looked fine, so let's do this:
> >>
> >>
> >> 1. Blacklist the cx18 driver if you can, so that it doesn't
> >> automatically load on boot. (On Fedora it means adding an entry
> >> in /etc/modporbe.d/blacklist.)
> >>
> >> 2. Reboot and execute the following commands:
> >>
> >> $ sudo modprobe -r cx18
> >> $ sudo modprobe cx18 debug=67 retry_mmio=1 enc_mpg_buffers=1
> >> enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0
> >>
> >> 3a. If the driver appears to load OK do this
> >>
> >> $ v4l2-ctl -d /dev/video0 --log-status
> >>
> >> 3b. If it does not load OK, do this
> >>
> >> $ sudo modprobe -r cx18
> >>
> >>
> >> 4. Send all output cx18 related out logged to dmesg
> >> (or /var/log/messages)
> >>
> >>
> >>
> >> Regards,
> >> Andy
> >>
> >>
> >> _______________________________________________
> >> ivtv-users mailing list
> >> ivtv-users [at] ivtvdriver
> >> http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >>
> >>
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > ivtv-users mailing list
> > ivtv-users [at] ivtvdriver
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


sofasurferlinux at charter

Oct 15, 2008, 9:23 PM

Post #12 of 16 (3379 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

Thanks for your attempt to help me. I have just one more question at
this time...

I had loaded the cx18 driver twice before and dmesg did show that the
card was recognized. In fact, I actually did have video at one time. But
after making a mess out of my system I reinstalled everything and have
not been able to get the card recognized since.

So now after the information you gave me about pci buses, I tend to
believe that I have a hardware issue or something related to packages.
It now seems obvious to me that I did something to change my system that
is causing the problem. Does this sound reasonable to you?

My problem is that I can not remember what changes I may have made to my
system.

Here is a list of possible changes that I wonder about. Please tell me
if any of these may be related to my problem.

I. Could the problem be related to using a differant kernel than I
originally used?

2. Could it be that originally I used the live cd installation and now I
am using the alternate cd installation?

3. Could it be related to installing a second hard drive on my system
and at differant times I have it enabled or disabled?

4. Anything else you may be able to think of that I may have done
differantly?

Thanks a million for your time,
Daryl

Andy Walls wrote:
>
>
>
>
> So there's not much specific advice I can give at this point. Only some
> general advice:
>
> 1. You can try loading the module also specifying the mmio_ndelay
> parameter. It may not help (actually it shouldn't), but it's easy
> enough to try:
>
> $ sudo modprobe -r cx18
> $ sudo modprobe cx18 debug=67 retry_mmio=1 mmio_ndelay=243 enc_mpg_buffers=1 enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0
>
>
> 2. If that doesn't help with the PCI MMIO read errors, then you need to
> start experimenting to find out what on the PCI bus is causing all the
> read errors: a particular card, device driver, or latency timer on a
> bridge are the things I would check. I might also try to disable
> message signaled interrupts, if that's feasible.
>
> Alternatively, can you try the card in another system and see if you get
> the same sort of behavior?
>
>
> 3. If you can resolve the PCI bus read errors, and the DVB frontend
> appears to register, and you still get -ENOMEM being returned, only then
> concentrate on trying to free up memory.
>
>
> Regards,
> Andy
>
>
>


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at radix

Oct 16, 2008, 3:54 PM

Post #13 of 16 (3355 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

On Thu, 2008-10-16 at 00:23 -0400, daryl wrote:
> Thanks for your attempt to help me. I have just one more question at
> this time...
>
> I had loaded the cx18 driver twice before and dmesg did show that the
> card was recognized. In fact, I actually did have video at one time. But
> after making a mess out of my system I reinstalled everything and have
> not been able to get the card recognized since.
>
> So now after the information you gave me about pci buses, I tend to
> believe that I have a hardware issue or something related to packages.
> It now seems obvious to me that I did something to change my system that
> is causing the problem. Does this sound reasonable to you?

Sure. The card is functioning - it's just that comms to the card are
suffering a high error rate. The CX23418 itself is a contributor to the
error rate, but your error rate is too high to be the CX23418 alone.

Another device on the PCI bus or another driver can be causing the
problem.

> My problem is that I can not remember what changes I may have made to my
> system.
>
> Here is a list of possible changes that I wonder about. Please tell me
> if any of these may be related to my problem.
>
> I. Could the problem be related to using a differant kernel than I
> originally used?
>
> 2. Could it be that originally I used the live cd installation and now I
> am using the alternate cd installation?

For both of these: well they could - the set of differences could be
huge. Given that every device on the bus has a kernel device driver of
some sort and that some system level hardware gets manipulated by the
kernel too.

I cannot assign a likelyhood to this being the case however.


> 3. Could it be related to installing a second hard drive on my system
> and at differant times I have it enabled or disabled?

Accesses to the hard drive go over the PCI bus between the CPU and the
disk controller. An increase in disk activity could cause the problem.
If the disk is relatively inactive, then I'd say it doesn't matter.


> 4. Anything else you may be able to think of that I may have done
> differantly?

On my short list would be checking the following, since they are
relatively easy:

1. the PCI latency timers on the bridges the CX23418 is behind and
setting them a little longer with setpci.

2. Any device and device driver that generates *a lot* of interrupts
according to /proc/interrupts. Blacklist/remove the driver module or
remove the device from the machine to check.

3. The power supply. A fully loaded system or maybe adding an extra
hard drive could cause enough load on the power that things near the
margin start not working properly. Check by removing non-essential PCI
cards and disk drives.

4. Dust or dirty contacts in the PCI slot that the CX23418 based card is
in. Remove card, blow dust out of slot, reinstall, and retest.

5. Unhooking the antenna cables and video cables from the card. To
eliminate any possible grounding problem.


With all these tests you want to look at the read/write retry stats from
the CX23418 driver to see if you've had a positive effect. Here's a
typical set from my system after init and the Mythbackend occasionally
pulling EPG info from the ATSC broadcast:

cx18-0 info: retried_write[0] = 4550379
cx18-0 info: retried_write[1] = 127
cx18-0 info: retried_write[2] = 76
cx18-0 info: retried_write[3] = 48
cx18-0 info: retried_write[4] = 59
cx18-0 info: retried_write[5] = 59
cx18-0 info: retried_write[6] = 41
cx18-0 info: retried_write[7] = 44
cx18-0 info: retried_write[8] = 34
cx18-0 info: retried_write[9] = 42
cx18-0 info: retried_write[10] = 1257915
cx18-0 info: retried_read[0] = 14124353
cx18-0 info: retried_read[1] = 0
cx18-0 info: retried_read[2] = 0
cx18-0 info: retried_read[3] = 0
cx18-0 info: retried_read[4] = 0
cx18-0 info: retried_read[5] = 0
cx18-0 info: retried_read[6] = 0
cx18-0 info: retried_read[7] = 0
cx18-0 info: retried_read[8] = 0
cx18-0 info: retried_read[9] = 0
cx18-0 info: retried_read[10] = 472

Just after driver/card init, a large deviation from this distribution of
retries would indicate you still have a problem.


And of course you can always try reverting to a previously known good
configuration where things worked, whenever you want to invest that
amount of time.

Regards,
Andy


> Thanks a million for your time,
> Daryl
>
> Andy Walls wrote:
> >
> >
> >
> >
> > So there's not much specific advice I can give at this point. Only some
> > general advice:
> >
> > 1. You can try loading the module also specifying the mmio_ndelay
> > parameter. It may not help (actually it shouldn't), but it's easy
> > enough to try:
> >
> > $ sudo modprobe -r cx18
> > $ sudo modprobe cx18 debug=67 retry_mmio=1 mmio_ndelay=243 enc_mpg_buffers=1 enc_ts_buffers=0 enc_vbi_buffers=0 enc_yuv_buffers=0 enc_pcm_buffers=0
> >
> >
> > 2. If that doesn't help with the PCI MMIO read errors, then you need to
> > start experimenting to find out what on the PCI bus is causing all the
> > read errors: a particular card, device driver, or latency timer on a
> > bridge are the things I would check. I might also try to disable
> > message signaled interrupts, if that's feasible.
> >
> > Alternatively, can you try the card in another system and see if you get
> > the same sort of behavior?
> >
> >
> > 3. If you can resolve the PCI bus read errors, and the DVB frontend
> > appears to register, and you still get -ENOMEM being returned, only then
> > concentrate on trying to free up memory.
> >
> >
> > Regards,
> > Andy
> >
> >
> >
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


sofasurferlinux at charter

Oct 17, 2008, 10:13 AM

Post #14 of 16 (3346 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

Andy.
My card is now properly detected!!
Does this dmesg output look better to you?

daryl [at] ubunt:~$ dmesg | grep cx18
[ 40.984424] cx18: Start initialization, version 1.0.1
[ 41.007731] cx18-0: Initializing card #0
[ 41.007735] cx18-0: Autodetected Hauppauge card
[ 41.008058] cx18-0: Unreasonably low latency timer, setting to 64
(was 32)
[ 41.009308] cx18-0: cx23418 revision 01010000 (B)
[ 41.229379] cx18-0: Autodetected Hauppauge HVR-1600
[ 41.229380] cx18-0: VBI is not yet supported
[ 41.310921] tuner 3-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
[ 41.310943] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[ 41.357354] cx18-0: Disabled encoder IDX device
[ 41.357400] cx18-0: Registered device video0 for encoder MPEG (2 MB)
[ 41.357403] DVB: registering new adapter (cx18)
[ 41.426775] cx18-0: DVB Frontend registered
[ 41.426805] cx18-0: Registered device video32 for encoder YUV (2 MB)
[ 41.426858] cx18-0: Registered device video24 for encoder PCM audio
(1 MB)
[ 41.426861] cx18-0: Initialized card #0: Hauppauge HVR-1600
[ 41.481627] cx18: End initialization
[ 46.008139] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000
(141200 bytes)
[ 46.513344] cx18-0: loaded v4l-cx23418-cpu.fw firmware (174716 bytes)
[ 46.518491] cx18-0: FW version: 0.0.71.0 (Release 2006/12/29)
[ 47.401321] cx18-0: loaded v4l-cx23418-dig.fw firmware (16382 bytes)


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


awalls at radix

Oct 17, 2008, 1:57 PM

Post #15 of 16 (3341 views)
Permalink
Re: Insertion erros when installing cx18 [In reply to]

On Fri, 2008-10-17 at 13:13 -0400, daryl wrote:
> Andy.
> My card is now properly detected!!
> Does this dmesg output look better to you?
>
> daryl [at] ubunt:~$ dmesg | grep cx18
> [ 40.984424] cx18: Start initialization, version 1.0.1
> [ 41.007731] cx18-0: Initializing card #0
> [ 41.007735] cx18-0: Autodetected Hauppauge card
> [ 41.008058] cx18-0: Unreasonably low latency timer, setting to 64
> (was 32)
> [ 41.009308] cx18-0: cx23418 revision 01010000 (B)
> [ 41.229379] cx18-0: Autodetected Hauppauge HVR-1600
> [ 41.229380] cx18-0: VBI is not yet supported
> [ 41.310921] tuner 3-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
> [ 41.310943] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
> [ 41.357354] cx18-0: Disabled encoder IDX device
> [ 41.357400] cx18-0: Registered device video0 for encoder MPEG (2 MB)
> [ 41.357403] DVB: registering new adapter (cx18)
> [ 41.426775] cx18-0: DVB Frontend registered
> [ 41.426805] cx18-0: Registered device video32 for encoder YUV (2 MB)
> [ 41.426858] cx18-0: Registered device video24 for encoder PCM audio
> (1 MB)
> [ 41.426861] cx18-0: Initialized card #0: Hauppauge HVR-1600
> [ 41.481627] cx18: End initialization
> [ 46.008139] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000
> (141200 bytes)
> [ 46.513344] cx18-0: loaded v4l-cx23418-cpu.fw firmware (174716 bytes)
> [ 46.518491] cx18-0: FW version: 0.0.71.0 (Release 2006/12/29)
> [ 47.401321] cx18-0: loaded v4l-cx23418-dig.fw firmware (16382 bytes)

Yup. Everything looks copacetic. Do you mind sharing on what
corrective action you took?


BTW, when testing, please don't be surprised by the following
annoyances:

1. The first analog capture after a modprobe will have messed up
audio/video timestamps or no audio at all, so playback will be like a
"fast forward" or have no sound at all. Every subsequent analog capture
will be fine.

2. Unbuffered playback will not be smooth. If you use mplayer, make
sure you use the -cache 16384 command line option to get buffered
playback.

3. During simultaneous digital and audio capture one of the streams may
halt (with MythTV at least). Reason unknown as of yet.


Regards,
Andy



_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users


sofasurferlinux at charter

Oct 18, 2008, 8:04 PM

Post #16 of 16 (3284 views)
Permalink
Insertion erros when installing cx18 [In reply to]

I don't want to tell you how I solved my problem (but I will) because I wasted so much of my time and your time that I fully expect to be called names
for being so dumb (just kidding).

The solution was something I learned years ago when I had dial-up modem troubles. Just remove the card and reinstall the system and THEN put the card back in.
Well, thats the sure fire method. I don't know the details yet but heres what I did...

I shut down, removed the tuner card, wiped my drive, reinstalled Ubuntu to previous state, reinserted tuner card into motherboard and then loaded v4l
driver and firmware.

I don't fully understand this because of this...

I then reinstall my OS on my other hard drive. I then loaded the v4l drivers and firmware and figured that if my dmesg cx18 output was bad I would try
removing and reinstalling the card. This would tell me if reinstalling the OS was nessessary or if it was only nessessary to remove
the card, restart the system, shut down and reinstall the card. HOWEVER, this time it was not nessessary to remove the card. I simply reinstalled the OS
and dmesg cx18 was good.

Anyway, the jist of it is that for error 12 and mmio_ndelay issues I recommend the above actions.

I have now run the "mplayer -cache 16384 /dev/video0" command and I do have video and sound.

I am now going to attempt to get Myth going. Probably see you in another thread real soon.

Thanks for all.



On Fri, 2008-10-17 at 13:13 -0400, daryl wrote:

> >/ Andy.
>
/>/ My card is now properly detected!!
/>/ Does this dmesg output look better to you?
/>/
/>/ daryl at ubuntu <http://ivtvdriver.org/mailman/listinfo/ivtv-users>:~$ dmesg | grep cx18
/>/ [ 40.984424] cx18: Start initialization, version 1.0.1
/>/ [ 41.007731] cx18-0: Initializing card #0
/>/ [ 41.007735] cx18-0: Autodetected Hauppauge card
/>/ [ 41.008058] cx18-0: Unreasonably low latency timer, setting to 64
/>/ (was 32)
/>/ [ 41.009308] cx18-0: cx23418 revision 01010000 (B)
/>/ [ 41.229379] cx18-0: Autodetected Hauppauge HVR-1600
/>/ [ 41.229380] cx18-0: VBI is not yet supported
/>/ [ 41.310921] tuner 3-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
/>/ [ 41.310943] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
/>/ [ 41.357354] cx18-0: Disabled encoder IDX device
/>/ [ 41.357400] cx18-0: Registered device video0 for encoder MPEG (2 MB)
/>/ [ 41.357403] DVB: registering new adapter (cx18)
/>/ [ 41.426775] cx18-0: DVB Frontend registered
/>/ [ 41.426805] cx18-0: Registered device video32 for encoder YUV (2 MB)
/>/ [ 41.426858] cx18-0: Registered device video24 for encoder PCM audio
/>/ (1 MB)
/>/ [ 41.426861] cx18-0: Initialized card #0: Hauppauge HVR-1600
/>/ [ 41.481627] cx18: End initialization
/>/ [ 46.008139] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000
/>/ (141200 bytes)
/>/ [ 46.513344] cx18-0: loaded v4l-cx23418-cpu.fw firmware (174716 bytes)
/>/ [ 46.518491] cx18-0: FW version: 0.0.71.0 (Release 2006/12/29)
/>/ [ 47.401321] cx18-0: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
/

> > Yup. Everything looks copacetic. Do you mind sharing on what
> > corrective action you took?
>



_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

ivtv users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.