New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xorg-server > 1.19 #133

Open
cacarr-pdxweb opened this Issue Jun 5, 2018 · 63 comments

Comments

Projects
None yet
@cacarr-pdxweb

cacarr-pdxweb commented Jun 5, 2018

Any information available on when DisplayLink will be compatible with xorg-server > 1.19.6 ?

With my AOC DisplayLink display plugged in, I can't log in, and when I plug it in after logged in, it kills the session and drops me back to the GDM login.

Apparently I need to downgrade to the following (have to use the Arch Linux Archive as I stupidly cleared my cache):

xorg-server-1.19.6+13+gd0d1a694f-2-x86_64.pkg.tar.xz
xf86-video-intel-1:2.99.917+823+gd9bf46e4-1-x86_64.pkg.tar.xz
xorg-server-common-1.19.6+13+gd0d1a694f-2-x86_64.pkg.tar.xz
xorg-server-xwayland-1.19.6+13+gd0d1a694f-2-x86_64.pkg.tar.xz
xf86-video-vesa-2.4.0-1-x86_64.pkg.tar.xz

I would prefer not to.

Whose problem is this? If xorg's, how long will I likely have to wait for a fix?

@MarcelPa

This comment has been minimized.

MarcelPa commented Jun 6, 2018

For me it was enough to only downgrade xorg-server to 1.19.6-2 (also on Arch Linux). The other components from X are still on Version 1.20, which keeps working for me for two Dell Displays on a Dell DisplayLink Dock.

@cacarr-pdxweb

This comment has been minimized.

cacarr-pdxweb commented Jun 6, 2018

@MarcelPa That's odd -- I ran into conflicts with xorg-server<1.20

In fact, I also had to downgrade xf86-video-fbdev.

Which party needs to fix the problem here?

@displaylink-dkurek

This comment has been minimized.

Contributor

displaylink-dkurek commented Jun 7, 2018

Just to check, have you checked this
https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades
or simply forcing modesetting driver with conf like

Section "Device"
  Identifier "DisplayLink"
  Driver "modesetting"
EndSection  

with 1.20?

@MarcelPa

This comment has been minimized.

MarcelPa commented Jun 7, 2018

I tried the following just now:
Disabling PageFlip with modesetting with xorg-server 1.20 -> did not work
Using the Intel DDX driver (xf86-video-intel) with xorg-server 1.20-> did not work
I fell back on using modesetting (by removing the intel driver and not installing any other) with xorg-server 1.19.6-2.

When I start X with version 1.20, I get the following error in my logs:
[ 31.535] (EE) modeset(G1): failed to set mode: No such file or directory

Additionally, systemd reports a dumped xore for Xorg. If needed, I can supply my logs from there too.

@jnvandermeer

This comment has been minimized.

jnvandermeer commented Jun 7, 2018

I can confirm that just the modesetting option in xorg.conf doesn't work for me (Arch Linux). In addition, removing the intel driver doesn't allow me to log into cinnamon.

My guess it's the people behind Displaylink who need to adapt in this case. And this will likely happen (my guess) once Ubuntu goes over to 1.20.

@Whax

This comment has been minimized.

Whax commented Jun 7, 2018

Same problem here with a fresh install and xorg-xserver 1.20 on an Acer S5-371T (7500U - Intel HD620).

To temporary fix it :

@MarcelPa

This comment has been minimized.

MarcelPa commented Jun 8, 2018

@Whax I use
pacman -Syu --ignore xorg-server
in order to update. It is a little bit of a hassle, but this keeps me remembering that I have an older version of xorg-server.

@displaylink-dkurek I guess that this is a new problem that does not relate to the link you posted (which relates to PageFlip behaviour in Xorg from 1.18.3 it says). Is there anything that can be done to narrow down the (new) problem?

By the way, I just noticed the following: on xorg-server 1.20 I am able to plug in the dock and all. It crashed the second I want to activate a monitor using xrandr. I am even able to create a new screen in X without crashing:
xrandr --output DVI-I-1-1 --left-of eDP1
works fine, I can put windows to the new screen, but the monitor itself stays black. Trying to turn that on with xrandr --output DVI-1-1 --auto will cause trouble. Dunno if that helps in any way.

@cacarr-pdxweb

This comment has been minimized.

cacarr-pdxweb commented Jun 10, 2018

Perhaps it would behoove folks involved with DisplayLink Ubuntu support to install Arch on a few machines, in order to assist in monitoring for upcoming issues. Current version on Bionic Beaver is 1.19.6-1 -- I get the impression you did not see issues with 1.20 coming?

@ScriptSmith

This comment has been minimized.

ScriptSmith commented Jun 13, 2018

I ended up needing to also install an old xf86-video-intel to get it working with i3

sudo pacman -U https://archive.archlinux.org/packages/x/xf86-video-intel/xf86-video-intel-1%3A2.99.917%2B829%2Bgd7dfab62-1-x86_64.pkg.tar.xz

And to get it to play nice with hardware-accelerated programs, deleted my config in /etc/X11/xorg.conf.d/, and then disabled vsync in my ~/.drirc

<device screen="0" driver="dri2">
	<application name="Default">
		<option name="vblank_mode" value="0"/>
	</application>
</device>
@badgumby

This comment has been minimized.

badgumby commented Jun 18, 2018

Also having this issue. Workaround is downgrading xorg-server.

@emilianosantucci

This comment has been minimized.

emilianosantucci commented Jul 4, 2018

Any news with the last version of xorg-server (1.20.0-9) ?

@MarcelPa

This comment has been minimized.

MarcelPa commented Jul 5, 2018

@emilianosantucci nope, Xorg log ends on the same error message as before "failed to set mode: no such file or directory". Just tested it on Linux 4.14 LTS (4.14.52-1-lts on Arch Linux).

@cacarr-pdxweb

This comment has been minimized.

cacarr-pdxweb commented Jul 27, 2018

It's been some time now -- any update?

@jnvandermeer

This comment has been minimized.

jnvandermeer commented Jul 27, 2018

@badgumby

This comment has been minimized.

badgumby commented Aug 7, 2018

I am still having this issue as well. I notice there haven't been any commits to this repo in well over a month.

@cacarr-pdxweb

This comment has been minimized.

cacarr-pdxweb commented Aug 8, 2018

@badgumby That does not inspire confidence.

@infabo

This comment has been minimized.

infabo commented Aug 23, 2018

Got 1.20 via Manjaro update yesterday. downgrading works for now.

@codextremist

This comment has been minimized.

codextremist commented Aug 29, 2018

Same here. I have been using low cost usb-c hubs now for several months which works flawlessly with Arch and Xorg > 1.20. Yesterday I decided to throw my DL on the garbage as it never really worked well for me

@stratosmacker

This comment has been minimized.

stratosmacker commented Aug 29, 2018

I collected some core dumps of getting thrown back to lightdm if anyone is interested

@Darkeye9

This comment has been minimized.

Darkeye9 commented Sep 10, 2018

@codextremist Could you please reference that adapter? I thought DP was the only real option to extend screens via USB. I don't have USB-C, but maybe I can source an UBS3 adapter with same chipset.

Thanks

@infabo

This comment has been minimized.

infabo commented Sep 12, 2018

@codextremist yes, please share.

@paco3346

This comment has been minimized.

paco3346 commented Sep 12, 2018

@Darkeye9 @infabo
The USB C version is actually just using the DP protocol over USB 3.1 so it's not actually USB. (The advantage here is that it's hardware driven and requires no drivers since it's literally seen as a physical display).

That being said- there's no way to make the USB C version work (since it doesn't support DL) on a non 3.1 port.

@codextremist

This comment has been minimized.

codextremist commented Sep 12, 2018

@infabo @Darkeye9
DisplayLink is just a shitty masterpiece! That being said, here are some cheap USB-C adapters:
https://wiki.archlinux.org/index.php/Talk:Dell_XPS_13_(9360)#USB-C_Compatibility_Chart

My personal choice was https://xiaomi-mi.com/accessories-for-laptops/xiaomi-usb-type-c-to-hdmi-multifunction-adapter/ . It's a cheap well constructed adapter

@Darkeye9

This comment has been minimized.

Darkeye9 commented Sep 12, 2018

Oh wow... So if I think correctly, users who do not have USB-C, cannot benefit from this adapter's direct display transmission system... Or it is possible to buy an USB3->USB-C->HDMI adapter?

Please shed some light on this topic, DisplayLink is indeed bullshit.

@codextremist

This comment has been minimized.

codextremist commented Sep 12, 2018

If your notebook has an USB-C 3.1 you can connect up to 2 external 4K monitors or a single 8k monitor to it. Both setups will work perfectly with XRandr. I'm not sure if there are USB 3.1 options available with other types of connections (i.e B and A).

@paco3346

This comment has been minimized.

paco3346 commented Sep 13, 2018

@Darkeye9

This is where the uniformity of USB gets tricky. There are 2 things to consider- the protocol and the physical connector.

  • USB 3.1 is a protocol that supports both the USB protocol and the Display Port protocol.

  • USB 3.0 is USB only and has nothing to do with Display Port.

  • USB-C is the only connector that supports USB 3.1.

The adapters @codextremist is referencing above are USB-C -> HDMI for physical connectors but DP -> HDMI for protocol (DP is backwards compatible with HDMI)

The genius of DisplayLink is that you can get another display without needing to add more video hardware. This was a win for laptop users because you can't just add a video card. The first 2 generations of DisplayLink adapters (USB 2 and then 3) were mostly seen on desks where you still had your typical 120v 19" LCD.

The next generation was portable screens. These were great because now the power was also coming from the USB port which meant you could use one in a coffee shop with literally only the USB cable.

With the advent of USB 3.1 and USB-C we've removed the need for DisplayLink because we're getting the benefit of direct hardware support (like plugging a monitor into your VGA or HDMI port) combined with the 5v power from USB.

@Darkeye9

This comment has been minimized.

Darkeye9 commented Sep 13, 2018

So I have nothing to do, as my USB 3.0 ports are not wired with the Graphics Hardware, right? The USB-C 3.1 ports have some sort of integration with the GPU in order to allow additional display protocols to flow through without the need of other SW/HW.

Is that all right? So I can only blame myself for not getting a laptop with USB-C connectors... I didn't know they worked so well to extend screens, even under Linux. I had so bad luck, that in my Dell Inspiron 15 7000 Gaming has the HDMI port hardwired to the NVIDIA card, and Linux has a lot of problems to use that output without some serious quirks...

Thanks for the information guys!

@runningnak3d

This comment has been minimized.

runningnak3d commented Oct 12, 2018

@scottgl9 That config did allow me to start X and "use" my DisplayLink screen. I put use in quotes because the cursor left artifacts all over both screens when it was moved.

I use Gentoo, and was testing with Xorg 1.20.1 using evdi driver 8eeb07a

I have a laptop with Nvidia Optimus, but I use nvidia-xrun so none of the Nvida drivers are loaded.

It is a good start, and I would love to get Xorg 1.20 working. 1.20 works MUCH better with the i965 driver.
Do you (or anyone here) have any idea how I could solve the cursor glitches?

This works perfectly with Xorg 1.19 (gotta love LVM snapshots to revert to ;) )

@Darkeye9

This comment has been minimized.

Darkeye9 commented Oct 16, 2018

@scottgl9 @runningnak3d That's right, and can be derived from stack traces when Xorg server crashes:

 Process 749 (Xorg) of user 0 dumped core.
                                                  
                                                  Stack trace of thread 749:
                                                  #0  0x00007feddb222d7f raise (libc.so.6)
                                                  #1  0x00007feddb20d672 abort (libc.so.6)
                                                  #2  0x000055d94ce2fcca OsAbort (Xorg)
                                                  #3  0x000055d94ce2fdbf FatalError (Xorg)
                                                  #4  0x000055d94ce3d34e n/a (Xorg)
                                                  #5  0x00007feddb222e00 __restore_rt (libc.so.6)
                                                  #6  0x00007feddb222d7f raise (libc.so.6)
                                                  #7  0x00007feddb20d672 abort (libc.so.6)
                                                  #8  0x00007feddb20d548 __assert_fail_base.cold.0 (libc.so.6)
                                                  #9  0x00007feddb21b396 __assert_fail (libc.so.6)
                                                  #10 0x000055d94cee6d49 dixRegisterPrivateKey (Xorg)
                                                  #11 0x00007fedd40fdc89 glamor_init (libglamoregl.so)
                                                  #12 0x00007fedd4a31f3d n/a (modesetting_drv.so)
                                                  #13 0x000055d94cf080bd AddGPUScreen (Xorg)
                                                  #14 0x000055d94ce0517c n/a (Xorg)
                                                  #15 0x000055d94cde82d6 n/a (Xorg)
                                                  #16 0x000055d94cdd61e9 n/a (Xorg)
                                                  #17 0x000055d94cdd6652 n/a (Xorg)
                                                  #18 0x000055d94ce389f1 n/a (Xorg)
                                                  #19 0x000055d94ce41410 WaitForSomething (Xorg)
                                                  #20 0x000055d94cdc388b n/a (Xorg)
                                                  #21 0x00007feddb20f223 __libc_start_main (libc.so.6)
                                                  #22 0x000055d94cdc42fe _start (Xorg)
                                                  
                                                  Stack trace of thread 788:
                                                  #0  0x00007fedda060afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                  #1  0x00007fedd7c39020 n/a (intel_drv.so)
                                                  #2  0x00007fedda05aa9d start_thread (libpthread.so.0)
                                                  #3  0x00007feddb2e6a43 __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 1063:
                                                  #0  0x00007fedda060afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                  #1  0x00007fedcb32c034 n/a (kms_swrast_dri.so)
                                                  #2  0x00007fedcb32bf78 n/a (kms_swrast_dri.so)
                                                  #3  0x00007fedda05aa9d start_thread (libpthread.so.0)
                                                  #4  0x00007feddb2e6a43 __clone (libc.so.6)

Is this a bug in Xorg? It is reported, or can be easily fixed?

I am not an expert in X11 gprahic drivers and so.. Can somebody clarify why it seems modesetting was used for a screen when X11 crashed trying to init glamor for it?
I always had the impression that modesetting was a debug thing and had horrible performance.

I am wondering these things, because after applying @scottgl9 patch, (that seems to imply that modesetting driver is to be used with DisplayLink screens, and setting the acceleration to NONE, effectively avoiding glamor from being used and thus, avoiding X11 crashes), I have some bad cursor artifacts happening with DisplayLink, that I did not have before this patch (And all of this X11 >1.19 debacle).

Any ideas, pointers, rants? I maybe happen to be of some use, since I am a software developer with C/C++ experience, but none in X11 graphics drivers ;)

@cacarr-pdxweb

This comment has been minimized.

cacarr-pdxweb commented Oct 18, 2018

Do I assume correctly that they just won't care about this until Ubuntu 19.04? Cosmic Cuttlefish is 1.20, and is released ... tomorrow, unless I'm mistaken?

@kugel-

This comment has been minimized.

kugel- commented Oct 26, 2018

Uhm while the workaround fixes the crash, the performance is unbearable on KDE with just one display (1920x1200). Like 0.3-1.0 fps.

And this is just on the desktop.

@Darkeye9

This comment has been minimized.

Darkeye9 commented Oct 26, 2018

While I don't know how it happened very reliably, I am enjoying my two 24' 1080p displays again with DisplayLink, in Arch Linux.

It happened after the last update, with relevant packages:
xorg-server 1.20.3-0
xorg-server-common 1.20.3-0
xf86-video-intel 1:2.99.917+847+g25c9a2fc-1

I realized it was working because at bootup my two displays powered on. (FYI: I had tried some patches suggested here, but at that time I had everything commented out, because it didn't work well). The performance was at the beggining the same as with the @scottgl9 patch. (Very bad, a lot of cursor glitches...). Then, somehow I managed to resolve it by changing the KDE compositor settings, and putting it back to Xrender, instead of OpenGL.

Eureka!! DisplayLink working like a charm with ZERO artifacts. I think it even works slightly better than before the blackout occurred this months...

@schrieveslaach

This comment has been minimized.

schrieveslaach commented Oct 27, 2018

I can confirm that evdi is working with xorg-server 1.20.3.

@jee-dev

This comment has been minimized.

jee-dev commented Oct 29, 2018

I deleted the evdidevice.conf, but still have the mouse artifacts. I would need some help how to solve the problem.

@a-sevin

This comment has been minimized.

a-sevin commented Oct 29, 2018

Indeed, it works better no more mouse artifacts but I still have an issue with the screen rotation...

@Darkeye9

This comment has been minimized.

Darkeye9 commented Oct 29, 2018

@jee-dev I fixed that by chaning the compositor settings. I am using KDE, so from the "start menu" just search for "compositor" and adjust the compositing software to Xrender, instead of OpenGL.

@a-sevin Sorry, but that was always an issue with Display link, wasn't it? I think it is not working even in Windows...

@a-sevin

This comment has been minimized.

a-sevin commented Oct 29, 2018

@Darkeye9 Tested on Windows, it works perfectly.

@tblancher

This comment has been minimized.

tblancher commented Oct 30, 2018

I just upgraded xorg-server-1.20.3-1 on Arch. My X cursor artifacts appear to be gone, with no extra effort on my part. However, my experience with artifacts were intermittent in prior versions. I will continue monitoring.

@paco3346

This comment has been minimized.

paco3346 commented Nov 7, 2018

I can also confirm that xorg-server-1.20.3-1 on Arch with xrender produces no cursor artifacts.

Other visual features such as window transparency weren't working with OpenGL on the DisplayLink display so I have 2 reasons to use xrender.

For anyone else looking for a simple copy/paste:
/etc/X11/xorg.conf.d/900-evdi.conf

# MBP integrated intel card, yours is probably different
Section "Device"
  Identifier  "intel"
  Driver      "modesetting"
  Option      "kmsdev" "/dev/dri/card0"
EndSection

# USB 3 DisplayLink monitor
Section "Device"
  Identifier  "USB3"
  BusID       "USB"
  Driver      "modesetting"
  # I have no other cards so this shows up as card1
  Option      "kmsdev" "/dev/dri/card1"
EndSection
@cacarr-pdxweb

This comment has been minimized.

cacarr-pdxweb commented Nov 8, 2018

I have an image now with xorg-server-1.20.3-1 -- but it's so screwed up I'm not even sure how to describe it -- the screen is squashed and is wrapping around the display multiple times, such that moving the (very distorted) cursor makes it travel to the top or bottom of the screen, and back out the other side.

Guess I'll have to go back over whatever modification it was that I made to a 99-evdi.conf to enable rotation (which was once working perfectly, prior to xorg-server update).

Or maybe I'll just throw this cruddy AOC monitor in a box and wait for Wayland compatibility -- or downgrade everything again. Grr.

Edit Working-ish now, except for rotation/portrait orientation is now broken -- I can select portrait in the Gnome display settings, but windows do not orient correctly. Which is a drag, because I really don't have any use for this display without portrait orientation.

@badgumby

This comment has been minimized.

badgumby commented Nov 14, 2018

After the latest Arch updates, dated 11/13/2018, my displaylink docking station is not working with my monitors anymore. I have downgraded Arch back to 11/09/18, and it is working again. I tried just downgrading Xorg-server, but it did not resolve it this time.

@davidbgonz

This comment has been minimized.

davidbgonz commented Nov 14, 2018

@badgumby This may be related to the most recent update to the 4.19 kernel. I am having the same issue on Arch after the 11/13/2018 updates. The LTS 4.14 kernel is still working. The issue is outlined here: #139

@infabo

This comment has been minimized.

infabo commented Nov 14, 2018

pity you still using displaylink...

@runningnak3d

This comment has been minimized.

runningnak3d commented Nov 14, 2018

Hey guys, @infabo has it figured out. He is going to go buy us all machines that have USB 3.1 Gen1 or Gen2 ports and then we don't have to fight with DisplayLink!

I am not really picky on brand as long as it is 17", with a Gen 9 Core i9, 32gigs of RAM, 1TB M.2 SSD, and an Nvidia 1080 GTX. I will PM you my address.

@numirias

This comment has been minimized.

numirias commented Nov 14, 2018

I'm following this thread for updates on the reported issue. Please keep the noise to a minimum and unrelated banter out of the thread.

@kugel-

This comment has been minimized.

kugel- commented Nov 19, 2018

FWIW, I could successfully keep OpenGL enabled by disabling vsync in the KDE compositor settings.

@ScottieD

This comment has been minimized.

ScottieD commented Nov 20, 2018

I had to run the following commands to restore displaylink
sudo pacman -U linux-4.18.10.arch1-1-x86_64.pkg.tar.xz linux-headers-4.18.10.arch1-1-x86_64.pkg.tar.xz virtualbox-host-modules-arch-5.2.18-11-x86_64.pkg.tar.xz; sudo grub-mkconfig -o /boot/grub/grub.cfg

@tryagains

This comment has been minimized.

tryagains commented Dec 9, 2018

So I installed a fresh version of Manjaro 18 xfce edition. I downgraded the xorg to xorg-server 1.19.6+13+gd0d1a694f-2

However, my DisplayLink monitor is still not working, its just random color pixels and when I unplug the monitor, my manjaro os freezes.

I checked my installed software and notice "xorg-server-common 1.20.3-1" is installed. Is this an issue?

I tried to remove it but it seems it will remove "xorg-server 1.19.6" too which I believe is required.

What can I do? anyway to trouble shoot this in a way so I can find the exact issue?

Also, Has anyone who installed Manjaro 18 gotten DisplayLink to work? please share how

@badgumby

This comment has been minimized.

badgumby commented Dec 9, 2018

@tryagains

This comment has been minimized.

tryagains commented Dec 9, 2018

What kernel are you running? I've noticed the newest kernel is giving me similar problems and had to downgrade to mid-November.
On Sat, Dec 8, 2018 at 7:51 PM tryagains ***@***.***> wrote: So I installed a fresh version of Manjaro 18 xfce edition. I downgraded the xorg to xorg-server 1.19.6+13+gd0d1a694f-2 However, my DisplayLink monitor is still not working, its just random color pixels and when I unplug the monitor, my manjaro os freezes. I checked my installed software and notice "xorg-server-common 1.20.3-1" is installed. Is this an issue? I tried to remove it but it seems it will remove "xorg-server 1.19.6" too which I believe is required. What can I do? anyway to trouble shoot this in a way so I can find the exact issue? Also, Has anyone who installed Manjaro 18 gotten DisplayLink to work? please share how — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#133 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AbiaeuZDYEUOOwbOWAf7o3ZyXSDiqK4pks5u3GyngaJpZM4UbwOi .
-- Andrew Smart

I am on 4.19.6-1-MANJARO

Do you also have "xorg-server-common 1.20.3-1" installed? im not sure if that could also be an issue

But yea it might be the kernel, which kernel are you on?

@badgumby

This comment has been minimized.

badgumby commented Dec 9, 2018

@tryagains

This comment has been minimized.

tryagains commented Dec 9, 2018

What kernel are you running? I've noticed the newest kernel is giving me similar problems and had to downgrade to mid-November.
On Sat, Dec 8, 2018 at 7:51 PM tryagains ***@***.***> wrote: So I installed a fresh version of Manjaro 18 xfce edition. I downgraded the xorg to xorg-server 1.19.6+13+gd0d1a694f-2 However, my DisplayLink monitor is still not working, its just random color pixels and when I unplug the monitor, my manjaro os freezes. I checked my installed software and notice "xorg-server-common 1.20.3-1" is installed. Is this an issue? I tried to remove it but it seems it will remove "xorg-server 1.19.6" too which I believe is required. What can I do? anyway to trouble shoot this in a way so I can find the exact issue? Also, Has anyone who installed Manjaro 18 gotten DisplayLink to work? please share how — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#133 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AbiaeuZDYEUOOwbOWAf7o3ZyXSDiqK4pks5u3GyngaJpZM4UbwOi .
-- Andrew Smart

I am on 4.19.6-1-MANJARO

Do you also have "xorg-server-common 1.20.3-1" installed? im not sure if that could also be an issue

But yea it might be the kernel, which kernel are you on?

EDIT:
I downgraded "xorg-server-common 1.20.3-1" to "xorg-server-common 1.19.6+13+gd0d1a694f-2"

I installed 4.14 kernel and booted into it. Same issue. Not sure if there was something else I was suppose to do besides just installing and rebooting into 4.14?

I think the issue is some other relevant packages installed that I have not downgraded yet

The Arch wiki mentions this warning
"You should downgrade your xorg-server and some relevant packages including but not limited to xf86-video-fbdev and xf86-video-intel to version 1.19.6 in order to make displaylinkAUR work"
https://wiki.archlinux.org/index.php/DisplayLink

However, I have downgraded but not sure what "some relevant packages" I might be missing?

again, the issue I face is when I plug in my USB monitor, the screen only displays streaks of colored pixels and if unplugged my whole OS freezes.

If anyone has any thoughts, ideas, guesses that would be greatly appreciated

@kugel-

This comment has been minimized.

kugel- commented Dec 9, 2018

Downgrading isn't necessary anymore

@wapsi

This comment has been minimized.

wapsi commented Dec 12, 2018

I can confirm this too. Xorg v1.20.3 works now but with "modesetting" driver only. When starting X with "intel" driver I'll get blank screen. Has anyone else tried with "intel" driver?

I've been using intel driver instead of modesetting because I've terrible screen tearing when modesetting is used. But this "workaround" doesn't work anymore. Has anyone else tried intel driver with Xorg v1.20.3?

And how about screen tearing with modesetting? In my setup it's so terrible that my desktop is almost unusable (2*2550x1440 external monitors via DisplayLink, laptop's own monitor is turned off).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment