From: forkosh@panix.com   
      
   Henrik Carlqvist wrote:   
   > On Wed, 08 Feb 2023 09:10:12 +0000, John Forkosh wrote:   
   >> the latest (-current64 as of 2/7/23)   
   >   
   > I have only experience from stable versions of Slackware like 15.0   
   > and older.   
      
   Yeah, I think I've had this problem before (last install on this   
   non-uefi box was 8/19/21 using 15.0x64 rc1), but not quite sure.   
      
   >> warned me it couldn't find any efi partitions, and that lilo   
   >> wouldn't work (which indeed it didn't)   
   >   
   > In which way did not lilo work?   
      
   "corrupt partition" fatal warnings. Running lilo -P ignore let   
   it run to completion, but didn't actually install on root block   
   ("boot = /dev/sda4" in lilo.conf), as far as I can tell.   
      
   > Did it complain when you ran lilo to install it in MBR?   
      
   Not at all, but that was an even older install on /dev/sda1,   
   from -current64 as of 9/1/19.   
      
   > Did it fail to boot? If so, what did you see on your screen at that   
   > failure?   
      
   Booted just fine. But I first booted into the above-mentioned   
   sda1 partition, edited its /etc/lilo.conf to add a section   
   for the new sda4 install...   
    # Linux bootable partition config begins   
    image = /mnt/sda4/boot/vmlinuz   
    root = /dev/sda4   
    label = slk150x64sda4   
    read-only # Partitions should be mounted read-only for checking   
    # Linux bootable partition config ends   
   and issued a mount /mnt/sda4/ /dev/sda4 to make that partition   
   visible. Then reran lilo so it would show up on boot menu. And this   
   lilo.conf has "boot = /dev/sda" so that it's the 9/1/19 slack15   
   that's installing on the mbr. And then rebooting indeed showed the   
   new partition on the boot menu, and booted into it without a hiccup.   
      
   > During the years I have mostly run lilo to boot Slackware installations.   
   > To be able to do that I have on newer machines had to enable legacy boot   
   > in CMOS setup.   
      
   Right. Now that you mention it, I recall "legacy boot" on some bioses.   
   I'll have to check that on this box's bios and see if maybe it's been   
   somehow reset. (And I also further checked that usbimg2disk.sh script,   
   which I usually run as   
    ./usbimg2disk.sh -f -s slackware64-current-07Feb2023 -o /dev/sdc   
   and I'm wondering if I should omit the -f and format the stick   
   myself before running usbimg2disk.)   
      
   > On some newer machines I have booted with UEFI on GPT   
   > partitions with some other bootloader than lilo, but to my surprise I   
   > have also found that lilo seems to work with a GPT partition and legacy   
   > boot.   
      
   Good to know. I've been keeping my boot disks to 2TB (usually   
   a 2.5" 1TB ssd) so that I could continue using fdisk. But I guess   
   maybe that's not necessary.   
      
   > regards Henrik   
   Thanks for all the help.   
      
   --   
   John Forkosh ( mailto: j@f.com where j=john and f=forkosh )   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|