QuickPup64 25.01 RC1

[mistfire]

Boot scenario - Pristine

1. Boot SG2D

2. Launch QP64 vRC10

3. QP64 assumes control

   • Allow distro to boot without touching anything when QP64 displays its boot menu. Thus the default (topmost QP64 menu stanza) is used by QP64

   • On QP64 desktop, minor tailoring of desktop

   • Open Menu>Setup>Firstrun to tailor timezone and PC's name

4. Tailoring completed,

5. Captured requested folder of logs for @mistfire's review

6. Open Menu to click icon to Reboot

   1. Shutdown wizard guides with steps

   2. Final Screen before the Copy SFS screen is presented. It is incomplete, though.

   3. Shows proper partition

   4. But, does not show proper folder. The screen shows it will place the save in the partition's root

   5. Manually changed the folder path adding the 'Session' directory to show /Sessions/qp64save...

   6. The Copy SFS screen is presented and "NO" was selected

7. I saw a message during the shutdown that the SFS was copied???

1st Reboot scenario

1. Boot SG2D

2. Launch QP64 vRC10

3. QP64 assumes control

   • Allow distro to boot without touching anything when QP64 displays its boot menu. Thus the default (topmost QP64 menu stanza) is used by QP64

   • Open Menu>Setup>Firstrun to review if changes from prior boot is preserved

   • This screen does NOT contain items tailored during pristine. Screen is as if it was never touched. It is obvious that the SAVESPEC is not used to find session.

4. Reboot the system: Plan to use the PSAVE parm at boot time to force a search for the session

5. Captured another folder of logs for @mistfire's review

6. I searched the ISO's folder as well as the Sessions folder looking for the copied SFS. But it is not present

Reboot 2nd time: - Edit QP64 Menu's 1st stanza

1. Boot SG2D

2. Launch QP64 vRC10

3. QP64 assumes control

   • Change the QP64 default stanza to add "PSAVE=Persistence:/Sessions/"

   • QP64, now, during boot finds the Sessions folder and list the prior 2 test sessions, pausing waiting for my selection number.

   • Selected the most recent session. The boot proceeds with messages that indicate the session selected in being loaded.

   • Upon desktop, Open Menu>Setup>Firstrun

   • This screen does NOT contain items tailored during pristine. Screen is as if it was never touched. It appears that the PSAVE processing is not functioning properly OR the session file saved does not contained the changes made before 1st shutdown.

Stopped all testing to report problems

Regarding on first scenario, where did you put the SAVESPEC file?

[Clarity]

By design (the author @gyrog ) it is to found in the same location as the ISO files (the boot location).

In some cases, as I remember from the past, some past ISOs, IIRC, will automatically create one if none is present.

Hope this is helpful. (@gyrog has a forum post detailing its operation.)

P.S. If need, I can post to you a small IMG file showing a sample where you can see an actual USB sample that will boot all 3 versions that I show in the "Test ..." of your distros for your personal review. It follows all the same instructions I have provided users, for years, for a safe experience in booting WoofCE ISO files. The sample has a SAVESPEC in the same location as the ISO files.

[mistfire]

QuickPup64 24.01 RC 11

Changes:
* Linux kernel 6.10.5-lxpup64
* Improved puppy boot and shutdown script
* Improved initrd
* Matcha-azul-light is the new default theme
* Puppy-431-dark is the new default wallpaper

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/Ed ... Q?e=oNyjbM
MD5 Checksum: 2c3651d038c594aea9c27723e7fdca56

[mistfire]

QuickPup64 24.01 RC 12 released

Changes:
* linux kernel 6.10.8-lxpup64
* 32-bit glibc libraries now included by default
* Added vkd3d
* Added dxvk (to enable, run winedxvk command if the wine folder was successfully created)
* Odd-numbered pupmodes are no longer supported
* Some bugfixes on pkg2 and ppm

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/ER ... A?e=Pe53f2
MD5 Checksum: e2aba72da8297a0b7547a98372be8366

[Clarity]

I have not tried the recent vRC12, yet. BUT thougth I'd ask.

Does the kernel used, have the nvidia support built-in?

Curious before I run down a rabbit hole on my nvidia only PCs with HDMI to TV as I am looking for video and audio support thru the TV. The adapters are 2010+ vintage of 250 and 4000 models

[mistfire]

I have not tried the recent vRC12, yet. BUT thougth I'd ask.

Does the kernel used, have the nvidia support built-in?

Curious before I run down a rabbit hole on my nvidia only PCs with HDMI to TV as I am looking for video and audio support thru the TV. The adapters are 2010+ vintage of 250 and 4000 models

What's the model of your nvidia gpu?

[Clarity]

Video Adapter model

nvidia on 1 PC.jpg (98.84 KiB) Viewed 2751 times

[mistfire]

Oh its GTX series. Nouveau will work just fine otherwise install the nvidia official drivers

[bugnaw333]

@mistfire

Im testing it right now by using UNetbootin as USB writing tool. It will not run on EasyDD and Balena etcher.

[dancytron]

QuickPup64 24.01 RC 12 released

Changes:
* linux kernel 6.10.8-lxpup64
* 32-bit glibc libraries now included by default
* Added vkd3d
* Added dxvk (to enable, run winedxvk command if the wine folder was successfully created)
* Odd-numbered pupmodes are no longer supported
* Some bugfixes on pkg2 and ppm

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/ER ... A?e=Pe53f2
MD5 Checksum: e2aba72da8297a0b7547a98372be8366

Why did you get rid of pupmode 13?

[mistfire]

QuickPup64 24.01 RC 12 released

Changes:
* linux kernel 6.10.8-lxpup64
* 32-bit glibc libraries now included by default
* Added vkd3d
* Added dxvk (to enable, run winedxvk command if the wine folder was successfully created)
* Odd-numbered pupmodes are no longer supported
* Some bugfixes on pkg2 and ppm

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/ER ... A?e=Pe53f2
MD5 Checksum: e2aba72da8297a0b7547a98372be8366

Why did you get rid of pupmode 13?

1. Due to the size of QuickPup64. It exceeds 700MB because of increasing installed size of packages as time passes. 80% of packages bundled in QuickPup64 was always up to date on every releases. Even though I tried to trim down the packages the growth was inevitable.

2. Impracticality. There are apps where the files generated are quickly grew rapidly which easily filled the RAM. Some transferred files from ram to save file might became corrupted because it was still opened by process.

If you still want PUPMODE 13. Just do the following
1. Extract the initrd
2. Open the overrides.cfg file
3. Put a comment on DISABLE_ODD_PUPMODES and save it
4. Rebuild the initrd

[sinc]

https://forum.puppylinux.com/viewtopic.php?t=12576

See this post for a response about Puppys not working with Etcher and EasyDD

[mistfire]

https://forum.puppylinux.com/viewtopic.php?t=12576

See this post for a response about Puppys not working with Etcher and EasyDD

I made some fixes on the puppy remaster script. New build of QuickPup64 will be released pretty soon

[mistfire]

QuickPup64 24.01 RC 13 released

Changes:
* Linux kernel 6.11.0-lxpup64
* Built with isohybrid
* initrd improvements: increasing maximum number of sfs modules to load from 13 to 15
* Bugfixes on shutdown and boot process when sfs modules are loaded
* Bugfixes on package management
* isohybrid now works on puppy remaster script

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/ER ... Q?e=Gs3xHR
MD5 Checksum: 18f6ee0347ee2fe635f6275cee2e2fd6

[Clarity]

This QP64 vRC13 ISO file, launched from SG2D, booted to desktop. The following 2 screen exemplifies a few items of concern.

1. Notice commands as well as the fact that the distro ignored the SWAP partition at boot.

2. Further in the 2nd screen, modesetting (NOT 'nouveau') is setup for video/audio driver

3. And, in the 3rd screen, Checking the box to set the system to use the system's clock is NOT respected.Not only is the time not updated when complete in GUI's use, BUT reopening the Firstrun GUI does not have the checkbox checked.

Admin commands as well as 'free' command showing SWAP ignored on boot

Screenshot_2024-09-19_07-20-41.png (143.86 KiB) Viewed 2414 times

Modesetting video autoselected during boot

Screenshot_2024-09-19_07-36-07.png (64.92 KiB) Viewed 2414 times

The Hardware Clock to UTC, when checked, does not set the time. Reopening shows this!

Screenshot_2024-09-19_07-50-47.png (30.24 KiB) Viewed 2409 times

[Clarity]

Launching vRC13 from Ventoy will boot to desktop, IFF no boot parm is changed when the PUP's boot menu is presented. BUT ...
if psave=Persistence:/Sessions/ is added to the linux line, the PUP will NOT boot; freezing immediately after F10 to proceed to boot.

'Current Status

1. SG2D launch - the RC13 boots to desktop with no need to change things because the SAVESPEC file contains session-management instructions

2. Ventoy launch - boots to desktop IF and only IF (IFF) no boot stanza is changed when the RC13 boot menu's options are shown

QEMU results will be reported later and your distro's table will be updated with all RC13 results.

[Clarity]

Used Applications>Setup>Puppy Package Manager to update its database and install needed apps
Installation failures for

• QEMU v8

• MtPaint v3.4

  Code: Select all

  [puppy->Desktop]# mtpaint
  mtpaint: error while loading shared libraries: libopenjpeg.so.5: cannot open shared object file: No such file or directory
  [puppy->Desktop]#

qp64-vRC13 attempt to install QEMU.jpg (130.17 KiB) Viewed 2281 times

qp64-vRC13 attempt to install QEMU2.jpg (105.31 KiB) Viewed 2281 times

[Clarity]

Would like to see few admin tools from the WoofCE plate added to the OOTB version.

• TLDR

• FastFetch/NeoFetch

• BTOP

• QEMU-Ready from the forum

• QPWgraph

[mistfire]

Used Applications>Setup>Puppy Package Manager to update its database and install needed apps
Installation failures for

• QEMU v8

• MtPaint v3.4

  Code: Select all

  [puppy->Desktop]# mtpaint
  mtpaint: error while loading shared libraries: libopenjpeg.so.5: cannot open shared object file: No such file or directory
  [puppy->Desktop]#

qp64-vRC13 attempt to install QEMU.jpgqp64-vRC13 attempt to install QEMU2.jpg

QuickPup64 uses Slackel as main source of package database repo because they include package dependencies. When slackware update its repo, the slackel may took few hours or even a day to update the package. As of this post, slackel was recently updated. So try to update it now

[mistfire]

QuickPup64 24.01 RC 14 released

Changes:
* linux kernel 6.11.5-lxpup64
* added pdfslicer
* xfce4-clipman replaced clipit
* bugfixes on sfs_load and pkg
* more bugfixes

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/Ee ... A?e=5bUhfV
MD5 Checksum: 67d924fa851ed585608965264b859fff

[Clarity]

Preliminary

In a KVM: Launched Ventoy as well as SG2D USB to allow QP64 vRC14 to boot to desktop via its ISO file.

The following KVM stanza creates the vPC

Code: Select all

qemu-system-x86_64 -name "MistFire's ISO file from Ventoy USB" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime /dev/sdh

Result the same in all tests thus far:

QP64 vRC14.jpg (66.79 KiB) Viewed 1844 times

Bare Metal test and report, later.

[Clarity]

Status

Bare-bones via Ventoy USB

Screenshot_2024-10-28_FirstRun.jpg (44.88 KiB) Viewed 1839 times

Screenshot_2024-10-28_neofetch.jpg (42.49 KiB) Viewed 1839 times

Screenshot_2024-10-28_Desktop.jpg (132.69 KiB) Viewed 1839 times

.
All HDMI carries audio to the monitor device.

[Clarity]

Additional notes

In an earlier post today,I posted about qpwgraph admin tool. Disregard that post as I see you have Helvum instead.

In EVERY ISO file boot case, the default boot menu stanza is allowed to timeout to boot the distro.

SG2D boots without issue, finds prior save-sessions on the drive labeled "Persistence" in the Sessions folder (I DO recognize that the SAVESPEC file in the BOOTISOS USB folder guides the discovery). This is expected behavior of WoofCE PUPs. ALSO, there are NO operattional issues including session are saved as expected appropriately on Persistence partition.

Ventoy is a different story as there are 2 scenarios:

1. ISO boot allowing the default boot menu to timeout to proceed booting, the distro boots to desktop.. Upon desktop it operates as would be expected with all applications and subsystems operating without issue. BUT at shutdown it does not select the Persistence drive. (This is a known issue for WoofCE PUPs...nothing new here.) .... BUT ...

2. If at ISO boot I edit the default boot menu giving it a PSAVE parm (namely psave=Persistence:/Sessions) the distro locks in its boot attempt requiring ctrl-alt-del to abort. Thus the existence of the psave option freezes the booting.

FYI

[mistfire]

QuickPup64 24.01 RC 15 released

Changes:
* linux kernel 6.11.7-lxpup64
* bugfix on initrd
* gexec3 replaced gmrun
* Some microsoft windows hotkeys mapped to equivalent linux counterpart
- Win Key + R: Opens gexec for running command
- Win Key + E: Opens thunar
- Win Key + V: Opens clipboard history
- Win Key + S or Win Key + Q - Opens gnome search tool
- Win Key + Pause - Opens about xfce
- CTRL + Shift + ESC - Opens lxtask

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/EV ... g?e=5898pM
MD5 Checksum: 476672e3044907270db388d4f023a4fc

[Clarity]

Hello @mistfire

Booted RC15 in bare-metal in SG2D: All is well, finds prior sessions and list them for selection by merely taking the 1st boot Menu stanza. No boot issues to report as it goes to desktop without issues. Also on subsequent boot in RAM only pristine booting, it saves all changes to Sessions folder on the partition labeled Persistence as prescribe by the SAVESPEC file. ALL IS WELL! This is consistent with prior bare-metal QP64 boots when launched from SG2D

Booting in Ventoy: 3 behaviors. As you KNOW, when the ISO file is selected, Ventoy asks if you want to boot Normal OR via GRUB2

GRUB2 Ventoy choice: 2 occurrences

1. taking the default QP64 boot-menu selection (that is, NOT making any changes and merely hitting the Enter-key) the distro boots to desktop. All of the desktop subsystems and apps work without issues. But, as usual, it does NOT afford the ability to save the session as WoofCE does not have the technology to use the SAVESPEC when booted from Ventoy.

2. taking a QP64 boot-menu, editing it to add the PSAVE parm, the boot-process immediately goes to sleep never showing any messages on-screen, never awaking. This requires a Ctrl-Alt-Del to restart Ventoy.

Normal Ventoy choice

• Entering the PSAVE parm, it fails looking for its SFS. This does allow me to capture the pupdebug (attached below) for your review.

[mistfire]

Hello @mistfire

Booted RC15 in bare-metal in SG2D: All is well, finds prior sessions and list them for selection by merely taking the 1st boot Menu stanza. No boot issues to report as it goes to desktop without issues. Also on subsequent boot in RAM only pristine booting, it saves all changes to Sessions folder on the partition labeled Persistence as prescribe by the SAVESPEC file. ALL IS WELL! This is consistent with prior bare-metal QP64 boots when launched from SG2D

Booting in Ventoy: 3 behaviors. As you KNOW, when the ISO file is selected, Ventoy asks if you want to boot Normal OR via GRUB2

GRUB2 Ventoy choice: 2 occurrences

1. taking the default QP64 boot-menu selection (that is, NOT making any changes and merely hitting the Enter-key) the distro boots to desktop. All of the desktop subsystems and apps work without issues. But, as usual, it does NOT afford the ability to save the session as WoofCE does not have the technology to use the SAVESPEC when booted from Ventoy.

2. taking a QP64 boot-menu, editing it to add the PSAVE parm, the boot-process immediately goes to sleep never showing any messages on-screen, never awaking. This requires a Ctrl-Alt-Del to restart Ventoy.

Normal Ventoy choice

• Entering the PSAVE parm, it fails looking for its SFS. This does allow me to capture the pupdebug (attached below) for your review.

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

Code: Select all

/dev/sda1|vfat|102400
/dev/sda2|none|16384
/dev/sda3|ntfs|314572800
/dev/sda4|ntfs|1048576
/dev/sda5|swap|16777216
/dev/sda6|ntfs|329670656
/dev/sda7|ext4|314572800
/dev/sdb|none|0
/dev/sdc|none|0
/dev/sdd|none|0
/dev/sde|none|0
/dev/sdf1|ntfs|5824512
/dev/sdf2|ntfs|172974080
/dev/sdf3|ext4|61204480
/dev/sr0|iso9660|0

Also where did you install QuickPup64? Is it booted directly from iso using Ventoy?

[mistfire]

@Clarity

Could you please do the following if you are booting QuickPup64 iso from ventoy?

1. Boot Quickpup64 using pfix=initrd boot paramter. This will run the root shell
2. Type this code then press enter.

Code: Select all

ls /dev/ventoy*

Then took a screenshot and post it here

3. Type this code again then press enter.

Code: Select all

ls /dev/mapper/ventoy*

and took a screenshot and post it here

[Clarity]

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

[Clarity]

@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.

[mistfire]

@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

Code: Select all

ls /dev/ventoy*

Code: Select all

ls /dev/mapper/ventoy*