WiFi adaptor (DL-DWA-131) (seems) working but cannot connect

Hi, there.
I’ve just set a WiFi adaptor, D-Link wireless N Nano usb adaptor DWA-131 so afterwards identify the interface name with the $ iw dev command I could manage , or I thought I did, to set it, following the below sequence of commands and now I see displayed the potential ESSID's around, including myESSID yep, but whenever I tried to connect by the following command:

$ nmcli -ask device wifi connect myESSID ;which will ask for my [password] ;so typing it.

I got the following output:

Error: Connection activation failed: (53) The Wi-Fi network could not be found.

It reads not found but the scanning functionality says the opposite. The Network-Manager applet is indeed displaying the ESSID list correctly. Would anyone know to tell what’s happening, give a clue or something? I’d appreciate it.

Here below the list of commands, I did use to set up the WIFI adaptor. ; ~~ means the/my interface name wlp0s20f0u3 , though some posts online have it as wlp0 etc.
$ iw ~~ link ; ~~ interface just output
$ sudo iw ~~ scan
$ sudo ip link set ~~ up

;; when at output: >>> RTNETLINK answers: Operation not possible due to RF-kill

$ rfkill list all
$ rfkill --output ID,TYPE
$ rfkill unblock wlan ;because wlan (from the above output) was the one ‘soft-blocked

;;now checking again with $ rfkill --output ID,TYPE (it should show all ‘no’ /so unblocked) and It does actually.

;; now up again:

$ sudo ip link set ~~ up

$ nmcli r wifi on

1 Like

Check this and post the output here:

uname -a
lsusb
lsusb -v -s BUS_ID:DEV_ID
nmcli radio all
nmcli device

Hi, thanks for your reply. Here the output I got for those commands:

$ uname -a
Linux btxarly 5.2.11-100.fc29.x86_64 #1 SMP Thu Aug 29 12:52:22 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 18f8:0f97 [Maxxter]
Bus 001 Device 005: ID 0c76:161e JMTek, LLC.
Bus 001 Device 004: ID 1c4f:0016 SiGma Micro
Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 002: ID 2001:3319 D-Link Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ lsusb -v -s BUS_ID:DEV_ID
not output

$ nmcli radio all
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled enabled

$ nmcli device
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet connected enp2s0
wlp0s20f0u3 wifi disconnected –
lo loopback unmanaged –

1 Like

Looks like it requires this driver:

And we also have a successfully resolved thread about installing this driver on Fedora 30:

Hi, @vgaetera thanks for the info, is quite complex I’m still reading up on it (especially regarding an issue I had in the past with some software I needed to install but being not free software it got tainted and continuously warned by the system). I will post back reporting how it works for me.

1 Like

So, reading up on those posts and trying to list a sequence of commands I got this first draft, though reading the building guide by Mange I cannot get yet how-to that reference to (DKMS) Dynamic Kernel Module Support works on Fedora(29).

;;Aniway, first make sure the system is updated

# dnf update

;; install rpmbuild

# dnf install rpm-build
# dnf install kernel-devel
# dnf groupinstall 'Development Tools'

;; Then the building zone, first dowload the drivers
;; sources of drivers

ftp://files.dlink.com.au/products/DWA-131/REV_E/Drivers/DWA-131_Linux_driver_v4.3.1.1.zip

;; Also following reference, another source of the drivers

http://files.dlink.com.au/products/DWA-131/REV_E/Drivers/DWA-131_Linux_driver_v4.3.1.1.zip

;;Then get into de dir where you had downloaded it and make by?
# rpmbuild -- the-driver-just-downloaded

Is it that Okay??

1 Like