Package Details: evdi 1.14.8-1

Git Clone URL: https://aur.archlinux.org/evdi.git (read-only, click to copy)
Package Base: evdi
Description: A Linux® kernel module that enables management of multiple screens.
Upstream URL: https://github.com/DisplayLink/evdi
Keywords: display displaylink dp evdi screens
Licenses: GPL
Submitter: PlusMinus
Maintainer: endorfina
Last Packager: endorfina
Votes: 56
Popularity: 1.25
First Submitted: 2016-09-16 07:44 (UTC)
Last Updated: 2024-12-19 19:13 (UTC)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 23 Next › Last »

squalou commented on 2020-12-19 13:26 (UTC) (edited on 2020-12-19 13:26 (UTC) by squalou)

same thing using yay, getting 1.8.0 in the PKGBUILD. Anyone faced with this ?


@@ -0,0 +1,55 @@
+# Maintainer: mwawrzyniak <arch at cmstactical dot net>
+# Contributor: PlusMinus
+
+pkgname=evdi
+pkgver=1.8.0
+pkgrel=1
+pkgdesc="A Linux® kernel module that enables management of multiple screens."
+arch=('i686' 'x86_64')
+url="https://github.com/DisplayLink/evdi"
+license=('GPL')
+groups=()
+depends=(glibc dkms libdrm)
+makedepends=()

==> Proceed with install? [Y/n] n
aborting due to user

mwawrzyniak commented on 2020-12-14 20:41 (UTC)

v1.7.2 has been released which includes officially adopted patches for kernel 5.9 and 5.10.

squalou commented on 2020-11-05 20:25 (UTC)

there's something strange, using yay as aur helper, it tells me it will install 1.7.0-2... but gets PKGBUILD containing 1.8.0

(I stopped the build at that moment)

could it be related to this particular aur helper ? First time I see downgrades like that. (Note : I can manually get the PKGBUILD too, no problem, just asking)

mwawrzyniak commented on 2020-10-18 15:02 (UTC)

I have downgraded this package to v1.7.0 and applied the patch from abucodonosor to let it compile on kernel version 5.9.

Please note sickcodes' comment about removing /etc/udev/rules.d/99-displaylink.rules if you have issues with X crashing.

Once the new versions of DisplayLink are available which use evdi > 1.7.0, I will switch back to keeping this package up-to-date with upstream.

sickcodes commented on 2020-10-15 13:26 (UTC)

Kernel 5.9 fix authored by @abucodonosor https://github.com/abucodonosor

sudo pacman -R evdi-git #used -Rns
yay --getpkgbuild evdi-git
cd evdi-git
sed -i -e s/DisplayLink/sickcodes/g PKGBUILD
makepkg -si
sudo modprobe evdi
sudo systemctl disable displaylink.service
# removing 99-displaylink.rules is necessary for me
# sudo rm sudo /etc/udev/rules.d/99-displaylink.rules
reboot
sudo systemctl start displaylink

His fix works for 1.7.0 too.

https://github.com/DisplayLink/evdi/pull/228

https://github.com/DisplayLink/evdi/pull/227

mwawrzyniak commented on 2020-10-13 12:25 (UTC) (edited on 2020-10-13 12:26 (UTC) by mwawrzyniak)

I have also experienced the X crashing problem. What I noticed is that it only crashes if the DisplayLink/evdi modules are loaded at boot. If I load them after I'm already logged in, there's no crash. I tried adding initial_device_count for the evdi module to try to reserve the DRM devices and that also didn't help.

I've also followed the same guidance that Matze found. I probably spent a few hours trying different combinations of config file changes and reboots.

What works for me currently is as follows for my Dell G3 3590 with Intel 630 iGPU / NVIDIA GeForce GTX 1660Ti is as follows:

Install xorg-server-git. Due to drivers not liking the git xorg-xserver version (IIRC it was NVIDIA that complained), I also had to add a .conf file (/etc/X11/xorg.conf.d/10-displaylink.conf for me) with the following contents:

Section "ServerFlags"
        Option "IgnoreABI" "true"
EndSection

Hope this helps.

Matze commented on 2020-10-12 23:13 (UTC) (edited on 2020-10-12 23:28 (UTC) by Matze)

TLDR; I got a solution, patch your corresponding config file:

/usr/share/X11/xorg.conf.d/20-evdidevice.conf
----------------------------------------------
Section "OutputClass"
    Identifier "DisplayLink"
    MatchDriver "evdi"
    Driver "modesetting"
    Option "PageFlip" "false"
    Option  "AccelMethod" "none"
EndSection

Explanation: After recent updates I experienced similar issues to the previous comment from >square252<. Notably, his solution (downgrading xorg) did work for a while until I eventually lost track of correct version combination in a recent update process.

After some trial and error I found that this is a known problem: https://wiki.archlinux.org/index.php/DisplayLink#DisplayLink_driver_does_not_work_with_Intel_GPUs_after_recent_X_upgrades

https://support.displaylink.com/knowledgebase/articles/1181623

However, knowledge from various source has to be combined correctly to make this work. Therefor you may consider reading up on the two previously posted link, if the patch on top does not work for you. Also, notice, that arch wiki mentiones two different config files: evdidevice.conf and displaylink.conf. I am running only the one I posted above and using multiple config files did not work for me, insted I combined the configurations from multiple sources.

square252 commented on 2020-08-27 11:27 (UTC)

Alright, i dont know what happend, but the recent updates on xorg to v 1.20.9-1 also broke version 1.7. Slowly I start missing my old school dock that basically worked as an pci extension... I downgraded the xorg packages (extra/xorg-server-common, extra/xorg-server and extra/xorg-server-xwayland) to version 1.20.8-1 and everything is working for now. Logs are unclear about the actual problem. The x server just crashes when polling the evdi cards.

morodan commented on 2020-08-14 04:47 (UTC) (edited on 2020-08-14 04:47 (UTC) by morodan)

@ralf_donald: the dmesg warnings shouldn't be the core of the problem; you could check if the module is loaded with lsmod | grep -i evdi. But you are right, this version of evdi doesn't work (for displays) with the actual version of the displaylink driver 5.3.0 and 5.3.1. Downgrade evdi to 1.7.0 could help. See https://github.com/DisplayLink/evdi/issues/216

phraktal commented on 2020-08-10 11:48 (UTC)

Confirming that evdi 1.8.0-1 breaks displaylink, in my case on 5.7.12-arch1-1. Installing 1.7.0-1 fixes displaylink.