LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Intel 82574L Gigabit LAN Not Functioning (https://www.linuxquestions.org/questions/linux-hardware-18/intel-82574l-gigabit-lan-not-functioning-4175583193/)

unassailable 06-27-2016 03:16 PM

Intel 82574L Gigabit LAN Not Functioning
 
Quick search of the forum showed no similar threads, sorry if this is covered elsewhere.

Embedded system has two Intel Ethernet controllers, 1 82574L and 1 82583V, running on Debian 7.11, kernel 3.2.0.4.

The 82583V functions correctly using the e1000e driver and gives me a connection via DHCP and static IP.

The 82574L does not. I can see the device in lspci, the e1000e driver is loaded correctly and I can even configure the network in ifconfig. But both static IP and DHCP yield no connection.

I checked the Intel driver site and it says that if the system has trouble with MSI/MSI-X interrupts to disable them on compilation. But checking /proc/interrupts shows both network adapters, so I assume this is not the issue.

No errors/warnings in /var/log/messages or dmesg. Verified cabling is good.

I'm at a loss of how else to diagnose this controller. Anyone have any ideas? Any help is appreciated.

Rinndalir 06-27-2016 03:24 PM

What criteria are you using to determine "not functioning"?

unassailable 06-27-2016 03:43 PM

No activity on the network. Unable to ping network devices. No sign of packets being sent, received or dropped. No connectivity or activity light on the physical Ethernet port.

Rinndalir 06-27-2016 03:47 PM

Check your bios and if a desktop pc check your motherboard docs. Try a new kernel. Sounds like an interrupt problem.

unassailable 06-27-2016 03:49 PM

I'll try recompiling the drivers tomorrow with interrupts disabled.

Out of curiosity, what makes you say it's an interrupt problem?

beachboy2 06-28-2016 08:10 AM

unassailable,

This may help you:

http://www.linuxquestions.org/questi...lution-831364/

unassailable 06-28-2016 08:58 AM

Quote:

Originally Posted by Rinndalir (Post 5567063)
Check your bios and if a desktop pc check your motherboard docs. Try a new kernel. Sounds like an interrupt problem.

Tried recompiling the drivers with interrupts disabled. After setting:
Code:

pcie_aspm=off e1000e.IntMode=1,1 e1000e.InterruptThrottleRate=10000,10000 acpi=off
to kernel parameters, still not working.

Quote:

Originally Posted by beachboy2 (Post 5567342)

Thanks for the link, but I have already tried that solution.

unassailable 06-28-2016 11:57 AM

1 Attachment(s)
Thank you both for trying to help out. Turns out it was a hardware issue, take a look at pin 2 in the attached image.

Attachment 22242

I straightened it out and everything works as it should.

Counter 11-08-2018 01:37 PM

Hey.
I know that this topic is very, very old, but I think I should share my experience.
Background: my network card, based on the NIC 82574L, built into the Intel D2500NN motherboard, died for an unknown reason after changing OS from Windows to Linux Ubuntu Desktop.
The BIOS did not show the mac address of the network card and Windows Device Manager showed "error code 10".

I came to the conclusion that the memory was somehow damaged. Fortunately, I had another exactly the same motherboard,
so I was able to dump the EEPROM memory image from the working motherboard and flash it into a non-working one.
Since I spent a large amount of my free time solving this issue, I want to help people who will follow my path.
I'll attach the MS-DOS utility for flashing Intel NIC's and the EEPROM image for 82574L.
I have replaced the MAC address with zeros (Its the first three bytes of EEPROM image). You can put there your own, or flash EEPROM without affecting yours with special command on EEUPDATE tool.
Wish you good luck.
https://drive.google.com/file/d/1PXY...ew?usp=sharing

wsy 11-28-2018 01:00 PM

Quote:

Originally Posted by Counter (Post 5924157)
Hey.
I know that this topic is very, very old, but I think I should share my experience.
Background: my network card, based on the NIC 82574L, built into the Intel D2500NN motherboard, died for an unknown reason after changing OS from Windows to Linux Ubuntu Desktop.
The BIOS did not show the mac address of the network card and Windows Device Manager showed "error code 10".

I came to the conclusion that the memory was somehow damaged. Fortunately, I had another exactly the same motherboard,
so I was able to dump the EEPROM memory image from the working motherboard and flash it into a non-working one.
Since I spent a large amount of my free time solving this issue, I want to help people who will follow my path.
I'll attach the MS-DOS utility for flashing Intel NIC's and the EEPROM image for 82574L.
I have replaced the MAC address with zeros (Its the first three bytes of EEPROM image). You can put there your own, or flash EEPROM without affecting yours with special command on EEUPDATE tool.
Wish you good luck.

This fixed my broken nic. Thank you very much!


All times are GMT -5. The time now is 06:48 AM.