> Creating symlink /var/lib/dkms/evdi/1.6.2/source -> > $ less /var/log/displaylink/displaylink.log > For me it fails because it can't find my kernel headers: > /sbin/dkms install evdi/1.6.2 > /var/log/displaylink/displaylink.log 2>&1 > /usr/bin/systemctl -q is-enabled rvice || /usr/bin/systemctl enable > /usr/bin/systemctl -q is-active rvice & /usr/bin/systemctl > # The displaylink service may crash as dkms rebuilds the module

> It looks like the rpm uses a post install script to start the Displaylink I've had a few hiccups which I've detailed > use a USB-C docking station (needs Displaylink to use monitors through USB-C

> I'm trying to get Displaylink drivers working on my P52s ThinkPad so I can No package kernel-devel-4.19.86_64 available. You can remove cached packages by executing 'dnf clean packages'. The downloaded packages were saved in cache until the next successful X86_64 1000:4.19. qubes-dom0-current-testing 13 MĭNF will only download packages for the transaction. Qubes Templates repository 2.3 kB/s | 12 kB 00:05 Qubes Dom0 Repository (updates-testing) 11 MB/s | 23 MB 00:02ĭetermining the fastest mirror (15 hosts). Qubes Dom0 Repository (updates) 3.4 MB/s | 12 MB 00:03 Using sys-firewall as UpdateVM to download updates for Dom0 this may take someįedora 25 - x86_64 - Updates 3.3 MB/s | 24 MB 00:07įedora 25 - x86_64 3.8 MB/s | 50 MB 00:13 Looks like the update VM downloading the package but then not passing the Looks like that's in qubes-dom0-current-testing. Packages for the version of the kernel that you are using. Answer is much more simple than I thought - you install the kernel-devel

Proton email 3.8 download