Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux    |    Getting to be as bloated as Windows!    |    107,822 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 106,700 of 107,822    |
|    Paul to bad sector    |
|    Re: migrating existing desktop to EFI bi    |
|    15 Dec 24 02:12:28    |
      From: nospam@needed.invalid              On Sat, 12/14/2024 9:52 PM, bad sector wrote:       >       > Since Intel have decided to fianally kill legacy BIOS in 2025 I have no       choice left. Knowing this day would come I've already created an EFI #1       partition, formatted with       >       > # mkfs.fat -F 32 /dev/sda1       >       >       > The current OS partitions are 10-17       >       > Device Start End Sectors Size Type       > /dev/sda1 2048 2099199 2097152 1G EFI System       > /dev/sda2 1348483072 1350580223 2097152 1G BIOS boot       > /dev/sda3 4196352 16779263 12582912 6G Linux swap       > /dev/sda4 16779264 16781311 2048 1M Linux       filesystem       > /dev/sda5 16781312 16783359 2048 1M Linux       filesystem       > /dev/sda6 16783360 16785407 2048 1M Linux       filesystem       > /dev/sda7 16785408 16787455 2048 1M Linux       filesystem       > /dev/sda8 16787456 16789503 2048 1M Linux       filesystem       > /dev/sda9 16789504 16791551 2048 1M Linux       filesystem       > /dev/sda10 16791552 593508351 576716800 275G Linux filesystem       > /dev/sda11 593508352 761280511 167772160 80G Linux filesystem       > /dev/sda12 761280512 929052671 167772160 80G Linux filesystem       > /dev/sda13 929052672 1096824831 167772160 80G Linux filesystem       > /dev/sda14 1096824832 1264596991 167772160 80G Linux filesystem       > /dev/sda15 1350580224 1518352383 167772160 80G Linux filesystem       > /dev/sda16 1518352384 1686124543 167772160 80G Linux filesystem       > /dev/sda17 1686124544 1853896703 167772160 80G Linux filesystem       >       > My current motherboard supports Legacy BIOS only but I'm getting a new board       that supports EFI (only I think). How do I get the new motherboard started up       using my existing boot disk above?       >       > What happens when the disk fails? What's the BIOS and boot recovery after I       restore all partitions form images? Can I also keep an image of the EFI       partition and run again with that after a recovery?       >       > TIA              On a brand new disk, install a "teaser OS" as a means       of updating the key store on the new system.              Allow the teaser OS to run the show long enough, for a       new kernel to come in, and for the distro packages to be       updated.              Upon the reboot, the MOKUTIL will appear, and it will       try to update *two* things. Do not stop it, because you       will only have info about the first thing it is trying       to update. You will need a second machine, to consult       Google as to what to do, or what the possible responses       might be.              Once the teaser OS is stable, clone over the remaining OSes.       Do an upgrade-grub, so OS-prober adds them to the menu.              When one of the cloned OSes updates its kernel, it might       well assert MOKUTIL on the next reboot too.              It's at this point, you might notice the EFI messages change       from two lines to three lines. And then you might wonder       about the health of the thing.              As far as I know, for serious Secure Boot issues, it will       stop dead. Warnings from EFI don't prevent you from running,       so I suppose that "makes it OK". I would personally prefer       though, that the same two line status appear each time,       as proof the multi-boot is "living in harmony". The threads       I can pick up in a Google, are not suggestive that anyone       thinks multi-boot is well supported as such.              These are two examples of recorded messages, just to show       what hairballs come out of the thing.               EFI stub: WARNING: Failed to measure data for event 1: 0x80000000        EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path        EFI stub: WARNING: Failed to measure data for event 0: 0x80000000        EFI stub: UEFI Secure Boot is enabled.              and after a teaser install               EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path        EFI stub: Measured initrd data into PCR 9        EFI stub: UEFI Secure Boot is enabled.              I have also seen references to PCR 7. Am I using up a resource ? Dunno.               Paul              --- SoupGate-DOS v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca