[driverloader] driverloader module will not load

Linuxant support support at linuxant.com
Wed Dec 3 18:24:19 EST 2003


Hi,

there seems to be a major problem with your PCI configuration.

When running "lspci", we see this error.

---
+ lspci -n
pcilib: Cannot open /proc/bus/pci/02/00.0
lspci: Unable to read 64 bytes of configuration space.
---


Also we can see this error in the "dmesg" output when you try to load the
"driverloader" module.

---
PCI: No IRQ known for interrupt pin A of device . Please try using
pci=biosirq.
: cache line size not set; forcing 8
driverloader: NdisWriteErrorLogEntry: ErrorCode=DRIVER_FAILURE
NumberOfErrorValues=1
driverloader: NdisWriteErrorLogEntry: ErrorValue 0=0xa
eth1: failed to initialize adapter (err = -5)
eth1: Failed to register net device (-5)
---


Please try the kernel boot parameter "pci=biosirq" as suggested. If it
doesn't work, you can try one of these options.


1) Play with the following kernel boot parameters:

"pci=noacpi", "acpi=off", "noapic" and/or "apm=off".


2) Configure and install a generic 2.4 kernel (from kernel.org) with the
ACPI patches found on this web site:

http://sf.net/projects/acpi


3) Configure and install a generic 2.6 kernel from ftp.kernel.org.


Please let us know about your results.

Regards,

Jean-Simon Durand
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


----- Original Message ----- 
From: "Richard Ozer" <rozer at pacbell.net>
To: <driverloader at lists.linuxant.com>
Sent: Wednesday, December 03, 2003 6:08 PM
Subject: [driverloader] driverloader module will not load


I get the dreaded "module: No such device" error when trying to modprobe
driverloader.  I have debian w/ kernel 2.4.22.  Card services load up fine,
the card is visible when polled using cardctl ident. It's a linksys
802.11g/broadcom.

I have ds, i82365, and pcmcia_core loaded.

I suspect I'm missing either a parameter or a kernel resource... or another
module is in conflict.  I sent my debug dump yesterday, but have not heard
anything yet.  Anyone else experience this problem?

Thanks
rozer at pacbell.net



More information about the driverloader mailing list