Yes but the terminal is frozen, cannot do anything other than reboot
Thats fine thanks 
I see. If everything is frozen then I guess we cannot get that log file. What a bummer!
Could you try deleting the partitions you have made and choose the automatic installation instead of the manual?
Go with the defaults. That would be BTRFS and systemd-boot.
I guess so. There is 4 different kinds of installation right?
1.Alongside
2.Replace a partition
3.Erase disk
4. Manual
which one?
I haven’t looked at the installer for quite a while but I am sure you will find the right option.
It might be Alongside then. Or Replace Partition.
Definitely not 3 and 4.
If you followed pebcak, and deleted the partitions you created before, it would be no. 2.
…potentially you would also need to create a new (empty) partition for that (replace partition), just to be sure.
Ok I’ll give it a shot. thanks 
Ahha, everything installed now, but on reboot it goes into windows. So I gotta find out what key to press during start
https://0x0.st/H8oi.txt
got into the uefi on startup but only windows boot as number 1
and HDD: Kingston as number 2
no endeavouros…
also think so…
Could you boot up your live usb and post the output of:
sudo parted -l
efibootmgr -v
Just skimping through the log, it looks like no new EFI was set up during the installation.
For systemd-boot EnOS sets up an ESP of 1G size.
PYTHON JOB]: "Device Start End Sectors Size Type\n"
[PYTHON JOB]: "/dev/sda1 2048 923647 921600 450M Windows recovery environment\n"
[PYTHON JOB]: "/dev/sda2 923648 1542239 618592 302M EFI System\n"
[PYTHON JOB]: "/dev/sda3 1542240 231846149 230303910 109.8G Microsoft basic data\n"
[PYTHON JOB]: "/dev/sda4 499054592 500115455 1060864 518M Windows recovery environment\n"
[PYTHON JOB]: "/dev/sda5 231846150 499054591 267208442 127.4G Linux filesystem\n"
I would delete /dev/sd5 and make the following partition using Gparted in live session:
- 1000 MiB FAT32 as ESP
- the rest of the disk EXT4 as root system
Then I would choose the manual install:
mount ESP at /efi flag boot
mount root system at / no flag
Also go with systemd-boot.
[liveuser@eos-2023.03.26 ~]$ sudo parted -l
Model: ATA KINGSTON RBUSC18 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 473MB 472MB ntfs Basic data partition hidden, diag
2 473MB 790MB 317MB fat32 EFI system partition boot, esp
3 790MB 119GB 118GB ntfs Basic data partition msftdata
5 119GB 256GB 137GB ext4 endeavouros
4 256GB 256GB 543MB ntfs hidden, diag
Model: SEMC SD CCR-80 (scsi)
Disk /dev/sdb: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 1940MB 2060MB 120MB primary fat16 esp
[liveuser@eos-2023.03.26 ~]$ efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,2001,2002,2003
Boot0000* USB HDD: Generic STORAGE DEVICE PciRoot(0x0)/Pci(0x15,0x0)/USB(3,0)/HD(1,MBR,0x4d909e77,0x39d480,0x39000)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 15 / 03 05 06 00 03 00 / 04 01 2a 00 01 00 00 00 80 d4 39 00 00 00 00 00 00 90 03 00 00 00 00 00 77 9e 90 4d 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
data: 52 43
Boot0001* Windows Boot Manager HD(2,GPT,63bace09-3141-403c-90df-38dae4e5a336,0xe1800,0x97060)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000065000100000010000000040000007fff0400
dp: 04 01 2a 00 02 00 00 00 00 18 0e 00 00 00 00 00 60 70 09 00 00 00 00 00 09 ce ba 63 41 31 3c 40 90 df 38 da e4 e5 a3 36 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 65 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot2001* EFI USB Device RC
dp: 7f ff 04 00
data: 52 43
Boot2002* EFI DVD/CDROM RC
dp: 7f ff 04 00
data: 52 43
Boot2003* EFI Network RC
dp: 7f ff 04 00
data: 52 43
@pebcak what do you think about a new install “alongside” to win ?
Using grub and the ESP of win ?
(EOS does take about 1MB only when running grub, — so at my EOS )
That’s also a valid option.
Sommehow, previously OP’s attempt at installing Grub had failed. We could never know why that happened since no log could be retrieved because system froze up
The ‘manual’ option have been tried many times with both systemd-boot and grub. All same results - frozen system. Also tried a slightly older installer offline.
So I guess the only thing I havn’t tried yet is the ‘alongside’ version. But what about the disk partitions. Then you install on ntfs?
no ntfs for EOS
I know but if I install alongside windows that is on ntfs
yes, alongside win, but that doesn’t mean in ntfs
choose ext4 (or btrfs)
I see guess I have to merge my two partitions dev/sda3 and dev/sda5 before I start the install, so that the installer can do the shrinking of the windows partition…
I would delete sda5 only