Can't install TP-Link TL-WN832N USB modem


#1

CAN‘T INSTALL TP-LINK TL-WN823N USB WiFi MODEM

A few months ago, I accidentally turned off my WiFi card on my Compaq Presario CQ57 and since then I‘ve found that there is no way of ever turning it on again, so I‘ve had to accept that it‘s dead. It happened just because I stopped the installation of Manjaro Linux too late by pressing the power button. Please make absolutely sure what you‘re doing before that, otherwise the same thing may happen to you.

I plan to go on a trip soon. I own two laptops, so I want to take my cheaper laptop mentioned above with me, instead of my more expensive Toshiba Satellite L750, in case I lose it.

I‘ve just bought a TP-LINK TL-WN823N USB WiFi modem, because Linux Format magazine (UK) recommended it in an article about hacking.

After receiving this modem, I read on the packaging that it actually supports Linux! There‘s an accompanying DVD, which I assumed was just for Windows and Mac OSX, so I left that to one side for the moment. I plugged in the USB WiFi modem and booted into Manjaro Linux, but found that I still couldn‘t turn on my WiFi. The same thing happened under Linux Mint.

I inserted the DVD, which I found mentioned Linux! Unfortunately, all it said was to download a Linux driver from www.tp-link.com , so I went there to searh for it. I soon found and downloaded the driver. It seems this was written for an earlier Linux Kernal which no one should be using anmore, but I hoped it was compatible with my system.

Unfortunately, my problems started with instructions which didn‘t mention any particular Linux distros. I had to use the shell to navigate to the right directory after unpacking a .zip file. I found that one of these directory names included the ( character, which produced an error message when trying to cd to it. I had to rename this directory so I could cd to it. After using cd to get into the directory I was able to give the sudo make command, which failed with the error no rules to make modules! I didn‘t notice this error at firsz, then gave the command sudo make install failed with the error message can‘t find 8192eu.ko.

Here‘s the output of my bash session where I tried to install it. Some error messages are in German, because I‘m trying to learn how to do everything in German, but the errors are as described above.

[paulb@paul-pc ~]$ ls
Bilder  Dokumente  Downloads  Musik  Öffentlich  Schreibtisch  Videos  Vorlagen
[paulb@paul-pc ~]$ cd Downloads
[paulb@paul-pc Downloads]$ ls
HP_Device_Manager-4.4.exe   TL-WN823NEU_V2_160315_Linux  'TL-WN823N(EU)_V2_160315_Linux_1479970241132h.zip'
[paulb@paul-pc Downloads]$ cd TL-WN823NEU_V2?160315_Linux
[paulb@paul-pc TL-WN823NEU_V2_160315_Linux]$ ls
'TL-WN823N(EU)_V2_160315_Linux'
[paulb@paul-pc TL-WN823NEU_V2_160315_Linux]$ sudo make
[sudo] Passwort für paulb:  
make: *** Es wurden keine Ziele angegeben und keine „make“-Steuerdatei gefunden.  Schluss.
[paulb@paul-pc TL-WN823NEU_V2_160315_Linux]$ ls
'TL-WN823N(EU)_V2_160315_Linux'
[paulb@paul-pc TL-WN823NEU_V2_160315_Linux]$ cd TL-WN823N(EU)_V2_160315_Linux  
bash: Syntaxfehler beim unerwarteten Wort `('
[paulb@paul-pc TL-WN823NEU_V2_160315_Linux]$ ls
newWiFi
[paulb@paul-pc TL-WN823NEU_V2_160315_Linux]$ cd newWiFi
[paulb@paul-pc newWiFi]$ ls
Driver  'Installation for linux driver_RTL.pdf'   Thumbs.db
[paulb@paul-pc newWiFi]$ cd Driver
[paulb@paul-pc Driver]$ ls
bin  clean  core  hal  ifcfg-wlan0  include  Kconfig  Makefile  os_dep  platform  runwpa  wlan0dhcp  wpa_0_8.conf
[paulb@paul-pc Driver]$ sudo make
[sudo] Passwort für paulb:  
"******************************************"
"NO SKRC,we will use default KSRC"
"******************************************"
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.9.34-1-MANJARO/build M=/home/paulb/Downloads/TL-WN823NEU_V2_160315_Linux/newWiFi/Driver  modules
make[1]: Verzeichnis „/usr/lib/modules/4.9.34-1-MANJARO/build“ wird betreten
make[1]: *** Keine Regel, um „modules“ zu erstellen.  Schluss.
make[1]: Verzeichnis „/usr/lib/modules/4.9.34-1-MANJARO/build“ wird verlassen
make: *** [Makefile:1696: modules] Fehler 2
[paulb@paul-pc Driver]$ sudo make install
"******************************************"
"NO SKRC,we will use default KSRC"
"******************************************"
install -p -m 644 8192eu.ko  /lib/modules/4.9.34-1-MANJARO/kernel/drivers/net/wireless/
install: der Aufruf von stat für '8192eu.ko' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
make: *** [Makefile:1702: install] Fehler 1
[paulb@paul-pc Driver]$

#2

Two things:

This is very old. Have you updated recently? Running old software on a rolling distro is a bad idea as you’re not getting any security updates.

https://forum.manjaro.org/search?q=8192eu

and


#3

I’m fairly new to Manjaro, after using Mint and Ubuntu for several years. I started off with Red Hat and Mandrake.

I get notifications from Octopi regularly, then I update my system.

As for the other topic in German which has been solved, I’ve looked at that before posting this topic and come to the conclusion that whatever it was that was causing the problem, nothing mentioned there would work for me.


#4

Some things. First update your system with pacman. Since it is probably a new Kernel available, you need to do a reboot.

sudo pacman -Syu

Are you sure you need this TP-Link Software/Driver? Did you test without.
Then since it is a Kernel Module you need to install the Kernel Header for your running Kernel.

pacman -S linux49-headers

Also do not run make as root. Do it only for make install.
Also if this is a 8192eu chip, then just install 8192eu-dkms form aur.


#5

xabbu , I’ve just carried out all of your suggestions. It took me about an hour or more. The end result is NO CONNECTION from the TP-Link TL-WN823N! I’ve clicked next to the WiFi icon and it shows no networks at all.


#6

Then you have to look in the logs. Specially what happens when you plug the TP-Link Stick in. Also did you install 8192eu-dkms or did you build and install the Driver/Module form TP-Link?

The easiest might be

sudo journalctl -f 

start the command before you plug in the TP-Link device. It might be also interesting wich module was loaded. Since it was loaded when you first plugged in the stick you might want look at dmesg.


#7

Here you go then. Now tell me what it means! BTW I plan to go on m< trip in about a week.

[paulb@paul-pc ~]$ sudo journalctl -f 
[sudo] Passwort für paulb: 
-- Logs begin at Wed 2017-07-12 01:04:38 BST. --
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]:        Last update :  QDateTime(2017-10-06 02:30:44.000 BST Qt::TimeSpec(LocalTime))
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]: After the adjustment
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]:      Current score :  4.56112
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]:       First update :  QDateTime(2017-07-12 10:29:20.000 BST Qt::TimeSpec(LocalTime))
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]:        Last update :  QDateTime(2017-10-06 02:30:44.000 BST Qt::TimeSpec(LocalTime))
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]: Interval length is  0
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]:          New score :  5.56112
Oct 06 02:32:45 paul-pc kactivitymanagerd[11924]: ResourceScoreUpdated: "ca0a95d2-adfa-4642-9ea6-0c98c0c38c27" "org.kde.plasma.kicker" "applications:org.kde.konsole.desktop"
Oct 06 02:32:58 paul-pc sudo[15742]:    paulb : TTY=pts/6 ; PWD=/home/paulb ; USER=root ; COMMAND=/usr/bin/journalctl -f
Oct 06 02:32:58 paul-pc sudo[15742]: pam_unix(sudo:session): session opened for user root by paulb(uid=0)
Oct 06 02:33:07 paul-pc kernel: usb 1-1: new high-speed USB device number 3 using ehci-pci
Oct 06 02:33:08 paul-pc kernel: usb 1-1: Vendor: Realtek
Oct 06 02:33:08 paul-pc kernel: [29B blob data]
Oct 06 02:33:08 paul-pc kernel: usb 1-1: Serial: 
Oct 06 02:33:08 paul-pc kernel: usb 1-1: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 00: 29 81 00 7c 01 40 03 00
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 08: 40 74 04 50 14 00 00 00
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 10: 29 29 28 28 28 28 2c 2c
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 18: 2c 2b 2b f2 ef ef ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 20: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 28: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 30: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 38: ff ff 2a 2a 28 27 27 27
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 40: 2c 2c 2a 29 29 f2 ef ef
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 48: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 50: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 58: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 60: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 68: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 70: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 78: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 80: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 88: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 90: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 98: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: a0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: a8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: b0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: b8: a1 0e 1f 00 00 00 ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: c0: ff 01 00 10 00 00 00 ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: c8: 00 00 ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: d0: 57 23 09 01 e7 47 02 c0
Oct 06 02:33:08 paul-pc kernel: usb 1-1: d8: 25 e9 19 d8 8f 0a 03 52
Oct 06 02:33:08 paul-pc kernel: usb 1-1: e0: 65 61 6c 74 65 6b 20 0e
Oct 06 02:33:08 paul-pc kernel: usb 1-1: e8: 03 38 30 32 2e 31 31 6e
Oct 06 02:33:08 paul-pc kernel: usb 1-1: f0: 20 4e 49 43 20 00 00 ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: f8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 100: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 108: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 110: ff ff ff ff ff ff ff 0d
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 118: 03 00 05 00 30 00 00 00
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 120: 00 93 ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 128: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 130: f6 a8 98 2d 03 92 98 00
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 138: fc 8c 00 11 9b 44 02 0a
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 140: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 148: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 150: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 158: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 160: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 168: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 170: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 178: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 180: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 188: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 190: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 198: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1a0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1a8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1b0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1b8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1c0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1c8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1d0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1d8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1e0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1e8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1f0: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: 1f8: ff ff ff ff ff ff ff ff
Oct 06 02:33:08 paul-pc kernel: usb 1-1: RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
Oct 06 02:33:08 paul-pc kernel: usb 1-1: RTL8192EU MAC: c0:25:e9:19:d8:8f
Oct 06 02:33:08 paul-pc kernel: usb 1-1: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
Oct 06 02:33:08 paul-pc kernel: usb 1-1: Firmware revision 19.0 (signature 0x92e1)
Oct 06 02:33:09 paul-pc systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 06 02:33:09 paul-pc NetworkManager[418]: <info>  [1507253589.2633] wifi-nl80211: (wlan0): using nl80211 for WiFi device control
Oct 06 02:33:09 paul-pc mtp-probe[15746]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-1"
Oct 06 02:33:09 paul-pc mtp-probe[15746]: bus: 1, device: 3 was not an MTP device
Oct 06 02:33:09 paul-pc NetworkManager[418]: <info>  [1507253589.2767] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/5)
Oct 06 02:33:09 paul-pc org_kde_powerdevil[11994]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "AllDevices"
Oct 06 02:33:09 paul-pc org_kde_powerdevil[11994]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Devices"
Oct 06 02:33:09 paul-pc kdeinit5[11111]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
Oct 06 02:33:09 paul-pc kdeinit5[11111]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
Oct 06 02:33:09 paul-pc plasmashell[11742]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
Oct 06 02:33:09 paul-pc plasmashell[11742]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
Oct 06 02:33:09 paul-pc kdeinit5[11111]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
Oct 06 02:33:09 paul-pc kdeinit5[11111]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
Oct 06 02:33:09 paul-pc kdeinit5[11111]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "AllDevices"
Oct 06 02:33:09 paul-pc kdeinit5[11111]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Devices"
Oct 06 02:33:09 paul-pc plasmashell[11742]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "LldpNeighbors"
Oct 06 02:33:09 paul-pc plasmashell[11742]: networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
Oct 06 02:33:09 paul-pc plasmashell[11742]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "AllDevices"
Oct 06 02:33:09 paul-pc plasmashell[11742]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Devices"
Oct 06 02:33:09 paul-pc systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 06 02:33:09 paul-pc NetworkManager[418]: <info>  [1507253589.8534] rfkill3: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/ieee80211/phy2/rfkill3) (driver rtl8xxxu)
Oct 06 02:33:09 paul-pc systemd-udevd[15757]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 06 02:33:09 paul-pc kernel: rtl8xxxu 1-1:1.0 wlp0s18f2u1: renamed from wlan0
Oct 06 02:33:09 paul-pc NetworkManager[418]: <info>  [1507253589.8730] device (wlan0): interface index 5 renamed iface from 'wlan0' to 'wlp0s18f2u1'
Oct 06 02:33:09 paul-pc dolphin[12226]: org.kde.baloo: "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/net/wlp0s18f2u1"
Oct 06 02:33:09 paul-pc dolphin[12226]: QObject::connect: invalid null parameter
Oct 06 02:33:09 paul-pc dolphin[12126]: org.kde.baloo: "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/net/wlp0s18f2u1"
Oct 06 02:33:09 paul-pc dolphin[12126]: QObject::connect: invalid null parameter
Oct 06 02:33:09 paul-pc dolphin[12193]: org.kde.baloo: "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/net/wlp0s18f2u1"
Oct 06 02:33:09 paul-pc dolphin[12193]: QObject::connect: invalid null parameter
Oct 06 02:33:09 paul-pc NetworkManager[418]: <info>  [1507253589.8957] device (wlp0s18f2u1): state change: unmanaged -> unavailable (reason 'managed', internal state 'external')
Oct 06 02:33:09 paul-pc kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s18f2u1: link is not ready
Oct 06 02:33:09 paul-pc NetworkManager[418]: <info>  [1507253589.8970] device (wlp0s18f2u1): set-hw-addr: set MAC address to EE:B3:79:FC:34:94 (scanning)
Oct 06 02:33:09 paul-pc kdeinit5[11111]: QObject::connect: invalid null parameter
Oct 06 02:33:09 paul-pc baloo_file[11737]: org.kde.baloo: "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/net/wlp0s18f2u1"
Oct 06 02:33:09 paul-pc baloo_file[11737]: QObject::connect: invalid null parameter
Oct 06 02:33:09 paul-pc dolphin[12226]: UdevQt: unhandled device action "move"
Oct 06 02:33:09 paul-pc dolphin[12126]: UdevQt: unhandled device action "move"
Oct 06 02:33:09 paul-pc dolphin[12193]: UdevQt: unhandled device action "move"
Oct 06 02:33:09 paul-pc krunner[11740]: UdevQt: unhandled device action "move"
Oct 06 02:33:09 paul-pc plasmashell[11742]: file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property 'width' of null
Oct 06 02:33:09 paul-pc plasmashell[11742]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipInstance.qml:418: ReferenceError: VirtualDesktop is not defined
Oct 06 02:33:09 paul-pc org_kde_powerdevil[11994]: UdevQt: unhandled device action "move"
Oct 06 02:33:09 paul-pc kdeinit5[11111]: UdevQt: unhandled device action "move"
Oct 06 02:33:09 paul-pc baloo_file[11737]: UdevQt: unhandled device action "move"
Oct 06 02:33:09 paul-pc plasmashell[11742]: UdevQt: unhandled device action "move"
Oct 06 02:33:12 paul-pc ModemManager[220]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:12.2/usb1/1-1': not supported by any plugin
Oct 06 02:33:47 paul-pc plasmashell[11742]: log_klipper: Checking clip data
Oct 06 02:33:47 paul-pc plasmashell[11742]: log_klipper: Synchronize? false
Oct 06 02:33:51 paul-pc plasmashell[11742]: log_klipper: Checking clip data
Oct 06 02:33:52 paul-pc plasmashell[11742]: log_klipper: Synchronize? false
Oct 06 02:33:55 paul-pc plasmashell[11742]: log_klipper: Checking clip data
Oct 06 02:33:55 paul-pc plasmashell[11742]: log_klipper: Synchronize? false
Oct 06 02:34:06 paul-pc plasmashell[11742]: log_klipper: Checking clip data
Oct 06 02:34:06 paul-pc plasmashell[11742]: log_klipper: Synchronize? false
^C
[paulb@paul-pc ~]$ ^C
[paulb@paul-pc ~]$

#8

You might want to get a different spare Dongle, just in case.

Firmware found and loaded. This is a very good sign.

There is your Device Name wlp0s18f2u1

Looking for channels.
So it should be working.

If not you might look closer to the log from NM. Start the command before you plug in the device.

 journalctl -u NetworkManager -f

Also you might try to do a scan from the command line. Do the steps until you can do a scan. No need to configure and connect to a network.
https://wiki.archlinux.org/index.php/Wireless_network_configuration#Manual_setup


#9

One thing I just noticed.

This is the Mainline Kernel driver. It is not the 8192eu Driver you installed with 8192eu-dkms.
After reading the latest two AUR comments form 8192eu-dkms, it seems you have two options. Stay with Kernel 4.9 and blacklist or try Kernel 4.13 with it your Wifi should work out of the box.

I do not use this package anymore because my adapter (TP-Link TL-WN823N v2) is now supported by the rtl8xxxu driver and works fine.

I would personally try Kernel 4.13 first, but it seems this Kernel is at the moment not that stable. So you might try the blacklist. You can install Kernel 4.13 with mhwd-kernel

sudo mhwd-kernel -i linux413 

If it isn’t working, then you need to blacklist rtl8xxxu.
https://wiki.archlinux.org/index.php/Kernel_modules#Using_files_in_.2Fetc.2Fmodprobe.d.2F_2
and/or read the latest comment on 8192eu-dkms in aur.
https://aur.archlinux.org/packages/8192eu-dkms/


#10

I’m fairly new to Manjaro Linux. The techniques of switching Kernels and blacklisting are totally unknown to me. I get the impression that I may just need to somehow turn on my USB modem. I’ve also got Linux Mint installed on my Compaq laptop. Last night I found some installation instructions on the Linux Mint forum in Italian. I used these instructions and there were no error messages. After this, I still had no WiFi connection, but found some mentions of wlan2. I’m fairly desperate, so I may have to do an old Apple trick of dropping my Compaq laptop from a low height to try and reseat the WiFi card, or even try to install Windows without erasing my Linux Mint partition.


#11

to blacklist create a file in /etc/modprobe.d

sudo nano /etc/modprobe.d/wlan.conf

Then write

blacklist rtl8xxxu
install rtl8xxxu /bin/false

You can save and close nano with Ctrl+x
Then reboot.


#12

First of all I created the blacklist file and rebooted, but that didn’t work. I then updated the Kernel and rebooted, but that didn’t work either. I then edited the blacklist file by placing # symbols in front of each line, which I hope means in this system that the lines have been commented out. I then rebooted. None of this worked!

What else can I do?

As for getting another USB WiFi adaptor, I’m worried that this will delay my trip. I couldn’t book any tickets until the item had arrived. I did have a USB WiFi adaptor from ThePiHut, which just plugged in and worked, but it no longer lights up and seems to have blown out. I wonder if there’s any other USB WiFi adaptor which just works as soon as you plug it in?


#13

What says the log?

That isn’t the best description of the problem. Because with this I can’t help you.

Look in the journal and find the problem. Also try to get a scan working on the command line to see if there is a problem with NM. Since you use KDE I can’t help you with the NM GUI.

There are certainly ones that do that, but I can’t recommend anything since I don’t use such a dongle.


#14

OK, here’s a log starting without the dongle plugged in, then after plugging it in, followed by turning the WiFi on with the Network Manager, then finding no WiFi networks listed, as usual.

[paulb@paul-pc ~]$ journalctl -u NetworkManager -f
-- Logs begin at Wed 2017-07-12 01:04:38 BST. --
Oct 06 17:29:37 paul-pc NetworkManager[429]: <info>  [1507307377.4143] dhcp6 (eno1): activation: beginning transaction (timeout in 45 seconds)
Oct 06 17:29:37 paul-pc NetworkManager[429]: <warn>  [1507307377.4156] dhcp6 (eno1): hostname is not a FQDN, it will be ignored
Oct 06 17:29:37 paul-pc NetworkManager[429]: <info>  [1507307377.5218] dhcp6 (eno1): dhclient started with pid 660
Oct 06 17:29:38 paul-pc dhclient[660]: XMT: Info-Request on eno1, interval 930ms.
Oct 06 17:29:38 paul-pc dhclient[660]: RCV: Reply message on eno1 from fe80::1.
Oct 06 17:29:38 paul-pc NetworkManager[429]: <info>  [1507307378.4929] dhcp6 (eno1):   nameserver 'fe80::1'
Oct 06 17:29:38 paul-pc NetworkManager[429]: <info>  [1507307378.4930] dhcp6 (eno1): state changed unknown -> bound
Oct 06 17:29:38 paul-pc NetworkManager[429]: <info>  [1507307378.4951] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Oct 06 17:29:38 paul-pc NetworkManager[429]: <info>  [1507307378.6744] dhcp6 (eno1): client pid 660 exited with status 0
Oct 06 17:29:38 paul-pc NetworkManager[429]: <info>  [1507307378.6773] dhcp6 (eno1): state changed bound -> done
Oct 06 17:33:21 paul-pc NetworkManager[429]: <info>  [1507307601.7434] wifi-nl80211: (wlan0): using nl80211 for WiFi device control
Oct 06 17:33:21 paul-pc NetworkManager[429]: <info>  [1507307601.7436] device (wlan0): driver supports Access Point (AP) mode
Oct 06 17:33:21 paul-pc NetworkManager[429]: <info>  [1507307601.7464] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
Oct 06 17:33:21 paul-pc NetworkManager[429]: <info>  [1507307601.7702] rfkill2: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/ieee80211/phy1/rfkill2) (driver rtl8192eu)
Oct 06 17:33:21 paul-pc NetworkManager[429]: <info>  [1507307601.8090] device (wlan0): interface index 4 renamed iface from 'wlan0' to 'wlp0s18f2u1'
Oct 06 17:33:21 paul-pc NetworkManager[429]: <info>  [1507307601.8346] device (wlp0s18f2u1): state change: unmanaged -> unavailable (reason 'managed', internal state 'external')
Oct 06 17:33:21 paul-pc NetworkManager[429]: <info>  [1507307601.8432] device (wlp0s18f2u1): set-hw-addr: set MAC address to A2:B4:49:2A:1A:B1 (scanning)
Oct 06 17:33:48 paul-pc NetworkManager[429]: <info>  [1507307628.4472] audit: op="radio-control" arg="wireless-enabled:1" pid=844 uid=1000 result="success"

#15

This shows no real errors.

try https://wiki.archlinux.org/index.php/Wireless_network_configuration#Manual_setup

iw dev 
sudo ip link show wlp0s18f2u1
sudo iw dev wlp0s18f2u1 scan | less

Also watch the complete journal.


#16

You’re saying that a hard power off disabled your wifi card?

Did you reinstall Manjaro after interrupting its installation process, or what are you running now?

Does this have a firmware lock on hardware (whitelist) like various HP and other machines do, which prevent you from using non-approved hardware?

OK, so why do your logs say you’re running such an old kernel?

Depending on what you’ve done to your system, which files you’ve installed where, and if it even installed correctly in the first place, a wipe/reinstall might be in order.

If devices are “blowing up” after being connected to the laptop, you might also think about getting a new laptop. :wink:


#17

I don’t know how to quote messages on this forum!

I stopped Manjaro from installing because I had a feeling that it may delete my Linux Mint partition and containing lots of data, so I pressed the power switch to turn it off just after I told it to install. After this, I pressed the power switch again, still with the Manjaro Linux 17 Live DVD in the drive, it booted from there, but there was suddenly no WiFi connection. I thought I could fix this after installation, so I connected via cable for the installation. After that, I explored Manjaro a bit, but I still couldn’t turn the WiFi on. Next, I installed Manjaro on my Toshiba Satellite L750 laptop and stopped using the Compaq laptop altogether. I didn’t update it using a cable and Octopi. The updates I remembered doing were in Manjaro on my Toshiba laptop.

I had a USB WiFi modem from ThePiHut plugged into my Compaq laptop for at least a few months, to avoid losing it. It was working for months when I used that laptop, although I mainly used my Toshiba laptop. I don’t know about any whitelist of hardware by Compaq.

I bought the Compaq laptop in an emergency because I had nothing else and couldn’t afford anything better at the time. I would much rather lose the Compaq laptop than the Toshiba.

Now can you tell me how to get my TP-Link USB modem working under Manjaro?


#18

Reinstall (so you’re working from a known base) and switch to kernel 4.13 as @xabbu suggested.


#19

Well, today (07-10-17) I managed to go to a Restart Party, which is a repairs workshop, as described on https://therestartproject.org/

I took my Compaq Presario CQ57 laptop, along with my new TP-Link TL-WN832N USB modem.

The repair job was given to someone called Christian from Norway. I told him what had happened to my laptop and that I couldn’t get my new USB modem working. He looked at my Manjaro Linux installation, but then later on chose to boot into my Linux Mint installation.

He unscrewed a panel on the back of the laptop which had a WiFi symbol on it. I hadn’t noticed this, so didn’t know how easy it was to gain access to the WiFi card. He examined and reseated the WiFi card, but this had no effect.

He was typing for what seemed like less than 10 minutes in a terminal, but with the lists of details that came up it turned into a 45 page document after I saved it! Eventually he managed to get the TP-Link USB modem working.

He typed this session under Linux Mint, but I think that all or nearly all of it should e the same under Manjaro Linux. Here’s the last few commands he typed. See if you can explain what he did or find anything which would be different under Manjaro.

Blockquote
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo ifconfig wlan0 up
[sudo] password for paulb:
SIOCSIFFLAGS: Operation not possible due to RF-kill
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo rfkill wlan0
Usage: rfkill [options] command
Options:
–version show version (0.5-1ubuntu1 (Ubuntu))
Commands:
help
event
list [IDENTIFIER]
block IDENTIFIER
unblock IDENTIFIER
where IDENTIFIER is the index no. of an rfkill switch or one of:
all wifi wlan bluetooth uwb ultrawideband wimax wwan gps fm nfc
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo rfkill list all
0: phy0: Wireless LAN Soft blocked: no
Hard blocked: yes
1: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
2: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo service network-manager restart
network-manager stop/waiting
network-manager start/running, process 3150
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo rfkill unblock all
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo rfkill unblock all
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo service network-manager restart
network-manager stop/waiting
network-manager start/running, process 3435
paulb@paulb-Presario-CQ57-Notebook-PC:~ > sudo service network-manager restart


#20

looks like they just made sure the hardware switch was turned to on/allow and unblocked all with
sudo rfkill unblock all
then restart NetworkManager with
systemctl restart NetworkManager

How rfkill wasnt mentioned earlier, I dont know. Anyways, you can check if it is blocked with

rfkill list all