Red Hat Bugzilla – Bug 74723
anaconda/kernel doesn't detect Intel Pro 100 adapter (eepro100) during install.
Last modified: 2014-03-16 22:31:14 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
My Intel Pro 100 NIC is not detected during install. This causes some
interesting problems for firstboot (trying to register with RHN). Once Red Hat
8.0 was installed, and even rebooted a few times, a manual run of "kudzu"
detected the eepro100. Before running kduzu, I was able to modprobe eepro100
and configure my network.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot from Red Hat Linux 8.0 CD 1
2. Install Red Hat Linux 8.0
Actual Results: eepro100 is not detected, I'm never presented with options to
configure my network, no network when Red Hat Linux 8.0 is booted.
Expected Results: NIC detected, allowed to configure, used upon boot.
This could be because I have my PC bios set for "pnp OS=yes". The mainboard is
an Asus A7m266, the CPU is an Athlon T-Bird 1.33ghz/266fsb.
My 'eepro100' was detected properly on boot. What can I provide that might
help determine the differences? Unless it was an anomoly or what-not. Cheers,
Could you attach the output from lspci?
Also could you attach /etc/sysconfig/hwconf on the system which the network card
Created attachment 77944 [details]
Lspci output on a laptop w/ eepro100 driver.
Created attachment 77945 [details]
Hwconf of same lappy.
Attached w/ data from a lappy that uses the eepro100 drivers. I'll attach from
the desktop that it all worked fine from (w/ eepro100) as well as soon as I'm
done re-installing (test box for other things). Cheers, -Ali
Created attachment 77984 [details]
LSPCI output from the machine that it didn't detect at install time.
Thanks I'll forward this to the hw database owner.
That's already in the DB; there's really no reason it shouldn't be detected. Can
you post the output of lspci -v?
Created attachment 81967 [details]
lspci -v of the box where eepro100 and emu10k1 were not detected until probed.
Is this lspci from before or after the modules were probed and loaded?
This is after. After I modprobed emu10k1 and eepro100, then I ran kudzu and
kudzu picked them up. Want me to rmmod those 2 modules and lspci -v again?
Hm, an lspci of a fresh bootup without them ever loaded would be best.
So far this has been unreproducable for me. Strange. Closing bug.