QuickPup64 25.01 RC4

[Clarity]

QP64 initrd request results2.jpg (25.87 KiB) Viewed 2618 times

[mistfire]

@Clarity

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

[Clarity]

Yes. Just trying to help by sharing my findings.

I never knew of the "find_iso= ..." parm.

Question

• Did you interrupt a particular boot stanza and entered in on the Linux line?

This is a good fact to know for WoofCE Pups.

Let me know how your Linux line looks and I will test it via the GRUB2 launch option of Ventoy when selecting QP64.

[mistfire]

• Did you interrupt a particular boot stanza and entered in on the Linux line?

Upon showing the QuickPup64 boot menu I just use the edit mode. Just follow the instructions at the boot menu to edit boot parameter

[Clarity]

I've tried what I think you recommend in both Ventoy's normal (where QP64 uses Grub4DOS to boot) as well as the GRUB2 offering. The results reported for vRC15 remain the same.

Question
What does your linux line change look like?

find_iso parm.jpg (45.51 KiB) Viewed 2501 times

find_iso parm2.jpg (54 KiB) Viewed 2501 times

[mistfire]

I've tried what I think you recommend in both Ventoy's normal (where QP64 uses Grub4DOS to boot) as well as the GRUB2 offering. The results reported for vRC15 remain the same.

Question
What does your linux line change look like?find_iso parm.jpgfind_iso parm2.jpg

did you put the iso fileon a subfolder? If yes, you need specify it on find_iso parameter for example

find_iso=/BOOTISOS/puppy_quickpup64_24.01-rc15.iso

My ventoy setup was the iso file was the root folder of ventoy partition that's why it boot by just iso filename

[Clarity]

Thanks for the parm knowledge and the guidance for a QP64 Grub4DOS booting.

Not sure how to get the same result when the Ventoy GRUB2 option is selected as it does not go to a screen where a debugsave can be capture. It just freezes.

find_iso parm3.jpg (43.74 KiB) Viewed 2476 times

QP64 vRC15.jpg (157.98 KiB) Viewed 2465 times

QP64 Terminal.jpg (36.69 KiB) Viewed 2454 times

[Luluc]

I just tried quickpup64_24.01-rc15 and I feel compelled to comment.

==== THE GOOD ====

I must say I am truly impressed by this endeavor. The degree of polish is remarkable. This is probably the best distro I have ever tried. Almost everything looks great (tiny minor glitches), almost nothing is confusing (still multiple different installers), everything is very tasteful and well organized and behaves as expected. And I don't even like XFCE. Very interesting and useful selection of applications too. Talk about a Swiss Army knife. You thought about everything. Absolutely remarkable. I often wonder why Puppy (or Dog) Linux doesn't make headlines at least once a month, why not once a week.

==== THE BAD ====

In case the developer is interested, I ran into these problems:

I booted three times from the ISO image on a Virtualbox VM. On all three times, the system started, showed the desktop area, then it crashed. I ran xwin and the desktop came back again. On one of those three sessions, the graphical environment crashed once again later into the session, but xwin brought it back and none of my customizations was lost.

Then I installed on the Virtualbox fake hard disk. The bootup sequence fails because it can't find initrd.gz. I vaguely remembered reading something on the forum so I rebooted, pressed 'e' to edit the grub line and replaced all occurrences of initrd.gz with initrd.xz. It didn't work. The kernel panicked.

The kernel was right. I rebooted from the ISO image and inspected the content of the installation directory. Look, no initrd.gz or initrd.xz. The installation fails to provide one. Mind you, I installed to hard disk twice (deleting the installation directory and creating a new one with a different name), with two different frugal installers. The installation failed to install initrd.gz or initrd.xz on both times.

Then I had an idea. I copied initrd.xz over from the CD (iso image seen as a CD by Virtualbox), rebooted, pressed 'e' to edit the grub line and replaced all occurrences of initrd.gz with initrd.xz. It worked. The system booted and I saw the desktop once again.

Last problem: before shutting down, I was offered the chance to save my changes. I chose yes, not encrypted. But upon shutdown, I got this message. It won't go away. Pressing SAVE has no effect. Tab has no effect either so I can't press No. It just won't go away. That doesn't happen only on the "hard disk" frugal installation. It happened at the end of every session, including those booted from the CD iso image.

.
.
.
.

==== THE UGLY ====

Hey, no DogRadio?! Boooooo...
.

[Clarity]

Hello @mistfire
2 issues on OOTB missing admin apps AND the PPM: TLDR & BTOP missing and in PPM they do not install.

Also how do I add the multiple workspaces, I defined, to the taskbar for navigation there?

Thanks for things thus far. I will update the isofile boot-results table later tonight.

QP64 PC video.png (29.38 KiB) Viewed 2311 times

QP64 PC.png (147.19 KiB) Viewed 2314 times

[Clarity]

Can you see the error in naming the folder? (Compare that to the boot-menu stanza in the prior post's 1st pic.)

QP64 vRC15 shutdown error.jpg (29.36 KiB) Viewed 2281 times

[mistfire]

Can you see the error in naming the folder? (Compare that to the boot-menu stanza in the prior post's 1st pic.)QP64 vRC15 shutdown error.jpg

May I see the screenshot upon entering savefile name on creating save file?

[Clarity]

See the boot-stanza in this post (ie the psave parm)

[mistfire]

See the boot-stanza in this post (ie the psave parm)

You mean, you only used the default options on creating save file dialog?

[Clarity]

In all of my testing...

QP64 PC video.jpg (20.24 KiB) Viewed 2171 times

.
AS noted often before:

• In launching from Ventoy, WoofCE ISO files requires this parm entry.

• Not needed when ISOs are launched from SG2D as the SAVESPEC file guides the ISO session management.

[Anacleto]

Hello mistfire.

All the distributions you made so far have worked well for me and I really liked them.

But this one isn't working so well for me, the audio fails and I can't hear it and neither does the file browser.

When I configure it for the Spanish keyboard it doesn't support it and it goes back to English again.

Well in the meantime I'll continue with your old distributions.

Thanks for everything and best regards.

[Clarity]

Noticed that RC15 get my nVidia adapter OOTB

Nvidia in RC15-2.png (63.86 KiB) Viewed 2002 times

[mistfire]

QuickPup64 24.01 RC16 released

Changes:
* Now works on ventoy grub mode
* Linux kernel 6.12.1-lxpup64
* Bugfixes on the puppy remaster script
* Bugfixes on shutdownconfig dealing with PSAVE boot parameter
* Bugfixes on PPM update package database
* Bugfixes on pkg2
* Bugfixes on samba and samba usershares
* Sakura terminal replaced rxvt
* Added gnome resources (advanced system monitor)
* More recent builtin package updates
* Wayland ready (highly experimental).

To enable wayland do the following.
1. Install and configure a wayland compositor.
2. Define the wayland compositor on Puppy Graphical Session Settings (Goto XFCE Settings Manager)
3. To test it click LOGOUT, select EXIT TO PROMPT, and run this command

Code: Select all

startwayland

4. To make it default upon boot, open /etc/desktop-session file, set DESKTOP_SESSION=wayland, click SAVE, and Reboot computer

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/ET ... A?e=b1Imh1
MD5 Checksum: 4a6b35bded8e427f6c58982e645d5fd9

[Luluc]

QuickPup64 24.01 RC16 released

Very first boot on Virtualbox. XFCE comes up in small resolution. It crashes. I run xwin and it comes back up. Exactly like in the previous version.

Frugal install. Can't boot. No initrd.gz again.

[mistfire]

Very first boot on Virtualbox. XFCE comes up in small resolution. It crashes. I run xwin and it comes back up. Exactly like in the previous version.

What is your virtualbox configuration?

Frugal install. Can't boot. No initrd.gz again.

What installer did you use on frugal install? QuickPup64 uses initrd.xz not initrd.gz, you need to edit your boot config file and change the initrd filename

[Luluc]

What is your virtualbox configuration?

Do you mean display? VboxVGA, 128MB of RAM. No 3D or 2D acceleration.

What installer did you use on frugal install?

Flexible frugal.
https://0x0.st/X7Nt.mp4

QuickPup64 uses initrd.xz not initrd.gz, you need to edit your boot config file and change the initrd filename

Yes, I can do that. But a lot of people can't. It's confusing. it's not normal. The installer is broken.

[Luluc]

There is no internet. The connection keeps going down over and over and over, endlessly throughout the entire session.

That also happened on RC15.

All other puppies and dogs I have tested had no such problem.

[Clarity]

WOW! This RC16 is a major step forward!

For me, I have 2 versions in 1 package. The old X11 with fixes: And the new, with fixes, Wayland. This is great looking back from the beginning of the year to now. I look forward to testing both desktops.

THANKS as you move us into 2025 reality among Linux distros!

Amazing work from the description of additions!

[Clarity]

On initial X11 pristine, via Ventoy launch, boots to desktop. Ethernet Network is operational without issue. "findsmb' shows other shares on the network. tested for admin apps and utility to manipulate desktop pics for presentation here.

These are missing OOTB, tldr-btop-mtpaint along with a picture to show boot-menu used.
Further tldr and btop will not install via PM.

RC16 pristine X11 desktop1.jpg (106.6 KiB) Viewed 1819 times

RC16 pristine X11 desktop2.png (67.64 KiB) Viewed 1818 times

RC16 pristine X11 desktop3.png (89.97 KiB) Viewed 1818 times

[mistfire]

QuickPup64 24.01 RC 17 released

Changes:
* Bugfix on xorg auto configuration
* Some core script bugfixes
* FrugalPup is now the official puppy installer for QuickPup64

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/EZ ... g?e=XnnR0g
MD5 Checksum: d21250633f74ec0b8bd06b0c5cdd1529

[mistfire]

tldr and btop will not install via PM.

It seems ponce repo database was not yet updated by its maintainer. Just chose other repos. Don't forget to update the package database first before using PPM since QuickPup64 was based from slackware current which is a rolling release. Its packages changes frequently

[Clarity]

Hello @mistfire
Booted this WoofCE version via SG2D launch taking the default boot-menu selection without change. This was done on the same PC that my earlier Hardinfo2 screen reported.
On Desktop

• Clicked "toast" message allowing system to update. 4 files found to update ... selected all to update.

  

  Boot Menu bootparms.jpg (15.85 KiB) Viewed 1686 times

• Opened PPM and enabled "salix extras" and updated. Search shows older BTOP v1.3 and the installation error-prone v1.13. Chose v1.3 to install.
  .

• No 'tldr' or 'tealdeer' available at this stage.

  

  1st-run update.jpg (22.58 KiB) Viewed 1692 times

• Added the [puppyshare] for sharing info to the LAN. You 'may' want to add your Public folder to the OOTB smb.conf as follows.

  Code: Select all

  [puppyshare]
  	path = /root/Public
  	writable = yes
  

  Open the SSM and started SAMBA for network sharing. "findsmb command" shows this PC is sharing. "smbclient" shows details of localhost sharing.
  .

• Via desktop menu>applications added workspaces
  .

• Added @ETP's GetChromeBrowser vMK15 PET and Menu>Internet opened Chrome browser
  .

• Clicked taskbar speaker as no sound was playing from youtube. Choose the HDMI2 selection for audio. Good! ... sound via TV speaker.
  .

• Click PrtScrn to capture a picture while a youtube was playing the background. Enabled the capture to be saved AND ===>System LOCKED...no mouse...no control via keyboard...no Ctrl-Alt-bksp to console ... NOTHING!

Cold Start Required!

P.S. You may also have noticed from 1stRun screen that this version is NOT auto-loading nVidia driver as I had reported in earlier post.

[Clarity]

Subsequent boot via SG2D. Made the same changes and additions as described before. No such system failure after an hour of use on a pristine session (no save-reboot, thus far, after an hour of use)

I'l let it set until later this afternoon. See what happens when I return to awaken this PC.

Edit: 12 hours later: Came back and the QP64 system continues without a lockup of this pristine operations. I have not rebooted to save the session, yet.

Problem:
Cannot set the system time

1. Tried via setting to UTC in Quick Setup as shown above. No taskbar clock change.

2. Re-opening the Quick Setup shows the UTC box unchecked ??? Checking it again and click OK in quicksetup and still no change. Each time I re-open Quicksetup, the UTC box is unchecked???

3. Tried via 'time' utility and I get a failure when it tries to go to "time.google.com"

Problem2:

• My keyboard for arrow keys are remapped by some system occurrance??? They dont navigate when editing text and instead they open applications; such as my up-arror opens screen-capture and other 3 keys do other apps. Never saw this phenom before. Recheck via Quick setup and all looks normal.

  

  quick setup each reopening.jpg (21.74 KiB) Viewed 1623 times

[Clarity]

1. Saved session and rebooted via SG2D.

2. Took QP64's boot-menu's default selection (top one)

3. Booting found its prior Session automatically

4. Problem2, earlier, is not present now???

5. The following allows me to set the system time fixing the problem reported during pristine usage:

   

   app to successfully set system time.jpg (28.3 KiB) Viewed 1553 times

.
Observation

• I am not sure, but a pristine boot "may" not (I say may because I am not sure if this is accurate as I haven't tested) provide normal behaviors until AFTER a session+reboot has been saved.

• OR

• Menu-Applications>Setup>QuickSetup App may have been a contributor to the 2 problems reported.

Again, this observation is speculation!!! as this WoofCE distro does NOT pristine boot to opening the Quick Setup App as the other WoofCE distros do.

[Clarity]

Next bare-metal test is also successful. Here, the ISO file is launched from Ventoy taking the GRUB2 option to QP64's boot-Menu. Edit the top-most stanza adding psave=Persistence:/Session/

The distro boots to desktop using the QP64save in the Sessions folder on the disk labeled Persistence.

It is behaving exactly the same as booting and finding the session when ISO file is launched from SG2D.

All is well.

[mistfire]

QuickPup64 24.01 RC18 released

Changes:
* Added Wayland support (upstream experimental). It includes labwc wayland compositor. To enable Wayland session, boot QuickPup64 using this boot parameter:

Code: Select all

psession=wayland

It will starts like a normal XFCE desktop but in wayland session

NOTE: Wayland session will persist on next boot upon the creation of save file or existing savefile is loaded even the psession boot parameter is not defined. Not all apps on XFCE components works on Wayland for now. To revert back to X11 session use this boot parameter:

Code: Select all

psession=x11

* XFCE 4.20 (With initial wayland support)
* Linux kernel 6.12.4
* Fixed CUPS printing issues
* Breeze replaced Matcha as the default theme
* More core puppy bugfixes.

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/EV ... w?e=bKcrtZ
MD5 Checksum: c102172b2c6e3ac5cc47ec9e90e827d0