Andy Walls wrote: > OK. Just so we don't wind up chasing ghosts, I need some > clarification: > > 1. Prior to every attempt to use a different mmio_ndelay value, did you > use 'modprobe -r cx18' to unload the module first? > This time around I did... sudo modprobe -r cx18 sudo modprobe cx18 mmio_ndelay=31 and sudo modprobe -r cx18 sudo modprobe cx18 mmio_ndelay=61
I also did the other numbers, earlier, but the results were the same as "31". So I am including the following "dmesg | grep cx18" results for "31" and "61". "61" gave a result that is noticably differant, although still not good. Here is the result... [EMAIL PROTECTED]:~$ dmesg | grep cx18 [ 35.922705] cx18: Start initialization, version 1.0.0 [ 35.922764] cx18-0: Initializing card #0 [ 35.922767] cx18-0: Autodetected Hauppauge card [ 35.923104] cx18-0: Unreasonably low latency timer, setting to 64 (was 32) [ 35.924286] cx18-0: cx23418 revision ffffffff (A) [ 36.088456] cx18-0: Invalid EEPROM [ 36.088459] cx18-0: VBI is not yet supported [ 36.300927] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 36.302875] cx18-0: Disabled encoder IDX device [ 36.302905] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 36.302908] DVB: registering new adapter (cx18) [ 36.400626] cx18-0: frontend initialization failed [ 36.400761] cx18-0: DVB failed to register [ 36.400789] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 36.400804] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 36.400818] cx18-0: Registered device radio0 for encoder radio [ 36.400962] cx18-0: Error -12 registering devices [ 36.402375] cx18-0: Error -12 on initialization [ 36.402392] cx18: probe of 0000:01:06.0 failed with error -12 [ 36.402427] cx18: End initialization [ 144.489776] cx18: Start initialization, version 1.0.0 [ 144.489823] cx18-0: Initializing card #0 [ 144.489826] cx18-0: Autodetected Hauppauge card [ 144.491003] cx18-0: cx23418 revision 01010000 (B) [ 144.563286] cx18-0: Invalid EEPROM [ 144.563288] cx18-0: VBI is not yet supported [ 144.608599] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 144.609967] cx18-0: Disabled encoder IDX device [ 144.610110] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 144.610223] DVB: registering new adapter (cx18) [ 144.610930] cx18-0: frontend initialization failed [ 144.611415] cx18-0: DVB failed to register [ 144.611530] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 144.611652] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 144.611777] cx18-0: Registered device radio0 for encoder radio [ 144.612028] cx18-0: Error -12 registering devices [ 144.613409] cx18-0: Error -12 on initialization [ 144.613585] cx18: probe of 0000:01:06.0 failed with error -12 [ 144.613752] cx18: End initialization [ 158.821794] cx18: Start initialization, version 1.0.0 [ 158.821848] cx18-0: Initializing card #0 [ 158.821851] cx18-0: Autodetected Hauppauge card [ 158.823041] cx18-0: cx23418 revision ffffffff (A) [ 158.895451] cx18-0: Invalid EEPROM [ 158.895452] cx18-0: VBI is not yet supported [ 158.940120] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 158.947411] cx18-0: Disabled encoder IDX device [ 158.947608] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 158.947724] DVB: registering new adapter (cx18) [ 158.948485] cx18-0: frontend initialization failed [ 158.951440] cx18-0: DVB failed to register [ 158.951623] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 158.951758] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 158.951892] cx18-0: Registered device radio0 for encoder radio [ 158.952235] cx18-0: Error -12 registering devices [ 158.953794] cx18-0: Error -12 on initialization [ 158.956328] cx18: probe of 0000:01:06.0 failed with error -12 [ 158.956566] cx18: End initialization [ 158.960974] [<ffffffff8826d355>] :cx18:cx18_setup_page+0x25/0x90 [ 158.960995] Modules linked in: cx18 dvb_core compat_ioctl32 i2c_algo_bit cx2341x tveeprom ipv6 aes_generic aes_x86_64 af_packet rfcomm l2cap bluetooth ppdev powernow_k8 cpufreq_userspace cpufreq_conservative cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table video output sbs container sbshc dock battery iptable_filter ip_tables x_tables ac lp loop snd_hda_intel snd_pcm_oss snd_mixer_oss arc4 snd_pcm ecb blkcipher snd_page_alloc snd_hwdep snd_seq_dummy s5h1409 snd_seq_oss snd_seq_midi cs5345 tuner snd_rawmidi rt61pci rt2x00pci rt2x00lib snd_seq_midi_event rfkill snd_seq input_polldev crc_itu_t snd_timer mac80211 videodev v4l1_compat snd_seq_device v4l2_common cfg80211 snd eeprom_93cx6 serio_raw button i2c_nforce2 parport_pc parport k8temp psmouse evdev soundcore i2c_core shpchp pci_hotplug pcspkr ext3 jbd mbcache sr_mod cdrom sg sd_mod sata_nv pata_amd ata_generic pata_acpi libata scsi_mod forcedeth ehci_hcd ohci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse [ 158.961044] RIP: 0010:[<ffffffff8826d355>] [<ffffffff8826d355>] :cx18:cx18_setup_page+0x25/0x90 [ 158.961094] [<ffffffff88262283>] :cx18:cx18_firmware_init+0x253/0x790 [ 158.961116] [<ffffffff8825f3cb>] :cx18:cx18_init_on_first_open+0x6b/0x180 [ 158.961137] [<ffffffff88264573>] :cx18:cx18_v4l2_open+0xa3/0x230 [ 158.961203] RIP [<ffffffff8826d355>] :cx18:cx18_setup_page+0x25/0x90 > 2. Make sure that '/sbin/modinfo cx18' show mmio_ndelay as a valid > module parameter (is it in the list?). > I can not access the file "/sbin/modinfo cx18" as this file does not exist. I have "/sbin/modinfo" but it is an executable. > 3. Did modprobe gripe about failures to load (it looks like you're short > on chunks of vmalloc address space)? > > 4. grepping on cx18 may hide some valuable troubleshooting information. > If providing subsequent reports, do your best to provide all the > messages between "Start initialization" and "End initialization" and > lines outside of that that look wrong. > > Here is the results of "dmesg cx18"... 35.922705] cx18: Start initialization, version 1.0.0 [ 35.922764] cx18-0: Initializing card #0 [ 35.922767] cx18-0: Autodetected Hauppauge card [ 35.923088] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 [ 35.923094] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 16 [ 35.923104] cx18-0: Unreasonably low latency timer, setting to 64 (was 32) [ 35.924286] cx18-0: cx23418 revision ffffffff (A) [ 35.945157] parport_pc 00:0a: reported by Plug and Play ACPI [ 35.945202] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [ 36.088450] tveeprom 2-0050: Huh, no eeprom present (err=-121)? [ 36.088454] tveeprom 2-0050: Encountered bad packet header [c0]. Corrupt or not a Hauppauge eeprom. [ 36.088456] cx18-0: Invalid EEPROM [ 36.088459] cx18-0: VBI is not yet supported [ 36.300927] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 36.302875] cx18-0: Disabled encoder IDX device [ 36.302905] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 36.302908] DVB: registering new adapter (cx18) [ 36.400600] s5h1409_readreg: readreg error (ret == -121) [ 36.400626] cx18-0: frontend initialization failed [ 36.400761] cx18-0: DVB failed to register [ 36.400789] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 36.400804] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 36.400818] cx18-0: Registered device radio0 for encoder radio [ 36.400962] cx18-0: Error -12 registering devices [ 36.402375] cx18-0: Error -12 on initialization [ 36.402392] cx18: probe of 0000:01:06.0 failed with error -12 [ 36.402427] cx18: End initialization 144.489776] cx18: Start initialization, version 1.0.0 [ 144.489823] cx18-0: Initializing card #0 [ 144.489826] cx18-0: Autodetected Hauppauge card [ 144.491003] cx18-0: cx23418 revision 01010000 (B) [ 144.563277] tveeprom 2-0050: Huh, no eeprom present (err=-121)? [ 144.563283] tveeprom 2-0050: Encountered bad packet header [c0]. Corrupt or not a Hauppauge eeprom. [ 144.563286] cx18-0: Invalid EEPROM [ 144.563288] cx18-0: VBI is not yet supported [ 144.608599] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 144.609967] cx18-0: Disabled encoder IDX device [ 144.610110] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 144.610223] DVB: registering new adapter (cx18) [ 144.610899] s5h1409_readreg: readreg error (ret == -121) [ 144.610930] cx18-0: frontend initialization failed [ 144.611415] cx18-0: DVB failed to register [ 144.611530] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 144.611652] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 144.611777] cx18-0: Registered device radio0 for encoder radio [ 144.612028] cx18-0: Error -12 registering devices [ 144.613409] cx18-0: Error -12 on initialization [ 144.613585] cx18: probe of 0000:01:06.0 failed with error -12 [ 144.613752] cx18: End initialization [ 158.821794] cx18: Start initialization, version 1.0.0 [ 158.821848] cx18-0: Initializing card #0 [ 158.821851] cx18-0: Autodetected Hauppauge card [ 158.823041] cx18-0: cx23418 revision ffffffff (A) [ 158.895445] tveeprom 2-0050: Huh, no eeprom present (err=-121)? [ 158.895448] tveeprom 2-0050: Encountered bad packet header [c0]. Corrupt or not a Hauppauge eeprom. [ 158.895451] cx18-0: Invalid EEPROM [ 158.895452] cx18-0: VBI is not yet supported [ 158.940120] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 158.947411] cx18-0: Disabled encoder IDX device [ 158.947608] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 158.947724] DVB: registering new adapter (cx18) [ 158.948455] s5h1409_readreg: readreg error (ret == -121) [ 158.948485] cx18-0: frontend initialization failed [ 158.951440] cx18-0: DVB failed to register [ 158.951623] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 158.951758] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 158.951892] cx18-0: Registered device radio0 for encoder radio [ 158.952235] cx18-0: Error -12 registering devices [ 158.953794] cx18-0: Error -12 on initialization [ 158.956328] cx18: probe of 0000:01:06.0 failed with error -12 [ 158.956566] cx18: End initialization [ 158.960969] Unable to handle kernel paging request at ffffc200033800f8 RIP: [ 158.960974] [<ffffffff8826d355>] :cx18:cx18_setup_page+0x25/0x90 [ 158.960987] PGD 3ed0e067 PUD 3ed0f067 PMD 3d580067 PTE 0 [ 158.960991] Oops: 0000 [1] SMP [ 158.960993] CPU 0 [ 158.960995] Modules linked in: cx18 dvb_core compat_ioctl32 i2c_algo_bit cx2341x tveeprom ipv6 aes_generic aes_x86_64 af_packet rfcomm l2cap bluetooth ppdev powernow_k8 cpufreq_userspace cpufreq_conservative cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table video output sbs container sbshc dock battery iptable_filter ip_tables x_tables ac lp loop snd_hda_intel snd_pcm_oss snd_mixer_oss arc4 snd_pcm ecb blkcipher snd_page_alloc snd_hwdep snd_seq_dummy s5h1409 snd_seq_oss snd_seq_midi cs5345 tuner snd_rawmidi rt61pci rt2x00pci rt2x00lib snd_seq_midi_event rfkill snd_seq input_polldev crc_itu_t snd_timer mac80211 videodev v4l1_compat snd_seq_device v4l2_common cfg80211 snd eeprom_93cx6 serio_raw button i2c_nforce2 parport_pc parport k8temp psmouse evdev soundcore i2c_core shpchp pci_hotplug pcspkr ext3 jbd mbcache sr_mod cdrom sg sd_mod sata_nv pata_amd ata_generic pata_acpi libata scsi_mod forcedeth ehci_hcd ohci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse [ 158.961042] Pid: 6288, comm: hald-probe-vide Not tainted 2.6.24-21-generic #1 [ 158.961044] RIP: 0010:[<ffffffff8826d355>] [<ffffffff8826d355>] :cx18:cx18_setup_page+0x25/0x90 [ 158.961052] RSP: 0018:ffff810020fb7cb8 EFLAGS: 00010296 [ 158.961053] RAX: ffffc20002680000 RBX: 0000000000000008 RCX: 0000000000008010 [ 158.961055] RDX: 0000000000000000 RSI: 0000000000000010 RDI: 000000000000003d [ 158.961057] RBP: 0000000000000010 R08: 0000000000000000 R09: ffff81003ff7b060 [ 158.961059] R10: ffff81003ed98430 R11: ffffffff803c53a0 R12: ffff81003e2f0000 [ 158.961061] R13: 0000000000000000 R14: ffff810020f77000 R15: ffffffff802b5fc0 [ 158.961063] FS: 00007f90173ad6e0(0000) GS:ffffffff805b9000(0000) knlGS:00000000f59e5b90 [ 158.961065] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 158.961067] CR2: ffffc200033800f8 CR3: 0000000020ccd000 CR4: 00000000000006e0 [ 158.961069] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 158.961071] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 158.961073] Process hald-probe-vide (pid: 6288, threadinfo ffff810020fb6000, task ffff810027208fc0) [ 158.961075] Stack: 0000000000000008 ffff81003e2f0000 ffff81003e2f26c0 ffffffff88262283 [ 158.961079] ffff81003eb080d0 ffffc20000680000 0000001000022790 ffffc200006bb000 [ 158.961081] 0000000100000101 ffffffff00120000 0000000000001000 0000000000000004 [ 158.961084] Call Trace: [ 158.961094] [<ffffffff88262283>] :cx18:cx18_firmware_init+0x253/0x790 [ 158.961111] [<ffffffff802b5fc0>] chrdev_open+0x0/0x1d0 [ 158.961116] [<ffffffff8825f3cb>] :cx18:cx18_init_on_first_open+0x6b/0x180 [ 158.961120] [<ffffffff802b5b2c>] cdev_get+0x1c/0x60 [ 158.961124] [<ffffffff802b5b7c>] exact_lock+0xc/0x20 [ 158.961128] [<ffffffff803c243b>] kobj_lookup+0x15b/0x170 [ 158.961137] [<ffffffff88264573>] :cx18:cx18_v4l2_open+0xa3/0x230 [ 158.961143] [<ffffffff802b6081>] chrdev_open+0xc1/0x1d0 [ 158.961152] [<ffffffff802b0deb>] __dentry_open+0xdb/0x200 [ 158.961159] [<ffffffff802b101a>] do_filp_open+0x3a/0x50 [ 158.961171] [<ffffffff802b0c57>] get_unused_fd_flags+0x77/0x120 [ 158.961178] [<ffffffff802b108a>] do_sys_open+0x5a/0xf0 [ 158.961184] [<ffffffff8020c37e>] system_call+0x7e/0x83 [ 158.961195] [ 158.961196] [ 158.961196] Code: 8b 98 f8 00 d0 00 48 85 ff 75 50 c1 ed 11 80 e7 e0 81 e5 00 [ 158.961203] RIP [<ffffffff8826d355>] :cx18:cx18_setup_page+0x25/0x90 [ 158.961209] RSP <ffff810020fb7cb8> [ 158.961211] CR2: ffffc200033800f8 [ 158.961213] ---[ end trace b930efaa70448a3e ]--- > > > The log also indicates an error -12 (-ENOMEM) on trying to get enough > memory space for transfer buffers. This is a separate problem, To fix > this we'll need to add a 'vmalloc=xxxM' to your kernel command line. > > PLease perform > > $ grep -i vmalloc /proc/meminfo > [EMAIL PROTECTED]:~$ grep -i vmalloc /proc/meminfo VmallocTotal: 34359738367 kB VmallocUsed: 6736 kB VmallocChunk: 34359731331 kB > Figure out how many MiB of address space is used currently for > VmallocTotal, I think that total is listed above. > add 128M to that value, and use the result for your > 'vmalloc=xxxM' option on your kernel command line. > Huh? I don't understand. "kernel command line"? Where is it and what do I do with it? > That will burn up some page table entries in the MMU, but it'll give you > the address space you need for dynamic allocations in the kernel. The > CX23418 chip needs at least one 64 MB continuous chunk of addresses for > all it's memory and registers. > > > > > > > >> [ 1328.767724] cx18: Start initialization, version 1.0.0 >> [ 1328.767783] cx18-0: Initializing card #0 >> [ 1328.767786] cx18-0: Autodetected Hauppauge card >> [ 1328.768920] cx18-0: cx23418 revision 01010000 (B) >> > > This is the second load attempt of the cx18 module at 33 minutes later. > Things are better as the chip revision could be read, so this is likely > mmio_ndelay=?? which is not 0, > > >> [ 1328.840479] cx18-0: Invalid EEPROM >> > > but the mmio_ndelay value used on this one attempt was not high enough > to get reliable operation out of the CX23418. > > > >> [ 1328.840481] cx18-0: VBI is not yet supported >> [ 1328.885352] cs5345 2-004c: chip found @ 0x98 (cx18 i2c driver #0-0) >> [ 1328.892069] cx18-0: Disabled encoder IDX device >> [ 1328.892451] cx18-0: Registered device video0 for encoder MPEG (2 MB) >> [ 1328.894814] DVB: registering new adapter (cx18) >> [ 1328.895522] cx18-0: frontend initialization failed >> [ 1328.895670] cx18-0: DVB failed to register >> [ 1328.895694] cx18-0: Registered device video32 for encoder YUV (2 MB) >> [ 1328.895710] cx18-0: Registered device video24 for encoder PCM audio >> (1 MB) >> [ 1328.895726] cx18-0: Registered device radio0 for encoder radio >> [ 1328.895884] cx18-0: Error -12 registering devices >> [ 1328.897348] cx18-0: Error -12 on initialization >> [ 1328.897375] cx18: probe of 0000:01:06.0 failed with error -12 >> [ 1328.897393] cx18: End initialization >> > > And again -12 is -ENOMEM. A vmalloc option on the kernel commandline > should fix this. > > > Keep at it. We should be able to get this working. > > > Regards, > Andy > > Replying to this letter is as complicated as learning how to make my computer work :-) When you reply please delete none relevant lines. I need to keep the confusion to a minimum. Also, as I said earlier, I have the card recognized on my other drive installation. I would however like to get it going on this "testing" system. But if it is a huge job and you would rather, I can forget this and just go to my other drive where the card is recognized but the tuner is still not showing a signal. I don't want to abuse a willing helper. My concern is that I don't want to take a chance on my good system until I am sure I can get it working on this system. Thanks you Andy > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
