Description of problem: - Combo card Realtek WIFI/BLUETOOTH needing firmware "8821ce" not working with mageia 7 and kernels generation 5x. - Sources present to GITHUB's : "https://github.com/tomaspinho/rtl8821ce" must be compiled in order to have the card working. - New RPM 8821ce present to ROSA's distribution only works for kernels 4x, and restrictively activates WIFI but not BLUETOOTH. Version-Release number of selected component (if applicable): - 5.0.5-desktop-2.mga7 - Command: "urpmf 8821" initially doesn't issue any result, but after compiling lists of course all the archives created when compiling. Thank you. How reproducible: Steps to Reproduce: 1. 2. 3.
CC: (none) => marja11Assignee: bugsquad => kernel
[jibz@jabztop ~]$ urpmf 8821ce | wc -l 0 [jibz@jabztop ~]$ urpmf 8821 | wc -l 219 [jibz@jabztop ~]$ urpmf 8821 [...] rtlwifi-firmware:/lib/firmware/rtl_bt/rtl8821a_fw.bin rtlwifi-firmware:/lib/firmware/rtl_bt/rtl8821c_config.bin rtlwifi-firmware:/lib/firmware/rtl_bt/rtl8821c_fw.bin rtlwifi-firmware:/lib/firmware/rtlwifi/rtl8821aefw.bin rtlwifi-firmware:/lib/firmware/rtlwifi/rtl8821aefw_29.bin rtlwifi-firmware:/lib/firmware/rtlwifi/rtl8821aefw_wowlan.bin [...] [jibz@jabztop ~]$ curl pkgsubmit.mageia.org/data/maintdb.txt 2>/dev/null | grep rtlwifi-firmware rtlwifi-firmware tmb
CC: (none) => j.biernacki
Seems sources have been recently modified at https://github.com/tomaspinho/rtl8821ce to allow installation with kernels above 5.1.x generation. Thanks
CC: (none) => egc
Will this be included in the final version? It's still not in 7RC ...
Added to latest kernel & to driver list in drakx's list_modules.pm
CC: (none) => thierry.vignaud
Thanks, Will be tested with "Release", or new kernel update on "RC", as already manually compiled on this last. Merci Thierry
Yep, works great here :-) Thanks!!
\o/
Status: NEW => RESOLVEDResolution: (none) => FIXED
Test with kernel-update 5.1.9-1 => In order to disallow auto recompil => stop dkms-autorebuild; uninstall dkms, dkms-minimal, kernel-devel. Update done; installation of 5.1.9-1; reboot; The WIFI perfectly works ! No more tainted kernel. MILIONS OF THANKS
With kernel 5.3.2 it does not work anymore. The driver seems to be installed, but when trying to connect to a wifi in network center, it says: "No network interface found for this device (using 8821ce)"
Confirmed here: Don't work anymore with kernel 5.3.2-1-1.1 To be noted: With previous versions of kernels, the connection lasted (+/-) 1 minute after the end of the boot to be effective. => Observing procesus (by mean of "Top") the start of the connection waited for "RTW_CMD_THREAD" just followed by "wpa_supplicant", to take effect => (Wether "network-manager" is installed or not, and "wpa_supplicant" launched at the start of the boot process, or not). No way to get the start of the connection immediately at the end of the boot. Thanks.
please provide output of lspcidrake -v
CC: (none) => tmb
Created attachment 11304 [details] lspci
Created attachment 11305 [details] dmesg
Ok, that's a driver/firmware crash ... Will look into it
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Can you try kernel-5.3.5-1.mga7 that is now in updates_testing
OK! Working now! Great job! ...Nevertheless the delay of about 1 minute for the connection to be up, has come back, just like with previous versions. Before the driver was introduced as module in the kernel, when this driver was compiled at hand, the connection was immediate (no delay)... Thanks anyway.
(In reply to Roger Checa from comment #17) > OK! Working now! Great job! > > ...Nevertheless the delay of about 1 minute for the connection to be up, has > come back, just like with previous versions. > Before the driver was introduced as module in the kernel, when this driver > was compiled at hand, the connection was immediate (no delay)... > Thanks anyway. Yeah, the realtek codedrops are quite low quality, and happends to work with older kernels, but gets in trouble with newer kernels... And realtek does not really care about providing new drivers for "old" hw... Thats why there is so many 3rdparty repos with warious quality exists... Can you attach dmesg when booting the 5.3.5-1 kernel so I can see if it gives any hint about the delay?
Created attachment 11307 [details] "dmesg" while waiting connection to be up
Created attachment 11308 [details] "dmesg" when connection is up
Ok, so the wifi driver is still having issues with the new kernels, wich causes the delays... I'll try to look into it
Can you try kernel-5.3.6-1.mga7 from testing ?
Created attachment 11311 [details] dmesg
No change - no result. (See dmesg above) My feeling is that the problem is not with the module itself, but with the network connection coping with the module. This connection never worked with "Network-Manager" at the difference of ROSA or OpenMandriva, which both have the compiled driver at hand version ...and as far as I remember, with Mageia Cauldon before the module was introduced. It is precisely "Network-Nanager" which launches the 8821ce during the boot of these distribs. ...And because also, what appears strange to me is the result of command "dracut -f" where "systemd" appears not loaded in the initrd (what I think could be a wrong message or momentaneous one) but which could explain the delay... => Join dracut -f below.
Created attachment 11312 [details] dracut -f
Enough tests, flushing out so I can build kmods for virtualbox security update
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugsWhiteboard: (none) => MGA7-64-OK, MGA7-32-OK
Oops, wrong report...
Whiteboard: MGA7-64-OK, MGA7-32-OK => (none)Keywords: advisory, validated_update => (none)
There is now a kernel-5.3.7-1.mga7 in testing with more fixes to rtl8821ce... Does it make any difference ?
Updated kernel + all new firmwares (just in case...) No change with 5.3.7-1 => same delay. Following, several tries: 1/ With "Modem manager" => no change => delay 2/ With "Network-Manager" => NO CONNECTION! => + ERRORS: A/ "a start job ... LSB => failed to bring up network" B/ "usb 1.4.1" address in DMESG (see below). ..but note => "8821ce renamed from wlan0" 3/ On same session (I mean, not rebooting) with errors, disabling/stopping Network-Manager + modifying as "NO" the config (disallowing NM to manage the connection) => the connection starts! => What happened with error about "usb 1.4.1" address, if the connection is OK? Always same scaring messages (see above "COMMENT 25") with command "dracut -f".
Created attachment 11325 [details] DMESG when booting with NetworkManager
rtl-8821ce support has been restored in 5.9.11-3.mga7 kernel in updates_testing Please test this.
Component: New RPM package request => RPM PackagesCC: (none) => ouaurelienSource RPM: dkms-rtl8192eu / rtlwifi-firmware => rtlwifi-firmware
*** Bug 27698 has been marked as a duplicate of this bug. ***
CC: (none) => omeritzicschwartz
Kernel 5.9.12-1 in testing updates YES ! The delay of (+/-) 1 minute -I had here- to get the connection working has now disappeared. As soon as reaching the desk the connection is up. (I am not using "Network_Manager" or "Modem-Manager" but Only "Network" in the services.) To be noted : 1/ - That the sole install of the kernel did not resolve the problem => the definitive solution was when I installed "rtlwifi-firmware" (20201022 - 1.mga7.nonfree noarch). 2/ - According the "dkms-rtl8821ce" was always installed, and the connection working well 1 minute after the end of the boot, this may confirm (IMHO) something wrong with the load of the firmware not necessarily the kernel itself. I mean, the dkms package could have been conflicting with another interface config/module. For instance, on my Mageia8-Cauldron for more than 1 month I had solved the problem -using precedents kernels- after "playing" with mga-applet (spare me the details I don't remember). 3/ - ROSA distrib has made a rpm for "8821ce" -and not a dkms package- and there has never been any problem with much older kernels. 4/ - Of course people not using "nonfree" firmware will not be totally satisfied but this is not my posture concerning the hardware. Thank you and bravo anyway for having solved the problem.
Depends on: (none) => 27672
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2020-0239.html
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED