Re: [comedi] ni_pcimio does not support attach using comedi_config
R Smith <[email protected]> Mon, 3 Jul 2023 17:22:47 -0700
| Newsgroups | gmane.linux.comedi |
|---|---|
| Message-ID | <CANgQxoGJvMQGckADAoLiGntBMSrQyQRDwZf=5twFtpXJSO5RsQ@mail.gmail.com> |
--000000000000069e9205ff9e49ea Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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_pci= mio.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! On Mon, Jul 3, 2023 at 3:08=E2=80=AFAM Ian Abbott <[email protected]> wrote= : > 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:" =E2=80=94 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_p= cimio.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 > > > > > On Fri, Jun 30, 2023 at 4:28=E2=80=AFAM Ian Abbott <[email protected] > > <mailto:[email protected]>> wrote: > > > > On 30/06/2023 01:29, Random Stuff wrote: > > > 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 th= e > > > "comedi.o not loaded" error and fixed it by setting autoconfig= =3D0. > > > However now, I'm getting the following error: > > > > > > configuring driver=3Dni_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 quit= e > > large. > > > Let me know if any further information is required, as I'm quite > > new to > > > this. > > > > > > Thanks! > > > > 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 > > <https://github.com/Linux-Comedi/comedi.git> (if you have done > that). > > 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 t= o > > 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 kerne= l > > 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 vendo= r > > 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 > > > > -- > > -=3D( Ian Abbott <[email protected] <mailto:[email protected]>> || = MEV > > Ltd. is a company )=3D- > > -=3D( registered in England & Wales. Regd. number: 02862268. )=3D= - > > -=3D( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=3D= - > > -=3D( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk > > <http://www.mev.co.uk> )=3D- > > > > -- > > 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 [email protected] > > <mailto:[email protected]>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/comedi_list/CANgQxoEzMAwR0hUVETo-O1idBr= dxWDFPjitx1vk1cQJx4OLJPQ%40mail.gmail.com > < > https://groups.google.com/d/msgid/comedi_list/CANgQxoEzMAwR0hUVETo-O1idBr= dxWDFPjitx1vk1cQJx4OLJPQ%40mail.gmail.com?utm_medium=3Demail&utm_source=3Df= ooter > >. > > -- > -=3D( Ian Abbott <[email protected]> || MEV Ltd. is a company )=3D- > -=3D( registered in England & Wales. Regd. number: 02862268. )=3D- > -=3D( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=3D- > -=3D( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=3D- > > --=20 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 e= mail to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/= comedi_list/CANgQxoGJvMQGckADAoLiGntBMSrQyQRDwZf%3D5twFtpXJSO5RsQ%40mail.gm= ail.com. --000000000000069e9205ff9e49ea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hello Ian,<br><br></div>Thank you very much for the r= esponse. I have removed the git repo version of comedi and am using the lin= ux kernel one. Here is the output of "sudo modinfo --filename comedi n= i_pcimio" now: <br><div><br></div><div>$ sudo modinfo --filename comed= i ni_pcimio<br></div><div>/lib/modules/4.4.0-210-generic/kernel/drivers/sta= ging/comedi/comedi.ko<br>/lib/modules/4.4.0-210-generic/kernel/drivers/stag= ing/comedi/drivers/ni_pcimio.ko<br><br></div><div>Here is a more verbose ou= tput of lspci; it still doesn't seem to be detecting the PCI. Do you ha= ve any recommendations on how to debug this and where to start? Do you thin= k 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 r= un comedi_config and the pci should automatically configure itself?<br></di= v><br><div class=3D"gmail-de1">$ lspci </div><div class=3D"gmail-de1">00:00.0 Host bridge: Intel Corporation 2nd G= eneration Core Processor Family DRAM Controller (rev 09) </div><div class=3D"gmail-de1">00:01.0 PCI bridge: Intel Corporation Xeon E= 3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) </div><div class=3D"gmail-de1">00:02.0 Display controller: Intel Corporatio= n 2nd Generation Core Processor Family Integrated Graphics Controller (rev = 09) </div><div class=3D"gmail-de1">00:14.0 USB controller: Intel Corporation 7 = Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) </div><div class=3D"gmail-de1">00:16.0 Communication controller: Intel Corp= oration 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) </div><div class=3D"gmail-de1">00:19.0 Ethernet controller: Intel Corporati= on 82579V Gigabit Network Connection (rev 04) </div><div class=3D"gmail-de1">00:1a.0 USB controller: Intel Corporation 7 = Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) </div><div class=3D"gmail-de1">00:1b.0 Audio device: Intel Corporation 7 Se= ries/C216 Chipset Family High Definition Audio Controller (rev 04) </div><div class=3D"gmail-de1">00:1c.0 PCI bridge: Intel Corporation 7 Seri= es/C216 Chipset Family PCI Express Root Port 1 (rev c4) </div><div class=3D"gmail-de1">00:1c.1 PCI bridge: Intel Corporation 7 Seri= es/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) </div><div class=3D"gmail-de1">00:1c.2 PCI bridge: Intel Corporation 7 Seri= es/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) </div><div class=3D"gmail-de1">00:1c.3 PCI bridge: Intel Corporation 7 Seri= es/C216 Chipset Family PCI Express Root Port 4 (rev c4) </div><div class=3D"gmail-de1">00:1c.4 PCI bridge: Intel Corporation 82801 = PCI Bridge (rev c4) </div><div class=3D"gmail-de1">00:1c.6 PCI bridge: Intel Corporation 7 Seri= es/C210 Series Chipset Family PCI Express Root Port 7 (rev c4) </div><div class=3D"gmail-de1">00:1c.7 PCI bridge: Intel Corporation 7 Seri= es/C210 Series Chipset Family PCI Express Root Port 8 (rev c4) </div><div class=3D"gmail-de1">00:1d.0 USB controller: Intel Corporation 7 = Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) </div><div class=3D"gmail-de1">00:1f.0 ISA bridge: Intel Corporation Z77 Ex= press Chipset LPC Controller (rev 04) </div><div class=3D"gmail-de1">00:1f.2 SATA controller: Intel Corporation 7= Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev = 04) </div><div class=3D"gmail-de1">00:1f.3 SMBus: Intel Corporation 7 Series/C2= 16 Chipset Family SMBus Controller (rev 04) </div><div class=3D"gmail-de1">01:00.0 VGA compatible controller: NVIDIA Co= rporation GK107 [GeForce GTX 650] (rev a1) </div><div class=3D"gmail-de1">01:00.1 Audio device: NVIDIA Corporation GK1= 07 HDMI Audio Controller (rev a1) </div><div class=3D"gmail-de1">02:00.0 VGA compatible controller: NVIDIA Co= rporation GF108 [GeForce GT 430] (rev a1) </div><div class=3D"gmail-de1">02:00.1 Audio device: NVIDIA Corporation GF1= 08 High Definition Audio Controller (rev a1) </div><div class=3D"gmail-de1">03:00.0 PCI bridge: Texas Instruments XIO221= 3A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) </div><div class=3D"gmail-de1">04:00.0 FireWire (IEEE 1394): Texas Instrume= nts XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01= ) </div><div class=3D"gmail-de1">05:00.0 USB controller: ASMedia Technology I= nc. ASM1042 SuperSpeed USB Host Controller </div><div class=3D"gmail-de1">06:00.0 SATA controller: ASMedia Technology = Inc. ASM1062 Serial ATA Controller (rev 01) </div><div class=3D"gmail-de1">07:00.0 PCI bridge: ASMedia Technology Inc. = ASM1083/1085 PCIe to PCI Bridge (rev 03) </div><div class=3D"gmail-de1">09:00.0 Network controller: Qualcomm Atheros= AR9485 Wireless Network Adapter (rev 01) </div><div class=3D"gmail-de1">0a:00.0 USB controller: ASMedia Technology I= nc. ASM1042 SuperSpeed USB Host Controller <br><br></div><div class=3D"gmail-de1">Thanks again for all the debugging h= elp. I really appreciate it!<br></div></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 3, 2023 at 3:08=E2=80=AFA= M Ian Abbott <<a href=3D"mailto:[email protected]">[email protected]</a>= > wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px = 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 0= 1/07/2023 00:35, Random Stuff wrote:<br> > Thank you very much for the detailed response. I'm not getting any= <br> > output from "lspci -v -n -d 1093:" =E2=80=94 does that mean = my computer doesn't <br> > physically detect a PCI?<br> > <br> > $ lspci -v -n -d 1093:<br> > $<br> <br> It means it could not find a PCI device that matches NI's PCI Vendor ID= , <br> but I would expect an NI PCI-6014 to use NI's vendor ID!=C2=A0 If you o= mit <br> the `-d 1093:` it will list all PCI devices.<br> <br> > In any case, here is the output I get from "sudo modinfo --filena= me <br> > comedi comedi_fc ni_pcimio" and "dmesg"<br> > <br> > $ sudo modinfo --filename comedi comedi_fc ni_pcimio<br> > /lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/comedi.ko= <br> > /lib/modules/4.4.0-210-generic/comedi/drivers/comedi_fc.ko<br> > /lib/modules/4.4.0-210-generic/kernel/drivers/staging/comedi/drivers/n= i_pcimio.ko<br> <br> It looks like you *do* have a mixture of the two sets of comedi modules <br= > installed.=C2=A0 The ones in "/lib/modules/$(uname <br> -r)/kernel/drivers/staging" are the ones built from Linux kernel sourc= es <br> (and since this looks like an Ubuntu or Linux Mint kernel, probably <br> installed by a "linux-modules-extra" package).=C2=A0 The ones in = <br> "/lib/modules/$(uname -r)/comedi" are the ones built from the com= edi git <br> repository.<br> <br> You can't really have both sets installed.=C2=A0 Given the choice, I wo= uld <br> prefer the ones built from the Linux kernel sources, not the ones built <br= > from the comedi git repository.<br> <br> > <br> > $ dmesg<br> [snip]<br> > *[86380.615473] comedi comedi0: driver 'ni_pcimio' does not su= pport <br> > attach using comedi_config*<br> <br> Indeed, the ni_pcimio built from the Linux kernel sources (which is the <br= > one that got matched first in the module path) does not support manual <br> configuration using comedi_config (since kernel version 3.10).<br> <br> > Do you recommend deleting all comedi folders I have on my machine and = <br> > re-installing using the github comedi modules since they support manua= l <br> > configuration?=C2=A0 If so, should I be following these instructions <= br> > <<a href=3D"https://github.com/Linux-Comedi/comedi/blob/master/INST= ALL" rel=3D"noreferrer" target=3D"_blank">https://github.com/Linux-Comedi/c= omedi/blob/master/INSTALL</a>>, and where <br> > is the<br> > recommended directory where I should git pull? Thanks again for taking= a <br> > look at this, I really appreciate it.<br> <br> Manual configuration with comedi_config would not help anyway if a <br> matching PCI device cannot be detected in the system.=C2=A0 I would recomme= nd <br> using the Linux kernel "staging" modules, even though they do not= <br> support manual configuration of most PCI devices.<br> <br> What we need to work out is why no PCI device with NI's PCI vendor ID <= br> has been listed by lspci.<br> <br> <br> Regards,<br> Ian<br> <br> <br> <br> > On Fri, Jun 30, 2023 at 4:28=E2=80=AFAM Ian Abbott <<a href=3D"mail= to:[email protected]" target=3D"_blank">[email protected]</a> <br> > <mailto:<a href=3D"mailto:[email protected]" target=3D"_blank">abbo= [email protected]</a>>> wrote:<br> > <br> >=C2=A0 =C2=A0 =C2=A0On 30/06/2023 01:29, Random Stuff wrote:<br> >=C2=A0 =C2=A0 =C2=A0 > Hello everyone,<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > I'm using a National Instruments PCI-6014= 188626D-01 daq and<br> >=C2=A0 =C2=A0 =C2=A0trying to<br> >=C2=A0 =C2=A0 =C2=A0 > run comedi_config to setup the daq. Initially= , I kept getting the<br> >=C2=A0 =C2=A0 =C2=A0 > "comedi.o not loaded" error and fix= ed it by setting autoconfig=3D0.<br> >=C2=A0 =C2=A0 =C2=A0 > However now, I'm getting the following er= ror:<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > configuring driver=3Dni_pcimio 0,0,0,0,0,...0= ,0,0<br> >=C2=A0 =C2=A0 =C2=A0 > Configure failed!: Input/output error<br> >=C2=A0 =C2=A0 =C2=A0 > Check kernel log for more information<br> >=C2=A0 =C2=A0 =C2=A0 > Possible reasons for failure:<br> >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 Driver not found<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > If I check kernel logs using "dmesg"= ;, I see: "comedi comedi0: driver<br> >=C2=A0 =C2=A0 =C2=A0 > ni_pcimio does not support attach using comed= i_config" multiple<br> >=C2=A0 =C2=A0 =C2=A0times as<br> >=C2=A0 =C2=A0 =C2=A0 > well as a few comedi_fc errors regarding unko= wn symbols. Let me<br> >=C2=A0 =C2=A0 =C2=A0know if<br> >=C2=A0 =C2=A0 =C2=A0 > you'd like me to send over the full dmesg= output, but it is quite<br> >=C2=A0 =C2=A0 =C2=A0large.<br> >=C2=A0 =C2=A0 =C2=A0 > Let me know if any further information is req= uired, as I'm quite<br> >=C2=A0 =C2=A0 =C2=A0new to<br> >=C2=A0 =C2=A0 =C2=A0 > this.<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > Thanks!<br> > <br> >=C2=A0 =C2=A0 =C2=A0It sounds like you *might* have a mixture of the tw= o mutually<br> >=C2=A0 =C2=A0 =C2=A0incompatible sets of comedi modules installed on yo= ur system, but<br> >=C2=A0 =C2=A0 =C2=A0perhaps not.=C2=A0 By the two mutually incompatible= sets of comedi<br> >=C2=A0 =C2=A0 =C2=A0modules, I<br> >=C2=A0 =C2=A0 =C2=A0mean:<br> > <br> >=C2=A0 =C2=A0 =C2=A01. The set of comedi modules built from sources at<= br> >=C2=A0 =C2=A0 =C2=A0<a href=3D"https://github.com/Linux-Comedi/comedi.g= it" rel=3D"noreferrer" target=3D"_blank">https://github.com/Linux-Comedi/co= medi.git</a><br> >=C2=A0 =C2=A0 =C2=A0<<a href=3D"https://github.com/Linux-Comedi/come= di.git" rel=3D"noreferrer" target=3D"_blank">https://github.com/Linux-Comed= i/comedi.git</a>> (if you have done that).<br> >=C2=A0 =C2=A0 =C2=A0These were previously hosted on <a href=3D"http://c= omedi.org" rel=3D"noreferrer" target=3D"_blank">comedi.org</a> <<a href= =3D"http://comedi.org" rel=3D"noreferrer" target=3D"_blank">http://comedi.o= rg</a>> so I<br> >=C2=A0 =C2=A0 =C2=A0will refer to them as<br> >=C2=A0 =C2=A0 =C2=A0the "<a href=3D"http://comedi.org" rel=3D"nore= ferrer" target=3D"_blank">comedi.org</a> <<a href=3D"http://comedi.org" = rel=3D"noreferrer" target=3D"_blank">http://comedi.org</a>>" comedi= modules.<br> > <br> >=C2=A0 =C2=A0 =C2=A02. The set of comedi modules included with the Linu= x kernel image<br> >=C2=A0 =C2=A0 =C2=A0packages, or perhaps in an "extra modules"= ; package.=C2=A0 I will refer to<br> >=C2=A0 =C2=A0 =C2=A0them as the "Linux" comedi modules.<br> > <br> >=C2=A0 =C2=A0 =C2=A0The modules from set 2 (the "Linux" comed= i modules) removed the support<br> >=C2=A0 =C2=A0 =C2=A0for manually configuration from most of the PCI and= USB drivers a long<br> >=C2=A0 =C2=A0 =C2=A0time ago, and also removed "comedi_fc" as= a separate module,<br> >=C2=A0 =C2=A0 =C2=A0incorporating its functions into the main "com= edi" module.<br> >=C2=A0 =C2=A0 =C2=A0Auto-configuration was removed from the "ni_pc= imio" driver in kernel<br> >=C2=A0 =C2=A0 =C2=A0version 3.10.=C2=A0 The "comedi_fc" modul= e was removed in kernel version<br> >=C2=A0 =C2=A0 =C2=A03.18.<br> > <br> >=C2=A0 =C2=A0 =C2=A0The modules from set 1 (the "<a href=3D"http:/= /comedi.org" rel=3D"noreferrer" target=3D"_blank">comedi.org</a> <<a hre= f=3D"http://comedi.org" rel=3D"noreferrer" target=3D"_blank">http://comedi.= org</a>>" comedi<br> >=C2=A0 =C2=A0 =C2=A0modules) still support<br> >=C2=A0 =C2=A0 =C2=A0manual configuration of PCI and USB devices and sti= ll has the<br> >=C2=A0 =C2=A0 =C2=A0"comedi_fc" module.<br> > <br> >=C2=A0 =C2=A0 =C2=A0The usual reason auto-configuration doesn't wor= k is when there is a<br> >=C2=A0 =C2=A0 =C2=A0variant of the card with different PCI ID informati= on that the driver's<br> >=C2=A0 =C2=A0 =C2=A0device ID table does not match.=C2=A0 That has happ= ened before with NI cards.<br> > <br> >=C2=A0 =C2=A0 =C2=A0The following info would be useful:<br> > <br> >=C2=A0 =C2=A0 =C2=A01. The output from: lspci -v -n -d 1093:<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (That will list info about PCI devic= es matching NI's PCI vendor<br> >=C2=A0 =C2=A0 =C2=A0ID.)<br> > <br> >=C2=A0 =C2=A0 =C2=A02. The output from: sudo modinfo --filename comedi = comedi_fc ni_pcimio<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (That will show the paths of various= comedi modules.)<br> > <br> >=C2=A0 =C2=A0 =C2=A03. Your "dmesg" output, preferably with b= its unrelated to comedi<br> >=C2=A0 =C2=A0 =C2=A0removed.<br> > <br> >=C2=A0 =C2=A0 =C2=A0Regards,<br> >=C2=A0 =C2=A0 =C2=A0Ian<br> > <br> >=C2=A0 =C2=A0 =C2=A0-- <br> >=C2=A0 =C2=A0 =C2=A0-=3D( Ian Abbott <<a href=3D"mailto:abbotti@mev.= co.uk" target=3D"_blank">[email protected]</a> <mailto:<a href=3D"mailto= :[email protected]" target=3D"_blank">[email protected]</a>>> || MEV<= br> >=C2=A0 =C2=A0 =C2=A0Ltd. is a company=C2=A0 )=3D-<br> >=C2=A0 =C2=A0 =C2=A0-=3D( registered in England & Wales.=C2=A0 Regd= . number: 02862268.=C2=A0 )=3D-<br> >=C2=A0 =C2=A0 =C2=A0-=3D( Regd. addr.: S11 & 12 Building 67, Europa= Business Park, )=3D-<br> >=C2=A0 =C2=A0 =C2=A0-=3D( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || <a= href=3D"http://www.mev.co.uk" rel=3D"noreferrer" target=3D"_blank">www.mev= .co.uk</a><br> >=C2=A0 =C2=A0 =C2=A0<<a href=3D"http://www.mev.co.uk" rel=3D"norefer= rer" target=3D"_blank">http://www.mev.co.uk</a>> )=3D-<br> > <br> > -- <br> > You received this message because you are subscribed to the Google <br= > > Groups "Comedi: Linux Control and Measurement Device Interface&qu= ot; group.<br> > To unsubscribe from this group and stop receiving emails from it, send= <br> > an email to <a href=3D"mailto:comedi_list%[email protected]= om" target=3D"_blank">[email protected]</a> <br> > <mailto:<a href=3D"mailto:comedi_list%[email protected]= m" target=3D"_blank">[email protected]</a>>.<br> > To view this discussion on the web visit <br> > <a href=3D"https://groups.google.com/d/msgid/comedi_list/CANgQxoEzMAwR= 0hUVETo-O1idBrdxWDFPjitx1vk1cQJx4OLJPQ%40mail.gmail.com" rel=3D"noreferrer"= target=3D"_blank">https://groups.google.com/d/msgid/comedi_list/CANgQxoEzM= AwR0hUVETo-O1idBrdxWDFPjitx1vk1cQJx4OLJPQ%40mail.gmail.com</a> <<a href= =3D"https://groups.google.com/d/msgid/comedi_list/CANgQxoEzMAwR0hUVETo-O1id= BrdxWDFPjitx1vk1cQJx4OLJPQ%40mail.gmail.com?utm_medium=3Demail&utm_sour= ce=3Dfooter" rel=3D"noreferrer" target=3D"_blank">https://groups.google.com= /d/msgid/comedi_list/CANgQxoEzMAwR0hUVETo-O1idBrdxWDFPjitx1vk1cQJx4OLJPQ%40= mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter</a>>.<br> <br> -- <br> -=3D( Ian Abbott <<a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>> || MEV Ltd. is a company=C2=A0 )=3D-<br> -=3D( registered in England & Wales.=C2=A0 Regd. number: 02862268.=C2= =A0 )=3D-<br> -=3D( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=3D-<br= > -=3D( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || <a href=3D"http://www.mev.= co.uk" rel=3D"noreferrer" target=3D"_blank">www.mev.co.uk</a> )=3D-<br> <br> </blockquote></div> <p></p> -- <br /> You received this message because you are subscribed to the Google Groups &= quot;Comedi: Linux Control and Measurement Device Interface" group.<br= /> To unsubscribe from this group and stop receiving emails from it, send an e= mail to <a href=3D"mailto:[email protected]">comedi_= [email protected]</a>.<br /> To view this discussion on the web visit <a href=3D"https://groups.google.c= om/d/msgid/comedi_list/CANgQxoGJvMQGckADAoLiGntBMSrQyQRDwZf%3D5twFtpXJSO5Rs= Q%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.g= oogle.com/d/msgid/comedi_list/CANgQxoGJvMQGckADAoLiGntBMSrQyQRDwZf%3D5twFtp= XJSO5RsQ%40mail.gmail.com</a>.<br /> --000000000000069e9205ff9e49ea--