Wireless problem after update

ivanblago · 2012-01-27 07:40:49

03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: Fujitsu Limited. Device 1537
	Kernel driver in use: ath9k

Linux btstation 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:40:20 CET 2012 x86_64 Intel(R) Pentium(R) CPU P6200 @ 2.13GHz GenuineIntel GNU/Linux

Ok, after update and restart AB. And can't conect to the network over wireless. Cable conection is OK.

I Updated this and restart:
linux 3.2.2-1
alsa-firmware 1.0.25-1
alsa-oss 1.0.25-1
alsa-lib 1.0.25-1
alsa-utils 1.0.25-1

Last edited by ivanblago (2012-01-27 07:41:42)

oliver · 2012-01-27 08:52:56

You could downgrade the kernel (or wait 5 minutes and another one will come along)

But if you want to troubleshoot, can you let us know if the device is plumbed (i.e. you do see wlan0 or something) and it can't get an IP or if it's not even detected

ivanblago · 2012-01-27 09:46:41

I can see my network, but, when I try to conect system required authentication again and again... at the end get disconected. (I have the right password, I chech twice).

oliver · 2012-01-27 10:12:17

is there anything in /var/log/everything or dmesg when you fail to connect?

An easy way to check logs is:

tail -f /var/log/everything | tee -a /tmp/mylog

and then look at /tmp/mylog

In saying that, you will need read permissions on /var/log/everything (sudo the command or be root) and I'm not sure it will be written to that log anyway

ivanblago · 2012-01-27 10:57:54

Here it is:

[ivan@btstation ~]$ sudo tail -f /var/log/everything | tee -a /tmp/mylog
Password: 
tail: cannot open `/var/log/everything' for reading: No such file or directory

/tmp/mylog is empty text file

Latest part of /var/log/everything.log I put on pastebin

oliver · 2012-01-27 13:39:34

ivanblago wrote:

Here it is:
[ivan@btstation ~]$ sudo tail -f /var/log/everything | tee -a /tmp/mylog
Password: 
tail: cannot open `/var/log/everything' for reading: No such file or directory
/tmp/mylog is empty text file
Latest part of /var/log/everything.log I put on pastebin

/tmp/mylog is empty because I forgot to add the .log part to the command. All the 'tee' does is sends the output to a new file (called /tmp/mylog)... it's very useful when you have huge log files and lots of scrolling data.

For your problem, assuming all was working before I see two possible causes

1) something in the new kernel is causing issues
2) something in networkmanager doesn't like a kernel change

Outside of downgrading the kernel, you could try doing stuff outside of Network Manager

To downgrade the kernel, go to /var/cache/pacman/pkg and look for older versions of 'linux-3*'

Then install with

# pacman -U <older version>

If you want to try at the command line, create a file called /tmp/wpa_supplicant.conf with the following data

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=network
network={
	ssid="<your essID>"
	psk="<your passphrase>"
}

Then, run

$ sudo wpa_supplicant -Dwext -iwlan0 -c/tmp/wpa_supplicant.conf -B
$ sudo dhcpcd

ivanblago · 2012-01-27 14:38:42

Unfortunately, Yesterday I deleted cache and can't downgrade, stupid from me... I know

A temporary solution:
I turn off Request a password, and now I can connect to my wireless network, now it is hidden but it will work until I find a solution for this problem.

I also tried /tmp/wpa_supplicant.conf , but I had no luck... After that I delete wpa_supplicant.conf, I hope that this will not cause problems...

I will write if I find a better solution...

oliver · 2012-01-27 15:02:37

ivanblago wrote:

I also tried /tmp/wpa_supplicant.conf , but I had no luck... After that I delete wpa_supplicant.conf, I hope that this will not cause problems....

It shouldn't cause any issue... the normal location is /etc/ but you can point to any file via the command line.

You can get old packages at

http://arm.konnichi.com/

This might be the right one for you (if you have an 64 bit install)
http://arm.konnichi.com/2012/01/25/core … pkg.tar.xz

ivanblago · 2012-01-27 15:31:08

Great Thanks ! I will check that, too.

wgianopoulos · 2012-01-28 13:02:31

I just ran into the same issue under fedora 16. The issue seems to be restricted to just this driver and just to connections using WEP security. If you can upgrade your wireless network to WPA2 (or failing that WPA) that would both enhance your network security and also avoid this issue.

I am going to file a bug on this.

wgianopoulos · 2012-01-28 13:36:12

You can follow progress on the fedora bug I filed at https://bugzilla.redhat.com/show_bug.cgi?id=785409

ivanblago · 2012-01-28 16:43:36

wgianopoulos wrote:

You can follow progress on the fedora bug I filed at https://bugzilla.redhat.com/show_bug.cgi?id=785409

Ok, great job. I will...

Thanks.

simon.swe · 2012-02-26 05:34:19

Hi! I had the same problem, with exact same wifi card.
neither wicd or NetworkManger let me connect. but wpasupplicant.conf and nl80211 worked out fine.
(and im using wireless-compat 3.2.5-1)
peeze

simon.swe · 2012-02-26 05:37:02

..and i have too, iw dev wlan0 set bitrates legacy-2.4 54
else the speed is just 1 mbit.

Arch Linux

Announcement

#1 2012-01-27 07:40:49

Wireless problem after update

#2 2012-01-27 08:52:56

Re: Wireless problem after update

#3 2012-01-27 09:46:41

Re: Wireless problem after update

#4 2012-01-27 10:12:17

Re: Wireless problem after update

#5 2012-01-27 10:57:54

Re: Wireless problem after update

#6 2012-01-27 13:39:34

Re: Wireless problem after update

#7 2012-01-27 14:38:42

Re: Wireless problem after update

#8 2012-01-27 15:02:37

Re: Wireless problem after update

#9 2012-01-27 15:31:08

Re: Wireless problem after update

#10 2012-01-28 13:02:31

Re: Wireless problem after update

#11 2012-01-28 13:36:12

Re: Wireless problem after update

#12 2012-01-28 16:43:36

Re: Wireless problem after update

#13 2012-02-26 05:34:19

Re: Wireless problem after update

#14 2012-02-26 05:37:02

Re: Wireless problem after update

Board footer