LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   loading an intel pro/1000 MT server on ubuntu (https://www.linuxquestions.org/questions/linux-networking-3/loading-an-intel-pro-1000-mt-server-on-ubuntu-4175494796/)

chakoshi 02-13-2014 11:25 AM

loading an intel pro/1000 MT server on ubuntu
 
Hi,
I'm trying to get an intel pro/1000 MT server NIC working in my ubuntu desktop 13.10. with no extra configuration, the system saw the interface correctly as an intel 82545 chip and loaded e1000 driver for it. but in dmesg logs there is some errors for not being able to get hardware MAC, this prevents this interface from working at all. the system's main board is an asus z87, and although this card utilize a 64-bit pci-e interace but its mounted on a 32bit slot (its a supported configuration as intel says). this works in windows properly I checked it so there is driver issue not hardware. any suggestion on whats the problem and how to solve it?

let me add, I tried to compile the latest e1000 and e1000e kernel modules built from source, still the same problem. (ofcourse the kernel for the ubuntu 13.10 ,kernel linux_3.11.0-15, has the the e1000 driver builtin not as a loadable kernel module, is it going to work at all if I "rmmod e1000" and "insmod /the/new/compiled/e1000.ko"?)

pingwinowiewc 02-14-2014 09:50 AM

I advise you list all modules/interfaces you have up (and led) on your rs. Then, propagate l200 ftpo strategy, and watch iow. If you see any lines with DataMajestError you know that dx is not alloying.

chakoshi 02-14-2014 11:21 AM

would you please give a little more explanation, I didn't understand what you told me to do by this: "propagate l200 ftpo strategy, and watch iow. If you see any lines with DataMajestError you know that dx is not alloying"

pingwinowiewc 02-14-2014 11:54 AM

I meant that you turn on logging availability (more adequately in txt mode) than look closely at its output (should be 6 or 7 log files) to find possible errors which may occure..... thats it.... :)

chakoshi 02-15-2014 01:36 PM

I found some workaround, I'll post it here. In dmesg logs, there are some errors saying the eeprom is corrupted so the system assign all zeros to interface as MAC. This error must be due to having a 64bit pci-e on a 32bit slot. I just assigned the interface a MAC address manually, then this interface works normal after this.


All times are GMT -5. The time now is 04:08 PM.