Yes. The command that got it to go is: `sudo iwconfig wifi0 essid myssid key mywe-pkey-xx commit && sudo dhclient`
Once that command runs, I see the applet in the notification tray where it seems to function normally. The only log I can get from it comes from syslog as follows, the bug link doesn't seem to help: Oct 13 19:44:30 dumpster NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Oct 13 19:49:07 dumpster NetworkManager: <info> HAL disappeared Oct 13 19:49:11 dumpster NetworkManager: <info> HAL re-appeared Oct 13 19:52:06 dumpster NetworkManager: <info> HAL disappeared Oct 13 19:52:08 dumpster NetworkManager: <info> HAL re-appeared Oct 13 19:56:40 dumpster NetworkManager: <info> starting... Oct 13 19:56:40 dumpster NetworkManager: <info> eth0: driver is 'e1000'. Oct 13 19:56:40 dumpster NetworkManager: <info> Found new Ethernet device 'eth0'. Oct 13 19:56:40 dumpster NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_0d_60_77_ce_20 Oct 13 19:56:40 dumpster NetworkManager: <info> eth1: driver is 'airo'. Oct 13 19:56:40 dumpster NetworkManager: <info> eth1: driver does not support SSID scans (scan_capa 0x00). Oct 13 19:56:40 dumpster NetworkManager: <info> Found new 802.11 WiFi device 'eth1'. Oct 13 19:56:40 dumpster NetworkManager: <info> (eth1): exported as /org/freedesktop/Hal/devices/net_00_02_8a_ea_3d_02 Oct 13 19:56:40 dumpster NetworkManager: <info> Trying to start the supplicant... Oct 13 19:56:40 dumpster NetworkManager: <info> Trying to start the system settings daemon... Oct 13 19:56:40 dumpster NetworkManager: <info> (eth1): supplicant manager is n ow in state 1 (from 0). Oct 13 19:56:41 dumpster nm-system-settings: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. Oct 13 19:56:41 dumpster nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Oct 13 19:56:41 dumpster NetworkManager: <info> (eth0): now unmanaged Oct 13 19:56:44 dumpster NetworkManager: <info> (eth1): device state change: 1 -> 2 Oct 13 19:56:44 dumpster NetworkManager: <info> (eth1): bringing up device. Oct 13 19:56:44 dumpster NetworkManager: <info> (eth1): preparing device. Oct 13 19:56:44 dumpster NetworkManager: <info> (eth1): deactivating device. Oct 13 19:56:44 dumpster NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Oct 13 19:56:44 dumpster NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Oct 13 19:56:44 dumpster NetworkManager: <info> (eth1): device state change: 2 -> 3 Oct 13 19:56:44 dumpster NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) On Mon, 2008-10-13 at 21:57 -0400, Vern Ceder wrote: > Jon wrote: > > The strange part is that once I get the network up using that, the > > nm-applet appears in the notification area with the signal strength info > > like it usually does. > > > > Could this be an issue with nm-applet starting and not finding some > > needed service or other dependency? > > Hmmm... it kinda sounds like it... > > I wonder if it's a permissions problem... I'm assuming you had to sudo > to configure the card manually? Neither iwconfig nor dhclient will run > correctly as the user... > > Vern > > > On Mon, 2008-10-13 at 20:56 -0400, Vern Ceder wrote: > >> Hey Jon, > >> > >> Have you tried killing nm-applet and then running it from the > >> commandline? It's possible it might print an error message to the > >> console... > >> > >> As far as configuring wifi from the commandline, iwlist, iwconfig and > >> dhclient would be the three things I would use... iwlist scanning will > >> show you the info on access points, iwlist will take care of > >> associating, etc. and of course dhclient gets an ip address. > >> > >> Cheers, > >> Vern > >> > >> Jon wrote: > >>> I'm running the Ibex beta on my laptop (IBM T40) and an update applied > >>> yesterday caused the network manager applet to no longer function. I > >>> have applied updates today and it hasn't fixed it. So I'm trying to see > >>> if I can find an existing bug for it or at least sort out how to provide > >>> relevant info. > >>> > >>> According to `ps aux | grep nm` nm-applet is running with the > >>> --sm-disable flag set. nm-applet does not appear in either the > >>> notification area nor the applet list for the Gnome panel. Attempting to > >>> kill and restart nm-applet yields no output nor responsiveness. > >>> nm-applet has no manpage. Wired network works just fine. > >>> > >>> Any ideas for where to start to find useful info for this issue? > >>> > >>> How would I configure my wireless card manually from the terminal? I > >>> have a hidden SSID and WEP encryption. > >>> > _______________________________________________ Fwlug mailing list [email protected] http://fortwaynelug.org/mailman/listinfo/fwlug_fortwaynelug.org
