mga9-64 OK here

GPU: nvidia GTX750Ti

Was using nvidia 470
used MCC -> drakx11 to switch to nvidia-current
Added using drakpm:
- nvidia-current-cuda-opencl-535.154.05-1.mga9.nonfree.x86_64
and rebooted -> Now CUDA and OpenCL is detected OK in BOINC.

Kernels:
Above with kernel 6.6.11-desktop-1.mga9
also now tested 6.5.13-desktop-6.mga9
and kernel linus 6.5.13-2.mga9

__Tested OK for each kernel:
Plasma X11, and various apps incl video in Firefox.
Suspend-resume
Virtualbox 7.0.14 running MSW7 64bit guest with desktop apps incl firefox video

In all tests new mesa was used, tainted variant.
Bug 32759 - Update request: mesa 23.3.3

$ dkms status | sort
nvidia-current, 535.154.05-1.mga9.nonfree, 6.5.13-2.mga9, x86_64: installed
nvidia-current, 535.154.05-1.mga9.nonfree, 6.5.13-desktop-6.mga9, x86_64: installed
nvidia-current, 535.154.05-1.mga9.nonfree, 6.6.11-desktop-1.mga9, x86_64: installed
virtualbox, 7.0.14-1.mga9, 6.5.13-2.mga9, x86_64: installed
virtualbox, 7.0.14-1.mga9, 6.5.13-desktop-6.mga9, x86_64: installed-binary from 6.5.13-desktop-6.mga9
virtualbox, 7.0.14-1.mga9, 6.6.11-desktop-1.mga9, x86_64: installed

CC: (none) => fri

Was 535.146.02 the only version between 535.154.05 and the previous one (535.129.03)? In other words, do the two links below cover everything that changes in Mageia 9 with this new version? 
https://www.nvidia.com/download/driverResults.aspx/217147/en-us/, 
https://www.nvidia.com/download/driverResults.aspx/216728/en-us/

URL: https://www.nvidia.com/download/driverResults.aspx/217147/en-us/ => https://www.nvidia.com/download/driverResults.aspx/217147/en-us/, https://www.nvidia.com/download/driverResults.aspx/216728/en-us/

Mageia9, x86_64

kernel 6.5.13-desktop-6.mga9

No problem with the update.  Ran drakx11 and rebooted.
This is a definite improvement over the previous driver.  Up until now it was being ignored at boot time and replaced by the nouveau driver.  However during reboot there were some ominous messages which I cannot interpret; during the closedown there was a loop with a complaint about nvrm which needed a hard reset to clear and when the boot sequence started there were messages which have been seen before after the USB devices had been registered - the journal gives:
usb usb3-port1: Cannot enable. Maybe the USB cable is bad?

These occur a few times but the named devices do still work normally after login.
Those particular messages had not been appearing under the nouveau driver.
The glmark2 score has increased by maybe a factor of 5.  The Mate desktop runs without problems.

CC: (none) => tarazed25

Continuing from comment 3:
Forgot the details -
$ inxi -G
Graphics:
  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 535.154.05
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: nvidia,v4l gpu: nvidia resolution: 2560x1440~60Hz
  API: OpenGL v: 4.6.0 NVIDIA 535.154.05 renderer: NVIDIA GeForce GTX 1080
    Ti/PCIe/SSE2

Did a full "# drakboot --boot" and logged out and rebooted.  No odd messages in the log and nothing about USB problems once reboot started.  However this time the nvidia module was rebuilt and installed.  ???  Had not used drakx11 but did use it during the initial test (comment 3).
Previous to that I had already checked that xorg.conf pointed to nvidia and that nvidia535 was in operation and no nouveau module was loaded but forgot to check dkms.
$ dkms status
[...]
nvidia-current, 535.154.05-1.mga9.nonfree, 6.5.13-server-6.mga9, x86_64: installed 
nvidia-current, 535.154.05-1.mga9.nonfree, 6.5.13-desktop-6.mga9, x86_64: installed 
..........

No changes in glmark2 and `inxi -G` and everything else is running.

Ah yes... for Comment 1

$ inxi -G
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750] driver: nvidia v: 535.154.05
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: nvidia,v4l gpu: nvidia resolution: 3840x2160~60Hz
  API: OpenGL v: 4.6.0 NVIDIA 535.154.05 renderer: NVIDIA GeForce GTX
    750/PCIe/SSE2

Len, maybe you could take a look at Bug 32579 ?

In reply to Morgan in comment 6:
Sure thing.

The puzzle in comment 5 might have had something to do with changing from desktop to server kernel at boot without realising it.

Advisory based on comment 0 and comment 2 added to SVN. Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete"

Keywords: (none) => advisory

(In reply to Len Lawrence from comment #8)
> 
> The puzzle in comment 5 might have had something to do with changing from
> desktop to server kernel at boot without realising it.

I think that's the most likely scenario.

MGA9-64 Plasma, i5-7500, Quadro K620 graphics, 1920x1080 monitor, running from the DVI cable. Tested with 6.5.13-6 desktop and server kernels.

Used qarepo to get the packages while in the desktop kernel, then updated. No installation issues. Rebooted, ran glmark2, vlc, and Firefox, with no issues. Glmark2 score was 4630.

Rebooted into the server kernel, and the driver was built during the process. Ran the same tests as before, with again no issues to report. Glmark2 score was 4494, a bit lower than with the desktop kernel, but not significantly so.

Looks good here.

CC: (none) => andrewsfarm

I've been using this on my production machine for a couple of days now without incident, and I just updated all three kernels on the install from comment 10 to 6.6.14, also without incident.

With no issues reported, it's time to move this along.

Validating.

Whiteboard: (none) => MGA9-64-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0032.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED