When I install from the newest iso usb everything goes well until the point where the bootloader get installed. Then everything stops. both offline and online. I install on a system where windows 10 is already installed and running. Can see windows has its own partition for /boot/efi. When I installed endeavouros on this laptop I made 3 partitions. One / root and one /boot/efi and on linuxswap.
Only way I could install endeavouros was without any bootloader.
After the install I tried to manually install grub but when it comes to actually installing, system goes down again.
Could it be that this laptop just dont want a linux system running together with windows? I dont mind getting rid of windows but I’m affraid same thing will happen with the bootloader, and then I have nothing. Any suggestions?
From the Live USB, please post the output of:
sudo parted -l
efibootmgr -v
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 123GB 4296MB linux-swap(v1) swap
6 123GB 124GB 524MB fat32 boot, esp
7 124GB 256GB 132GB ext4
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
I assume these are the partitions you made for your EnOS install.
In the live session, make sure you have network connection.
Open a terminal and run the following commands:
sudo mount /dev/sda7 /mnt
sudo mkdir -p /mnt/boot/efi
sudo mount /dev/sda6 /mnt/boot/efi
sudo arch-chroot /mnt
pacman -S grub
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=enos-grub
exit
Now check with efibootmgr to make sure an EFI boot entry has been created.
If you get any errors at any of the steps above, please post it here.
And please don’t forget to format the posted text by highlighting it and pressing Ctrl-E.
EDIT: correction
sudo mkdir -p /boot/efi should be sudo mkdir -p /mn/boot/efi
Sorry for that 
Thanks you. I just did this and when I press enter on the last command (grub-install) system freeze! seems like that is what is happening all the time.
I made a correction above.
Would you like to give it a try?
yes i’ll reboot. in the correction above sudo mkdir -p /boot/efi should be sudo mkdir -p /mn/boot/efi is it right that it is mkdir -p mn/boot/efi and not mkdir -p /mnt/boot/efi
This! Sorry for the typo again!
I should be getting some sleep 
@pebcak — don’t worry, be happy 
In case the installation of the bootloader fails again, I suggest you reinstall the system with Grub bootloader and all and if it fails again post the installation log on the forum. It might give us some more clues.
After a failed installation, run:
cat /home/liveuser/endeavour-install.log | eos-sendlogs
and post the URL you get in the terminal.
Thanks for the reminder 
I was getting a bit worried and unhappy about my repeated mistakes
you’re welcome,
we all are humans - and make mistakes sometimes
– no prob at all 
okay thanks so much, it will be tomorrow 
Me too!
Good night!
good night, just did the corrections again, and system freezes again. so no more tonight. talk another time. thanks
Tried to install system again including grub bootloader, and same thing happens arround 82% (installing bootloader) system freezes. So I cannot do anything except rebooting. So I guess the log files dissapear when i reboot the live iso. Or are they stored in another place?
I can show the hardware I installing on.
https://0x0.st/H8-W.txt
I do have a feeling that it is something with either windows or the computer.
In your UEFI-Bios, you need to disable fast-boot and secure-boot, I guess. Did you do that before trying to install Linux on a Windoze computer?
secure boot is disabled. I don’t see the fast boot option…
Yes, they do.
But after a failed install and before you reboot, run:
I guess you can forget about that one (my mistake), sorry! 