The second searches out the driver associated with each pci device (only a few lines are relevant).Īs a test procedure I would suggest this:Īlso look through the dmesg output like this: The first uses the socket interface and asks for all the interfaces. So there are two ways to search to see if the interface was created. It's entirely possible that NM is too dumb to recognize a new interface after it's started (as yo usurmised). Network Manager is a very complex and IMO still-too-fragile bit of code. Next - you should ignore network manager until you get the system to report the interface correctly. My first hunch would be that the e1000 (not e1000e) would be the right one. I have little faith in the website that Stoat & Google report. This is the exact line from lspci.Ġ0:19.0 Ethernet controller : Intel Corporation Device (rev 05)Īny other ideas? Is this device too new for the e1000e driver?įirst, I'm not certain that the e1000e supports this device without modification. I tried adding the ven/dev id to the new_id like stevea suggested and it didn't seem to have any effect. However, after restarting NetworkManager there is still no network device listed. I tried what Stoat suggested and the driver seems to load fine. Last edited by stevea 3rd November 2009 at 10:19 PM. IF that works make a script in /etc/sysconfog/modules/ The filename should be "e1000e.modules" You might want to find a better place for these commands (perhaps in /etc/init.d/network) otherwise the networkĬonfiguration will precede the driver installation. Just edit this script and add the commands to end of file. If that works then you can add the two lines to /etc/rc.d/rc.local Load the e1000e driver using modprobe as Stoat described, the nyou can add your ID to the driver list like this:Įcho "8086 10f0" > /sys/bus/pci/drivers/e1000e/new_id Your device ID has not yet been added to the 2.6.30.9 kernel. Something fail - it may be that the udevd tables are missing an entry. To see exactly what happened when the kernel initialized and there was an attempt to find a driver for the device. If the modprobe that Stoat suggest DOES work, then please look the the output of dmesg If that doesn't work then please let us know.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |