Originally posted by birdie
View Post
Announcement
Collapse
No announcement yet.
Ubuntu 22.04 LTS Changes Default For NVIDIA Driver Back To Using X.Org Rather Than Wayland
Collapse
X
-
Originally posted by piotrj3 View Post
Out-of-date is design here of Wayland.
(Yes, the above sentence is sarcasm. Yes, I was making a point.)
Look, it's perfectly simple. AMD, Intel, Qualcomm et. al. can make a driver that works with Wayland, and does so by collaborating on Mesa. Let's put aside that it is following a filthy non-optimal technology path that should die a thousand deaths. Are you saying that Nvidia is not competent enough to do what their competitors has been doing for years?
The market is screaming for a working Wayland render path. Nvidia, thus far, cannot provide one. The only explanations I can find are that Nvidia are either incompetent, or are otherwise doing their best to exert willful malice. Would love to be proven wrong though.
Now, thank you for pointing out that Wayland needs to be updated. Can you please develop a proof-of-concept on how to make a Wayland-like protocol that does have explicit sync and is compatible with Mesa?Last edited by wertigon; 25 April 2022, 08:53 AM.
Comment
-
Originally posted by skeevy420 View PostBasically, using gasoline and internal combustion engines is more environmental friendly than EVs and coal plants.Last edited by wertigon; 25 April 2022, 09:04 AM.
- Likes 1
Comment
-
Originally posted by JMB9 View Post
I am happy that you have a good experience with Wayland ... but there were still some functionality missing - and after revoking Wayland as default with Nvidia and SDL2
revoking Wayland by default, I don't think anybody can really say that Wayland is stable and has all X.org functionality as a subset.
There are still users complaining that X.org is still use as otherwise more development will go to Wayland ... and more bugs will show up.
But it is the other way round: on professional systems a change in a component is done when everything is better and proven so.
When KDE devs will say that the experience with KDE is better under Wayland than under X.org I will start thinking about a change - not before.
So we will see what is in KDE neon 'user edition' - and after my experience this will work - as those devs do care and really work with their system.
As I have hardened servers I know that X.org is a target - but I was also responsible for workstation and I never saw any problems with stability or security in real life.
And I am using X.org since 1994 on my Linux installations.
A script is something I (or an admin) puts on the system - so there is no security problem. You don't run things from Internet resources you do not know, right?
Otherwise there is no security at all. Root must know what she/he does - otherwise hell breaks lose. That's a professional system. And it works as proven by reality!
From my point of view X.org as extremely insecure which eats your date and put every personal bit you have on social media is just witch hunting.
If the share of Wayland would be well above 50%, we may see if this not so new kid on the block keeps its promises ... maybe, but we will see ...
And still using XWayland ... is this code bullet proof?
The problem is with Nvidia is that it has legitimately decided to continue on its proprietary driver path and is now having difficulty using wayland, they have the money to solve their problems, I don't think these problems need to be solved by the community that doesn't take a penny from Nvidia!
When you say that wayland still has some problems to solve it is true, but most of these are not from wayland, but they are compositing or missing bees and concern some specificities, such as some problems with the multimonitor, which by the way there I've also seen on Xorg etc.
In the world of open source if everyone sticks to the old just because it works, it wouldn't go on, users like not to pay and not contribute anything, but that way you don't go anywhere and unfortunately it limits development.
So it's obvious that if wayland doesn't work well for your needs, stick to Xorg, but if it works for you, it doesn't make any sense to stay on Xorg just because it's the default, because the default has to take into account so many things, which in the personal experience may be irrelevant.
Comment
-
Originally posted by birdie View Post
I don't freaking care about built-in GPUs. If we are talking about real GPUs NVIDIA is king by a huge wide margin, period.
The iGPUs matter because they're used as workstations *everywhere.* Who gives a shit about nvidia down at the bottom with less than 20%? They don't even register to people trying to get real work done in an office environment or on their home office PC.
Comment
-
Originally posted by Developer12 View Post
Sorry, but that's not how the world works. This is all about sheer market volume. Developers don't write applications and desktop environments for the most powerful GPUs, they write the for the most likely GPU some is to have on their desk. An intel i7 with an integrated GPU.
The iGPUs matter because they're used as workstations *everywhere.* Who gives a shit about nvidia down at the bottom with less than 20%? They don't even register to people trying to get real work done in an office environment or on their home office PC.
Intel being on "top" of the GPU market is akin to walking being on top of the movement market. Yeah, you can walk. Good luck walking to your job from your home which is located 10 miles away or going on vacation.
Ryzen 6000 mobile CPUs with RDNA2 graphics are somewhat usable for 1080p but their market share doesn't exist at the moment.
Stop putting crap into my years thank you very much.
Comment
-
Originally posted by wertigon View Post
The market is screaming for a working Wayland render path. Nvidia, thus far, cannot provide one. The only explanations I can find are that Nvidia are either incompetent, or are otherwise doing their best to exert willful malice. Would love to be proven wrong though.
- Likes 3
Comment
-
Originally posted by Ladis View Post
You not being able to find an explanation doesn't mean it doesn't exist (the explanation was already given - the implicit vs. explicit synchronization). Linux GPU market is mostly GPU compute servers, where NVidia is the king. Linux desktop is often broken and is usabe only for 1-2 % of people.
Since every other GPU vendor *does* care enough to implement a working Mesa driver that kicks Nvidia butt, this only reaffirms my stance to simply not buy Nvidia hardware for Linux use. I will continue to recommend AMD and Intel for Linux desktop until such a time Nvidia get their act together and start owning up.
And no, implicit / explicit synchronization is not a valid concern - If everyone else can do it in a vendor neutral way, that still means Nvidia is either incompetent, or they do not allocate enough resources to it (aka doesn't care). Or perhaps refusing to do it out of spite, at which point they're just being dicks.
Comment
-
Originally posted by wertigon View PostAnd no, implicit / explicit synchronization is not a valid concern - If everyone else can do it in a vendor neutral way, [...]
Unless you're seriously suggesting every hardware vendor whose drivers aren't implemented as a back-end of Mesa should either assimilate or die?Last edited by IndioNuvemChuva; 25 April 2022, 10:02 AM.
- Likes 2
Comment
-
Originally posted by IndioNuvemChuva View Post
How is it vendor neutral? Mesa is a driver vendor. q=
Unless you're seriously suggesting every hardware vendor whose drivers aren't implemented as a back-end of Mesa should either assimilate or die?
Comment
Comment