Do you perhaps need to load the module for the NIC? I'm sure Ubuntu has a friendly little GUI hidden away somewhere, but I generally stuff the module name into /etc/modules and have done with it.
Of course, the trick is to find out which module it is. This might do the trick as a first pass by loading every non-"special" network driver module:
All one line: cd /lib/modules/`uname -r`/kernel/drivers/net
All one line: ls *.ko | sed s/.ko$ | awk {'print "modprobe "$1'} | sh
dmesg | less should then show you which module it is; look for messages about the relevant interface (eth0, I'm guessing?) preceded by a message about the relevant driver being loaded.
1 Comments:
Do you perhaps need to load the module for the NIC? I'm sure Ubuntu has a friendly little GUI hidden away somewhere, but I generally stuff the module name into /etc/modules and have done with it.
Of course, the trick is to find out which module it is. This might do the trick as a first pass by loading every non-"special" network driver module:
All one line:
cd /lib/modules/`uname -r`/kernel/drivers/net
All one line:
ls *.ko | sed s/.ko$ | awk {'print "modprobe "$1'} | sh
dmesg | less should then show you which module it is; look for messages about the relevant interface (eth0, I'm guessing?) preceded by a message about the relevant driver being loaded.
Post a Comment
<< Home