ni_pcimio does not support attach using comedi_config

[Random Stuff]

Hello everyone,

I'm using a National Instruments PCI-6014 188626D-01 daq and trying to run comedi_config to setup the daq. Initially, I kept getting the "comedi.o not loaded" error and fixed it by setting autoconfig=0. However now, I'm getting the following error:

configuring driver=ni_pcimio 0,0,0,0,0,...0,0,0

Configure failed!: Input/output error

Check kernel log for more information

Possible reasons for failure:

  Driver not found

If I check kernel logs using "dmesg", I see: "comedi comedi0: driver ni_pcimio does not support attach using comedi_config" multiple times as well as a few comedi_fc errors regarding unkown symbols. Let me know if you'd like me to send over the full dmesg output, but it is quite large. Let me know if any further information is required, as I'm quite new to this.

Thanks!

[Ian Abbott]

It sounds like you *might* have a mixture of the two mutually
incompatible sets of comedi modules installed on your system, but
perhaps not. By the two mutually incompatible sets of comedi modules, I
mean:

1. The set of comedi modules built from sources at
https://github.com/Linux-Comedi/comedi.git (if you have done that).
These were previously hosted on comedi.org so I will refer to them as
the "comedi.org" comedi modules.

2. The set of comedi modules included with the Linux kernel image
packages, or perhaps in an "extra modules" package. I will refer to
them as the "Linux" comedi modules.

The modules from set 2 (the "Linux" comedi modules) removed the support
for manually configuration from most of the PCI and USB drivers a long
time ago, and also removed "comedi_fc" as a separate module,
incorporating its functions into the main "comedi" module.
Auto-configuration was removed from the "ni_pcimio" driver in kernel
version 3.10. The "comedi_fc" module was removed in kernel version 3.18.

The modules from set 1 (the "comedi.org" comedi modules) still support
manual configuration of PCI and USB devices and still has the
"comedi_fc" module.

The usual reason auto-configuration doesn't work is when there is a
variant of the card with different PCI ID information that the driver's
device ID table does not match. That has happened before with NI cards.

The following info would be useful:

1. The output from: lspci -v -n -d 1093:
(That will list info about PCI devices matching NI's PCI vendor ID.)

2. The output from: sudo modinfo --filename comedi comedi_fc ni_pcimio
(That will show the paths of various comedi modules.)

3. Your "dmesg" output, preferably with bits unrelated to comedi removed.

Regards,
Ian

--
-=( Ian Abbott <abb...@mev.co.uk> || MEV Ltd. is a company )=-
-=( registered in England & Wales. Regd. number: 02862268. )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-

[Random Stuff]

Thank you very much for the detailed response. I'm not getting any output from "lspci -v -n -d 1093:" — does that mean my computer doesn't physically detect a PCI?

$ lspci -v -n -d 1093:

$

In any case, here is the output I get from "sudo modinfo --filename comedi comedi_fc ni_pcimio" and "dmesg"

$ sudo modinfo --filename comedi comedi_fc ni_pcimio

/lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/comedi.ko

/lib/modules/4.4.0-210-generic/comedi/drivers/comedi_fc.ko

/lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/drivers/ni_pcimio.ko

$ dmesg

[84157.165914] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[84179.538722] wlp9s0: deauthenticating from ac:23:16:f8:19:65 by local choice (Reason: 3=DEAUTH_LEAVING)
[84180.179801] wlp9s0: authenticate with ac:23:16:f8:19:65
[84180.200523] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[84180.206824] wlp9s0: authenticated
[84180.207320] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[84180.228855] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=57)
[84180.228954] wlp9s0: associated
[84180.310325] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[84185.089415] wlp9s0: authenticate with ac:23:16:f8:19:65
[84185.110236] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[84185.212820] wlp9s0: send auth to ac:23:16:f8:19:65 (try 2/3)
[84185.320944] wlp9s0: send auth to ac:23:16:f8:19:65 (try 3/3)
[84185.425082] wlp9s0: authentication with ac:23:16:f8:19:65 timed out
[84225.568582] IPv6: ADDRCONF(NETDEV_UP): wlp9s0: link is not ready
[84226.667126] wlp9s0: authenticate with ac:23:16:f8:19:65
[84226.687759] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[84226.690390] wlp9s0: authenticated
[84226.694507] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[84226.696807] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=66)
[84226.696877] wlp9s0: associated
[84226.696888] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0: link becomes ready
[84229.042156] wlp9s0: authenticate with ac:23:16:f8:19:65
[84229.062849] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[84229.065343] wlp9s0: authenticated
[84229.068412] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[84229.071889] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=63)
[84229.071971] wlp9s0: associated
[84230.982161] wlp9s0: authenticate with ac:23:16:f8:19:65
[84231.002891] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[84231.008630] wlp9s0: authenticated
[84231.011932] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[84231.124560] wlp9s0: associate with ac:23:16:f8:19:65 (try 2/3)
[84231.283955] wlp9s0: associate with ac:23:16:f8:19:65 (try 3/3)
[84231.385023] wlp9s0: association with ac:23:16:f8:19:65 timed out
[84271.194360] IPv6: ADDRCONF(NETDEV_UP): wlp9s0: link is not ready
[85627.113738] usb 3-3: new high-speed USB device number 2 using xhci_hcd
[85627.304865] usb 3-3: New USB device found, idVendor=058f, idProduct=6387
[85627.304879] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[85627.304882] usb 3-3: Product: Mass Storage
[85627.304885] usb 3-3: Manufacturer: Generic
[85627.304888] usb 3-3: SerialNumber: 169FF990
[85627.356659] usb-storage 3-3:1.0: USB Mass Storage device detected
[85627.356858] scsi host8: usb-storage 3-3:1.0
[85627.357006] usbcore: registered new interface driver usb-storage
[85627.359657] usbcore: registered new interface driver uas
[85628.356553] scsi 8:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 4
[85628.357204] sd 8:0:0:0: Attached scsi generic sg2 type 0
[85628.357768] sd 8:0:0:0: [sdb] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[85628.358424] sd 8:0:0:0: [sdb] Write Protect is off
[85628.358429] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
[85628.359088] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[85628.366918]  sdb: sdb1 sdb2 sdb3
[85628.369269] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[85650.614007] EXT4-fs (sdb3): recovery complete
[85650.621883] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[85650.624493] ISO 9660 Extensions: Microsoft Joliet Level 3
[85650.628192] ISO 9660 Extensions: Microsoft Joliet Level 3
[85650.635537] ISO 9660 Extensions: RRIP_1991A
[85694.520039] usb 3-3: USB disconnect, device number 2
[85698.923225] usb 3-3: new high-speed USB device number 3 using xhci_hcd
[85699.113951] usb 3-3: New USB device found, idVendor=058f, idProduct=6387
[85699.113956] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[85699.113960] usb 3-3: Product: Mass Storage
[85699.113963] usb 3-3: Manufacturer: Generic
[85699.113966] usb 3-3: SerialNumber: 169FF990
[85699.114476] usb-storage 3-3:1.0: USB Mass Storage device detected
[85699.115493] scsi host9: usb-storage 3-3:1.0
[85700.116523] scsi 9:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 4
[85700.117140] sd 9:0:0:0: Attached scsi generic sg2 type 0
[85700.117857] sd 9:0:0:0: [sdb] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[85700.118513] sd 9:0:0:0: [sdb] Write Protect is off
[85700.118519] sd 9:0:0:0: [sdb] Mode Sense: 23 00 00 00
[85700.120464] sd 9:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[85700.124572]  sdb: sdb1 sdb2 sdb3
[85700.127203] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[85709.404416] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[85711.732420] ISO 9660 Extensions: Microsoft Joliet Level 3
[85711.734741] ISO 9660 Extensions: Microsoft Joliet Level 3
[85711.735858] ISO 9660 Extensions: RRIP_1991A
[85737.280251] usb 3-3: USB disconnect, device number 3
[85827.347610] usb 3-3: new high-speed USB device number 4 using xhci_hcd
[85827.538404] usb 3-3: New USB device found, idVendor=058f, idProduct=6387
[85827.538410] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[85827.538413] usb 3-3: Product: Mass Storage
[85827.538417] usb 3-3: Manufacturer: Generic
[85827.538420] usb 3-3: SerialNumber: 169FF990
[85827.538873] usb-storage 3-3:1.0: USB Mass Storage device detected
[85827.539130] scsi host10: usb-storage 3-3:1.0
[85828.537362] scsi 10:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 4
[85828.537927] sd 10:0:0:0: Attached scsi generic sg2 type 0
[85828.538606] sd 10:0:0:0: [sdb] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[85828.539280] sd 10:0:0:0: [sdb] Write Protect is off
[85828.539285] sd 10:0:0:0: [sdb] Mode Sense: 23 00 00 00
[85828.539953] sd 10:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[85828.546222]  sdb: sdb1 sdb2 sdb3
[85828.548462] sd 10:0:0:0: [sdb] Attached SCSI removable disk
[85830.672515] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[85840.618312] ISO 9660 Extensions: Microsoft Joliet Level 3
[85840.620836] ISO 9660 Extensions: Microsoft Joliet Level 3
[85840.621805] ISO 9660 Extensions: RRIP_1991A
[85844.039762] ISO 9660 Extensions: Microsoft Joliet Level 3
[85844.042094] ISO 9660 Extensions: Microsoft Joliet Level 3
[85844.043030] ISO 9660 Extensions: RRIP_1991A
[85882.414456] usb 3-3: USB disconnect, device number 4
[86063.511434] wlp9s0: authenticate with ac:23:16:f8:19:65
[86063.525694] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86063.529376] wlp9s0: authenticated
[86063.531320] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86063.540511] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=67)
[86063.540590] wlp9s0: associated
[86063.540603] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0: link becomes ready
[86063.571418] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86079.349488] wlp9s0: authenticate with ac:23:16:f8:19:65
[86079.370451] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86079.375418] wlp9s0: authenticated
[86079.376982] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86079.384866] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=55)
[86079.384964] wlp9s0: associated
[86079.643963] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86081.365990] wlp9s0: authenticate with ac:23:16:f8:19:65
[86081.386400] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86081.407806] wlp9s0: authenticated
[86081.408886] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86081.475331] wlp9s0: associate with ac:23:16:f8:19:65 (try 2/3)
[86081.628064] wlp9s0: associate with ac:23:16:f8:19:65 (try 3/3)
[86081.718147] wlp9s0: association with ac:23:16:f8:19:65 timed out
[86108.729482] IPv6: ADDRCONF(NETDEV_UP): wlp9s0: link is not ready
[86110.012279] wlp9s0: authenticate with ac:23:16:f8:19:65
[86110.026479] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86110.053770] wlp9s0: authenticated
[86110.056369] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86110.067513] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=56)
[86110.067580] wlp9s0: associated
[86110.067625] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0: link becomes ready
[86110.670730] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86113.287422] wlp9s0: authenticate with ac:23:16:f8:19:65
[86113.308275] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86113.312823] wlp9s0: authenticated
[86113.314731] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86113.341628] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=60)
[86113.341726] wlp9s0: associated
[86113.743192] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86117.261106] wlp9s0: authenticate with ac:23:16:f8:19:65
[86117.281739] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86117.284557] wlp9s0: authenticated
[86117.288491] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86117.294619] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=58)
[86117.294710] wlp9s0: associated
[86117.531804] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86131.243091] wlp9s0: authenticate with ac:23:16:f8:19:65
[86131.263823] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86131.266778] wlp9s0: authenticated
[86131.270458] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86131.331408] wlp9s0: associate with ac:23:16:f8:19:65 (try 2/3)
[86131.335312] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=52)
[86131.335418] wlp9s0: associated
[86133.281013] wlp9s0: authenticate with ac:23:16:f8:19:65
[86133.302393] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86133.306134] wlp9s0: authenticated
[86133.308230] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86133.310790] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=62)
[86133.310913] wlp9s0: associated
[86134.326405] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86151.208663] wlp9s0: authenticate with ac:23:16:f8:19:65
[86151.231409] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86151.234596] wlp9s0: authenticated
[86151.236050] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86151.247114] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=57)
[86151.247205] wlp9s0: associated
[86152.247672] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86155.675466] IPv6: ADDRCONF(NETDEV_UP): wlp9s0: link is not ready
[86156.220984] wlp9s0: authenticate with ac:23:16:f8:19:65
[86156.241767] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86156.288227] wlp9s0: authenticated
[86156.292350] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86156.371699] wlp9s0: associate with ac:23:16:f8:19:65 (try 2/3)
[86156.386530] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=59)
[86156.386626] wlp9s0: associated
[86156.386682] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0: link becomes ready
[86156.550624] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86187.258531] wlp9s0: authenticate with ac:23:16:f8:19:65
[86187.279141] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86187.288701] wlp9s0: authenticated
[86187.289768] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86187.293183] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=65)
[86187.293276] wlp9s0: associated
[86187.373162] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86201.722483] wlp9s0: deauthenticating from ac:23:16:f8:19:65 by local choice (Reason: 3=DEAUTH_LEAVING)
[86202.364945] wlp9s0: authenticate with ac:23:16:f8:19:65
[86202.385794] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86202.387871] wlp9s0: authenticated
[86202.388612] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86202.398804] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=64)
[86202.398898] wlp9s0: associated
[86202.429338] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86210.304799] wlp9s0: authenticate with ac:23:16:f8:19:65
[86210.325715] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86210.332218] wlp9s0: authenticated
[86210.336283] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86210.338683] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=66)
[86210.338775] wlp9s0: associated
[86210.516864] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86241.461107] wlp9s0: authenticate with ac:23:16:f8:19:65
[86241.481871] wlp9s0: send auth to ac:23:16:f8:19:65 (try 1/3)
[86241.484227] wlp9s0: authenticated
[86241.484567] wlp9s0: associate with ac:23:16:f8:19:65 (try 1/3)
[86241.494793] wlp9s0: RX AssocResp from ac:23:16:f8:19:65 (capab=0x1421 status=0 aid=63)
[86241.494887] wlp9s0: associated
[86241.549356] wlp9s0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:23:16:f8:19:65
[86247.839847] wlp9s0: deauthenticating from ac:23:16:f8:19:65 by local choice (Reason: 3=DEAUTH_LEAVING)
[86380.615473] comedi comedi0: driver 'ni_pcimio' does not support attach using comedi_config

Do you recommend deleting all comedi folders I have on my machine and re-installing using the github comedi modules since they support manual configuration? If so, should I be following these instructions, and where is the
recommended directory where I should git pull? Thanks again for taking a look at this, I really appreciate it.

[Ian Abbott]

On 01/07/2023 00:35, Random Stuff wrote:
> Thank you very much for the detailed response. I'm not getting any
> output from "lspci -v -n -d 1093:" — does that mean my computer doesn't
> physically detect a PCI?
>
> $ lspci -v -n -d 1093:
> $

It means it could not find a PCI device that matches NI's PCI Vendor ID,
but I would expect an NI PCI-6014 to use NI's vendor ID! If you omit
the `-d 1093:` it will list all PCI devices.

> In any case, here is the output I get from "sudo modinfo --filename
> comedi comedi_fc ni_pcimio" and "dmesg"
>
> $ sudo modinfo --filename comedi comedi_fc ni_pcimio
> /lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/comedi.ko
> /lib/modules/4.4.0-210-generic/comedi/drivers/comedi_fc.ko
> /lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/drivers/ni_pcimio.ko

It looks like you *do* have a mixture of the two sets of comedi modules
installed. The ones in "/lib/modules/$(uname
-r)/kernel/drivers/staging" are the ones built from Linux kernel sources
(and since this looks like an Ubuntu or Linux Mint kernel, probably
installed by a "linux-modules-extra" package). The ones in
"/lib/modules/$(uname -r)/comedi" are the ones built from the comedi git
repository.

You can't really have both sets installed. Given the choice, I would
prefer the ones built from the Linux kernel sources, not the ones built
from the comedi git repository.

>
> $ dmesg
[snip]
> *[86380.615473] comedi comedi0: driver 'ni_pcimio' does not support
> attach using comedi_config*

Indeed, the ni_pcimio built from the Linux kernel sources (which is the
one that got matched first in the module path) does not support manual
configuration using comedi_config (since kernel version 3.10).

> Do you recommend deleting all comedi folders I have on my machine and
> re-installing using the github comedi modules since they support manual
> configuration? If so, should I be following these instructions

> <https://github.com/Linux-Comedi/comedi/blob/master/INSTALL>, and where

> is the
> recommended directory where I should git pull? Thanks again for taking a
> look at this, I really appreciate it.

Manual configuration with comedi_config would not help anyway if a
matching PCI device cannot be detected in the system. I would recommend
using the Linux kernel "staging" modules, even though they do not
support manual configuration of most PCI devices.

What we need to work out is why no PCI device with NI's PCI vendor ID
has been listed by lspci.


Regards,
Ian

> These were previously hosted on comedi.org <http://comedi.org> so I

> will refer to them as

> the "comedi.org <http://comedi.org>" comedi modules.

>
> 2. The set of comedi modules included with the Linux kernel image
> packages, or perhaps in an "extra modules" package.  I will refer to
> them as the "Linux" comedi modules.
>
> The modules from set 2 (the "Linux" comedi modules) removed the support
> for manually configuration from most of the PCI and USB drivers a long
> time ago, and also removed "comedi_fc" as a separate module,
> incorporating its functions into the main "comedi" module.
> Auto-configuration was removed from the "ni_pcimio" driver in kernel
> version 3.10.  The "comedi_fc" module was removed in kernel version
> 3.18.
>

> The modules from set 1 (the "comedi.org <http://comedi.org>" comedi

> modules) still support
> manual configuration of PCI and USB devices and still has the
> "comedi_fc" module.
>
> The usual reason auto-configuration doesn't work is when there is a
> variant of the card with different PCI ID information that the driver's
> device ID table does not match.  That has happened before with NI cards.
>
> The following info would be useful:
>
> 1. The output from: lspci -v -n -d 1093:
>     (That will list info about PCI devices matching NI's PCI vendor
> ID.)
>
> 2. The output from: sudo modinfo --filename comedi comedi_fc ni_pcimio
>     (That will show the paths of various comedi modules.)
>
> 3. Your "dmesg" output, preferably with bits unrelated to comedi
> removed.
>
> Regards,
> Ian
>
> --

> -=( Ian Abbott <abb...@mev.co.uk <mailto:abb...@mev.co.uk>> || MEV

> Ltd. is a company  )=-
> -=( registered in England & Wales.  Regd. number: 02862268.  )=-
> -=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
> -=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk

> <http://www.mev.co.uk> )=-
>
> --
> You received this message because you are subscribed to the Google
> Groups "Comedi: Linux Control and Measurement Device Interface" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to comedi_list...@googlegroups.com
> <mailto:comedi_list...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/comedi_list/CANgQxoEzMAwR0hUVETo-O1idBrdxWDFPjitx1vk1cQJx4OLJPQ%40mail.gmail.com <https://groups.google.com/d/msgid/comedi_list/CANgQxoEzMAwR0hUVETo-O1idBrdxWDFPjitx1vk1cQJx4OLJPQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[R Smith]

Hello Ian,

Thank you very much for the response. I have removed the git repo version of comedi and am using the linux kernel one. Here is the output of "sudo modinfo --filename comedi ni_pcimio" now:

$ sudo modinfo --filename comedi ni_pcimio

/lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/comedi.ko
/lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/drivers/ni_pcimio.ko

Here is a more verbose output of lspci; it still doesn't seem to be detecting the PCI. Do you have any recommendations on how to debug this and where to start? Do you think it is a hardware issue, or is something going wrong on the software side with comedi? Also, because you said the linux version of comedi doesn't support manual configuration anymore, does that mean there is no need to run comedi_config and the pci should automatically configure itself?

$ lspci

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)

00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)

00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)

00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)

00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)

00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)

00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)

00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)

00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)

00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 (rev c4)

00:1c.4 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4)

00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4)

00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4)

00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)

00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04)

00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)

00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)

01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1)

01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)

02:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)

02:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1)

03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01)

04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01)

05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller

06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)

07:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)

09:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)

0a:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller

Thanks again for all the debugging help. I really appreciate it!

[Ian Abbott]

On 04/07/2023 01:22, R Smith wrote:
> Hello Ian,
>
> Thank you very much for the response. I have removed the git repo
> version of comedi and am using the linux kernel one. Here is the output
> of "sudo modinfo --filename comedi ni_pcimio" now:
>
> $ sudo modinfo --filename comedi ni_pcimio
> /lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/comedi.ko
> /lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/drivers/ni_pcimio.ko
>
> Here is a more verbose output of lspci; it still doesn't seem to be
> detecting the PCI. Do you have any recommendations on how to debug this
> and where to start? Do you think it is a hardware issue, or is something
> going wrong on the software side with comedi? Also, because you said the
> linux version of comedi doesn't support manual configuration anymore,
> does that mean there is no need to run comedi_config and the pci should
> automatically configure itself?

Yes, it should load automatically configure itself. Sorry, I do not
know why the PCI device is not detected, but it's nothing to do with
comedi. Do you have another PC with a different motherboard to test it
with, at least as far as getting it listed by lspci?

[R S]

Hello Ian,

Got it, and thank you very much for the debugging help. I'll try it out on a different pc, and hopefully that solves the issue.

Thank you very much.