|
05-14-2020, 11:57 PM | #1 |
Junior Member
Join Date: May 2020
Posts: 4
|
Update/workaround
Ok, an update. If I plug my xp13 laptop with a fresh install of 20.04 into my dell displaylink dock (D6000) and *don't* turn off the laptop monitor, everything is fast and useable. It's only if you either use the display settings to turn off the laptop screen (as you normally would for a docked laptop configuration) or physically close the lid of the laptop that everything goes glacial. Not a perfect fix, but at least it makes things workable again.
|
05-15-2020, 05:59 PM | #2 |
Junior Member
Join Date: Dec 2019
Posts: 9
|
|
05-27-2020, 08:27 AM | #3 |
Junior Member
Join Date: May 2019
Posts: 9
|
Has anyone else found that any applications on the laptop screen itself are very slow (under wayland)?
Code:
echo $XDG_SESSION_TYPE # to check which compositor you're using |
05-27-2020, 11:37 AM | #4 |
Junior Member
Join Date: May 2020
Posts: 2
|
I'm seeing the exact same issues from a desktop machine. If I have one monitor plugged in directly, the second monitor plugged into the docking station works. If they are both plugged into the docking station, it is so slow as to be unusable. This behavior is different than previous releases of Ubuntu when I would have to change the pageflip Display setting in xorg.conf.d. Now, the screen draws OK, the mouse moves around just fine; however, you have to hover over an icon for several seconds before you can click it, and wait several seconds after you click it for the interaction to be registered. The same with the keyboard: even in a pico editor each key strike takes several seconds to register in the terminal. For me, the DisplayLink driver only works for 1 monitor and then only if I am directly plugged into my video card for my primary monitor. This is less than optimal for me.
|
05-28-2020, 10:26 AM | #5 |
Member
Join Date: Jun 2018
Posts: 49
|
Is internal laptop's screen turned off? I noticed that on my laptop too. But only when my laptop's screen is turned off. When the laptop's screen is turned on, everything works without any problem.
|
08-26-2021, 11:01 PM | #6 |
Junior Member
Join Date: Jul 2021
Posts: 3
|
Workaround
This is fixed up stream on xserver-xorg-core now, the distros just have to merge the change.
there is a workaround right now by adding ``` LIBGL_DRI3_DISABLE=true ``` to your /etc/environment file |
10-09-2021, 10:21 PM | #7 |
Junior Member
Join Date: Oct 2021
Posts: 1
|
Works
Had to create an account to thank you. Not sure what this does but this solved my issue on ubuntu 20.04.3 , gnome 3.36.8 and windowing system x11. Thank you!
|
08-27-2021, 08:18 PM | #8 |
Junior Member
Join Date: Aug 2021
Posts: 1
|
Workaround with fixed kernel v5.4
For me one (bad) solution here works, I tried to describe it here as far as I have experienced it, my external monitors now worked:
https://askubuntu.com/questions/1358...-2021-after-up But that means going back to kernel v5.4 (probably also any kernel up to v5.5) and fix it there. You do not have to follow my steps to go to Ubuntu 21.04. At least I think this was only party of my way. The problem is that the sources of evdi has slightly changed to support modern kernels up to v5.13. Some pointer prototypes changed, But that would mean that just compiling and installing the new evdi driver would fix it for the new kernel >v5.11. But for my experiences that is not enough. External monitors are then detected but system freezes immediately after login. So I guess the DisplayLink App is somehow involved and must comply to the evdi interface. Is there any way to get to this sources to just fix this quicker? Last edited by peddanet; 08-27-2021 at 08:20 PM. |
09-02-2021, 10:37 AM | #9 |
Junior Member
Join Date: Sep 2021
Posts: 2
|
same here
I have the same problem, my second screen is really slow and my cpu is heating a lot.
I'm on Ubuntu 20.04 frsh install on a Asus vivobook laptop with a AMD Ryzen CPU. Closing or opening the lid does not change anything. I tried using X11 and Waylan with the same bad results. I don't know what to do, could DisplayLink fix the driver? |
|
|