You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Framework
Product Name: Laptop 13 (Intel Core Ultra Series 1)
Version: A5
Serial Number: <REDACTED>
UUID: <REDACTED>
Wake-up Type: Power Switch
SKU Number: FRANDPCP05
Family: Laptop
BIOS VERSION
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: INSYDE Corp.
Version: 03.04
Release Date: 10/09/2024
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
Yes
No
Describe the bug
"Erase all Secure Boot Settings" leaves EFI variables in an unexpected state that is described in multiple posts on the forum:
I’ve tried restarting with “Erase all Secure Boot Settings”, “Restore Secure Boot to Factory Settings”, and both “Erase” and “Restore” set to enabled in the BIOS menu, but on booting and running sbctl status it shows setup mode as disabled.
Device Information
System Model or SKU
Please select one of the following
BIOS VERSION
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
Describe the bug
"Erase all Secure Boot Settings" leaves EFI variables in an unexpected state that is described in multiple posts on the forum:
See https://community.frame.work/t/cant-enable-secure-boot-setup-mode/57683
See https://community.frame.work/t/putting-secureboot-into-setup-mode-breaks-several-efi-tools/62033
Steps To Reproduce
Steps to reproduce the behavior:
The EFI firmware enters a state where several EFI variables are just missing.
Expected behavior
"Erase all Secure Boot Settings" should enter a proper Secure Boot Setup Mode state.
Operating System (please complete the following information):
6.5.7
Additional context
/sys/firmware/efi/efivars/SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
EFI variable file Foxboron/sbctl#407The text was updated successfully, but these errors were encountered: