You are not logged in.
Pages: 1
After doing `sudo pacman -Syu`, the following error pops up (i do `sudo pacman -S linux-headers` to reproduce):
(3/3) Install DKMS modules
==> dkms install --no-depmod uvesafb-dkms/1.0.4+r10.20210102.cada654 -k 6.19.10-arch1-1
Deprecated feature: CLEAN (/var/lib/dkms/uvesafb-dkms/1.0.4+r10.20210102.cada654/source/dkms.conf)
Error! Bad return status for module build on kernel: 6.19.10-arch1-1 (x86_64)
Consult /var/lib/dkms/uvesafb-dkms/1.0.4+r10.20210102.cada654/build/make.log for more information.
==> WARNING: `dkms install --no-depmod uvesafb-dkms/1.0.4+r10.20210102.cada654 -k 6.19.10-arch1-1' exited 10The log file reads the following:
DKMS (dkms-3.3.0) make.log for uvesafb-dkms/1.0.4+r10.20210102.cada654 for kernel 6.19.10-arch1-1 (x86_64)
Tue Mar 31 11:19:47 PM MSK 2026
Building module(s)
# command: 'make' BASEDIR=/usr/lib/modules/6.19.10-arch1-1 modules
make -C src/ modules
make[1]: Entering directory '/var/lib/dkms/uvesafb-dkms/1.0.4+r10.20210102.cada654/build/src'
make -C /usr/lib/modules/6.19.10-arch1-1/build M=/var/lib/dkms/uvesafb-dkms/1.0.4+r10.20210102.cada654/build/src modules
make[2]: Entering directory '/usr/lib/modules/6.19.10-arch1-1/build'
make[3]: Entering directory '/var/lib/dkms/uvesafb-dkms/1.0.4+r10.20210102.cada654/build/src'
CC [M] uvesafb.o
uvesafb.c: In function ‘uvesafb_exec’:
uvesafb.c:323:18: error: implicit declaration of function ‘prandom_u32’; did you mean ‘get_random_u32’? [-Wimplicit-function-declaration]
323 | m->ack = prandom_u32();
| ^~~~~~~~~~~
| get_random_u32
uvesafb.c: In function ‘uvesafb_vbe_getmonspecs’:
uvesafb.c:892:50: error: ‘fb_vesa_modes’ undeclared (first use in this function); did you mean ‘vesa_modes’?
892 | &fb_vesa_modes[i], info))
| ^~~~~~~~~~~~~
| vesa_modes
uvesafb.c:892:50: note: each undeclared identifier is reported only once for each function it appears in
uvesafb.c: In function ‘uvesafb_init_info’:
uvesafb.c:1661:23: error: ‘FBINFO_FLAG_DEFAULT’ undeclared (first use in this function); did you mean ‘FAULT_FLAG_DEFAULT’?
1661 | info->flags = FBINFO_FLAG_DEFAULT |
| ^~~~~~~~~~~~~~~~~~~
| FAULT_FLAG_DEFAULT
uvesafb.c: At top level:
uvesafb.c:1953:19: error: initialization of ‘void (*)(struct platform_device *)’ from incompatible pointer type ‘int (*)(struct platform_device *)’ [-Wincompatible-pointer-types]
1953 | .remove = uvesafb_remove,
| ^~~~~~~~~~~~~~
uvesafb.c:1953:19: note: (near initialization for ‘uvesafb_driver.remove’)
uvesafb.c:1926:12: note: ‘uvesafb_remove’ declared here
1926 | static int uvesafb_remove(struct platform_device *dev)
| ^~~~~~~~~~~~~~
make[5]: *** [/usr/lib/modules/6.19.10-arch1-1/build/scripts/Makefile.build:289: uvesafb.o] Error 1
make[4]: *** [/usr/lib/modules/6.19.10-arch1-1/build/Makefile:2065: .] Error 2
make[3]: *** [/usr/lib/modules/6.19.10-arch1-1/build/Makefile:248: __sub-make] Error 2
make[3]: Leaving directory '/var/lib/dkms/uvesafb-dkms/1.0.4+r10.20210102.cada654/build/src'
make[2]: *** [Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/usr/lib/modules/6.19.10-arch1-1/build'
make[1]: *** [Makefile:18: modules] Error 2
make[1]: Leaving directory '/var/lib/dkms/uvesafb-dkms/1.0.4+r10.20210102.cada654/build/src'
make: *** [Makefile:4: modules] Error 2
# exit code: 2
# elapsed time: 00:00:01
----------------------------------------------------------------I can't quite make anything of it and looking around the internet for a solution, nothing seems to work. During the upgrade there was also an issue with Quickshell, which I rebuilt as the issue said to, I don't quite know what to do to reproduce it now so I can't check whether the problem is fixed and whether it is related, but I thought I'd mention it.
`mkinitcpio -P` generates the initramfs with no problem. I have not rebooted yet following the update because I am scared. Does anyone know whether this is dangerous and how to fix it?
Edit: I don't know if this is visible to anyone because apparently I am banned? Maybe? But I just uninstalled uvesafb-dkms and there is no issue now.
Last edited by simon-rattus (2026-04-02 17:28:25)
Offline
prandom_u32's removal should be fixed by https://github.com/jghodd/uvesafb-dkms/pull/3. As the removal was part of 6.1 release of Linux the build failure should not be a new issue. Is your system currently using the uvesafb mode?
Last edited by loqs (2026-03-31 21:07:06)
Offline
prandom_u32's removal should be fixed by https://github.com/jghodd/uvesafb-dkms/pull/3. As the removal was part of 6.1 release of Linux the build failure should not be a new issue. Is your system currently using the uvesafb mode?
I am not entirely aware if the module is used, I don't really understand what it is and what it does. I have not heard of it before, and looking it up doesn't help that much.
Offline
Was uvesafb-dkms installed from a pacman package of the same name which may have been in AUR in years past? You can see if the module is currently loaded by checking lsmod's output.
Offline
Was uvesafb-dkms installed from a pacman package of the same name which may have been in AUR in years past? You can see if the module is currently loaded by checking lsmod's output.
I don't know when it was installed, but I have only been using Arch for around a year, and I think I didn't install it through AUR (I am trying to be careful with that). lsmod doesn't show it as loaded.
Offline
You could try looking through /var/log/pacman.log as DKMS would run every time the linux-header package is updated provided the dkms package was installed. linux 6.1.1.arch1-1 was packaged in December 2022 and linux-lts 6.1.12 in February 2023. If the installation is under three years old then uvesafb-dkms will have never worked so it will be safe to reboot and remove as it serves no purpose.
Offline
Pages: 1