| ikey | |
| Oct 30 2017, 5:39 PM |
| F1384091: Zrzut ekranu z 2017-12-23 18-55-36.png | |
| Dec 23 2017, 6:24 PM |
Just tracking this for myself so I don't forget tomorrow..
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Wontfix | None | T4235 Meta: Post-release blues | |||
| Resolved | ikey | T4901 Improve NVIDIA GL/EGL situation |
@ikey I was curious what your thoughts were on EGL-Streams. I know that KWin has refused to support them. Will that affect Budgies move to Qt?
blog post: https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/
@ikey @MrMonotone Looks like not only KDE refusing to support EGLStreams: http://sircmpwn.github.io/2017/10/26/Fuck-you-nvidia.html
XWayland probably will support NVIDIA EGLStreams next year with version Xorg 1.20: https://www.phoronix.com/scan.php?page=news_item&px=Xorg-Server-1.20-Features
Investigate plausibility of libglvnd. Would love to drop the filesystem butchery we currently do
@ikey are there currently any plans/WIP for libglvnd?
I just implemented it for Mesa (wasn't hard) : https://github.com/mati865/solus-glvnd
If this direction is appreciated I can prepare nvidia-glx-drivers to use it as well.
I've got EGL enabled but I'm going to dismiss glvnd until it matures significantly and all drivers support it. We support 304 + 340 and glvnd would break this right now.
Yknow what if we don't fix this before Solus 4 then I'm a complete and utter eejit.
@mati865 you have most experience here with glvnd - mind helping me plan how we do this?
@ikey I made final touches on nvidia-current, xorg-server, mesalib, libgvlnd and was about to send it when I was your comment TBH.
I have no idea what to do with 304 and 340, allow them to replace libglvnd libs maybe?
I dropped /usr/lib/glx-provider completely so Nvidia drivers are discovered by conf files in /usr/share/X11/xorg.conf.d/. It's similar to the Fedora and Arch but they are backporting few patches (merged in xorg 1.20; maintainers are hoping to release it in January) to have only 1 conf file instead of 2.
I can't tell about optimus but on the desktop it seems to work fine (tested with Garry's Mod). Should I resend diffs?
Well we need to plan what we're changing. LDM will need to lose the butcher approach (which makes my rewrite simpler tbh)
and we'll have to use the custom patch for xorg extension directory for nvidia. We can't allow any file replacement for any of
this to work properly, so we need glvnd working on all of them. We also need to deal with the obvious fallout which will be
the impact on snapd. :)
We can't allow any file replacement for any of this to work properly, so we need glvnd working on all of them.
So Arch way (replacing files for 304 and 340) doesn't fit and you cannot patch binary files to work with libglvnd.
Maybe Fedora way then?
All conflicting files are moved to /usr/lib/nvidia-340 and they are added to the PATH via ld.conf.so.d but I have no idea if it works for 32 bit libs.
Having plan of the changes surely would make this mess easier to understand.
Happy to now close this. We'll fix the bugs during the week before the sync (like the now broken snapd :P)
files/xorg.conf for nvidia-glx-driver-384.111 needs to be fixed, aside from that LGTM for desktop users.
Early adopters with Optimus laptops might get a bit angry but it should make things easier in the future.
Needs fixing how? Its working here and i'm using it. Also what do you mean optimus users might get a bit angry..?
My bad about nvidia-glx-driver, https://dev.solus-project.com/R2210:fca60614a17a5adbc40f9674c425c39748a4abdb wasn't linked to this task.
Also what do you mean optimus users might get a bit angry..?
I was talking about Early adopters.
I remember when Arch switched to libglvnd and broke Optimus for some users, then there was Ubuntu did it and again Optimus was broken OOTB for some users. I hope it will be smoother this time.
Ah right. Yeah I have an Optimus laptop which is working just like it did before. The main thing that is broken right now is snapd, but one thing at a time :)
What we need to do is try to make sure the always-on support is correctly prime synced, because I'm still experiencing some tearing (like before)