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

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

I did do a full install of Slackware.

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

we are getting closer hang in there that is supported by the kernel. This version of the stick should be supported by the r8192u_usb kernel driver

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

need the output of lsusb . I need to know the revision the first revision do not work in linux may need to use a ndiswrapper that is where we use a windows driver for that device.

WBP · 12-23-2017, 09:01 PM

Quote:

Originally Posted by Drakeo

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

"dmesg | grep error" returned no results. After I typed it, I just got another prompt.

WBP · 12-23-2017, 09:04 PM

"lsusb" returned: Bus 001 Device 003: ID 07d1:3300 D-Link System DWA-130 802.11n Wireless N Adapter (rev.E) [ Realtek RTL8191SU]

Nille_kungen · 12-23-2017, 09:13 PM

Quote:

Originally Posted by Drakeo

I need to know the revision the first revision do not work in linux may need to use a ndiswrapper that is where we use a windows driver for that device.

IIRC ndiswrapper is for 32bit drivers, there for useless for an modern 64bit install, or does it work on multilib?
I don't now if TS has an 32 or 64 bit Slackware.

WBP · 12-23-2017, 09:27 PM

Quote:

Originally Posted by Nille_kungen

IIRC ndiswrapper is for 32bit drivers, there for useless for an modern 64bit install, or does it work on multilib?
I don't now if TS has an 32 or 64 bit Slackware.

I installed the 32 bit version of Slackware 14.2.

Drakeo · 12-23-2017, 09:53 PM

This is a learning curve for you.Your device is well supported by slackware. Kinda like riding a different bike.
the device works. You need to learn how to configure it.
always dhcp.

Drakeo · 12-23-2017, 10:18 PM

what are you using to chat with me with. hard wire or another computer ?

WBP · 12-23-2017, 10:35 PM

Another computer. I have a slackware and a windows machine side by side.

Drakeo · 12-23-2017, 11:01 PM

I am lost. https://docs.slackware.com/slackbook:wifi

WBP · 12-23-2017, 11:13 PM

Same here. I appreciate your help, though. You've gone above and beyond. I was messing around with the wicd-client and during the connection process it produced an error saying:

Connection failed: Bad Password

I googled it and found some info on an ubuntu forum that I'm currently looking over.

I went to the wpa_supplicant man page and found then ran "wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan0"

and got:

Successfully initialized wpa_supplicant
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: Failed to initialize driver interface

bassmadrigal · 12-23-2017, 11:29 PM

Ok, let's start from scratch and see what we can get to work. The first thing to do is to try and get wpa_supplicant to connect to the network manually. First, let's make sure your /etc/wpa_supplicant.conf file is set properly. We can use wpa_passphrase to generate that. Run the following replacing "your_ssid" and "your_password" with your info.

Code:

wpa_passphrase your_ssid your_password >> /etc/wpa_supplicant.conf

Now, we can try and run wpa_supplicant manually and see what it spits out. Run the following and paste the output here:

Code:

wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant.conf

Ideally, you should see something like this (I've masked some data for privacy reasons):

Code:

Successfully initialized wpa_supplicant
wlan0: SME: Trying to authenticate with XX:XX:XX:XX:1c:f4 (SSID='MYSSID' freq=5260 MHz)
wlan0: Trying to associate with XX:XX:XX:XX:1c:f4 (SSID='MYSSID' freq=5260 MHz)
wlan0: Associated with XX:XX:XX:XX:1c:f4
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: WPA: Key negotiation completed with XX:XX:XX:XX:1c:f4 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:1c:f4 completed [id=0 id_str=]

Notice how at the bottom it states that the connection has completed? That should mean that wpa_supplicant is successfully connected to your router. Right now, we're running this in the foreground so we can see any messages, so any further commands will need to be entered in a new terminal window. Now you should be able to run iwconfig and have it show that it's associated with a network.

Code:

jbhansen@craven-moorhead:~$ iwconfig
tun0      no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11  ESSID:"MYSSID"
          Mode:Managed  Frequency:5.26 GHz  Access Point: XX:XX:XX:XX:1C:F4
          Bit Rate=200 Mb/s   Tx-Power=22 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=62/70  Signal level=-48 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:6   Missed beacon:0

Now that you're this far, you should just need to run dhcpcd wlan0 to request an IP address for your wlan0. If this works and you get online, you can Ctrl+C your wpa_supplicant program and then add a -B to the command, which will cause it to run in the background, so you don't need to keep it up in a terminal.

Code:

wpa_supplicant -B -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant.conf

If you get this far, then we know your driver works and wpa_supplicant works with your card/driver. Beyond that, we'll then need to troubleshoot either wicd or Network Manager, or, if you don't intend to connect this device to many new networks, we can set it up to work with rc.inet1 without requiring wicd or Network Manager.

If you don't get the whole way through, please copy and paste any error messages into your post and we'll see what went wrong and git it resolved.

WBP · 12-23-2017, 11:42 PM

Quote:

Originally Posted by bassmadrigal

Ok, let's start from scratch and see what we can get to work. The first thing to do is to try and get wpa_supplicant to connect to the network manually. First, let's make sure your /etc/wpa_supplicant.conf file is set properly. We can use wpa_passphrase to generate that. Run the following replacing "your_ssid" and "your_password" with your info.

Code:

wpa_passphrase your_ssid your_password >> /etc/wpa_supplicant.conf

Now, we can try and run wpa_supplicant manually and see what it spits out. Run the following and paste the output here:

Code:

wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant.conf

Ideally, you should see something like this (I've masked some data for privacy reasons):

Code:

Successfully initialized wpa_supplicant
wlan0: SME: Trying to authenticate with XX:XX:XX:XX:1c:f4 (SSID='MYSSID' freq=5260 MHz)
wlan0: Trying to associate with XX:XX:XX:XX:1c:f4 (SSID='MYSSID' freq=5260 MHz)
wlan0: Associated with XX:XX:XX:XX:1c:f4
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: WPA: Key negotiation completed with XX:XX:XX:XX:1c:f4 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:1c:f4 completed [id=0 id_str=]

Notice how at the bottom it states that the connection has completed? That should mean that wpa_supplicant is successfully connected to your router. Right now, we're running this in the foreground so we can see any messages, so any further commands will need to be entered in a new terminal window. Now you should be able to run iwconfig and have it show that it's associated with a network.

Code:

jbhansen@craven-moorhead:~$ iwconfig
tun0      no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11  ESSID:"MYSSID"
          Mode:Managed  Frequency:5.26 GHz  Access Point: XX:XX:XX:XX:1C:F4
          Bit Rate=200 Mb/s   Tx-Power=22 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=62/70  Signal level=-48 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:6   Missed beacon:0

Now that you're this far, you should just need to run dhcpcd wlan0 to request an IP address for your wlan0. If this works and you get online, you can Ctrl+C your wpa_supplicant program and then add a -B to the command, which will cause it to run in the background, so you don't need to keep it up in a terminal.

Code:

wpa_supplicant -B -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant.conf

If you get this far, then we know your driver works and wpa_supplicant works with your card/driver. Beyond that, we'll then need to troubleshoot either wicd or Network Manager, or, if you don't intend to connect this device to many new networks, we can set it up to work with rc.inet1 without requiring wicd or Network Manager.

If you don't get the whole way through, please copy and paste any error messages into your post and we'll see what went wrong and git it resolved.

Hi bassmadrigal,

When I run "wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_supplicant.conf" I get the following output:

Successfully initialized wpa_supplicant
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.

Should I go ahead and delete /var/run/wpa_supplicant/wlan0 ?

Richard Cranium · 12-24-2017, 12:25 AM

You'll have to turn off wicd before running those commands.