Error: Bad SHIM signature on Boot signed Vanilla Kernel (4.9.20) in Knoppix 9.1
Knoppix 9.1 is a popular Linux distribution known for its ease of use and live CD/DVD capabilities. However, some users have reported an error when trying to boot the signed kernel (4.9.20) using a secured boot with GRUB (2.06). This article will provide a detailed explanation of the issue and offer potential solutions.
Understanding the Error
The error message "Bad SHIM signature" is related to the Secure Boot feature in modern computers. Secure Boot is a security standard developed by members of the PC industry to help ensure that your PC boots using only software that is trusted by the PC manufacturer. When the Secure Boot process is initiated, it checks the signatures of the bootloader and kernel to ensure that they are trusted. If the signature is not valid, the boot process will fail, resulting in the error message.
Potential Solutions
There are a few potential solutions to this issue:
Disable Secure Boot: This is the simplest solution, but it may not be desirable for all users as it reduces the security of the boot process. To disable Secure Boot, you can follow the instructions provided by your computer manufacturer or in the BIOS settings.
Use an Unsigned Kernel: Another solution is to use an unsigned kernel. This can be done by booting the Knoppix 9.1 live CD/DVD and selecting the "Expert" mode at the boot prompt. From there, you can select the "Install" option and choose to install the unsigned kernel. This will allow you to boot the system without the Secure Boot error.
Sign the Kernel: If you want to continue using the signed kernel with Secure Boot enabled, you can sign the kernel yourself. This is a more advanced solution and requires a good understanding of Linux and the Secure Boot process. There are several guides available online that can help you with this process.
The "Bad SHIM signature" error on Knoppix 9.1 when booting the signed kernel (4.9.20) with Secure Boot enabled can be frustrating, but there are several potential solutions. Whether you choose to disable Secure Boot, use an unsigned kernel, or sign the kernel yourself, you should be able to boot your system without encountering this error.
References
End of Article