Install Fail: Missing Component: libdrm Ub 20.04

[txtweet]

I have done some other tests.
I have the same problem on a clean install of 18.04 with Displaylink 5.3 but Displaylink 5.2 can be installed without trouble.

Libdrm-dev seems to have been updated very recently. I think this is the problem and that's why the driver can't be installed anymore on a clean install.

I can't suceed to install the previous version of the libdrm-dev package but maybe it can solve the problem.

[JakubDabrowski]

Dear users,

Thank you for your constant communication here on the forum.

We would like to apologize for the inconveniences that you have faced while trying to use our new driver.
We are aware of libdrm issue on our new driver for Ubuntu 20.04

Right now our Engineering Team is working on the resolution of the problem. We should be able to release a fix very shortly as our engineers are already testing the possible solution for this case.

As a possible temporary workaround you may start our installer in this manner:

$ LANG=C ./displaylink-installer-5.xxx.run where xxx is the installer version.
This should help you for now before we have a permanent fix done.

Thank you very much for your patience and I will be posting here any new information we would be able to share with you!

Kind regards,
Jakub

[Stofe7]

Thank you, but still issue:

sudo LANG=C ./displaylink-driver-5.3.0.28.run

Verifying archive integrity... 100% All good.
Uncompressing DisplayLink Linux Driver 5.3.0.28 100%
DisplayLink Linux Software 5.3.0.28 install script called:
Distribution discovered: Ubuntu 20.04 LTS

Installing

[ Installing EVDI ]
[[ Installing EVDI DKMS module ]]
Error! DKMS tree already contains: evdi-1.7.0
You cannot add the same module/version combo more than once.
EVDI DKMS module already installed.
[[ Installing module configuration files ]]
[[ Installing EVDI library ]]
cc -I../module -std=gnu99 -fPIC -c -o evdi_lib.o evdi_lib.c
In file included from evdi_lib.c:5:
/usr/lib/gcc/x86_64-linux-gnu/9/include/stdint.h:9:16: fatal error: stdint.h: No such file or directory
9 | # include_next <stdint.h>
| ^~~~~~~~~~
compilation terminated.
make: *** [<builtin>: evdi_lib.o] Error 1
ERROR: Failed to build evdi/5.3.0.28 library.

[greghead]

I had the same issue with the

Unsatisfied dependencies. Missing component: libdrm.

Message. After using

LANG=C ./displaylink-driver-5.3.0.28.run

it worked for me with 20.04 LTS fresh installation and latest updates installed.

I tried the older Firmware with 19.10 and it was really laggy. Not it's working pretty good. I'm happy with the performance and i hope it will keep that good

[Stofe7]

My reported issue is still valid with the 5.3.1 driver.
I've tried to uninstall and install again, but I got the same result:

"/usr/lib/gcc/x86_64-linux-gnu/9/include/stdint.h:9:16: fatal error: stdint.h: No such file or directory
9 | # include_next <stdint.h>
| ^~~~~~~~~~
compilation terminated."

Best,

[ribakip304]

Originally Posted by JakubDabrowski

As a possible temporary workaround you may start our installer in this manner:

$ LANG=C ./displaylink-installer-5.xxx.run where xxx is the installer version.
This should help you for now before we have a permanent fix done.

Working great!
Thanks a lot for the fast reply !

[JakubDabrowski]

Hello,

Thank you for your patience.

As I have mentioned yesterday, we were working on a installation fix for Ubuntu 20.04.

Here it is: https://www.displaylink.com/downloads/file?id=1576

Please verify that version and if you would face any issues inform us.

Thank you very much for your cooperation!

Best regards,
Jakub

[1kenthomas]

Hi Jakub,

Unfortunately, after using the below, my system hangs after login. I can only get to a recovery root command prompt. Using the script to attempt uninstall of the driver does not work, "Display not found" (it appear to assume a graphical environment).

Can someone over there provide instructions to disable / remove the driver from the command line, so I can get back in working order?

Thanks, Ken

UPDATE: using .run, I was almost able to get somewhere by booting into the -29 kernel (required) and using LANG=C for the installer, but am stuck at "component linux-headers not available" even through headers for -29 are installed.

Using displaylink-debian.sh, --uninstall is still blocked by "Can't open display", alas.

UPDATE2: I got out of this situation by installing lightdm from the command line, which got me into a UI. Problem may only be with gdm3? Able to uninstall, will post the loop situation that caused hang from syslog when I have a chance.[/B]

Originally Posted by JakubDabrowski

Hello,

Thank you for your patience.

As I have mentioned yesterday, we were working on a installation fix for Ubuntu 20.04.

Here it is: https://www.displaylink.com/downloads/file?id=1576

Please verify that version and if you would face any issues inform us.

Thank you very much for your cooperation!

Best regards,
Jakub

[jarsal]

Originally Posted by JakubDabrowski

Dear users,

Thank you for your constant communication here on the forum.

We would like to apologize for the inconveniences that you have faced while trying to use our new driver.
We are aware of libdrm issue on our new driver for Ubuntu 20.04

Right now our Engineering Team is working on the resolution of the problem. We should be able to release a fix very shortly as our engineers are already testing the possible solution for this case.

As a possible temporary workaround you may start our installer in this manner:

$ LANG=C ./displaylink-installer-5.xxx.run where xxx is the installer version.
This should help you for now before we have a permanent fix done.

Thank you very much for your patience and I will be posting here any new information we would be able to share with you!

Kind regards,
Jakub

New script works for me, external monitors are working now, but they are unsable.
After connecting dock, cpu usage is above 100% and external monitors are laggy, unsable.
Graphics cards: Radeon Vega 8 Graphics/Radeon RX 560X. Everything is working correctly on windows.

[JakubDabrowski]

Hello,

Here is the message for three of our users: Strofe7, 1kenthomas and jarsal:

Strofe7:

Could you please use the command sudo apt-get install build-essential ?
It will install the compiler and basic C libraries.

Please let me know if that resolves your issue.

1kenthomas:

Please use the following commands in your console:

rm -f /etc/modprobe.d/evdi.conf
rm -f /etc/modules-load.d/evdi.conf

It will change the auto-loading of evdi module while booting. Please also follow this guide and gather log files for me.

Thank you for the log files and further information.

jarsal:

We would need to have the log files that you can gather by following this guide.

Additionally, please also gather Gnome output for us by using this command:
journalctl /usr/bin/gnome-shell > gnome_shell.txt and attach the file created by it.

If this is possible we would like also to see a short video showing the mentioned lags. That would help us greatly.



Thank you to every single one of you for your actions and patience. We will be verifying your cases as soon as we got these new information from you.

If you would like to move from the forum for a email communication, please write back on: technical_enquiries@displaylink.com

Best regards,
Jakub