Open AndreV84 opened 4 years ago
sudo ./displaylink-driver-5.2.14.run
[sudo] password for nvidia:
Verifying archive integrity... 100% All good.
Uncompressing DisplayLink Linux Driver 5.2.14 100%
DisplayLink Linux Software 5.2.14 install script called: install
Distribution discovered: Ubuntu 18.04.4 LTS
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64-ubuntu-1604/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing licence file
Adding udev rule for DisplayLink DL-3xxx/4xxx/5xxx/6xxx devices
Please read the FAQ http://support.displaylink.com/knowledgebase/topics/103927-troubleshooting-ubuntu Installation complete! but when I connect the display it won't work
neither it will appear in the list of xrandr --providers is reflected by lsusb though
Hello,
Do you have any news with this screen? Im' also trying to use an old Mimo 720S screen, using DisplayLink without success.
My screen is well recognized by lsusb :
lsusb -d 17e9:401a
Bus 001 Device 006: ID 17e9:401a DisplayLink
the installation is working fine (kind of) :
./displaylink-installer.sh install
DisplayLink Linux Software 5.1.26 install script called: install
Distribution discovered: Ubuntu 18.04.4 LTS
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64-ubuntu-1604/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing licence file
Adding udev rule for DisplayLink DL-3xxx/4xxx/5xxx/6xxx devices
Please read the FAQ
http://support.displaylink.com/knowledgebase/topics/103927-troubleshooting-ubuntu
Installation complete!
But the screen continue to show the blinking's colors screens.
Hello!
“Installing DisplayLink driver at Nvidia jetson nano device”
Is there any new progress at present?
Hi there,
Getting crowded here, ha?
We suffer from the same problem.
AFAIK, the problem is sourced from a kernel modification done by NVIDIA. They are aware of the problem for years through their forum, but they haven't fixed anything until now.
This is what I get my x86 Ubuntu 18.04 and everythink works as expected: das@ubuntu-pc: lsmod | grep evdi evdi 57344 2 drm_kms_helper 172032 2 evdi,i915 drm 401408 12 drm_kms_helper,evdi,i915 syscopyarea 16384 2 drm_kms_helper,evdi sysfillrect 16384 2 drm_kms_helper,evdi sysimgblt 16384 2 drm_kms_helper,evdi das@ubuntu-pc: lsusb Bus 002 Device 007: ID 17e9:4301 DisplayLink Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 004: ID 04b4:0033 Cypress Semiconductor Corp. Mouse Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
In a Xavier NX platform, I see only evdi driver with lsmod. There is nothing about drm_kms_helper lines that I see in the x86 platform.
Best,
Could you provide steps to implement support of USB-A support [usb-c monitor] at aarch64 linux device, please? Reference thread: More reference