EVDI kernel 5.11/5.12 support #275

displaylink-emajewsk · 2021-04-02T07:56:45Z

Hello, everyone. Again, sorry for the wait.

Current evdi has been pushed to Github. It is however, NOT a complete driver and will require new DLM in order to work correctly. It should be up on our website in a couple of days (it may vary because of the holidays).

I will update this thread when it goes up.

I'll also be closely monitoring our Github, so if you'll be having any issues with the new kernels, I hope we'll be able to resolve them in a more timely manner. 😇

Thank you for your patience.

joren485 · 2021-04-02T09:38:51Z

Thanks for the update!

I noticed that the changes have been pushed to the devel branch, but not the 1.7.x branch. Does this mean that the new DisplayLink Manager version will work with evdi 1.9.x?

mfs12 · 2021-04-04T15:01:53Z

does this update bring better support/performance for AMD Ryzen 4650?

echosa · 2021-04-05T15:04:16Z

It should be up on our website in a couple of days (it may vary because of the holidays).

Looking forward to this! I was wondering why my SideTrak stopped working, though I assumed it was a system update. Kernel update makes perfect sense. Hopefully the upcoming update will fix it!

jteib · 2021-04-06T03:03:56Z

Can't wait for the update! For now I just set my default kernel in grubby to 5.10.23

bnavigator · 2021-04-06T09:32:30Z

Sounds great!

DisplayLink 5.4 is on the website, but we still need a evdi release, which supports 5.11/5.12. The 1.9.0 and 1.9.1 tagged versions are too old and so is the current commit in the master branch.

sickcodes · 2021-04-06T12:44:08Z

@bnavigator are you using Wayland or X? It's not working for me on Xorg unfortunately, 5.11, testing 5.12 though

EDIT: I see the package you're referring to on the site. Let me try it with the DL pkgbuild

Nillu · 2021-04-06T12:48:16Z

I hope that it solve my problems with evdi :)
i'm on pop'os 20.04 and update to kernel 5.11 without know that issue .... I've turn on 1 output screen instead of 3 😢
Thanks for your support !

bnavigator · 2021-04-06T12:50:24Z

@bnavigator are you using Wayland or X? It's not working for me on Xorg unfortunately, 5.11, testing 5.12 though

X11 on Archlinux with my displaylink package from AUR and evdi-git from AUR. Kernel 5.11.11-arch1-1

moodyhunter · 2021-04-06T13:12:03Z

It's worth noting that on Archlinux I'm affected by #274 , downgrading mesa may resolve the problem.

bnavigator · 2021-04-06T13:44:25Z

It's also worth noting that DisplayLink 5.4.0-55.153 comes with a bundled evdi.tar.gz from 0f1ad21

Just found out and I am considering changing the AUR and openSUSE package to not require a separate evdi at all...

joren485 · 2021-04-06T13:53:37Z

Just found out and I am considering changing the AUR and openSUSE package to not require a separate evdi at all...

As DLM and evdi are two separate projects, with separate releases and separate versions, I would prefer keeping them as separate AUR packages. In my opinion, that is the least confusing w.r.t. what is actually installed on your system.

bnavigator · 2021-04-06T13:56:28Z

It is totally confusing with all the different old and recent AUR packages for evdi. Some work, some don't and it's always a new situation for every new release (or lack of it).

joren485 · 2021-04-06T14:03:48Z

It is totally confusing with all the different old and recent AUR packages for evdi. Some work, some don't and it's always a new situation for every new release (or lack of it).

That's a very good point. However, all those different AUR packages are necessary because every new kernel update breaks evdi in someway and evdi requires a patch. As DisplayLink does not add these patches into the DLM releases (as far as I am aware), you would need some other way to patch the bundled evdi. How would you deal with such a scenario without a separate evdi package that can be patched and updated regardless of DLM releases?

bnavigator · 2021-04-06T14:09:01Z

How would you deal with such a scenario without a separate evdi package that can be patched and updated regardless of DLM releases?

Add a patchfile and patch inside the PKGBUILD. This would avoid what happened with DisplayLink 5.3 and evdi >=1.8. People were trying to use this combination very often, which did of course not work.

nckrse · 2021-04-06T14:43:54Z

After installing current dev (f703808) and DLM 5.4, I can finally detect displays :) But when trying to assign the display, I get the below in my Xorg log. I will wait for new evdi release or devel updates as @bnavigator stated above. Thanks

[  1247.149] (II) modeset(0): Allocate new frame buffer 3840x1080 stride
[  1247.245] failed to add fb -22
[  1247.245] (EE) modeset(G0): failed to set mode: Invalid argument
[  1247.455] (II) modeset(0): Allocate new frame buffer 1920x1080 stride
[  1247.697] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1247.697] (II) modeset(0): Printing DDC gathered Modelines:
[  1247.697] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1247.821] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1247.821] (II) modeset(0): Printing DDC gathered Modelines:
[  1247.821] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1247.955] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1247.955] (II) modeset(0): Printing DDC gathered Modelines:
[  1247.955] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1248.080] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1248.081] (II) modeset(0): Printing DDC gathered Modelines:
[  1248.081] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1248.428] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1248.428] (II) modeset(0): Printing DDC gathered Modelines:
[  1248.428] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1248.552] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1248.553] (II) modeset(0): Printing DDC gathered Modelines:
[  1248.553] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)

bnavigator · 2021-04-06T14:47:48Z

@nckrse did you try to inspect reported modes and assing a valid mode with xrandr? Did 3840x1080 work with DL 5.3 and evdi 1.7?

bnavigator · 2021-04-06T14:49:42Z

After installing current dev (f703808)

That's not a commit in current dev

echosa · 2021-04-06T15:58:32Z

Perhaps someone can help me out. Using Pop!_OS 20.10 with GNOME 3.38.3 on Xorg. I installed the new Ubuntu driver version 5.4 from the DisplayLink site and rebooted. The service is running, seemingly without error:

$ systemctl status displaylink-driver.service
● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: active (running) since Tue 2021-04-06 10:50:53 CDT; 3min 21s ago
    Process: 1275 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1  | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=0/SUCCESS)
   Main PID: 1278 (DisplayLinkMana)
      Tasks: 27 (limit: 38060)
     Memory: 20.5M
     CGroup: /system.slice/displaylink-driver.service
             └─1278 /opt/displaylink/DisplayLinkManager

Apr 06 10:50:53 caelum systemd[1]: Starting DisplayLink Driver Service...
Apr 06 10:50:53 caelum systemd[1]: Started DisplayLink Driver Service.

I have evdi 1.9.1 installed from this PPA because the regular repos only have 1.7:

$ apt search evdi
Sorting... Done
Full Text Search... Done
evdi-dkms/groovy,groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 all [installed]
  Extensible Virtual Display Interface driver kernel module

libevdi0/groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 amd64 [installed,automatic]
  Extensible Virtual Display Interface driver client library

GNOME detects that there is a second monitor plugged in:

However, it won't let me switch away from "single display". If I select "mirror" or "join displays" and click apply, it automatically goes back to "single display".

nckrse · 2021-04-06T16:13:55Z

After installing current dev (f703808)

That's not a commit in current dev

@bnavigator , sorry, i was trying separate forks a few days ago. I re-installed on dev b0b3d13 and run into the same issue. I have tried different xrandr modes also. My issue is the same exact as @echosa , but I had tailed the logs during doing so.

bnavigator · 2021-04-06T16:31:05Z

You should move your questions to the displaylink support forum. This is out of scope for "EVDI kernel 5.11/5.12 support"

Nillu · 2021-04-07T09:43:06Z

Perhaps someone can help me out. Using Pop!_OS 20.10 with GNOME 3.38.3 on Xorg. I installed the new Ubuntu driver version 5.4 from the DisplayLink site and rebooted. The service is running, seemingly without error:
$ systemctl status displaylink-driver.service
● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: active (running) since Tue 2021-04-06 10:50:53 CDT; 3min 21s ago
    Process: 1275 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1  | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=0/SUCCESS)
   Main PID: 1278 (DisplayLinkMana)
      Tasks: 27 (limit: 38060)
     Memory: 20.5M
     CGroup: /system.slice/displaylink-driver.service
             └─1278 /opt/displaylink/DisplayLinkManager

Apr 06 10:50:53 caelum systemd[1]: Starting DisplayLink Driver Service...
Apr 06 10:50:53 caelum systemd[1]: Started DisplayLink Driver Service.
I have evdi 1.9.1 installed from this PPA because the regular repos only have 1.7:
$ apt search evdi
Sorting... Done
Full Text Search... Done
evdi-dkms/groovy,groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 all [installed]
  Extensible Virtual Display Interface driver kernel module

libevdi0/groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 amd64 [installed,automatic]
  Extensible Virtual Display Interface driver client library
GNOME detects that there is a second monitor plugged in:

However, it won't let me switch away from "single display". If I select "mirror" or "join displays" and click apply, it automatically goes back to "single display".

Same issue for me on my external monitors, detected but no way to display and get it working with DLM 5.4, think it's mainly mesa 21 problems... Downgrading on popos is very dangerous but if it's the only way ... i will try as soon as i'll have time and get back here to give you feedback.

AlFontal · 2021-04-07T10:32:57Z

@Nillu I find myself in the same situation, Pop!_OS 20.04 and kernel 5.11.0-7612-generic. After upgrading kernel, one of my screens became completely useless.

I was thinking of downgrading kernel but I don't want to break my install at this point as it is my work PC. If you are able to get it working let me know! :)

bnavigator · 2021-04-07T10:54:47Z

I have evdi 1.9.1 installed from this PPA because the regular repos only have 1.7:

Note that the PPA says "evdi 1.9.1+master". master does not have the fixes for kernel >=5.11.

DisplayLink 2.4 comes with evdi bundled. Did you try to uninstall the PPA evdi and reinstall DisplayLink from the official installer?

echosa · 2021-04-07T19:03:34Z

I know it was recommended to go to the displaylink support, but when I contacted them, they only support Ubuntu. So, to update here since it was mentioned: I used Timeshift to rollback to before kernel 5.11. Then I used the previous driver installer to completely remove the old version of the driver and its evdi. (I was having issues with not being able to remove evdi completely). Once that was uninstalled and all clean again, I upgraded back to 5.11 again. I then installed the latest displaylink driver that was just released, including its bundled evdi, without having evdi installed via apt (whether PPA or not). Same issue. Everything seems fine. Service is running. Display is detected by GNOME. Still can't get it to actually display.

Just wanted to update, since "Did you try to uninstall the PPA evdi and reinstall DisplayLink from the official installer?" didn't work.

bnavigator · 2021-04-07T21:42:41Z

When you say PPA, I suspect Pop!_OS is close enough to Ubuntu. The "official" support might not be willing to help, but the forums are probably a better place to discuss this issue with the DisplayLink Manager than the GitHub issue tracker for evdi:
https://www.displaylink.org/forum/forumdisplay.php?f=29

echosa · 2021-04-07T21:48:19Z

Thank you for that link. I've reached back out to the official support, but having access to that forums is nice too. I'll avoid cluttering this GitHub issue anymore.

displaylink-emajewsk · 2021-04-08T07:17:44Z

Just to reiterate, DLM 5.4 has since been released. 😇

It works with the current devel, at last.

No updates for AMD-specific bugs yet.

We're aware of the issues on Pop!_OS and we'll be promptly investigating what has happened over there. 😉

echosa · 2021-04-08T14:55:09Z

Thanks, @displaylink-emajewsk! Regarding:

We're aware of the issues on Pop!_OS and we'll be promptly investigating what has happened over there. wink

Is there somewhere we can track progress of that other than just watching for messages here?

elguero · 2021-04-08T16:13:57Z

@displaylink-emajewsk Thank you for the updates. I can confirm that it is working on Fedora 33.

Question: Are there any plans to re-tag 1.9.1 from the current devel branch?

This would be helpful for packaging. Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm

Thanks again for keeping us updated.

devujan · 2021-04-09T19:51:42Z

I try to get 5.4 in running on devuan chimaera
I get EVDI compiled and loaded as dkms on the 5.10.0-5-amd64 kernel.

But inserting fails with:

dmesg | grep evdi

[ 85.702974] evdi: [I] Initialising logging on level 5
[ 85.702975] evdi: [I] Atomic driver: yes
[ 85.703024] evdi: [D] evdi_platform_add_devices:158 Increasing device count to 4
[ 85.703073] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p0000000032537284
[ 85.703083] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 85.703088] evdi evdi.0: [drm] Cannot find any crtc or sizes
[ 85.703097] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 85.703199] [drm] Initialized evdi 1.9.1 20210126 for evdi.0 on minor 1
[ 85.703205] evdi: [I] Evdi platform_device create
[ 85.703235] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000a7cad1e5
[ 85.703240] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 85.703242] evdi evdi.1: [drm] Cannot find any crtc or sizes
[ 85.703245] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 85.703474] [drm] Initialized evdi 1.9.1 20210126 for evdi.1 on minor 2
[ 85.703480] evdi: [I] Evdi platform_device create
[ 85.703507] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p0000000043467b57
[ 85.703510] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 85.703512] evdi evdi.2: [drm] Cannot find any crtc or sizes
[ 85.703515] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 85.703681] [drm] Initialized evdi 1.9.1 20210126 for evdi.2 on minor 3
[ 85.703689] evdi: [I] Evdi platform_device create
[ 85.703728] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000c48faaa7
[ 85.703736] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 85.703740] evdi evdi.3: [drm] Cannot find any crtc or sizes
[ 85.703747] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 85.705042] [drm] Initialized evdi 1.9.1 20210126 for evdi.3 on minor 4
[ 85.725138] evdi: [I] Evdi platform_device create
[ 85.801299] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.801972] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[ 85.802641] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.802642] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[ 85.802646] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.802646] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[ 85.802651] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.804697] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[ 85.834554] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.836303] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 85.838188] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.840605] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 85.842700] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.843966] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 85.844761] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.845557] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 85.894930] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.894935] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 85.894961] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.894963] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 85.894979] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.894980] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 85.894993] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[ 85.894994] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[ 86.067434] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.067519] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[ 86.067521] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[ 86.067534] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.067820] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.067878] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[ 86.067879] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[ 86.067887] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.068128] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.068183] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[ 86.068185] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[ 86.068192] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.068417] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.068466] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[ 86.068468] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[ 86.068474] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.138127] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.138131] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.138927] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.138930] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.139653] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.139657] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.140331] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.140333] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.873706] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.873712] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.873729] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.873732] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.873743] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.873745] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.873755] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[ 86.873757] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[ 86.874800] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.874818] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.874868] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.874877] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.874924] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.874934] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.874981] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 86.874992] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected

Any ideas?
Jan

devujan · 2021-04-10T19:40:20Z

I found another error myself.
DisplayLink(R) && Lennart implicitly assume that /opt is part of the root filesystem which is mounted when /etc/udev/rules.d/99-displaylink.rules is executed.
I oversaw the error in dmesg about /opt/displaylink/udev.sh could not be executed (because it was not mounted at that time.....).
Additionally executing
/opt/displaylink/udev.sh /dev usb-004-003-DisplayLink_USB-C_Triple-4K_Dock_DGWC00110028635 /dev/bus/usb/004/003
(for my computer) from within the /etc/init.d/displaylink.sh script didn't help. (Even with the evdi module loaded later - not via /etc/modules-load.d/evdi.conf ....).
Adapting 99-displaylink.rules with /sbin instead of /opt/displaylink and copying udev.sh to /sbin solved that problem.
I am still stuck with
....
[ 77.396608] evdi: [D] evdi_platform_add_devices:158 Increasing device count to 4
[ 77.399153] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p000000000dedf4d6
[ 77.399949] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 77.400744] evdi evdi.0: [drm] Cannot find any crtc or sizes
[ 77.402867] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 77.407206] [drm] Initialized evdi 1.9.1 20210126 for evdi.0 on minor 0
[ 77.408026] evdi: [I] Evdi platform_device create
[ 77.408898] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000f68ea074
[ 77.409670] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 77.410433] evdi evdi.1: [drm] Cannot find any crtc or sizes
[ 77.411200] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 77.411654] [drm] Initialized evdi 1.9.1 20210126 for evdi.1 on minor 1
[ 77.413197] evdi: [I] Evdi platform_device create
[ 77.414002] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000314633ec
[ 77.414777] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 77.415538] evdi evdi.2: [drm] Cannot find any crtc or sizes
[ 77.416310] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 77.416382] [drm] Initialized evdi 1.9.1 20210126 for evdi.2 on minor 2
[ 77.418017] evdi: [I] Evdi platform_device create
[ 77.418829] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000a94bae34
[ 77.419615] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[ 77.420393] evdi evdi.3: [drm] Cannot find any crtc or sizes
[ 77.421214] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[ 77.421280] [drm] Initialized evdi 1.9.1 20210126 for evdi.3 on minor 3
.....
evdi 1.9.1 does not like the 5.10.0-5-amd64 #1 SMP Debian 5.10.26-1 kernel.

This should be the same kernel as in bullseye.
Anybody having displaylink on bullseye running?

swoopla · 2021-04-11T11:51:28Z

Hi,

it works with Ubuntu Hirsute (5.11.0) and Displaylink 5.4 (displaylink-driver-5.4.0-55.153.run)

NAME="Ubuntu"
VERSION="21.04 (Hirsute Hippo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Hirsute Hippo (development branch)"
VERSION_ID="21.04"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute

uname -a
Linux swoopla 5.11.0-13-generic #14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

dmesg

[   58.009718] evdi: [I] Attaching to usb:2-1.4
[   58.010893] evdi: [D] evdi_painter_connect:851 (dev=0) Process is trying to connect
[   58.010896] evdi: [I] Task 2380 (DesktopManagerE) of process 2372 (DisplayLinkMana)
[   58.011043] evdi: [D] evdi_add_i2c_adapter:813 (dev=0) Added i2c adapter bus number 11
[   58.011045] evdi: [D] evdi_painter_connect:903 (dev=0) Connected with 00000000f441ac4f
[   58.011049] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.011736] evdi: [I] Attaching to usb:2-1.4
[   58.012741] evdi: [D] evdi_painter_connect:851 (dev=0) Process is trying to connect
[   58.012743] evdi: [I] Task 2380 (DesktopManagerE) of process 2372 (DisplayLinkMana)
[   58.012808] evdi: [D] evdi_add_i2c_adapter:813 (dev=1) Added i2c adapter bus number 12
[   58.012810] evdi: [D] evdi_painter_connect:903 (dev=1) Connected with 000000000f7351f1
[   58.012813] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.086479] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.086481] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.086566] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.086567] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.086661] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.086662] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.086857] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.086858] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.087056] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.087060] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.087064] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.087067] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.105959] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105962] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.105964] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105964] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.105966] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105967] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.105968] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105968] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.185434] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.185437] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.185522] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.185523] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.185610] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.185611] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.185808] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.185810] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.186017] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.186021] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.186025] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.186028] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.198062] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198065] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.198066] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198067] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.198069] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198070] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.198071] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198071] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.274820] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   58.274824] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   58.274830] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   58.274831] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   58.289755] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 0
[   58.289763] evdi: [D] evdi_painter_mode_changed_notify:762 (dev=0) Notifying mode changed: 1920x1080@60; bpp 32; 
[   58.289765] evdi: [D] evdi_log_pixel_format:741 pixel format XR24 little-endian (0x34325258)
[   58.289767] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 0
[   58.305406] evdi: [D] evdi_painter_dpms_notify:715 (dev=1) Notifying dpms mode: 0
[   58.305414] evdi: [D] evdi_painter_mode_changed_notify:762 (dev=1) Notifying mode changed: 1920x1080@60; bpp 32; 
[   58.305417] evdi: [D] evdi_log_pixel_format:741 pixel format XR24 little-endian (0x34325258)
[   58.305418] evdi: [D] evdi_painter_dpms_notify:715 (dev=1) Notifying dpms mode: 0

But i don't have evdi package installed on my system:

swoopla@swoopla:~$ dpkg -l |grep evdi
swoopla@swoopla:~$ dpkg -l |grep dkms
ii  dkms                                       2.8.4-4                                                     all          Dynamic Kernel Module Support Framework

bnavigator · 2021-04-11T13:23:49Z

If you use the official standalone installer from DisplayLink, it comes with evdi bundled. It won't install any package into the dpkg database.

Once again, please: The title of this page is "EVDI kernel 5.11/5.12 support". For anything else, please either use the displaylink support forum, or if it is specific to the evdi driver, open a new issue.

muellerjoel · 2021-04-13T14:23:07Z

I have Arch Linux with Kernel 5.11.12 on a Cinnamon Desktop and latest evdi & Displaylink commit. So every change of resolution or master screen ends up on a freeze also zoom isn‘t possible.

elguero · 2021-04-15T13:45:52Z

@displaylink-emajewsk Thank you for the updates. I can confirm that it is working on Fedora 33.

Question: Are there any plans to re-tag 1.9.1 from the current devel branch?

This would be helpful for packaging. Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm

Thanks again for keeping us updated.

Just following up on this question.

Thanks

elguero · 2021-04-20T13:59:59Z

@displaylink-emajewsk Thank you for the updates. I can confirm that it is working on Fedora 33.
Question: Are there any plans to re-tag 1.9.1 from the current devel branch?
This would be helpful for packaging. Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm
Thanks again for keeping us updated.

Just following up on this question.

Thanks

@displaylink-emajewsk @displaylink-dkurek

Sorry to ask once more. Can we expect to get a proper EVDI release that works with Kernel 5.11/5.12? The current 1.9.1 tag is not compatible with those kernels. You are bundling with the DisplayLink 5.4 drivers an unreleased version of EVDI.

Thank you for your help and support.

echosa · 2021-04-20T15:04:01Z

FYI for Pop!_OS users having issues, follow this thread instead: #279

ztoufie · 2021-04-23T09:36:31Z

@displaylink-emajewsk Thank you for the updates. I can confirm that it is working on Fedora 33.
Question: Are there any plans to re-tag 1.9.1 from the current devel branch?
This would be helpful for packaging. Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm
Thanks again for keeping us updated.

Just following up on this question.
Thanks

@displaylink-emajewsk @displaylink-dkurek

Sorry to ask once more. Can we expect to get a proper EVDI release that works with Kernel 5.11/5.12? The current 1.9.1 tag is not compatible with those kernels. You are bundling with the DisplayLink 5.4 drivers an unreleased version of EVDI.

Thank you for your help and support.

How about we create a downstream repo of this EVDI devel branch on https://github.com/displaylink-rpm/ and then tag it ourselves. That way we not dependent on any tags here.

displaylink-emajewsk · 2021-04-26T14:03:49Z

I'm back from holiday. Thanks for the patience. 😇

@elguero The release has been retagged. Someone must've tagged the version incorrectly before pushing and we did not notice. I'll be more vigilant in the future. 😅
Is there anything else I can do to make packaging easier?

elguero · 2021-04-26T14:39:23Z

@displaylink-emajewsk Thank you!

One thing that would be helpful is to have support for newer kernels done at a quicker pace. I know it all comes down to resources. Some in the community are quick to help test the release candidates and they point out when changes are needed for upcoming kernel releases. If those items could be taken care of before the official release or at least before the distros start to use the newer kernel that causes issues, that would be helpful.

This is probably a no go as far as being resolved but the DisplayLink manager binary complicates being able to put something up on Fedora copr or even considered for inclusion in Fedora, if we are understanding things correctly (displaylink-rpm/displaylink-rpm#125). There was a request to add it to Fedora copr but we think that the DisplayLink manager binary prevents this from being done according to the current policies. Work is being done by contributors to try and get the displaylink-rpm project included in RPMFusion. One contributor has submitted a PR to help work towards this (displaylink-rpm/displaylink-rpm#97).

Thank you for asking and for your responses.

bnavigator · 2021-04-26T16:10:25Z

It might be even more out of scope, but IMHO the best solution would be to commit the opensource kernel module into the official linux kernel tree. It's the recommended way to keep all the drivers in sync with kernel development as it draws on the resources of kernel developers. See amdgpu vs nvidia drivers and how their approaches are received within the Linux community.

ztoufie · 2021-04-26T23:30:47Z

I'm back from holiday. Thanks for the patience. innocent

@elguero The release has been retagged. Someone must've tagged the version incorrectly before pushing and we did not notice. I'll be more vigilant in the future. sweat_smile
Is there anything else I can do to make packaging easier?

You should probably also update your Releases page to indicate that v1.9.1 is the latest release, it's still showing v1.9.0 as being the latest release.

https://github.com/DisplayLink/evdi/releases

displaylink-emajewsk · 2021-04-27T10:32:07Z

One thing that would be helpful is to have support for newer kernels done at a quicker pace.

@elguero Unfortunately, we only officially support Ubuntu LTS releases. Other Linux releases are being put in the "nice to have if there's time" category as of now. 😢
Actually, in regards to your second question, probably the best way to have support done earlier would be to message DisplayLink as a distro representative and offer to work together to bring support on both ends, or something similar, I think.
Fedora's policies indeed prevent us from being included. RPMFusion sounds like a good idea though. Ideally, there will soon be some improvement in our driver distribution. At least it'd seem my nagging has worked for once. 😀

@bnavigator This is out of my hands, sorry.

@ztoufie Ah, thanks! 😇

dominikzogg · 2021-05-10T06:45:53Z

@displaylink-emajewsk 5.11 will the default kernel of ubuntu 20.04 within the next 3 months (about 3 months after 21.04 release).

cement-head · 2021-05-10T15:18:58Z

Dumb (noob) question: Does EVDI module come packaged within the DisplayLink Driver? I'm assuming so, because when I list the DKMS modules, EVDI shows up, but it's not listed in SYNAPTIC.

On Ubuntu 20.04, running on a System76 Galago Pro (galp3-c) laptop, DL is broken for me.

$ dkms status
evdi, 1.9.1, 5.11.0-7614-generic, x86_64: installed
openrazer-driver, 3.0.1, 5.11.0-7614-generic, x86_64: installed
system76, 1.0.12~1616424713~20.04~c42d494~dev, 5.11.0-7614-generic, x86_64: installed
system76_acpi, 1.0.2~1600812457~20.04~0bc966c~dev, 5.11.0-7614-generic, x86_64: installed
system76-io, 1.0.1~1616424744~20.04~57c15ff~dev, 5.11.0-7614-generic, x86_64: installed

Does that mean (a) that the patched EVDI 1.9.1 module hasn't been updated, or (b) that the System76 specific kernel(s) have issues?

TIA

bnavigator · 2021-05-10T17:57:14Z

Dumb (noob) question: Does EVDI module come packaged within the DisplayLink Driver? I'm assuming so, because when I list the DKMS modules,

If you installed from the official installer, yes.

But it's not listed in SYNAPTIC.

What do you mean by that?

Does that mean (a) that the patched EVDI 1.9.1 module hasn't been updated

No.

(b) that the System76 specific kernel(s) have issues?

Probably not to do with the kernel itself. Check lsmod if the evdi module is actually loaded.

Check your Xserver logs if you got errors. Any more questions about usage: --> Displaylink support forum.

cement-head · 2021-05-10T20:23:14Z

EVDI module is loaded; No errors in XOrg.log.0

I guess if EVDI is included in DLM, it doesn't get listed as a separate package in SYNAPTIC.

Okay - then it's something else.

cement-head · 2021-06-15T18:53:44Z

Fix in Xserver is done! Needs to built for Ubuntu from master: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1931547

synaptics-lspintzyk · 2021-07-08T06:47:45Z

Discussion on this issue deviated from 5.12 kernel to that Pop!_OS issue:
#279 that is fixed now.

If there is any 5.11/5.12 kernel issue please raise new issue.
This one is to be closed.

This was referenced Apr 6, 2021

Fedora 33 kernel 5.11 displaylink-rpm/displaylink-rpm#162

Closed

Building EVDI fails with kernel 5.11+ displaylink-rpm/displaylink-rpm#161

Closed

bnavigator mentioned this issue Apr 6, 2021

Mesa 21 not supported #274

Closed

sickcodes mentioned this issue Apr 9, 2021

5.11.0-rc1 Building #249

Closed

cement-head mentioned this issue May 10, 2021

Pop!_OS 20.04: Display Recognized but not usable #279

Closed

displaylink-emajewsk closed this as completed Jul 8, 2021

FBobbioC mentioned this issue Jul 20, 2021

EVDI-Kernel 5.13.2 Issues #296

Closed

jacobgkau mentioned this issue Jul 27, 2022

evdi-dkms doesn't install with kernel 5.11 pop-os/linux#46

Closed

EVDI kernel 5.11/5.12 support #275

EVDI kernel 5.11/5.12 support #275

Comments

displaylink-emajewsk commented Apr 2, 2021

joren485 commented Apr 2, 2021

mfs12 commented Apr 4, 2021

echosa commented Apr 5, 2021

jteib commented Apr 6, 2021

bnavigator commented Apr 6, 2021 • edited Loading

sickcodes commented Apr 6, 2021 • edited Loading

Nillu commented Apr 6, 2021

bnavigator commented Apr 6, 2021

moodyhunter commented Apr 6, 2021

bnavigator commented Apr 6, 2021

joren485 commented Apr 6, 2021 • edited Loading

bnavigator commented Apr 6, 2021

joren485 commented Apr 6, 2021

bnavigator commented Apr 6, 2021

nckrse commented Apr 6, 2021

bnavigator commented Apr 6, 2021

bnavigator commented Apr 6, 2021

echosa commented Apr 6, 2021

nckrse commented Apr 6, 2021

bnavigator commented Apr 6, 2021

Nillu commented Apr 7, 2021 • edited Loading

AlFontal commented Apr 7, 2021

bnavigator commented Apr 7, 2021

echosa commented Apr 7, 2021

bnavigator commented Apr 7, 2021 • edited Loading

echosa commented Apr 7, 2021

displaylink-emajewsk commented Apr 8, 2021

echosa commented Apr 8, 2021 • edited Loading

elguero commented Apr 8, 2021

devujan commented Apr 9, 2021

dmesg | grep evdi

devujan commented Apr 10, 2021

swoopla commented Apr 11, 2021

bnavigator commented Apr 11, 2021

muellerjoel commented Apr 13, 2021

elguero commented Apr 15, 2021

elguero commented Apr 20, 2021

echosa commented Apr 20, 2021

ztoufie commented Apr 23, 2021

displaylink-emajewsk commented Apr 26, 2021

elguero commented Apr 26, 2021

bnavigator commented Apr 26, 2021

ztoufie commented Apr 26, 2021

displaylink-emajewsk commented Apr 27, 2021

dominikzogg commented May 10, 2021

cement-head commented May 10, 2021

bnavigator commented May 10, 2021

cement-head commented May 10, 2021

cement-head commented Jun 15, 2021

synaptics-lspintzyk commented Jul 8, 2021

bnavigator commented Apr 6, 2021 •

edited

Loading

sickcodes commented Apr 6, 2021 •

edited

Loading

joren485 commented Apr 6, 2021 •

edited

Loading

Nillu commented Apr 7, 2021 •

edited

Loading

bnavigator commented Apr 7, 2021 •

edited

Loading

echosa commented Apr 8, 2021 •

edited

Loading