This is a discussion on ASUS P5LD2-VM integrated ethernet card within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hello everybody. I've upgraded my computer and it now has ASUS P5LD2-VM motherboard with built-in ethernet card. Winxp sees ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello everybody. I've upgraded my computer and it now has ASUS P5LD2-VM motherboard with built-in ethernet card. Winxp sees it properly, but my Linux Slackware 10.1 can not see it. I have kernel 2.4.29. I have ethernet 1000mb enabled in my kernel. After I googled, I found linux driver on ASUS site, I've downloaded it and compiled, file ...(path_to_linux_drivers).../drivers/net/e1000/e1000.o appeared. But when I try to insmod it, it doesn't load, and says that I have wrong IO or IRQ settings. But I use default settings, and I thought that the driver shoult detect it. I've tried to google more, but I can't find anything. What I have done wrong? wbr, lanka. |
| ||||
| > I've upgraded my computer and it now has ASUS P5LD2-VM motherboard with > built-in ethernet card. Winxp sees it properly, but my Linux Slackware > 10.1 can not see it. > I have kernel 2.4.29. That motherboard most likely has the intel ether express 1000 card, so yes the correct driver is e1000. Now the 2.4.29 kernel from Slack 10.1 does include the e1000 driver so you shouldn't have had to compile it separately ... but if that driver doesn't work by any chance, I'd suggest you get the latest 2.4.32 kernel and modules from -current (if you insist on staying with 2.4.x, that is - the drivers in 2.6.xx are certainly more up-to-date but that would be a more involved upgrade). > I have ethernet 1000mb enabled in my kernel. After I googled, I found > linux driver on ASUS site, I've downloaded it and compiled, file > ..(path_to_linux_drivers).../drivers/net/e1000/e1000.o appeared. > But when I try to insmod it, it doesn't load, and says that I have > wrong IO or IRQ settings. But I use default settings, and I thought > that the driver shoult detect it. As I said, in most cases you wouldn't need to compile an out-of-tree driver since the linux kernel has had a driver for that chip for some time. But anyway, no matter what driver you are trying to use, check these things: - does it show up in the output of the "lspci" commmand - what are the last several lines in the "dmesg" output when modprove e1000 fails. Also, since this is a new motherboard it might require that you have ACPI enabled in the kernel so that it's onboard components function properly. In which case, you'd need to get the bareacpi kernel. -- damjan |