The driver I found (opi displaylink) breaks my Tumbleweed booting letting me without graphical interface. It works without adding a driver in Windows 10.
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
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.