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 Code:
$ systemctl status displaylink Code:
Section "OutputClass" dmesg doesn't show DisplayLink: Code:
[ 1.226512] usb 4-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd Code:
$ lsusb Code:
$ uname -r |
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 |
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 |
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) |
Quote:
|
Quote:
|
Quote:
|
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>. |
Quote:
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 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 |
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. |
All times are GMT. The time now is 06:42 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.