Package Details: uvesafb-dkms 1.0.4-1

Git Clone URL: (read-only, click to copy)
Package Base: uvesafb-dkms
Description: uvesafb dkms driver and v86d userspace helper for uvesafb that runs x86 code in an emulated environment
Upstream URL:
Licenses: GPL2
Provides: v86d
Replaces: v86d
Submitter: bartus
Maintainer: jghodd
Last Packager: jghodd
Votes: 9
Popularity: 0.000066
First Submitted: 2018-03-13 08:40 (UTC)
Last Updated: 2021-01-02 19:22 (UTC)

Latest Comments

dreieck commented on 2022-05-10 12:31 (UTC)

I suggest to split out v86d from this package and depend on v86d instead (I just have adopted said package). This way v86d and a DKMS recipe for the uvesafb module can be installed seperately, and users can install more fine-grained.

I also strongly suggest to remove v86d from the replaces-entry. Reason:
Users who have the uvesafb module installed by other means (i.e. compiling their own kernel with uvesafb) won't want to install uvesafb-dkms, but still need v86d. Having uvesafb-dkms replacing v86d will pull in uvesafb-dkms automatically on each upgrade, which is not wanted in that scenario.

And I suggest to add UVESAFB-MODULE to the provides and conflicts arrays.

I also strongly suggest to move the uvesafb.conf into /etc/modprobe.d/ and add etc/modprobe.d/uvesafb.conf to the backup array, since it is a configuration file which the user should alter to suit the local setup. And I suggest to comment out the example line, since it will mess up displays that do not support that mode. Leave the user to set their values.

Furthermore, I suggest to move the mkinitcpio hooks out to an extra package (I have just created one: mkinitcpio-uvesafb) where this package can optdepends on, in order to have them available even if the user has the uvesafb module provided by another source (e.g. self compiled kernel). Further modularisation of packages.

I made a package uvesafb-dkms-git which reflects those changes; feel free to get inspired by it.

Also, the source protocol needs to be updated from git:// to git+https:// due to changes at

Thanks for maintaining!

andreas_baumann commented on 2022-04-02 07:50 (UTC)

change 'source' to:

source=("uvesafb-dkms::git+$pkgname-$pkgver" "v86d::git+$_v86d-$_v86dver" v86d_install v86d_hook 'dkms.conf' modprobe.uvesafb)

The it builds fine.

Daerun commented on 2022-03-16 19:20 (UTC)

I'm getting this error

The unauthenticated git protocol on port 9418 is no longer supported. Please see for more information.

bartus commented on 2021-10-30 12:30 (UTC) (edited on 2021-10-30 12:43 (UTC) by bartus)

@schenedan: looks like something on your machine is already using this io range, check out sudo cat /proc/ioports and look for region overlapping with 03c0-03df

On my system (i7-4790K,nv-grx980) it looks like this:

$sudo cat /proc/ioports
 02a0-02af : pnp 00:04
 03c0-03df : vesafb
 03f8-03ff : serial

Kernel should emit message containing conflict if found any:

Check journal -k for Unadressable device waring.

schnedan commented on 2021-10-29 21:56 (UTC)

currently I get sudo dmesg | fgrep fail 579:[ 2.200245] uvesafb: module verification failed: signature and/or required key missing - tainting kernel 584:[ 2.377474] uvesafb: request region 0x3c0-0x3e0 failed 585:[ 2.377481] uvesafb: probe of uvesafb.0 failed with error -5

just rebuild/reinstalled a few minutes ago.

Distro: Arch Linux [x86_64] Kernel: Linux 5.14.14-arch1-1 CPU: 4 x Intel(R) Atom(TM) CPU D2700 @ 2.13GHz GPU: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09)

willspoke commented on 2020-12-31 17:20 (UTC) (edited on 2021-01-02 21:02 (UTC) by willspoke)

having an error with normal kernel (latest), with same log output as github issue link

edit: link above has been updated with a temporary fix by jghodd

librewish commented on 2020-05-05 15:23 (UTC) (edited on 2020-05-05 15:24 (UTC) by librewish)

@jghodd depend on v86d instead of providing it. i have removed uvesafb-dkms dependancy from the v86d package.

firekage commented on 2020-03-15 16:25 (UTC) (edited on 2020-03-16 16:31 (UTC) by firekage)

Changing only version number fix problem with currenct kernel? If i modify it while being created via aur helper it will solve problem? Edit: yes, it did in facet. Build correctly.

yolf commented on 2019-12-29 23:29 (UTC)

for updating to version 1.0.2, you should replace "pkgver=1.0.1" with "pkgver=1.0.2" in PKGBUILD

BELiAL commented on 2019-12-26 19:41 (UTC)

this version does not compile against current kernel, you should upgrade to release 1.0.2

dreieck commented on 2019-08-05 09:57 (UTC)

Maybe best idea is to depend on v86d and not provide v86d by yourself?

x3ro commented on 2018-07-18 10:01 (UTC)

I got the following error when upgrading my AUR packages:

error: failed to commit transaction (conflicting files) v86d: /usr/bin/v86d exists in filesystem (owned by uvesafb-dkms) v86d: /usr/lib/initcpio/hooks/v86d exists in filesystem (owned by uvesafb-dkms) v86d: /usr/lib/initcpio/install/v86d exists in filesystem (owned by uvesafb-dkms) v86d: /usr/lib/modprobe.d/uvesafb.conf exists in filesystem (owned by uvesafb-dkms) Errors occurred, no packages were upgraded.

The problem was that I had v86d installed.

v86d has a dependency on uvesafb-dkms but uvesafb-dkms (now?) also provides v86d. (I assume that uvesafb-dkms changed recently to also provide v86d.)

Uninstalling v86d and upgrading uvesafb-dkms seems to have fixed the problem. At least the v86d command is still available after that.

rubystallion commented on 2018-05-10 05:55 (UTC)

I'm getting the following error: loading out-of-tree module taints kernel. Getting VBE info block failed (eax=0x4f00, err=1) ube_init() failed with -22 probe of uvesafb.0 failed with error -22

I installed this package, did the checks in the wiki and ran mkinitcpio without any warnings. Graphics driver is i915 for Intel onboard graphics and nouveau for NVIDIA GP107M.

eschwartz commented on 2018-04-17 23:04 (UTC)

The real question here, is why does this have a versioned dependency on dkms?

karl_gerh commented on 2018-04-01 20:02 (UTC)

Thank you very much!

jghodd commented on 2018-03-31 21:07 (UTC) (edited on 2018-03-31 21:09 (UTC) by jghodd)

@karl_gerh - yeah. tested it. the dkms-sorted maintainer needs to change conflicts to replaces for dkms in his PKGBUILD. so actually, dkms-sorted doesn;t play nicely with uvesafb-dkms, or any other package with a dkms dependency for that matter. ;-)

jghodd commented on 2018-03-31 19:22 (UTC) (edited on 2018-03-31 19:28 (UTC) by jghodd)

@karl_gerh - dkms-sorted both provides and conflicts with dkms from the official repositories. honestly, i don;t see any way around this. i have to provide support for the official version. i'll look into it and see if i have any options here, but so far i'm not seeing any syntax for an OR operation under depends (e.g. dkms OR dkms-sorted). i have to depend on dkms and dkms-sorted is supposed to provide dkms. the answer may be that the dkms-sorted maintainer should change his package so that instead of conflicting with dkms, it just replaces dkms.

replaces=('dkms') vs. conflicts=('dkms')

you can try this out yourself by downloaded the dkms-sorted snapshot, modify the PKGBUILD, substituting conflicts with replaces, build a new copy of dkms-sorted, install it and try it out.

karl_gerh commented on 2018-03-31 18:40 (UTC) (edited on 2018-03-31 18:41 (UTC) by karl_gerh)


uvesafb-dkms doesn't seem to play along nicely with dkms-sorted (which I use for zfs). Is there a way to make this work?

:: Building uvesafb-dkms package(s)... ==> Making package: uvesafb-dkms 1.0.0-2 (Sam Mär 31 20:37:42 CEST 2018) ==> Checking runtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for conflicting packages... :: dkms and dkms-sorted are in conflict. Remove dkms-sorted? [y/N] error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: dkms and dkms-sorted are in conflict ==> ERROR: 'pacman' failed to install missing dependencies. :: failed to build uvesafb-dkms package(s)