Usb wireless adapter recognition problem

quemexordium · 05-06-2017, 09:41 PM

Hello. I'm running Fedora 25 (4.10.13-200.fc25.x86_64). I bought TP LINK TL-WN722N v2 usb wireless adapter with rtl8188eus chipset but it wasn't seen in lsusb.

Here's the output:

Code:

Bus 002 Device 003: ID 8087:07da Intel Corp. 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0c45:644a Microdia 
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 2357:010c  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So I followed this tutorial to download and compile the files that are needed for rtl8188eu chipset:

Code:

sudo dnf install git dkms
cd /usr/src
sudo git clone https://github.com/lwfinger/rtl8188eu.git
sudo dkms add ./rtl8188eu
sudo dkms build 8188eu/1.0
sudo dkms install 8188eu/1.0
sudo modprobe 8188eu

I compiled them successfully. When I plugged in my usb wireless adapter, I saw the green light on it but it was still not seen in lsusb.

I actually can see USB wi-fi option in my wireless settings but I can't turn off my built-in wireless card. When I turn it off, my usb adapter gets turned off as well. And when they're both turned on, my computer uses its built-in wireless card instead of usb adapter. So I need help with blacklisting/disabling my built-in wireless card too.

But I don't believe that my usb wireless adapter is working/will work properly. Here are some things you might find useful about my situation:

iwconfig:

Code:

virbr0    no wireless extensions.

enp7s0    no wireless extensions.

lo        no wireless extensions.

wlp8s0    IEEE 802.11  ESSID:"Tenda_3281B8"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: C8:3A:35:32:81:B8   
          Bit Rate=150 Mb/s   Tx-Power=16 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=59/70  Signal level=-51 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:100   Missed beacon:0

virbr0-nic  no wireless extensions.

wlp0s20u1  unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ifconfig:

Code:

enp7s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e0:db:55:d0:13:7b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 584  bytes 52112 (50.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 584  bytes 52112 (50.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:a9:28:84  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp8s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.16  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::e07e:732a:4782:8927  prefixlen 64  scopeid 0x20<link>
        ether 84:a6:c8:e2:3f:c4  txqueuelen 1000  (Ethernet)
        RX packets 9682  bytes 8536301 (8.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8791  bytes 1336953 (1.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

And when I unplug my usb wireless adapter, run journalctl -fa as root and plug it in back, these lines show up:

Code:

May 07 04:54:10 localhost.localdomain kernel: usb 3-1: new high-speed USB device number 4 using xhci_hcd
May 07 04:54:10 localhost.localdomain kernel: usb 3-1: New USB device found, idVendor=2357, idProduct=010c
May 07 04:54:10 localhost.localdomain kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 07 04:54:10 localhost.localdomain kernel: usb 3-1: Product: 802.11n NIC
May 07 04:54:10 localhost.localdomain kernel: usb 3-1: Manufacturer: Realtek
May 07 04:54:10 localhost.localdomain kernel: usb 3-1: SerialNumber: 00E04C0001
May 07 04:54:10 localhost.localdomain kernel: Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
May 07 04:54:10 localhost.localdomain kernel: EEPROM ID = 0x8129
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.3240] (wlan0): driver supports SSID scans (scan_capa 0x3F).
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.3244] (wlan0): using WEXT for WiFi device control
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.3265] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/7)
May 07 04:54:10 localhost.localdomain mtp-probe[4212]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
May 07 04:54:10 localhost.localdomain mtp-probe[4212]: bus: 3, device: 4 was not an MTP device
May 07 04:54:10 localhost.localdomain kernel: r8188eu 3-1:1.0 wlp0s20u1: renamed from wlan0
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.3638] device (wlan0): interface index 8 renamed iface from 'wlan0' to 'wlp0s20u1'
May 07 04:54:10 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.3688] device (wlp0s20u1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 07 04:54:10 localhost.localdomain kernel: MAC Address = 18:d6:c7:1b:be:23
May 07 04:54:10 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.7053] (wlp0s20u1): driver supports SSID scans (scan_capa 0x3F).
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.7053] (wlp0s20u1): using WEXT for WiFi device control
May 07 04:54:10 localhost.localdomain kernel: R8188EU: INFO indicate disassoc
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <warn>  [1494122050.8131] device (wlp0s20u1): set-hw-addr: new MAC address 9E:CE:08:1D:82:7D not successfully set (scanning)
May 07 04:54:10 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: nl80211: Could not configure driver mode
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: nl80211: deinit ifname=wlp0s20u1 disabled_11b_rates=0
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: rfkill: Cannot get wiphy information
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: ioctl[SIOCSIWAP]: Operation not permitted
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.8372] sup-iface[0x556ca8ed9ec0,wlp0s20u1]: supports 1 scan SSIDs
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.8403] device (wlp0s20u1): supplicant interface state: starting -> ready
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.8404] device (wlp0s20u1): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 07 04:54:10 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
May 07 04:54:10 localhost.localdomain kernel: R8188EU: INFO indicate disassoc
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <warn>  [1494122050.9471] device (wlp0s20u1): set-hw-addr: new MAC address 9E:CE:08:1D:82:7D not successfully set (scanning)
May 07 04:54:10 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.9498] device (wlp0s20u1): supplicant interface state: ready -> disabled
May 07 04:54:10 localhost.localdomain NetworkManager[1052]: <info>  [1494122050.9756] device (wlp0s20u1): supplicant interface state: disabled -> inactive
May 07 04:54:12 localhost.localdomain kernel: R8188EU: INFO indicate disassoc
May 07 04:54:12 localhost.localdomain kernel: R8188EU: INFO indicate disassoc
May 07 04:54:12 localhost.localdomain NetworkManager[1052]: <warn>  [1494122052.2043] device (wlp0s20u1): set-hw-addr: new MAC address 9E:CE:08:1D:82:7D not successfully set (scanning)
May 07 04:54:12 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
May 07 04:54:12 localhost.localdomain NetworkManager[1052]: <info>  [1494122052.2075] device (wlp0s20u1): supplicant interface state: inactive -> disabled
May 07 04:54:12 localhost.localdomain NetworkManager[1052]: <info>  [1494122052.2249] device (wlp0s20u1): supplicant interface state: disabled -> inactive
May 07 04:54:12 localhost.localdomain kernel: R8188EU: INFO indicate disassoc
May 07 04:54:12 localhost.localdomain NetworkManager[1052]: <warn>  [1494122052.3324] device (wlp0s20u1): set-hw-addr: new MAC address 9E:CE:08:1D:82:7D not successfully set (scanning)
May 07 04:54:12 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
May 07 04:54:12 localhost.localdomain NetworkManager[1052]: <info>  [1494122052.3351] device (wlp0s20u1): supplicant interface state: inactive -> disabled
May 07 04:54:12 localhost.localdomain NetworkManager[1052]: <info>  [1494122052.3543] device (wlp0s20u1): supplicant interface state: disabled -> inactive
^C

And that's a part of dmesg:

Code:

//... hundreds of these lines above
[ 1890.348349] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1891.623549] R8188EU: INFO indicate disassoc
[ 1891.728457] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1891.753795] R8188EU: INFO indicate disassoc
[ 1891.858506] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1893.137503] R8188EU: INFO indicate disassoc
[ 1893.242992] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1893.273466] R8188EU: INFO indicate disassoc
[ 1893.376789] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1894.654152] R8188EU: INFO indicate disassoc
[ 1894.759570] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1894.787922] R8188EU: INFO indicate disassoc
[ 1894.812512] usb 3-1: USB disconnect, device number 3
[ 1949.002421] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[ 1949.170802] usb 3-1: New USB device found, idVendor=2357, idProduct=010c
[ 1949.170807] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1949.170809] usb 3-1: Product: 802.11n NIC
[ 1949.170812] usb 3-1: Manufacturer: Realtek
[ 1949.170813] usb 3-1: SerialNumber: 00E04C0001
[ 1949.171789] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[ 1949.193507] EEPROM ID = 0x8129
[ 1949.219123] r8188eu 3-1:1.0 wlp0s20u1: renamed from wlan0
[ 1949.240834] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1949.574442] MAC Address = 18:d6:c7:1b:be:23
[ 1949.576013] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1949.581444] R8188EU: INFO indicate disassoc
[ 1949.684472] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1949.712045] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1949.714881] R8188EU: INFO indicate disassoc
[ 1949.818540] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1950.944075] R8188EU: INFO indicate disassoc
[ 1950.970141] R8188EU: INFO indicate disassoc
[ 1951.075724] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1951.100357] R8188EU: INFO indicate disassoc
[ 1951.203776] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1952.476101] R8188EU: INFO indicate disassoc
[ 1952.581437] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1952.610922] R8188EU: INFO indicate disassoc
[ 1952.714595] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1953.981697] R8188EU: INFO indicate disassoc
[ 1954.087171] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1954.108929] R8188EU: INFO indicate disassoc
[ 1954.211569] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1955.491039] R8188EU: INFO indicate disassoc
[ 1955.594011] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1955.617911] R8188EU: INFO indicate disassoc
[ 1955.720677] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1956.982627] R8188EU: INFO indicate disassoc
[ 1957.087885] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1957.107509] R8188EU: INFO indicate disassoc
[ 1957.210229] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1958.483621] R8188EU: INFO indicate disassoc
[ 1958.588882] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1958.614798] R8188EU: INFO indicate disassoc
[ 1958.718297] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1960.001296] R8188EU: INFO indicate disassoc
[ 1960.106259] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1960.124105] R8188EU: INFO indicate disassoc
[ 1960.229232] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1961.504499] R8188EU: INFO indicate disassoc
[ 1961.610309] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1961.631492] R8188EU: INFO indicate disassoc
[ 1961.734781] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[ 1963.002802] R8188EU: INFO indicate disassoc
[ 1963.108053] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
//hundreds of these lines below...

There are like hundreds of exactly these lines in dmesg

I'm sorry if all these informations look overwhelming but I desperately need help. Thanks.

ondoho · 05-07-2017, 02:30 AM

Quote:

Originally Posted by quemexordium

So I need help with blacklisting/disabling my built-in wireless card too.

let's start with this, and with a bit of luck the other problems will go away, too...

please post the output of this:

Code:

lspci -knn | grep -EiA5 net

or maybe you don't even need to post it, it should show you the built-in wifi and which kernel driver it uses.
now all you have to do is blacklist that driver:

Create a new file under /etc/modprobe.d/ that contains the command blacklist name_of_driver. Give the file a descriptive name that will help you find it in future, and use the filename extension .conf. For example, to continue to blacklist the driver foobar when the root device is mounted, run:

Code:

echo "blacklist foobar" >> /mnt/sysimage/etc/modprobe.d/blacklist-foobar.conf

( https://docs.fedoraproject.org/en-US...cklisting.html )

quemexordium · 05-07-2017, 07:27 AM

Thanks for your answer. I actually managed to blacklist my built-in wireless card with creating "blacklist.conf" in /etc/modprobe.d/ and adding the line: "blacklist iwlwifi". But when I rebooted my machine, my usb wireless adapter didn't work either. There were no lights on it etc. And I didn't see USB Wi-Fi option in my wireless settings. I think they're somehow interconnected. When both my built-in and usb wireless adapter is turned on, my usb wireless adapter doesn't find any networks. It says "No Networks" which is a bit odd because although my built-in wireless is connected, my usb wireless adapter should be able to scan networks as well.

ardvark71 · 05-07-2017, 10:57 AM

Hi...

Can you confirm this adapter works correctly in another computer and/or operating system? Does this behavior change if you try plugging the adapter into another usb port?

Regards...

quemexordium · 05-07-2017, 11:15 AM

Quote:

Originally Posted by ardvark71

Hi...

Can you confirm this adapter works correctly in another computer and/or operating system? Does this behavior change if you try plugging the adapter into another usb port?

Regards...

Hey. Thanks for the answer. I've tried this adapter on Windows (on my laptop) and on another computer and it works perfectly out-of-the-box. So it can't be the adapter nor my usb sockets.

ondoho · 05-07-2017, 12:15 PM

Quote:

Originally Posted by quemexordium

But when I rebooted my machine, my usb wireless adapter didn't work either. There were no lights on it etc. And I didn't see USB Wi-Fi option in my wireless settings. I think they're somehow interconnected.

that doesn't make sense; are you sure this: https://github.com/lwfinger/rtl8188eu is actually the right driver for your usb device?
so the name of the driver is actually rtl8188eu?
have you followed ALL instructions from that page?

i think blacklisting the internal device was the right thing to do, maybe you're just a small step away from the solution.

other question:
why can't you use the builtin device?

quemexordium · 05-07-2017, 02:39 PM

Quote:

Originally Posted by ondoho

that doesn't make sense; are you sure this: https://github.com/lwfinger/rtl8188eu is actually the right driver for your usb device?
so the name of the driver is actually rtl8188eu?
have you followed ALL instructions from that page?

i think blacklisting the internal device was the right thing to do, maybe you're just a small step away from the solution.

other question:
why can't you use the builtin device?

Yes it is actually the right driver for my usb device. I installed Ubntu GNOME a couple of days ago and tried the same device in Ubuntu. At first, I thought its chipset was Atheros AR9271, tried to install the driver for AR9271 but I failed. So I created a thread on askubuntu: https://askubuntu.com/questions/9124...not-recognized

As you can see, New USB device found, idVendor=2357, idProduct=010c points out that its chipset is rtl8188eu. Also, the device's wiki page confirms that information: https://wikidevi.com/wiki/TP-LINK_TL-WN722N_v2

I also know it's the right driver because I've installed the same files in Ubuntu and my device worked. The reason why I changed my OS is that I'm sort of addicted to Fedora for some odd reason.

And to answer your question; I don't want to use my built-in wireless card because it doesn't support aircrack and I'm a bit far from the router.

And yes, I followed all the instructions that are described in the link (dkms ones) and I managed to install it without any errors. They worked in Ubuntu but I don't know why I'm having this problem in Fedora. Here's what I followed:

Code:

sudo dnf install git dkms
cd /usr/src
sudo git clone https://github.com/lwfinger/rtl8188eu.git
sudo dkms add ./rtl8188eu
sudo dkms build 8188eu/1.0
sudo dkms install 8188eu/1.0
sudo modprobe 8188eu

ondoho · 05-08-2017, 01:55 AM

Quote:

Originally Posted by quemexordium

And yes, I followed all the instructions that are described in the link (dkms ones) and I managed to install it without any errors. They worked in Ubuntu but I don't know why I'm having this problem in Fedora. Here's what I followed:

Code:

sudo dnf install git dkms
cd /usr/src
sudo git clone https://github.com/lwfinger/rtl8188eu.git
sudo dkms add ./rtl8188eu
sudo dkms build 8188eu/1.0
sudo dkms install 8188eu/1.0
sudo modprobe 8188eu

ok, so all this worked, no error messages i presume.

have you also noticed the FAQ:
The network manager says: "Device is not ready"!
Make sure you copied the firmware (rtl8188eufw.bin) to /lib/firmware/rtlwifi/

quemexordium · 05-08-2017, 07:56 AM

Quote:

Originally Posted by ondoho

ok, so all this worked, no error messages i presume.

have you also noticed the FAQ:
The network manager says: "Device is not ready"!
Make sure you copied the firmware (rtl8188eufw.bin) to /lib/firmware/rtlwifi/

Yes, I installed it successfully. No error or even warning messages.
I also copied the firmware to /lib/firmware/rtlwifi/ manually as it is said in FAQ. No changes. I think my dmesg output gives a hint about what's wrong but unfortunately I know nothing about all this.

ondoho · 05-09-2017, 12:24 AM

if i understand the journalctl output correctly, there seems to be yet another driver that is trying to access one of the wifi devices:

Code:

wpa_supplicant[1257]: nl80211: Could not configure driver mode
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: nl80211: deinit ifname=wlp0s20u1 disabled_11b_rates=0
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: rfkill: Cannot get wiphy information

i am not sure if i'm interpreting this correctly, but you should make sure that networkmanager really requires wpa_supplicant. if not, purge it (since we're going the networkmanager route all the way, right?).

further on, afaics, networkmanager is constantly trying to reconnect to the device, and fails without particular reason (though it seems to have sth to do with the mac address).
again, i'm not sure, but some things come to mind:
- try to disable hardware encryption (if that helps, it can be replaced by software encryption)
- try to disable power management.

quemexordium · 05-09-2017, 10:43 AM

Quote:

Originally Posted by ondoho

if i understand the journalctl output correctly, there seems to be yet another driver that is trying to access one of the wifi devices:

Code:

wpa_supplicant[1257]: nl80211: Could not configure driver mode
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: nl80211: deinit ifname=wlp0s20u1 disabled_11b_rates=0
May 07 04:54:10 localhost.localdomain wpa_supplicant[1257]: rfkill: Cannot get wiphy information

i am not sure if i'm interpreting this correctly, but you should make sure that networkmanager really requires wpa_supplicant. if not, purge it (since we're going the networkmanager route all the way, right?).

further on, afaics, networkmanager is constantly trying to reconnect to the device, and fails without particular reason (though it seems to have sth to do with the mac address).
again, i'm not sure, but some things come to mind:
- try to disable hardware encryption (if that helps, it can be replaced by software encryption)
- try to disable power management.

I don't know how to disable hardware encryption. I searched it but couldn't find anything helpful. Thanks for trying to help me though. I think I should slowly accept distro recommendations lol

I talked with the person who created that driver files on github and that's what he said:

"Your user-space system (NetworkManager, etc.) is not recognizing the USB device. That is a problem with that driver that I do not know how to fix.
Your solution will be to go to a new kernel (4.10) and use the rtl8xxxu in it."

So it's the driver, not me