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

Can't boot, date overflow error #42

Closed
ragnarblackmane opened this issue Feb 29, 2024 · 4 comments
Closed

Can't boot, date overflow error #42

ragnarblackmane opened this issue Feb 29, 2024 · 4 comments

Comments

@ragnarblackmane
Copy link

Please identify some basic details to help process the report

During boot Heads tells that the keys have been created 19578 days in the future, won't boot with (goes directly to the recovery console) or without the Nitrokey (goes to Heads menu). The hwclock date is 01-01-1970. The only way to boot is to set a date prior to today through the console and copy it to hwclock, then reboot.

This happens on a NitroPad NS50 with Heads 2.4.1.
It happens on every NitroPad NS50 we have.

Steps to reproduce the behavior:

  1. Try to boot.

Expected behavior
The system should boot and not lose the date.

Screenshots

Past

Future

@ragnarblackmane
Copy link
Author

Setting the date to March 1st 2024 and copying it to hwclock, survives reboot . It seems that the bug is due to the leap year.

@123ahaha
Copy link

Same on my side with heads-nitropad-nv41-v0.2.0-2038-gebdcc85.rom

Probably due to 29 february but can t tell ....

Boot in untrusted mode

@ragnarblackmane
Copy link
Author

ragnarblackmane commented Feb 29, 2024

Seems the problem is upstream on coreboot
https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/57F4LNJQ6MBRT5VAJAKWHU4QHW5EFPVN/

Same on my side with heads-nitropad-nv41-v0.2.0-2038-gebdcc85.rom

Probably due to 29 february but can t tell ....

Boot in untrusted mode

@daringer
Copy link
Collaborator

daringer commented Mar 1, 2024

I answered so many requests yesterday about this, thus forgot this issue ;)
thx @ragnarblackmane for reporting, that's also the coreboot issue I think is reponsible, to be complete, the workaround was during the Feb 29th:

date -s 2024-03-01
hwclock -w
reboot

this will be fixed with the next coreboot update, closing

@daringer daringer closed this as completed Mar 1, 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

3 participants