You are not logged in.

#1 2012-04-08 17:38:49

rps63ifid
Member
From: Idaho, US
Registered: 2008-08-02
Posts: 39
Website

Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

After updating this morning, which included an update to the 3.3 version of the kernel, I am no longer able to connect to my wireless LAN. The network manager just repeatedly prompts me for the password (which I have verified to be correct). Wireless router, etc., is up and functional; I am posting this from a different non-Linux box connected to the same wireless LAN.

Any clues as to potential ripples the kernel update might have brought with it that could be causing this?

A bit of additional follow-up: I am posting this edit from another Arch-based laptop (but one that I have not and will not, for obvious reasons, updated today). I have verified that both  systems are using the same password to attempt to authenticate. This box (the one that works) shows the following in dmesg:

[   20.282454] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   27.819649] wlan0: authenticate with 20:4e:7f:b7:ea:f6 (try 1)
[   27.823235] wlan0: authenticated
[   27.824270] wlan0: associate with 20:4e:7f:b7:ea:f6 (try 1)
[   27.827738] wlan0: RX AssocResp from 20:4e:7f:b7:ea:f6 (capab=0x411 status=0 aid=3)
[   27.827744] wlan0: associated
[   27.838011] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

The box that has been updated and is now failing to connect shows repeated "wlan0: authenticate with 20:4e:7f:b7:ea:f6" messages (try 1, try 2, try 3) followed by a "wlan0: authentication with 20:4e:7f:b7:ea:f6 timed out" message. That pattern is repeated multiple times in the dmesg output.

If this matters, it is a password (as opposed to hex-key) protected network.

--
/ron

Last edited by rps63ifid (2012-04-08 19:46:19)

Offline

#2 2012-04-08 20:15:42

drmilosz
Member
From: Serbia, Belgrade
Registered: 2008-12-13
Posts: 2
Website

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

I have exactly the same issue. My Wirelles card is  Atheros AR928X and problem occured after upgrade to 3.3.1. From what i found on google this problem should be fixed in next version and suggestion for now is downgrade to previous version of kernel.


First they ignore you... Then they laugh at you... Then they fight you... Then you win...

Offline

#3 2012-04-08 20:20:58

rps63ifid
Member
From: Idaho, US
Registered: 2008-08-02
Posts: 39
Website

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

@drmilosz: Thanks for the follow-up. I had come to the same conclusion based on another thread here on the forums. I too am on a netbook with an Atheros-based network interface. I just downgraded the kernel and it works fine again.

I am curious, though, about something in your response: you indicate you found something indicating "... this problem should be fixed in the next version..." -- next version of what, precisely?

--
/ron

Offline

#4 2012-04-08 20:37:15

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,837

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

The kernel.

Offline

#5 2012-04-08 22:47:12

jlacroix
Member
Registered: 2009-08-16
Posts: 576

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

Same problem here, with an AR5B91 card.

Offline

#6 2012-04-08 23:21:42

sergio.correia
Member
Registered: 2012-04-02
Posts: 2

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

3.3.1-1-ARCH and AR9285 here, and the same problem, but it happens after a suspend/resume cycle. It works fine until I try to resume from a suspend, then it will get stuck at those timeout messages trying to associate/authenticate.

Offline

#7 2012-04-09 12:52:42

magikmw
Member
Registered: 2012-02-10
Posts: 5

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

I can confirm that kernel 3.3 -> 3.2 downgrade fixed the problem for me. Wifi works fine again. I'd avoid 3.3.1 and try upgrading again after next kernel release.

Offline

#8 2012-04-09 15:29:20

Songohan
Member
Registered: 2012-03-19
Posts: 11

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

magikmw wrote:

I can confirm that kernel 3.3 -> 3.2 downgrade fixed the problem for me. Wifi works fine again. I'd avoid 3.3.1 and try upgrading again after next kernel release.

I confirm the kernel downgrade fixed the problem smile .
My chipset : AR9287

Offline

#9 2012-04-10 01:03:19

shellclear
Member
Registered: 2012-04-10
Posts: 1

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

confirming downgrade kernel fixes the problem!!

My chip is:

02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
        Subsystem: Lenovo Device 30a1
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at d0400000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis+
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
                         EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
        Capabilities: [140 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
                        Status: NegoPending- InProgress-
        Capabilities: [160 v1] Device Serial Number 00-15-17-ff-ff-24-14-12
        Capabilities: [170 v1] Power Budgeting <?>
        Kernel driver in use: ath9k

Offline

#10 2012-04-10 07:56:48

borrell
Member
Registered: 2008-12-02
Posts: 29
Website

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

Checking in,

Same issue with an AR9285 card, and downgrading to 3.2.13 works fine.

Offline

#11 2012-04-10 15:38:48

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

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

If folks are willing to rebuild their kernel there's a patch listed in this thread https://bbs.archlinux.org/viewtopic.php … 0#p1085310

Offline

#12 2012-04-10 17:25:59

sintoni
Member
Registered: 2012-04-02
Posts: 3

Re: Unable to connect to wireless LAN after kernel upgrade 3.3.1 today?

AR922X for me, same issue smile

Offline

Board footer

Powered by FluxBB