08-01-2021, 09:47 AM | #1 |
Junior Member
Join Date: Aug 2021
Posts: 1
|
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 1. Install evdi: Code:
# dkms status evdi, 1.9.1, 5.12.14-arch1-1, x86_64: installed 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 Code:
Section "OutputClass" Identifier "DisplayLink" MatchDriver "evdi" Driver "modesetting" Option "AccelMethod" "none" Option "PageFlip" "false" EndSection 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 Code:
$ lsusb Bus 004 Device 009: ID 0bda:0412 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub Code:
$ uname -r 5.12.14-arch1-1 $ pacman -Qi xorg-server | grep Version Version : 1.20.11-1 |
08-12-2021, 04:17 PM | #2 |
Junior Member
Join Date: Aug 2021
Posts: 4
|
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. |
08-12-2021, 05:05 PM | #3 |
Junior Member
Join Date: Aug 2021
Posts: 4
|
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 Code:
./displaylink-driver-5.4.0-55.153.run --noexec --keep Code:
cd ./displaylink-driver-5.4.0-55.153 Code:
curl -L https://github.com/DisplayLink/evdi/archive/refs/heads/devel.tar.gz -o evdi.tar.gz Code:
if ! tar xf "$TARGZ" -C "$EVDI"; then Code:
if ! tar xf "$TARGZ" -C "$EVDI" --strip-components=1; then Last edited by karly; 08-23-2021 at 05:25 PM. Reason: add -L to curl |
08-18-2021, 04:20 PM | #4 |
Junior Member
Join Date: Aug 2021
Posts: 2
|
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) |
08-23-2021, 05:24 PM | #5 | |
Junior Member
Join Date: Aug 2021
Posts: 4
|
Quote:
|
|
08-25-2021, 03:46 PM | #6 | |
Junior Member
Join Date: Aug 2021
Posts: 2
|
Quote:
|
|
08-26-2021, 07:54 AM | #7 |
Junior Member
Join Date: Aug 2021
Posts: 4
|
|
09-16-2021, 12:18 PM | #8 |
Junior Member
Join Date: Feb 2019
Posts: 6
|
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>. |
09-25-2021, 08:48 AM | #9 |
Junior Member
Join Date: Sep 2021
Posts: 1
|
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 Code:
https://support.displaylink.com/knowledgebase/articles/683672-my-displaylink-device-does-not-work-on-ubuntu 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; 09-25-2021 at 08:49 AM. Reason: works on dell laptop |
10-21-2021, 09:33 AM | #10 |
Junior Member
Join Date: Oct 2021
Posts: 1
|
I am dealing with monitor issues as well, with a quite different scenario, on a totally different system, but it seems to me that the kernel is not seeing the monitor's DisplayLink chip, or it would show in lsusb.
My experience is with a DoubleSight monitor on ArchLInuxArm, which is quite different than your systems, but still, I would expect the monitor to show up, even if it is not attached to the correct driver. Instead, it is shown as a hub? Possibly it is not getting enough power? Is it plugged in to a hub? Have you seen lsusb output, and especially lsusb -t output, for someone who has gotten this monitor to work on Ubuntu? I bet that in the device tree, DisplayLink will show up. Also, try lsusb -t on your system without the DisplayLink plugged in - If lsusb -t looks the same, then it is not getting seen by the kernel. Another possibility is that the device and product ID are not interpreted properly, it should be seen as an I/O device even if it is not claimed by any driver, I believe. EDIT: Did a bit of googling, did not come up with an answer but it seems important to look at information about "Billboard Devices". There may be power issues, because of how various USB standards work. Also look at Power Delivery issues (abbreviated PD). It may require some sort of docking station to resolve them. Last edited by sdjf; 10-21-2021 at 10:19 AM. Reason: Additional ideas |
|
|