[SOLVED] Updates 2012-04-03 killed wifi

[wobo]

After this morning's updates (including kernel 3.3.1-desktop-1.mga2) wifi is not working any more on both of my laptop's cauldron KDE installations.
- using Atheros chip AR9285, module ath9k, WPA encryption, wpa_supplicant, no networkmanager.
- KDE, x86_64

Wifi has been working ok until I rebooted after updates. Opening the context menu of the net applet -> "Wireless connections" I see my network. Restarting it fails.

In /var/log/messages I see:

Code: Select all

network: Configuring wireless regulatory domain [ok]
kernel: ADDRCONF(NETDEV_UP: wlan0: link is not ready
network: Activating "wlan0": Error for wireless request "Set Encode" :
network: SET failed on device wlan0 ; Invalid argument
ifplugd(wlan0): Using interface wlan0/XX:XX:XX:XX:XX:XX with driver <ath9k> (version: 3.3.1-desktop-1.mga2)
ifplugd(wlan0): Using detection mode: SIOCETHTOOL
ifplugd(wlan0): Initialisation complete, link beat not detected

This is identical in both cauldron installation after update.

I removed the connection, re-created it, checked settings twice, rebooted: no success.

PS: On another machine with same KDE desktop latest updates (including kernel) as of today do not give that failure.
Differences to the first machine: i586, Broadcom 4312 (broadcom-wl).

[obgr_seneca]

Did you try booting into the old kernel?

[wobo]

Did you try booting into the old kernel?

Sorry, forgot to add this to my post
wifi works ok with the old kernel (3.3.0-desktop-2.mga2), that's why I emphasized the inclusion of a new kernel in updates.

The only thing I can say about the new kernel is that the module ath9k was built against the new kernel without failure messages.
I checked the files in /etc/sysconfig/network-scripts: ifcfg-wlan0 is identical with the previous, other related files were not touched (according to time stamp).

Besides that I have no clue (as usual).

[obgr_seneca]

I can confirm your problems: When booting into kernel-3.3.1 I have no wifi.
My wifi chip is a

Code: Select all

Atheros Communications Inc. AR9285 Wireless Network Adapter

Some work for tmb, I'd say.

Oliver

[obgr_seneca]

The problem is an upstream patch in the kernel, killing ath wifi support.
Tmb has built a new kernel in which he reverted that. For those bold enough to try, you can find more info here:
https://www.zarb.org/pipermail/mageia-dev/2012-April/013848.html

Oliver

[wobo]

Yes, I read that in the -dev list but I'm too scared, I'll wait for the related update of the real kernel. Glad to read that the cause is found (hopefully)

[obgr_seneca]

Ok, this new kernel solves it for me.

[wobo]

I guess that means we will find the patch in the next kernel update, right?

[obgr_seneca]

I thinks so.
As tmb wrote, it's an upstream bug and upstream is working on it. His "fix" here was just a reverting of two changes done upstream. So it's not a final solution.
I gues tmb is waiting for the upstream kernel developers to create a real fix before he builds an official new kernel for Cauldron.
I could ask him.

Oliver

[wobo]

Not really needed to ask - we'll see when it comes in.

[wobo]

And there it is!
Todays updates (as of 15:00 on the mandrivauser.de mirror) include kernel 3.3.1-desktop-2.mga2. Changelog lists the fix for the ath9k module. Problem solved.

Good job!

[artful-codger]

I'm running the netbook kernel and usually connect with a USB dongle but have found tha wifi has now stopped working.
Is it confirmed the desktop kernel is now working, should I expect a netbook kernel update soon (nothing yet) or switch to desktop?

[dbg]

ILast night I upgraded my Asus eee netbook to Mageia 3 and ran into this problem. No wireless on AR9285. I reverted back to desktop 3.4.45 kernel and wireless works.

[doktor5000]

Could be a totally different problem - the problem reported in this thread is confirmed fixed since more than a year !
You should report that as a bug please - after searching if it hasn't been reported yet already: https://wiki.mageia.org/en/How_to_report_a_bug_properly
For completeness's sake and also to allow others to follow up on that bug report, please also post the link to it here in the thread, thanks.