

⋅ the settings of your bios ( is it UEFI ? is it UEfi-in-legacy-mode ? is SecureBoot disabled ? ) To avoid that, you must chose to do « something else » at installation time, in Ubiquity ( not « install beside existing OS » I don’t know how it’s worded in English ) and there do your partitioning the way you like or targeting previously prepared partitions.įirst things to check before installation are

If Ubiquity sees an UEFI compliant bios it will imediatly do the UEFI compliant partitioning - even if you already have other OS installed in non-UEFI partitioning… Even if the disc has an mbr/msdos partition table… and here starts the glorious mess. Older bios are not UEFI.ġ00% UEFI implies GPT partition table + a different partitioning compared to non-UEFI ( legacy mode or older bios ). I don’t understand “If you target an UEFI bios in legacy mode, or an old classic bios”.ĭepending on bios type, you’ll have to act differently with Ubuntu installer ( ubiquity ).Ī modern UEFI can be set to run in « legacy » mode.
