[SOLVED] Can't use wireless : Slackware 14.0 vs. Intel PRO/Wireless 3945ABG

kikinovak · 10-29-2013, 07:23 AM

Hi,

I've just installed my personal blend of Slackware 14.0 on a Compaq Presario V6000, for a client. So far everything is working fine: video acceleration, sound, KDE is fast and snappy. The only remaining problem seems to be wireless, which I can't get to work. According to lspci, the card is an Intel PRO/Wireless 3945ABG.

I'm using NetworkManager with the GNOME Network Manager applet, which I've tweaked to use it in KDE. This setup works very well on two of my own laptops.

Various ESSIDs around here show up fine, except I can't connect to any of them.

Now I remember very vaguely having had a similar issue with an Intel card a few years ago, where I had to blacklist the free (iwlwifi) driver and specify explicitly the use of the semi-proprietary ipwsomething driver, together with some piece of firmware in /lib/firmware. I can't seem to find that information anymore.

Any suggestions?

kikinovak · 10-29-2013, 07:49 AM

OK, I investigated this a little further. I did a tail -f /var/log/messages and tried to connect to my access point. Here's what I get:

Code:

Oct 29 15:30:49 presario-v6000 NetworkManager[1589]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 29 15:30:49 presario-v6000 NetworkManager[1589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 29 15:30:49 presario-v6000 NetworkManager[1589]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 29 15:30:49 presario-v6000 NetworkManager[1589]: <info> Activation (wlan0/wireless): access point 'microlinux' has security, but secrets are required.
Oct 29 15:30:49 presario-v6000 NetworkManager[1589]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct 29 15:30:49 presario-v6000 NetworkManager[1589]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 29 15:31:14 presario-v6000 NetworkManager[1589]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]

So apparently there's a problem with the key.

I temporarily deactivated the encryption and could connect fine this time.

Indeed, when I try to connect to any access point with some security (WEP or WPA), NetworkManager doesn't ask for a password and simply fails to connect after some time.

So what's wrong here? Why does NetworkManager act like this? Something missing?

WhiteWolf1776 · 10-29-2013, 08:05 AM

Just a heads up, but Slackware 14.1 (currently at RC3 and rather stable) includes the network manager stock.

kikinovak · 10-29-2013, 08:13 AM

Thanks, but I need this to work on 14.0 for a series of reasons.

kikinovak · 10-29-2013, 08:21 AM

It looks like gnome-keyring is the missing thing here. ps aux | grep gnome-keyring shows nothing. I tried various ways to start it under KDE, but failed. This is starting to get messy.

marnold · 10-31-2013, 07:39 PM

NetworkManager is in 14.0 stock too.

I set up NetworkManager using the KDE Network Management applet (or whatever they call it). When you edit the network connection there is a spot to enter your WPA2, etc., key. Make sure that "System connection" is checked and it should be fine from there. Make sure to make /etc/rc.d/rc.networkmanager executable too. Works for me in 14.0 and the 14.1 RCs with WPA2 on my router.

FWIW, I don't have gnome-keyring running either.

ReaperX7 · 10-31-2013, 08:05 PM

If you need gnome-keyring check out SlackBuilds.org for the package to download, build, and install it.

I've had it working on Xfce without a problem also when I was strictly using Slackware also.

_gin · 10-31-2013, 08:49 PM

Quote:

Originally Posted by kikinovak

Hi,
...
I'm using NetworkManager with the GNOME Network Manager applet...

Any suggestions?

Did you try to configure your connection with Wicd ?

kikinovak · 11-01-2013, 12:13 AM

OK, got it. I resolved the problem by simply installing the 'networkmanagement' applet for KDE. And it works. Keep It Stupid Stupid.