RTL8822CE - Rtw88-fixed-dkms-git cannot upgrade wifi driver

Issues & Assistance Networking Support
1

Hi, thank You very much for help. But today when I launch garuda updte everything went fine. I don’t have to change anything :slight_smile:

But I have problem with other stuff.
Sometime ago I change for zen kernel because it works better with my laptop battery.
When I change kernel I have to also change wifi drivers because they don’t works with zen. I use now rtw88-fixed-dkms-git but I cannot upgrade them for few months.

udowanie rtw88-fixed-dkms-git...
==> Tworzenie pakietu: rtw88-fixed-dkms-git r667.fa96fd4-1 (pią, 25 lip 2025, 11:27:25)
==> Sprawdzanie zależności potrzebnych do uruchomienia...
==> Sprawdzanie zależności potrzebnych do budowy...
==> Pobieranie źródeł...
  -> Aktualizowanie rtw88 repozytorium git...
  -> Znaleziono rtw88-fixed.conf
  -> Znaleziono firmware-path.patch
==> Sprawdzanie plików source za pomocą sha256sums...
    rtw88 ... Pominięto
    rtw88-fixed.conf ... Zgadza się
    firmware-path.patch ... Zgadza się
==> Usuwanie istniejącego katalogu $srcdir/...
==> Rozpakowywanie źródeł...
  -> Tworzenie kopii roboczej repozytorium rtw88 git...
Klonowanie do „rtw88”...
gotowe.
==> Rozpoczynanie prepare()...
patching file rtw8703b.c
Hunk #1 FAILED at 1955.
Hunk #2 succeeded at 1956 (offset -59 lines).
Hunk #3 succeeded at 2009 (offset -59 lines).
1 out of 3 hunks FAILED -- saving rejects to file rtw8703b.c.rej
patching file rtw8723d.c
Hunk #1 FAILED at 2114.
Hunk #2 succeeded at 2199 (offset 1 line).
1 out of 2 hunks FAILED -- saving rejects to file rtw8723d.c.rej
patching file rtw8812a.c
Hunk #1 FAILED at 1016.
Hunk #2 succeeded at 1117 (offset 22 lines).
1 out of 2 hunks FAILED -- saving rejects to file rtw8812a.c.rej
patching file rtw8821a.c
Hunk #1 FAILED at 1110.
Hunk #2 succeeded at 1218 (offset 28 lines).
1 out of 2 hunks FAILED -- saving rejects to file rtw8821a.c.rej
patching file rtw8821c.c
Hunk #1 FAILED at 1951.
Hunk #2 succeeded at 2057 (offset 23 lines).
1 out of 2 hunks FAILED -- saving rejects to file rtw8821c.c.rej
patching file rtw8822b.c
Hunk #1 FAILED at 2490.
Hunk #2 succeeded at 2603 (offset 23 lines).
1 out of 2 hunks FAILED -- saving rejects to file rtw8822b.c.rej
patching file rtw8822c.c
Hunk #1 FAILED at 5310.
Hunk #2 succeeded at 5394 (offset 22 lines).
Hunk #3 succeeded at 5435 (offset 22 lines).
1 out of 3 hunks FAILED -- saving rejects to file rtw8822c.c.rej
==> ERROR: in prepare().
    Przerywam...

I need advice what to do now. Remove that drivers and try rtw88-dkm-git, then if wifi don’t work, change kernel or it’s possible to make some fix?

 ╰─λ garuda-inxi
System:
  Kernel: 6.15.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: hpet avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=417f187a-a42b-44a5-b6b3-c27517119ed0 rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=8f7c97f0-2758-4001-95b0-57f15fb14228 loglevel=3 ibt=off
  Desktop: GNOME v: 48.3 tk: GTK v: 3.24.49 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 48.0 Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: HUAWEI product: KLVL-WXX9 v: M1300
    serial: <superuser required>
  Mobo: HUAWEI model: KLVL-WXX9-PCB v: M1300 serial: <superuser required>
    part-nu: C178 uuid: <superuser required> UEFI: HUAWEI v: 1.06
    date: 09/14/2020
Battery:
  ID-1: BAT0 charge: 21.1 Wh (42.6%) condition: 49.5/54.9 Wh (90.0%)
    volts: 8.1 min: 7.6 model: SUNWODA HB4593R1ECW-22S0 type: Li-ion
    serial: <filter> status: charging cycles: 674
CPU:
  Info: model: AMD Ryzen 5 4600H with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 gen: 2 level: v3 note: check built: 2020-22
    process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1
    microcode: 0x860010D
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 1397 min/max: 1400/3000 boost: enabled scaling:
    driver: acpi-cpufreq governor: powersave cores: 1: 1397 2: 1397 3: 1397
    4: 1397 5: 1397 6: 1397 7: 1397 8: 1397 9: 1397 10: 1397 11: 1397 12: 1397
    bogomips: 71864
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir [Radeon Vega Series /
    Radeon Mobile Series] vendor: Huaqin driver: amdgpu v: kernel arch: GCN-5
    code: Vega process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 04:00.0
    chip-ID: 1002:1636 class-ID: 0300 temp: 40.0 C
  Device-2: IMC Networks HD Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4:3 chip-ID: 13d3:5451
    class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0893 built: 2019 res: 2160x1440
    dpi: 185 gamma: 1.2 size: 296x197mm (11.65x7.76") diag: 356mm (14")
    ratio: 3:2 modes: max: 2160x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    renoir ACO DRM 3.63 6.15.7-zen1-1-zen) device-ID: 1002:1636
    memory: 500 MiB unified: no display-ID: :0.0
  API: Vulkan v: 1.4.321 layers: 5 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: mesa radv v: 25.1.6-arch1.1
    device-ID: 1002:1636 surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.1.6-arch1.1 (LLVM
    20.1.8) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo wl: wdisplays
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
    Audio vendor: Huaqin driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Huaqin
    driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Huaqin driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.15.7-zen1-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.4.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    vendor: & Tele RSH driver: rtw_8822ce v: kernel modules: rtw88_8822ce pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 01:00.0
    chip-ID: 10ec:c822 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:2 chip-ID: 1358:c123
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 476.94 GiB used: 261.04 GiB (54.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN530
    SDBPNPZ-512G-1027 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 21117000 temp: 43.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 261.04 GiB (55.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 596 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 261.04 GiB (55.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 261.04 GiB (55.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 261.04 GiB (55.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 7.12 GiB used: 788.4 MiB (10.8%)
    priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: amdgpu temp: 40.0 C
  Fan Speeds (rpm): fan-1: 2796 fan-2: 3262
Info:
  Memory: total: 8 GiB note: est. available: 7.13 GiB used: 4.3 GiB (60.4%)
  Processes: 367 Power: uptime: 1h 33m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 2.81 GiB services: gsd-power,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: 1885 pm: dpkg pkgs: 0 pm: pacman pkgs: 1845 libs: 420
    tools: gnome-software,pamac,paru pm: flatpak pkgs: 40 Compilers: gcc: 15.1.1
    Shell: garuda-inxi default: Bash v: 5.3.3 running-in: gnome-terminal
    inxi: 3.3.38
Garuda (2.7.3-2):
  System install date:     2022-04-09
  Last full system update: 2025-07-25 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio
  Windows dual boot:       No/Undetected
  Failed units:            syncthing@przemyslaw.service

Regards.

2

pls reboot

Driver ↔ kernel… have everytime a dependence. Which driver is to use if “i” switch to a different kernel.

If you use this you need rtw88-fixed-firmware-git (my mind)
Special linux-firmware stuff “was” a small problem some days ago.

Yes, try and test on different kernels “only” rtw88-dkms-git
To test pls delete the rtw88 folder in your /home/(user)/.cache/paru/ directory then uninstall rtw88-fixed-dkms ( paru -R rtw88-fixed-dkms ) then install
pacman -S linux-firmware-realtek
paru -S rtw88-dkms-git
→ reboot → result = ?

as info …if you install over paru a package and a update is pulled in (aur source) → pls delete this folder inside your home/user/.cache/paru folder every time before you make a update.
(my mind)

3 Likes
3

As a last resort, I suggest that you should leave a comment in the AUR package below for the maintainer to check what might be going on.

I’m not a developer, but something tells me that maybe the patch file below needs to be adjusted.

It seems to me that your compilation process cannot process the patches correctly

2 Likes
4

Thank You ,I will start with that.
Regards.

5

I’m not a great believer in installing someone else’s hacked firmware verson. My suggestions would be to test the rtw88-dkms-git driver package along with the LTS kernel. Many Realtek WiFi drivers break temporarily when the kernel is updated. The usual solution in these circumstances is to switch to the LTS kernel until the current kernel has been modified to work with the affected Realtek WiFi driver again.

Follow my directions below to hopefully get your WiFi working properly with the LTS kernel.

Install the LTS kernel:

sudo pacman -S linux-lts linux-lts-headers

Reboot.

Uninstall any other Realtek driver version you currently have installed, then reboot.

Next, install the required Realtek firmware package with this command:

sudo pacman -S linux-firmware-realtek

Reboot.

Once any alternate driver has been uninstalled and the Realtek firmware package has been installed, then install the rtw88-dkms-git driver from the Chaotic AUR.

Install the rtw88-dkms-git Chaotic AUR Realtek driver with the following command:

sudo  pacman -S rtw88-dkms-git

Then reboot.

Generally the RTL8822CE WiFi adapter won’t operate properly without creating additional configuration files. You will firstly need to create a driver parameter configuration file for your newly installed driver:

 sudo touch /etc/modprobe.d/rtl8822ce.conf

Open the newly created /etc/modprobe.d/rtl8822ce.conf file in your favorite text editor and paste the following contents:

options rtw_pci disable_aspm=1
blacklist rtw88_8822ce

Save the new additions to the configuration file, and close your text editor, then reboot.

Alternately, you can instead generate the above required conf file with the following command:

echo -e "options rtw_pci disable_aspm=1\nblacklist rtw88_8822ce" | sudo tee /etc/modprobe.d/rtl8822ce.conf

This will automatically generate the required rtl8822ce driver parameter configuration file without requiring any manual editing.

Reboot after the creation of the conf file using either method.

If your WiFi is still not performing adequately after creating a driver configuration file, you can also try adding a kernel boot parameter that could help further improve your WiFi’s performance.

Follow the directions below to test out a kernel boot parameter that could improve your WiFi’s performance:

Backup your grub config file:

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

Then edit /etc/default/grub and add pci=noaer to the end of the following line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3 pci=noaer"

The above line will look similar on most systems, but will likely contain different boot parameters as each system is different.

After adding the boot parameter and saving your changes, run:

sudo update-grub

Reboot.

Editing the grub configuration file can be risky. If you are not comfotable/familiar with performing this type of editing, then use the method below.

Alternately:

Again, rather than creating the required changes manually you can generate the change to the grub config file automatically with the following command::

sudo cp /etc/default/grub /etc/default/grub.bak && sudo sed '/^GRUB_CMDLINE_LINUX_DEFAULT=/s/"$/ pci=noaer"/g' -i /etc/default/grub

After the above command successfully adds the boot parameter(s), run:

sudo update-grub

Then, reboot.

I hope those suggestions help get your WiFi working correctly. Unfortunately, this is one of Realtek’s most problematic wifi adapters. You might want to consider a replacement to avoid these driver/firmware issues.

Good luck.

5 Likes
6

sorry.. you have absolutly right with your comment / answer and the steps, only..install with
paru -S rtw88-dkms-git

6 Likes
7

You are correct, rtw88-dkms-git is no longer in the chaotic aur, so using paru would be the correct installation method.

Good catch @gampel.

6 Likes
8

Thanks, developer answer me and tell to use rtw88-dkms-git. Now it’s fixed and working with zen kernel. My wifi works and everything looks ok for now.
Regards.

9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.