Exactly - reverse what you did, reverse everything I told you to do! It is not exactly rocket science - undo the edits.
I get the boot screen with the multiple options for boot and recover but none of them work.
The kernel options with recover produce errors (not all disks have been found).
I changed /etc/kernel/cmdline
and /etc/default/grub
back to the original lines and deleted
/etc/modprobe.d/nvidia-power-management.conf.
Sorry I’m not as astute as you are using endeavour!
How do I change sudo grub-mkconfig -o /boot/grub/grub.cfg?
I don’t know what has screwed up here, chroot in from the live media and re-run sudo grub-mkconfig -o /boot/grub/grub.cfg
Which grub was in use ? Mint or EnOS?
You need to be using either systemd-boot or Grub. Not both. The system is configured differently depending on which one.
If you can boot up your live usb, provide the following info (to begin with):
sudo parted -l
efibootmgr
Also, what file system did you choose in the installer when you installed the system?
I didn’t get an option when installing yesterday but it’s systemd-boot I’m pretty sure.
https://ibb.co/Hzpgfzw
Looks like you are using systemd-boot.
It would be helpful if you could provide the output of the commands as requested above.
This sounds a bit odd. There is always a dropdown menu from which you could choose the filesystem type.
This sounds a bit odd. There is always a dropdown menu from which you could choose the filesystem type.
Pretty sure the option I chose was to “choose disk and install”.
Endeavour is installed on /dev/nvme4n1
https://ibb.co/bvtFB7C
sudo parted -l
Model: ATA HGST HDN724040AL (scsi)
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
2 135MB 4001GB 4001GB ntfs Basic data partition msftdata
Model: SanDisk Extreme SSD (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 1000GB 1000GB primary boot
2 1000GB 1000GB 33.6MB primary fat16 esp
Model: USB DISK 3.0 (scsi)
Disk /dev/sdc: 15.5GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 2688MB 2855MB 167MB primary fat16 esp
Model: Realtek RTL9210B-CG (scsi)
Disk /dev/sdd: 2000GB
Sector size (logical/physical): 512B/2048B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 2000GB 2000GB ext4
Model: Realtek RTL9210B-CG (scsi)
Disk /dev/sde: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 2000GB 2000GB primary ext4
Model: Corsair MP600 PRO XT (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 512MB 511MB fat32 boot, esp
2 512MB 101GB 100GB ext4
3 101GB 2000GB 1900GB ext4
Model: PNY CS2241 4TB SSD (nvme)
Disk /dev/nvme3n1: 4001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB ext4 4TBNVMe
Model: PNY CS2241 4TB SSD (nvme)
Disk /dev/nvme2n1: 4001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB ext4 NVME4TB2
Model: PNY CS2241 2TB SSD (nvme)
Disk /dev/nvme1n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2000GB 2000GB ext4 2TBNVMe1
Model: PNY CS2241 2TB SSD (nvme)
Disk /dev/nvme4n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 2097kB 1076MB 1074MB fat32 EFI boot, esp
2 1076MB 2000GB 1999GB ext4 endeavouros
[liveuser@eos-2024.04.20 ~]$ efibootmgr
BootCurrent: 0016
Timeout: 1 seconds
BootOrder: 0016,0000,0003,000F,0012,0015,0017,0001,0013,0014
Boot0000* rEFInd Boot Manager HD(1,GPT,07669e0e-2a1d-40bc-8e75-44a477cc1e22,0x800,0xf3800)/\EFI\REFIND\REFIND_X64.EFI
Boot0001* ubuntu HD(1,GPT,07669e0e-2a1d-40bc-8e75-44a477cc1e22,0x800,0xf3800)/\EFI\UBUNTU\SHIMX64.EFI
Boot0003* Linux Boot Manager HD(1,GPT,33035a2f-c77e-4df3-8991-49ef181bf0c9,0x1000,0x200000)/\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI
Boot000F* UEFI OS HD(1,GPT,33035a2f-c77e-4df3-8991-49ef181bf0c9,0x1000,0x200000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0012* Hard Drive BBS(HD,,0x0)0000474f00004e4fb7000000010000007b0043006f007200730061006900720020004d0050003600300030002000500052004f0020005800540000000501090002000000007fff040002010c00d041030a0000000001010600010101010600000003171000010000006479a77b6ac010217fff040001043e00ef47642dc93ba041ac194d51d01b4ce63200330032003000370039003300390030003000300031003300310030003200300031003400410000007fff04000000424f00004e4fbd00000001000000810048004700530054002000480044004e0037003200340030003400300041004c00450036003400300000000501090002000000007fff040002010c00d041030a0000000001010600020101010600000001010600000a01010600000003120a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000200020004b00500033003100380033003400500036004800450041004200320000007fff04000000424f00004e4fb3000000010000007b0050004e00590020004300530032003200340031002000320054004200200053005300440000000501090002000000007fff040002010c00d041030a0000000001010600010301010600000003171000010000006479a771da304be97fff040001043e00ef47642dc93ba041ac194d51d01b4ce650004e0059003200320035003100320032003100320032003200300031003000330044003700410000007fff04000000424f00004e4fb3000000010000007b0050004e00590020004300530032003200340031002000340054004200200053005300440000000501090002000000007fff040002010c00d041030a0000000001010600020301010600000003171000010000006479a77a10c002107fff040001043e00ef47642dc93ba041ac194d51d01b4ce650004e0059003200330031003800320033003000350030003200300031003000330030003000330000007fff04000000424f00004e4fb3000000010000007b0050004e00590020004300530032003200340031002000340054004200200053005300440000000501090002000000007fff040002010c00d041030a0000000001010600030301010600000003171000010000006479a7733a20069b7fff040001043e00ef47642dc93ba041ac194d51d01b4ce650004e0059003200330030003200320033003000310031003300300031003000300034003500460000007fff04000000424f00004e4fb3000000010000007b0050004e00590020004300530032003200340031002000320054004200200053005300440000000501090002000000007fff040002010c00d041030a0000000001010600040301010600000003171000010000006479a771da304b0f7fff040001043e00ef47642dc93ba041ac194d51d01b4ce650004e0059003200320035003100320032003100320032003200300031003000330044004300360000007fff04000000424f
Boot0013* USB BBS(Floppy,,0x0)0000474f00004e4fb70000000100000073005200650061006c00740065006b002000520054004c00390032003100300042002d0043004700200031002e003000300000000501090001000000007fff040002010c00d041030a000000000101060002010101060000000101060000060101060000000305060006000305060003007fff040001042e00ef47642dc93ba041ac194d51d01b4ce630003100320033003400350036003700390030003300390000007fff04000000424f
Boot0014* USB BBS(HD,,0x0)0000474f00004e4fb70000000100000073005200650061006c00740065006b002000520054004c00390032003100300042002d0043004700200031002e003000300000000501090002000000007fff040002010c00d041030a000000000101060002010101060000000101060000060101060000000305060002000305060002007fff040001042e00ef47642dc93ba041ac194d51d01b4ce630003100320033003400350036003700390030003300390000007fff04000000424f00004e4fc9000000010000008500530061006e004400690073006b002000450078007400720065006d00650020005300530044002000310030003100320000000501090002000000007fff040002010c00d041030a000000000101060002010101060000000101060000060101060000000305060000007fff040001044600ef47642dc93ba041ac194d51d01b4ce633003100330038003300350033003200330032003300340033003400330030003300300033003400330031003300300000007fff04000000424f00004e4fad000000010000007500200055005300420020004400490053004b00200033002e003000200050004d004100500000000501090002000000007fff040002010c00d041030a000000000101060002010101060000000101060000080101060001000305060009007fff040001043600ef47642dc93ba041ac194d51d01b4ce6300037003000410038004100410033004400460036004600380032003600350000007fff04000000424f
Boot0015* ubuntu HD(2,MBR,0x542fda33,0x746f6800,0x10000)/\EFI\UBUNTU\GRUBX64.EFI0000424f
Boot0016* UEFI: USB DISK 3.0 PMAP PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(9,0)/CDROM(1,0x501b60,0x4fa98)0000424f
Boot0017* UEFI: USB DISK 3.0 PMAP, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(9,0)/HD(2,MBR,0x7498467c,0x501b60,0x4f800)0000424f
[liveuser@eos-2024.04.20 ~]$
Endeavor is installed on /dev/nvme4n1
Disk /dev/nvme4n1: 2000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 2097kB 1076MB 1074MB fat32 EFI boot, esp 2 1076MB 2000GB 1999GB ext4 endeavouros
Thanks for the output!
In the continuation, if you get any error message at any step, stop and post the whole of the terminal output here
Make sure you are connected to the internet in the live session.
Now let’s set up a chroot to get into your installed system:
1.
sudo mount /dev/nvme4n1p2 /mnt
2.
sudo mount /dev/nvme4n1p1 /mnt/efi
3 .
sudo arch-chroot /mnt
Now in the chroot:
update the system:
pacman -Syu
remove the package Grub:
pacman -R grub
reinstall systemd-boot’s efi binary:
bootctl install
revert the changes you made in
/etc/kernel/cmdline
regenerate initrds and boot entries:
reinstall-kernels
If everything is fine so far:
-
type exit followed by enter to quit chroot
-
-
reboot
This is results so far?
[liveuser@eos-2024.04.20 ~]$ sudo mount /dev/nvme4n1p2 /mnt
[liveuser@eos-2024.04.20 ~]$ sudo mount /dev/nvme4n1p1 /mnt/efi
[liveuser@eos-2024.04.20 ~]$ sudo arch-chroot /mnt
[root@EndeavourOS /]# pacman -Syu
:: Synchronizing package databases...
endeavouros is up to date
core 121.1 KiB 319 KiB/s 00:00 [----------------------------] 100%
extra 7.9 MiB 15.8 MiB/s 00:01 [----------------------------] 100%
multilib 138.4 KiB 364 KiB/s 00:00 [----------------------------] 100%
:: Starting full system upgrade...
there is nothing to do
[root@EndeavourOS /]# pacman -R grub
error: target not found: grub
[root@EndeavourOS /]# bootctl install
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/BOOT/BOOTX64.EFI".
⚠ Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! ⚠
⚠ Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole! ⚠
Random seed file /efi/loader/random-seed successfully refreshed (32 bytes).
Created EFI boot entry "Linux Boot Manager".
[root@EndeavourOS /]# /etc/kernel/cmdline
bash: /etc/kernel/cmdline: Permission denied
[root@EndeavourOS /]#
root@EndeavourOS /]# /etc/kernel/cmdline bash: /etc/kernel/cmdline: Permission denied [root@EndeavourOS /]#
You have to edit that file with an editor like nano for example:
nano /etc/kernel/cmdline
When you are done editing, press in turn, Ctrl-O, enter, Ctrl-X to save the file and quit nano.
Go on with the rest of the commands.
You have to edit that file with an editor like nano for example:
nano /etc/kernel/cmdline
This is what is in there now…
nvme_load=YES nowatchdog rw root=UUID=616f707c-d652-497d-a967-b2292a98d495
It looks good! You don’t need to make any changes.
Go on with the point 5 above and onward.
It looks good! You don’t need to make any changes.
Go on with the point 5 above and onward.
All done, and success!!! THANK YOU!!
Wondering now what I should do about the Nvidia driver?
Wondering now what I should do about the Nvidia driver?
I am not an Nvidia user so what I know is mostly theoretical.
I leave you in the capable hands of other forum members experienced with Nvidia cards.
EnOS provides a script for installing drivers for Nvidia graphics. You might want to have a look at it in the meantime:
https://discovery.endeavouros.com/nvidia/new-nvidia-driver-installer-nvidia-inst/2022/03/
Also, perhaps better to “archive” this thread an open a new one with a “catchy” title to attract attention to the issue at hand: driver installation for Nvidia (or some such)
Ok thanks, I’ll research that more. Thanks again for your help!
I had done a lot of customizations to my Desktop just in one day so very glad not having to do that again!
You are welcome! Good to know that your system is back up and running!
Good luck with resolving the Nvidia “issue” and enjoy your system and your time here on the forum!
Just about there but the terminal is complaining about…
sudo grub-mkconfig -o /boot/grub/grub.cfg … saying cmd not found.
it does not change anything as of grub is not installed… or not installed anymore or you removed the binary manually.
And if you were following ALL steps from this:
systemd-boot: edit /etc/kernel/cmdline cat /etc/kernel/cmdline nvme_load=YES quiet NVreg_PreserveVideoMemoryAllocations=1 nvidia_drm.modeset=1 nvidia-drm.fbdev=1 pci=nommconf nowatchdog rw root=UUID=1fe53a1a-6f4f-47df-a8cd-2f3d78155d7c resume=UUID=0942ac91-77f1-46a0-b31e-e10933c7b1bb Then: sudo reinstall-kernels Grub: edit /etc/default/grub Edit line GRUB_CMDLINE_LINUX_DEFAULT No example - sorry! Then: sudo grub-mkconfig -o /boot/grub/grub.cfg Enable services: sudo systemctl enable…
you was doing steps for both first for systemd-boot and second for grub… one or the other should have given error or warnings you should have seen in the terminal output.
But as of you do not have nvidia drivers installed the added cmd for this driver could prevent from boot already… plus… if you simple copy paste the example line:
nvme_load=YES quiet NVreg_PreserveVideoMemoryAllocations=1 nvidia_drm.modeset=1 nvidia-drm.fbdev=1 pci=nommconf nowatchdog rw root=UUID=1fe53a1a-6f4f-47df-a8cd-2f3d78155d7c resume=UUID=0942ac91-77f1-46a0-b31e-e10933c7b1bb
and these UUIDS are not yours it would also cause system to not properly boot…
If everything is fine so far:
6. type exit followed by enter to quit chroot
I think I may have not exited out of chroot correctly as I now have an “ownership” issue with sudo…
[jozey@jozeywhales ~]$ sudo pacman -Syu
sudo: /etc/sudo.conf is owned by uid 1000, should be 0
sudo: /etc/sudo.conf is owned by uid 1000, should be 0
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: error initializing audit plugin sudoers_audit
/etc/sudo.conf is owned by uid 1000, should be 0
Not really sure what is the best or easiest way to deal with this issue as I have never had to.
I would try though setting up the chroot (as per instructions given above) and once in the chroot:
chown root:root /etc/sudo.conf
chown root:root /etc/sudoers
exit
HTH
I would try though setting up the chroot (as per instructions given above) and once in the chroot:
I can’t use sudo to setup chroot, can I use su instead?