Skip to content
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.

Sign up for GitHub

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

Jump to bottom

xorg-server > 1.19 #133

Closed
cacarr-pdxweb opened this issue Jun 5, 2018 · 79 comments
Closed

xorg-server > 1.19 #133

cacarr-pdxweb opened this issue Jun 5, 2018 · 79 comments

Comments

@cacarr-pdxweb
Copy link

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
Copy link

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
Copy link
Author

cacarr-pdxweb commented Jun 6, 2018 •
edited
Loading

@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?

@cacarr-pdxweb cacarr-pdxweb reopened this Jun 6, 2018
@displaylink-dkurek
Copy link
Contributor

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
Copy link

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
Copy link

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
Copy link

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
Copy link

MarcelPa commented Jun 8, 2018 •
edited
Loading

@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
Copy link
Author

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
Copy link

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
Copy link

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

@emilianosantucci
Copy link

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

@MarcelPa
Copy link

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).

@mrTsjolder mrTsjolder mentioned this issue Jul 25, 2018
Merged
@cacarr-pdxweb
Copy link
Author

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

@jnvandermeer
Copy link

jnvandermeer commented Jul 27, 2018 via email

@badgumby
Copy link

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
Copy link
Author

@badgumby That does not inspire confidence.

@infabo
Copy link

infabo commented Aug 23, 2018

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

@codextremist
Copy link

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

@jesse-osiecki
Copy link

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

@Darkeye9
Copy link

Darkeye9 commented Sep 10, 2018 •
edited
Loading

@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
Copy link

infabo commented Sep 12, 2018

@codextremist yes, please share.

@paco3346
Copy link

paco3346 commented Sep 12, 2018 •
edited
Loading

@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
Copy link

@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
Copy link

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
Copy link

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
Copy link

@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
Copy link

Darkeye9 commented Sep 13, 2018 •
edited
Loading

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!

@kugel-
Copy link

kugel- commented Nov 19, 2018

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

@ScottieD
Copy link

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

@igoricegit igoricegit mentioned this issue Nov 25, 2018
Closed
@tryagains
Copy link

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
Copy link

badgumby commented Dec 9, 2018 via email

@tryagains
Copy link

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
Copy link

badgumby commented Dec 9, 2018 via email

@tryagains
Copy link

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-
Copy link

kugel- commented Dec 9, 2018

Downgrading isn't necessary anymore

@wapsi
Copy link

wapsi commented Dec 12, 2018 •
edited
Loading

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).

@innovate-invent
Copy link

Everything 'just works' upgrading Arch to 4.20.0-arch1-1-ARCH. There is a missing dependency for the evdi package and I had to ensure I have linux-headers installed before.
There is one gotcha, I had to remove iommu=on from the kernal parameters to get around this error: DMAR: Allocating domain for evdi.0 failed. I don't know if I should open a separate issue.

@badgumby
Copy link

badgumby commented Jan 4, 2019

Everything 'just works' upgrading Arch to 4.20.0-arch1-1-ARCH. There is a missing dependency for the evdi package and I had to ensure I have linux-headers installed before.
There is one gotcha, I had to remove iommu=on from the kernal parameters to get around this error: DMAR: Allocating domain for evdi.0 failed. I don't know if I should open a separate issue.

I didn't need to perform the kernel param change, but upgrading the linux kernel package (linux-4.20.arch1-1 [version: 4.20.0-arch1-1-ARCH]), along with the current 'linux-headers' package (linux-headers-4.20.arch1-1), and upgrading my 'evdi' package (evdi [version 1.5.1-2]) from the AUR has completely resolved my issues.

@innovate-invent
Copy link

innovate-invent commented Jan 4, 2019 •
edited
Loading

I didn't need to perform the kernel param change,

Do you have iommu=on in your kernel params? This usually appears on systems that do virtualization.

@badgumby
Copy link

badgumby commented Jan 4, 2019

I did not have it in there.

@AdnanHodzic AdnanHodzic mentioned this issue Jan 9, 2019
Closed
@runningnak3d
Copy link

runningnak3d commented Jan 11, 2019 •
edited
Loading

So I finally decided to risk it, and upgraded to Xorg 1.20.3. I used the devel branch -- specifically c7e80bc (haven't checked to see if there have been more commits) and built it -- and viola...

I was even able to re-enable glamor acceleration. ZERO screen issues. ZERO cursor issues. Added bonus is the acceleration, and having drop shadows back.

I run Gentoo if anyone has any specific questions.

-- Brian

@tryagains
Copy link

Okay, I went ahead and updated to the newest xorg, however, seems to have broken DisplayLink for me.

I get a corrupted rainbow pixelated screen display. Or this one time just a black screen

Did anyone here have to do anything else besides just update to Xorg 1.20.3?

Also does anyone know how to trouble shoot this as I am not certain what is the issue on my end.

DisplayLink was working on xorg 1.19 on 4.19.13-1-MANJARO. (displaylink also works on WIndows 10 but that is probably irrelevant)

Just doesn't seem to be working on xorg 1.20.3.

@runningnak3d
Copy link

@tryagains What version of the evdi module are you using?

@tryagains
Copy link

@tryagains What version of the evdi module are you using?

evdi 1.5.1-2

I do notice evdi has optional dependencies like
"linux-lts-headers: build modules against the LTS kernel"

That I can't install, I get error "target not found: "

Not sure if that is relevant tho as it seems I have
"linux-headers: build modules against the Arch kernel"
installed

@runningnak3d
Copy link

@tryagains So you are trying to compile the devel branch (that is what I know works with 1.20.3 -- even tearing is gone)?

If so, what kernel version do you have installed? I know it compiles fine with 4.18.5 as long as you have the headers installed. I have not tested with any older or newer kernels (although it should work fine with any 4.18.x kernel) because I have some patches for work equipment that I don't feel like porting yet.

I know that others have had some success with 4.19.x, but (and anyone can feel free to correct me), I believe there are still issues with 4.20.x.

So again, my setup that works great is:

Xorg 1.20.3
Kernel 4.18.5
modesetting driver for Displaylink (Intel driver has issues)

Here is my DisplayLink xorg.conf

cat /etc/X11/xorg.conf.d/21-displaylink.conf 
Section "Device"
  Identifier "DisplayLink"
  Driver "modesetting"
  Option "accelMethod" "glamor"
  Option "PageFlip" "true"
EndSection

@wapsi
Copy link

wapsi commented Jan 14, 2019

@runningnak3d : Do you mean the issues with evdi module in 4.20? There's a patch already to fix them: #145

And another question: Did you get rid of the tearing with modesetting driver? I'm still using Xorg 1.19 because intel driver still works. With 1.20.3 the intel driver is broken if it's being used with DisplayLink (black screen). And with all Xorg versions I've tested + DisplayLink the modesetting driver gives me a ridiculous amount of tearing.

@runningnak3d
Copy link

@wapsi I have not been able to test any kernel newer than 4.18.5 due to some custom patches that I have to use for some internal hardware. So my comments about 4.20 were based on what I have read on here, and some other support sites. Glad to know that there is a patch because I will be porting my patches ASAP. I was going to wait for 5.0 to drop, but might as well get a head start.

I have no tearing once I enabled glamor -- scrolling is butter smooth. My entire DisplayLink conf is pasted above.

@tryagains
Copy link

@tryagains So you are trying to compile the devel branch (that is what I know works with 1.20.3 -- even tearing is gone)?

If so, what kernel version do you have installed? I know it compiles fine with 4.18.5 as long as you have the headers installed. I have not tested with any older or newer kernels (although it should work fine with any 4.18.x kernel) because I have some patches for work equipment that I don't feel like porting yet.

I know that others have had some success with 4.19.x, but (and anyone can feel free to correct me), I believe there are still issues with 4.20.x.

So again, my setup that works great is:

Xorg 1.20.3
Kernel 4.18.5
modesetting driver for Displaylink (Intel driver has issues)

Here is my DisplayLink xorg.conf

cat /etc/X11/xorg.conf.d/21-displaylink.conf 
Section "Device"
  Identifier "DisplayLink"
  Driver "modesetting"
  Option "accelMethod" "glamor"
  Option "PageFlip" "true"
EndSection

I am on kernel 4.19.13

I am not sure what compiling the devel branch entails, I just update from xorg 1.19 to 1.20 and it seems to not work.

I didn't need to edit any conf file on 1.19 but I have tried yours and others conf and it still seems to not work.

Sticking to 1.19 for now,

Also i should warn for others that be careful editing the conf files, it could cause issues, Like I think I created 21-displaylink.conf and forgot to delete 20-displaylink.conf and my screen was blank on reboot

@runningnak3d
Copy link

If you don't compile the latest version of the evdi module, it won't work, and again, I haven't tested with kernels greater than 4.18.5 yet.

You should Google how to compile a kernel module for Arch -- I am sure there are some great howtos out there.

@strix
Copy link

strix commented Feb 1, 2019

Everything is working properly for me now without any manual configuration on my end on

kernel 4.19.16-1-MANJARO
evdi 1.5.1-2
xorg-server 1.20.3-1

I'm using a Lenovo Thinkpad (6th generation) if that matters

@tblancher
Copy link

tblancher commented Feb 2, 2019 via email

@geostar1024 geostar1024 mentioned this issue May 5, 2019
Closed
@eyJhb eyJhb mentioned this issue Jun 8, 2019
Closed
@displaylink-dkurek
Copy link
Contributor

Seems it has been settled down, but we will probably see more problems with new xorg versions. If this will happen please create new issue. Closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests