![]() |
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#1 |
|
Junior Member
Join Date: Oct 2025
Posts: 1
|
Hi there.
Has anyone encountered anything like this before? Can't make displaylink-driver work on the recent Dell laptop. Got "evdi.0: [drm] Cannot find any crtc or sizes" errors. * Here we are: Linux distribution: Ubuntu 24.04.3 LTS Linux kernel version: 6.14.0-33-generic #33~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 19 17:02:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Hardware name: Dell Inc. Dell Pro 13 Premium PA13250/0NGT53, BIOS 2.6.1 08/26/2025 * Did the standard displaylink-driver installation following https://www.synaptics.com/products/d...wnloads/ubuntu 1. installed Synaptics APT Repository 2. apt-get update 3. apt-get install displaylink-driver * Installation was smooth, no errors. * systemctl status displaylink-driver shows it's running: ● displaylink-driver.service - DisplayLink Driver Service Loaded: loaded (/usr/lib/systemd/system/displaylink-driver.service; static) Active: active (running) since Thu 2025-10-23 15:26:35 BST; 23min ago Process: 8041 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1 | sed -e "s:-:/:") && modprobe evdi) (code=exited, status> Main PID: 8055 (DisplayLinkMana) Tasks: 74 (limit: 37727) Memory: 108.6M (peak: 109.0M) CPU: 35.993s CGroup: /system.slice/displaylink-driver.service └─8055 /opt/displaylink/DisplayLinkManager Oct 23 15:26:35 laptopname systemd[1]: Starting displaylink-driver.service - DisplayLink Driver Service... Oct 23 15:26:35 laptopname systemd[1]: Started displaylink-driver.service - DisplayLink Driver Service. but displaylink-driver seems can't find compatible graphics component (CRTC) to drive the display: $ dmesg | grep evdi .... [ 2907.263245] evdi_prime_import_sg_table+0xa4/0x110 [evdi] [ 2907.264549] Modules linked in: tls evdi(OE) exfat rfcomm snd_seq_dummy snd_hrtimer snd_soc_sof_sdw snd_soc_intel_hda_dsp_common snd_soc_sdw_utils snd_sof_probes snd_soc_cs35l56_spi snd_soc_cs35l56 snd_soc_wm_adsp snd_soc_cs35l56_shared snd_soc_cs_amp_lib cs_dsp snd_soc_cs42l43 pinctrl_cs42l43 spi_cs42l43 snd_soc_cs42l43_sdw cs42l43_sdw regmap_sdw cs42l43 snd_soc_dmic qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_sof_pci_intel_lnl snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel soundwire_cadence snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda snd_hda_codec_hdmi snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_acpi soundwire_bus snd_soc_sdca intel_uncore_frequency intel_uncore_frequency_common snd_soc_core x86_pkg_temp_thermal intel_powerclamp snd_compress ac97_bus snd_pcm_dmaengine coretemp iwlmvm snd_hda_intel snd_usb_audio [ 2907.264844] evdi_prime_import_sg_table+0xa4/0x110 [evdi] [ 2907.266079] evdi: [E] evdi_painter_grabpix_ioctl:1090 Failed to map scanout buffer log file shows these errors: ... 2025-10-23T15:53:42.252737+01:00 laptopname kernel: ? __pm_runtime_idle+0x7b/0xd0 2025-10-23T15:53:42.252738+01:00 laptopname kernel: ? __task_pid_nr_ns+0x6f/0xd0 2025-10-23T15:53:42.252740+01:00 laptopname kernel: ? arch_exit_to_user_mode_prepare.isra.0+0x22/0xd0 2025-10-23T15:53:42.252741+01:00 laptopname kernel: ? syscall_exit_to_user_mode+0x38/0x1d0 2025-10-23T15:53:42.252741+01:00 laptopname kernel: ? do_syscall_64+0x8a/0x170 2025-10-23T15:53:42.252742+01:00 laptopname kernel: ? arch_exit_to_user_mode_prepare.isra.0+0x22/0xd0 2025-10-23T15:53:42.252743+01:00 laptopname kernel: ? syscall_exit_to_user_mode+0x38/0x1d0 2025-10-23T15:53:42.252747+01:00 laptopname kernel: ? do_syscall_64+0x8a/0x170 2025-10-23T15:53:42.252748+01:00 laptopname kernel: ? irqentry_exit+0x43/0x50 2025-10-23T15:53:42.252749+01:00 laptopname kernel: ? exc_page_fault+0x96/0x1e0 2025-10-23T15:53:42.252750+01:00 laptopname kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e 2025-10-23T15:53:42.252751+01:00 laptopname kernel: RIP: 0033:0x713f4bb24e1d 2025-10-23T15:53:42.252753+01:00 laptopname kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00 2025-10-23T15:53:42.252773+01:00 laptopname kernel: RSP: 002b:00007ffc0fe186d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 2025-10-23T15:53:42.252774+01:00 laptopname kernel: RAX: ffffffffffffffda RBX: 00007ffc0fe187c4 RCX: 0000713f4bb24e1d 2025-10-23T15:53:42.252775+01:00 laptopname kernel: RDX: 00007ffc0fe1876c RSI: 00000000c00c642e RDI: 0000000000000091 2025-10-23T15:53:42.252777+01:00 laptopname kernel: RBP: 00007ffc0fe18720 R08: 0000713f4bc03b20 R09: 0000000000000220 2025-10-23T15:53:42.252778+01:00 laptopname kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 00007ffc0fe1876c 2025-10-23T15:53:42.252779+01:00 laptopname kernel: R13: 00000000c00c642e R14: 0000000000000091 R15: 000060d1239483a0 2025-10-23T15:53:42.252780+01:00 laptopname kernel: </TASK> 2025-10-23T15:53:42.252781+01:00 laptopname kernel: ---[ end trace 0000000000000000 ]--- 2025-10-23T15:53:42.252907+01:00 laptopname kernel: evdi: [E] evdi_painter_grabpix_ioctl:1090 Failed to map scanout buffer I believe this is a compatibility issue between the driver version and the kernel. I've reinstalled the driver following https://support.displaylink.com/know...rticles/684649 but got the same result. PS: Did not have any such errors before on previous Dell models.. |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Nov 2025
Posts: 3
|
Hello nnk,
Have you already received a response to your problem description? I have been using Ubuntu 24.04 LTS on my HP ZBook since the beginning of July 2024 and am also (still) using an HP docking station with the displaylink driver. However, this means that I started the installation with a driver that was current at this time and that it has always been updated via the apt repository. So I can't reproduce your installation problems myself. But since the last update to version 6.2.0 (which probably also included a firmware update), I have noticed a problem that did not exist before: One of my monitors is no longer recognized correctly and I can only run it at Full HD resolution and no longer at WQHD. Which docking station are you using? |
|
|
|
![]() |
|
|