On Jul 5, 2024, at 04:00, François Patte <francois.patte@xxxxxxxxxxxxxxxxxxxx> wrote: > > Le 2024-07-05 03:03, Tide Ka a écrit : >>> Should I understand that if you have a windows installation on a disk with some (big) space left, you cannot install f40 as a dual boot system? (because anaconda is unable to ignore the windows partition) >> That (dual-boot) is based upon anaconda's behaviour. Basically it is >> about telling bootloader about other partitions to boot from by adding >> more entries. >> Anaconda being unable to ignore partition, in case of preparing a >> dual-boot, should not be the root cause. As you cannot add an entry >> for a partition if you simply ignore it. >> Just like others have mentioned, you may consider adding another entry >> to existing bootloader configuration instead of trying to make another >> ESP. > > How can I do that? I have a /boot partition (RAID1 array) containing kernel stuff for installed fedora 36 (config, initramfs, System.map, vmlinuz...) and some directories: > > efi/EFI/fedora/ (empty) > > grub2/ a lot of things for grub (config, etc...) > > loader/entries > > How can I use this partition to tell anaconda to add fedora 40 system boot? > > Thank you. Is it possible that your Fedora 36 install was installed as a BIOS boot install, but you’ve booted the Fedora 40 installer as an EFI boot? You can’t install a non-efi bootloader if you booted via EFI bootloader on installer. That would explain why there’s no EFI volume on your 36 install. -- Jonathan Billings -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
