Arch Linux User Repository

Package installation without problems - with kernel 5.13.1-3 (manjaro, install displaylink afterwards)

This package seems to use the wrong Linux headers.

From the last line of the install log:

==> Unable to install module evdi/1.9.1 for kernel 5.12.9-arch1-1: Missing kernel modules tree.
➜  ~ uname -a
Linux pedro 5.12.8-arch1-1 #1 SMP PREEMPT Fri, 28 May 2021 15:10:20 +0000 x86_64 GNU/Linux
➜  ~ 

Notice x.y.9 vs x.y.8 in the kernel version. Am I doing something wrong? Any ideas for a workaround? Installing with paru evdi-git.

As max-k wrote before: Installing displaylink: ...

==> Sources are ready.
 -> evdi-git-1.9.1.r3.gb0b3d13-1 already made -- skipping build
 -> Found git repo: github.com/DisplayLink/evdi
 -> evdi-git>=1.9.1.r4.gb0b3d13 not satisfied, flushing install queue

...

evdi-git provides evdi-git-1.9.1.r3.gb0b3d13-1 which breaks displaylink package.

r4 version seems to be gone. Latest available version seems to be 1.9.1.r3.xxxx which breaks displaylink package.

Hi @mtorromeo could you throw a version up on github which better fits your recommendations? This way @severach may be able to just copy and paste the appropriate changes and users (like me) could start using your version directly if @sererach doesn't update this version immediately.

This PKGBUILD needs a lot cleanup:

• Remove the useless set -u/set+u, they are causing issues.

• Do not build the whole module in the build() step. It builds against the running kernel instead of against the installed ones, again causing issues and wasting time for nothing.

• Remove the .install script, it's not a wiki for the package.

The previous version wrote by @ajs124 was mostly fine.

Hmm - linux 5.11.13.arch1-1

Making package: evdi-git 1.9.1.r4.gb0b3d13-1 (Sun 11 Apr 2021 12:32:16 PM MDT)
...
/var/build/evdi-git/src/evdi/module/evdi_encoder.c: In function ‘evdi_encoder_init’:
/var/build/evdi-git/src/evdi/module/evdi_encoder.c:57:11: error: format not a string literal and no format arguments [-Werror=format-security]
   57 |           DRM_MODE_ENCODER_TMDS, dev_name(dev->dev));
      |           ^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
...

This from the new pacman 5.2.2-3, in testing, with /etc/makepkg.conf, CFLAGS, now including "-Werror=format-security".

And then, anyway:

:: removing evdi breaks dependency 'evdi<1.8.0' required by displaylink

And then:

error: failed to commit transaction (conflicting files)
evdi-git: /usr/lib/libevdi.so.0 exists in filesystem
Errors occurred, no packages were upgraded.

So, instead:

sudo vim /etc/makepkg.conf
[ comment-out -Werror=format-security ]
sudo pacman -Rc displaylink
sudo rm -v /usr/lib/libevdi.so.0
yay -S evdi-git
[ dkms runs, and then ]
yay -S displaylink
[ and maybe restore /etc/makepkg.conf ]

Just disable the build of the kernel module completely and let dkms do its magic. You only need to build the library, like in the non-git evdi PKGBUILD.

This issue with the evdi-git PKGBUILD looking in the nonexistent /lib/modules/ directory is pretty silly. Yes, pacman's makepkg did the wrong thing too, providing a useless error message, and yes, the user did the wrong thing too, not rebooting after the kernel upgrade. But the finger-pointing is juvenile. Don't simply blame the user, and don't simply blame pacman and makepkg, when it should be easy enough to fix the PKGBUILD, to first check whether the /lib/modules/ directory exists.

Is it actually necessary to only build the evdi library while the most recent kernel is running?