The dkms-rtl8192eu package has been updated to the latest snapshot as of
October 4th, with full support for the 5.9 series Linux kernels, bug fixes, and
other enhancements. See the upstream commit log for details.
Updated packages in core/updates_testing:
MGA7-64 Plasma on Lenovo B50
No installation issues
Running kernel 5.7.19 at first glance does not affect my wifi connection (Intel 3160)
I have (temporarily) a D-Link N300 Nano USB adapter available. I have been succesfull in making that one work in MGA7 some time before with some fiddling.
Now plugging the device in causes big problems, but can someone confirm me that this should work with the current kernel, or only with the 5.9 ????
Should still work with the current kernel, that's what QA should be testing.
Here we go:
After installation I plug in the device and check in MCC-Hardware: still using the old rtl8xxx driver which does not work for this device. That's OK as I suppose the driver is still to be build.
So, leaving the device plugged in, I reboot. After some messages (I don't use the quiet and splash options in the boot) the screen geos black and nothing happens anymore. Pulling out the device, gives to lines mentioning the remove of the USB device, nothing further. Plugging in again, similar.
CTRL-ALT-delete forces boot (device still plugged in) , that one goes on, builds the rtl8192eu driver with success, but a few seconds later, same problem: black screen, no further progress.
Removing the device allows a good boot.
Right now trying what happens with MGA8, will report on this in bug 22599
Booting with a USB device plugged in can cause a number of problems, so I would wait until the system is booted to plug it in.
Right, that's a known issue. But the driver needs to build once to start. Would the first boot build it if the device is not plugged in???
Yes, dkms builds at boot, it doesn't care if the device is present.
As a side remark: my previous old Dell 32-bit test laptop had no onboard wifi, so a USB wifi adapter was plugged in all the time, that never ever caused any problem booting. Booting with an USB flash or rust drive causes problems most of the time, that is true.
I have to correct myself: booting with the device plugged in eventually comes to an end.
After doing tests with M8 on this laptop, rebooted M7 with the device inserted and went on to play a card game on my desktop PC. The boot runs with success after xxx minutes. I didn't do anything on the laptop, just rebooted, and now there are still delays in the process, but not that bad anymore.
But in MCC-Hardware there is still the rtl8xxx driver shown, and from the CLI I get:
# journalctl -b | grep rtl8192
Oct 19 15:47:36 mach5.hviaene.thuis kernel: usb 2-2: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):
Oct 19 15:47:36 mach5.hviaene.thuis kernel: usb 2-2: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
Oct 19 15:47:43 mach5.hviaene.thuis dkms-autorebuild.sh: rtl8192eu (18.104.22.168_11320.20140505-4.mga7): Installing module.
Oct 19 15:47:43 mach5.hviaene.thuis dkms-autorebuild.sh: dkms build -m rtl8192eu -v 22.214.171.124_11320.20140505-4.mga7 -k 5.7.19-desktop-1.mga7 -a x86_64 -q --no-clean-kernel
And "connection failed"
I wonder if you have to put something in one of the modprobe configuration files to get it to use this module.
Be aware that all rtl8192xx devices are not created equal. The two-letter suffix makes a difference. I have an rtl8192cu usb device, and it does not use this driver. Instead, it requires firmware contained in (IIRC) kernal-firmware-nonfree, and I suppose uses an open-source driver.
All I have to do is plug it in and it "just works." I don't know what might happen if I had dkms-rtl8192eu installed with my device - possibly a conflict.
BTW, I just tried booting my desktop (wired connection) with the 8192cu device inserted, and it failed to boot. It doesn't fail on other machines if there's no wired connection, however.
I remember that when I had to download the driver, I had to blacklist the rtl8xxx driver. I cann't remember about other modprobe manipulations. It was not on my own laptop, and I made a note on that machine, but I cann't get to that one shortly.