Hacker News new | ask | show | jobs
by SmellyGeekBoy 3169 days ago
Not to mention HiDPI problems and serious issues with the proprietary nvidia driver. The situation is improving all the time though and hopefully this should mark the beginning of some good times for Wayland. More choice is always a good thing.

Of course, the option is right there on the login screen to start an X session instead, if Wayland doesn't work for you.

4 comments

I recommend everybody intending to run Linux to avoid nvidia GPUs. The experience with amd and intel GPUs is vastly superior.
I use nothing but Nvidia on Linux. Their performance and stability is greatly superior to AMD on high-end 3D applications such as Maya. I'll admit, I have not revisited AMD cards in a while, so perhaps I'm out of touch with the current generation. I also do not consider the open source nouveau driver to be acceptable. I've had too many problems with it in 3D apps.
But their proprietary driver is lagging behind a lot of the ecosystem. E.g. until recently their driver did not work with Wayland/mutter because NVIDIA was pushing their own device memory allocator (via the EGLStreams API). It seems that it now finally works, but is very slow.

In contrast, AMD is actively contributing to the open source amdgpu driver.

>until recently their driver did not work with Wayland/mutter because NVIDIA was pushing their own device memory allocator (via the EGLStreams API). It seems that it now finally works, but is very slow.

Can you give a source for this? I'd be very much interested in trying out Plasma on Wayland on NVIDIA, but I can't find any information about NVIDIA implementing GBM.

Yes, I wish Nvidia was a bit more generous with the open source community, but for some situations, they are the best choice, if not the only choice.
Your experience is not incompatible with the parent commenter's. On Linux, generally speaking, Intel > NVidia > AMD.
Unfortunately there's a lot of software that only runs on nvidia GPUs (anything that depends on CUDA, including tensorflow), so some of us really don't have a choice at the moment.
That's surprising since I've had a hell of a time getting GPU acceleration working on AMD cards while the nVidia cards hum right along with the nVidia driver. For some reason my AMD laptop apparently has blacklisted WebGL support which is a real bummer.
No issues with Gnome 3.26 HiDPI on Wayland using nvidia driver. I was running alpha version of 17.10 on my Dell XPS with minimal issues
Which generation XPS is that?
XPS 9560
I'm writing this on 17.10, a 1080Ti and a 4k monitor. Other than the lack of video acceleration in any browser (which is not specific to this setup), it's fine.
That's interesting, I was hoping for some improvements in HiDPI support with the shift to Wayland.
On a Debain sid install I was somehow recently bumped from Gnome3 on X11 toi Gnome3 on wayland. Chromium and Qt apps got broken scaling; I solved it by forcing the session to be Gnome3 on X11.

This is just anecdote of course! I would have liked to dig more into it and figure things out, but honestly I just had too much to do and chose whatever was working for me.

Have you tried again after upgrading to gnome-shell 3.26 (it's only been in Debian unstable for one week)?
Tried right now; QtCreator and chromium are still broken. Curiously, the former is super tiny and the latter huge!