DKMS
2026
Comment:
|
1893
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from UEFI/SecureBoot/NotSignedDKMS ## page was renamed from UEFI/SecureBoot/DKMSnotWork |
|
Line 12: | Line 10: |
2. Disable secure boot 3. Save configuration 4. Reboot the system |
1. Disable secure boot 1. Save configuration 1. Reboot the system |
Line 17: | Line 15: |
1. Open a terminal by '''Ctrl + Alt + T''', execute '''sudo update-secureboot-policy''' and then select '''Yes''' {{attachment:update-secureboot-policy.png}} 2. Enter a temporary password between 8 to 16 digits. (For example, 12345678, we will use this password later.){{attachment:Enter_a_temporary_password.png}} 3. Enter the same password again to confirm{{attachment:confirm_password.png}} 4. Reboot the system and press any key when you see the blue screen (MOK management) {{attachment:press_any_key.png}} 5. Select '''Change Secure Boot state''' {{attachment:change_secureboot_state.png}} 6. Press the corresponding password character and press Enter. Repeat this step several times to confirm previous temporary password like 12345678 in '''Step 2''' and '''Step 3'''. For exmaple, 2 shown in below picture {{attachment:enter_password.png}} 7. Select '''Yes''' to disable Secure Boot in shim-signed {{attachment:select_yes.png}} 8. Press '''Enter''' key to finish the whole procedure {{attachment:press_enter_key.png}} 9. We can still enable Secure Boot in shim-signed again. Just execute '''sudo update-secureboot-policy --enable''' and then follow the similar steps above |
1. Open a terminal ('''Ctrl + Alt + T'''), and execute '''sudo update-secureboot-policy''' and then select '''Yes'''. {{attachment:update-secureboot-policy.png|align="left"}} 1.#2 Enter a temporary password between 8 to 16 digits. (For example, 12345678, we will use this password later {{attachment:Enter_a_temporary_password.png|align="left"}} 1.#3 Enter the same password again to confirm. {{attachment:confirm_password.png|align="left"}} 1.#4 Reboot the system and press any key when you see the blue screen (MOK management {{attachment:press_any_key.png|align="left"}} 1.#5 Select '''Change Secure Boot state''' {{attachment:change_secureboot_state.png|align="left"}} 1.#6 Enter the password you had selected in '''Step 2''' and press Enter. {{attachment:enter_password.png|align="left"}} 1.#7 Select '''Yes''' to disable Secure Boot in shim-signed. {{attachment:select_yes.png|align="left"}} 1.#8 Press '''Enter''' key to finish the whole procedure. {{attachment:press_enter_key.png|align="left"}} You can still enable Secure Boot in shim-signed again. Just execute '''sudo update-secureboot-policy --enable''' and then follow the steps above |
DKMS do not work on systems with Secure Boot enabled
Following an UOS approved spec, Ubuntu is checking module signing by default, on kernels 4.4.0-18.34, 4.4.0-21.37, 4.2.0-42.49, 3.19.0-65.73 and 3.13.0-92.139 onwards.
Because of those changes, DKMS modules will not work on systems with Secure Boot is enabled.
In order to make DKMS work, Secure Boot needs to be disabled. There are several methods to disable Secure Boot in your system:
Method 1 - Disable Secure Boot from BIOS
- Enter BIOS setup
- Disable secure boot
- Save configuration
- Reboot the system
Method 2 - Disable Secure Boot in shim-signed
Open a terminal (Ctrl + Alt + T), and execute sudo update-secureboot-policy and then select Yes.
- Enter a temporary password between 8 to 16 digits. (For example, 12345678, we will use this password later
- Enter the same password again to confirm.
- Reboot the system and press any key when you see the blue screen (MOK management
Select Change Secure Boot state
Enter the password you had selected in Step 2 and press Enter.
Select Yes to disable Secure Boot in shim-signed.
Press Enter key to finish the whole procedure.
You can still enable Secure Boot in shim-signed again. Just execute sudo update-secureboot-policy --enable and then follow the steps above
UEFI/SecureBoot/DKMS (last edited 2018-06-26 19:53:49 by cyphermox)