Unsigned kernel and Secure Boot
up vote
0
down vote
favorite
I have just bought a Lenovo Ideapad 330 and installed 18.04LTS. Turns out, touchpad is not working.
I found a solution for the touchpad here: Lenovo IdeaPad 330 touchpad not working
I then downloaded .deb packages for mainline kernel 4.19 and installed them. Touchpad now working (sort of).
However, I'm concerned about the warnings I got when installing the kernel, about about the kernel being unsigned and thus incompatible with Secure Boot. Also, when installing the package vim-gtk3 I got error messages about shim-signed and grub-efi-amd64-signed.
Is there a way to get rid of these warnings/errors and still have a working touchpad?
And what is this signed/unsigned business about anyway - why are some kernels not signed?
kernel touchpad lenovo grub-efi secure-boot
asked Nov 27 at 12:55
DKlaus
11
add a comment |
up vote
0
down vote
favorite
I have just bought a Lenovo Ideapad 330 and installed 18.04LTS. Turns out, touchpad is not working.
I found a solution for the touchpad here: Lenovo IdeaPad 330 touchpad not working
I then downloaded .deb packages for mainline kernel 4.19 and installed them. Touchpad now working (sort of).
However, I'm concerned about the warnings I got when installing the kernel, about about the kernel being unsigned and thus incompatible with Secure Boot. Also, when installing the package vim-gtk3 I got error messages about shim-signed and grub-efi-amd64-signed.
Is there a way to get rid of these warnings/errors and still have a working touchpad?
And what is this signed/unsigned business about anyway - why are some kernels not signed?
kernel touchpad lenovo grub-efi secure-boot
asked Nov 27 at 12:55
DKlaus
11
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have just bought a Lenovo Ideapad 330 and installed 18.04LTS. Turns out, touchpad is not working.
I found a solution for the touchpad here: Lenovo IdeaPad 330 touchpad not working
I then downloaded .deb packages for mainline kernel 4.19 and installed them. Touchpad now working (sort of).
However, I'm concerned about the warnings I got when installing the kernel, about about the kernel being unsigned and thus incompatible with Secure Boot. Also, when installing the package vim-gtk3 I got error messages about shim-signed and grub-efi-amd64-signed.
Is there a way to get rid of these warnings/errors and still have a working touchpad?
And what is this signed/unsigned business about anyway - why are some kernels not signed?
kernel touchpad lenovo grub-efi secure-boot
asked Nov 27 at 12:55
DKlaus
11
I have just bought a Lenovo Ideapad 330 and installed 18.04LTS. Turns out, touchpad is not working.
I found a solution for the touchpad here: Lenovo IdeaPad 330 touchpad not working
I then downloaded .deb packages for mainline kernel 4.19 and installed them. Touchpad now working (sort of).
However, I'm concerned about the warnings I got when installing the kernel, about about the kernel being unsigned and thus incompatible with Secure Boot. Also, when installing the package vim-gtk3 I got error messages about shim-signed and grub-efi-amd64-signed.
Is there a way to get rid of these warnings/errors and still have a working touchpad?
And what is this signed/unsigned business about anyway - why are some kernels not signed?
kernel touchpad lenovo grub-efi secure-boot
kernel touchpad lenovo grub-efi secure-boot
asked Nov 27 at 12:55
DKlaus
11
asked Nov 27 at 12:55
DKlaus
11
asked Nov 27 at 12:55
DKlaus
11
asked Nov 27 at 12:55
DKlaus
11
asked Nov 27 at 12:55
DKlaus
11
11
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
Turn off secure boot in UEFI menu. Every laptop has a different way for doing this, you can find this with a quick google search. This will turn off messages about unsigned kernel and modules.
It only allows signed software to boot.
If you are confident of the downloaded
Kernel turn it off. Or you can sign it yourself and register machine owner key in secureboot database.
You can read more about Secure Boot here & go here if you want to read about signing kernel and kernel modules.
answered Nov 27 at 14:04
harshit
599
add a comment |
up vote
0
down vote
You probably installed an unsigned kernel, that's why Secure Boot complains on it.
Mainline kernels are never signed, but Ubuntu kernels are signed.
You can disable Secure Boot to get rid of those messages.
The Secure Boot feature is not very useful, especially whan you are using a mainline kernel.
answered Nov 27 at 13:55
Pilot6
51.3k15107195
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Turn off secure boot in UEFI menu. Every laptop has a different way for doing this, you can find this with a quick google search. This will turn off messages about unsigned kernel and modules.
It only allows signed software to boot.
If you are confident of the downloaded
Kernel turn it off. Or you can sign it yourself and register machine owner key in secureboot database.
You can read more about Secure Boot here & go here if you want to read about signing kernel and kernel modules.
answered Nov 27 at 14:04
harshit
599
add a comment |
up vote
1
down vote
Turn off secure boot in UEFI menu. Every laptop has a different way for doing this, you can find this with a quick google search. This will turn off messages about unsigned kernel and modules.
It only allows signed software to boot.
If you are confident of the downloaded
Kernel turn it off. Or you can sign it yourself and register machine owner key in secureboot database.
You can read more about Secure Boot here & go here if you want to read about signing kernel and kernel modules.
answered Nov 27 at 14:04
harshit
599
add a comment |
up vote
1
down vote
up vote
1
down vote
Turn off secure boot in UEFI menu. Every laptop has a different way for doing this, you can find this with a quick google search. This will turn off messages about unsigned kernel and modules.
It only allows signed software to boot.
If you are confident of the downloaded
Kernel turn it off. Or you can sign it yourself and register machine owner key in secureboot database.
You can read more about Secure Boot here & go here if you want to read about signing kernel and kernel modules.
answered Nov 27 at 14:04
harshit
599
Turn off secure boot in UEFI menu. Every laptop has a different way for doing this, you can find this with a quick google search. This will turn off messages about unsigned kernel and modules.
It only allows signed software to boot.
If you are confident of the downloaded
Kernel turn it off. Or you can sign it yourself and register machine owner key in secureboot database.
You can read more about Secure Boot here & go here if you want to read about signing kernel and kernel modules.
answered Nov 27 at 14:04
harshit
599
answered Nov 27 at 14:04
harshit
599
answered Nov 27 at 14:04
harshit
599
answered Nov 27 at 14:04
harshit
599
599
add a comment |
add a comment |
up vote
0
down vote
You probably installed an unsigned kernel, that's why Secure Boot complains on it.
Mainline kernels are never signed, but Ubuntu kernels are signed.
You can disable Secure Boot to get rid of those messages.
The Secure Boot feature is not very useful, especially whan you are using a mainline kernel.
answered Nov 27 at 13:55
Pilot6
51.3k15107195
add a comment |
up vote
0
down vote
You probably installed an unsigned kernel, that's why Secure Boot complains on it.
Mainline kernels are never signed, but Ubuntu kernels are signed.
You can disable Secure Boot to get rid of those messages.
The Secure Boot feature is not very useful, especially whan you are using a mainline kernel.
answered Nov 27 at 13:55
Pilot6
51.3k15107195
add a comment |
up vote
0
down vote
up vote
0
down vote
You probably installed an unsigned kernel, that's why Secure Boot complains on it.
Mainline kernels are never signed, but Ubuntu kernels are signed.
You can disable Secure Boot to get rid of those messages.
The Secure Boot feature is not very useful, especially whan you are using a mainline kernel.
answered Nov 27 at 13:55
Pilot6
51.3k15107195
You probably installed an unsigned kernel, that's why Secure Boot complains on it.
Mainline kernels are never signed, but Ubuntu kernels are signed.
You can disable Secure Boot to get rid of those messages.
The Secure Boot feature is not very useful, especially whan you are using a mainline kernel.
answered Nov 27 at 13:55
Pilot6
51.3k15107195
answered Nov 27 at 13:55
Pilot6
51.3k15107195
answered Nov 27 at 13:55
Pilot6
51.3k15107195
answered Nov 27 at 13:55
Pilot6
51.3k15107195
51.3k15107195
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096481%2funsigned-kernel-and-secure-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
