Arch Linux

smokn

Member

Registered: 2010-06-13

Posts: 17

Wireless is not working properly after kernel 3.7 and up

Hello, I've been using Fedora with kernel 3.6 and the wireless internet was working as it should.

Then updated the kernel to 3.7. The wireless card connects to my network for like 2-3 mins, Then it stop afterwards,

By "stops" i mean keep reconnecting by itself to the network and asking for password again, or connects successfuly but cannot do any data transfering.

I switched to Arch. Now it uses kernel 3.9.9, And the exact same problem occurs.

So i guess it's all about kernels 3.7 and up or something.

I have no idea what should i do.

My wireless device is Ralink.

Any help would be greatly appreciated.

Thanks.

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,700

Website

Re: Wireless is not working properly after kernel 3.7 and up

Any errors in dmesg or elsewhere?

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

smokn

Member

Registered: 2010-06-13

Posts: 17

Re: Wireless is not working properly after kernel 3.7 and up

Any errors in dmesg or elsewhere?

I don't know exactly what to look for in dmesg.
But when i do

ip link set wlo1 up

I get :

[   73.809837] phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'.
[   74.085549] phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34.
[   74.127635] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready

Although it says "link is not ready" I selected my network using "wifi-menu" and got this output from dmesg :

[   95.456819] wlo1: authenticate with 20:4e:7f:e1:4a:b0
[   95.469540] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 1/3)
[   95.472578] wlo1: authenticated
[   95.472760] rt2800pci 0000:07:00.0 wlo1: disabling HT/VHT due to WEP/TKIP use
[   95.475867] wlo1: associate with 20:4e:7f:e1:4a:b0 (try 1/3)
[   95.519077] wlo1: RX AssocResp from 20:4e:7f:e1:4a:b0 (capab=0x431 status=0 aid=2)
[   95.519600] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[   95.519717] wlo1: associated

But several minutes later the connection stopped (actually while i'm writing this, so i switched to wired connection). I looked in dmesg :

[  409.827729] cfg80211: Calling CRDA to update world regulatory domain
[  411.009443] wlo1: authenticate with 20:4e:7f:e1:4a:b0
[  411.016367] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 1/3)
[  411.088856] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 2/3)
[  411.126655] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 3/3)
[  411.180859] wlo1: authentication with 20:4e:7f:e1:4a:b0 timed out
[  412.767820] wlo1: authenticate with 20:4e:7f:e1:4a:b0
[  412.774920] wlo1: direct probe to 20:4e:7f:e1:4a:b0 (try 1/3)
[  412.977483] wlo1: direct probe to 20:4e:7f:e1:4a:b0 (try 2/3)
[  413.181075] wlo1: direct probe to 20:4e:7f:e1:4a:b0 (try 3/3)
[  413.384623] wlo1: authentication with 20:4e:7f:e1:4a:b0 timed out
[  415.470724] wlo1: authenticate with 20:4e:7f:e1:4a:b0
[  415.477635] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 1/3)
[  415.481450] wlo1: authenticated
[  415.481604] rt2800pci 0000:07:00.0 wlo1: disabling HT/VHT due to WEP/TKIP use
[  415.483476] wlo1: associate with 20:4e:7f:e1:4a:b0 (try 1/3)
[  415.488634] wlo1: RX AssocResp from 20:4e:7f:e1:4a:b0 (capab=0x431 status=0 aid=2)
[  415.488874] wlo1: associated
[  425.506145] wlo1: deauthenticating from 20:4e:7f:e1:4a:b0 by local choice (reason=3)
[  425.517919] cfg80211: Calling CRDA for country: DE
[  439.789462] wlo1: authenticate with 20:4e:7f:e1:4a:b0
[  439.795975] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 1/3)
[  439.815218] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 2/3)
[  439.858002] wlo1: send auth to 20:4e:7f:e1:4a:b0 (try 3/3)
[  439.900096] wlo1: authentication with 20:4e:7f:e1:4a:b0 timed out
[  451.001163] wlo1: authenticate with 20:4e:7f:e1:4a:b0
[  451.008512] wlo1: direct probe to 20:4e:7f:e1:4a:b0 (try 1/3)
[  451.210765] wlo1: direct probe to 20:4e:7f:e1:4a:b0 (try 2/3)
[  451.414345] wlo1: direct probe to 20:4e:7f:e1:4a:b0 (try 3/3)