-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
HP t520 fails to load kernel on 13.1 #3557
Comments
@a4mkd9 I've started a Edit: oops, wrong params. This one should be correct: https://github.com/home-assistant/operating-system/actions/runs/10527069248 |
Hello sairon, Sorry for the delay - had to find original 16GB m2 SATA drive to avoid reinstalling and recovering everything again in case of failure. |
@a4mkd9 Thank you, I'll create a PR to include the fix, which means it will be available on the next OS >13.1, starting with the next RC already. You should be safe running the dev version in the meantime, or using the EFI binaries to fix an older stable release. |
HP t520 have been reported to have the same issues as Atom boards with bad UEFI firmware that doesn't work well with the new EFI loader used since GRUB 2.12. Apply the patch to use legacy loader for its CPU ID as well. Fixes #3557
HP t520 have been reported to have the same issues as Atom boards with bad UEFI firmware that doesn't work well with the new EFI loader used since GRUB 2.12. Apply the patch to use legacy loader for its CPU ID as well. Fixes #3557
I am experiencing the exact same issue on an Hp T630 Thin Client AMD GX-420GI. When I update from version 12.4 to 13.1, after rebooting, I encounter the following error: Slot A (OK=1 Try=3) I have even tried clean installing both versions 13 and 13.1, but I still get the same error. I have also updated my BIOS, but the issue persists. |
Tried SLOT A and B, also recovery console - nothing boots. I have backups on Google Drive - didn't try the restore procedure yet. Just in case - booted live linux and backing up drive contents to my NAS.
Is there anything I could get from the logs that would help figuring out the reason of this issue?..
UPDATE
Spent some time today troubleshooting this issue:
So it seems my issue is related to #3305 and it turns out it affects AMD CPUs also...
Attaching dmidecode and "smbios --type 4 --get-qword 8" output :
32386119686159359
dmidecode.txt
Originally posted by @a4mkd9 in #3153 (comment)
The text was updated successfully, but these errors were encountered: