Hi. I
I've installed Kaos two times today. It's a laptop with Windows 10, and i wanted overwrite with kaos a Chakra installation, that i used to boot using rEFInd.
At the first time, finished the install process, the systemd-boot manager was not displaying windows option. To boot Windows i had to change the boot priority devices in BIOS. Then, i start to read this and other forums. Then i find this:
https://wiki.archlinux.org/index.php/Dual_boot_with_Windows#UEFI_systems
I understand on this manual that i would must install the Kaos /boot on the preexisting ESP, the Windows ESP.
After the first installation my first partitions were:
dev/sda1: 8MB (unknown, i think BIOS)
dev/sda12: fat32. /boot (kaos), with tags Boot and ESP. 491MB. Before the install this partitions was unknown, not used.
dev/sda3: fat32. Tags: SYSTEM, Boot, ESP. This was the original windows boot efi partition.
Ok. The result with this was, like i said, that Windows was not displayed at systemd-boot manager from kaos. it was neccesary configure the bios boot device priority to boot Windows.
To solve this, i've attempted another kaos installation process. I deleted the kaos original boot manager partition crated on the first installationt, and to not waste the sda12 memory (491M😎, i've expand the sda3 partition on the left side, filling 491 + 300. On this partition i've mounted this time /boot, but without no formating.
The result: I've no Windows boot, and no Kaos Boot.
Could be that the sda3 first sector are empty, and i have to move the original info to the start of this partition? It's possible with the kde partition manager of the live iso (from where i've created this post)??
Thanks for your help. I am wishing to test Kaos in my pc.
EDIT: This is the content of dev/sda2 (the 791MB partition):
[live@AtivBook4 dev]$ sudo mount /dev/sda2 /mnt
[live@AtivBook4 dev]$ ls /mnt
Boot/ syslinux/ BOOTSECT.BAK vmlinuz-linux
EFI/ bootmgr initramfs-linux-fallback.img
loader/ BOOTNXT initramfs-linux.img
[live@AtivBook4 dev]$