You are not logged in.
Although, ifconfig shows the usb adapter with that exact name so I don't understand why that command results in "No such device".
This can be a strange quirk of the module.
For reference, the link leads to another alternative module and your card may be covered. https://github.com/pvaret/rtl8192cu-fixes
To turn powersafe off, try the picked answer of this post for networkmanager instead: https://unix.stackexchange.com/question … ermanently
(NB a pity iwconfig is no longer shipped..)
Offline
Try:
# modprobe -r rtl8192cu
Then:
# modprobe rtl8192cu swenc=1
That's a pretty lousy adapter, you might want consider buying another.
Offline
I'll try these lasts suggestions as soon as possible.
So if I got this right, the problem here is with the driver of the usb adapter...
Would this be solved by using simply a different adapter?
Offline
There is a good chance replacing it with a better quality adapter may solve your issue, but you need to be careful to buy an adapter with good Linux compatibility.
Offline
On #26 and #27 - his is NOT a RTL8188CUS chip
I've such, edimax used them earlier, they're covered by and use the rtl8192cu driver and workforme™
R8188EU is a different chip and covered by a different module and I don't think the rtl8192cu module will operate it at all (you can try to unload r8188eu and load rtl8192cu but don't hold your breath)
The r8188eu module has a whole host of parameters, ("modinfo r8188eu") but I can't say whether any of them would help here.
But a different adapter w/ a different chipset (I usually tend to look for atheros or intel but as mentioned, the rtl8192cu workforme™) will likely not cause you those troubles - it can however be hard to figure which chip is actually behind the brand, you'll have to google and pay close attention to the exact model and version
Offline
I already own another adapter I could try. It's a Alfa awus036nha network adapter.
Would it be more compatible?
Also...
For reference, the link leads to another alternative module and your card may be covered. https://github.com/pvaret/rtl8192cu-fixes
I'm sorry for the dumb question, but how do I install this driver being the instructions for Ubuntu?
Last edited by ordinary.schreiber (2022-01-16 20:01:14)
Offline
Would it be more compatible?
Plug it an post the output of "lsusb", the brand itself tells little to nothing about the actual chipset.
The rtl8192cu module is part of the kernel and so is the rtl8xxxu module which is referenced in that fork and far more likely be able to drive your chip.
You'd be https://wiki.archlinux.org/title/Kernel … acklisting r8188eu and probably have to explicitly "modprobe rtl8xxxu" and see whether that gets you a (usable) NIC.
Offline
Here is the output after plugging the ALFA awus036nha network adapter:
$ lsusb
Bus 002 Device 006: ID 4e53:5407 USB OPTICAL MOUSE
Bus 002 Device 005: ID 1a2c:4c5e China Resource Semico Co., Ltd USB Keyboard
Bus 002 Device 007: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
Bus 002 Device 003: ID 1bcf:2cb4 Sunplus Innovation Technology Inc. EKACOM-K30
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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
One thing I noticed, was an immediate increase in the connection speed and fluency after plugging the other adapter.
Although, I would still like to figure out how to fix the Edimax adapter...
Last edited by ordinary.schreiber (2022-01-16 21:23:12)
Offline
The ath9k* drivers are usually a *very* reliable.
Although, I would still like to figure out how to fix the Edimax adapter...
One thing I just noticed looking at the journal again:
pacman -Qs firmware
Offline
The ath9k* drivers are usually a *very* reliable.
Ok, sounds like good news.
Here is that output I left behind:
# pacman -Qs firmware
local/linux-firmware 20211216.f682ecb-1
Firmware files for Linux
Last edited by ordinary.schreiber (2022-01-16 22:01:06)
Offline
So the firmware is there.
As mentioned, you can try the rtl8xxxu module but don't hold your breath…
Offline
How do I do that?
Again, I'm sorry if I ask obvious questions. I'm just doing my best and trying to follow you guys.
Offline
You find brief instructions in Seth's post #32 and it is as easily reversible as done. Before you blacklist anything, you have to prepare the module to replace the regular one with. Probably you can try https://aur.archlinux.org/packages/8188eu-dkms-git/
If it compiles cleanly to a package to install, you can blacklist the r8188eu and install the alternative, reboot and see if a usable network device appears.
Offline
Ok, I'll give it a try. Thank you all
Offline
You're welcome. I just see the last AUR package I linked does the blacklisting during install automatically.
Offline
So just to make sure... I would be doing someting like this?
/etc/modprobe.d/blacklist.conf
# Blacklisting the r8188eu module
blacklist r8188eu
or
/etc/modprobe.d/blacklist.conf
# Blacklisting the r8188eu module
install r8188eu /bin/true
And reinstall this alternative
Or should I just go with something like:
/etc/modprobe.d/blacklist.conf
# Blacklisting the r8188eu module
blacklist r8188eu
or
/etc/modprobe.d/blacklist.conf
# Blacklisting the r8188eu module
install r8188eu /bin/true
# modprobe -r rtl8xxxu
# modprobe rtl8xxxu swenc=1
Offline
The regular blacklist will do and as Strike0 pointed out, the 8188eu-dkms-git package does that anyway for you.
Whether the 8188eu-dkms-git module or the rtl8xxxu module operate your chip (any better) is something you'll have to test and see.
You can easily undo (unblacklist the driver resp. remove the 8188eu-dkms-git package) this and the atheros adapter won't be affected by this at all.
Offline
I tried blacklisting the r8188eu and loading both r8188eu-dkms-git and rtl8xxxu, but now the adapter won't even be recognized.
/etc/modprobe.d/blacklist.conf
# Blacklisting the r8188eu module
blacklist r8188eu
Installed the 8188eu-dkms-git module
Then tried also
# modprobe -r rtl8xxxu
# modprobe rtl8xxxu swenc=1
Now I removed the /etc/modprobe.d/blacklist.conf to revert it but the adapter will not be recognized yet.
Last edited by ordinary.schreiber (2022-01-17 13:31:10)
Offline
Because, as pointed out everal times, https://aur.archlinux.org/packages/8188eu-dkms-git/ adds /etc/modprobe.d/blacklist-r8188eu.conf so you've blacklisted the module twice.
Offline
Right, I missed that part.
Now I reverted the operation and I am back where I started.
The only solution that seems to be working is to replace the adapter with a different one.
Offline
For anyone else looking for a solution to this problem, this should help:
options r8188eu rtw_power_mgnt=0
Put that line into /etc/modprobe.d/r8188eu.conf and reload the r8188eu module.
It makes the built-in driver more usable, but the driver in the AUR package 8188eu-dkms-git still has better speed.
Offline