[opensuse] Problems (minor?) with 11.2 upgrade
After seeing a lot of praise for 11.2, and not having seen the early complaints about its killing Intel networking, I decided to upgrade. I followed the instructions provided on the "Upgrade/Supported" page of the wiki. Things went pretty well, I think. One hitch is that I needed two iterations of zypper dup after I'd done all the preparatory actions. When I did the first dup it crunched for 2-1/2 hours installing thousands of packages. I got some warnings about running processes that needed to be restarted. Since there had been a kernel upgrade, I simply restarted the computer. Panic followed :-). Several blank dialogs popped up. Worse yet, when I started yast to do an online update the progress box was blank. So I went back to the command line and did a zypper up Nothing to do. Meantime more blank dialogs popped up. Willing to try anything, I did another zypper dup It installed hundreds more packages. One of the messages mentioned a 2.6.29... kernel, which I recalled was in 11.1. So I rebooted again. Now uname -a says Linux embelex 2.6.31.5-0.1-pae #1 SMP 2009-10-26 15:49:03 +0100 i686 i686 i386 GNU/Linux so I guess I'm ok. I tried embelex:~ # zypper up Loading repository data... Reading installed packages... Nothing to do. then embelex:~ # zypper dup Loading repository data... Reading installed packages... Computing distribution upgrade... 3 Problems: sesam_srv-3.0.1-171.1.1.i586 kdm-branding-upstream-4.3.1-7.5.i586 kio_sysinfo-branding-upstream-11.2-3.2.noarch (above slightly edited for clarity). I skipped all of them since they don't appear to be particularly useful (except possibly sesam -- I don't know what it is). I had installed the branding-upstream to see if kde looked better than suse, which i suppose is the reason for the upstream branding warnings. Now I can't get rid of them without downgrading dozens of other packages. So far things look good. Firefox is up to 3.5.6 and seems to work well; Tbird is up to 3.0 and looks good; skype still appears to work (can't test it on people at 0200, but the test call was good :-). Oh yeah. wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}. Earlier in 11.1, knetworkmanager simply connected and after a few seconds, I was online again. I didn't need to do anything manually. So I'm still on ethernet. John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Montag, 4. Januar 2010 09:06:12 schrieb John E. Perry:
Oh yeah. wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}.
Earlier in 11.1, knetworkmanager simply connected and after a few seconds, I was online again. I didn't need to do anything manually.
For NetworkManager issues it is useful to try a different client, e.g. nm- applet. If that works it's a knm (config) issue. If that does not work a look at the wpa_supplicant and NetworkManager logs as well as warn and messages helps too. And of course you can try to use YaST to configure your wifi connection to rule out NM completely. If you have a big enough USB stick you could even try to create a live DVD/CD to simulate a fresh install and see if that helps. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John E. Perry wrote:
After seeing a lot of praise for 11.2, and not having seen the early complaints about its killing Intel networking, I decided to upgrade.
I followed the instructions provided on the "Upgrade/Supported" page of the wiki. Things went pretty well, I think.
One hitch is that I needed two iterations of
zypper dup
after I'd done all the preparatory actions. When I did the first dup it crunched for 2-1/2 hours installing thousands of packages. I got some warnings about running processes that needed to be restarted. Since there had been a kernel upgrade, I simply restarted the computer.
Panic followed :-). Several blank dialogs popped up. Worse yet, when I started yast to do an online update the progress box was blank. So I went back to the command line and did a
zypper up
Nothing to do. Meantime more blank dialogs popped up. Willing to try anything, I did another
zypper dup
It installed hundreds more packages. One of the messages mentioned a 2.6.29... kernel, which I recalled was in 11.1.
So I rebooted again. Now uname -a says
Linux embelex 2.6.31.5-0.1-pae #1 SMP 2009-10-26 15:49:03 +0100 i686 i686 i386 GNU/Linux
so I guess I'm ok. I tried
embelex:~ # zypper up Loading repository data... Reading installed packages...
Nothing to do.
then
embelex:~ # zypper dup Loading repository data... Reading installed packages... Computing distribution upgrade... 3 Problems: sesam_srv-3.0.1-171.1.1.i586 kdm-branding-upstream-4.3.1-7.5.i586 kio_sysinfo-branding-upstream-11.2-3.2.noarch
(above slightly edited for clarity). I skipped all of them since they don't appear to be particularly useful (except possibly sesam -- I don't know what it is). I had installed the branding-upstream to see if kde looked better than suse, which i suppose is the reason for the upstream branding warnings. Now I can't get rid of them without downgrading dozens of other packages.
So far things look good. Firefox is up to 3.5.6 and seems to work well; Tbird is up to 3.0 and looks good; skype still appears to work (can't test it on people at 0200, but the test call was good :-).
Oh yeah. wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}.
Information about tracking NM problems can be found here: http://userbase.kde.org/NetworkManagement HTH, Robert
Earlier in 11.1, knetworkmanager simply connected and after a few seconds, I was online again. I didn't need to do anything manually.
So I'm still on ethernet.
John Perry
-- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert@novell.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 04 January 2010 14:16:39 Robert Schweikert wrote:
Oh yeah. wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}.
Information about tracking NM problems can be found here:
Right, and you've got direct access to the author of that document and of knetworkmanager. Pity all those kubuntu users! If you can give me the details requested in the 'It's all KDE's fault' section of the above URL we can get you going and solve the problem for future releases. The NetworkManager log as well as wireless hardware details should be a good first step; if you are able to connect with another NM client then DBUS dumps of both working and non-working connections would be extremely helpful. Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 01/04/2010 11:09 AM, Will Stephenson wrote:
On Monday 04 January 2010 14:16:39 Robert Schweikert wrote:
Oh yeah. wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}.
Information about tracking NM problems can be found here:
Right, and you've got direct access to the author of that document and of knetworkmanager. Pity all those kubuntu users! If you can give me the details requested in the 'It's all KDE's fault' section of the above URL we can get you going and solve the problem for future releases.
The NetworkManager log as well as wireless hardware details should be a good first step; if you are able to connect with another NM client then DBUS dumps of both working and non-working connections would be extremely helpful.
Will
Will, everything in that section talked about either recompiling knm or trying other clients. I don't have the courage to try any others (ifup was about my limit), so I just now gave up and tried connecting to generate some messages. I read around the kde page and selected a few log files, but even with aggressive editing it's nearly 300 lines long. I've sent it directly to you in a separate email -- hope that's not a problem. It consists of lines from dmesg, /var/log/wpa_supplicant.log, /var/log messages, and /var/log/NetworkManager. I started copying from when I disconnected the cable, and kept lines until the repetition became excessive, or until eth0 started coming up (in the case of NetworkManager). John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Montag, 4. Januar 2010 09:06:12 schrieb John E. Perry:
After seeing a lot of praise for 11.2, and not having seen the early complaints about its killing Intel networking, I decided to upgrade. Also broken for me (see below). Does anyone know of bug reports on this?
wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}. Earlier in 11.1, knetworkmanager simply connected and after a few seconds, I was online again. I didn't need to do anything manually. So I'm still on ethernet. I also had perfect WLAN connectivity using knetworkmanager on 11.1 since the earliest 11.2 alphas my WLAN is broken in exactly the way you describe (network is visible but connection attempts always fail even if i make the network unencrypted).
Stefan. Q. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 01/08/2010 07:27 PM, John E. Perry wrote:
On 01/04/2010 11:09 AM, Will Stephenson wrote:
On Monday 04 January 2010 14:16:39 Robert Schweikert wrote:
Oh yeah. wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}.
Information about tracking NM problems can be found here:
Right, and you've got direct access to the author of that document and of knetworkmanager. Pity all those kubuntu users! If you can give me the details requested in the 'It's all KDE's fault' section of the above URL we can get you going and solve the problem for future releases.
The NetworkManager log as well as wireless hardware details should be a good first step; if you are able to connect with another NM client then DBUS dumps of both working and non-working connections would be extremely helpful.
Will
Will, everything in that section talked about either recompiling knm or trying other clients. I don't have the courage to try any others (ifup was about my limit), so I just now gave up and tried connecting to generate some messages.
I read around the kde page and selected a few log files, but even with aggressive editing it's nearly 300 lines long. I've sent it directly to you in a separate email -- hope that's not a problem. It consists of lines from dmesg, /var/log/wpa_supplicant.log, /var/log messages, and /var/log/NetworkManager. I started copying from when I disconnected the cable, and kept lines until the repetition became excessive, or until eth0 started coming up (in the case of NetworkManager).
...So, Will, after hearing nothing more for a couple of weeks, and still having no wifi after _many_ zypper up's and dup's, I finally worked up the courage to try the procedure given by Josef Wolf on 01/12/2010 (Re: [opensuse] network-manager in 11.2). I'd looked through the web pages and documents, but I'm apparently too simple-minded to figure this out on my own. It worked! I'm finally free of Ethernet, after a month and more of having my laptop's kde desktop tied by a cat5e cable to my wooden desktop :-). Thank you, Josef. John Perry, via wifi again, finally. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 02 February 2010 05:06:16 John E. Perry wrote:
On 01/08/2010 07:27 PM, John E. Perry wrote:
On 01/04/2010 11:09 AM, Will Stephenson wrote:
On Monday 04 January 2010 14:16:39 Robert Schweikert wrote:
Oh yeah. wifi doesn't work any more. One of the 11.1 updates broke it, and I was hoping 11.2 would fix whatever that was. It's still doing the same thing it was before: knetworkmanager shows me my SSID, I click on it, it churns for a while, and comes back asking for my passphrase. I give it, and {repeat ad infinitum}.
Information about tracking NM problems can be found here:
Right, and you've got direct access to the author of that document and of knetworkmanager. Pity all those kubuntu users! If you can give me the details requested in the 'It's all KDE's fault' section of the above URL we can get you going and solve the problem for future releases.
The NetworkManager log as well as wireless hardware details should be a good first step; if you are able to connect with another NM client then DBUS dumps of both working and non-working connections would be extremely helpful.
Will
Will, everything in that section talked about either recompiling knm or trying other clients. I don't have the courage to try any others (ifup was about my limit), so I just now gave up and tried connecting to generate some messages.
I read around the kde page and selected a few log files, but even with aggressive editing it's nearly 300 lines long. I've sent it directly to you in a separate email -- hope that's not a problem. It consists of lines from dmesg, /var/log/wpa_supplicant.log, /var/log messages, and /var/log/NetworkManager. I started copying from when I disconnected the cable, and kept lines until the repetition became excessive, or until eth0 started coming up (in the case of NetworkManager).
...So, Will, after hearing nothing more for a couple of weeks, and still having no wifi after _many_ zypper up's and dup's, I finally worked up the courage to try the procedure given by Josef Wolf on 01/12/2010 (Re: [opensuse] network-manager in 11.2). I'd looked through the web pages and documents, but I'm apparently too simple-minded to figure this out on my own.
It worked! I'm finally free of Ethernet, after a month and more of having my laptop's kde desktop tied by a cat5e cable to my wooden desktop :-).
Thank you, Josef.
John Perry, via wifi again, finally.
Sorry John, I was travelling a lot in January and this got dropped on the floor. The logs that you sent me privately didn't show anything conclusive - just association timeouts. Now that you do have an alternate client, could I prevail upon you compare working and non-working wifi connections using qdbus so we can save others the hassle in future? If you go to http://userbase.kde.org/NetworkManagement#It.27s_All_KDE.27s_Fault.21 and start at the paragraph beginning "If you do not build from source" you should be good. Find the 'Grotto' (right?) connection as provided by both nm- applet and knetworkmanager and send me the qdbus output. Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 02/04/2010 06:41 AM, Will Stephenson wrote:
...
Now that you do have an alternate client, could I prevail upon you compare working and non-working wifi connections using qdbus so we can save others the hassle in future?
If you go to http://userbase.kde.org/NetworkManagement#It.27s_All_KDE.27s_Fault.21 and start at the paragraph beginning "If you do not build from source" you should be good. Find the 'Grotto' (right?) connection as provided by both nm- applet and knetworkmanager and send me the qdbus output.
My qdbus output didn't look a lot like what's in the referenced web page, but I think I've got the editing figured out. And I could see no evidence that qdbus saw any of the dozen other neighborhood connections shown by nm-applet when I first started it up (interestingly, I can't figure out how to get back to that list, now that I'm connected). Do you want me to put this into bugzilla, too? -------------------------------------------------------------- Working connection using nm-applet: embelex:/home/john # /usr/bin/qdbus --system --literal org.freedesktop.NetworkManagerUserSettings /org/freedesktop/NetworkManagerSettings/0 org.freedesktop.NetworkManagerSettings.Connection.GetSettings [Argument: a{sa{sv}} {"802-11-wireless" = [Argument: a{sv} {"mode" = [Variant(QString): "infrastructure"], "seen-bssids" = [Variant(QStringList): {"00:1b:2f:46:e5:6c"}], "ssid" = [Variant(QByteArray): {71, 114, 111, 116, 116, 111}], "security" = [Variant(QString): "802-11-wireless-security"]}], "802-11-wireless-security" = [Argument: a{sv} {"key-mgmt" = [Variant(QString): "wpa-psk"]}], "connection" = [Argument: a{sv} {"uuid" = [Variant(QString): "336ae7ee-2fb2-462d-a460-274b015b69e3"], "id" = [Variant(QString): "Auto Grotto"], "type" = [Variant(QString): "802-11-wireless"], "timestamp" = [Variant(qulonglong): 1265393783]}]}] -------------------------------------------------------------- Nonworking using kde plasmoid: embelex:/home/john # /usr/bin/qdbus --system --literal org.freedesktop.NetworkManagerUserSettings /org/freedesktop/NetworkManagerSettings/0 org.freedesktop.NetworkManagerSettings.Connection.GetSettings [Argument: a{sa{sv}} {"802-11-wireless" = [Argument: a{sv} {"mode" = [Variant(QString): "infrastructure"], "ssid" = [Variant(QByteArray): {80, 104, 111, 101, 110, 105, 120, 32, 73, 73, 32, 85, 110, 105, 116, 32, 50, 48, 49, 49}]}], "connection" = [Argument: a{sv} {"autoconnect" = [Variant(bool): true], "id" = [Variant(QString): ""], "type" = [Variant(QString): "802-11-wireless"], "uuid" = [Variant(QString): "57208ef5-40a8-4eac-8831-23327111fa3a"]}], "ipv4" = [Argument: a{sv} {"dns-search" = [Variant(QStringList): {""}], "method" = [Variant(QString): "auto"]}]}] -------------------------------------------------------------- An interesting quirk is that when I tried to start the knetworkmanager, it wasn't found, and when I searched for it, rpm said NetworkManager-kde4.rpm was not installed. Maybe it was deleted by one of my zypper dup's? When I installed it, the icon was the one I recognize from all my previous efforts trying to get back onto wifi. Doesn't make any difference, though, as far as I can see. knm still doesn't work; to get back onto wifi, I had to kill it and restart nm-applet, which, again, instantly connected without issue. jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 02/05/2010 01:31 PM, John E. Perry wrote:
On 02/04/2010 06:41 AM, Will Stephenson wrote:
...
Now that you do have an alternate client, could I prevail upon you compare working and non-working wifi connections using qdbus so we can save others the hassle in future? ...
Working connection using nm-applet:
embelex:/home/john # /usr/bin/qdbus --system --literal org.freedesktop.NetworkManagerUserSettings /org/freedesktop/NetworkManagerSettings/0 org.freedesktop.NetworkManagerSettings.Connection.GetSettings ... Doesn't make any difference, though, as far as I can see. knm still doesn't work; to get back onto wifi, I had to kill it and restart nm-applet, which, again, instantly connected without issue.
I guess you found what you needed, Will? It appears to have been fixed last week -- now I don't have to start nm-applet any more, and knm works automatically and silently again. Thanks to all, both for the workarounds and for restoring the excellent performance of knm.
jp
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
John E. Perry -
Robert Schweikert -
Stefan Quandt -
Sven Burmeister -
Will Stephenson