Hi,
My nics work fine and I can see which drivers they are using by using hwinfo and lsmod. I can also remove and add them with modprobe, I just dont know where they’re getting loaded. All it says in /etc/modprobe.conf is install eth0 /bin/true theres no alias for the network driver??
On 03/17/2011 06:06 AM, allywait wrote:
>
> Hi,
>
> My nics work fine and I can see which drivers they are using by using
> hwinfo and lsmod. I can also remove and add them with modprobe, I just
> dont know where they’re getting loaded. All it says in
> /etc/modprobe.conf is install eth0 /bin/true theres no alias for the
> network driver??
If you look at the output of the dmesg command, you will see the driver for your
PCI-based network devices starting just after the vga device driver and just
before the disk driver. USB devices start a little later. On my system, the
first line for the wired device is
[11.533051] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
and my USB wireless device is started at
[15.098756] rtl8192cu: MAC address: 00:1f:1f:c8:8e:cb
By comparison, /etc/boot.local is run at 21.44 seconds.
No thats not what im asking. In modprobe.conf there is no mention of the nic drivers, all it says is install eth0 /bin/true. It doesnt say anything about the specific drivers to be loaded, in which config file is that set?
On 03/17/2011 10:06 AM, allywait wrote:
>
> No thats not what im asking. In modprobe.conf there is no mention of the
> nic drivers, all it says is install eth0 /bin/true. It doesnt say
> anything about the specific drivers to be loaded, in which config file
> is that set?
It is set in a structure in the driver that tells the kernel what devices that
this driver handles. That is not handled by user space with any configuration
file, but by the kernel doing scans of the various buses. As I showed with the
dmesg outputs, this is all done long before user space is setup. If there are
two drivers that claim the same device, this problem is handled by blacklisting
the one you do not want.
Why do you want to change the specific driver for a device?
Im getting it now cheers. So when you up date a driver you just compile and install it and the kernel will pick up the fact that it is for that device, then you could black list the old driver, is that right?
So what is modprobe.conf doing now, wasnt that were you would list drivers to be loaded in the past, what is install eth0 /bin/true doing for example in my modprobe.conf file.
Cheers for your help.