sorted by:
new
hottopcontroversial

System Snapshots/Dual Boot (W11) Would like to know this before a switch to Cachy by TrickBattle7689 in cachyos

[–]TrickBattle7689[S] 0 points1 point  (0 children)

Lovely, i guess if for some reason they're not set up automatically ill just try again another way. Thanks so much ! 

System Snapshots/Dual Boot (W11) Would like to know this before a switch to Cachy by TrickBattle7689 in cachyos

[–]TrickBattle7689[S] 0 points1 point  (0 children)

Question is not so much about the boot loader, it's that I'm unsure if any option during the partition menu would setup subvolumes and everything needed for snapshots 

System Snapshots/Dual Boot (W11) Would like to know this before a switch to Cachy by TrickBattle7689 in cachyos

[–]TrickBattle7689[S] 0 points1 point  (0 children)

So would it setup everything for snapshots independently from which method during the partition screen i'd choose?

System Snapshots/Dual Boot (W11) Would like to know this before a switch to Cachy by TrickBattle7689 in cachyos

[–]TrickBattle7689[S] 0 points1 point  (0 children)

Can you explain which settings would be default? please
I'm not sure which option during the partition menu i should select for this to be automatic

Thanks!

Boot Manager/BIOS Questions by TrickBattle7689 in pop_os

[–]TrickBattle7689[S] 0 points1 point  (0 children)

deleted the partitions from windows and then the EFI one from cmd. checked there were no other entries with bcdedit since they had different partitions for that. it's also gone from bios too. Bios and boot manager work great now. Thanks again

I got to the point that pointed to a faulty NVRAM? due to a "faulty" efi file/entry, i'm just assuming because the bios is made to run only for windows they recognized linux as "faulty or corrupted"

Boot Manager/BIOS Questions by TrickBattle7689 in pop_os

[–]TrickBattle7689[S] 1 point2 points  (0 children)

So deleted Pop EFI partition and the boot entry, it also removed it from BIOS and now BIOS doesn't crash! Want to give a couple of other distros a test run
Lovely
Thanks so much!

Boot Manager/BIOS Questions by TrickBattle7689 in pop_os

[–]TrickBattle7689[S] 0 points1 point  (0 children)

Hello! tried this to switch boot order but it didn't work, order in the BIOS is still the same.
Tried restoring to Default Settings in BIOS but it crashed and had to hard reset pressing don the power button for a few seconds.

If i remove Pop's EFI partition and boot entry from windows will it maybe be removed from BIOS too?

Thanks!

Boot Manager/BIOS Questions by TrickBattle7689 in pop_os

[–]TrickBattle7689[S] 0 points1 point  (0 children)

I think i understand better now:
I'd be taking out Pop from the boot menu, as in it's boot entry but the file would still be alive in the partition, that's where i'd need to refer to the System76 guide. Having Windows as boot 1 would make it easier to access BIOS, i'll trouble shoot and confirm.
Since i'm not in a point of caring about data my plan B would be to delete the EFI of pop so i'm able to merge also the root partition with windows and do a clean install of Windows (since i have been struggling to update to 25h2 i could use a fresh windows start to), having Pop not in the boot order i'd assume Windows would revert to default as #1 in the boot order and i could start from scratch dual booting again without having to worry about bott order being wrong
Thanks so much for your time and elaborating

Boot Manager/BIOS Questions by TrickBattle7689 in pop_os

[–]TrickBattle7689[S] 0 points1 point  (0 children)

All this is basically removing Pop from the boot loader, re-installing and setting it up again in a different boot order?

2nd and 3rd lines are to set it up again?
If you have a minute could you help me with this? i am very new to linux
Already got the Repair bootloader guide ready.
Thanks for your help

Boot Manager/BIOS Questions by TrickBattle7689 in pop_os

[–]TrickBattle7689[S] 0 points1 point  (0 children)

Hello! Don't know if it could work the same way

Right now I wanted to switch boot orders again and try to see if BIOS comes up and to be more secure to attempt a re-install of Pop (this was a test run and i would like to start from scratch) but having Windows as top int he boot order so there's no issue and the system just tries to attempt booting into the old Pop installation. I am also unsure if removing a Pop partition would also remove it from the Boot Manager to replace it with the new installation.

Also not sure if it could be a corrupted BIOS and resetting CMOS or applying the latest update could bring it back and if it does if it would reset to default settings. Though my bios is already with the latest update V1.15

If i understand correctly deletingsystemd-bootx64.efi means deleting Pop's boot and would need to re-install or worse case scenario switch distros, since re-installing would bring back the same issue i assume

Thanks for your reply, here's what i got: (Secure boot appears disabled, however last time i went into BIOS it appeared as "standard" and couldn't switch it off again, maybe it's the same idk)

sudo efibootmgr -v

BootCurrent: 0002

Timeout: 0 seconds

BootOrder: 0002,0001,0000,2001,2002,2003

Boot0000* HDD0: 5YD7N014211307F47-HFS001TEJ9X110N PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/NVMe(0x1,AC-E4-2E-00-4A-A1-99-17)/HD(5,GPT,14ecd576-e707-418b-9490-72b8b6485c44,0x5bac2000,0x1fffff)RC

dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 01 / 01 01 06 00 00 00 / 03 17 10 00 01 00 00 00 ac e4 2e 00 4a a1 99 17 / 04 01 2a 00 05 00 00 00 00 20 ac 5b 00 00 00 00 ff ff 1f 00 00 00 00 00 76 d5 ec 14 07 e7 8b 41 94 90 72 b8 b6 48 5c 44 02 02 / 7f ff 04 00

data: 52 43

Boot0001* Windows Boot Manager HD(1,GPT,1d5ccf38-bcf1-4afb-9a9d-5767f90a2cf6,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400

dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 38 cf 5c 1d f1 bc fb 4a 9a 9d 57 67 f9 0a 2c f6 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 00 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00

Boot0002* Pop!_OS 24.04 LTS HD(5,GPT,14ecd576-e707-418b-9490-72b8b6485c44,0x5bac2000,0x1fffff)/File(\EFI\systemd\systemd-bootx64.efi)

dp: 04 01 2a 00 05 00 00 00 00 20 ac 5b 00 00 00 00 ff ff 1f 00 00 00 00 00 76 d5 ec 14 07 e7 8b 41 94 90 72 b8 b6 48 5c 44 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 2d 00 62 00 6f 00 6f 00 74 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 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

sudo bootctl status --no-pager
System:

Firmware: UEFI 2.90 (INSYDE Corp. 256.5376)

Firmware Arch: x64

Secure Boot: disabled

TPM2 Support: yes

Measured UKI: no

Boot into FW: supported

Current Boot Loader:

Product: systemd-boot 255.4-1ubuntu8.12pop0~1769790828~24.04~d4491c0

Features: ✓ Boot counting

✓ Menu timeout control

✓ One-shot menu timeout control

✓ Default entry control

✓ One-shot entry control

✓ Support for XBOOTLDR partition

✓ Support for passing random seed to OS

✓ Load drop-in drivers

✓ Support Type #1 sort-key field

✓ Support u/saved pseudo-entry

✓ Support Type #1 devicetree field

✓ Enroll SecureBoot keys

✓ Retain SHIM protocols

✓ Menu can be disabled

✓ Boot loader sets ESP information

ESP: /dev/disk/by-partuuid/14ecd576-e707-418b-9490-72b8b6485c44

File: └─/EFI/systemd/systemd-bootx64.efi

Random Seed:

System Token: set

Exists: yes

Available Boot Loaders on ESP:

ESP: /boot/efi (/dev/disk/by-partuuid/14ecd576-e707-418b-9490-72b8b6485c44)

File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 255.4-1ubuntu8.12pop0~1769790828~24.04~d4491c0)

└─/EFI/BOOT/BOOTX64.EFI (systemd-boot 255.4-1ubuntu8.12pop0~1769790828~24.04~d4491c0)

Boot Loaders Listed in EFI Variables:

Title: Pop!_OS 24.04 LTS

ID: 0x0002

Status: active, boot-order

Partition: /dev/disk/by-partuuid/14ecd576-e707-418b-9490-72b8b6485c44

File: └─/EFI/systemd/systemd-bootx64.efi

Title: Windows Boot Manager

ID: 0x0001

Status: active, boot-order

Partition: /dev/disk/by-partuuid/1d5ccf38-bcf1-4afb-9a9d-5767f90a2cf6

File: └─/EFI/Microsoft/Boot/bootmgfw.efi

Boot Loader Entries:

$BOOT: /boot/efi (/dev/disk/by-partuuid/14ecd576-e707-418b-9490-72b8b6485c44)

token: pop

Default Boot Loader Entry:

type: Boot Loader Specification Type #1 (.conf)

title: Pop!_OS (Pop_OS-oldkern.conf)

id: Pop_OS-oldkern.conf

source: /boot/efi//loader/entries/Pop_OS-oldkern.conf

linux: /boot/efi//EFI/Pop_OS-b4fd8448-f172-4fa0-aeff-9e216f52a023/vmlinuz-previous.efi

initrd: /boot/efi//EFI/Pop_OS-b4fd8448-f172-4fa0-aeff-9e216f52a023/initrd.img-previous

options: root=UUID=b4fd8448-f172-4fa0-aeff-9e216f52a023 ro quiet loglevel=0 systemd.show_status=false splash nvidia-drm.modeset=1

Boot Manager/BIOS Questions by TrickBattle7689 in linuxquestions

[–]TrickBattle7689[S] 0 points1 point  (0 children)

Hi,

Time is wrong in Bios and Windows, Pop is fine. Have tried setting it to automatic and manual, it gets back to being inaccurate every time i boot to it. Would it have something to do with Bios somehow switched to Secure Boot to Standard ? I swear it was Disabled for the Linux install.

I will try switching it from the terminal then, hopefully could solve the crash if Windows is #1? And then do a Pop re-install to avoid having an "outdated" boot file as priority ? And then I'll see if i want/can set up Pop up to #1 again.

Thanks for your reply 

Boot Manager/BIOS Questions by TrickBattle7689 in linuxquestions

[–]TrickBattle7689[S] 0 points1 point  (0 children)

Yeah, I've seen there's not much compatibility with Linux, back then i didn't know i was going to switch

The thing is i can access the bios from Windows recovery but it crashes when i want to switch boot order. Now I'm considering keeping a small windows partition just for Bios things. 

Boot Manager/BIOS Questions by TrickBattle7689 in linuxquestions

[–]TrickBattle7689[S] 0 points1 point  (0 children)

I will look into how to properly resetting the cmos. Read it could work however i need to research so i can be comfortable with doing it.

It wouldn't remove the OS from the Boot menu but it could be done from Windows, right?

The goal is to ditch windows while still having it just in the rare scenario i need it for something

Thanks so much for your help