Update Incomplete Gigabyte Specific Instructions On The Secure Boot Guide
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux
- Domain
- documentation, operating-systems, security
Research direction
Start by reading the existing Gigabyte motherboard-specific Secure Boot guide in the wiki and checking the Factory Key Provision setting against the reported B650 Gaming X AX v2 behavior. Update the guide to cover that setting and the existing --firmware-builtin warning; done when the instructions address the reported duplicate EFI key-variable behavior.
Written by the indexing model from the issue text.
Description
Rewriting my original issue request, since I realized it didn't specify enough that the current instructions on the wiki are incomplete.
Suggesting an update on the Gigabyte motherboard specific secure boot guide already in the wiki, since it is incomplete for some Gigabyte motherboards and their behavior.
It already mentions that you are not to use the --firmware-builtin flag on sbctl enroll-keys as it will cause duplicate entries of the EFI key variable builtin-db, which will cause Secure Boot not to work. Unfortunately this alone will not allow
Secure Boot to work, as it will show the same behavior either way, due to a what seems like a Gigabyte specific quirk in how it handles these keys. The actual problem is a setting called "Factory Key Provision" in the Secure Boot Expert Key Management settings. This seems to be the actual root cause, which creates the duplicated builtin-db variables.
I'm reporting this behavior happening on the Gigabyte B650 Gaming X AX v2. I have also found evidence supporting this to be a replicatable bug from another users forum post:
https://discuss.cachyos.org/t/issues-enabling-secure-boot-on-gigabyte-motherboard-for-dual-boot-windows-11-battlefield-6-javelin-anticheat/23444/3
- Dominant language
- MDX
- Stars
- 160
- Forks
- 240
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CachyOS/wiki
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
EGL HeadlessOpen
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Make seperate instruction for updating dotfiles from cachyos-*-settings package using meldMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 Half a day Newbie friendliness 74/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Similar issues
-
documentation needs-triage priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
yeongseon/azure-functions-validation-python#546 ·
Maintainers usually reply within 1 day
-
domain:upgrade
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
spec-kitty/spec-kitty#6362 ·
Maintainers usually reply within 1 day
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24755 ·
Maintainers usually reply within 1 day
-
enhancement priority:p3 track:open-source
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
ChristianHandy/FleetPilot#120 ·
Maintainers usually reply within 1 day