Bug 21192 - on-board NIC non-functional if EFI uses it first
on-board NIC non-functional if EFI uses it first
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
ia64 Linux
high Severity high
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
Florence Gold
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-11-21 12:35 EST by Matt Domsch
Modified: 2005-10-31 17:00 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-01-11 16:06:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
nicreset.efi (577.00 KB, application/octet-stream)
2000-11-21 12:36 EST, Matt Domsch
no flags Details

  None (edit)
Description Matt Domsch 2000-11-21 12:35:37 EST
On Intel Lion systems, all BIOS versions <= 1063 at least, Linux cannot 
communicate via the on-board Intel NIC if EFI first tried to use the NIC.  
As ACPI PXE boot is now enabled in the BIOS, a system may try to PXE boot, 
fail, and then drop to the EFI shell and start Linux.  In this case, the 
NIC driver (e100 or eepro100) loads just fine, but does not work.  No data 
is transmitted or received.

Dell developed a 'nicreset.efi' application to reset the NIC prior to 
starting Linux, which solves this problem.  I'm encouraging Dell to 
release the code under a GPL-compatable license, so that at worst case the 
Linux distributions may include this app in their loader, and best-case, 
we can fix the NIC drivers to do this automatically.
Comment 1 Matt Domsch 2000-11-21 12:36:57 EST
Created attachment 5623 [details]
nicreset.efi
Comment 2 Glen Foster 2001-01-11 16:03:22 EST
This defect is considered MUST-FIX for Florence Gold release
Comment 3 Bill Nottingham 2001-01-11 16:06:11 EST
a) this is alread fixed in ELI
b) it's a firmware bug anyways, that is fixed in recent firmware.

I should have closed this a while ago. :)
Comment 4 Matt Domsch 2001-01-11 16:42:05 EST
Agreed, this is fixed in the 12/07 release.

Note You need to log in before you can comment on or make changes to this bug.