Bionic 64 installs, but not fossapup64-9.5

[bigpup]

Stop calling it Focal 64.
It is Fossapup64 9.5.

[barquest]

Tails recommends using the Restore Disk Image function of GNOME Disk Utility to "burn" a LiveUSB. It works fine for that, so I tried it with Fossapup64 9.5, but it resulted in the same grub/whatever screens mentioned before. That functionality probably uses dd, so the result is not surprising.

[Deanus]

Hi all,

Complete puppy newbie here. I ran into the same problem (I ended up staring at grub4dos while booting fossa from usb). I managed to boot by typing root=(hd0)/ then going back to the menu and selecting the first entry.

Not sure if that says anything new or if it helps.

Dean

[hesparza]

The solution posted by Deanus worked for me.

You just need to run command: root=(hd0)/
Then hit escape and then hit enter, it should load the menu this time.

Thank you very much Deanus!

[mikewalsh]

Hm. I confess, I'm finding this hard to understand, but.....well. Could be because I'm something of a Puppy "veteran" by now, with years of experience with Puppy's quirks & foibles.

Still.....

I have Fossapup64 9.5 running on two machines, as many of you know. The 'new' HP desktop rig; 2019-vintage, so UEFI-equipped.....and the refurb'd Dell Latitude D630 I bought last year to replace the truly ancient 2002 Inspiron lappie, which turned up its toes after 21 years of sterling service. This is approx 2008-vintage, and is very definitely the older MBR/BIOS configuration.

Despite that modern Pups now come equipped with a different bootloader system, I still run Grub4DOS. It's simple; it's elegant; I fully understand what I'm doing with it.....and for me, it just works.

The reason I continued using it with the new desktop rig was, I guess, mainly because I chose to install an elderly, nearly 8-yr old Puppy as the first occupant of the new 'kennels'.......unlike most of you, who would almost certainly have chosen to run the very newest Puppy with a brand-new machine. I'm strange like that..!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It took a wee while to figure out the boot 'stanzas' for Grub4DOS so they would work with this new UEFI stuff. I think I took inspiration from some of rcrsn51's work with the DebianDog 'starter kit'.....but the "menu.lst" I use ended up looking like the following:-

Code: Select all

# menu.lst produced by grub4dosconfig-v1.9.3
color white/blue black/cyan white/black cyan/black
splashimage=/pupsplash2.xpm
timeout 20
default 0

# Frugal installed Puppy

title Quirky 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Quirky64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Quirky64 pmedia=satahd pfix=fsckp
  initrd /Quirky64/initrd.gz
  
title Fossapup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Fossapup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Fossapup64 pmedia=satahd pfix=fsckp edd=off
  initrd /Fossapup64/initrd.gz  
  
title F96-CE_64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /F96-CE/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/F96-CE pmedia=satahd pfix=fsckp edd=off net.ifnames=0
  initrd /F96-CE/initrd.gz
  
title Bionicpup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Bionicpup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Bionicpup64 pmedia=satahd pfix=fsckp
  initrd /Bionicpup64/initrd.gz
  
title JammyPup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /JammyPup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/JammyPup64 pmedia=satahd pfix=fsckp
  initrd /JammyPup64/initrd.gz
  
title Studio 1337
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Studio1337/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Studio1337 pmedia=satahd pfix=fsckp
  initrd /Studio1337/initrd.gz
  
title Tahrpup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Tahr64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Tahr64 pmedia=satahd pfix=fsckp
  initrd /Tahr64/initrd.gz
  
title Xenialpup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Xenialpup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Xenialpup64 pmedia=satahd pfix=fsckp
  initrd /Xenialpup64/initrd.gz
  
title BookwormPup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Bookworm64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Bookworm64 pmedia=satahd pfix=fsckp
  initrd /Bookworm64/initrd.gz  
  
title Vanilla DPup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /VanillaDPup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/VanillaDPup64 pmedia=satahd pfix=fsckp edd=off net.ifnames=0
  initrd /VanillaDPup64/initrd.gz
  
title
  root

title ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  root
  
title Xenialpup 32 (+64)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Xenial32_64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Xenial32_64 pmedia=satahd pfix=fsckp
  initrd /Xenial32_64/initrd.gz
  
title Tahrpup 32 (+64)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Tahr32_64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Tahr32_64 pmedia=satahd pfix=fsckp
  initrd /Tahr32_64/initrd.gz  
  
title
  root

title ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  root
  
title Slacko 560
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Slacko560/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3 psubdir=/Slacko560 pmedia=satahd pfix=fsckp
  initrd /Slacko560/initrd.gz
  
title Slacko 571
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Slacko_571/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Slacko_571 pmedia=satahd pfix=fsckp
  initrd /Slacko_571/initrd.gz  
  
title Tahrpup 32
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Tahr32/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Tahr32 pmedia=satahd pfix=fsckp
  initrd /Tahr32/initrd.gz
  
title Xenialpup 32
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Xenial32/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Xenial32 pmedia=satahd pfix=fsckp
  initrd /Xenial32/initrd.gz
  
title
  root

title ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  root
  
# 'Portable' Linux

title Porteus 5.0 KDE (sdc1/boot)
  rootnoverify (hd2,0)
  chainloader +1  
  
title
  root

title ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  root

#Full installed Linux

title Haiku OS (sdc2/EFI)
  rootnoverify (hd2,0)
  chainloader +1
  
title ChromeOS Flex (sdc12/efi)
  rootnoverify (hd3,11)
  chainloader +1
  
title
  root

title ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  root
  
# Advanced Menu
title Advanced menu
  configfile /menu-advanced.lst
  commandline

The business with the blank 'title' & 'root' entries, and dotted lines, I picked up from one of our members over the last year or so. It's their way of being able to tidy-up & re-organise the menu so as to group certain things together; I use it to keep 64-bitzers together, 32-bitzers together, plus a couple of 32-bitzers that use peebee's marvellous 64-bit compat SFS (so modern browsers can be used).

Finally, a couple of chainloaders to externally-installed OSs that had their own bootloaders installed. These CAN be started through the Advanced Menu, but it's just nice to have entries for them in the main Menu as well.

(I'm using what amounts to the exact same set-up in the older, BIOS-equipped Latitude.....just with the UUIDs & locations adjusted to suit).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Perhaps the above might help some of our 'noobs' that are posting with issues concerning this stuff. Hopefully, it may be of some use...

(*shrug...*)

Mike.

[stevie pup]

I can understand your frustration. I have FossaPup 9.5 frugal installed, with Grub4DOS bootloader, to a portable hard drive. All my laptops are fairly old and all are BIOS only. It doesn’t matter which laptop I plug the drive into, FossaPup 9.5 always boots without any issues.

However, it hasn’t been plain sailing all along, and I had some problems at the beginning which I started a thread about. When I first installed the files I then ran the Grub4DOS bootloader, and it wouldn’t boot. Can’t remember now what error messages I got.

So I started again, and it still wouldn’t boot. Third attempt and it failed again. I was on the verge of giving up but decided to give it one last try, 4th attempt and it suddenly booted. And it’s booted ok ever since.

I should point out that on that final attempt I did nothing whatsoever any differently to what I had done on the previous 3 attempts. So why the first 3 failed and the 4th was a success remains a mystery.