[SOLVED] Can't get Wi-Fi working in Slackware 14.2 with usb adapter and networkmanager

enorbet · 12-22-2017, 10:46 PM

Just an anecdote but while NetworkManager is convenient its a tad buggy. I use it where it works. Where it doesn't I use the provided "wicd" and enjoy the visual help of --- WiFi Radar --- . I don't use much wifi anymore but that combo has saved me bacon on a few occasions.

Just a snafu check - Since what you hve has apparently tried to connect but has some problem with password handshaking are you absolutely certain both match in protocols AND that the password isn't suffering from a typo?

Richard Cranium · 12-22-2017, 11:30 PM

Quote:

Originally Posted by Drakeo

in the begenning I said you should use wicd. there is a reason why Pat has had it in the extra for many years. Networkmanger is default for kde. we leave it in slackware.

The reason wicd is in /extra is that it used to be the way to connect to random wireless networks. Networkmanager is the newer way to connect to random wireless networks.

If you don't need to connect to random wireless networks, there are other ways to connect to known wireless networks that require neither wicd nor Networkmanager.

Drakeo · 12-23-2017, 12:08 AM

Quote:

Originally Posted by Richard Cranium

The reason wicd is in /extra is that it used to be the way to connect to random wireless networks. Networkmanager is the newer way to connect to random wireless networks.

If you don't need to connect to random wireless networks, there are other ways to connect to known wireless networks that require neither wicd nor Networkmanager.

Thank you. IF anyone would know you would. It has saved me a few times. I understand. Good thing is to read that wifi document. You get a better Idea of the process.

Nille_kungen · 12-23-2017, 10:53 AM

Is there only problems to connect to your network?
Some rtl devices has problems to connect but usually /var/log/messages shows more information.
I got an RTL8192EU that doesn't work with linux, i e-mailed the developer and the answer was " The 8192eu devices seem to have problems at times loading the driver if the device is already powered up." and he hopped he would get time to look into it.
I got my driver loaded and things looked ok but i couldn't connect to any network with that one.

WBP · 12-23-2017, 06:45 PM

Quote:

Originally Posted by Drakeo

in the begenning I said you should use wicd. there is a reason why Pat has had it in the extra for many years. Networkmanger is default for kde. we leave it in slackware.
your device is seen

https://docs.slackware.com/slackbook:wifi

read to the wicd section. and make networkmanager non-executable. and do as Pat says in the wicd section.
in the slackware install dvd there is a folder extra/packages/wicd.
Networkmanager is buggy.

I followed the instructions from the link, and I'm still not able to connect.

I ran "iwconfig wlan0 essid mynetwork freq 2.462G.

Then I edited /etc/wpa_supplicant.conf. At first there was only two lines in the file: ctrl_interface=/var/run/wpa_supplicant and ctrl_interface_group=root. A Google search revealed this was normal if I had chosen to let networkmanager configure my network during the initial installation, which I had. So, I added the lines from the example. Replacing SSID and PSK with my own. I'll admit I wasn't 100% on what a psk is, after not being able to log into my router I phoned my service provider and they told me that the psk is the same as the password I use to connect to mynetwork.

I ran "wpa_supplicant" and received this message: Successfully initialized wpa_supplicant.

Next I edited /etc/rc.d/rc.inet1.conf and set it up exactly the same as the one in Slackbook:wifi.

I made networkmanager unexecutable.

I installed wicd from the dvd, then started it.

Then I ran wicd-curses, selected my network and received these messages:

Putting interface up...
Validating authentication...
Not connected.

I decided to reboot just to be sure, and received these messages when booting:

...
/etc/rc.d/rc.M: wlan0 information: 'Any ESSID'
Error for wireless request "Set Nickname" (8B1C) :
SET failed on device wlan0 ; Function not implemented.
Successfully initialized wpa_supplicant
rfill: Cannot open RFKILL control device
ioctl[SIOCSIWAP]: Device or resource busy
ioctl[SIOCSIWESSID]: Device or resource busy
Polling for DHCP server on interface wlan0:
all:IPv6 kernel autoconf disabled
wlan0: adding address fe80::6121:8de2:8d0a:e3f4
if_addaddress6: Operation not supported
wlan0: waiting for carrier...
timed out
dhcpcd exited

Is there anything else that I can try?

WBP · 12-23-2017, 06:51 PM

Quote:

Originally Posted by enorbet

Just an anecdote but while NetworkManager is convenient its a tad buggy. I use it where it works. Where it doesn't I use the provided "wicd" and enjoy the visual help of --- WiFi Radar --- . I don't use much wifi anymore but that combo has saved me bacon on a few occasions.

Just a snafu check - Since what you hve has apparently tried to connect but has some problem with password handshaking are you absolutely certain both match in protocols AND that the password isn't suffering from a typo?

Thanks for the tip about wifiradar

I have disabled networkmanager and now am running is wicd. How can I check if both passwords match in protocols? I've checked and rechecked the passwords and no typos.

WBP · 12-23-2017, 06:55 PM

Quote:

Originally Posted by Nille_kungen

Is there only problems to connect to your network?
Some rtl devices has problems to connect but usually /var/log/messages shows more information.
I got an RTL8192EU that doesn't work with linux, i e-mailed the developer and the answer was " The 8192eu devices seem to have problems at times loading the driver if the device is already powered up." and he hopped he would get time to look into it.
I got my driver loaded and things looked ok but i couldn't connect to any network with that one.

Well, the adapter I'm using was originally used with Vista, and at my old residence. It had no problem connecting. It was last used in April of this year.

Interesting. Maybe it would be a good idea to look into a different type of adapter?

Drakeo · 12-23-2017, 06:59 PM

Code:

 safe using an 8 character alphanumeric pass phrase key to secure a home Wireless LAN using WPA-PSK or WPA2-PSK
 using these simple guidelines. A simple random 8 character alphanumeric WPA-PSK key would look something 
like 2b8uwo35 which is very easy to handle.

your router your wifi wpsk2

WBP · 12-23-2017, 07:03 PM

Quote:

Originally Posted by Drakeo

Code:

 safe using an 8 character alphanumeric pass phrase key to secure a home Wireless LAN using WPA-PSK or WPA2-PSK
 using these simple guidelines. A simple random 8 character alphanumeric WPA-PSK key would look something 
like 2b8uwo35 which is very easy to handle.

your router your wifi wpsk2

Under network settings in Windows 10 it says security type is WPA2.

Drakeo · 12-23-2017, 07:04 PM

look your getting stressed ok. .
step one the device is seen.
step 2 that boot means the device is not associated with a profile.
step three you make a profile per essid.
find the essid put the key in and connect. if it does not connect
then open a terminal type su then password then type dmesg
paste the bottm here.

it would never find the essid if it was not up and talking.

Drakeo · 12-23-2017, 07:07 PM

Quote:

I got an RTL8192EU that doesn't work with linux, i e-mailed the developer and the answer was " The 8192eu devices seem to have problems at times loading the driver if the device is already powered up." and he hopped he would get time to look into it.
I got my driver loaded and things looked ok but i couldn't connect to any network with that one.

well lets see if the firmware is loading from the dmesg

Nille_kungen · 12-23-2017, 07:22 PM

Quote:

Originally Posted by WBP

Well, the adapter I'm using was originally used with Vista, and at my old residence. It had no problem connecting. It was last used in April of this year.

Interesting. Maybe it would be a good idea to look into a different type of adapter?

The reason i got a fair sum of usb adapters is that i had a laptop for a short while where the network was disconnecting all the time and when i was a bit angry i went on ebay and bought one of every cheap adapter i could find.
While it might sound a bit extreme the total wasn't really that much but i can say that even if it says that it works in linux it's not always true.
Also some adapters change chips overtime.
The adapters are so cheap on ebay that it's not worth putting time into an problematic adapter, also the chipping takes some time.

WBP · 12-23-2017, 07:39 PM

Quote:

Originally Posted by Drakeo

look your getting stressed ok. .
step one the device is seen.
step 2 that boot means the device is not associated with a profile.
step three you make a profile per essid.
find the essid put the key in and connect. if it does not connect
then open a terminal type su then password then type dmesg
paste the bottm here.

it would never find the essid if it was not up and talking.

Okay I ran wicd-client, found my network, went into properties, entered the password, then saved and "setting encryption info..." appeared in the terminal. I hit connect then received this message:

/usr/shar/wice/gtk/gui.py:583: Warning: source ID 53 was not found when attempting to remove it
gobject.source_remove(self.update_cb)
ERROR:dbus.connection: Exception in handler for D-bus signal:
Traeback (most recent call last):
File "/usr/lib/python2.7/site-packages/dbus/connetion.py", line 230, in maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/shar/wicd/gtk/gui.py", line 281, in handle_connection_results
error(self.window, language[results], block=False)
KeyError: dbus.String(u'bad_pass')
...

Then it just hangs.

The last line of dmesg:

{ 8337.421308] IPv6: ADDRCONF (NETDEV_UP): wlan0: link is not ready

Drakeo · 12-23-2017, 08:24 PM

did you do a full install ??

Drakeo · 12-23-2017, 08:31 PM

dmesg | grep error
see how many errors we have.
See if the firmware is not loading for it