Package Details: uvesafb-dkms 1.0.4-1

Git Clone URL: https://aur.archlinux.org/uvesafb-dkms.git (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: https://github.com/jghodd/uvesafb-dkms
Licenses: GPL2
Provides: v86d
Replaces: v86d
Submitter: bartus
Maintainer: None
Last Packager: jghodd
Votes: 9
Popularity: 0.000000
First Submitted: 2018-03-13 08:40 (UTC)
Last Updated: 2021-01-02 19:22 (UTC)

Latest Comments

1 2 3 Next › Last »

jghodd commented on 2023-02-06 22:51 (UTC) (edited on 2023-02-06 22:54 (UTC) by jghodd)

@dreieck - uvesafb is now being provided as part of the 6.1.9 kernel. we only need v86d and a hook. the current build issue comes down to 2 things - the first is the new git+https addressing protocol as pointed out below by Andreas Baumann, and the second is in uvesafb.c with the use of prandom_u32 which now must be changed to get_random_u32. but that's irrelevant, given that the module is now provided.

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 github.com.

Thanks for maintaining!

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

change 'source' to:

source=("uvesafb-dkms::git+https://github.com/jghodd/uvesafb-dkms.git#tag=$pkgname-$pkgver" "v86d::git+https://github.com/mjanusz/v86d.git#tag=$_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 https://github.blog/2021-09-01-improving-git-protocol-security-github/ 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:

https://github.com/torvalds/linux/blob/c12a29ed9094b4b9cde8965c12850460b9a79d7c/kernel/resource.c#L1188-L1191

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)