#EndeavourOS/Windows 11 Dual Boot Problems
77 messages · Page 1 of 1 (latest)
why is that entry for efibootmgr so big?
and yeah, grub isn't there
when you installed grub did you do it on the same efi partition as windows efi, or it's own one?
gave me the option to either choose the existing one or make a new one
and you selected?
so I chose the existing one
I always like to have it on a dedicated one, so that windows is less likely to fuck with it
and if anything goes wrong, I can just start fresh without worrying about messing with windows shit lol
which is what I suggest we do this time, can you make a 1 gig efi partition?
absolutely, one sec
make it fat 32, and then mount it to either /boot or /boot/efi, which ever you prefer, you can check which you had by checking the /etc/fstab file if you mount your root partition
in case I'm not here when you need help:
.aw grub
you'll want to install grub, install the kernel, and make the configuration
you'll also want to make sure that your /etc/fstab aligns with your UUID's
mount all the drives in /etc/fstab manually, and then run lsblk -f to make sure the UUID's are correct
you can just comment out the windows efi instead though
you may need to remake the grub-mkconfig if windows isn't showing up by booting into your system and making sure os-prober is installed and enabled, and that your windows drive is mounted
Much appreciated - in Gparted at the moment, and it does not seem to give me the option to make a new partition
does it say why?
Had to resize an existing partition to make the space, there we go
personally I use fdisk, most people use cfdisk, but yeah, whatever works, just remember, EFI
Tbh might do that. Doesn't give me an option to make this one efi
you already have the unallocated space so, yeah
or if you made it, just delete it using one of those two, and remake it
I would save the changes so far in gparted, then use gdisk to create the partition, as you can set the type to ef00 easily via the tui
lol, you can set efi easily in fdisk and cfdisk too, but, it's all much the sameness
did you look at the efibootmgr above @tropic herald ?
yes, something happened to it for sure
What if I were to start with a clean slate? Haven't done much on Linux yet so wouldn't mind just reinstalling it. This time I would have it make a new EFI partition instead of using the existing one
@rigid sand
Ended up reinstalling and had it make a new EFI partition. Doesn't appear in boot order now either
pretty lost tbh, not sure how to make it appear. Also wouldn't mind not using grub and adding it to the windows boot manager instead
did you install grub to the efi partition as per the wiki article I gave you?
show me lsblk -f
once you've mounted root and boot
.s rs
<command to print output> |& curl --data-binary @- https://paste.rs
Let me show you where I'm at right now
this is the EFI that endeavor automatically made it would appear
here's the main endeavor partition
here's the main windows partition
With this, it gives me the option to edit mount point as well if that helps
@tropic herald
Trying to follow your guide Vegan but completely lost at this point tbh. Also for some reason Windows has disappeared from bios as well
And I boot into the error "file /boot/grub/x86_64-efi/normal.mod" not found
Mount the efi and look at what’s in it
If you’ve done a fresh install I don’t understand how it could be broken
Is the new grub the default boot option?
I don't understand it either 🤷♂️ but yeah grub is default now, just that when it boots into it that error pops up
Cut off one head, two more grow back lol
Yeah Mount the boot in the iso, and then ls it
How would I do that? I'm in KDE partition manager at the moment, and it does give me the option to edit mount point, no mount point is set at the moment though
Open a terminal
mount —mkdir /dev/partition you want /myveryspecialmountpoint
Change the partition and the mountpoint
So my EFI partition is /dev/sda1
and my main endeavor partition is /dev/sda6
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 0 100% /run/archiso/airootfs sda ├─sda1 vfat FAT32 CC9E-1FB7 68.7M 28% /myveryspecialmountpoint ├─sda2 ├─sda3 ntfs AEB05A2FB059FE71 ├─sda4 ntfs 026489DE6489D4B7 ├─sda5 ntfs 24F44403F443D628 └─sda6 ext4 1.0 endeavouros 62ab8c9c-6e6b-4d4a-b9b0-0bbaee925c26 sdb iso9660 Joliet Extensio EOS_202401 2024-01-25-18-25-14-00 ├─sdb1 iso9660 Joliet Extensio EOS_202401 2024-01-25-18-25-14-00 0 100% /run/archiso/bootmnt └─sdb2 vfat FAT16 ARCHISO_EFI 8093-0377 sr0
^ results of lsblk -f
Yeah, you need to mount
How does this look?
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 0 100% /run/archiso/airootfs sda ├─sda1 vfat FAT32 CC9E-1FB7 68.5M 29% /mnt/boot/efi ├─sda2 ├─sda3 ntfs AEB05A2FB059FE71 ├─sda4 ntfs 026489DE6489D4B7 ├─sda5 ntfs 24F44403F443D628 └─sda6 ext4 1.0 endeavouros 62ab8c9c-6e6b-4d4a-b9b0-0bbaee925c26 424.6G 2% /mnt sdb iso9660 Joliet Extension EOS_202401 2024-01-25-18-25-14-00 ├─sdb1 iso9660 Joliet Extension EOS_202401 2024-01-25-18-25-14-00 0 100% /run/archiso/bootmnt └─sdb2 vfat FAT16 ARCHISO_EFI 8093-0377 sr0
ls /mnt/boot/efi
EFI 'System Volume Information'
all it says @rigid sand
command I ran to install grub was
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=endeavour
Does this
efi-directory=/boot/efi
need to be this
efi-directory=/mnt/boot/efi
It does if you aren’t chrooted
There’s no kernel or config
Unmount your boot, Mount your root, mount your boot into the root, and then arch-chroot into the root, reinstall the kernel, and make the grub-mkconfig
oh I didn't see on mobile you had root mounted already