You are not logged in.

#1 2012-04-09 16:20:28

rlevArch
Member
Registered: 2011-12-04
Posts: 35

wicd stuck "validating authentication" after kernel upgrade [ath9k]

Hey everyone,

I upgraded from Kernel 3.2.14-1 to 3.3.1 last night. After a reboot today, I couldn't connect through my wifi at all. I use wicd, and it was able to scan for networks but would get stuck on the "validating authentication" stage of a WPA2 wireless network.  I'm lucky I was able to use my phone to look for solutions, or I woulda been stuck for much longer than I was.

I tried connecting manually without wicd following the steps outlined here https://bbs.archlinux.org/viewtopic.php?id=72772, but dhcpcd timed out in the last step and I couldn't connect.

I have an exam tomorrow so I don't have that much time to keep troubleshooting, but I thought I should post abouit it.

I've downgraded back to 3.2.14-1 and that fixed my wifi for now, I have Arch on my Macbook 2,1 using an ath9k wireless card. Let me know if there is any other useful info I can give you guys.

EDIT:
Here is my /var/log/pacman.log for the upgrade and downgrade

[2012-04-08 19:49] upgraded bitlbee (3.0.5-2 -> 3.0.5-3)
[2012-04-08 19:49] upgraded chromium (18.0.1025.151-1 -> 18.0.1025.151-3)
[2012-04-08 19:49] upgraded dirmngr (1.1.0-3 -> 1.1.0-4)
[2012-04-08 19:49] >>> Updating module dependencies. Please wait ...
[2012-04-08 19:49] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2012-04-08 19:49] ==> Building image from preset: 'default'
[2012-04-08 19:49]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-04-08 19:49] ==> Starting build: 3.3.1-1-ARCH
[2012-04-08 19:49]   -> Parsing hook: [base]
[2012-04-08 19:49]   -> Parsing hook: [udev]
[2012-04-08 19:49]   -> Parsing hook: [autodetect]
[2012-04-08 19:49]   -> Parsing hook: [pata]
[2012-04-08 19:49]   -> Parsing hook: [scsi]
[2012-04-08 19:49]   -> Parsing hook: [sata]
[2012-04-08 19:49]   -> Parsing hook: [filesystems]
[2012-04-08 19:49]   -> Parsing hook: [usbinput]
[2012-04-08 19:49] ==> Generating module dependencies
[2012-04-08 19:49] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-04-08 19:49] ==> Image generation successful
[2012-04-08 19:49] ==> Building image from preset: 'fallback'
[2012-04-08 19:49]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-04-08 19:49] ==> Starting build: 3.3.1-1-ARCH
[2012-04-08 19:49]   -> Parsing hook: [base]
[2012-04-08 19:49]   -> Parsing hook: [udev]
[2012-04-08 19:49]   -> Parsing hook: [pata]
[2012-04-08 19:49]   -> Parsing hook: [scsi]
[2012-04-08 19:49]   -> Parsing hook: [sata]
[2012-04-08 19:49]   -> Parsing hook: [filesystems]
[2012-04-08 19:49]   -> Parsing hook: [usbinput]
[2012-04-08 19:49] ==> Generating module dependencies
[2012-04-08 19:49] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-04-08 19:49] ==> Image generation successful
[2012-04-08 19:49] upgraded linux (3.2.14-1 -> 3.3.1-1)
[2012-04-08 19:49] upgraded lirc-utils (1:0.9.0-12 -> 1:0.9.0-15)
[2012-04-08 19:49] upgraded ncmpcpp (0.5.9-1 -> 0.5.10-1)
[2012-04-08 19:49] upgraded python-pysqlite (2.6.3-1 -> 2.6.3-2)
[2012-04-08 19:49] The default location of gem installs is $HOME/.gem/ruby
[2012-04-08 19:49] Add the following line to your PATH if you plan to install using gem
[2012-04-08 19:49] $(ruby -rubygems -e "puts Gem.user_dir")/bin
[2012-04-08 19:49] If you want to install to the system wide location, you must either:
[2012-04-08 19:49] edit /etc/gemrc or run gem with the --no-user-install flag.
[2012-04-08 19:49] upgraded ruby (1.9.3_p125-3 -> 1.9.3_p125-4)
[2012-04-09 12:02] Running 'pacman -U linux-3.2.14-1-x86_64.pkg.tar.xz'
[2012-04-09 12:02] >>> Updating module dependencies. Please wait ...
[2012-04-09 12:02] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2012-04-09 12:02] ==> Building image from preset: 'default'
[2012-04-09 12:02]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-04-09 12:02] ==> Starting build: 3.2.14-1-ARCH
[2012-04-09 12:02]   -> Parsing hook: [base]
[2012-04-09 12:02]   -> Parsing hook: [udev]
[2012-04-09 12:02]   -> Parsing hook: [autodetect]
[2012-04-09 12:02]   -> Parsing hook: [pata]
[2012-04-09 12:02]   -> Parsing hook: [scsi]
[2012-04-09 12:02]   -> Parsing hook: [sata]
[2012-04-09 12:02]   -> Parsing hook: [filesystems]
[2012-04-09 12:02]   -> Parsing hook: [usbinput]
[2012-04-09 12:02] ==> Generating module dependencies
[2012-04-09 12:02] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-04-09 12:02] ==> Image generation successful
[2012-04-09 12:02] ==> Building image from preset: 'fallback'
[2012-04-09 12:02]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-04-09 12:02] ==> Starting build: 3.2.14-1-ARCH
[2012-04-09 12:02]   -> Parsing hook: [base]
[2012-04-09 12:02]   -> Parsing hook: [udev]
[2012-04-09 12:02]   -> Parsing hook: [pata]
[2012-04-09 12:02]   -> Parsing hook: [scsi]
[2012-04-09 12:02]   -> Parsing hook: [sata]
[2012-04-09 12:02]   -> Parsing hook: [filesystems]
[2012-04-09 12:02]   -> Parsing hook: [usbinput]
[2012-04-09 12:02] ==> Generating module dependencies
[2012-04-09 12:02] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-04-09 12:02] ==> Image generation successful
[2012-04-09 12:02] upgraded linux (3.3.1-1 -> 3.2.14-1)

Last edited by rlevArch (2012-04-09 17:14:11)

Offline

#2 2012-04-09 16:37:16

ise
Developer
From: Karlsruhe / Germany
Registered: 2005-10-06
Posts: 404
Website

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

I have no problem with wicd and the newest kernel. Would be great if you also post the output from wicd.log

Offline

#3 2012-04-09 16:45:56

rlevArch
Member
Registered: 2011-12-04
Posts: 35

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

Here is my wicd.log: http://codepad.org/9qFAUj8M

Seems like I have a lot of dhcpcd warnings also, but the reason I think it's kernel related is pretty straightforward: stopped working after upgrade, started working again after downgrade. If something else is going on, I'd love to know what!

Offline

#4 2012-04-09 16:48:52

Micah89
Member
Registered: 2011-05-01
Posts: 29

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

Whats your wireless chip? Atheros?

Offline

#5 2012-04-09 16:50:51

rlevArch
Member
Registered: 2011-12-04
Posts: 35

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

Yup, Atheros.
From lspci:

Network controller: Atheros Communications Inc. AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01)

and I am using ath9k

Offline

#6 2012-04-09 17:09:33

alyy
Member
Registered: 2010-05-20
Posts: 6

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

I have the same problem on Atheros chip, however no issues with an external wireless adapter (realtek)

Last edited by alyy (2012-04-09 17:13:47)

Offline

#7 2012-04-09 17:13:36

rlevArch
Member
Registered: 2011-12-04
Posts: 35

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

I should also add that for the first set of 3.2.x kernel updates, ath9k was causing a lot of kernel panics. Other people were complaining about that though, and it seems like it was fixed in a later update.

This issue probably has to do with Atheros and not wicd. The kernel deals with hardware and I didn't have to touch wicd to break/fix the validation issue. I'm gonna add ath9k to the thread title.

Last edited by rlevArch (2012-04-09 17:14:31)

Offline

#8 2012-04-09 17:22:08

mcmillan
Member
Registered: 2006-04-06
Posts: 737

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

There's already been two other threads posted about atheros issues with the latest kernel. https://bbs.archlinux.org/viewtopic.php?pid=1084982 seems to have tracked down the commit that seems to be the issue, though I haven't had a chance to test if reverting it fixes anything yet.

Offline

#9 2012-04-11 03:22:54

sefsinalas
Member
From: Salta - Argentina
Registered: 2010-06-13
Posts: 14
Website

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

I have the same problem and cant connect to wifi sad
Any solution?

Offline

#10 2012-04-11 03:56:07

sefsinalas
Member
From: Salta - Argentina
Registered: 2010-06-13
Posts: 14
Website

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

networkmanager works fine smile

Offline

#11 2012-04-11 08:39:13

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: wicd stuck "validating authentication" after kernel upgrade [ath9k]

A patch is available as documented in this thread.


Burninate!

Offline

Board footer

Powered by FluxBB