On Wed, Nov 18, 2009 at 4:00 PM, Daniel Fetchinson <[email protected]> wrote: >>> >> >> Hi folks, I have a super weird situation on my Sony VAIO VGN-FZ240E: >>> >> >> >>> >> >> I have Fedora 8 which ships network manager 0.7.0-0.5.svn3030 and >>> >> >> until yesterday everything has been working perfectly well, >>> >> >> nm-applet >>> >> >> connected to both wired and wireless networks without a problem. And >>> >> >> the strange thing is that I didn't do anything, no new installs, no >>> >> >> upgrades, absolutely nothing (that I know of). >>> >> > >>> >> > What's the output of 'nm-tool' when that command is run in a >>> >> > terminal, >>> >> > when you're experiencing the problem? >>> >> >>> >> Thanks for the answer, so nm-tool says this: >>> >> >>> >> >>> >> NetworkManager Tool >>> >> >>> >> State: disconnected >>> >> >>> >> - Device: eth0 >>> >> ---------------------------------------------------------------- >>> >> Type: Wired >>> >> Driver: sky2 >>> >> Active: no >>> >> HW Address: 00:1A:80:49:CF:34 >>> >> >>> >> Capabilities: >>> >> Supported: yes >>> >> Carrier Detect: yes >>> >> Speed: 100 Mb/s >>> >> >>> >> Wired Settings >>> >> >>> >> >>> >> - Device: wlan0 >>> >> ---------------------------------------------------------------- >>> >> Type: 802.11 Wireless >>> >> Driver: iwl4965 >>> >> Active: no >>> >> HW Address: 00:13:E8:87:8E:4F >>> >> >>> >> Capabilities: >>> >> Supported: yes >>> >> >>> >> Wireless Settings >>> >> WEP Encryption: yes >>> >> WPA Encryption: yes >>> >> WPA2 Encryption: yes >>> >> >>> >> Wireless Access Points >>> >> >>> >> >>> >> I noticed the line 'State: disconnected' however right now I'm >>> >> connected, I'm sending this email :) Again I had to manually 'dhclient >>> >> eth0' which results in a working connection, only nm-applet thinks >>> >> that somehow there is no wired network connection. >>> > >>> > Right, because the connection wasn't made through NetworkManager, and >>> > thus the information about the connection isn't available to >>> > NEtworkManager because dhclient wasn't run with the right callout >>> > script, etc. >>> > >>> > Can you grab /var/log/messages for me? That will show what NM thinks is >>> > going on. It may be a carrier change race that was fixed in F10 and >>> > higher and the logs might help us figure that out. >>> >>> My reply with the attached /var/log/messages got held up for >>> moderation because it was too big so I've uploaded the >>> /var/log/messages file to >>> >>> http://danielfetchinson.appspot.com/ >> >> I think it's more these: >> >> Nov 17 02:29:48 localhost NetworkManager: Missing required value 'name'. >> Nov 17 02:29:48 localhost NetworkManager: 'connection' setting not >> present. >> >> I don't know what the cause of that could be off the top of my head, but >> you said you're running svn3030, which is from "Sat Oct 27 2007". >> That's really, really old :) The latest NetworkManager available for >> Fedora 8 is: >> >> NetworkManager-0.7.0-0.12.svn4326.fc8 > > From which repo is this available? yum tells me no upgrades are > available. My enabled repos are: fedora, fedora-updates, livna. > >> which you can update to with 'yum upgrade NetworkManager*'. It's highly >> likely that new build from over a year later will fix your problem. >> >> If you don't want to update, you could try to remove all the connections >> you can find from nm-connection-editor. > > When I fire up nm-connection-editor I don't see any connections there. > I have never used this tool before, what should I be seeing? > >> Those log messages mean >> something is providing a bad connection profile to NetworkManager. > > Where are these connection profiles stored? I'd really like to get to > the bottom of this but I'm totally out of ideas. > > Thanks a lot, > Daniel > > >> Dan >> >> >>> You can see the problems start with: >>> >>> Nov 17 02:28:34 localhost console-kit-daemon[1999]: WARNING: Couldn't >>> read /proc/2174/environ: Error reading file '/proc/2174/environ': No >>> such process >>> Nov 17 02:28:34 localhost NetworkManager: (eth0) supplicant interface >>> is now in state 1 (from 0). >>> Nov 17 02:28:34 localhost NetworkManager: killswitch_getpower_reply(): >>> Error getting killswitch power: hal-ipw-killswitch-linux returned 255. >>> Nov 17 02:28:34 localhost NetworkManager: (eth0) supplicant interface >>> is now in state 2 (from 1). >>> >>> And there is more, stuff like: >>> >>> Nov 17 02:29:09 localhost gconfd (fetchinson-2449): Resolved address >>> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only >>> configuration source at position 0 >>> Nov 17 02:29:09 localhost gconfd (fetchinson-2449): Resolved address >>> "xml:readwrite:/home/fetchinson/.gconf" to a writable configuration >>> source at position 1 >>> Nov 17 02:29:09 localhost gconfd (fetchinson-2449): Resolved address >>> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only >>> configuration source at position 2 >>> Nov 17 02:29:48 localhost NetworkManager: Missing required value 'name'. >>> Nov 17 02:29:48 localhost NetworkManager: 'connection' setting not >>> present. >>> Nov 17 02:29:48 localhost NetworkManager: Missing required value 'name'. >>> >>> I'm not sure what all this means, but maybe the gnome config files got >>> messed up? >>> >>> Cheers, >>> Daniel >>>
You may also find all the requisite packages on koji. A quick search on koji turned up the following link to NetworkManager-0.7.0-0.12.svn4326.fc8: http://koji.fedoraproject.org/koji/buildinfo?buildID=70593 Rod _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
