Red Hat Bugzilla – Bug 106962
network driver 8139too failed to load
Last modified: 2007-11-30 17:10:32 EST
Description of problem:
network driver 8139too failed to load because of broken dependencies
Version-Release number of selected component (if applicable):
severn-disk1 dated 10/10/03
Steps to Reproduce:
1. network card requires 8139too driver.
2. make bootdisk.img and drvnet.img
3. select NFS install
4. load drivers disk and select RealTek 8139 (8139too)
driver failed to load, observe error messages in VT3
driver loads with no errors
Workaround: load 8139cp which will cause mii to be correctly loaded. 8139cp will
fail but it does not matter. Then load 8139too again, successfully, because mii
has already been loaded.
8139too should have a dependency on mii.o properly -- Can you do this sequence
and then attach /tmp/anaconda.log from after you get to the second stage of the
install (when you can switch to tty2 and grab the file from the shell)
I am away from that system currently. Attempt to load 8139cp clearly indicated
required mii.o and attempt to load 8139too clearly indicated no dependent modules.
In addition my network card was not autodetected - the first time ever for a lot
of releases tested on this hardware. There might be a relation with 106649 ...
Oddly, the modules.dep on drvnet.img has duplicate entries.
Loading 8139too by hand on a test box here properly loads mii.o first with the
current tree. Seeing the /tmp/anaconda.log and /tmp/syslog from this would be
I see a simillar issue. The card worked no problem until I added a usb
nic card. If I boot without the usb nic alias eth0 8139too is fine.
If I boot with the usb nic I have to alias the 8139too to eth1 in
modules.conf as well as swapping devices in ifcfg-eth0 amd ifcfg-eth1.
This is with latest packages, basically Fedora 1.
Created attachment 96085 [details]
Fixes RTL8139 load failure
I have just added an attachment that may fix this sort of problem.
Forgot to add the test comment though so here it is.
Problem seemed to be lack of mii in the initrd.img modules set.
No, mii shouldn't have to be explicitly listed. It get pulls in due
to the dependencies in modules.dep.
I'll soon try Fedora install on original system and let you know.
i just did a nfs install of FC2 test3 on a machine that uses 8139too
nic and had no issues at all with network related items