You are not logged in.
Hello everybody,
I could connect once to wireless networks with arch. Since an update (can't remember version number) I can't any more. I think it's a driver issue; on windows the hardware works regularly. I already searched this forum for a solution, but it seems nobody has the same problem, or has it solved.
Since I'm very bad at network configuring, I'd like you to help me verify there isn't any configuration problem, and I just have to wait a decent driver. I installed today the 2.6.24-1 kernel, but it behaves in the same way, and it seems the integrated driver is the same as the iwlwifi package. I also copied the ucode from Intel site, overwriting the older one installed by pacman, but nothing changed. Restarting computer or the network adapter, or reloading kernel module also have no effect.
The problem is quite strange, since I can see the network interface ( wlan0 ) and the scan works well. I can't associate with the router. I used network manager and wlassistant, fruitlessly. I think the problem is evident in dmesg:
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
phy1: Selected rate control algorithm 'iwl-4965-rs'
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:04:ed:5a:8d:20
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: RX authentication from 00:04:ed:5a:8d:20 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:04:ed:5a:8d:20
wlan0: [b]mismatch in privacy configuration and mixed-cell disabled - abort association[/b]
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: deauthenticated
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:04:ed:5a:8d:20
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: RX authentication from 00:04:ed:5a:8d:20 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:04:ed:5a:8d:20
wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: authentication frame received from 00:04:ed:5a:8d:20, but not in authenticate state - ignored
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: deauthenticated
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
wlan0: RX deauthentication from 00:04:ed:5a:8d:20 (reason=6)
As I said, ifconfig is regular:
[marco@myhost ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1C:23:96:39:42
inet addr:192.168.0.104 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21c:23ff:fe96:3942/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2742 errors:0 dropped:0 overruns:0 frame:0
TX packets:2902 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2101279 (2.0 Mb) TX bytes:437753 (427.4 Kb)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1200 (1.1 Kb) TX bytes:1200 (1.1 Kb)
wlan0 Link encap:Ethernet HWaddr 00:13:E8:80:5D:17
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-13-E8-80-5D-17-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
As also iwconfig:
[marco@myhost ~]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Thanks for any help you can give.
Offline
what about /etc/wpa_supplicant.conf
Zygfryd Homonto
Offline
I use wlassistant... has wpa_supplicant.conf any meaning in this case? I can see only examples in that file.. I commented them out and nothing changed...
Offline
Did you upgrade to the kernel in [testing]? If so, someone else was having a problem where the kernel upgrade killed their 3945-based connection. Maybe it's related?
If that's not the case, ignore me.
Matt
"It is very difficult to educate the educated."
Offline
Did you upgrade to the kernel in [testing]? If so, someone else was having a problem where the kernel upgrade killed their 3945-based connection. Maybe it's related?
I can confirm the same problem with kernel 2.6.24 from testing - killing periodically iwl4965
I compiled vanilla kernel from kernel.org an hour ago and no problem so far
also some config issues with kernel from testing make it unusable for my laptop
Zygfryd Homonto
Offline
iwlwifi package is replaced by testing/kernel26 --- the new kernel provides that driver... but that also is a problem for me too... i can't connect to my wireless router unless i reinstall iwlwifi package (since it's removed with the last system upgrade).. i hope that it'll be fixed soon..
Quis custodiet ipsos custodiet?
Offline
I've pointed this out before (it may, or may not be relevant obviously), but my 4965 doesn't associate with dhclient. Only with dhcpcd (as networkmanager does it).
"Your beliefs can be like fences that surround you.
You must first see them or you will not even realize that you are not free, simply because you will not see beyond the fences.
They will represent the boundaries of your experience."
SETH / Jane Roberts
Offline
First, thanks to all for interesting
What makes my case strange is that my connection was killed not by the new kernel, but by the iwlwifi upgrade (as I can remember)... I installed this kernel hoping it could resolve this problem...
Instead nothing changed in my system behaviour... The problem is exactly the same, this damned message
"mismatch in privacy configuration and mixed-cell disabled, abort association"
I'm not used to network tweaking (though I have the suspect I have to get used to), so I was wondering if this message could be ought to any configuration problem, since it survived to a driver upgrade...
Thanks again for your help
Offline
Same issue here with a 3945ABG after upgrading to kernel26 2.6.24.1-2. The AP has just WEP, never needed wpa_supplicant to connect. It logs the following error: privacy configuration mismatch and mixed-cell disabled - disassociate.
The only workaround I've found is to reinstall iwlwifi and go back to kernel26 2.6.23.14-1.
Offline
I have a 3945ABG with WEP and yesterday I did an pacman -Syu which resulted in the same error message
I don't want to downgrade to 2.6.23 so I really don't know what to do
Maybe I'll give the good old ipw3945 a chance if it works with the 2.6.24.
At least the Wireless LED worked with the ipw driver
Has anybody any suggestions what to do ?
ileach
Last edited by triplefault (2008-04-07 07:06:59)
Offline