On Fri, 12 Feb 1999, Arun Khan wrote:
> What is the procedure when the driver is built into the kernel as opposed
> to using the module? I have this situation - where in Linuxconf tries to
> insert th module and I get "device busy ..." message.
Linuxconf won't try to insert the module if the built-in driver as
detected an adaptor. Linuxconf only try to load a module if the
corresponding network device is missing. For example, if you have a
builtin driver for ethernet and the driver detects one adaptor, eth0 will
be available. Linuxconf won't try to load any module for eth0 since there
is already one.
I guess that in your care, even the builtin driver can't probe the device
properly (why I don't know).
After booting, you will see that /proc/net/dev only contain the lo device
and no eth0. This means that the driver did not probed anything.
---------------------------------------------------------
Jacques Gelinas <[EMAIL PROTECTED]>
Check out Linuxconf at http://www.solucorp.qc.ca/linuxconf
New modules: mgettyconf, managerpm
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
