Red Hat Bugzilla – Bug 64090
Second network interface not recognized at boot
Last modified: 2014-03-16 22:27:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
Description of problem:
I have a Dell latitude c810 with an internal wireless card and a xircom cardbus
When I boot the system with no cabel in the xircom, but the wireless within
range of a base station, the xircom appears on eth0 and the wireless as eth1,
but eth1 is not reporting an IP address. I even try dhcpcd -n for force a new
IP, but nothing. Clearly the xircom should be inactive since it isn't plugged
in, but the wireless should be active.
Only when I do 'cardctl eject 0', 'cardctl eject 1', 'cardctl insert 0' does the
wireless come up with a valid IP.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.do ifconfig eth0 and ifconfig eth1 to see that neither has an IP
Actual Results: the wireless card, eth1, doesn't have an IP
It seems that linux is having trouble recognizing the second interface.
That sounds more like a problem in the hotplug/kernel/initscripts area.
Reasigning it to initscripts (which sounds the most likely source of the problem).
Read ya, Phil
Please try to reproduce on a current OS.
I still can't get the second interface, but for slightly different
reasons. I've since moved to a Dell C840 with a built in ethernet and
wireless. When I boot with a stock Fedora 2, the wireless should be
at eth1, but it never appears. I have to put a card eject and insert
into the rc.local to get it to appear.
I recall there being some other bug reports about this being a init
scripts problem with the pcmcia system being started after the
network, but I don't recall the exact reason or bugzilla id: perhaps
Yeah, that's bug 121742.
*** This bug has been marked as a duplicate of 121742 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.