Puppy Linux Discussion Forum

Hello @mistfire
You ask 3 questions, in your 2nd prior post. I answer with explanation to help in understanding:

1. Upon reading the logs that you send. I wonder, which of these detected drives is the Ventoy? "sdf"

   • Ventoy provides method to take a USB and structure it to boot and list user's ISO files available for launching. I keep ALL forum distros in a folder I create on Ventoy's partition #1 named BOOTISOS. Ventoy will find any/all ISO files on the partiton and list them for user selection. User selects their choice and Ventoy launched the ISO as if you had installed a distro.

2. Also where did you install QuickPup64? "No need!"

   • Forum distros exist as bootable ISO and a session. This constitutes what is called a Frugal. Just that there is no need to go thru any extraction process to run a forum distro. Merely boot the ISO file; and if the path is provided for prior session(s), it will boot to desktop using any prior session. The path to session folder-file for WoofCE (as is the case of any forum distro) is crucial.

3. Is it booted directly from iso using Ventoy? "Yes",

   • as explained above, Ventoy launches any ISO/IMG file one provides on partition #1. As has been the case for all forum distros, the QP64 ISO files have all been launched
     via Ventoy & SG2D USBs for past 5 years

   • The cost of Ventoy to anyone is minimal; any size USB, Merely provide Ventoy any USB it will build it bootable for you.

     • I advise everyone add a folder for keeping all distro ISO files as I see this as good housekeeping. On its partition #1, mkdir BOOTISOS. Place all ISO files within. When the USB boots it shows all ISO/IMG files.

   Try any cheap any size USB to see the same.

Hope this is helpful understanding

@mistfire, do you still want your "ls ..." command results?

And, do you want it with/without the PSAVE= parm? Those produce different results, as reported when I bare-metal tested vRC15.

Are you seeing something different with your Ventoy USB boots? ... such that, maybe, you are thinking its platform (aka 'CPU') dependent?

The results are presented to show what is seen via booting the ISO file in various environments; namely in VMs and on bare-metal.

BTW: It is widely known that this is limited to WoofCE distros being launched from Ventoy. This is NOT a problem seen when launched from either SG2D nor ISObooter.

Clarity wrote: Wed Nov 27, 2024 1:20 am

@mistfire, do you still want your "ls ..." command results?

And, do you want it with/without the PSAVE= parm? Those produce different results, as reported when I bare-metal tested vRC15.

Are you seeing something different with your Ventoy USB boots? ... such that, maybe, you are thinking its platform (aka 'CPU') dependent?

The results are presented to show what is seen via booting the ISO file in various environments; namely in VMs and on bare-metal.

BTW: It is widely known that this is limited to WoofCE distros being launched from Ventoy. This is NOT a problem seen when launched from either SG2D nor ISObooter.

Actually both with/without PSAVE param as long will get into the root shell. Using pfix=initrd, will launch root shell from QuickPup64's initrd after the kernel was loaded and booted. It will not kick the actual init script. Using ls on /dev and /dev/mapper will see what the block devices listed after booting on ventoy

In case that you launched the QuickPup64's initrd shell
run these command and post the shell output here

ls /dev/ventoy*

ls /dev/mapper/ventoy*

Oh no device found.

I tried to simulate Ventoy by using its live cd and install it on a VM. It failed to found the puppy main sfs at first. But later I successfully booted QuickPup64 from ventoy (normal mode) by using find_iso=<quickpup64 iso filename> boot parameter. Which is suddenly I suddenly remembered that I implemented that feature before