start:issecurebootworking
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| start:issecurebootworking [2022/09/11 13:10] – peter | start:issecurebootworking [2024/04/24 13:27] (current) – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | NOTE ON 24-April-2024 | ||
| + | Honestly secure boot is super annoying on Debian. In Ubuntu its automatic, but Debian everytime there is a kernel or Nvidia driver update you have to manually resign all the drivers which I find of questionable value. Im not sure what security benefit is actually being achieved here, at high cost and annoyance. Also the signing code has stopped working due to some bug at the moment so its not even super reliable when you cant sign your graphics drivers because devs are working on fixing bugs in the code. I recommend not using secure boot on Debian testing. If you absolutely have to have this then you can try fiddling around with the below guide, or using Debian or Ubuntu stable. I tried it for a few years but it was always annoying and provided no tangible benefit. | ||
| + | |||
| + | DATE CHECKED THIS PAGE WAS VALID: 30/ | ||
| + | |||
| Ok So it was possible to get secure boot working. It took me a long time as I didnt fully understand what was happening. | Ok So it was possible to get secure boot working. It took me a long time as I didnt fully understand what was happening. | ||
| Line 66: | Line 71: | ||
| </ | </ | ||
| - | Very important - after you type the next command it asks you for a password, but its not obvious that its asking for a password, the terminal just sits and waits for input. | + | **CRITICAL NOTE!!!!!!!!! |
| + | ON DEBIAN 12 THERE WAS A CHANGE WHERE THIS PART OF THE SCRIPT INCORRECTLY GETS THE DIRECTORY: | ||
| + | < | ||
| + | uname -r | cut -d . -f 1-2 | ||
| + | </ | ||
| + | This means that ls / | ||
| + | < | ||
| + | SHORT_VERSION=" | ||
| + | </ | ||
| + | This means "ls / | ||
| + | |||
| + | |||
| + | Very important - after you type the next command it asks you for a password, but its not obvious that its asking for a password, the terminal just sits and waits for input. | ||
| < | < | ||
| Line 85: | Line 102: | ||
| sudo modinfo nvidia-tesla-510-drm.ko | sudo modinfo nvidia-tesla-510-drm.ko | ||
| </ | </ | ||
| - | NOTE: Filename may be different just use tab completion to find appropriate file to check. | + | NOTE: Filename may be different just use tab completion to find appropriate file to check eg even nvidia-current-drm or some other name. |
| Above assumes you have that particular driver installed but just check a different file/ | Above assumes you have that particular driver installed but just check a different file/ | ||
start/issecurebootworking.1662901853.txt.gz · Last modified: 2022/09/11 13:10 by peter
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
