DisplayLink Forum

DisplayLink Forum (https://www.displaylink.org/forum/index.php)
-   Linux and Open Source (https://www.displaylink.org/forum/forumdisplay.php?f=29)
-   -   Broken behaviour (https://www.displaylink.org/forum/showthread.php?t=64368)

safarik 02-12-2016 08:21 AM

Broken behaviour
 
1 Attachment(s)
Hello,

I had displaylink screen working mostly ok on Debian testing / XPS 13 / DA100.
(more details here http://displaylink.org/forum/showthread.php?t=64259)

But recently I encouter broken behaviour meaning:

- cursor often creates digital artefacts / displays old position (see attachment)
- context menus does not open on curso position but on second screen or not visible at all

I think (but I am not 100%) that is it due to update of the xorg. Currently the versions in my system are:

xorg 1:7.7+13
xserver-common 2:1.18.0-3
xserver-xorg 1:7.7+13
xserver-xorg-core 2:1.18.0-3
xserver-xorg-video-all 1:7.7+13
xserver-xorg-video-intel 2:2.99.917+git20160127-1+b1

And in the dmesg output I see:

Code:

[42506.905376] [D] evdi_painter_connect (dev=1) Connected with ffff880232cff000
[42506.905381] [D] evdi_painter_connect (dev=1) Edid (3 bytes): 00 ff ff
[42506.905396] [D] evdi_detect (dev=1) Painter is connected
[42506.907168] [D] evdi_detect (dev=1) Painter is connected
[42506.907174] [D] evdi_painter_get_edid (dev=1) 00 ff ff
[42506.932611] [D] evdi_painter_mode_changed_notify (dev=1) Notifying mode changed: 1920x1200@60; bpp 32; pixel format 875713112
[42506.932693] [D] evdi_painter_crtc_state_notify (dev=1) Notifying crtc state: 1
[42506.932700] [D] evdi_painter_dpms_notify (dev=1) Notifying dpms mode: 0
[42507.077693] [D] evdi_detect (dev=1) Painter is connected
[42507.077698] [D] evdi_painter_get_edid (dev=1) 00 ff ff
[42507.117155] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.121274] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.263145] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.263538] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.267098] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.269880] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.273112] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.276066] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.296656] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.297459] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42507.302540] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f
[42537.738362] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xbb, supported mask 0x7400003f


I tried both versions of displaylink driver 1.0.138 and 1.0.335

Thanks for any help,

Tomas Safarik

AndyC 02-12-2016 04:46 PM

On fedora the menu displaying on the wrong screen is fixed by downgrading Xorg. There are other posts on that.

But the pointers being left all over the screen still exists, making it unusable.


All times are GMT. The time now is 11:12 AM.

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