Hello Ed,
LOL, thanks for that one. Yeah, the issue would have been even more confused indeed.
Best regards.
Francisco.
On 3/10/21 12:07 PM, Ed Greshko wrote:
On 10/03/2021 15:32, Francisco Tissera wrote:
in the command you gave me,
sudo grub2-editenv - set "saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86
the entry x64 is absent. Is it normal, is it supposed to be like that?
FWIW, I decided to test on a system here what would happen with a bogus entry.
My system was booted to the 5.10.20-200 kernel and I gave a bogus entry....
[root@f33k ~]# grub2-editenv list
saved_entry=8b511c4b483b4414b7bf742b35809e2c-5.10.19-200.fc33.x86
boot_success=0
boot_indeterminate=0
I then rebooted the system. The entry above remained unchanged but the system again
booted to the 5.10.20-200 kernel.
So, the good news is that I'd probably wouldn't be responsible for breaking your system. The bad
news is that the results would have probably confused the issue even more.
-- People who believe they don't make mistakes have already made one.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
