multibootusb working with fossa?

[galen]

I've tried installs 9.0 9.5 of fossa64 via multibootusb
upon reboot and selecting fossa this system drops to grub>
anyone have a solution of having MBUSB installing fossa?

USB stick msdos table
partition 1 fat32 lba
p2 multibootusb boot flag

system is bios not UEFI

bionic 32 or 64 works fine

PS please dont suggest another multiboot product especially ventoy

[bigpup]

I assume, multibootusb makes some kind of boot loader menu entry, for Fossapup64 9.5.

Can you post what is in the boot menu entry.
It probably just has the boot entry, wrong.

Could compare the files in the Fossapup64 9.5 iso, to what files, actually got put, on the USB.

[Clarity]

On some BIOS PCs that do not have firmware updates, you MUST start all boots from a cold start. Power the PC off, first, then try again to see if it boots.

@bigpup also asking important questions.

By your mention of Ventoy, you seem to be attempting to boot the ISO. Is that true?

There is a Puppy proven method available for the past year + for booting PUP/DOG ISOs without issues, while yielding all of the comforts expected from a live PUP.

[galen]

MBUSB uses a chain that includes
syslinux.cfg
it includes a section similar to bionic

Code: Select all

#start bionicpup64-8.0-uefi
LABEL bionicpup64-8.0-uefi
MENU LABEL bionicpup64-8.0-uefi
BOOT /multibootusb/bionicpup64-8.0-uefi/puppy.bs
#end bionicpup64-8.0-uefi

that .bs file indicates what MBUSB type of OS
this case
puppy
from there I guess it selects to use a .cfg in destination folder
isolinux
syslinux
inside one of those you'll find similar

Code: Select all

label puppy
linux vmlinuz
initrd initrd.gz
append pmedia=usbflash psubok=TRUE psubdir=/multibootusb/bionicpup64-8.0-uefi/
menu label bionicpup64 8.0
text help
Start bionicpup64 8.0 normally.
endtext

I'll try fossa again and get better .cfg files to dissect

[galen]

On some BIOS PCs that do not have firmware updates, you MUST start all boots from a cold start. Power the PC off, first, then try again to see if it boots.

@bigpup also asking important questions.

By your mention of Ventoy, you seem to be attempting to boot the ISO. Is that true?

There is a Puppy proven method available for the past year + for booting PUP/DOG ISOs without issues, while yielding all of the comforts expected from a live PUP.

Ventoy scripts for linux are not what I want.
I dont want to wipe the entire USB stick and be locked into non resizable stick partitions
Ventoy Linux instructions are lacking

[galen]

here's what MBUSB creates for a fossa grub.cfg

Code: Select all

insmod part_acorn
insmod part_amiga
insmod part_apple
insmod part_bsd
insmod part_dfly
insmod part_dvh
insmod part_gpt
insmod part_msdos
insmod part_plan
insmod part_sun
insmod part_sunpc

loadfont /multibootusb/fossapup64-9.5/boot/grub/font.pf2
set gfxmode=800x600
set gfxpayload=keep

insmod efi_gop
insmod efi_uga

insmod all_video
insmod video_bochs
insmod video_cirrus
insmod gfxterm
insmod png
insmod jpeg
terminal_output gfxterm

insmod ext2
insmod f2fs
insmod ntfs
insmod exfat

insmod loopback
insmod iso9660
insmod udf

background_image /multibootusb/fossapup64-9.5/boot/splash.png
set timeout=10

# https://help.ubuntu.com/community/Grub2/Displays
color_normal=cyan/black
#menu_color_highlight=black/light-gray
menu_color_highlight=yellow/red
menu_color_normal=light-gray/black

menuentry "fossapup64 9.5" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - Copy SFS files to RAM" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=copy,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - Don't copy SFS files to RAM" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=nocopy,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - RAM only" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=ram,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - No X" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=nox,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - No KMS (Kernel modesetting)" {
    linux /multibootusb/fossapup64-9.5/vmlinuz nomodeset pfix=fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - Ram Disk SHell" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=rdsh pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "Shutdown" {
	halt
}

menuentry "Reboot" {
	reboot
}

[tosim]

Here are Ventoy instructions:

========== Ventoy2Disk.sh ===============

sudo sh Ventoy2Disk.sh { -i | -I | -u } /dev/sdX sdX is the USB device, for example /dev/sdb.

Ventoy2Disk.sh CMD [ OPTION ] /dev/sdX
CMD:
-i install ventoy to sdX (fail if disk already installed with ventoy)
-I force install ventoy to sdX (no matter installed or not)
-u update ventoy in sdX

OPTION: (optional)
-r SIZE_MB preserve some space at the bottom of the disk (only for install)
-s enable secure boot support (default is disabled)
-g use GPT partition style, default is MBR style (only for install)

Please refer https://www.ventoy.net/en/doc_start.html for details.

========== VentoyWeb.sh ===============
1. sudo sh VentoyWeb.sh
2. open your browser and visit http://127.0.0.1:24680

========== VentoyWebDeepin.sh ===============
1. sudo sh VentoyWebDeepin.sh

========== CreatePersistentImg.sh ===============

sudo sh CreatePersistentImg.sh [ -s SIZE_IN_MB ] [ -t FSTYPE ] [ -l LABEL ] for example:

sh CreatePersistentImg.sh ----> persistence.dat in 1GB size and ext4 filesystem and casper-rw label
sh CreatePersistentImg.sh -l MX-Persist ----> persistence.dat in 1GB size and ext4 filesystem and MX-Persist label
sh CreatePersistentImg.sh -s 2048 ----> persistence.dat in 2GB size and ext4 filesystem and casper-rw label
sh CreatePersistentImg.sh -s 4096 -t xfs ----> persistence.dat in 4GB size and xfs filesystem (ext2/3/4 xfs are supported) and casper-rw label

Please refer https://www.ventoy.net/en/plugin_persistence.html for details.

[galen]

I have the Ventoy instructions, thanks

the big problem with Ventoy is that it LOCKS the exfat partition and
does not allow the saving of puppy persistent files
it forces puppy to use the VTOYEFI boot partition FAT16 32MB! to save
= not of use for me

[ThruHammer]

Too bad not all contributors can heed the OP's directive...

PS -- Please dont suggest another multiboot product, especially Ventoy.

[Clarity]

My question presented asks "were you looking to boot PUPPY 'live' via its ISO?"

You have misinterpreted my question to you. It was never about Ventoy, its about YOUR objective.

I accept any responsibility of your misinterpretation, as, If I had underlined the question in that post, you might have understood my request to help you.

[ThruHammer]

Ball's in your court, galen.

[bigpup]

upon reboot and selecting fossa this system drops to grub>

I am not exactly sure what you are saying.
Could you explain a little more?

Fossapup does have a grub.cfg file it uses for the boot loader that comes with Fossapup.

Not seeing anything wrong in that posted boot menu entry.

Only have the USB stick, Fossapup is on, plugged into computer.
It has a bug about not finding files, if another USB drive, is also plugged into the computer.

[Clarity]

The OP is asking something similar here, as well.

His/her question(s) seem to want "something for nothing" kind of questioning...meaning 'maybe' he wants help to boot using a pathway WE do not use.

How can we help assist to understand how PUPs/DOGs/EASYs boot?

[galen]

The OP is asking something similar here, as well.

His/her question(s) seem to want "something for nothing" kind of questioning...meaning 'maybe' he wants help to boot using a pathway WE do not use.

How can we help assist to understand how PUPs/DOGs/EASYs boot?

I know how Puppy boots, I've been installing & using it for over a decade,
so don't be a dick

If someone does not want to wipe a flash drive there are other options, which I am exploring & sharing.

[Clarity]

I see. Thanks

[ThruHammer]

Two posts back.. there ya go.

You tell'm, galen Mac...

[Flash]

ThruHammer, are you trolling? Your posts in this thread seem intended to incite. If you have nothing to contribute to the solution of galen's problem, just sit quietly on the sidelines.

[bigpup]

I know how Puppy boots, I've been installing & using it for over a decade,

If someone does not want to wipe a flash drive there are other options, which I am exploring & sharing.

I still do not understand what is happening when you try to boot Fossapup64 9.5??????
You do what?
You see what?

My spy satellite, is not getting a clear image of your computer screen, when you boot!

[galen]

I am creating a fossa install onto a USB stick
MultibootUSB takes the iso
and creates a subdir on the stick
and creates proper grub cfg files

Boot up to USB stick
see MBUSB grub menu
from there select fossa
grub then hops to fossa's grub

Code: Select all

insmod part_acorn
insmod part_amiga
insmod part_apple
insmod part_bsd
insmod part_dfly
insmod part_dvh
insmod part_gpt
insmod part_msdos
insmod part_plan
insmod part_sun
insmod part_sunpc

loadfont /multibootusb/fossapup64-9.5/boot/grub/font.pf2
set gfxmode=800x600
set gfxpayload=keep

insmod efi_gop
insmod efi_uga

insmod all_video
insmod video_bochs
insmod video_cirrus
insmod gfxterm
insmod png
insmod jpeg
terminal_output gfxterm

insmod ext2
insmod f2fs
insmod ntfs
insmod exfat

insmod loopback
insmod iso9660
insmod udf

background_image /multibootusb/fossapup64-9.5/boot/splash.png
set timeout=10

# https://help.ubuntu.com/community/Grub2/Displays
color_normal=cyan/black
#menu_color_highlight=black/light-gray
menu_color_highlight=yellow/red
menu_color_normal=light-gray/black

menuentry "fossapup64 9.5" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - Copy SFS files to RAM" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=copy,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - Don't copy SFS files to RAM" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=nocopy,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - RAM only" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=ram,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - No X" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=nox,fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - No KMS (Kernel modesetting)" {
    linux /multibootusb/fossapup64-9.5/vmlinuz nomodeset pfix=fsck pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "fossapup64 9.5 - Ram Disk SHell" {
    linux /multibootusb/fossapup64-9.5/vmlinuz pfix=rdsh pmedia=usbflash psubok=TRUE psubdir=/multibootusb/fossapup64-9.5/
    initrd /multibootusb/fossapup64-9.5/initrd.gz
}

menuentry "Shutdown" {
	halt
}

menuentry "Reboot" {
	reboot
}

from there grub fails and sends me to the grub prompt
grub>

If I had chosen another install from MBUSB's menu like bionic
it works

there is something quirky about fossapup

[Grey]

This is NOT a Fossapup issue. The latest version of multibootusb was released in 2018(even their main website is dead). It does not have to know about Fossapup released in 2020. Use UNetbootin, which is updated regularly - it works .

[bigpup]

Is the only USB drive, plugged into the computer, the one with Fossapup on it?
If other USB drives are plugged in.
Have no other USB drives plugged in. Only the one with Fossapup on it.

Any help?

[bigpup]

Could look and see what actual Fossapup files are on the USB, in /multibootusb/fossapup64-9.5/
Only ones needed are:
all the .sfs files.
initrd.gz
vmlinuz

Anything else there.
Delete and see what happens when it now boots.

[Clarity]

It appears your problem is MB.

Is FossaPUP64 the ONLY distro on that USB? If so, boot something, and set up a Frugal as @BigPUP is trying to get you to. If that boots, then consider whether you want to continue your way or if @BigPUP's way, the Frugal boot method of PUPPY, allows you to get the PUP to boot as you want.

Also, There are Frugal options which will allow you to achieve multiple versions of PUPs on the same USB/HDD/SSD, if that is your aim.

Hope this is helpful insight.

[galen]

This is NOT a Fossapup issue. The latest version of multibootusb was released in 2018(even their main website is dead). It does not have to know about Fossapup released in 2020. Use UNetbootin, which is updated regularly - it works .

thanks,
I know about unetbootin I've used it for years

MBUSB is not dead, only the site has expired

[galen]

update:

I've tried SARDU multiboot system [note you have to register the program for it to work]
It is very similar to MBUSB in how it creates grub.cfg files and chain loads

thought I try removing
syslinux.cfg from the fossa install
since it is the cfg that points to a non existent grub.exe
but that did not work, it did not fall back to grub2 chain

So there is something different from bionic & fossa in how it communicated to the boot loader,
bionic will use grub & fossa with force trying to use grub.exe
Though it might be the installer detecting the destination was FAT32 and selecting to use grub.exe
but it did the same if the destination was ext4.
fossa seems like it is telling boot loader to configure for grub.exe grub4dos not grub

good to know what does not work

[Grey]

MBUSB is not dead, only the site has expired

That's exactly what I said - the site, not the program, is dead. But even if you look at the project's GitHub page, the latest version was released on April 4, 2018, that is, exactly three years have passed.
Take a look at the changes: "add support for AntiX 17.1", "added Parabola Linux" - the program was constantly being modified for specific distro versions.