View Single Post
Old 03-02-2025, 02:01 PM   #1
schmidi314
Junior Member
 
Join Date: Mar 2025
Posts: 1
Default Displaylink docking station on Gentoo

Hello all,

again a Gentoo issue. One that doesn't show up in the threads yet, I think. But basically I can't get it up and running.


So, I managed to compile the evdi library and kernel module with the ubuntu displaylink installer (6.1.0-17). I can modprobe evdi and it shows up in system log. But somehow something is still missing. It would be great to get some help as I cannot read the DisplayLinkManager logs.

So, here's what I see: Upon loading evdi (modprobe evdi) I get this

PHP Code:
Mar 02 13:47:05 tuxedo kernelevdi: [IInitialising logging on level 4
Mar 02 13
:47:05 tuxedo kernelevdi: [IAtomic driveryes
Mar 02 13
:47:05 tuxedo kernelevdi: [IIncreasing device count to 4
Mar 02 13
:47:05 tuxedo kernelevdi: [I] (card0Opened by Task 7934 (modprobeof process 7934 (modprobe)
Mar 02 13:47:05 tuxedo kernelevdi evdi.0: [drmCannot find any crtc or sizes
Mar 02 13
:47:05 tuxedo kernel: [drmInitialized evdi 1.14.7 for evdi.0 on minor 0
Mar 02 13
:47:05 tuxedo kernelevdi: [IEvdi platform_device create
Mar 02 13
:47:05 tuxedo kernelevdi: [I] (card1Opened by Task 7934 (modprobeof process 7934 (modprobe)
Mar 02 13:47:05 tuxedo kernelevdi evdi.1: [drmCannot find any crtc or sizes
Mar 02 13
:47:05 tuxedo kernel: [drmInitialized evdi 1.14.7 for evdi.1 on minor 1
Mar 02 13
:47:05 tuxedo kernelevdi: [IEvdi platform_device create
Mar 02 13
:47:05 tuxedo kernelevdi: [I] (card2Opened by Task 7934 (modprobeof process 7934 (modprobe)
Mar 02 13:47:05 tuxedo kernelevdi evdi.2: [drmCannot find any crtc or sizes
Mar 02 13
:47:05 tuxedo kernel: [drmInitialized evdi 1.14.7 for evdi.2 on minor 2
Mar 02 13
:47:05 tuxedo kernelevdi: [IEvdi platform_device create
Mar 02 13
:47:05 tuxedo kernelevdi: [I] (card3Opened by Task 7934 (modprobeof process 7934 (modprobe)
Mar 02 13:47:05 tuxedo kernelevdi evdi.3: [drmCannot find any crtc or sizes
Mar 02 13
:47:05 tuxedo kernel: [drmInitialized evdi 1.14.7 for evdi.3 on minor 3
Mar 02 13
:47:05 tuxedo kernelevdi: [IEvdi platform_device create 
I can also see the corresponding files in `/sys/devices/evdi` as long as evdi is loaded (after modprobe -r evdi, they vanish as expected).

Later on in the Xorg part of the log I see this

PHP Code:
Mar 02 13:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIconfig/udevremoving GPU device /sys/devices/platform/evdi.3/drm/card3 /dev/dri/card3
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIconfig/udevAdding drm device (/dev/dri/card3)
Mar 02 13:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIxfree86Adding drm device (/dev/dri/card3)
Mar 02 13:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIPlatform probe for /sys/devices/platform/evdi.3/drm/card3
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (EEsystemd-logindfailed to take device /dev/dri/card3Invalid argument
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIconfig/udevremoving GPU device /sys/devices/platform/evdi.1/drm/card1 /dev/dri/card1
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIconfig/udevAdding drm device (/dev/dri/card1)
Mar 02 13:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIxfree86Adding drm device (/dev/dri/card1)
Mar 02 13:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIPlatform probe for /sys/devices/platform/evdi.1/drm/card1
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (EEsystemd-logindfailed to take device /dev/dri/card1Invalid argument
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIconfig/udevremoving GPU device /sys/devices/platform/evdi.2/drm/card2 /dev/dri/card2
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIconfig/udevAdding drm device (/dev/dri/card2)
Mar 02 13:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIxfree86Adding drm device (/dev/dri/card2)
Mar 02 13:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (IIPlatform probe for /sys/devices/platform/evdi.2/drm/card2
Mar 02 13
:47:05 tuxedo /usr/libexec/gdm-x-session[1275]: (EEsystemd-logindfailed to take device /dev/dri/card2Invalid argument 
And this is where I fail. What does this "failed to take device /dev/dri/cardX: Invalid argument" mean?

I'd really appreciate some help!

Thanks,
Manuel
schmidi314 is offline   Reply With Quote