NVIDIA MX150 (560.35.03) not working on Ubuntu 24.10 (Kernel 6.11, Gnome 47) with Wayland

Hi folks.

I just installed Ubuntu 24.10 (kernel Linux 6.11.0-8-generic, Gnome 47). The NVIDIA driver 560.35.03 was automatically installed.

I am using a Lenovo Thinkpad T480 (Intel® Core™ i7-8650U × 8, 32Gb RAM, 1Tb SSD) with integrated Intel® UHD Graphics 620 (KBL GT2) and dedicated GPU NVIDIA GeForce MX150 (Pascal architecture).

My NVIDIA GPU is not working on Wayland and it is working with serious problems on Xorg. When I try to use Xorg, some apps delay a lot to open, sometimes never open, and open with the light theme (since I configured it for the dark theme). I tried “Reset to Default” on Gnome Tweaks and it didn’t resolve the problem. So, on Wayland the NVIDIA GPU is not working and on Xorg I am having serious problems in opening and using the apps.

The softwares for video edition Kdenlive (24.08.1) and DaVinci Resolve (19.0.2) recognizes but doesn’t use the NVIDIA GPU on Wayland. Curiously, DaVinci Resolve runs and recognizes the NVIDIA GPU on Wayland, but shows up the message “Your GPU memory is full” all the time (I guess DaVinci Resolve is not using the NVIDIA GPU in fact). My main goal is to use my NVIDIA GPU for video editing.

The option “Intel (Power Saving Mode)” is not able to be selected on NVIDIA Settings. I tried the option “NVIDIA (Performance Mode)” and nothing changed on Wayland.

I already tested the 550 and the 560-open drivers without success. I also installed all the available nvidia* packages via apt without improvements or better results.

For the Xorg, I tried to use the xorg.config file generated by nvidia-xconfig and also generated by the nvidia-settings. With both files the system crash and the Xorg session doesn’t start after the login screen. The Xorg is starting without xorg.config file, so that, I guess the Xorg is auto-detecting the settings to start.

I wrote a full report to linux-bugs@nvidia.com with the nvidia-bug-report.log.gz file attached. While I didn’t receive some answer, I am looking for some solution to use my NVIDIA on Wayland and/or to fix the problems to use it on Xorg.

Tips are welcome.

For more information and collaborations, this same post was also published at:

UPDATES

NVIDIA MX150 not working on Ubuntu 24.04/24.10 (Gnome 46/47) on Wayland and has issues on Xorg

Summary:
NVIDIA MX150 (notebook) hybrid GPU not working on Ubuntu 24.04/24.10 with Gnome/Wayland and experiencing significant issues on Gnome/Xorg. So, it is not possible to use the NVIDIA GPU in a satisfactory way in Wayland and Xorg.

Software Versions:

  • Ubuntu 24.04, GNOME 46, Kernel 6.8.0-47-generic, NVIDIA Driver 550.107.02
  • Ubuntu 24.10, GNOME 47, Kernel 6.11.0-8-generic, NVIDIA Driver 560.35.03
  • Kdenlive (24.08.1) flatpak (both)
  • DaVinci Resolve (19.0.2) from Blackmagic website (both)

Hardware Information:

  • Device: Lenovo ThinkPad T480
  • CPU: Intel® Core™ i7-8650U × 8
  • RAM: 32 GB
  • Storage: 1 TB SSD
  • Integrated GPU: Intel® UHD Graphics 620
  • Dedicated GPU: NVIDIA GeForce MX150 (Pascal architecture)

Issues:

  • On Wayland:
    – GPU NVIDIA not working.
    – Kdenlive do not reconize NVIDIA GPU.
    – DaVinci Resolve recognize but do not use NVIDIA GPU.
    – DaVinci Resolve shows “Your GPU memory is full” message all the time.

  • On Xorg:
    – Gnome GTK4 (libadwaita) apps delay a lot to open, sometimes never open, and open with the light theme (since the system is configured for dark theme). “Reset to Default” on Gnome Tweaks didn’t resolve the problem.
    – Crashes when using xorg.config files generated by nvidia-xconfig or nvidia-settings.

Additional Information:

  • Intel (Power Saving Mode) option in NVIDIA Settings it is not selectable (gray color) on Wayland and Xorg.
  • Used NVIDIA (Performance Mode) with no changes on Wayland.
  • Tested drivers 550 and 560-open on Ubuntu 24.10 without success.
  • Installed all available vidia packages via apt with no improvements.
  • Xorg is starting without xorg.config file (auto-detecting the settings).
  • Similar issues found on Debian 13 Trixie Testing with Gnome 47.
  • The issues with GTK4 (libadwaita) apps were not observed on Pop_OS 22.04 with Gnome 42.6.
  • nvidia-bug-report.log.gz (Ubuntu cases) already sent to linux-bugs@nvidia.com.

For collaboration, also published at:

I have similar problems with a Nvidia MX330 , 560.35.03, and Ubuntu 24.10.

Let me respond to some of your points…

On Wayland:
This doesn’t work in “Performance Mode”. gnome-shell is the only process showing as accelerated.

On Xorg:
In “Performance Mode”, I can’t open folders on my Desktop. “On-Demand” works fine. I suspect the 560 driver. Still testing.
The Nvidia xorg.config file shouldn’t be used. It WILL crash.

See Ubuntu 24.10 under Wayland, and Nvidia - Ask Ubuntu

Cheers, Al

I have a very similar problem.

Details like you: My hardware is a notebook Lenovo Thinkpad T580 (yes, a 5! Because 15", if not known …) with CPU Intel® Core™ i7-8550U × 8, 24GB (not Gb, which would be Gigabit) RAM, 0.5TB (not Tb … same as mentioned) SSD). Normally this details should not be important.
As graphic cards it has an integrated Intel® UHD Graphics 620 (KBL GT2) and dedicated GPU NVIDIA GeForce MX150 (Pascal architecture) installed.

The last detail tells that we have surely the same problem.

But a driver works and this is 535.

Wayland is not the same as X11, so nvidia-settings performance mode surely do not work, as they seem to be for X11. From terminal I call my developed app with ‘@__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./releaseApp’ (yes, completely with @ and so on, but without '), then my app starts with rendering from MX150 with closed source driver. So that shall be a solution for you, if you (surely) can execute the app from terminal (advice, if you are a novice in bash and those terminal things: write space and ‘&’ (without ') after command, then terminal keeps being usable and it keeps getting error logs and so on from executed app).

Now I have to write a full report to NVIDIA as theoretically this dedicated card shall be supported by the driver. Any help is appreciated (sorry, I do not know now how to report and what they need).

EDIT: I use Ubuntu 24.04.1 (with latest updates and Pro updates) and run development editor under Wayland (nvidia-settings performance works perhaps , when Gnome with X11 started - earlier try: 550 works there also, but window manager suddenly does not use dark mode in Gnome … strange, although Wayland shall be less supported in 535).

Simlar. I use Dell I7-11, 32G, 1T SSD, MX330 w/550.127.01 driver. Ubuntu 24.10.

For Xorg, I installed Nemo, and then changed pref in ‘Desktop Icons NG (DING)’ to use Nemo. Now I can open files/folders on the Desktop.

Besides the Nautilus/folder issue, I find that flutter apps like Plex, and Security Center don’t run.

For Wayland, it appears that ‘prime-select’ and ‘nvidia-settings’ don’t work properly. ‘nvidia-smi’ may not report properly in Wayland either.

To report a bug, first do ‘sudo sh /usr/bin/nvidia-bug-report.sh’ and upload it to the Dev Forum.

2 Likes

Thank you, I will do this as soon as I have more time. :-)

Short answer… the NVIDIA drivers are a mess.

Three workarounds… pick one…

  • run NVIDIA in On-Demand mode in Xorg

  • install Nemo and switch prefs in the “Desktop Icons NG” (DING) extension to use Nemo in Xorg

  • use Wayland with NVIDIA in Performance Mode.

1 Like

@shabapiffer (and naturally all others) can use 535 with wayland. Then start desired app with nvidia driver support in terminal with (as said above) [quote=“monoworks.com, post:4, topic:309548”]
‘@__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia desiredApp’
[/quote].

This works for the features I need in developing. Perhaps more advanced features like Tesselation in OpenGL 4 will make more problems, but luckily I have a Thinkpad P16g2 with RTX 3500 Ada now. There 550 seems to work (there I am able to move my object without delays). And if important features are missing, I hope 560 will be released soon (officially by ubuntu, not by additional ppa, where this shall be already possible). And if I have bad luck, I need 565 or something later, but I hope not.

For old Thinkpad perhaps I have to switch back to X11 and deactivate dark mode, as this does not work. Perhaps then 550 also works calling app and windows appear without huge delays. But I do not know this yet.

@shabapiffer Im having the exact same problem with nvidia 3060, driver 560 and 24.10 wayland does not go using the gpu to render making some kind laggy on my second screen,

and having the other same problems as you do

“My NVIDIA GPU is not working on Wayland and it is working with serious problems on Xorg. When I try to use Xorg, some apps delay a lot to open, sometimes never open, and open with the light theme (since I configured it for the dark theme). I tried “Reset to Default” on Gnome Tweaks and it didn’t resolve the problem. So, on Wayland the NVIDIA GPU is not working and on Xorg I am having serious problems in opening and using the apps.”

totally the same,

did you find any solution for this? or we have to pray for an update from nvidia or the guys from wayland :(

Hi @1mm.villanueva1.

So, the solution I found was selling my NVIDIA GPU laptop and switched to one with an AMD GPU instead.

Everything’s working perfectly now—for both video editing and 3D gaming. AMD’s Linux drivers are way more advanced and functional than NVIDIA’s at the moment.

I just couldn’t wait around for NVIDIA to fix things.

I have read some news that NVIDIA is working on solutions for Wayland, Vulkan, and dual-GPU laptops (integrated + dedicated), but honestly, I have no clue when those will actually roll out.

It’s wild how NVIDIA, one of the richest big tech companies in the world, still doesn’t offer solid support for Linux. You’d think they could just hire a small team—like 3 or 4 engineers—to focus solely on Linux drivers and solutions.

just to update this thread, downloding the driver NVIDIA-Linux-x86_64-550.144.03.run from the official nvidia site did the job for me, everything looks its working on wayland. also I have to disabled UEFI secure boot.