DisplayLink Forum

DisplayLink Forum (https://displaylink.org/forum/index.php)
-   Linux and Open Source (https://displaylink.org/forum/forumdisplay.php?f=29)
-   -   Ubuntu 16.10 support (https://displaylink.org/forum/showthread.php?t=65044)

asdfwadfawdf 01-06-2017 02:16 PM

Ubuntu 16.10 support
 
I upgraded from 16.04 to 16.10 with unity, displaylink barely works.

1) Chrome is so sluggish on displaylink screen. It works fine on every other screen
2) x-org crashes a lot

I tried gnome, the screen size created is smaller than actual 3 physical screens..

Sparxy 01-10-2017 08:22 AM

The displaylink issue with chrome can be worked around by disabling hardware acceleration or disabling vsync in chrome.
From what I can tell OpenGL appears to VSync to 1Hz (1 frame per second) on DisplayLink devices.
Disabling hardware acceleration can be done through the settings. To just disable VSync you can edit the shortcut and add
env vblank_mode=0
at the start of exec, i.e. Exec=env vblank_mode=0 /usr/bin/google-chrome-stable

asdfwadfawdf 01-13-2017 06:42 PM

Quote:

Originally Posted by Sparxy (Post 82413)
The displaylink issue with chrome can be worked around by disabling hardware acceleration or disabling vsync in chrome.
From what I can tell OpenGL appears to VSync to 1Hz (1 frame per second) on DisplayLink devices.
Disabling hardware acceleration can be done through the settings. To just disable VSync you can edit the shortcut and add
env vblank_mode=0
at the start of exec, i.e. Exec=env vblank_mode=0 /usr/bin/google-chrome-stable

The problem affects more than just Chrome. SecureCRT, Gnome Terminal, Sublime are also affected just not as obvious as Chrome.

asdfwadfawdf 01-23-2017 01:54 AM

And the latest driver did not generate X config. How can I create a X config from xrandr script?

mlukaszek 01-25-2017 10:56 AM

Quote:

Originally Posted by asdfwadfawdf (Post 82455)
The problem affects more than just Chrome. SecureCRT, Gnome Terminal, Sublime are also affected just not as obvious as Chrome.

This is a problem in X, which we will be reporting. Anything that uses reverse PRIME would be affected.

Can you can see if the performance is normal if at least one line of a window is on a non-DisplayLink screen, and only once it's fully moved to USB connected screens then you start to see the problem?

Regards,
Michal

RussianNeuroMancer 02-11-2017 02:44 AM

Quote:

Originally Posted by mlukaszek (Post 82551)
only once it's fully moved to USB connected screens then you start to see the problem?

This is what happening for me with default DDX (modesetting DDX with DRI3 and GLAMOR acceleration) however this is not reproducible with intel DDX (with DRI2 and SNA acceleration).

Could you please take a look at this one?


All times are GMT. The time now is 06:06 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.