- From: David Schleef <ds_at_schleef.org>
- Date: Tue, 4 Jun 2002 16:30:34 -0700
On Tue, Jun 04, 2002 at 05:30:17PM -0400, Patrick Allison wrote: > Here's the output of lspci -vv -s 0:a (pci device 0:a is the PCI-DIO-96) > > 00:0a.0 Class ff00: National Instruments PCI-DIO-96 > 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- > Interrupt: pin A routed to IRQ 7 > Region 0: [virtual] Memory at d9000000 (32-bit, > non-prefetchable) [disabled] > Region 1: [virtual] Memory at d9001000 (32-bit, > non-prefetchable) [disabled] > > It is now listing memory in two locations, but listing them as disabled. Disabled is ok, since the driver enables the device (and the regions) when it starts. > It's also listing itself as non-I/O and non-Memory capable (I/O-, Mem-). However, this is not good. The driver doesn't do anything about this, although it could. I tried playing with setpci on my machine, and managed to get my board into the condition yours is in, so I assume that setpci can get it out of this condition as well. I preferred the easier "reboot". "setpci -s 0:a COMMAND=0x0017" is probably a good place to start. > With both cards plugged in, the PCI-DIO-96 no longer requests any space > whatsoever: lspci -vv -s 0:a reports This is very bad. I'm guessing a lot of this is your BIOS's fault, and Linux and/or Comedi is not cleaning up the mess. Or, it could just be a bug in your particular choice of Linux version. dave...
Received on 2002-06-04Z22:30:34