Re: nm-applet stopped connecting to wired network
>> >> >> >> >> 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. >> > >> > It looks like the updates have been cleared from the mirrors since F8 >> > has been unsupported for a year already. You have to play roulette to >> > find a mirror that has them, and I got lucky when I tried: >> > >> > http://mirror.steadfast.net/fedora//updates/8/ >> > >> > None of the other mirrors have F-8 anymore. >> > >> > Assuming you aren't running a 64-bit install (if you are, replace i386 >> > with x86_64 as appropriate), install this RPM with "rpm -Uhv >> > ": >> > >> > http://mirror.steadfast.net/fedora//updates/8/i386.newkey/fedora-release-8-6.transition.noarch.rpm >> > >> > Then update your fedora.repo and fedora-updates.repo files to point to >> > the steadfast.net mirror. The sections should look like this: >> > >> > [updates] >> > name=Fedora $releasever - $basearch - Updates >> > failovermethod=priority >> > baseurl=http://mirror.steadfast.net/fedora//updates/$releasever/$basearch.newkey/ >> > #mirrorlist= >> > >> > (and the same for fedora.repo) >> > >> > And then 'yum upgrade NetworkManager*" >> >> >> Thanks Dan, I've done all of this, NetworkManager* is at the latest >> fedora 8 version. >> >> However this didn't solve the pr
Re: nm-applet stopped connecting to wired network
On Thu, 2009-11-19 at 00:18 +0100, Daniel Fetchinson 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. > > > > It looks like the updates have been cleared from the mirrors since F8 > > has been unsupported for a year already. You have to play roulette to > > find a mirror that has them, and I got lucky when I tried: > > > > http://mirror.steadfast.net/fedora//updates/8/ > > > > None of the other mirrors have F-8 anymore. > > > > Assuming you aren't running a 64-bit install (if you are, replace i386 > > with x86_64 as appropriate), install this RPM with "rpm -Uhv > > ": > > > > http://mirror.steadfast.net/fedora//updates/8/i386.newkey/fedora-release-8-6.transition.noarch.rpm > > > > Then update your fedora.repo and fedora-updates.repo files to point to > > the steadfast.net mirror. The sections should look like this: > > > > [updates] > > name=Fedora $releasever - $basearch - Updates > > failovermethod=priority > > baseurl=http://mirror.steadfast.net/fedora//updates/$releasever/$basearch.newkey/ > > #mirrorlist= > > > > (and the same for fedora.repo) > > > > And then 'yum upgrade NetworkManager*" > > > Thanks Dan, I've done all of this, NetworkManager* is at the latest > fedora 8 version. > > However this didn't solve the problem, the only difference I'm seeing > is that the nm-applet icon that showed no connection before (static > icon) is now an animated icon as if it were trying to conne
Re: nm-applet stopped connecting to wired network
> 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 Thanks a lot, I actually managed to get everything I need from steadfast. Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet stopped connecting to wired network
>> >> >> >> 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. > > It looks like the updates have been cleared from the mirrors since F8 > has been unsupported for a year already. You have to play roulette to > find a mirror that has them, and I got lucky when I tried: > > http://mirror.steadfast.net/fedora//updates/8/ > > None of the other mirrors have F-8 anymore. > > Assuming you aren't running a 64-bit install (if you are, replace i386 > with x86_64 as appropriate), install this RPM with "rpm -Uhv > ": > > http://mirror.steadfast.net/fedora//updates/8/i386.newkey/fedora-release-8-6.transition.noarch.rpm > > Then update your fedora.repo and fedora-updates.repo files to point to > the steadfast.net mirror. The sections should look like this: > > [updates] > name=Fedora $releasever - $basearch - Updates > failovermethod=priority > baseurl=http://mirror.steadfast.net/fedora//updates/$releasever/$basearch.newkey/ > #mirrorlist= > > (and the same for fedora.repo) > > And then 'yum upgrade NetworkManager*" Thanks Dan, I've done all of this, NetworkManager* is at the latest fedora 8 version. However this didn't solve the problem, the only difference I'm seeing is that the nm-applet icon that showed no connection before (static icon) is now an animated icon as if it were trying to connect but couldn't. Again clicking the 'Wired network' radio button doesn't do anything. The relevant section of /var/log/messages is this, it's full of suspicious items from NetworkManager, I'm pretty sure something is screwed up with gconf connections and it's not the fault of NetworkManager itself. As I've said ev
Re: nm-applet stopped connecting to wired network
On Wed, Nov 18, 2009 at 4:00 PM, Daniel Fetchinson 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:readonl
Re: nm-applet stopped connecting to wired network
On Wed, 2009-11-18 at 22:00 +0100, Daniel Fetchinson 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. It looks like the updates have been cleared from the mirrors since F8 has been unsupported for a year already. You have to play roulette to find a mirror that has them, and I got lucky when I tried: http://mirror.steadfast.net/fedora//updates/8/ None of the other mirrors have F-8 anymore. Assuming you aren't running a 64-bit install (if you are, replace i386 with x86_64 as appropriate), install this RPM with "rpm -Uhv ": http://mirror.steadfast.net/fedora//updates/8/i386.newkey/fedora-release-8-6.transition.noarch.rpm Then update your fedora.repo and fedora-updates.repo files to point to the steadfast.net mirror. The sections should look like this: [updates] name=Fedora $releasever - $basearch - Updates failovermethod=priority baseurl=http://mirror.steadfast.net/fedora//updates/$releasever/$basearch.newkey/ #mirrorlist= (and the same for fedora.repo) And then 'yum upgrade NetworkManager*" Dan > > 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
Re: nm-applet stopped connecting to wired network
>> >> >> 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 NetworkM
Re: nm-applet stopped connecting to wired network
On Wed, 2009-11-18 at 09:47 +0100, Daniel Fetchinson 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 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. Those log messages mean something is providing a bad connection profile to NetworkManager. 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 > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet stopped connecting to wired network
>> >> 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/ 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 -- Psss, psss, put it down! - http://www.cafepress.com/putitdown ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet stopped connecting to wired network
On Tue, 2009-11-17 at 23:21 +0100, Daniel Fetchinson wrote: > On 11/17/09, Dan Williams wrote: > > On Tue, 2009-11-17 at 11:02 +0100, Daniel Fetchinson 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. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet stopped connecting to wired network
On 11/17/09, Dan Williams wrote: > On Tue, 2009-11-17 at 11:02 +0100, Daniel Fetchinson 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. Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet stopped connecting to wired network
On Tue, 2009-11-17 at 11:02 +0100, Daniel Fetchinson 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? Dan > But suddenly since yesterday nm-applet wouldn't connect to the wired > network. The icon shows the 2 monitors with the red dot in the lower > right corner with the white cross on it, showing there is no network > connection. When I click the icon the wired network label and radio > button is enabled on the pop-up menu, I can click it, but nothing > happens. > > Strangely though if I do a 'dhclient eth0' the wired network comes up > and the connection is perfectly okay. However the nm-applet icon is > still in the 'no connection' mode. > > This happens both at work and at home. > > I just can't figure out what can be going on. Any ideas? > > For reference, here is the output from 'lspci | grep Ethernet': > > 08:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 > PCI-E Fast Ethernet Controller (rev 16) > > Here is 'ifconfig eth0' > > eth0 Link encap:Ethernet HWaddr 00:1A:80:49:CF:34 > inet addr:157.181.170.115 Bcast:157.181.170.127 > Mask:255.255.255.128 > inet6 addr: fe80::21a:80ff:fe49:cf34/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1025 errors:0 dropped:0 overruns:0 frame:0 > TX packets:751 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:476598 (465.4 KiB) TX bytes:125296 (122.3 KiB) > Interrupt:16 > > And the last couple of lines from 'dmesg': > > ACPI: PCI Interrupt :00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 > [drm] Initialized drm 1.1.0 20060810 > [drm] Initialized i915 1.6.0 20060119 on minor 0 > eth0: no IPv6 routers present > wlan0: no IPv6 routers present > iwl4965: Radio Frequency Kill Switch is On: > Kill switch must be turned off for wireless networking to work. > sky2 eth0: disabling interface > sky2 eth0: enabling interface > ADDRCONF(NETDEV_UP): eth0: link is not ready > sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > eth0: no IPv6 routers present > iwl4965: Error sending REPLY_STATISTICS_CMD: time out after 500ms. > > Currently I'm connected to the wired network because 'dhclient eth0' > connected without a problem, only nm-applet seems to not work because > the icon still shows no network connection. > > Cheers, > Daniel > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
