Realtek RTL8822BE - wifi unable to connect

The other thing that comes to mind is regarding this:

It is possible your phone is broadcasting at an 802.11 channel that your router is not. Depending on your router, you may be able to log in and configure different channels to find the one that your wifi card is able to pick up.

Here is what mine looks like:

I changed the 802.11 mode on our router to b/g/n mode because we had this old Roku device that needed the b channel (or n channel, I forget, doesnโ€™t matter!). I would try out a few different channels and see if you can find one that works.

As far as the frequency goes, your phone is probably broadcasting at 2.4 GHz (unless you configured it otherwise), but again it might be worth playing around and seeing if you can set it to a frequency that your laptop will pick up.

1 Like

A post was split to a new topic: Hijack from another distro

I've switched into linux lts and updated the system, wrote that line in /etc/modprobe.d/rtl8822be.conf , rebooted but nothing changed: still facing the same problem.
Btw, I don't think that the problem is related to my router as the wifi was working when I just installed Garuda Linux.

Running the line : cat /etc/modprobe/.d/rtl8822be.conf justs displays : options rtw_pci disable_aspm=Y


@pro, I apologize for locking your thread and not reopening it for days. It was the only way to stop a very persistent user from hijacking your thread continually with unrelated posts.


If you still have the rtw88-dkms-git driver installed (reinstall it if you don't), try blacklisting the rtw88_8822be module.

Create or modify the following file:

/etc/modprobe.d/rtl8822be.conf

Add only the following line to the conf file, (delete any other entries):

blacklist rtw88_8822be

Then reboot.


If the new blacklist doesn't help, then try below:


Disable IPv6 and set your WiFi to performance via kernel boot parameters:

If you are unfamiliar with how to add a kernel boot parameter it can be done easily by using the following command:

sudo cp /etc/default/grub /etc/default/grub.bak && sudo sed '/^GRUB_CMDLINE_LINUX_DEFAULT=/s/"$/ pcie_aspm.policy=performance ipv6.disable=1"/g' -i /etc/default/grub && sudo update-grub 

Press ENTER again if the grub update process does not start scrolling onscreen.

The process wil take a little while to complete, and this is perfectly normal.

Once the grub update process is complete, reboot.

If the change does not improve your connectivity you can restore the file to its original state with:

sudo cp /etc/default/grub.bak /etc/default/grub

After restoring the grub file, again run:

sudo update-grub 

Then reboot again.


If none of above helps, then please post:

systemctl status iwd.service
systemctl status wpa_supplicant.service
systemctl status NetworkManager.service
pacman -Q rtw88-dkms-git
grep -r "blacklist\|install\|options"  /etc/modprobe.d/ /etc/modules-load.d/ /usr/lib/modprobe.d/

I hope that helps get things working @pro.


4 Likes

Nothing has worked yet.
Here are the outputs :

Loaded: loaded (/usr/lib/systemd/system/iwd.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-02-15 08:13:01 CET; 2min 21s ago
Main PID: 510 (iwd)
Tasks: 1 (limit: 9376)
Memory: 1.7M
CPU: 327ms
CGroup: /system.slice/iwd.service
โ””โ”€510 /usr/lib/iwd/iwd

ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:                 HT RX MCS indexes:
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:                         0-15
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:                         32
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:                 VHT Capabilities:
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:                         Short GI for 80Mhz
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:                         Max RX MCS: 0-9 for NSS: 2
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:                         Max TX MCS: 0-9 for NSS: 2
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:         Ciphers: CCMP TKIP BIP
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]:         Supported iftypes: ad-hoc station ap
ููŠูุฑูŠ 15 08:13:01 salem-hppaviliongaminglaptop15cx0xxx iwd[510]: Wiphy phy0 will only use the default interface
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~



wpa_supplicant.service
Loaded: masked (Reason: Unit wpa_supplicant.service is masked.)
Active: inactive (dead)


NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
โ””โ”€NetworkManager-ovs.conf
Active: active (running) since Tue 2022-02-15 08:13:02 CET; 4min 55s ago
Docs: man:NetworkManager(8)
Main PID: 506 (NetworkManager)
Tasks: 3 (limit: 9376)
Memory: 12.1M
CPU: 127ms
CGroup: /system.slice/NetworkManager.service
โ””โ”€506 /usr/bin/NetworkManager --no-daemon

ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.3406] settings: (eno1): created default wired connection 'Wired connection 1'
ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.3410] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.6902] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.6908] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.8382] device (wlan0): new IWD device state is disconnected
ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.8383] ovsdb: disconnected from ovsdb
ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.8391] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
ููŠูุฑูŠ 15 08:13:04 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909184.8428] modem-manager: ModemManager available
ููŠูุฑูŠ 15 08:13:10 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909190.6924] manager: startup complete
ููŠูุฑูŠ 15 08:13:34 salem-hppaviliongaminglaptop15cx0xxx NetworkManager[506]: <info>  [1644909214.7454] agent-manager: agent[6a443684d9decf8d,:1.28/org.kde.plasma.networkmanagement/1000]: agent registered


rtw88-dkms-git r121.ac5fce5-1

/etc/modprobe.d/rtl8822be.conf:blacklist rtw88_8822be
/usr/lib/modprobe.d/optimus-manager.conf:blacklist nouveau
/usr/lib/modprobe.d/optimus-manager.conf:blacklist nvidia_drm
/usr/lib/modprobe.d/optimus-manager.conf:blacklist nvidia_uvm
/usr/lib/modprobe.d/optimus-manager.conf:blacklist nvidia_modeset
/usr/lib/modprobe.d/optimus-manager.conf:blacklist nvidia
/usr/lib/modprobe.d/nvidia-utils.conf:blacklist nouveau
/usr/lib/modprobe.d/nvdimm-security.conf:install libnvdimm /usr/bin/ndctl load-keys ; /sbin/modprobe --ignore-install libnvdimm $CMDLINE_OPTS
/usr/lib/modprobe.d/bluetooth-usb.conf:options btusb reset=1
/usr/lib/modprobe.d/nobeep.conf:blacklist pcspkr
/usr/lib/modprobe.d/noime.conf:blacklist mei
/usr/lib/modprobe.d/noime.conf:blacklist mei_me
/usr/lib/modprobe.d/systemd.conf:options bonding max_bonds=0
/usr/lib/modprobe.d/systemd.conf:options dummy numdummies=0
/usr/lib/modprobe.d/amdgpu.conf:options amdgpu ppfeaturemask=0xffffffff

Please read

I just edit your post.

1 Like

please post:

lsmod |sort
uname -r
bash -c "pacman -Qsq ^linux | grep ^linux | grep -viE 'api|firm|nvidia|hotspot|console'"
sudo dmesg  | grep -Ei 'error|segf|fail|broke|warn|dump|denied|firm|regdom|cfg80211|alpha2|wmi|rtl|wl|rtw|blue|deauth' | grep -viE 'acpi|ras'
journalctl --no-pager -S "$(date +'%Y-%m-%d')" -u NetworkManager  | grep -i 'discon\|error\|seg\|fail\|broke\|warn\|change\|wl\|rtl|rtw'      
hwinfo --netcard --wlan --bluetooth | grep -Ei "model\:|driver\:|status\:|cmd\:|file\:|detected\:" | grep -v "Config Status"
cat /etc/modprobe.d/rtl8822be.conf
3 Likes
ac97_bus               16384  1 snd_soc_core
acpi_call              16384  0
acpi_pad               24576  0
acpi_thermal_rel       16384  1 int3400_thermal
aesni_intel           380928  3
af_alg                 32768  7 algif_hash,algif_skcipher,algif_aead
alcor                  32768  0
alcor_pci              20480  1 alcor
algif_aead             16384  0
algif_hash             16384  1
algif_skcipher         16384  1
amdgpu               8507392  0
atkbd                  40960  0
blake2b_generic        20480  0
bluetooth             737280  35 btrtl,btintel,btbcm,bnep,btusb,rfcomm
bnep                   28672  2
bpf_preload            16384  0
btbcm                  20480  1 btusb
btintel                45056  1 btusb
btrfs                1691648  1
btrtl                  28672  1 btusb
btusb                  65536  0
cbc                    16384  0
ccm                    20480  0
cfg80211             1048576  2 rtw_core,mac80211
cm32181                16384  0
cmac                   16384  2
coretemp               20480  0
crc16                  16384  1 bluetooth
crc32c_generic         16384  0
crc32c_intel           24576  2
crc32_pclmul           16384  0
crct10dif_pclmul       16384  1
cryptd                 28672  3 crypto_simd,ghash_clmulni_intel
crypto_simd            16384  1 aesni_intel
crypto_user            24576  0
des_generic            16384  0
drm_ttm_helper         16384  2 amdgpu,radeon
ecb                    16384  0
ecdh_generic           16384  1 bluetooth
ee1004                 20480  0
fat                    86016  1 vfat
fuse                  172032  1
ghash_clmulni_intel    16384  0
gpu_sched              49152  1 amdgpu
hp_accel               28672  0
hp_wmi                 24576  0
i2c_dev                24576  0
i2c_i801               45056  0
i2c_smbus              20480  1 i2c_i801
i8042                  45056  1 hp_accel
i915                 3227648  40
industrialio          102400  4 industrialio_triggered_buffer,cm32181,kfifo_buf,kxcjk_1013
industrialio_triggered_buffer    16384  1 kxcjk_1013
int3400_thermal        20480  0
int3403_thermal        20480  0
int340x_thermal_zone    20480  2 int3403_thermal,processor_thermal_device
intel_agp              24576  0
intel_cstate           20480  0
intel_gtt              28672  2 intel_agp,i915
intel_pch_thermal      20480  0
intel_pmc_bxt          16384  1 iTCO_wdt
intel_powerclamp       20480  0
intel_rapl_common      32768  2 intel_rapl_msr,processor_thermal_rapl
intel_rapl_msr         20480  0
intel_soc_dts_iosf     20480  1 processor_thermal_device_pci_legacy
intel_tcc_cooling      16384  0
intel_uncore          204800  0
intel_vbtn             24576  0
intel_wmi_thunderbolt    20480  0
intel_xhci_usb_role_switch    16384  0
ipmi_devintf           20480  0
ipmi_msghandler        77824  1 ipmi_devintf
ip_tables              36864  0
iTCO_vendor_support    16384  1 iTCO_wdt
iTCO_wdt               16384  0
joydev                 28672  0
kfifo_buf              16384  1 industrialio_triggered_buffer
kxcjk_1013             36864  0
ledtrig_audio          16384  1 snd_hda_codec_generic
libarc4                16384  1 mac80211
libcrc32c              16384  1 btrfs
libdes                 24576  1 des_generic
libphy                163840  3 r8169,mdio_devres,realtek
libps2                 20480  2 atkbd,psmouse
lis3lv02d              32768  1 hp_accel
loop                   40960  14
mac80211             1204224  2 rtw_core,rtw_pci
mac_hid                16384  0
mc                     69632  4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
md4                    16384  0
mdio_devres            16384  1 r8169
mmc_core              221184  1 alcor
Module                  Size  Used by
mousedev               24576  0
nfnetlink              20480  0
ns                     36864  1 qrtr
nvidia              39124992  89 nvidia_modeset
nvidia_drm             73728  2
nvidia_modeset       1163264  3 nvidia_drm
pkcs8_key_parser       16384  0
platform_profile       16384  1 hp_wmi
processor_thermal_device    20480  1 processor_thermal_device_pci_legacy
processor_thermal_device_pci_legacy    16384  0
processor_thermal_mbox    16384  2 processor_thermal_rfim,processor_thermal_device
processor_thermal_rapl    20480  1 processor_thermal_device
processor_thermal_rfim    16384  1 processor_thermal_device
psmouse               212992  0
qrtr                   20480  4
r8169                 102400  0
radeon               1863680  0
raid6_pq              122880  1 btrfs
rapl                   16384  0
realtek                36864  1
rfcomm                 90112  4
rfkill                 36864  8 hp_wmi,bluetooth,cfg80211
roles                  16384  2 typec_ucsi,intel_xhci_usb_role_switch
rtw_8822b             233472  1 rtw_8822be
rtw_8822be             16384  0
rtw_core              278528  2 rtw_8822b,rtw_pci
rtw_pci                36864  1 rtw_8822be
serio                  28672  7 serio_raw,atkbd,hp_accel,psmouse,i8042
serio_raw              20480  0
snd                   126976  18 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm
snd_compress           28672  1 snd_soc_core
snd_hda_codec         180224  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
snd_hda_codec_hdmi     81920  2
snd_hda_codec_realtek   163840  1
snd_hda_core          114688  8 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl
snd_hda_ext_core       36864  2 snd_soc_hdac_hda,snd_soc_skl
snd_hda_intel          61440  2
snd_hrtimer            16384  1
snd_hwdep              16384  1 snd_hda_codec
snd_intel_dspcfg       32768  2 snd_hda_intel,snd_soc_skl
snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg
snd_pcm               159744  8 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_seq                94208  7 snd_seq_dummy
snd_seq_device         16384  1 snd_seq
snd_seq_dummy          16384  0
snd_soc_acpi           16384  2 snd_soc_acpi_intel_match,snd_soc_skl
snd_soc_acpi_intel_match    57344  1 snd_soc_skl
snd_soc_core          385024  2 snd_soc_hdac_hda,snd_soc_skl
snd_soc_hdac_hda       28672  1 snd_soc_skl
snd_soc_skl           217088  0
snd_soc_sst_dsp        36864  1 snd_soc_skl
snd_soc_sst_ipc        20480  1 snd_soc_skl
snd_timer              49152  3 snd_seq,snd_hrtimer,snd_pcm
soundcore              16384  1 snd
sparse_keymap          16384  2 hp_wmi,intel_vbtn
squashfs               77824  7
ttm                    86016  4 amdgpu,radeon,drm_ttm_helper,i915
typec                  65536  1 typec_ucsi
typec_ucsi             53248  1 ucsi_acpi
ucsi_acpi              16384  0
uinput                 20480  0
uvcvideo              143360  0
vfat                   24576  1
video                  57344  1 i915
videobuf2_common       81920  4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
videobuf2_memops       20480  1 videobuf2_vmalloc
videobuf2_v4l2         40960  1 uvcvideo
videobuf2_vmalloc      20480  1 uvcvideo
videodev              299008  3 videobuf2_v4l2,uvcvideo,videobuf2_common
wireless_hotkey        16384  0
wmi                    45056  3 hp_wmi,intel_wmi_thunderbolt,wmi_bmof
wmi_bmof               16384  0
x86_pkg_temp_thermal    20480  0
xhci_pci               20480  0
xhci_pci_renesas       24576  1 xhci_pci
xor                    24576  1 btrfs
x_tables               57344  1 ip_tables
zram                   36864  2
uname -r
5.15.22-1-lts
bash -c "pacman -Qsq ^linux | grep ^linux | grep -viE 'api|firm|nvidia|hotspot|console'"
linux
linux-headers
linux-lts
linux-lts-headers
linux-zen
linux-zen-headers
sudo dmesg  | grep -Ei 'error|segf|fail|broke|warn|dump|denied|firm|regdom|cfg80211|alpha2|wmi|rtl|wl|rtw|blue|deauth' | grep -viE 'acpi|ras'
[sudo] password for salem:
[    0.134032] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    1.335632] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    2.028791] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    2.028797] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    2.028800] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    2.028803] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    2.029371] wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control method not found
[    2.058001] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.058590] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[    2.058592] pcieport 0000:00:1c.7:   device [8086:9d17] error status/mask=00001000/00002000
[    2.058601] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.058881] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.059177] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.059465] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[    2.059467] pcieport 0000:00:1c.7:   device [8086:9d17] error status/mask=00001000/00002000
[    2.059474] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
[    2.060335] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.060632] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
[    2.060633] pcieport 0000:00:1c.7:   device [8086:9d17] error status/mask=00001001/00002000
[    2.061224] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.061812] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[    2.061814] pcieport 0000:00:1c.7:   device [8086:9d17] error status/mask=00001000/00002000
[    2.061821] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.062103] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.062401] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.063003] pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[    2.063005] pcieport 0000:00:1c.7:   device [8086:9d17] error status/mask=00001000/00002000
[    2.063011] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.063018] pcieport 0000:00:1c.7: AER: Multiple Corrected error received: 0000:00:1c.7
[    2.063026] pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7
[    2.915280] usb 1-6: Product: Bluetooth Radio
[   10.382477] systemd[1]: Listening on Process Core Dump Socket.
[   10.410166] systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
[   12.837427] intel-vbtn INT33D6:00: failed to read Intel Virtual Button driver
[   13.930453] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   13.931998] Bluetooth: Core ver 2.22
[   13.932015] NET: Registered PF_BLUETOOTH protocol family
[   13.932016] Bluetooth: HCI device and connection manager initialized
[   13.932019] Bluetooth: HCI socket layer initialized
[   13.932020] Bluetooth: L2CAP socket layer initialized
[   13.932023] Bluetooth: SCO socket layer initialized
[   13.933370] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   14.226204] r8169 0000:02:00.0 eth0: RTL8168h/8111h, b0:0c:d1:ed:4d:76, XID 541, IRQ 129
[   14.559158] input: HP WMI hotkeys as /devices/virtual/input/input8
[   14.749923] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x4d5f02)
[   14.786746] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822
[   14.787763] Bluetooth: hci0: RTL: rom_version status=0 version=2
[   14.787766] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
[   15.109615] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
[   15.110505] Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
[   15.646486] rtw_8822be 0000:03:00.0: Firmware version 27.2.0, H2C version 13
[   15.852731] Bluetooth: hci0: RTL: fw version 0xab6b705c
[   19.849509] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   19.849511] Bluetooth: BNEP filters: protocol multicast
[   19.849515] Bluetooth: BNEP socket layer initialized
[   20.247255] rtw_8822be 0000:03:00.0: start vif 48:5f:99:19:3f:f7 on port 0
[   51.198655] audit: type=1100 audit(1644928906.120:112): pid=2626 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="salem" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[   51.199099] audit: type=1103 audit(1644928906.120:114): pid=2626 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct="salem" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
[   65.718010] Bluetooth: RFCOMM TTY layer initialized
[   65.718015] Bluetooth: RFCOMM socket layer initialized
[   65.718018] Bluetooth: RFCOMM ver 1.11
[  117.571977] audit: type=1130 audit(1644928972.500:137): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nmb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[  416.381616] audit: type=1100 audit(1644929271.310:140): pid=20797 uid=1000 auid=1000 ses=2 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="salem" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[  416.381921] audit: type=1110 audit(1644929271.310:142): pid=20797 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
journalctl --no-pager -S "$(date +'%Y-%m-%d')" -u NetworkManager  |grep -i 'discon\|error\|seg\|fail\|broke\|warn\|change\|wl\|rtl|rtw'
fish: $(...) is not supported. In fish, please use '(date)'.
journalctl --no-pager -S "$(date +'%Y-%m-%d')" -u NetworkManager  |grep -i 'discon\|error\|seg\|fail\|broke\|warn\|change\|wl\|rtl|rtw'
^
hwinfo --netcard --wlan --bluetooth | grep -Ei "model\:|driver\:|status\:|cmd\:|file\:|detected\:" | grep -v "Config Status"
Model: "Hewlett-Packard Company Realtek RTL8822BE 802.11ac 2 ร— 2 Wi-Fi + Bluetooth 4.2 Combo Adapter (MU-MIMO supported)"
Driver: "rtw_8822be"
Device File: wlan0
Link detected: no
Driver Status: rtw88_8822be is not active
Driver Activation Cmd: "modprobe rtw88_8822be"
Driver Status: rtw_8822be is active
Driver Activation Cmd: "modprobe rtw_8822be"
Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
Driver: "r8169"
Device File: eno1
Link detected: no
Driver Status: r8169 is active
Driver Activation Cmd: "modprobe r8169"
Model: "Realtek Bluetooth 4.2 Adapter"
Driver: "btusb"
Driver Status: btusb is active
Driver Activation Cmd: "modprobe btusb"
cat /etc/modprobe.d/rtl8822be.conf
File: /etc/modprobe.d/rtl8822be.conf
blacklist rtw88_8822be

Try using the iwd utility to connect. For example,

  • Find your device name
iwctl device list
  • Search available WiFi providers, using the device found from previous command (example wlan0)
iwctl station wlan0 scan

Read manual, how-to usage and test. Post feedback.

Sadly, there have been so many changes at this point that it may be impossible to figure out what needs to be done to effect a fix (if that is even possible with your adapter).

I rarely ever tell people this, but it may be that reinstalling is the only way to methodically work through what needs to be done. Immediately after reinstalling create a snapshot of your system.

Was your wifi working on the live disk before you installed?

Was the wifi working immediately after install, before you rebooted?

If the answer is yes to either of those questions, you may be better to perform an offline install without an internet connection.

That way you could take a system snapshot immediately after install and have a known good working setup to roll your system back to.

We would then need to meticulously work through steps one at a time to pinpoint the changes that will result in giving you a working setup (after performing an update).

If you perform an offline install, do not make any changes without my instructing you specifically to do so. Simply take a system snapshot immediately after installation and then wait for me to tell you what to do.

Sorry, but this seems the most straight forward way of finding the cause, and any possible fix for your issues.


If you haven't given up on your issue completely I have an Idea on how to sort through all the different modules and the different driver options that need to be tested. My thought is to blacklist every rtl8822be related module and then test the different modules and options via modprobing. Creating the blacklist file required for this will also disable your bluetooth. Bluetooth can often interfere with proper wifi operation on some wifi/bluetooth combo chips such as yours, so we need to test disabling it. If you are using bluetooth devices such as a wireless mouse or keyboard you will need to substitute a non-bluethooth device during this test.


Create the following file:

/etc/modprobe.d/rtl8822be-blacklist.conf

Add the following lines to the rtl8822be-blacklist.conf file:

blacklist btrtl
blacklist btusb
blacklist 8822b
blacklist 8822be
blacklist r8822b
blacklist r8822be
blacklist rtw88
blacklist rtw88_8822b
blacklist rtw88_8822be
blacklist rtw88_pci
blacklist rtw88_core
blacklist rtwpci
blacklist rtw_pci

This file will blacklist all the rtl8822be driver modules including Bluetooth, (preventing all from auto-starting).

Save the blacklist file, then run:

sudo depmod -a && sudo mkinitcpio -P

Then power down (not reboot).


After restarting, install/reinstall the rtw88-dkms-git driver from the Chaotic AUR:

sudo  pacman -Syu rtw88-dkms-git

After the installation is complete, again run:

sudo depmod -a && sudo mkinitcpio -P

Then power off completely, remove the power plug and battery, (if possible). Wait for a minute or so, reconnect power, then boot into Garuda.


After restarting, issue the following command:

sudo modprobe rtw_pci disable_aspm=1

Check your wifi connectivity, and if no better then issue the following command:

sudo modprobe -r rtw_pci ; sleep 3; sudo modprobe rtw_pci disable_aspm=y

If your connectivity is still no better, then reboot.


After restarting, issue the following command:

sudo modprobe rtw88_8822be

Check your wifi connectivity, and if no better, then reboot again.


After restarting, issue the following command:

sudo modprobe rtw88_8822be disable_aspm=1

Check your wifi connectivity, and if no better, then reboot again.


After restarting, issue the following command:

sudo modprobe rtw88_pci 

Check your wifi connectivity, and if no better, then reboot again.


After restarting, issue the following command:

sudo modprobe rtw88_pci disable_aspm=1

Check your wifi connectivity, and if no better, then reboot again.


After restarting, issue the following command:

sudo modprobe rtw88_core disable_lps=y; sudo modprobe rtw88_pci disable_aspm=y disable_msi=y

Then check your wifi connectivity.


Hopefully, modprobing one of the driver/options will successfully initiate your wifi. Once this is determined, we can then figure out how best to configure your system for this to work automatically, (without requiring a manual modprobe). Please report on all results by providing the terminal input and output of all modprobe commands run.


Hopefully one of the above modprobe commands now has your wifi working correctly.

If so, and you require Bluetooth to be working run this command:

sudo modprobe btrtl; sudo systemctl restart bluetooth: sudo bluetoothctl power on

If your bluetooth and wifii are still working correctly after running that command, then you should check if bluetooth can be re-enabled permanently.

To check if bluetooth can be permanently enabled, alter the blacklist file contents to this:

#blacklist btrtl
#blacklist btusb
blacklist 8822b
blacklist 8822be
blacklist r8822b
blacklist r8822be
blacklist rtw88
blacklist rtw88_8822b
blacklist rtw88_8822be
blacklist rtw88_pci
blacklist rtw88_core
blacklist rtwpci
blacklist rtw_pci


Comment out the blacklisting of the two bluetooth modules with hash tags, (as above). You must restart the computer for these changes to take effect. If your wifi and bluetooth are still working after startup, then the bluetooth entries can be removed from the blacklist permanently. If your wifi and bluetooth are not working after removing the bluetooth entries from the blacklist, then you will need to blacklist them again. If your bluetooth can be restarted manually, then you will need to run those commands after each startup. You could alternatively create a service to start your bluetooth automatically for you.

You can delete the /etc/modprobe.d/rtl8822be-blacklist.conf file entirely if does not improve your wifi.

Reboot after making any alterations to configuration files in /etc/modprobe.d.


5 Likes

I worked through the rtl8822be driver issue with another user recently. The process for getting the driver working correctly is located here:

3 Likes

Hi there @pro.

What up bro?

I've typed up a thousand word essay since you last responded on your own help request 12 days ago. I see you were online a few days ago, yet you didn't have the common courtesy to even acknowledge the attempts from several admins to help you with your issue in going on 2 weeks.

Has your issue been resolved yet?

If not, see the link I posted for a likely fix for your adapter. I put in a lot of effort refining the steps I first posted here to solve the riddle of what was required to get the Rtl8822be adapter working. The user on that thread stuck with it until the end to find a solution (unlike yourself).

From all appearances you made a cry for help here, then simply abandoned your thread without so much as an acknowledgement or thank you to those who attempted to help you.

Very poor form my friend.

If your issue is now resolved, please mark the thread solved. I don't like to leave threads dangling in the Network Support category as I always try to see them wrapped up in some way that will help other users with the same issue.

4 Likes

The OP has not responded in 3 weeks.

Thread deemed abandoned.

Thread locked.

1 Like