NetworkManager Issues

Kyrre Ness Sjobak kyrre at solution-forge.net
Wed Nov 3 15:05:33 UTC 2004


But i still should show up in syslog?

ons, 03.11.2004 kl. 16.02 skrev Dan Williams:
> On Wed, 2004-11-03 at 00:42 -0500, Jason 'vanRijn' Kasper wrote:
> > - NetworkManager has to have the mode set to "Managed"
> > in /etc/sysconfig/network-scripts/ifcfg-eth1, from what I saw.  This
> > conflicts with FC's insistence on making the mode "Auto" so that I can
> > change the channel to 6 and the rate to Auto
> > (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133500).
> 
> NM always sets the mode to Managed/Infrastructure.  You should not be
> able to change the channel on the card, since when you put the card into
> Infrastructure mode, it will _automatically_ switch to the channel of
> the ESSID you set on the card.  There is no need to manually set the
> channel and rate unless:
> 
> 1) your AP is broken
> 2) your card/firmware is broken
> 3) you're using Ad-Hoc mode, in which case you aren't using NM
> 
> What do you need to explicitly set the channel for?
> 
> > - unless I log into gnome as root, NetworkManagerInfo hard-locks-up my
> > laptop.  No, I cannot give a stack trace or anything useful to debug
> > this.  Specifically, what happens is I start NetworkManagerInfo, click
> > on its menu, choose the SID of my network, and then sometimes
> > immediately and sometimes after the error dialog box comes up to say
> > "can't connect to this network" (it does NOT ask me for a WEP key if I'm
> > not root), my laptop freezes hard.  Mouse doesn't respond, kernel
> > doesn't respond, etc., etc.
> 
> Previously there were issues wtih the IPv6 stack and wireless drivers in
> the _kernel_ (#rh135432# in bugzilla), these may be fixed.  They caused
> a hard-lock of machine where a panic would print to the console, but of
> course you couldn't see it because you were in X.
> 
> Dan




More information about the test mailing list