LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
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


Reply
  Search this Thread
Old 06-27-2016, 03:16 PM   #1
unassailable
Member
 
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42

Rep: Reputation: 2
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.
 
Old 06-27-2016, 03:24 PM   #2
Rinndalir
Member
 
Registered: Sep 2015
Posts: 733

Rep: Reputation: Disabled
What criteria are you using to determine "not functioning"?
 
Old 06-27-2016, 03:43 PM   #3
unassailable
Member
 
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42

Original Poster
Rep: Reputation: 2
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.
 
Old 06-27-2016, 03:47 PM   #4
Rinndalir
Member
 
Registered: Sep 2015
Posts: 733

Rep: Reputation: Disabled
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.
Old 06-27-2016, 03:49 PM   #5
unassailable
Member
 
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42

Original Poster
Rep: Reputation: 2
I'll try recompiling the drivers tomorrow with interrupts disabled.

Out of curiosity, what makes you say it's an interrupt problem?
 
Old 06-28-2016, 08:10 AM   #6
beachboy2
Senior Member
 
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 20.1 MATE, MX-19.3, antiX, EndeavourOS
Posts: 3,340
Blog Entries: 17

Rep: Reputation: 1264Reputation: 1264Reputation: 1264Reputation: 1264Reputation: 1264Reputation: 1264Reputation: 1264Reputation: 1264Reputation: 1264
unassailable,

This may help you:

http://www.linuxquestions.org/questi...lution-831364/
 
1 members found this post helpful.
Old 06-28-2016, 08:58 AM   #7
unassailable
Member
 
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Rinndalir View Post
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 View Post
Thanks for the link, but I have already tried that solution.
 
Old 06-28-2016, 11:57 AM   #8
unassailable
Member
 
Registered: May 2012
Distribution: gentoo, debian, qubes, openELEC
Posts: 42

Original Poster
Rep: Reputation: 2
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.

Click image for larger version

Name:	IMG_20160628_124634.jpg
Views:	562
Size:	231.7 KB
ID:	22242

I straightened it out and everything works as it should.
 
Old 11-08-2018, 01:37 PM   #9
Counter
LQ Newbie
 
Registered: Nov 2018
Posts: 1

Rep: Reputation: Disabled
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.
Old 11-28-2018, 01:00 PM   #10
wsy
LQ Newbie
 
Registered: Nov 2018
Posts: 1

Rep: Reputation: Disabled
Thumbs up

Quote:
Originally Posted by Counter View Post
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!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Confusion between PCI and PCIE network adapter... 82574L Gigabit Network Connection diablo046 Linux - Newbie 6 08-26-2014 09:49 AM
Intel 82574L Gigabit Ethernet on Ubuntu 8.04 baddah Linux - Hardware 3 04-13-2012 01:21 AM
[SOLVED] Intel 82574L Gigabit network card - issues and resolution unkie888 Linux - Hardware 4 04-13-2012 01:21 AM
Intel Gigabit lan on Woody Aevron Debian 1 07-09-2004 05:48 AM
Intel Onboard Gigabit LAN wombatman Linux - Hardware 7 08-17-2003 10:41 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:07 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration