Bug 1183829

Summary: RTL8821CE 802.11ac PCIe Wireless Network Adapter - Not handled properly by the rtw_8821ce dirver on Kernel 5.11.6-1
Product: [openSUSE] openSUSE Tumbleweed Reporter: Michal T <mt>
Component: KernelAssignee: openSUSE Kernel Bugs <kernel-bugs>
Status: NEW --- QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: Larry.Finger, mbenes, Sauerlandlinux, tiwai
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Michal T 2021-03-20 13:51:40 UTC
No wifi icon in Plasma.
The black place where it is supposed to be can be clicked but shows no wifi networks.
This is a recurrent problem since several months now. On some kernels it works on some it doesn't. More tests are critically needed here. This is a super standard chipset on several Lenovo laptops.

journalctl -b | grep 8821
mars 19 22:49:13 localhost kernel: rtw_8821ce 0000:07:00.0: Firmware version 24.8.0, H2C version 12
mars 19 22:49:13 localhost NetworkManager[639]: <info>  [1616190553.7766] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.4/0000:07:00.0/ieee80211/phy0/rfkill2) (driver rtw_8821ce)
mars 19 22:49:13 localhost kernel: rtw_8821ce 0000:07:00.0 wlp7s0: renamed from wlan0
mars 19 22:49:14 localhost kernel: rtw_8821ce 0000:07:00.0: start vif 28:39:26:ab:b4:5d on port 0
mars 19 22:49:14 localhost kernel: rtw_8821ce 0000:07:00.0: stop vif 28:39:26:ab:b4:5d on port 0
mars 19 22:49:14 localhost kernel: rtw_8821ce 0000:07:00.0: start vif 7a:36:c4:26:1d:f1 on port 0
mars 19 22:56:07 linux.local kernel: rtw_8821ce 0000:07:00.0: stop vif 7a:36:c4:26:1d:f1 on port 0
mars 19 22:56:07 linux.local kernel: rtw_8821ce 0000:07:00.0: start vif c2:a0:c3:48:17:58 on port 0
mars 19 23:03:00 linux.local kernel: rtw_8821ce 0000:07:00.0: stop vif c2:a0:c3:48:17:58 on port 0
mars 19 23:03:00 linux.local kernel: rtw_8821ce 0000:07:00.0: start vif ae:92:06:47:50:83 on port 0
mars 19 23:09:52 linux.local kernel: rtw_8821ce 0000:07:00.0: stop vif ae:92:06:47:50:83 on port 0
...
And continues like this indefinitely

uname -a
Linux linux.local 5.11.6-1-default #1 SMP Thu Mar 11 16:11:36 UTC 2021 (7358b30) x86_64 x86_64 x86_64 GNU/Linux

rfkill list 
0: ideapad_wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: ideapad_bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
Comment 1 Stephan Hemeier 2021-03-20 16:39:41 UTC
maybe the driver is not patched:
https://bugzilla.opensuse.org/show_bug.cgi?id=1178105

I build rpms here:
https://build.opensuse.org/package/show/home:Sauerland:hardware/rtl8821ce
Comment 2 Michal T 2021-03-21 11:49:06 UTC
I tried with rtl8821ce-kmp-default and without. No change. I think that as usually the rtl8821ce driver is not taking over the kernel's driver. rtw_8821ce remains active even when the rtl8821ce-kmp-default is installed.
Comment 3 Stephan Hemeier 2021-03-21 13:29:37 UTC
For kernel 5.10 or 5.11 (I do not know when) you need also the blacklist rpm to blacklist the rtw_8821ce.

This is a temporary snapshot in the Repo:
https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Tumbleweed/x86_64/rtl8821ce-blacklist-rtw_8821ce-git20210206-4.4.x86_64.rpm
https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Tumbleweed/x86_64/rtl8821ce-kmp-default-git20210206_k5.11.6_1-4.4.x86_64.rpm

Better is to use the Repo to get the updates in time.
Comment 4 Larry Finger 2021-03-21 23:30:06 UTC
(In reply to Stephan Hemeier from comment #1)
> maybe the driver is not patched:
> https://bugzilla.opensuse.org/show_bug.cgi?id=1178105
> 
> I build rpms here:
> https://build.opensuse.org/package/show/home:Sauerland:hardware/rtl8821ce

That patch is needed for only a few devices, not all of them. If that was your problem, you would get a dmesg logging and the device would not work at all.

You logs show that the driver in use is named rtw_8821ce. That one likely comes from my repo at https://Github.com/lwfinger/rtw88.git. I carefully named it that way to distinguish from the kernel version named rtw88_rtl8821ce. With a 5.11 kernel, you run the risk of the drivers being mixed. Note that my repo is updated to match the latest code coming from Realtek. The code in kernel 5.11.6 may not contain all the fixes. 

Please post the output of 'lsmod | grep rtw'

I do not own an RTW8821CE, thus I can only test for building.
Comment 5 Michal T 2021-03-23 11:28:23 UTC
(In reply to Larry Finger from comment #4)
> (In reply to Stephan Hemeier from comment #1)
> > maybe the driver is not patched:
> > https://bugzilla.opensuse.org/show_bug.cgi?id=1178105
> > 
> > I build rpms here:
> > https://build.opensuse.org/package/show/home:Sauerland:hardware/rtl8821ce
> 
> That patch is needed for only a few devices, not all of them. If that was
> your problem, you would get a dmesg logging and the device would not work at
> all.
> 
> You logs show that the driver in use is named rtw_8821ce. That one likely
> comes from my repo at https://Github.com/lwfinger/rtw88.git. I carefully
> named it that way to distinguish from the kernel version named
> rtw88_rtl8821ce. With a 5.11 kernel, you run the risk of the drivers being
> mixed. Note that my repo is updated to match the latest code coming from
> Realtek. The code in kernel 5.11.6 may not contain all the fixes. 
> 
> Please post the output of 'lsmod | grep rtw'
> 
> I do not own an RTW8821CE, thus I can only test for building.

I'm using the driver from your repo since a long time as it was the only way for me to have WiFi. I tough that with the blacklist patch it should be taking over but it seems it is not.

Here is the lsmod result:

lsmod | grep rtw
rtw88_8821ce           16384  0
rtw88_8821c            77824  1 rtw88_8821ce
rtw88_pci              28672  1 rtw88_8821ce
rtw88_core            163840  2 rtw88_pci,rtw88_8821c
mac80211             1097728  2 rtw88_pci,rtw88_core
cfg80211              970752  4 wl,rtw88_core,mac80211,8821ce
Comment 6 Michal T 2021-03-23 11:35:30 UTC
(In reply to Michal T from comment #5)
> (In reply to Larry Finger from comment #4)
> > (In reply to Stephan Hemeier from comment #1)
> > > maybe the driver is not patched:
> > > https://bugzilla.opensuse.org/show_bug.cgi?id=1178105
> > > 
> > > I build rpms here:
> > > https://build.opensuse.org/package/show/home:Sauerland:hardware/rtl8821ce
> > 
> > That patch is needed for only a few devices, not all of them. If that was
> > your problem, you would get a dmesg logging and the device would not work at
> > all.
> > 
> > You logs show that the driver in use is named rtw_8821ce. That one likely
> > comes from my repo at https://Github.com/lwfinger/rtw88.git. I carefully
> > named it that way to distinguish from the kernel version named
> > rtw88_rtl8821ce. With a 5.11 kernel, you run the risk of the drivers being
> > mixed. Note that my repo is updated to match the latest code coming from
> > Realtek. The code in kernel 5.11.6 may not contain all the fixes. 
> > 
> > Please post the output of 'lsmod | grep rtw'
> > 
> > I do not own an RTW8821CE, thus I can only test for building.
> 
> I'm using the driver from your repo since a long time as it was the only way
> for me to have WiFi. I tough that with the blacklist patch it should be
> taking over but it seems it is not.
> 
> Here is the lsmod result:
> 
> lsmod | grep rtw
> rtw88_8821ce           16384  0
> rtw88_8821c            77824  1 rtw88_8821ce
> rtw88_pci              28672  1 rtw88_8821ce
> rtw88_core            163840  2 rtw88_pci,rtw88_8821c
> mac80211             1097728  2 rtw88_pci,rtw88_core
> cfg80211              970752  4 wl,rtw88_core,mac80211,8821ce

Here is the info about the installed packages:

zypper info rtl8821ce-kmp-default

Loading repository data...
Reading installed packages...


Information for package rtl8821ce-kmp-default:
----------------------------------------------
Repository     : sauerland_wifi
Name           : rtl8821ce-kmp-default
Version        : git20210206_k5.11.6_1-7.2
Arch           : x86_64
Vendor         : obs://build.opensuse.org/home:Sauerland
Installed Size : 3,5 MiB
Installed      : Yes
Status         : out-of-date (version git20210206_k5.11.6_1-7.1 installed)
Source package : rtl8821ce-git20210206-7.2.src
Summary        : Wlan-Driver for Realtek RTL8821CE 802.11ac WLAN Adapter
Description    : 
    This is the Wlan-Driver for the Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter
    ported from the Endless OS variant of the linux kernel.
    Its named 8821ce.

    Bugs: see https://github.com/tomaspinho/rtl8821ce/blob/master/README.md


    Driver is in kernel 5.9 but does not work, so you need also the blacklist rpm.


zypper info rtl8821ce-blacklist-rtw_8821ce

Loading repository data...
Reading installed packages...


Information for package rtl8821ce-blacklist-rtw_8821ce:
-------------------------------------------------------
Repository     : sauerland_wifi
Name           : rtl8821ce-blacklist-rtw_8821ce
Version        : git20210206-7.2
Arch           : x86_64
Vendor         : obs://build.opensuse.org/home:Sauerland
Installed Size : 23 B
Installed      : Yes
Status         : up-to-date
Source package : rtl8821ce-git20210206-7.2.src
Summary        : To favour rtl8192ce blacklist the rtw_8821ce device driver
Description    : 
    The rtl8821ce is supported with kernel 5.9 by rtw88_8821ce, but this module does not work. To solve this the rtw_8821ce kernel module has to be
    blacklisted to enable the system to load the new device driver 8821ce.

    This rpm blacklists the rtw88_8821ce
Comment 7 Michal T 2021-03-23 11:45:27 UTC
Same problem after updating to the git20210206_k5.11.6_1-7.2 version
Comment 8 Michal T 2021-03-23 11:51:19 UTC
(In reply to Michal T from comment #7)
> Same problem after updating to the git20210206_k5.11.6_1-7.2 version

With the blacklist rpm installed "lsmod | grep rtw" is empty

lsmod | grep 8821
8821ce               1966080  0
cfg80211              970752  2 wl,8821ce
Comment 9 Stephan Hemeier 2021-03-23 12:02:55 UTC
Please post:
lsmod | grep -Ei 'rtw|rtl'

Do not mix my build with the original rtw driver.
Comment 10 Michal T 2021-03-23 12:51:47 UTC
(In reply to Stephan Hemeier from comment #9)
> Please post:
> lsmod | grep -Ei 'rtw|rtl'
> 
> Do not mix my build with the original rtw driver.

"lsmod | grep -Ei 'rtw|rtl'" returns empty result (balcklist part of driver installed)
Comment 11 Stephan Hemeier 2021-03-23 13:04:10 UTC
My fault, it should be:
lsmod | grep -Ei 'rtw|rtl|8821ce'

My rtl8821ce is running with kernel:stable on a Leap 15.2 Laptop:

uname -a && zypper se -si rtl8821ce
Linux hp-laptop 5.11.8-1.g995fe45-default #1 SMP Sat Mar 20 18:00:06 UTC 2021 (995fe45) x86_64 x86_64 x86_64 GNU/Linux
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                           | Type  | Version                                | Arch   | Repository
---+--------------------------------+-------+----------------------------------------+--------+------------------------
i+ | rtl8821ce-blacklist-rtw_8821ce | Paket | git20210206-lp152.6.1                  | x86_64 | Sauerland-15.2
i+ | rtl8821ce-kmp-default          | Paket | git20210206_k5.11.8_1.g995fe45-6.2     | x86_64 | Sauerland-Kernel-Stable
i+ | rtl8821ce-kmp-default          | Paket | git20210206_k5.3.18_lp152.66-lp152.6.1 | x86_64 | Sauerland-15.2-Update

lsmod | grep -Ei 'rtw|rtl|8821ce'
btrtl                  28672  1 btusb
bluetooth             700416  28 btrtl,btintel,btbcm,bnep,btusb
8821ce               1966080  0
cfg80211              970752  1 8821ce
Comment 12 Michal T 2021-03-23 13:09:20 UTC
(In reply to Stephan Hemeier from comment #11)
> My fault, it should be:
> lsmod | grep -Ei 'rtw|rtl|8821ce'
> 
> My rtl8821ce is running with kernel:stable on a Leap 15.2 Laptop:
> 
> uname -a && zypper se -si rtl8821ce
> Linux hp-laptop 5.11.8-1.g995fe45-default #1 SMP Sat Mar 20 18:00:06 UTC
> 2021 (995fe45) x86_64 x86_64 x86_64 GNU/Linux
> Repository-Daten werden geladen...
> Installierte Pakete werden gelesen...
> 
> S  | Name                           | Type  | Version                       
> | Arch   | Repository
> ---+--------------------------------+-------+--------------------------------
> --------+--------+------------------------
> i+ | rtl8821ce-blacklist-rtw_8821ce | Paket | git20210206-lp152.6.1         
> | x86_64 | Sauerland-15.2
> i+ | rtl8821ce-kmp-default          | Paket |
> git20210206_k5.11.8_1.g995fe45-6.2     | x86_64 | Sauerland-Kernel-Stable
> i+ | rtl8821ce-kmp-default          | Paket |
> git20210206_k5.3.18_lp152.66-lp152.6.1 | x86_64 | Sauerland-15.2-Update
> 
> lsmod | grep -Ei 'rtw|rtl|8821ce'
> btrtl                  28672  1 btusb
> bluetooth             700416  28 btrtl,btintel,btbcm,bnep,btusb
> 8821ce               1966080  0
> cfg80211              970752  1 8821ce

lsmod | grep -Ei 'rtw|rtl|8821ce'
8821ce               1966080  0
cfg80211              970752  2 wl,8821ce

uname -a && zypper se -si rtl8821ce
Linux linux.local 5.11.6-1-default #1 SMP Thu Mar 11 16:11:36 UTC 2021 (7358b30) x86_64 x86_64 x86_64 GNU/Linux
Loading repository data...
Reading installed packages...

S  | Name                           | Type    | Version                   | Arch   | Repository
---+--------------------------------+---------+---------------------------+--------+---------------
i+ | rtl8821ce-blacklist-rtw_8821ce | package | git20210206-7.2           | x86_64 | sauerland_wifi
i+ | rtl8821ce-kmp-default          | package | git20210206_k5.11.6_1-7.2 | x86_64 | sauerland_wifi
Comment 13 Larry Finger 2021-03-23 14:45:57 UTC
I have no idea where the code in the sauerland_wifi repo comes from.

My GitHub repo, which produces the rtw_* drivers is a copy of the latest kernel effort from Realtek. In my thinking, that has the best possibility of working on kernels older than 5.12. In any case, I have nothing more to contribute to this bug entry!
Comment 14 Michal T 2021-03-23 18:33:07 UTC
(In reply to Larry Finger from comment #13)
> I have no idea where the code in the sauerland_wifi repo comes from.
> 
> My GitHub repo, which produces the rtw_* drivers is a copy of the latest
> kernel effort from Realtek. In my thinking, that has the best possibility of
> working on kernels older than 5.12. In any case, I have nothing more to
> contribute to this bug entry!

Can I have the official address of your repo for zypper?
I don't think I have it configured in zypper but I still have the rtw_8821ce and not rtw_rtl8821ce drivers. Does it require a specific package to be installed?
Strange situation but probably not of major importance as the rtw_* drivers from Realtek never worked on my system despite me posting a bug report on the Kernel Wireless mailing list several months ago.
Comment 15 Stephan Hemeier 2021-03-23 19:04:50 UTC
I have switched from the rtl8821ce to rtw88 because the rtl8821ce disconnects and does not reconnect any more.

I have seen an error in the log.

So I switched to rtw88 from Larry Finger and it is working.

Delete all rtl8821ce also the blacklist and install rtw88.
rtw88 is in the Repo.
Comment 16 Larry Finger 2021-03-23 20:40:18 UTC
(In reply to Michal T from comment #14)
 
> Can I have the official address of your repo for zypper?
> I don't think I have it configured in zypper but I still have the rtw_8821ce
> and not rtw_rtl8821ce drivers. Does it require a specific package to be
> installed?
> Strange situation but probably not of major importance as the rtw_* drivers
> from Realtek never worked on my system despite me posting a bug report on
> the Kernel Wireless mailing list several months ago.

My repo at https://GitHub.com/lwfinger/rtw88.git is not an rpm repo. It is source code for the drivers that the user needs to build for themselves.

The drivers are being improved gradually, and those changes are ported to the GitHub repo, thus it corresponds to what will be in kernel 5.12.

Unfortunately, I cannot force the Realtek developers to respond to anything posted on the Linux Wireless ML.
Comment 17 Michal T 2021-03-24 17:08:59 UTC
(In reply to Larry Finger from comment #13)
> I have no idea where the code in the sauerland_wifi repo comes from.
> 
> My GitHub repo, which produces the rtw_* drivers is a copy of the latest
> kernel effort from Realtek. In my thinking, that has the best possibility of
> working on kernels older than 5.12. In any case, I have nothing more to
> contribute to this bug entry!

Can I have the official address of your repo for zypper?
I don't think I have it configured in zypper but I still have the rtw_8821ce and not rtw_rtl8821ce drivers. Does it require a specific package to be installed?
Strange situation but probably not of major importance as the rtw_* drivers from Realtek never worked on my system despite me posting a bug report on the Kernel Wireless mailing list several months ago.(In reply to Stephan Hemeier from comment #15)
> I have switched from the rtl8821ce to rtw88 because the rtl8821ce
> disconnects and does not reconnect any more.
> 
> I have seen an error in the log.
> 
> So I switched to rtw88 from Larry Finger and it is working.
> 
> Delete all rtl8821ce also the blacklist and install rtw88.
> rtw88 is in the Repo.

I've done this and installed the rtw88 from the repo. I basically ended up in the initial situation with the following lsmod:

lsmod | grep rtw
rtw_8821ce             16384  0
rtw_8821c              90112  1 rtw_8821ce
rtw_pci                28672  1 rtw_8821ce
rtw_core              217088  2 rtw_8821c,rtw_pci
mac80211             1097728  2 rtw_core,rtw_pci
cfg80211              970752  3 wl,rtw_core,mac80211

And unfortunately no WiFi.

Any ideas on how to debug this further?
Comment 18 Michal T 2021-03-24 17:10:27 UTC
(In reply to Larry Finger from comment #16)
> (In reply to Michal T from comment #14)
>  
> > Can I have the official address of your repo for zypper?
> > I don't think I have it configured in zypper but I still have the rtw_8821ce
> > and not rtw_rtl8821ce drivers. Does it require a specific package to be
> > installed?
> > Strange situation but probably not of major importance as the rtw_* drivers
> > from Realtek never worked on my system despite me posting a bug report on
> > the Kernel Wireless mailing list several months ago.
> 
> My repo at https://GitHub.com/lwfinger/rtw88.git is not an rpm repo. It is
> source code for the drivers that the user needs to build for themselves.
> 
> The drivers are being improved gradually, and those changes are ported to
> the GitHub repo, thus it corresponds to what will be in kernel 5.12.
> 
> Unfortunately, I cannot force the Realtek developers to respond to anything
> posted on the Linux Wireless ML.

Any chance that if I build the driver from source from your github repo I'll have access to some log that could help me to diagnose this issue?
Comment 19 Stephan Hemeier 2021-03-24 18:52:35 UTC
Please post:
zypper se -si rtw rtl8821
and
rfkill list all
and
uname -a

Its working here on my Laptop:
LANG=C zypper se -si rtw rtl8821ce
Loading repository data...
Reading installed packages...

S  | Name                 | Type    | Version                                | Arch   | Repository
---+----------------------+---------+----------------------------------------+--------+------------------
i  | libKPimImportWizard5 | package | 20.04.2-lp152.1.1                      | x86_64 | Main Repository
i+ | rtw88-kmp-default    | package | git20210323_k5.11.8_1.g995fe45-2.1     | x86_64 | (System Packages)
i+ | rtw88-kmp-default    | package | git20210323_k5.3.18_lp152.19-lp152.2.1 | x86_64 | (System Packages)

uname -a
Linux hp-laptop 5.11.8-1.g995fe45-default #1 SMP Sat Mar 20 18:00:06 UTC 2021 (995fe45) x86_64 x86_64 x86_64 GNU/Linux
Comment 20 Larry Finger 2021-03-24 20:08:08 UTC
> 
> Any chance that if I build the driver from source from your github repo I'll
> have access to some log that could help me to diagnose this issue?

There is a possibility of enabling debug options, but I have no idea what to enable, or how to interpret the output. Unfortunately, you will need to post the question through the Linux wireless mailing list. That "start vif/stop vif" sequence should help then narrow the cause.
Comment 21 Larry Finger 2021-03-25 02:12:58 UTC
I installed my rtl8822ce to verify what you are seeing. I get the following:

rtw_8822ce 0000:02:00.0 wls1: renamed from wlan0
rtw_8822ce 0000:02:00.0: start vif 00:e0:4c:09:94:03 on port 0
rtw_8822ce 0000:02:00.0: stop vif 00:e0:4c:09:94:03 on port 0
rtw_8822ce 0000:02:00.0: start vif 4e:f1:00:b3:d8:0e on port 0
rtw_8822ce 0000:02:00.0: stop vif 4e:f1:00:b3:d8:0e on port 0
rtw_8822ce 0000:02:00.0: start vif 00:e0:4c:09:94:03 on port 0
wls1: authenticate with 84:1b:5e:f7:6b:03


I would like to see your signal strength. Run 'iw dev'. Using the string on the interface line as <iface>, run and post the output of
sudo iw dev <iface> scan | egrep "signal|SSID"
Comment 22 Michal T 2021-03-25 09:02:52 UTC
(In reply to Stephan Hemeier from comment #19)
> Please post:
> zypper se -si rtw rtl8821
> and
> rfkill list all
> and
> uname -a
> 
> Its working here on my Laptop:
> LANG=C zypper se -si rtw rtl8821ce
> Loading repository data...
> Reading installed packages...
> 
> S  | Name                 | Type    | Version                               
> | Arch   | Repository
> ---+----------------------+---------+----------------------------------------
> +--------+------------------
> i  | libKPimImportWizard5 | package | 20.04.2-lp152.1.1                     
> | x86_64 | Main Repository
> i+ | rtw88-kmp-default    | package | git20210323_k5.11.8_1.g995fe45-2.1    
> | x86_64 | (System Packages)
> i+ | rtw88-kmp-default    | package | git20210323_k5.3.18_lp152.19-lp152.2.1
> | x86_64 | (System Packages)
> 
> uname -a
> Linux hp-laptop 5.11.8-1.g995fe45-default #1 SMP Sat Mar 20 18:00:06 UTC
> 2021 (995fe45) x86_64 x86_64 x86_64 GNU/Linux

Here they are:

# zypper se -si rtw rtl8821

Loading repository data...
Reading installed packages...

S  | Name                 | Type    | Version                   | Arch   | Repository
---+----------------------+---------+---------------------------+--------+----------------------
i  | libKPimImportWizard5 | package | 20.12.3-1.1               | x86_64 | Main Repository (OSS)
i  | libKPimImportWizard5 | package | 20.12.3-1.1               | x86_64 | openSUSE-20200610-0
i+ | rtw88-kmp-default    | package | git20210323_k5.11.6_1-3.2 | x86_64 | sauerland_wifi


# rfkill list all
0: ideapad_wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: ideapad_bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

# uname -a
Linux linux.local 5.11.6-1-default #1 SMP Thu Mar 11 16:11:36 UTC 2021 (7358b30) x86_64 x86_64 x86_64 GNU/Linux
Comment 23 Michal T 2021-03-25 09:08:23 UTC
(In reply to Larry Finger from comment #21)
> I installed my rtl8822ce to verify what you are seeing. I get the following:
> 
> rtw_8822ce 0000:02:00.0 wls1: renamed from wlan0
> rtw_8822ce 0000:02:00.0: start vif 00:e0:4c:09:94:03 on port 0
> rtw_8822ce 0000:02:00.0: stop vif 00:e0:4c:09:94:03 on port 0
> rtw_8822ce 0000:02:00.0: start vif 4e:f1:00:b3:d8:0e on port 0
> rtw_8822ce 0000:02:00.0: stop vif 4e:f1:00:b3:d8:0e on port 0
> rtw_8822ce 0000:02:00.0: start vif 00:e0:4c:09:94:03 on port 0
> wls1: authenticate with 84:1b:5e:f7:6b:03
> 
> 
> I would like to see your signal strength. Run 'iw dev'. Using the string on
> the interface line as <iface>, run and post the output of
> sudo iw dev <iface> scan | egrep "signal|SSID"

The problem is that my wireless interface never even goes up:
3: wlp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 36:4d:af:72:60:bc brd ff:ff:ff:ff:ff:ff permaddr 28:39:26:ab:b4:5d

And then my
# iw dev wlp7s0 scan
returns nothing at all.
Comment 24 Michal T 2021-03-25 09:08:54 UTC
(In reply to Larry Finger from comment #20)
> > 
> > Any chance that if I build the driver from source from your github repo I'll
> > have access to some log that could help me to diagnose this issue?
> 
> There is a possibility of enabling debug options, but I have no idea what to
> enable, or how to interpret the output. Unfortunately, you will need to post
> the question through the Linux wireless mailing list. That "start vif/stop
> vif" sequence should help then narrow the cause.

Ok, I'll try my luck there again.
Comment 25 Stephan Hemeier 2021-03-25 12:51:14 UTC
My rtw88 is the one from Larry Fingers rtw88.

But I would say:
Delete my rtw88 rpm,  get connected with LAN to Internet and build it by your own.
As User in your /home:
git clone https://github.com/lwfinger/rtw88.git

And build the driver as posted in the README.
Comment 26 Stephan Hemeier 2021-03-25 18:00:53 UTC
secure boot is disabled in Bios/UEFI?
Comment 27 Michal T 2021-03-26 09:14:52 UTC
(In reply to Stephan Hemeier from comment #26)
> secure boot is disabled in Bios/UEFI?

No, I'm not using EFI:

#> efibootmgr
EFI variables are not supported on this system.
Comment 28 Miroslav BeneŇ° 2022-02-26 09:02:15 UTC
Michal, have you managed to install Larry's github driver in the end?

Also, since it has been a while, there is v5.16 kernel in TW now. Is there any improvement with just that?