Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Secure boot support #284

Open
shetakeyourmoneyleaveupoor opened this issue Dec 19, 2021 · 4 comments
Open

Secure boot support #284

shetakeyourmoneyleaveupoor opened this issue Dec 19, 2021 · 4 comments

Comments

@shetakeyourmoneyleaveupoor
Copy link

shetakeyourmoneyleaveupoor commented Dec 19, 2021 •
edited
Loading

Distribution (run cat /etc/os-release):

Pop!_OS 21.10

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

Issue/Bug Description:

Invalid signature
Invalid Load from kernel first

Steps to reproduce (if you know):
Downloaded iso directly from system 76 website. Burned iso properly using Rufus to usb.
Booted from secure start up menu off usb
Messages were" Invalid signature and Invalid Load from kernel first"

Expected behavior:

Load Pop os for trial run

Other Notes:
Tried both ISO's on system 76 website
@ids1024
Copy link
Member

ids1024 commented Dec 19, 2021

You need to disable Secure Boot in the BIOS. Pop doesn't currently support booting with Secure Boot.

@shetakeyourmoneyleaveupoor

This comment was marked as spam.

Sign in to view
@shetakeyourmoneyleaveupoor shetakeyourmoneyleaveupoor changed the title Pop!_OS 21.10 would not load at all on boot menu Pop!_OS 21.10 Does not boot secure mode Dec 20, 2021
@shetakeyourmoneyleaveupoor shetakeyourmoneyleaveupoor changed the title Pop!_OS 21.10 Does not boot secure mode Pop!_OS 21.10 Will not load when secure boot mode is enabled Dec 20, 2021
@shetakeyourmoneyleaveupoor shetakeyourmoneyleaveupoor changed the title Pop!_OS 21.10 Will not load when secure boot mode is enabled Pop!_OS 21.10 Will not load when secure boot mode is enabled Pop_OS Must be written to run in Secure Boot mode. Otherwise this is a good way for Malware or Virus to enter Boot Sector. Dec 20, 2021
@shetakeyourmoneyleaveupoor shetakeyourmoneyleaveupoor changed the title Pop!_OS 21.10 Will not load when secure boot mode is enabled Pop_OS Must be written to run in Secure Boot mode. Otherwise this is a good way for Malware or Virus to enter Boot Sector. Pop!_OS 21.10 Will not load when secure boot mode is enabled. Pop_OS Must be written to run in Secure Boot mode. Otherwise this is a good way for Malware or Virus to enter Boot Sector. Dec 20, 2021
@shetakeyourmoneyleaveupoor shetakeyourmoneyleaveupoor changed the title Pop!_OS 21.10 Will not load when secure boot mode is enabled. Pop_OS Must be written to run in Secure Boot mode. Otherwise this is a good way for Malware or Virus to enter Boot Sector. Pop!_OS 21.10 Will not load when secure boot mode is enabled. Pop_OS Must be written to run in Secure Boot mode. Otherwise this is a good way for Malware or Virus to enter Boot Sector. High Security Risk posed by all Linux distros that do not use secure boot installation Dec 20, 2021
@jacobgkau jacobgkau changed the title Pop!_OS 21.10 Will not load when secure boot mode is enabled. Pop_OS Must be written to run in Secure Boot mode. Otherwise this is a good way for Malware or Virus to enter Boot Sector. High Security Risk posed by all Linux distros that do not use secure boot installation Secure boot support Dec 20, 2021
@Ampersandstorm Ampersandstorm mentioned this issue Mar 31, 2022
Merged
@AhmedFaisal
Copy link

Having the same issue with Pop!Os.
"Secure boot is currently not supported" is not an answer, this is exactly the bug. It should be supported as it is on Fedora, Ubuntu, Debian and more. Thus, the bug should remain open and seriously reviewed until Secure Boot get supported by Pop!Os.
p.s.: so you mean Secure Boot is not available on System76 machines? really?

@pop-os pop-os locked as off-topic and limited conversation to collaborators May 16, 2022
@jackpot51
Copy link
Member

Locking this as changing the title and commenting the same thing over and over is not going to change the issue itself or the timeline with which Secure Boot support is delivered. We are will be working on it, that is all there is to say right now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ids1024 @AhmedFaisal @jackpot51 @shetakeyourmoneyleaveupoor