|
Home > Archive > Red Hat General > June 2004 > missing eth1 freezes boot
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
missing eth1 freezes boot
|
|
| Stephan Goeldi 2004-06-20, 10:45 pm |
| my notebook has 2 ethernet cards, running with Fedora Core 2: eth0 is
built in, eth1 is a wireles card.
when I remove the wireless card and try to boot, the boot sequence stops
at the point, where the commands from /etc/rc.d/rc.local are executed
(setting essid etc. of the wireless card).
What bothers me is, that the boot sequence does not only give me an error
message, but the boot sequence freezes completely. Ctrl-C doesn't stop
anything. It just hangs there with the error message.
I think a workaround would be, to remove the commands from rc.local. But I
cannot find any documentation about setting up profiles which are
selectable at boot time.
Anyway, an error message should not freeze the complete boot process.
| |
| Take a Walk 2004-06-20, 10:45 pm |
| On Fri, 18 Jun 2004 10:12:12 +0200, Stephan Goeldi wrote:
> my notebook has 2 ethernet cards, running with Fedora Core 2: eth0 is
> built in, eth1 is a wireles card.
>
> when I remove the wireless card and try to boot, the boot sequence stops
> at the point, where the commands from /etc/rc.d/rc.local are executed
> (setting essid etc. of the wireless card).
>
> What bothers me is, that the boot sequence does not only give me an error
> message, but the boot sequence freezes completely. Ctrl-C doesn't stop
> anything. It just hangs there with the error message.
>
> I think a workaround would be, to remove the commands from rc.local. But I
> cannot find any documentation about setting up profiles which are
> selectable at boot time.
>
> Anyway, an error message should not freeze the complete boot process.
Are you waiting long enough? Mine takes a while in such a situation, but
eventually resumes boot.
Also, do you have Kudzu enabled and running before the activation of
eth1-if it was it should pick up the missing eth1 and prevent the problem
anyway.
|
|
|
|
|