Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
06-27-2016, 03:16 PM
|
#1
|
Member
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42
Rep:
|
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.
|
|
|
06-27-2016, 03:24 PM
|
#2
|
Member
Registered: Sep 2015
Posts: 733
Rep:
|
What criteria are you using to determine "not functioning"?
|
|
|
06-27-2016, 03:43 PM
|
#3
|
Member
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42
Original Poster
Rep:
|
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.
|
|
|
06-27-2016, 03:47 PM
|
#4
|
Member
Registered: Sep 2015
Posts: 733
Rep:
|
Check your bios and if a desktop pc check your motherboard docs. Try a new kernel. Sounds like an interrupt problem.
|
|
1 members found this post helpful.
|
06-27-2016, 03:49 PM
|
#5
|
Member
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42
Original Poster
Rep:
|
I'll try recompiling the drivers tomorrow with interrupts disabled.
Out of curiosity, what makes you say it's an interrupt problem?
|
|
|
06-28-2016, 08:10 AM
|
#6
|
Senior Member
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 22 MATE, Peppermint OS-Devuan, EndeavourOS
Posts: 4,198
|
|
|
1 members found this post helpful.
|
06-28-2016, 08:58 AM
|
#7
|
Member
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42
Original Poster
Rep:
|
Quote:
Originally Posted by Rinndalir
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
|
Thanks for the link, but I have already tried that solution.
|
|
|
06-28-2016, 11:57 AM
|
#8
|
Member
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42
Original Poster
Rep:
|
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.
I straightened it out and everything works as it should.
|
|
|
11-08-2018, 01:37 PM
|
#9
|
LQ Newbie
Registered: Nov 2018
Posts: 1
Rep:
|
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
Last edited by Counter; 11-10-2018 at 03:07 AM.
|
|
1 members found this post helpful.
|
11-28-2018, 01:00 PM
|
#10
|
LQ Newbie
Registered: Nov 2018
Posts: 1
Rep:
|
Quote:
Originally Posted by Counter
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 09:13 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|