Hello,
The driver I found (opi displaylink) breaks my Tumbleweed booting letting me without graphical interface. It works without adding a driver in Windows 10.
Details:
I just buy a second hand ASUS TUF 706IU computer.
This one have usb C and USB3 ports but no Display port one as had my previous laptop. Amd and Nvidia video cards.
Even more, some scan on the net shows the usb C port is not that video friendly.
I have a 4k monitor needed for some video editing (kdenlive) that uses the hdmi port, and need a other port to accommodate an other full HD monitor (total three displays).
After some disappointments with cheap brands not working at all, I ended up buying a WL-UG3501H Rev a device because on Amazon comments a Mint user said it worked.
it’s seen like this:
new SuperSpeed USB device number 4 using xhci_hcd
[16241.369088] usb 5-1: New USB device found, idVendor=17e9, idProduct=4301, bcdDevice=36.05
[16241.369098] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[16241.369102] usb 5-1: Product: USB3 to HDMI
[16241.369104] usb 5-1: Manufacturer: DisplayLink
[16241.369107] usb 5-1: SerialNumber: U3HD338838869
The opi found driver is probably this one:
https://software.opensuse.org/package/displaylink?search_term=DisplayLink
As I said, if I install the driver and reboot, the computer do not go to kde anymore.
I don’t know how to setup my computer to accommodate this new driver. All the threads on the subject here are pretty old, so this post
Thanks for your help.
@jdd_sysop:
First, welcome to the openSUSE Forums.
Now – those DisplayLink drivers for the USB – HDMI device are all private builds within the openSUSE Build Service – they’re not part of the community distribution.
- For support, you’ll have to contact the person who privately built the package you downloaded …
To get you system back up and running, you’ll have to remove that private build package.
- It may well be that, the USB – HDMI device is useable without the need for an additional driver –
Simply try it …
We need more details. First, provide output using ~~~ ~~~ to surround (one set of 3 above and one set below; alternatively, use PRE tags in same manner: </> icon) your paste of complete command input/output from inxi -GSaz run from konsole without the displaylink driver installed. Next, from having the displaylink driver installed, we need to see output from /var/log/Xorg.0.log. Do this thus: susepaste -e 10080 /var/log/Xorg.0.log and then provide here the resulting URL. This log must be from using the displaylink driver, though an additional one from not using the displaylink driver might be useful in a separate susepaste.
Are you able when booted using the displaylink driver to Ctrl-Alt-F3 to reach a command prompt? If yes, the above instructions ought to be sufficient. If not, you may need to use a rescue boot to acquire the log. Also, the log may need to be a prior one, Xorg.0.log.old, if you have trouble, and need to boot without the displaylink driver installed to capture a correct log.
Before going through all the above, strike the E key at the Grub menu and remove both quiet and splash=silent from the linu line, then append plymouth=0 before proceeding with boot per Grub instructions at menu’s bottom. This will enable extra boot messages to appear with possible clues to what is wrong. It might even allow your SDDM login menu to appear.
Appending nomodeset as you would plymouth=0 will disable the competent display drivers, hopefully causing a crude fallback to be employed, making the GUI passable for possible Plasma login. Plasma may fail to start this way, but very likely if you select an IceWM session from SDDM you would get a crude GUI to work with.
> inxi -GSaz
System:
Kernel: 6.2.9-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.0.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.2.9-1-default
root=UUID=b5f429c8-acdc-4254-92d0-0cafe6d4da37 splash=silent
resume=/dev/disk/by-uuid/7ca04441-6390-4731-8405-bbd952fe8606
mitigations=auto quiet security=apparmor nosimplefb=1
Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
Distro: openSUSE Tumbleweed 20230412
Graphics:
Device-1: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] vendor: ASUSTeK
driver: nvidia v: 525.105.17 alternate: nouveau,nvidia_drm non-free: 520.xx+
status: current (as of 2022-10) arch: Turing code: TUxxx
process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 3 speed: 8 GT/s lanes: 16 ports: active: none empty: DP-1
bus-ID: 01:00.0 chip-ID: 10de:2191 class-ID: 0300
Device-2: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel
arch: GCN-5.1 code: Vega-2 process: TSMC n7 (7nm) built: 2018-21 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1,eDP-1 empty: none
bus-ID: 06:00.0 chip-ID: 1002:1636 class-ID: 0300 temp: 39.0 C
Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
bus-ID: 1-4:9 chip-ID: 13d3:56a2 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
unloaded: fbdev,vesa alternate: nouveau,nv dri: radeonsi gpu: amdgpu
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1011x284mm (39.80x11.18")
s-diag: 1050mm (41.34")
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: right model: 22CV1Q
serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2
size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: eDP-1 pos: primary,left model: BOE Display 0x08be built: 2019
res: 1920x1080 hz: 120 dpi: 128 gamma: 1.2 size: 382x215mm (15.04x8.46")
diag: 438mm (17.3") ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 23.0.1 renderer: AMD Radeon Graphics (renoir LLVM
16.0.1 DRM 3.49 6.2.9-1-default) direct render: Yes
https://paste.opensuse.org/pastes/5559f2ccf507
no driver, the device is plugged in but not connected to any monitor
I will make the same after installing the driver, let me the time to do it and reboot 
Thanks
X logs:
https://paste.opensuse.org/9ab51014db24
inxi :
https://paste.opensuse.org/pastes/d5d23c363978
This one was what prevented openSUSE to boot: 20-displaylink.conf
May be created by a previous attempt to install ubuntu displaylink driver
That said. Having control after driver install / reboot, allows me to investigate more.
found the “systemctl start displaylink.service”
and the journalctl corresponding when failing
says module “evdi” is lacking
may be the module is somewhere in the displaylink driver, I see it in source, do I have to compile it?
also I know that a binary blob have probably to be loaded in the device, but is that still true? I have both the windows and the ubuntu drivers at hand, may be it’s inside,
see you tomorrow thanks
jdd
I have somewhere a github account, but I’m unable to use it for anything
valuable (I’m not a programmer :-()!).
That said I can make most of the steps by hand, but the github account
is very old (2016!!), the script do not works anymore.
present driver is displaylink-driver-5.6.1-59.run!! and the patch do not
apply of course.
I did the
chmod 755 displaylink-driver-1.1.62.run
./displaylink-driver-1.1.62.run --noexec --keep
cd displaylink-driver-1.1.62
(changing the driver name, of course)
but still the patch is too complicated for me.
I can follow this conversation every where it fit you, here, on
displaylink forum, on opensuse forum…
thanks
jdd