Closed Lastique closed 1 year ago
I have pushed a fix for this (all the git branches should be in sync now), but it hasn't been approved in the Ubuntu archive yet. This is being tracked here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2025640
Thanks, 15b7731c5a072b7c3895535a3d7b0656fb52953a and cf3ed4abdccdf42be36cc9dcf5b5e85c99dbead8 fixed the problem for me.
sorry for interrupting. I got same/similar problem here after running software manage update my second monitor not detected and never wakes up. after long search (Knowing that i am a new Ubunutu user) found that nvidia drivers are not loaded because of security boot is enabled but they are correctly installed.
before the update i had never problems like this and i had my security boot always enabled.
info : nvidia/535.113.01, 6.2.0-33-generic, x86_64: installed
so my question is it really seem problem as labeled here? and would it be fixed after this issue is confirmed and merged? or is this another issue? and if yes how could be fixed.
Thx in advanced
Mohammed: No, your problem is probably due to the fact that the linux-restricted-modules for the kernel were not available when you installed the NVIDIA driver, and you installed the dkms package as a result, hence the problem with secure boot. We have a fix for that too, and it is coming soon.
Really thx for fast replay and explaining.
Have a nice day :smile:
@executioner90 Please, report this as a separate issue.
Installing/reinstalling/upgrading 535 series of drivers causes the display to permanently turn off during package installation. In the background, the installation seems to proceed, but the DE becomes broken (I'm on KDE, and plasmashell starts to consume 100% CPU in kernel mode). It looks like the GPU simply shuts down during the installation. After that, I cannot reboot the system other than with a SysRq combination or hard reset.
This happens regardless of whether the driver is installed in the DE or in a secondary console.
I believe, this was introduced with 6778e2e983dd2ac48cc202c536f32c9170461b1e and fa3239ef695d44b3b1c9deec2d793feb507a3aab. Reverting those two commits (i.e. switching back to debhelper 9 and
dh_systemd_enable
instead ofdh_installsystemd
) resolves the issue, the driver becomes installable again, including in DE GUI.I tried to change the
dh_installsystemd
arguments from--no-start
to--restart-after-upgrade
,--no-restart-after-upgrade
or-r
- nothing worked, the issue is the same.Steps to reproduce:
Install/upgrade the driver. Or, if it is already installed, reinstall it with a command like this:
Kubuntu 22.04.