Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 08-01-2021, 09:47 AM   #1
txan2
Junior Member
 
Join Date: Aug 2021
Posts: 1
Default Monitor is not detected

Greetings,

I have an ASUS ZenScreen MB16AC portable monitor which is supposed to work with DisplayLink as in here:
Code:
https://www.displaylink.com/products/find?cat=2&br=-1&usbc=1
I have tried everything but it still not working:

1. Install evdi:
Code:
# dkms status
evdi, 1.9.1, 5.12.14-arch1-1, x86_64: installed
2. Install displaylink:
Code:
$ systemctl status displaylink
displaylink.service - DisplayLink Manager Service
     Loaded: loaded (/usr/lib/systemd/system/displaylink.service; enabled; vendor preset: disabled)
     Active: active (running) since Sun 2021-07-04 22:08:28 CEST; 14min ago
    Process: 489 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
   Main PID: 490 (DisplayLinkMana)
      Tasks: 14 (limit: 38078)
     Memory: 11.1M
        CPU: 398ms
     CGroup: /system.slice/displaylink.service
             └─490 /usr/lib/displaylink/DisplayLinkManager
3. Add Xorg configuration:
Code:
Section "OutputClass"
    Identifier  "DisplayLink"
    MatchDriver "evdi"
    Driver      "modesetting"
    Option      "AccelMethod" "none"
    Option      "PageFlip" "false"
EndSection
4. Attach the portable monitor and restart the computer;
dmesg doesn't show DisplayLink:
Code:
[    1.226512] usb 4-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.258506] usb 4-2: New USB device found, idVendor=0bda, idProduct=0412, bcdDevice= 0.00
[    1.258509] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.258510] usb 4-2: Product: 4-Port USB 3.0 Hub
[    1.258511] usb 4-2: Manufacturer: Generic
and lsusb shows some USB hub thingy:
Code:
$ lsusb
Bus 004 Device 009: ID 0bda:0412 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
My system:
Code:
$ uname -r
5.12.14-arch1-1
$ pacman -Qi xorg-server | grep Version
Version         : 1.20.11-1
What can I do next?
txan2 is offline   Reply With Quote
Old 08-12-2021, 04:17 PM   #2
karly
Junior Member
 
Join Date: Aug 2021
Posts: 4
Default

I think this might be because you have a kernel version higher than what the pre-built driver works with. I am using the 5.13.9 kernel right now and monitors aren't detected (everything else works though). From what I can tell from their github evdi repo, 5.12 kernel support was added in March, but not sure if it was part of the evdi version that is shipped with the 5.4 display link driver.

Ref: https://github.com/DisplayLink/evdi/commits/devel

Last edited by karly; 08-12-2021 at 04:54 PM.
karly is offline   Reply With Quote
Old 08-12-2021, 05:05 PM   #3
karly
Junior Member
 
Join Date: Aug 2021
Posts: 4
Lightbulb

After having the same issue myself by using a mainline 5.13 kernel in Pop OS, I managed to get the monitors working by having a look at the guide for porting the driver to other distros here: https://support.displaylink.com/know...r-to-other-lin

A small summary though (only tested in PopOs, but should probably work in most Debian/Ubuntu based distros):

1. Make sure you uninstall the current EVDI driver. Do this by calling the currently installed DisplayLink installer file with a "uninstall" argument. For example:
Code:
sudo ./displaylink-driver-5.4.0-55.153.run uninstall
2. Extract the content of the installer file. For example:
Code:
./displaylink-driver-5.4.0-55.153.run --noexec --keep
3. A folder will now exist in the same path as your installer file. CD into it like so: (replace x.x.xx with the real numbers)
Code:
cd ./displaylink-driver-5.4.0-55.153
4. Replace the evdi.tar.gz file that exists there. I just downloaded a tarball from the latest dev branch from their Github like so:
Code:
curl -L https://github.com/DisplayLink/evdi/archive/refs/heads/devel.tar.gz -o evdi.tar.gz
5. Because the structure of the tar.gz file from Github has an extra folder in its root level, you also need to modify the install_evdi() function in the displaylink-installer.sh file. Look for this:

Code:
if ! tar xf "$TARGZ" -C "$EVDI"; then
and replace with:

Code:
if ! tar xf "$TARGZ" -C "$EVDI" --strip-components=1; then
6. Run the installer script as root: sudo ./displaylink-installer.sh and it should install and compile the very latest EVDI driver which is compatible with linux kernels up til and including 5.14.

Last edited by karly; 08-23-2021 at 05:25 PM. Reason: add -L to curl
karly is offline   Reply With Quote
Old 08-18-2021, 04:20 PM   #4
Gaboto
Junior Member
 
Join Date: Aug 2021
Posts: 2
Default

I did exactly the steps Karly said, but it doesn't work. When I connect the displaylink docking station to my USB and i check de status of the doplaylink-driver service, I get:
displaylink-driver.service - DisplayLink Driver Service
Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2021-08-18 13:12:56 -03; 4s ago
Process: 4262 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1 | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=1/FAILURE)
Gaboto is offline   Reply With Quote
Old 08-23-2021, 05:24 PM   #5
karly
Junior Member
 
Join Date: Aug 2021
Posts: 4
Default

Quote:
Originally Posted by Gaboto View Post
I did exactly the steps Karly said, but it doesn't work. When I connect the displaylink docking station to my USB and i check de status of the doplaylink-driver service, I get:
displaylink-driver.service - DisplayLink Driver Service
Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2021-08-18 13:12:56 -03; 4s ago
Process: 4262 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1 | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=1/FAILURE)
Hm, that is too bad, but do you use a Debian or Ubuntu based OS? I know for Fedora an extra step is needed according to this: https://github.com/DisplayLink/evdi/issues/297
karly is offline   Reply With Quote
Old 08-25-2021, 03:46 PM   #6
Gaboto
Junior Member
 
Join Date: Aug 2021
Posts: 2
Default

Quote:
Originally Posted by karly View Post
Hm, that is too bad, but do you use a Debian or Ubuntu based OS? I know for Fedora an extra step is needed according to this: https://github.com/DisplayLink/evdi/issues/297
I use Ubuntu 20.04
Gaboto is offline   Reply With Quote
Old 08-26-2021, 07:54 AM   #7
karly
Junior Member
 
Join Date: Aug 2021
Posts: 4
Default

Quote:
Originally Posted by Gaboto View Post
I use Ubuntu 20.04
I also fixed a missing -L argument in the curl command above though, as pointed out in the mentioned Github thread. If that failed previously it might be worth giving it another try now
karly is offline   Reply With Quote
Old 09-16-2021, 12:18 PM   #8
cement_head
Junior Member
 
Join Date: Feb 2019
Posts: 6
Default

Great! Just found this post via GitHub - and I **think** it worked on Ubuntu 20.04 (no errors). I'm running vanilla Ubuntu with the System76 PPA for a System76 GalagoPro laptop.

Just an FYI for Ubuntu; the two commands should replace the <./> with <bash>.
cement_head is offline   Reply With Quote
Old Today, 08:48 AM   #9
johnsongw
Junior Member
 
Join Date: Sep 2021
Posts: 1
Default

Quote:
Originally Posted by Gaboto View Post
I use Ubuntu 20.04
I had encountered similar, or maybe I should say identical issue, on a freshly install Ubuntu 20.04 on Lenovo X13. I am not sure if it's hardware related.

One thing I noticed in common is our laptop detected the new monitor as:

Code:
: new high-speed USB device number 10 using xhci_hcd
: New USB device found, idVendor=0bda, idProduct=5412, bcdDevice= 1.27
: New USB device strings: Mfr=1, Product=2, SerialNumber=0
: Product: 2-Port USB 2.1 Hub
: Manufacturer: Generic
: USB hub found
: 2 ports detected
: new full-speed USB device number 11 using xhci_hcd
: not running at top speed; connect to a high speed hub
: New USB device found, idVendor=0bda, idProduct=5450, bcdDevice= 0.06
: New USB device strings: Mfr=17, Product=18, SerialNumber=19
: Product: BillBoard Device
: Manufacturer: Realtek
This is puzzling. Based on the documentation it seems that the monitor's USB vendor ID should be 17e9

Code:
https://support.displaylink.com/knowledgebase/articles/683672-my-displaylink-device-does-not-work-on-ubuntu
I have tried the github manner, as well as installing the vanilla displaylink-driver-5.4.1-55.174.run. same observation.

Would greatly appreciate any advice / idea / pointer. Thank you.

PS: forgot to mention, the vanilla displaylink driver and the same Asus monitor works on a Dell laptop, fresh Ubuntu 20.04 installation. lsusb shows correct vendor ID on that Dell laptop

Last edited by johnsongw; Today at 08:49 AM. Reason: works on dell laptop
johnsongw is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 03:41 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2021, vBulletin Solutions, Inc.