Read elsewhere it could be a kwallet issue and/or a kde plasma applet issue.
I do not have the plasma applet running. I have knetworkmanager running.
I tried the applet. It seems to be handling better the kwallet (e.g. : asking for permission to access it), and it even seems like scanning and connecting to my network. However the connection is not stable : it constantly loses it and have to re-acquire it. It's not usable at all.
With regular knetworkmanager, it may be a kwallet issue, because kwallet never gets fired.
Trying to activate a connection seems to have no effect, and I regularly see my active iwconfig ssid to be the one of a random existing network, but never the one I asked for !
Manually configuring the network (and killing networkmanager) is ok for me and the connection is rock stable.
=> does not seem to be a module/kernel problem
Well, at least for my iwl3945 module.
My ath5k module on my other box is so slow I cannot do anything with it. I found other bug reports for the ath5k, so I guess this whole entry is a big duplicate.
Sorry for the noise.
Read elsewhere it could be a kwallet issue and/or a kde plasma applet issue.
I do not have the plasma applet running. I have knetworkmanager running.
I tried the applet. It seems to be handling better the kwallet (e.g. : asking for permission to access it), and it even seems like scanning and connecting to my network. However the connection is not stable : it constantly loses it and have to re-acquire it. It's not usable at all.
With regular knetworkmanager, it may be a kwallet issue, because kwallet never gets fired.
Trying to activate a connection seems to have no effect, and I regularly see my active iwconfig ssid to be the one of a random existing network, but never the one I asked for !
Manually configuring the network (and killing networkmanager) is ok for me and the connection is rock stable.
=> does not seem to be a module/kernel problem
Well, at least for my iwl3945 module.
My ath5k module on my other box is so slow I cannot do anything with it. I found other bug reports for the ath5k, so I guess this whole entry is a big duplicate.
Sorry for the noise.