You are not logged in.
Pages: 1
Previously I could select different boot entries, but now systemd-boot uses the session I've used earlier.
Is this normal since the latest update or is there a damage?
I'm using UEFI, and I'm only able to boot into Windows by using UEFI first.
Thanks.
EDIT: Turns out my FAT-partition was damaged; after upgrading the kernel and running bootctl update the boot menu is back.
Last edited by beta990 (2017-10-24 07:08:14)
Offline
Hmm, the issue is back again. Could this be a issue with fast boot?
Strange it happens after the latest Windows update.
Two kernels installed, but only detects the last used one.
Last edited by beta990 (2017-10-24 07:08:40)
Offline
I'd say it is an issue with Windows; it is known to disrespect other boot entries:
https://wiki.archlinux.org/index.php/Un … boot_order
Not an Installation issue, moving to NC...
Offline
Hmm, the issue is back again. Could this be a issue with fast boot?
The wiki says that fast boot should be disabled on dual-boot systems because, essentially, it does not shut the OS down completely between boots. Booting the other OS is, therefore, expected to screw things up.
[Note that I do not use Windows, so I have no experience of this - I just happen to have read this in the wiki recently while doing a new install of Arch.]
Last edited by cfr (2017-10-24 12:13:44)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Pages: 1