ericonr
commented
3 years ago Regarding the screenshot, this is the same issue as seen in #181 ... Just that the PAM update made it fatal instead of just a warning.
If I had seen your issue earlier I might have known to check for it when doing the PAM update, so thanks very much for reporting.
but no EFI boot entry was put in automatically for GRUB as I would have kinda expected, and therefore I just had to add it manually and all was fine.
I would have expected GRUB to create the entry automatically... But I could be wrong, I remember having some weird issue with the only installer + UEFI install I did.
Somewhat related to #131 from what I've seen but doesn't seem to be entirely the same issue:
So I migrated to Void a few days ago and so far am very happy with it, I just had a mild scare upon installation because no matter what I did and after a few retries, my laptop claimed right after reboot always that it couldn't find anywhere to boot from (it's a Dell XPS 13 from 2018 if that helps, latest BIOS firmware to my knowledge). After trying a few things frantically that didn't work, I eventually looked into my BIOS configuration and found out that the boot entries were understandably wiped, but no EFI boot entry was put in automatically for GRUB as I would have kinda expected, and therefore I just had to add it manually and all was fine.
I would assume this is unintended behaviour, but please feel free to tell me if I should have just realized this on my own, since the Void documentation, at least as far as I could tell, doesn't mention this eventuality anywhere.
Also, this systematically showed up in one of the last steps of autoconfig before the installer claimed it had finished its work, I couldn't find much for what it's supposed to mean though, not sure whether it's related or should be a new issue (sorry for the quality, it shows up only briefly-ish, on the left what's cut off says "configuration error":