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.

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

Reboot from Heads not working anymore after 2.1->2.4 upgrade #34

Closed
12 of 50 tasks
UndeadDevel opened this issue Jan 11, 2024 · 4 comments
Closed
12 of 50 tasks

Reboot from Heads not working anymore after 2.1->2.4 upgrade #34

UndeadDevel opened this issue Jan 11, 2024 · 4 comments

Comments

@UndeadDevel
Copy link

UndeadDevel commented Jan 11, 2024

Please identify some basic details to help process the report

After upgrading to NK Heads 2.4 from 2.1 reboot from Heads doesn't work anymore (it does work from QubesOS 4.2); i.e. it neither works when I trigger it manually from recovery shell nor when the reboot is supposed to be automatically triggered during OEM factory reset. It's a relatively minor issue. Possibly related to #24.

A. Provide Hardware Details

1. What board are you using (see list of boards here)?
Nitropad NV41

2. Does your computer have a dGPU or is it iGPU-only?

  • dGPU
  • iGPU-only

3. Who installed Heads on this computer?

  • Insurgo
  • Nitrokey (original 2.1)
  • Purism
  • Other provider
  • Self-installed (2.4 via internal GUI upgrade function)

4. What PGP key is being used?

  • Librem Key
  • Nitrokey Pro 2
  • Nitrokey Storage
  • Yubikey
  • Other (Nitrokey 3A Mini)

5. Are you using the PGP key to provide HOTP verification?

  • Yes
  • No
  • I don't know

B. Identify how the board was flashed

1. Is this problem related to updating heads or flashing it for the first time?

  • First-time flash
  • Updating heads
  • Neither, separate issue with the new firmware

2. If the problem is related to an update, how did you attempt to apply the update?

  • Using the Heads GUI
  • Flashrom via the Recovery Shell
  • External flashing

3. How was Heads initially flashed

  • External flashing (presumably...NitroKey did it)
  • Internal-only / 1vyrain
  • Don't know

4. Was the board flashed with a maximized or non-maximized/legacy rom?

  • Maximized (presumably)
  • Non-maximized / legacy
  • I don't know

5. If Heads was externally flashed, was IFD unlocked?

  • Yes (presumably)
  • No
  • Don't know

C. Identify the rom related to this bug report

NK Heads 2.4
1. Did you download or build the rom at issue in this bug report?

  • I downloaded it
  • I built it

2. If you downloaded your rom, where did you get it from?

  • Heads CircleCi
  • Purism
  • Nitrokey (this GitHub repo)
  • Somewhere else (please identify)

Please provide the release number or otherwise identify the rom downloaded

3. If you built your rom, which repository:branch did you use?

  • Heads:Master
  • Other (please identify)

4. What version of coreboot did you use in building?

  • 4.8.1 (current default in heads:master)
  • 4.13
  • 4.14
  • 4.15
  • Other (please specify)
  • I don't know

5. In building the rom where did you get the blobs?

  • No blobs required
  • Provided by the company that installed Heads on the device
  • Extracted from a backup rom taken from this device
  • Extracted from another backup rom taken from another device (please identify the board model)
  • Extracted from the online bios using the automated tools provided in Heads
  • I don't know

Please describe the problem

Describe the bug
reboot from Heads recovery shell or automated scripts doesn't work; machine shuts down without rebooting instead.

To Reproduce
Steps to reproduce the behavior:

  1. Upgrade NV41 to NK Heads 2.4
  2. Enter recovery shell and execute reboot

Expected behavior
reboots as before under 2.1

@daringer
Copy link
Collaborator

yes, this is kind of a "feature"....

in reboot and poweroff the EC is used for a proper shutdown - this reduces the risk that the nitropads might need to be started more than once (this may happen after a firmware update)

So I have to admit this will be a won't fix as of now...

@UndeadDevel
Copy link
Author

Well it's not a big deal anyway; reboot from the OS works as expected. Closing as won't fix.

@UndeadDevel UndeadDevel closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2024
@UndeadDevel UndeadDevel changed the title Reboot from Heads not working anymore after 2.1->2.4 upgrade Reboot from Heads and sometimes from OS not working anymore after 2.1->2.4 upgrade Jan 16, 2024
@UndeadDevel
Copy link
Author

UndeadDevel commented Jan 16, 2024

I'll just add that while sometimes rebooting from the OS does work, other times it leaves the system hanging and requires a hard shutdown...is this also expected or should I open a new issue?
Edit: now opened under #38

@daringer
Copy link
Collaborator

not expected, also not necessarily a firmware only thing, still feel free to create an issue - pls include OS & kernel-version

@UndeadDevel UndeadDevel changed the title Reboot from Heads and sometimes from OS not working anymore after 2.1->2.4 upgrade Reboot from Heads not working anymore after 2.1->2.4 upgrade Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants