Description of problem: I install Fedora 7 test 3 and run 'ifconfig' and no eth0 device exists! I have a broadcom network card using b44 module. I remove and reload b44 module - than eth0 device exists for a minute or two and I can use it - browse the net and get updates. After no more than 2 minutes eth0 device dissapears and I can't use it anymore. I have tested this on default kernel and also the last one that is available today. On both kernels I see the same behavior. Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1. Install Fedora 7 test 3 2. Try to use the network card 3. Actual results: Expected results: Working network. Additional info:
Could you attach the output of running 'dmesg' and also 'lspci'? Thanks!
Ok, I found out something else. It seams that there is a bug somewhere but not the one I described in the first post. Sorry for that. The problem was that now my broadcom network card, lspci: 02:0e.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) is eth1 and not etho anymore! This probably happened after first kernel upgrade, because after the install it was eth0. I deleted all network scripts in: /etc/sysconfig/network-scripts/ and created new ones. But I still have problems, after the boot I don't have working network. I remove and reload b44 kernel module and network work from then on. Now I have 2.6.20-1.3059.fc7 kernel.
Created attachment 152775 [details] dmesg output dmesg output
Created attachment 152776 [details] modprobe.conf modprobe config file
any ideas?
Your modprobe.conf file has "alias eth1 b44" and has "#alias eth0 b44" (i.e. the eth0 version is commented out). Is this a change you made intentionally?
Yes I added comment for eth0. The default version was with both "alias eth1 b44" and also "alias eth0 b44" I didn't look at the modprobe.conf before this issue so I don't know if before kernel upgrade there were both eth0 and eth1 tied with b44. I hoped that atleast eth1 would work fine if I comment eth0 but that didn't help. I'll try not to delete again all networking scripts and leave only eth0 alias in modprobe.conf be back after the reboot.
I updated to another kernel - 2.6.20-1.3079.fc7 THis is not a kernel bug. Because everything works fine now. My card is eth0 and works after the reboot with no problem. Maybe it is a system-config-network bug? This is a snow-stopper for new linux users so should be escalated to a high level - and fixed swiftly.
the eth0/eth1 switching was caused by an anaconda bug which should now be fixed. do a reinstall when test4 comes out, it should be fixed. (or you could try a rawhide install before then).
Ok, I will. thanks.