Bug 861 - Intel Etherexpress 100(B?) seems to be broken in kernel-2.0.36-3
Summary: Intel Etherexpress 100(B?) seems to be broken in kernel-2.0.36-3
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 5.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-01-18 07:04 UTC by ajames
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-01-18 21:23:38 UTC

Attachments (Terms of Use)

Description ajames 1999-01-18 07:04:01 UTC
I am using 4 IBM Intellistations with Redhat 5.2.  All
were working fine.  When I installed the
kernel-2.0.36-3.i386.rpm package (from your updates ftp
site), the new kernel slotted in just fine.  However, upon
reboot, no ethernet card was seen.  (localhost login: )

To verify it was not a hardware problem, I promptly booted
the install disks, and the installation dialogues told me
that I had an Intel EtherExpress Pro/100 (which I do).  I
again tried to boot the 2.0.36-3 kernel from my hard disk,
and again, no network.

Unfortunately, I didn't opt to install mtools, so I don't
even know how to copy the 2.0.36-0.7 kernel from an other
machine to this one.  I will probably end up re-installing
the entire system tonight, but wanted to let you know
because others are probably having this problem.


P.S.  Its possible that I might have the 100B which you list
as "unsupported but compatable."  I'm really not sure if
these machines come with the standard Pro/100 or
Pro/100B....  even if it is the B, it would be nice for you
to go up to a higher kernel where ieep/100 support is

Comment 1 David Lawrence 1999-01-18 21:23:59 UTC
I attempted to replicate this problem in our test lab with an Intel
EtherExpress Pro 10/100 PCI and was unable to get it to fail. I
started with a fresh install of 5.2 as shipped on CD. I then uograded
to the new 2.0.36-3 update RPM, edited lilo.conf to point to the new
kernel, re-ran lilo to enable the new setting, and then rebooted. The
Intel card was recognized and networking set up fine.

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