Realtek rtl8192eu Wifi - device disappeared after upgrading Garuda

Issues & Assistance Networking Support
1

Hi!

Something strange happened when I upgraded Garuda. I should have device2 in the networking part of the inxi with TP-Link TL-WN823N and rtl8192eu-dkms as a driver for it, but instead there’s nothing. I checked that my blacklist for rtl8xxxu (if I remember this right as I’m writing this on another computer) is still in place and the aforementioned driver installed and they seem to be there, but not in use and no network connection either.

Here’s the inxi and after it, an exerpt from pacman.log where the error occurred and after that, an another exerpt from the file mentioned after the error line in the log.

System:
Kernel: 6.13.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=069e92bc-7096-454e-acbc-99c4eff50739 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: H510M K V2 v: -CF
serial: <superuser required>
Mobo: Gigabyte model: H510M K V2 v: x.x serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends v: F2 date: 06/07/2023
CPU:
Info: model: Intel Core i3-10105F bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 3 microcode: 0xFC
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 800/4400 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 bogomips: 59197
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel DG2 [Arc A310] vendor: ASRock driver: i915 v: kernel
alternate: xe arch: Xe-HPG code: Alchemist process: TSMC n6 (7nm)
built: 2022+ pcie: gen: 1 speed: 2.5 GT/s lanes: 1 ports: active: HDMI-A-1
empty: DP-1,HDMI-A-2 bus-ID: 03:00.0 chip-ID: 8086:56a6 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: HP 24y serial: <filter> built: 2019 res:
mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
size: 528x297mm (20.79x11.69") diag: 606mm (23.9") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Arc A310 Graphics (DG2)
device-ID: 8086:56a6 memory: 3.86 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.304 layers: 10 device: 0 type: discrete-gpu name: Intel
Arc A310 Graphics (DG2) driver: N/A device-ID: 8086:56a6
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
19.1.7 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel
v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: Intel DG2 Audio vendor: ASRock driver: snd_hda_intel v: kernel
pcie: speed: Unknown lanes: 63 link-max: gen: 1 speed: 2.5 GT/s
bus-ID: 04:00.0 chip-ID: 8086:4f92 class-ID: 0403
API: ALSA v: k6.13.7-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.1 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 RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 09:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 129.9 GiB used: 92.57 GiB (71.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SU650 size: 111.79 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 831a scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 model: Multi Flash Reader size: 3.69 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-3: /dev/sdc maj-min: 8:32 vendor: Kingston model: DataTraveler 2.0
size: 14.42 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 1.00
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 82.94 GiB (74.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 19.3 MiB (6.5%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 82.94 GiB (74.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 82.94 GiB (74.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 82.94 GiB (74.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.53 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 8
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 57.0 C pch: 50.0 C mobo: 42.0 C
Fan Speeds (rpm): cpu: 0
Info:
Memory: total: 16 GiB available: 15.53 GiB used: 2.3 GiB (14.8%)
Processes: 272 Power: uptime: 1h 52m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.2 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2013 libs: 576 tools: octopi,pacseek,paru
Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish
v: 4.0.1 running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2024-12-08
Last full system update: 2025-03-21
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:            nmb.service

THE MOMENT OF UPGRADE FAILURE FROM THE PACMAN.LOG:

[2025-03-21T13:39:16+0200] [ALPM] running '70-dkms-install.hook'...
[2025-03-21T13:39:16+0200] [ALPM-SCRIPTLET] ==> dkms install --no-depmod digimend-kernel-drivers/11.r42.gf3c7c7f -k 6.13.7-zen1-1-zen
[2025-03-21T13:39:19+0200] [ALPM-SCRIPTLET] ==> dkms install --no-depmod v4l2loopback/0.14.0 -k 6.13.7-zen1-1-zen
[2025-03-21T13:39:22+0200] [ALPM-SCRIPTLET] ==> dkms install --no-depmod v4l2loopback/0.14.0 -k 6.12.9-zen1-1-zen
[2025-03-21T13:39:25+0200] [ALPM-SCRIPTLET] ==> dkms install --no-depmod rtl8192eu/5.6.4.r302.g2fddecc -k 6.13.7-zen1-1-zen
[2025-03-21T13:40:08+0200] [ALPM-SCRIPTLET]
[2025-03-21T13:40:08+0200] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 6.13.7-zen1-1-zen (x86_64)
[2025-03-21T13:40:08+0200] [ALPM-SCRIPTLET] Consult /var/lib/dkms/rtl8192eu/5.6.4.r302.g2fddecc/build/make.log for more information.
[2025-03-21T13:40:08+0200] [ALPM-SCRIPTLET] ==> WARNING: `dkms install --no-depmod rtl8192eu/5.6.4.r302.g2fddecc -k 6.13.7-zen1-1-zen' exited 10
[2025-03-21T13:40:08+0200] [ALPM-SCRIPTLET] ==> depmod 6.13.7-zen1-1-zen
[2025-03-21T13:40:10+0200] [ALPM-SCRIPTLET] ==> depmod 6.12.9-zen1-1-zen
[2025-03-21T13:40:11+0200] [ALPM] running '80-check-broken-packages.hook'...

AN EXERPT FROM THE END OF THE FILE ASKED TO BE CONSULTED:

os_dep/linux/ioctl_cfg80211.c:674:5: warning: no previous prototype for 'nl80211_iftype_to_rtw_mlme_state' [>
674 | u32 nl80211_iftype_to_rtw_mlme_state(enum nl80211_iftype type)
|     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:2090:5: warning: no previous prototype for 'cfg80211_rtw_set_default_mgmt_key'>
2090 | int cfg80211_rtw_set_default_mgmt_key(struct wiphy *wiphy,
|     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:2614:5: warning: no previous prototype for 'rtw_cfg80211_is_target_wps_scan' [>
2614 | int rtw_cfg80211_is_target_wps_scan(struct cfg80211_scan_request *scan_req, struct cfg80211_ssid *ta>
|     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c: In function 'cfg80211_rtw_connect':
os_dep/linux/ioctl_cfg80211.c:3899:32: warning: implicit conversion from 'enum mlme_auth_type' to 'enum nl80>
3899 |                 sme->auth_type = MLME_AUTHTYPE_SAE;
|                                ^
os_dep/linux/ioctl_cfg80211.c: At top level:
os_dep/linux/ioctl_cfg80211.c:5227:6: warning: no previous prototype for 'dump_station_parameters' [-Wmissin>
5227 | void dump_station_parameters(void *sel, struct wiphy *wiphy, const struct station_parameters *params)
|      ^~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:5756:18: warning: no previous prototype for 'rtw_sta_info_get_by_idx' [-Wmissi>
5756 | struct sta_info *rtw_sta_info_get_by_idx(struct sta_priv *pstapriv, const int idx, u8 *asoc_list_num)
|                  ^~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:9792:5: warning: no previous prototype for 'cfg80211_rtw_external_auth' [-Wmis>
9792 | int cfg80211_rtw_external_auth(struct wiphy *wiphy, struct net_device *dev,
|     ^~~~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:9953:32: error: initialization of 'int (*)(struct wiphy *, struct net_device *>
9953 |         .set_monitor_channel = cfg80211_rtw_set_monitor_channel,
|                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:9953:32: note: (near initialization for 'rtw_cfg80211_ops.set_monitor_channel')
make[4]: *** [/usr/lib/modules/6.13.7-zen1-1-zen/build/scripts/Makefile.build:196: os_dep/linux/ioctl_cfg802>
make[3]: *** [/usr/lib/modules/6.13.7-zen1-1-zen/build/Makefile:1987: .] Error 2
make[2]: *** [/usr/lib/modules/6.13.7-zen1-1-zen/build/Makefile:251: __sub-make] Error 2
make[2]: Leaving directory '/var/lib/dkms/rtl8192eu/5.6.4.r302.g2fddecc/build'
make[1]: *** [Makefile:251: __sub-make] Error 2
make[1]: Leaving directory '/usr/lib/modules/6.13.7-zen1-1-zen/build'
make: *** [Makefile:2287: modules] Error 2

# exit code: 2
# elapsed time: 00:00:43

Can I somehow revert the part of upgrade which led to this or what? The correct driver is still at least locally available as I can uninstall it if I want. The device2 is still connected and worked perfectly up to the end of the upgrade, but disappeared right after that when I restarted the system.

2

Please post the complete output, and not just what you think is important. It’s not clear if all dkms packages are failing or just rtl8192eu-dkms.

Are the kernel headers installed? If so, are they intact or broken?

pacman -Qikk linux-zen-headers
6 Likes
3

I’m only on my cell, so I didn’t get a good look at your logs.

Realtek drivers have a habit of breaking regularly.

Things to try:

Reinstall your kernel and headers, and then rebuild your WiFi driver.

Install the LTS kernel and headers.

Reinstall your WiFi driver while booted into the LTS kernel.

Roll your system back to a pre-update snapshot.

Downgrade your driver if it was part of the update.

Downgrade Network Manager if it was part of the update.

Downgrade wpa_supplicant if it was part of the update.

Edit:

I just noticed that you are likely dual booting with Windows.

In case’s like this where your WiFi adapter is no longer displayed in your garuda-inxi, follow this procedure:

Shutdown and unplug your computer from any power source for 5 minutes. Restart your computer and check if your WiFi adapter is now visible.

If not, restart and boot into your bios. Once in your bios utility, perform a factory reset of your bios. Restart, then make any changes required for Linux compatibility in your bios settings.

Also, how exactly did you install your WiFi driver and from which source?

6 Likes
4

Thanks for advice. I decided to roll back with snapshot. At first it went well up to garuda snapshot loader asking to reboot immediately. But then the bootloader was missing and I got to grub 2.06 with minimal editing capabilities. So I had to use the live usb medium to fix the boot loader and now I’m almost back in the square one, wondering if I could somehow upgrade the system without breaking it.

Regarding to the question about how exactly did I install Wifi driver: That is an another thread here https://forum.garudalinux.org/t/realtek-rtl8192eu-wifi-adapter-unstable-no-connection/41016 as at first, I had issues with unstable connection and I followed the guidelines I got from here. The driver is from AUR.

5

Initially, just prior to upgrade failure I had installed dkms driver for a graphic tablet. Could it be a part of the problem - I don’t know but I think it is the only other dkms driver in my system. Unfortunately I was a bit too quick in choosing the solution to restore my computer’s useability and so I guess the pacman.log is lost by now. With the rolled back system the zen header query gives these results ( if it is relevant any more):

╰─λ pacman -Qikk linux-zen-headers
Nimi                     : linux-zen-headers
Versio                   : 6.12.9.zen1-1
Kuvaus                   : Headers and scripts for building modules for the Linux ZEN kernel
Arkkitehtuuri            : x86_64
URL                      : https://github.com/zen-kernel/zen-kernel
Lisenssit                : GPL-2.0-only
Ryhmät                   : Ei ole
Tarjoaa                  : Ei ole
Riippuu paketeista       : pahole
Valinnaiset riippuvuudet : Ei ole
Riippuvuutena paketeille : Ei ole
Valinnainen paketeille   : dkms
Ristiriidassa paketeille : Ei ole
Korvaa paketit           : Ei ole
Koko asennettuna         : 137,65 MiB
Paketoija                : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Luomispäivä              : pe 10. tammikuuta 2025 02.39.35
Asennuspäivä             : ke 15. tammikuuta 2025 14.49.04
Asennuksen syy           : Asennettu itsenäisesti
Asennusskripti           : Ei
Validoitu tavoilla       : Allekirjoitus

linux-zen-headers: yhteensä 20443 tiedostoa, 0 muutettua tiedostoa
6

Lastly. No dual boot here. Instead something was left over when I removed Fedora. That fragment of SSD can’t be reallocated for some unknown reason.

7

Now that you’ve undone everything, it doesn’t help any more. But at least in your loaded snapshot the linux-zen-headers are ok.

According to your log in the start post, the build of the dynamic kernel modules fails.

You have installed several dkms packages:

Maybe only one of them is the cause (for example the digimend-kernel-drivers-dkms package for non-Wacom USB graphics tablets :wink: ), so all the others fail. In this case it is sufficient to remove the defective dkms package and then repeat the system update - after that you can try to reinstall the removed dkms package. But we don’t know, because you didn’t post the complete log.

Post the output of

pacman -Qs dkms

and

dkms status

You can also try to remove all dkms packages, then run a system update and then reinstall the dkms packages one by one. If an error occurs with one of them, then it may be defective.

2 Likes
8 
╰─λ pacman -Qs dkms
local/dkms 3.1.4-1
Dynamic Kernel Modules System
local/garuda-settings-manager 1.0.5-3
Garuda Linux system settings (Manjaro settings manager ported to work with Arch standards and limited to only DKMS drivers)
local/mhwd-db-garuda 2:1.1.6-1.1
MHWD-db backported to Archlinux with additional features and limited to DKMS drivers
local/mhwd-garuda 1.1.4-3
MHWD-db backported to Archlinux with additional features and limited to DKMS drivers
local/rtl8192eu-dkms 5.6.4.r302.g2fddecc-1
Driver for Realtek 8192eu chipset (DKMS)
local/v4l2loopback-dkms 0.13.2-1
v4l2-loopback device – module sources

╰─λ dkms status
rtl8192eu/5.6.4.r302.g2fddecc, 6.12.9-zen1-1-zen, x86_64: installed
v4l2loopback/0.13.2, 6.12.9-zen1-1-zen, x86_64: installed

I’ll propably retry upgrading this system by the next weekend to see if it can be done without digimend drivers. The rest of the dkms packages were in use at least when I successfully upgraded the system last time.
I didn’t consider those loopbacks to be actual drivers..just had no idea what they are but ofcourse some way necessary.

9

Looks good and the digimend-kernel-drivers-dkms package is not installed in the snapshot. Just try to update and see what happens.

v4l2loopback creates virtual video devices and is needed for screen casting and streaming etc (for example for OBS) - if you don’t need it then you can remove it (if you are not sure then just keep it).

2 Likes
10

Now as I’ve retried upgrading, the end result is the same. The entire log cannot be put here due to restriction of 32000 lines. I installed nothing in between these upgrade tries.

11

Inxi right after the upgrade, no rebooting yet so it still knows the wifi device:

╰─λ garuda-inxi -Faz
System:
Kernel: 6.12.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=069e92bc-7096-454e-acbc-99c4eff50739 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: H510M K V2 v: -CF
serial: <superuser required>
Mobo: Gigabyte model: H510M K V2 v: x.x serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends v: F2 date: 06/07/2023
CPU:
Info: model: Intel Core i3-10105F bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 3 microcode: 0xFC
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 800/4400 scaling: driver: intel_pstate
governor: performance cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
7: 800 8: 800 bogomips: 59197
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel DG2 [Arc A310] vendor: ASRock driver: i915 v: kernel
alternate: xe arch: Xe-HPG code: Alchemist process: TSMC n6 (7nm)
built: 2022+ pcie: gen: 1 speed: 2.5 GT/s lanes: 1 ports: active: HDMI-A-1
empty: DP-1,HDMI-A-2 bus-ID: 03:00.0 chip-ID: 8086:56a6 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: HP 24y serial: <filter> built: 2019 res:
mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
size: 528x297mm (20.79x11.69") diag: 606mm (23.9") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.2-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Arc A310 Graphics (DG2)
device-ID: 8086:56a6 memory: 3.86 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 10 device: 0 type: discrete-gpu name: Intel
Arc A310 Graphics (DG2) driver: N/A device-ID: 8086:56a6
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
19.1.7 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel
v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: Intel DG2 Audio vendor: ASRock driver: snd_hda_intel v: kernel
pcie: speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s
bus-ID: 04:00.0 chip-ID: 8086:4f92 class-ID: 0403
API: ALSA v: k6.12.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.1 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 RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 09:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Device-2: TP-Link TL-WN823N v2/v3 [Realtek RTL8192EU] driver: rtl8192eu
type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:3
chip-ID: 2357:0109 class-ID: 0000 serial: <filter>
IF: wlp0s20f0u7 state: up mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Drives:
Local Storage: total: 111.79 GiB used: 90.38 GiB (80.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: A-Data model: SU650 size: 111.79 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 831a scheme: GPT
Partition:
ID-1: / raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 90.36 GiB (81.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 19.3 MiB (6.5%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 90.36 GiB (81.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 90.36 GiB (81.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 111.5 GiB size: 111.5 GiB (100.00%)
used: 90.36 GiB (81.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.53 GiB used: 264 MiB (1.7%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 8
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 41.0 C pch: 50.0 C mobo: 33.0 C
Fan Speeds (rpm): fan-1: 0
Info:
Memory: total: 16 GiB available: 15.53 GiB used: 2.73 GiB (17.5%)
Processes: 278 Power: uptime: 1h 44m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.2 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2014 libs: 577 tools: octopi,pacseek,paru
Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish
v: 4.0.1 running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2024-12-08
Last full system update: 2025-03-31 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:
12

Use Garuda PrivateBin for this and share the generated link here.

How did you update, with garuda-update or with garuda-update -a?

1 Like
13

Here’s the link to the pacman.log, and make.log. (in the same pastebin file)

I guess it is garuda-update as I just clicked the update symbol, which opened terminal-like window asking for password and then began the process.

14

Still haven’t rebooted, but check and merge can’t be done:


✦2 [🔴] × sudo pacdiff
==> pacnew file found for /etc/issue
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] s
==> pacnew file found for /etc/locale.gen
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] m
bsdtar: Error opening archive: Failed to open '/var/cache/pacman/pkg/glibc-2.40+r16+gaa533d58ff-2-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/glibc-2.40+r16+gaa533d58ff-2-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/glibc-2.40+r16+gaa533d58ff-2-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/glibc-2.40+r16+gaa533d58ff-2-x86_64.pkg.tar.zst'
-> Unable to extract the previous version of this file.
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] s
==> pacnew file found for /etc/pacman.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
2 tiedostoa muokattavana
fish: Job 3, 'sudo pacdiff' has stopped


✦3 [🔴] × sudo pacdiff
==> pacnew file found for /etc/issue
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] s
==> pacnew file found for /etc/locale.gen
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] s
==> pacnew file found for /etc/pacman.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] r
poistettiin tiedosto '/etc/pacman.conf.pacnew'
==> pacnew file found for /etc/pacman.d/mirrorlist
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] v
2 tiedostoa muokattavana
fish: Job 4, 'sudo pacdiff' has stopped


✦4 [🔴] × sudo pacdiff
==> pacnew file found for /etc/issue
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] s
==> pacnew file found for /etc/locale.gen
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] s
==> pacnew file found for /etc/pacman.d/mirrorlist
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] m
bsdtar: Error opening archive: Failed to open '/var/cache/pacman/pkg/pacman-mirrorlist-20250101-1-any.pkg.tar.zst
/var/cache/pacman/pkg/pacman-mirrorlist-20250101-1-any.pkg.tar.zst
/var/cache/pacman/pkg/pacman-mirrorlist-20250101-1-any.pkg.tar.zst
/var/cache/pacman/pkg/pacman-mirrorlist-20250101-1-any.pkg.tar.zst'
-> Unable to extract the previous version of this file.
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q]
15

Forget it.

Nope, dkms build fails again. I just tested it myself, rtl8192eu-dkms definitely fails.

The package is marked out of date and does not seem to work since kernel version 6.13.5:

Here is a patch:

No idea if it works. Good luck. :slight_smile:

1 Like
17

I gave you a list of 9 or 10 things you could try, and you provided very minimal feedback to my suggestions. It is very difficult to help someone who leaves forum assistants guessing as to what suggestions they attempted and the result. I would highly suggest providing better indepth responses when forum assistants give you a list of suggestions if you desire to find a solution to your issue.

I no longer use Realtek WiFi adapters, but I will give you my opinion from my time using Realtek WiFi. Some Realtek WiFi models are very solid with few issues, and others are a hot mess. I would put your adapter into the latter category. From my experience providing WiFi support, I would personally say you’d be far better off looking for a reliable replacement.

Realtek drivers often break when updated, (even the most reliable models). If this happens the most likely fix is to downgrade the Realtek WiFi driver to the last working driver version and switch to using the LTS kernel. If you do this, you will need to freeze your WiFi driver package in your pacman.conf until such time as the new Realtek driver has been updated to work with the newest kernels.

Sometimes, (although not that often) the Realtek driver update is not responsible for the wifi breakage. It could possibly be another networking component that is responsible for the breakage. The only way to determine if this is the case, is to selectively downgrade your other networking packages to determine if their recent upgrade caused the breakage.

The most likely suspects to cause WiFi breakages are NetworkManager and wpa_supplicant.

Rather than downgrading wpa_supplicant, I would suggest testing out the iwd package instead. @dr460nf1r3 has recently added this option to the the newest RANI version. You may need to upgrade to rani-git to take advantage of this new RANI feature or you can install iwd manually yourself.

Please provide proper feedback as to what you have attempted. You did not even provide a list of kernels you tested. This info is very important.

1 Like
18

Thanks for directions :slightly_smiling_face: I’ll experiment with that patch later, but for now opt in to choose 6.12.21-1 lts kernel to keep things running.

19

Thanks for very in-depth assistance :slightly_smiling_face: I just began with the kernels as this looks more reliable solution than patching the driver.
So I installed the 6.12.21-1 lts kernel. As rebuilding WiFi driver sounds too complicated process to me, I’m gonna look if the Wifi driver is just fine after booting with lts and if not, then it is time to downgrade parts of the system - especially if there isn’t network connection after that. Temporary cable connection is a possibility too but with such a big hassle that it doesn’t tempt much..
I’ll return to this tomorrow.

20

It is not complicated at all, but in your case the logs seem to indicate there is indeed a problem with building your current driver version.

In that case you can go back to using an older version of your WiFi driver. You likely already have older driver versions stored in your Pacman cache (unless you have cleaned out your cache to regain storage space).

What you need to do is read the Archwiki’s entries regarding downgrading packages. Try switching to the LTS kernel and then downgrade your Realtek WiFi driver. That is your most likely fix from my experiences with Realtek drivers. You can use USB cellular phone tethering if you need a temporary internet connection.

IMO downgrading your system’s other networking components is not what you should be concentrating on. Start with testing alternate kernels and downgrading your current Realtek driver.

3 Likes
21

It seems that with 6.12.21-1 lts kernel no further actions are necessary. To make sure the Realtek driver keeps on working, I’m gonna freeze it in the pacman.conf.

I was planning to clear cache after successful upgrading. For the next couple of days I’ll be monitoring the system through using it to see if it is okay and if so, then clear pacman cache. And if not, then there will be further actions to report here.

Thanks a lot about using your valuable time to help me - and the same to nepti too. Propably I can do something for Garuda linux some day..

1 Like