# Common Firmware issues but no Response

**URL:** <https://community.frame.work/t/common-firmware-issues-but-no-response/63555>\
**Category:** Linux\
**Tags:** nixos\
**Created:** [January 21, 2025, 12:52pm UTC](https://community.frame.work/t/common-firmware-issues-but-no-response/63555 "2025-01-21T12:52:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Philipp\_Jungkamp](https://avatars.discourse-cdn.com/v4/letter/p/5fc32e/32.png) [@Philipp\_Jungkamp](https://community.frame.work/u/Philipp_Jungkamp)\
**Post date:** [January 21, 2025, 12:52pm UTC](https://community.frame.work/t/common-firmware-issues-but-no-response/63555/1 "2025-01-21T12:52:17Z")

</div>

# Is the Firmware Issue tracker on GitHub dead?

I tried to describe my issues in the [SoftwareFirmwareIssueTracker](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker) on GitHub.  
There hasn’t been any answer for the both the [EFI Setup Mode](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues/30) and the [DMI Wake-Up Type](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues/29) issues for a month.

I’ll repost a short summary here to maybe get more attention to these issues.

## Broken EFI Secure Boot Setup Mode

The “Erase all Secure Boot Settings” option 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.

See [Can't enable secure boot setup mode](https://community.frame.work/t/cant-enable-secure-boot-setup-mode/57683)

> When I put secureboot into setup mode via:
> 
> Firmware settings → “Administer Secureboot” → “Erase all Secureboot Settings” → Enable → F10
> 
> Several efi-based tools stop working on subsequent boots.

See [Putting secureboot into setup mode breaks several efi-tools](https://community.frame.work/t/putting-secureboot-into-setup-mode-breaks-several-efi-tools/62033)

### Workaround

The workaround of manually deleting PK, KEK, and DB options in the EFI as suggested by @Alec_Miller seems to work for now.

You can find more information in my [EFI Setup Mode](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues/30) issue on GitHub.

## Incorrect DMI Wake-up type when woken by APM timer

This causes `systemctl suspend-then-hibernate` on my GNOME DE too endlessly loop between suspend for an hour and showing a lock screen for 15 minutes. This almost drained my battery over night.

The problem is that `suspend-then-hibernate` checks the `Wake-Up Type` in the DMI to determine whether the user has woken the laptop intentionally to exit suspend or if the laptop was woken by a timer and should switch to hibernation.

### Workaround

I could work around this issue by adding `use_acpi_alarm=1` to the options for the `rtc_cmos` kernel module. This was a suggestion for AMD models of the Framework laptop on older kernel versions, but I hadn’t seen this suggested for the Core Ultra Series 1 Laptops on the Forum yet.

You can find more information in my [DMI Wake-Up Type](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues/29) issue on GitHub.

## Details

- NixOS unstable (2025-01-14)
- Linux Kernel 6.12.9
- Framework Laptop Core Ultra 7 155H
- 64GB RAM

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\
**Post date:** [July 20, 2025, 12:52pm UTC](https://community.frame.work/t/common-firmware-issues-but-no-response/63555/2 "2025-07-20T12:52:18Z")

</div>

Closed on July 20, 2025, 12:52pm UTC

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.