I took the plunged and upgraded to 11.4 and for the most part I like it. It’s not as buggy as 11.3 and seems a lot faster. Though post upgrade left my machine crippled from Yast refusing to load applets in GUI mode until I switched display setting from auto to qt. Plus the missing halt.local which I had to set RUN_PARALLEL to no is System/Boot, and a lot of other things I’ve had to work through, but one issue for the life of me I can’t seem to fix.
My wireless connection will not work anywhere but the place I installed the upgrade. I upgraded my computer at work with WICD on a Wired connection, then after it finished I connected to the AP with no problems. However when I went to my home I noticed I could not authenticate anymore. So I thought maybe it was my network, but all my other wireless devices worked perfectly. So I made a non encrypted AP and still no dice, instead of not authenticating it just would connect and then immediately drop the connection.
I took it back to work and tried to connect and it works flawlessly. The only difference at work is the encryption is Wpa2-psk TKIP. While at home it’s CCMP-AES, but that doesn’t account for the inability to connect to open networks.
I tried Netconfig by manually setting it up and connecting which seems to allow it to auth, but then it drops immediately and starts over. Network Manager just keeps asking for the password and the log repeats a line about “New Secret” I’ll have to go read the log again to get the exact message, but it’s basically requesting the key in an infinite loop without showing any other errors.
I’m using the B43 driver which has worked flawless in the past and works perfectly at work as well. No instability issues or any other quirks. It works flawlessly at my offices, but no where else.
Have you tried configuring via the network manager (using plasmoid-networkmanagement) and kwallet enabled. The latter is required for managing multiple encrypted keys:
So if you think 11.3 was buggy and just upgraded. But didn’t care to explain exactly how you managed that process. I suspect you may have undergone such in a way not likely to result in success.
Nevertheless, my first recommendation to you is create a new user login to test things. See how things work in a new account.
11.2 was rock solid. 11.3 had severe issues with pulseaudio, and nautilus was completely unusable for me as it managed to lock up just attempting to browse files. It was at the time so horrid that I had to switch to Dolphin to have a decent graphical file-manager.
Also I’m sorry if I struck a cord with you, but I used the official supported method with zypper as specified here SDB:System upgrade - openSUSE. I tried KDE in 11.3 and didn’t like it so I switched back to GNOME.
So in short. 11.2 was extremely solid for me, 11.3 was not, and 11.4 is very solid except for the wireless issue. I use Gnome 2, and I’m running it on an Acer Aspire One, Model: Kav60.
This may sound odd, but I had originally used he WL driver back with 11.2 and had problems with it dropping connection, which is why I switched to B43 in the first place. I mean at my work it works flawlessly for hours with no lagging or anything of the sort.
I just have a feeling something is not configured correctly with the Wpa_supplicant. If it’s alright I’m going to post my Network Manager, Wpa_supplicant, and Dmesg logs. Then if it still seems to be a driver issue I’ll switch over.
NetworkManager,
*Oct 29 11:34:12 linux-s3jy NetworkManager[1509]: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <warn> Activation (wlan0/wireless): association took too long.
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <warn> Activation (wlan0/wireless): asking for new secrets
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Activation (wlan0/wireless): connection ‘Auto blah’ has securit$
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Config: added ‘ssid’ value ‘blah’
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Config: added ‘scan_ssid’ value ‘1’
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Config: added ‘key_mgmt’ value ‘WPA-PSK’
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Config: added ‘psk’ value ‘<omitted>’
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> (wlan0): supplicant connection state: scanning -> disconnected
Oct 29 11:34:36 linux-s3jy NetworkManager[1509]: <info> Config: set interface ap_scan to 1
Oct 29 11:34:37 linux-s3jy NetworkManager[1509]: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 29 11:34:52 linux-s3jy NetworkManager[1509]: <warn> (wlan0): link timed out.
Oct 29 11:35:02 linux-s3jy NetworkManager[1509]: <warn> Activation (wlan0/wireless): association took too long.
Oct 29 11:35:02 linux-s3jy NetworkManager[1509]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Oct 29 11:35:02 linux-s3jy NetworkManager[1509]: <warn> Activation (wlan0/wireless): asking for new secrets
*
On 10/29/2011 03:26 PM, caf4926 wrote:
>
> You need Larry to advise. It’s beyond me.
>
> b43 works better in kernel 3
> But that’s another complication you don’t really need.
Your wireless is authenticating and associating, but is deauthenticating after
10 seconds for reason 3, which is “Deauthenticated because sending station is
leaving (or has left) IBSS or ESS.”. I don’t know why that is happening.
From the subject of this thread, I expect that your Broadcom wireless worked
with this AP under 11.3. Is that correct?
Is it possible for you to download a copy of the openSUSE 12.1 RC1 Live CD? If
so, please do so and burn the CD. Before you boot it, copy the contents of
/lib/firmware/b43/ to a USB stick. After the Live CD is booted, copy those files
to /lib/firmware/b43/, then unload and reload b43 using
Do you have access to another machine with a wireless interface? If so, we might
see what is happening by running wireshark to capture what is on the air.
Alright, I loaded 12.1 RC1 on an external drive and booted from it. It immediately connected as soon as I loaded the firmware. So I copied the b43 driver over and rebooted the machine and unloaded then reloaded the b43 driver in 11.4…which didn’t work. So I rebooted the machine and it still wouldn’t connect. That was about 2am last night.
I shut the machine down and decided to wait til today to rig an old laptop to run Wireshark to capture the handshake. I logged on today and suddenly its working and has been for the last 3 hours. I’m not one to look a gift horse in the mouth, but what changed from last night? Nothing was updated to my knowledge.
I’m going to leave it running and try disconnecting and reconnecting repeatedly to see if it is permanently fixed or just a momentary fluke.
On 10/30/2011 02:56 PM, Jworix wrote:
>
> Alright, I loaded 12.1 RC1 on an external drive and booted from it. It
> immediately connected as soon as I loaded the firmware. So I copied the
> b43 driver over and rebooted the machine and unloaded then reloaded the
> b43 driver in 11.4…which didn’t work. So I rebooted the machine and
> it still wouldn’t connect. That was about 2am last night.
Driver modules must be compiled for the kernel under which they are running. It
is not surprising that a 3.1 module did not work with a 2.6.37 kernel.
> I shut the machine down and decided to wait til today to rig an old
> laptop to run Wireshark to capture the handshake. I logged on today and
> suddenly its working and has been for the last 3 hours. I’m not one to
> look a gift horse in the mouth, but what changed from last night?
> Nothing was updated to my knowledge.
I don’t know.
> I’m going to leave it running and try disconnecting and reconnecting
> repeatedly to see if it is permanently fixed or just a momentary fluke.
I don’t understand why, but it’s still working. It shows that i’m using 4.174.64.19-3.1 which is the correct driver for 2.6.37 I believe. Well…I’ll let it go for another day and if it survives the journey to work and back then I’ll mark this solved.
Thanks again for all the amazing help I received. You guys are the best!
When I loaded 11.2 it worked perfectly, but after my first distro upgrade I began having glitches. It’s possible had I done a clean install of 11.3 that there would have been no bugs, but like I said I followed the official method and stayed as close to the official repos as I could, and for my upgrade to 11.4 I only used the official repos.
> When I loaded 11.2 it worked perfectly, but after my first distro
> upgrade I began having glitches. It’s possible had I done a clean
> install of 11.3 that there would have been no bugs, but like I said I
> followed the official method and stayed as close to the official repos
> as I could, and for my upgrade to 11.4 I only used the official repos.
I have been doing upgrades since 5.3 to 11.4 with no permanent glitches.
And I very seldom use something else than the official repos.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Unfortunately I cannot say the same about my experience, and I tend to only delve into Packman, but most of my non repo installs come from One-Click installs, and I do not keep the repositories after.
Anyway regardless of how well your’s has performed, mine has developed a major issue which needs to be corrected. So pointing out that you don’t have an issue does little to help solve mine I’m sorry to say.
> Anyway regardless of how well your’s has performed, mine has developed
> a major issue which needs to be corrected. So pointing out that you
> don’t have an issue does little to help solve mine I’m sorry to say.
I’m just telling that upgrade issues can be solved. I’m not a wifi expert,
so I can’t say how in your case.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
