First time Debian user, I have no idea what I'm doing, I try to keep it concise. I tried to write more info into the title, but it didn't let me.
The problem: secure boot doesn't work, sudo mokutil --sb-state outputs "This system doesn't support secure boot". When I somehow did enrolled MOK keys, it still outputs this. If I boot by pressing the power button/restarting either with button or from the menu, NVidia Persistence Daemon fails to start and prevents boot, seemingly except when I open BIOS first, and leave, even without changing anything there. When first installed Debian it seemed to work properly, reinstalled Debian, it doesn't work anymore.
During the following, I restarted the PC and wipe SSD-installed Debian many times. At any point while reading, assume I did either of the two.
Initial information: desktop setup, GTX 1050 Ti, B650 Tomahawk Wifi, empty SSD, USB pendrive with Debian 12.6.
Booting up the Debian installer from pendrive, moving through installation process, everything is on rail. Whole SSD for Debian, no dual booting.
https://wiki.debian.org/NvidiaGraphicsDrivers
Open browser, open above link, follow tutorial. NVidia drivers are successfully installed. Open below link.
https://wiki.debian.org/SecureBoot
Somewhere here I can't login into desktop via Wayland (bottom left corner) but I can with X11. It seems the line in the below link works _sometimes_, but not always.
https://www.reddit.com/r/debian/s/FIyfubNXmR
Following tutorial, sudo mokutil --sb-state says "This system doesn't support secure boot".
Based on this link's solution part at the end of the page (viewtopic.php?t=153816) I tried to delete keys in MSI BIOS, give factory defaults, not give factory defaults, switch to manual, switch back to default, switch to CSM, switch back and forth with various settings, and after sacrificing a virgin, mokutil outputs "Secure boot disabled" I guess (or it did outputted enabled sometimes too, didn't remember 100%). Following offical tutorial generate keys with copy pasting the commands into konsole while adding sudo before them, and among the many tries I did managed to trigger the command where I have to give a one-time password. I gave one, restart, big solid blue screen, press enroll keys before it boots up automatically, some yes option I don't remember exactly, then I got to a file folder system which I assume is a place to enroll further keys. Esc back and/or press restart button (I don't remember exactly how did I got out).
Upon booting, check sudo mokutil --sb-state, it outputs "This system doesn't support secure boot", but the other command from the tutorial says the keys are enrolled. Sometimes booting stops because NVidia Persistence Daemon failed to start, but seemingly it works if I go to BIOS first, leave (even without changing things), and then boot up normally.
I have no idea what is happening, what I'm doing, or why these happens. I'm just following tutorials and several year old posts from the internet mixed with brute force/trial and error.
I'm on the verge of just not enabling secure boot (which is not quite ideal, free security is left on the table), or switching back to a Fedora derivative (I used Bazzite before for a brief time, similarly reinstalled things when I messed up something, but I always could enable secure boot consistently without much trouble), also they have the new 555 NVidia drivers too which has explicit sync (no flickering with Wayland) and other fancy features.
Alternatively, I don't know what the MESA drivers are, how they work, what they do, or how can I install and use them, I just read that MESA is the non-proprietary alternative for NVidia drivers for NVidia GPUs. Given how old is my GPU I'm not even certain it would work at all, and how much performance and compatibility would be lost compared to NVidia's own drivers. If there are advantages to MESA drivers other than being non-proprietary software (based on old internet posts, MESA is behind performance and compatibility compared to NVidia drivers, but given how fast technology evolves this might be outdated info), and someone has free time to link/write instructions on how to install them, I'm not against using MESA drivers instead.
Thank you for helping!
The problem: secure boot doesn't work, sudo mokutil --sb-state outputs "This system doesn't support secure boot". When I somehow did enrolled MOK keys, it still outputs this. If I boot by pressing the power button/restarting either with button or from the menu, NVidia Persistence Daemon fails to start and prevents boot, seemingly except when I open BIOS first, and leave, even without changing anything there. When first installed Debian it seemed to work properly, reinstalled Debian, it doesn't work anymore.
During the following, I restarted the PC and wipe SSD-installed Debian many times. At any point while reading, assume I did either of the two.
Initial information: desktop setup, GTX 1050 Ti, B650 Tomahawk Wifi, empty SSD, USB pendrive with Debian 12.6.
Booting up the Debian installer from pendrive, moving through installation process, everything is on rail. Whole SSD for Debian, no dual booting.
https://wiki.debian.org/NvidiaGraphicsDrivers
Open browser, open above link, follow tutorial. NVidia drivers are successfully installed. Open below link.
https://wiki.debian.org/SecureBoot
Somewhere here I can't login into desktop via Wayland (bottom left corner) but I can with X11. It seems the line in the below link works _sometimes_, but not always.
https://www.reddit.com/r/debian/s/FIyfubNXmR
Following tutorial, sudo mokutil --sb-state says "This system doesn't support secure boot".
Based on this link's solution part at the end of the page (viewtopic.php?t=153816) I tried to delete keys in MSI BIOS, give factory defaults, not give factory defaults, switch to manual, switch back to default, switch to CSM, switch back and forth with various settings, and after sacrificing a virgin, mokutil outputs "Secure boot disabled" I guess (or it did outputted enabled sometimes too, didn't remember 100%). Following offical tutorial generate keys with copy pasting the commands into konsole while adding sudo before them, and among the many tries I did managed to trigger the command where I have to give a one-time password. I gave one, restart, big solid blue screen, press enroll keys before it boots up automatically, some yes option I don't remember exactly, then I got to a file folder system which I assume is a place to enroll further keys. Esc back and/or press restart button (I don't remember exactly how did I got out).
Upon booting, check sudo mokutil --sb-state, it outputs "This system doesn't support secure boot", but the other command from the tutorial says the keys are enrolled. Sometimes booting stops because NVidia Persistence Daemon failed to start, but seemingly it works if I go to BIOS first, leave (even without changing things), and then boot up normally.
I have no idea what is happening, what I'm doing, or why these happens. I'm just following tutorials and several year old posts from the internet mixed with brute force/trial and error.
I'm on the verge of just not enabling secure boot (which is not quite ideal, free security is left on the table), or switching back to a Fedora derivative (I used Bazzite before for a brief time, similarly reinstalled things when I messed up something, but I always could enable secure boot consistently without much trouble), also they have the new 555 NVidia drivers too which has explicit sync (no flickering with Wayland) and other fancy features.
Alternatively, I don't know what the MESA drivers are, how they work, what they do, or how can I install and use them, I just read that MESA is the non-proprietary alternative for NVidia drivers for NVidia GPUs. Given how old is my GPU I'm not even certain it would work at all, and how much performance and compatibility would be lost compared to NVidia's own drivers. If there are advantages to MESA drivers other than being non-proprietary software (based on old internet posts, MESA is behind performance and compatibility compared to NVidia drivers, but given how fast technology evolves this might be outdated info), and someone has free time to link/write instructions on how to install them, I'm not against using MESA drivers instead.
Thank you for helping!
Statistics: Posted by Baker — 2024-07-05 13:56 — Replies 2 — Views 161