You are not logged in.

#1 2007-11-20 19:08:00

RobF
Member
Registered: 2006-10-10
Posts: 157

[FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

After a full system upgrade two weeks ago (last -Syu before that was 3 weeks earlier) Arch doesn't autostart my wireless network connection anymore on bootup.  The wireless card (Broadcom 4311, using ndiswrapper and the Windows driver bcmwl5 and WPA v.1 encryption (TKIP)) associates with my wireless access point all right, but then it looks as though the WPA authentication fails, and after 30 sec or so it times out and Arch drops network connectivity. 

I'd made no change whatsoever in my /etc/rc.conf, /etc/wpa_supplicant.conf, /etc/network-profiles/wlan0 or to the router configuration - all of this worked flawlessly before the upgrade (I'm using Arch network-profiles to pick wlan0 or eth0).  The upgrade included the vanilla kernel26 (2.6.22.9-1 -> 2.6.23.1-6) and many networking packages (e.g. ndiswrapper, ndiswrapper-utils, wireless_tools, wlan-ng26, kdenetwork, dhcpcd, also udev, hal, many kde packages).  I've run -Syu twice since then, and that hasn't fixed the problem.

After Arch fails to establish a wireless connection during the boot process, I can try # /etc/rc.d/network restart, or # /etc/rc.d/network stop -> # /etc/rc.d/network start multiple time (sometimes 4, 5 or 6 times) and if I'm lucky that works but often it fails.

To troubleshoot the problem I wrote the following script:

ifconfig wlan0 192.168.0.xxx
iwconfig wlan0 essid networkname channel 11 key ....WPA key in hex here..... 
wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf
dhcpcd wlan0 -s 192.168.0.xxx

When I run this script a representative sample output is as follows:

# ./archwlan0
Trying to associate with xx:xx:xx:xx:xx:xx (SSID='MyAP' freq=2462 MHz)
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Authentication with xx:xx:xx:xx:xx:xx timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with xx:xx:xx:xx:xx:xx (SSID='MyAp' freq=2462 MHz)
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Authentication with xx:xx:xx:xx:xx:xx timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with xx:xx:xx:xx:xx:xx (SSID='MyAp' freq=2462 MHz)
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
Associated with xx:xx:xx:xx:xx:xx
WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed (auth) [id=0 id_str=]

I then have to stop this process (CTRL-Z) and run the last command separately:

[1]+  Stopped                 ./archwlan0
# dhcpcd wlan0 -s 192.168.0.xxx
Error, wlan0: timed out          # at this point I still don't have a working connection - no default gateway
# dhcpcd wlan0 -s 192.168.0.xxx
Error, wlan0: dhcpcd already running on pid 7144 (/var/run/dhcpcd-wlan0.pid)

At this point I finally have a working connection to the internet. [Perhaps 'dhcpcd wlan0 -s 192.168.0.xxx' is not needed, 'route add default gw 192.168.0.1' will also do, without the dhcpcd command]

It looks as though the problem is with the WPA authentication, it seems to be very flaky.  What changed with the upgrade?  Is the new kernel or the ndiswrapper module or wireless_tools or wlan-ng26 or dhcpcd or udev to blame?  Do any of the old networking scripts that were working flawlessly before have to be changed?

My rc.conf:

MODULES=(ndiswrapper capability sg acpi-cpufreq !p4-clockmod cpufreq_ondemand cpufreq_performance cpufreq_powersave)
HOSTNAME="RFDellLT"
lo="lo 127.0.0.1"
INTERFACES=(lo)
gateway="default gw 192.168.0.1"
ROUTES=(gateway)
NET_PROFILES=(wlan0)
DAEMONS=(syslog-ng !hotplug !pcmcia network hal cpufreq portmap @nfslock @nfsd @netfs sshd 
!xinetd @crond cups alsa openntpd privoxy)

Last edited by RobF (2007-11-30 04:38:27)

Offline

#2 2007-11-21 04:56:48

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

I have exactly the same problem different hardware:
ipw3945
WPA2
so this is not related to the hardware. In my opinion this is caused by cfs. I had intermitent problems with different kernels patched with cfs and wireless/wpa2, and no problems with kernels without cfs.

Offline

#3 2007-11-21 09:05:38

once
Member
From: Taiwan
Registered: 2006-09-12
Posts: 266

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

/etc/rc.d/network restart had problem, it halt. after update core rebuilded.
and some problem with system shutdown also.

Offline

#4 2007-11-21 09:23:38

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

I can confirm issues with the wireless (ipw2200) WPA authentication after the last updates (wpa_supplicant update?).

Last edited by ekerazha (2007-11-21 09:34:50)

Offline

#5 2007-11-21 12:19:55

Nekos
Member
From: Italy
Registered: 2007-07-09
Posts: 7

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

some probem here after last updates, with ipw3945 and iwlwifi driver, wpa don't work.

Offline

#6 2007-11-21 12:20:08

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

broch wrote:

I have exactly the same problem different hardware:
ipw3945
WPA2
so this is not related to the hardware. In my opinion this is caused by cfs. I had intermitent problems with different kernels patched with cfs and wireless/wpa2, and no problems with kernels without cfs.

I had no issues before the last updates, also with the 2.6.23 kernel.

Imo this is related to wpa_supplicant or another network component.

Last edited by ekerazha (2007-11-21 12:20:57)

Offline

#7 2007-11-21 14:23:58

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

ekerazha wrote:
broch wrote:

I have exactly the same problem different hardware:
ipw3945
WPA2
so this is not related to the hardware. In my opinion this is caused by cfs. I had intermitent problems with different kernels patched with cfs and wireless/wpa2, and no problems with kernels without cfs.

I had no issues before the last updates, also with the 2.6.23 kernel.

Imo this is related to wpa_supplicant or another network component.

I was/I am running vanilla kernels (including -rc) with most possible versions of cfs or without cfs. Problems related to cfs and wireless were reported earlier.
I have seen this before wpa_supplicant update.
currently four kernels with one important change cfs.
2.6.23.1 works
2.6.23.1-grsec works
2.6.23.8 does not work
2.6.24.rc3 works

applying cfs-devel patch fixed problem with 2.6.23, before cfs was added to the official kernel, I had same 2.6.22.x with or without cfs. without always worked, with cfs (depending on version - one of the later) wireless eithe worked or not

Offline

#8 2007-11-22 00:49:14

RobF
Member
Registered: 2006-10-10
Posts: 157

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

I did another full system upgrade just now: 148 packages were upgraded including quite a few networking packages and in particular wpa_supplicant.  kernel26 was upgraded: 2.6.23.1-6 -> 2.6.23.8-1.  Still the problem persists in exactly the way described in the top post.  Wireless has become almost unusable.

Perhaps I have to wait for kernel 2.6.24 as broch's posts suggest.

Offline

#9 2007-11-22 01:50:20

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

I applied cfs devel on 2.6.23.8 and it seems that wpa2 wireless works now without any problems. this again indicates that there is an issue with (still new) cfs scheduler.

anyone interested:
http://kamikaze.waninkoko.info/patches/ … roken-out/
and apply
sched-cfs-devel.patch


sched-cfs-boost.patch
and
sched-cfs-boost-tunables.patch
are not required but you can try these and have fun

This definitely resolved issues in my case but I can't guarantee that this patch will work for everybody. It would be interesting to see though if patch works for other users and if it does not work for some, then comparing hardware driver differences may further help isolate the problem.

problem:
WPA2 authentication failing. System requires several network restarts to get connected.
First identified on 2.6.22 with different (late) Molnar's CPU scheduler patches. 2.6.22 without cfs worked. 2.6.22 with SD (Kolivas) patches also worked without problems

hardware:
NIC: Intel PRO/Wireless 3945ABG Network Connection

software:
OS: 32-bit current (last update today, but did not help with connectivity)
driver: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.2
kernel 2.6.23.8
specific patches:
sched-cfs-devel.patch
grsecurity-2.1.11-2.6.23.1-200710311914.patch

grsec patch is not related as 2.6.23.8 and 2.6.23.8-grsec work only after sched-cfs-devel.patch is applied

Offline

#10 2007-11-22 10:10:19

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

If you think this is 2.6.23.8 related (this is possible... however I didn't have this issue with CFS on 2.6.23 and 2.6.23.1), it's better to open a bug report.

Offline

#11 2007-11-22 16:10:40

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

ekerazha wrote:

If you think this is 2.6.23.8 related (this is possible... however I didn't have this issue with CFS on 2.6.23 and 2.6.23.1), it's better to open a bug report.

well I pointed out that:

2.6.23.1 works[b/]
[b]2.6.23.1-grsec works

2.6.23.8 does not work
2.6.24.rc3 works

So the fact that you don't have any issues with 2.6.23 and 2.6.23.1
is normal what I described. I hope that you know that upgrading to 2.6.23.1 from 2.6.23 affect users (not many really) with one very specific sata_mv driver so practically for most users there is no difference between 2.6.23 and 2.6.23.1. everything else between these two is exactly the same.

is this clear?

I also explained that 2.6.23.8 works well after applying devel patch to cfs

Because bug can be fixed by cfs patch, because this happened in 2.6.22 with some (not all) versions of cfs scheduler, because it never happened to 2.6.22 without cfs and finally because it never happened to SD cpu scheduler it seems that it is related to Molnar's cfs scheduler. There is still a chance that though cfs scheduler is not at fault it "helps" real bug to appear.

This is not Arch linux issue but vanilla kernel (I always run my own kernels). So I can't submitt Arch linux  bug.

I also pointed out how easy is to fix this, so if you want (seems that you have experience with kernels) simply apply patch (I provided link to the patch above) to 2.6.23.8 and you are done.

Personally I have seen more problems with cfs than with SD but choice was made on more personal grounds than real technical merits. This seem to be confirmed by whole cfs story including WPA2 authentication issues

Last edited by broch (2007-11-22 17:02:52)

Offline

#12 2007-11-23 10:32:34

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

broch wrote:
ekerazha wrote:

If you think this is 2.6.23.8 related (this is possible... however I didn't have this issue with CFS on 2.6.23 and 2.6.23.1), it's better to open a bug report.

well I pointed out that:

2.6.23.1 works[b/]
[b]2.6.23.1-grsec works

2.6.23.8 does not work
2.6.24.rc3 works

So the fact that you don't have any issues with 2.6.23 and 2.6.23.1
is normal what I described. I hope that you know that upgrading to 2.6.23.1 from 2.6.23 affect users (not many really) with one very specific sata_mv driver so practically for most users there is no difference between 2.6.23 and 2.6.23.1. everything else between these two is exactly the same.

is this clear?

Yes... *initially* you said it was a CFS problem (without talking about different kernel versions), I just pointed out that CFS (yes CFS) on 2.6.23 worked fine.

Maybe you should open a bug report so Arch mantainers could include the patch inside the kernel26 package.

Last edited by ekerazha (2007-11-23 10:34:01)

Offline

#13 2007-11-23 15:31:32

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

Yes... *initially* you said it was a CFS problem (without talking about different kernel versions),

No in my first post I pointed out that I had this problems with different kernels:

In my opinion this is caused by cfs. I had intermittent problems with different kernels patched with cfs and wireless/wpa2, and no problems with kernels without cfs.

I don't think that Arch maintainers will include cfs devel patch but it might be possible to backport cfs from 2.6.24 to 2.6.23.8 or use cfs from 2.6.23 in 2.6.23.8. Again this will require some time for testing so it is possible that before testing is done, we will have 2.6.24 in official Arch repositories. That is why I would suggest patching kernel by users or going back to 2.6.23.1


Now, I don't have time for experiments and I don't know if bug is in cfs or if cfs is exposing a bug somewhere else. Definitely including cfs into main kernel tree was unnecessary mistake and primary suggestion to have several cpu schedulers (as Kolivas suggested) was absolutely correct.

I can open a bug asking devs to test upcoming kernels for "WPA2/cfs bug"  (assuming that devs have similar hardware). But this is not real bug report I am afraid.

Last edited by broch (2007-11-23 15:32:46)

Offline

#14 2007-11-23 16:06:09

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

o.k.
I added bug report:
http://bugs.archlinux.org/task/8745

Offline

#15 2007-11-23 21:16:28

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

broch wrote:

No in my first post I pointed out that I had this problems with different kernels:

Yeah, with different kernels patched with cfs == I've tried different kernels patched with cfs and they had problems: as I've already said, I've pointed out that there weren't problems with 2.6.23 (and 2.6.23.1).

I don't think that Arch maintainers will include cfs devel patch but it might be possible to backport cfs from 2.6.24 to 2.6.23.8 or use cfs from 2.6.23 in 2.6.23.8. Again this will require some time for testing so it is possible that before testing is done, we will have 2.6.24 in official Arch repositories. That is why I would suggest patching kernel by users or going back to 2.6.23.1

2.6.23.8 was out without many testing... so they could also give out the fixed version (this is a critical bug) with the same testing time.

Offline

#16 2007-11-23 22:13:56

RobF
Member
Registered: 2006-10-10
Posts: 157

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

FWIW, I have the problem described in the top post with vanilla kernels 2.6.23.1 AND 2.6.23.8 but not with 2.6.22.9.

Offline

#17 2007-11-23 22:19:54

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

I think that you have some serious problems with basic understanding:
I had intermittent = periodic issues with cfs
Periodic problems: some versions of cfs did caused authentication issues some did not..
Now because you never really played with the kernels (if you would, you would notice this issue too), I don't see any point to continue this conversation as it goes nowhere. Particularly if it seems that it was clear to first poster.
You don't have anything new to add, but you must have the last word.
So please add your last word and get over this.

Offline

#18 2007-11-23 22:40:37

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

broch wrote:

I think that you have some serious problems with basic understanding:
I had intermittent = periodic issues with cfs
Periodic problems: some versions of cfs did caused authentication issues some did not..
Now because you never really played with the kernels (if you would, you would notice this issue too), I don't see any point to continue this conversation as it goes nowhere. Particularly if it seems that it was clear to first poster.

Intermittent problems != "intermittent" kernels
Intermittent problems... ex. with that kernel, I had intermittent problems

I think you have a critical bug in your linguistic skills.

End of this pointless discussion.

You don't have anything new to add, but you must have the last word.
So please add your last word and get over this.

Ahaha... dude, please save me from these old and pathetic dialectic exercises.

Offline

#19 2007-11-24 00:37:26

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

Please quote my words correctly (in my first post I said different kernels, but I understand your fixation, and i am really sorry for you), don't try to interpret anything because it seems that this is a task beyond your capabilities.

Now, tell me what all this has to do with the original issue?

Instead of interpreting my  words, get recent kernel sources patch as i suggested and see if you can confirm (or not) that cfs patch fixes authentication problem.

Up until now, I  have not see you doing this (well compiling kernel takes more or less 20 min, you would be done by now). So can you compile custom kernel or you only have big mouth?

Offline

#20 2007-11-24 11:14:21

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

broch wrote:

You don't have anything new to add, but you must have the last word.
So please add your last word and get over this.

Offline

#21 2007-11-24 17:24:50

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

FWIW, I have the problem described in the top post with vanilla kernels 2.6.23.1 AND 2.6.23.8 but not with 2.6.22.9.

hmm..
I am not sure whether I installed 2.6.23.1 with or without cfs patch. RobF, you are correct that both 2.6.23 and 2.6.23.8 have this problem. If you can, please add your comment to
http://bugs.archlinux.org/task/8745

Last edited by broch (2007-11-24 17:26:21)

Offline

#22 2007-11-24 17:38:20

delphiki
Member
Registered: 2007-11-17
Posts: 66
Website

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

ekerazha wrote:
broch wrote:

I have exactly the same problem different hardware:
ipw3945
WPA2
so this is not related to the hardware. In my opinion this is caused by cfs. I had intermitent problems with different kernels patched with cfs and wireless/wpa2, and no problems with kernels without cfs.

I had no issues before the last updates, also with the 2.6.23 kernel.

Imo this is related to wpa_supplicant or another network component.

On my other laptop, a Lenovo 3000 N100, I updated everything again today and have not gotten any problems using wireless with the iwlwifi drivers (not the ipw3945 drivers). I use wpa_supplicant with WPA2-EAP, so you might want to try out your wireless again sometime soon, and possibly using the iwlwifi drivers because the ipw3945 drivers take 20+ iterations of failed authentications before it obtains authentication successfully.

Hope this helps,

Offline

#23 2007-11-25 00:32:06

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

well after I applied cfs devel patch, ipw3945 with WPA2 works.
However, as you see above there is a problem with WPA2 and other cards.

Last edited by broch (2007-11-25 00:34:10)

Offline

#24 2007-11-25 11:02:09

ekerazha
Member
Registered: 2007-02-27
Posts: 290

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

delphiki wrote:

On my other laptop, a Lenovo 3000 N100, I updated everything again today and have not gotten any problems using wireless with the iwlwifi drivers (not the ipw3945 drivers). I use wpa_supplicant with WPA2-EAP, so you might want to try out your wireless again sometime soon, and possibly using the iwlwifi drivers because the ipw3945 drivers take 20+ iterations of failed authentications before it obtains authentication successfully.

Hope this helps,

I use ipw2200 and WPA-TKIP (WPA "1").

Offline

#25 2007-11-25 16:25:09

broch
Banned
From: L.A. California
Registered: 2006-11-13
Posts: 975

Re: [FIXED] Wireless doesn't autostart after -Syu...WPA authent. problem?

in my case
WPA-PSK/AES-CCMP

Offline

Board footer

Powered by FluxBB