Bug 4963 - ath5k on Acer Extensa 5620Z laptop
Summary: ath5k on Acer Extensa 5620Z laptop
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks: 5015
  Show dependency treegraph
 
Reported: 2012-03-15 20:29 CET by Tony Blackwell
Modified: 2013-04-23 03:08 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
syslog showing wlan failure (9.65 KB, text/plain)
2012-03-15 20:29 CET, Tony Blackwell
Details
syslog around running rmmod (4.83 KB, text/plain)
2012-03-15 20:30 CET, Tony Blackwell
Details

Description Tony Blackwell 2012-03-15 20:29:37 CET
Created attachment 1774 [details]
syslog showing wlan failure

Description of problem:There have been some other ath5k bugs and I note the beta2 errata.  Put this in to attach more info.

Problem is wireless doesn't spontaneously come up.  Strange thing is that just running "rmmod ath5k" and doing nothing else at all will bring it up.

I attach firstly syslog extracts from the boot process where it has failed, and secondly more syslog around when I've run rmmod and it wakes up.


Version-Release number of selected component (if applicable):


How reproducible: always
Comment 1 Tony Blackwell 2012-03-15 20:30:50 CET
Created attachment 1775 [details]
syslog around running rmmod
Marja Van Waes 2012-03-18 20:08:38 CET

Blocks: (none) => 5015

Comment 2 fabien henon 2012-03-25 15:17:09 CEST
(In reply to comment #0)
> Created attachment 1774 [details]
> syslog showing wlan failure
> 
> Description of problem:There have been some other ath5k bugs and I note the
> beta2 errata.  Put this in to attach more info.
> 
> Problem is wireless doesn't spontaneously come up.  Strange thing is that just
> running "rmmod ath5k" and doing nothing else at all will bring it up.
> 
> I attach firstly syslog extracts from the boot process where it has failed, and
> secondly more syslog around when I've run rmmod and it wakes up.
> 
> 
> Version-Release number of selected component (if applicable):
> se chec
> k b
> How reprug 5oducible: always

please try workaround of bug 5087

CC: (none) => fabien.henon

Comment 3 Marja Van Waes 2012-05-26 13:02:37 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 roelof Wobben 2013-01-02 08:21:10 CET
Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
roelof

CC: (none) => r.wobben

Comment 5 Tony Blackwell 2013-01-03 04:49:49 CET
Appears still to be valid as at M3_beta1 x86_64,  in that wireless seems not to be working.  I'll look at it closely in the next couple of days and report.
Comment 6 Tony Blackwell 2013-01-17 12:15:52 CET
initially in M3B2 no servers are seen.
If run rmmod -f ath5k
rfkill unblock all
modprobe ath5k
then trying to connect again will work after some time delay.

It would be much better if it just worked without this, as with M1.
Comment 7 Tony Blackwell 2013-02-02 02:59:20 CET
I think this is now old and superceded

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 8 Tony Blackwell 2013-04-23 02:45:44 CEST
I'm sorry to report this at this late stage, but it's not fixed.

Using M3 RC x86_64 I just can't get wireless to work.  The base station is found, full signal strength.  Configuration proceeds normally, but connection fails.
I've done the stuff:
rmmod ath5k
rfkill unblock all
modprobe ath5k

and it doesn't help at all.
I attach relevant  journalctl stuff at the end

Comment: why a myriad lines (which I've edited out)re WEP? - despite that I've set it up as WPA?
I also notice that usually when I come back to configure it again via MCC, the type of security defaults back to WEP - is this a bug?

I don't know where to go from here.
Tony Blackwell



output of 'journalctl|grep ath5k:

Apr 23 07:02:33 mobile2.grh.au kernel: ath5k 0000:04:00.0: registered as 'phy0'
Apr 23 07:02:33 mobile2.grh.au kernel: ath5k: phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Apr 23 07:02:44 mobile2.grh.au NetworkManager[649]: <info> rfkill2: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:04:00.0/ieee80211/phy0/rfkill2) (driver ath5k)
Apr 23 07:02:44 mobile2.grh.au NetworkManager[649]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath5k' ifindex: 4)
Apr 23 10:05:36 mobile2.grh.au draknetcenter[5063]: adding alias pci:v0000168Cd0000001Csv00001A32sd00000105bc02sc00i00 to ath5k
Apr 23 10:05:50 mobile2.grh.au ifplugd(wlan0)[5304]: Using interface wlan0/00:17:C4:21:0B:17 with driver <ath5k> (version: 3.8.8-desktop-1.mga3)
Apr 23 10:06:32 mobile2.grh.au ifplugd(wlan0)[5563]: Using interface wlan0/00:17:C4:21:0B:17 with driver <ath5k> (version: 3.8.8-desktop-1.mga3)
Apr 23 10:06:32 mobile2.grh.au kernel: ath5k 0000:04:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
Apr 23 10:06:34 mobile2.grh.au kernel: ath5k 0000:04:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
*repeated myriad times*
Apr 23 10:08:56 mobile2.grh.au ifplugd(wlan0)[6396]: Using interface wlan0/00:17:C4:21:0B:17 with driver <ath5k> (version: 3.8.8-desktop-1.mga3)
Apr 23 10:10:40 mobile2.grh.au ifplugd(wlan0)[6862]: Using interface wlan0/00:17:C4:21:0B:17 with driver <ath5k> (version: 3.8.8-desktop-1.mga3)
Apr 23 10:12:05 mobile2.grh.au harddrake2[7037]: running: modinfo -p ath5k
Apr 23 10:12:19 mobile2.grh.au harddrake2[7037]: running: modinfo -p ath5k
Apr 23 10:12:59 mobile2.grh.au drakconnect[7175]: No settings found for driver "ath5k" in category "network::connection::wireless"
Apr 23 10:13:24 mobile2.grh.au harddrake2[7037]: running: modinfo -p ath5k
[root@mobile2 ~]#

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 9 Tony Blackwell 2013-04-23 03:08:14 CEST
Sorry for the spam.
I forgot to set the wireless regulatory domain to 'au'

:-(

Tony Blackwell

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.