Bug 494380 - ath5k never associates with an AP, unless first connected to wired eth0
Summary: ath5k never associates with an AP, unless first connected to wired eth0
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-06 16:39 UTC by Konstantin Ryabitsev
Modified: 2009-11-11 01:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-11 01:14:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg info (41.64 KB, text/plain)
2009-04-06 16:40 UTC, Konstantin Ryabitsev
no flags Details

Description Konstantin Ryabitsev 2009-04-06 16:39:45 UTC
Yeah, so it's a weird one, and it's driving me nutters. I never seem to get connected to an AP running PSA2, unless I first connect to wired eth0 (or, potentially, unless I first get a kernel stack trace). I'm willing to provide any sort of data you may need to help troubleshoot this issue.

This is a Thinkpad x31 with an Atheros wireless chipset.

My dmesg is attached. Please help! :)

Comment 1 Konstantin Ryabitsev 2009-04-06 16:40:21 UTC
Created attachment 338357 [details]
dmesg info

Comment 2 Konstantin Ryabitsev 2009-04-06 16:55:59 UTC
And by PSA2 I mean WPA2 Personal, of course. Sorry.

Comment 3 Niels Haase 2009-04-10 19:37:11 UTC
Thanks for filling this bug.

Can you please provide the version of NM you use with

rpm -qa NetworkManager

and also /var/log/messages when you try to connect to your AP and need to activate the wired connection to do this. Thank you.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Bug Zapper 2009-06-09 13:20:47 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Dan Williams 2009-11-11 01:14:38 UTC
Please re-open if this still happens with latest Fedora 11 update kernels.  Latest should be 2.6.30.9-96.fc11.  Updated kernels have fixes for various ath5k and other wifi issues.  Thanks!


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