home bbs files messages ]

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,701 of 107,822   
   Phillip Frabott to bad sector   
   Re: migrating existing desktop to EFI bi   
   15 Dec 24 01:09:37   
   
   From: nntp@fulltermprivacy.com   
      
   On 12/14/2024 21:52, 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   
   >   
   >   
   >   
   >   
      
   Least I'm mistaken, the only real change you'll need will be to grub2.   
   (I'm assuming your bootloader. YMMV). EFI partition will need to be   
   mounted (either to /efi or to /boot but standards will say /efi is the   
   way to go. Regardless of what you choose be sure that grub2 is updated   
   and you will probably need the efi boot manager (efibootmgr) and efivar   
   installed for grub2. (Assuming you use a package manager, those will be   
   present, otherwise use the directions from BLFS handbook)   
      
   You also need some kernel changes. This page includes the kernel changes   
   you need to make:   
      
   https://linuxfromscratch.org/blfs/view/stable-systemd/postlfs/grub-setup.html   
      
   Look at section "Kernel Configuration for UEFI support" section (it's   
   the first one.) Also you need secure boot off unless you sign your files   
   (out of scope for your question).   
      
   Execute command   
      
   [ grub-install --target=x86_64-efi --efi-directory=/efi   
   --bootloader-id=GRUB ]   
      
   you'll likely need to run   
      
   [ grub-mkconfig -o /boot/grub/grub.cfg ]   
      
   That should be everything. Be sure to update your /etc/fstab with the   
   EFI partition details. UEFI does not use any boot sectors or special   
   areas of the drive. It will simply look for a partition FAT32/VFAT of   
   type EFI and then look for a specific efi file in a specific directory   
   (/efi/EFI/bootx64.efi or /efi/EFI/grubx64.efi usually) and execute the   
   code in the efi binary. That gets the boot process started before it   
   hands it to the normal linux boot process from there.   
      
      
   Phillip Frabott   
   ----------   
   - Adam: Is a void really a void if it returns?   
   - Jack: No, it's just nullspace at that point.   
   ----------   
      
   --- 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