SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
So this morning i decided to upgrade to 2.6.30. Now I am wishing I hadn't.
For some reason my Atheros wireless card (AR5213) will no longer connect to the Wireless network I have. Not only that but also the reporting of wireless strengths has changed and is giving erroneous strengths.
When I try to connect to a network using either WICD or iwconfig my card can no longer associate with the wireless network and just times out at trying to associate.
For the readings on how strong the signal is, I am getting 15% higher strengths but the stations disappear at anything below 30% strength.
dmesg shows nothing other than the time outs.
Upon trying to revert back to 2.6.29.4, every time i put the interface down using either 'ifconfig wlan0 down' or when WICD resets the interface the system does a hard lock-up and I am unable to exit with anything other than a hard re-boot.
I am not quite sure what is going on here so any information is greatly appreciated.
Well I guess you compiled your own kernel. if you go back and install the Slackware kernel package which is 2.6.29.5 right now that is the one Slackware built sence the 2.6.29.4 make sure you install the sklackware kernel firmware pkg. This may help. Just a guess.
If you compiled both you could have some extra firmware problems
Well I guess you compiled your own kernel. if you go back and install the Slackware kernel package which is 2.6.29.5 right now that is the one Slackware built sence the 2.6.29.4 make sure you install the sklackware kernel firmware pkg. This may help. Just a guess.
If you compiled both you could have some extra firmware problems
Ok thanks, I will give that a try, in the mean time though I am going to try to track down the changes made to the Atheros Code and see what might be causing my issues.
I moved to 2.6.30 two weeks ago, no problems at all. Previous kernel - 2.6.29.2. Chipset - AR2424. Tested thoroughly on various networks - WEP, WPA, WPA2.
I moved to 2.6.30 two weeks ago, no problems at all. Previous kernel - 2.6.29.2. Chipset - AR2424. Tested thoroughly on various networks - WEP, WPA, WPA2.
I will test it on my other Atheros wifi card that runs the 2412 Chip and see if it is any different.
quick question, how do I pass arguments to get the debug working?
I have mounted debugfs with "mount -t debugfs debug /mnt/debug" and enabled debugging of the ath5k driver. i then pass "echo 0xffffffff > /mnt/debug/ath5k/phy0/debug" however it does not seem to want to accept my command.
you know in Slackware the newer kernels handles permissions per device through hal. if you are having no problem as root using the device please make sure deamon,dialout,and netdev in your users group.
ugh, no dice. There is a reset file that is locked and I think that might be part of my problems but adding myself to the daemon group did nothing. I could not find the groups netdev or dialout.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.