Fedora 10 wireless timing out on bootup

[jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org (Jarod Wilson)]

On Thursday 05 March 2009 16:47:04 Don Levey wrote:
> Jarod Wilson wrote:
> > On Thursday 05 March 2009 15:37:50 Jerry Feldman wrote:
> >> On 03/05/2009 02:47 PM, Jarod Wilson wrote:
> >>> On Thursday 05 March 2009 14:41:30 Matthew Gillen wrote:
> >>>
> >>>> Randy Cole wrote:
> >>>>
> >>>>> Under Fedora 10, my wireless is identified as eth1.  On bootup, stalls
> >>>>> for a full minute until something times out.
> >>>>>
> >>>>> How can I prevent Fedora from waiting?  This doesn't seem to be a
> >>>>> problem in Ubuntu.
> >>>>>
> >>>> Try running system-config-network, and check the box that says "Controlled by
> >>>> NetworkManager", and un-check the box that says "Activate when computer starts".
> >>>>
> >>>> The latter option is usually redundant with the former.
> >>>>
> >>> Just to explain a bit more what's going on here... Since the wireless device
> >>> is identified as eth1, rather than wlan0, NM probably thinks its a wired
> >>> connection, and thus tries to start it earlier. Is that an out-of-tree wireless
> >>> driver by chance?
> >>>
> >>>
> >> On my Ubuntu system, it also comes up as eth1, and NM has no problem in
> >> identifying it.
> >
> > Its not so much a matter of identifying it once you're at the desktop, its
> > a matter of what's done with it during boot up, because Fedora 10 actually
> > uses NetworkManager to bring up your wired interfaces prior to the desktop
> > being available.
> >
> 
> If Fedora used NetworkManager during boot-up, why does it fail to
> establish the connection then while it succeeds at the desktop?

Because pre-desktop, it doesn't have access to your user-specific keyring
that stores important information like SSID of the base station to connect
to, wep/wpa key, etc.

-- 
Jarod Wilson
jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org