Hi,
I think that is *exactly* how I do start NetworkManagerInfo -- from a command line from within a gnome-terminal. Should I do it from the "Run
Application..."? Yes the NetworkManager daemon is running, and no, netplugd is not.
(I've been looking for info on how/where to start NetworkManagerInfo because I figured I must be doing it wrong). I was just chalking it up to the
"oddness" in the prism54 driver. To me it feels like there is a race or at least a bad sequence of events when it comes to the interaction between the
kernel/hotplug hal and NetworkManager for wireless cards that load firmware. FWIW hal always gets the wrong MAC address for my prism54 card --
unless I restart hald while the card is inserted. The iw* tools and ifconfig all report the correct MAC address for the card. So I was thinking that
hald was trying to get the MAC before it really could because of the loading of the firmware, that plus it usually takes 3 attempts for the firmware
to load in the first place -- which I also think is caused by a race condition -- I can't prove that yet, but it feels that way. -- Sure that is just
speculation but there is definitely something wrong between the those 3 components. --- Where exactly the problem lies I don't know, but I do know
100% for sure that there IS a bug in its sysfs or kobject kset->hotplug_ops callbacks implementation in the prism54 driver, as I witnessed myself.
I specifically haven't opened a NetworkManager bug b/c I was chalking up it to the above. --
Sorry for going off topic. -- I don't want to hijack this thread.
Thanks, Andrew
Dan Williams wrote:
On Wed, 20 Oct 2004, Andrew wrote:
I am running udev-039-3 and hal 0.4.0-4. So, let me ask if you are running NetworkManager or are you just doing the equiv of manual system-config-network? For me NetworkManager just drives me nuts as I get 3 or more notification applets (and if I don't kill them all before I logout), I get even more the next time I log in.
Could it be NetworkManager?
Andrew,
That's probably because they are in your session. Use
gnome-session-properties to remove all instances of NetworkManagerInfo and
NetworkManagerNotification, and then run NetworkManagerInfo once from the
command-line.
Dan