QuickPup64 25.01 RC4

[Clarity]

Restarted the testing. This time, I booted the ISO file via Ventoy taking the Wayland option changing pfix=ram,fsck while adding the PSAVE parm as before. My intent is to boot to create a Wayland session completely separate from the prior X11 session tests for your 2025 version. Upon desktop, same steps as before starting with Update Manager updating packages.

After update, I tried to install btop and tldr via the package manager; but not available.

I opened QuickSetup to tailor use:

1. New, Keyboard layout is grayed-out

2. I get a Puppy Input Wizard notification message "This settings is of X11 session only" when completing QuickSetup

3. And the time setting problems persist

Screenshot_2025-02-24_12-46-16.jpg (52.94 KiB) Viewed 1860 times

[Clarity]

As reported earlier,

1. SFS files were copied onto my Persistence partition even though I chose the "NO" options at shutdown.

2. The actual 'save' was placed correctly within the Sessions folder

3. On this Wayland session, it has done the same thing, again.

Am I misunderstanding that screen's request OR Is this a bug?

[mistfire]

Restarted the testing. This time, I booted the ISO file via Ventoy taking the Wayland option changing pfix=ram,fsck while adding the PSAVE parm as before. My intent is to boot to create a Wayland session completely separate from the prior X11 session tests for your 2025 version. Upon desktop, same steps as before starting with Update Manager updating packages.

After update, I tried to install btop and tldr via the package manager; but not available.

I opened QuickSetup to tailor use:

1. New, Keyboard layout is grayed-out

2. I get a Puppy Input Wizard notification message "This settings is of X11 session only" when completing QuickSetup

3. And the time setting problems persist

Screenshot_2025-02-24_12-46-16.jpg

Keyboard layout on Wayland is actually depends on the wayland compositor. Just go to xfce desktop settings. and select keyboard settings. And it will redirected to labwc settings gui

[mistfire]

QuickPup64 25.01 RC3 released

Changes:
* Fixes on initrd, Improvements for odd numbered pupmodes (still disabled by default, required to enable)
* linux kernel 6.13.5-lxpup64
* Added brlaser and bcachefs-tools
* Disk Image Creator now supports BTRFS and bcachefs

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/EQ ... g?e=3zAnfF
MD5 Checksum: ead40d46ddd085318d79837ec4308c51

[Clarity]

Hello @mistfire

Testing launching vRC3 via Ventoy. These can be verified with your own USB that you've tested from before.

Few issues
Selecting GRUB2 option from Ventoy when launching the ISO, there are several error messages, too fast to capture, that flash quickly before the QP64 boot-menu is displayed. To test, at the QP64 boot-menu each case of booting with and without PSAVE is shown below.

1. Attempts with PSAVE parm

   • When 1st stanza is selected and the PSAVE= parm is added for Persistence, the boot will display the Puppy grub image, but will not progress the boot to a prompt or to a desktop. It just hangs at the image.

   • The same thing occurs when attempting to boot using the Wayland stanza with a PSAVE parm.

2. Attempts without the PSAVE parm - A different behavior

   • Allowing the boot-menu to timeout at the default stanza the boot starts. After a 60sec wait, the boot will progress and stop with the following information locked on-screen

     Code: Select all

     QuickPup64
     Linux 6.13.5-1xpup64 [x86_64 arch]
     puppypc22926 login: root (automatic login)
     
     Welcome to Puppy Linux!
     /usr/lib/puppy/bin/start-display-server: line 50: /usr/sbin/pm13: No such file or directory 
     [puppy::root]# ModemManager [10009]: <msg> ModemManager (version 1.22.0) starting in system bus...
     
     acpid: starting up with netlink and the input layer
     acpid: 1 rule loaded
     acpid: waiting for events: event logging is off
     crond[10167]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice
     
     haveged: haveged starting up
     haveged: haveged: ver: 1.9.19; arch: x86; vend: GenuineIntel; build: (gcc 14.2.0 ITV); collect: 128K
     
     haveged: haveged: cpu: (L4 VC); data: 32K (L2 L4 V); inst: 32K (L2 L4 V); idx: 24/40; sz: 32156/54021
     
     haveged: haveged: tot tests(BAB): A:1/1 B:1/1 continuous tests(B): last entropy estimate 7.99764
     
     haveged: haveged: fills: 0, generated: 0
     
     ModemManager [10009]: <msg> [base-manager] couldn't check support for device'/sys/devices/pci0000:00/00000:00:1c.5/0000:06:00.0': not supported by any plugin
     

     There is nothing more...no prompt...nothing to indicate some user actions is needed. Using Cntrl-Alt-Delete starts a Shutdown asking if I want to save???

   • Taking the Wayland stanza the same behavior occurs. This time at the last message I waited, then hit the Enter-key. I got a prompt. At the prompt, I entered "xwin" and the desktop started. But as is the case for all WoofCEs launched from ventoy, session saving is impossible without a beginning PSAVE parm.

[Clarity]

Booting from SG2D not changing any boot stanza allowing the boot-menu to default on its topmost stanza. It boots to its desktop.

[Clarity]

ALL tests launches from both Ventoy AND from SG2D are on bare-metal. Prior post report is from Ventoy while this post is SG2D results.

SG2D - Upon session end, cannot save. SAVESPEC is not honored by distro.

Shutdown report.jpg (44.2 KiB) Viewed 1454 times

Code: Select all

[    0.000000] Linux version 6.13.5-lxpup64 (root@puppypc28762) (gcc-14.2.0 (GCC) 14.2.0, GNU ld version 2.42-slack151) #1 SMP PREEMPT_DYNAMIC Thu Feb 27 15:25:09 GMT 2025
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz pfix=fsck pmedia=cd find_iso=/BOOTISOS/quickpup64_25.01-rc3.iso rdinit=/vtoy/vtoy
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] BIOS-provided physical RAM map:

[Clarity]

Summary: ISO file booting on bare-metal does not follow save-session expectations once on the desktop.

[mistfire]

QuickPup64 25.01 RC4 released

Changes:
* package management is now fully aligned to the slackware current upstream repo. Slackel repo will now handle the package dependency instead
* Improved PPM and PKG2. Now supports slackware deps files (located /var/packages/repo/slack-deps) and automatically updates the package repo when needed.
* linux kernel 6.13.7-lxpup64
* updated linux firmware drivers
* reco replaced audio-recorder as sound recording app
* more bugfixes

Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/EX ... A?e=wG4n7H
MD5 Checksum: b44eadea85b11f80a9d9e511b505f97e

[Clarity]

Launched to desktop on bare-metal via Ventoy and also SG2D without issues. This was done taking the default QP64 boot-menu stanza. Using that stanza, SG2D using SAVESPEC locates all prior QP64 sessions offering the option to select or 'none' to boot. I chose none for a pristine boot of this version RC4.

Problems, thus far

• My arrow keys and other keys between the keyboard letters and numbers-keys are NOT behaving as they normally would. Not sure how to resolve. I did review the
  desktop menu>Desktop>Keyboard Shortcuts, but nothing stands out on how to activate normal operations of those keys. The keyboard is set in FirstRun as US English.

• USing Firstrun, I choose the UTC clock option, but it is NOT respected. When Firstrun is reopened, the UTC option is unchecked.

• My PrtScrn key does not work. This may be related to the other keyboard behavior reported.

• On pristine use, opening the Drawing graphic utility offers a guide, but when checked, no manual/user-guide is presented.

Next will be tests booting QP64 using its Wayland boot menu stanza. Wayland was not present in this report's findings.

[Clarity]

Wayland Tests

On a pristine boot on bare-metal, I have a problem getting to desktop. The boot hangs before I gain control of desktop and startx as shown below:

Code: Select all

QuickPup64
Linux 6.13.7-1xpup64 [x86_64 arch]
puppурс17895 login: root (automatic login)
Welcome to Puppy Linux!
/usr/lib/puppy/bin/start-display-server: line 50: /usr/sbin/pm13: No such file or directory
[puppy: :root]# ModemManager [10581]: <msg> ModemManager (version 1.22.0) starting in system bus...

acpid: starting up with netlink and the input layer
acpid: 1 rule loaded
acpid: waiting for events: event logging is off
crond[10728]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice

haveged: haveged starting up
haveged: haveged: ver: 1.9.19; arch: x86; vend: GenuineIntel; build: (gcc 14.2.0 ITU); collect: 128K
haveged: haveged: cpu: (L4 UC); data: 32K (L2 L4 V); inst: 32K (L2 L4 V); idx: 24/40; sz: 32156/54021
haveged: haveged: tot tests (BAB): A:1/1 B:1/1 continuous tests(B): last entropy estimate 7.99838
haveged: haveged: fills: 0, generated: 0
ModemManager [10581]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:06.00.0': not supported by any plugin
^C
[puppy:root]# echo "Interrupted after waiting 5 minutes for ModemManger result/completion that never happened"
Interrupted after waiting 5 minutes for ModemManger result/completion that never happened
[puppy:root]# startx  # required to get a desktop

.
Question
What would you have done, at this point, for this attempted boot of the Wayland boot-menu option?

Screenshot.jpg (68.23 KiB) Viewed 477 times

[Clarity]

Wayland Tests

@mistfire as you have noticed from the above issue I report, I rebooted in SG2D taking the Wayland option. It is KNOWN that if a SAVESPEC is present the booting WoofCE will respect its contents for session inclusion as well as to know where to find-save the session.

Selecting the Wayland boot option the boot fails allowing a debugsave to create useful information to the developer. Here it is ...

pupdebug-0324250135.tar.gz

DebugSave from boot-time failure when Wayland selected

(91.85 KiB) Downloaded 2 times

[Clarity]

Advise on these vRC4 issues, above post and below in this post.

Screenshot_admin apps needed.jpg (91.06 KiB) Viewed 461 times

Screenshot_admin app needed2.jpg (35.25 KiB) Viewed 461 times

[mistfire]

Wayland Tests

@mistfire as you have noticed from the above issue I report, I rebooted in SG2D taking the Wayland option. It is KNOWN that if a SAVESPEC is present the booting WoofCE will respect its contents for session inclusion as well as to know where to find-save the session.

Selecting the Wayland boot option the boot fails allowing a debugsave to create useful information to the developer. Here it is ...pupdebug-0324250135.tar.gz

I noticed to the debug file that there is /dev/sr0 detected by probepart. Did you try to use find_iso boot parameter to locate the iso file?

[Clarity]

Did you see the kernel in the "Command line" of the log files; BOOT_IMAGE=/vmlinux pfix=fsck ... find_iso=/BOOTISOS/quickpup64_25.01-rc4.iso ...

Or is it missing in the logs I sent?

Can I send you a 2GB USB "IMG" file that you can use for your tests where you can mimic the problems which surface in booting. Its merely Ventoy USB with an SG2D ISO and a QP64 ISO. Its a replica of what I use it to test booting everything for last 6 years. I launch directly from Ventoy or I boot SG2D and launch from there ... same USB for all ISO file boot testing and reporting. This would give you ability to see what I see in booting tests, from time to time. If this would be helpful, PM me.

[mistfire]

Can I send you a 2GB USB "IMG" file that you can use for your tests where you can mimic the problems which surface in booting. Its merely Ventoy USB with an SG2D ISO and a QP64 ISO. Its a replica of what I use it to test booting everything for last 6 years. I launch directly from Ventoy or I boot SG2D and launch from there ... same USB for all ISO file boot testing and reporting. This would give you ability to see what I see in booting tests, from time to time. If this would be helpful, PM me.

sure why not?

[Clarity]

Check your PM.

@mistfire, completed.

[Clarity]

On booting the vRC4 ISO file via SG2D, it finds and lists the Session files on the attached partitions. BUT ...

1. The PC has 2 SCSI drives. One is exclusively Windows and Linux Swap, while the other is used for Linux.

2. Recently, the 80GB SCSI approaches full. This drive contains the Persistence partition.

3. I renamed this partition Persist from its original Persistence label.

4. I installed a SATA HDD drive attached to the motherboard, created a partition and named it "Persistence" adding a

5. Sessions folder to become a mirror of the SCSI's "Persist".

6. I copied ALL of the sessions and its SAVESPEC file from the Persist partition to the new Persistence partition.

7. No other changes are done to the PC

8. Each of the partitions are formatted EXT4

9. Upon completion of the Persistence updates, I booted the PC.

What happens next...
Booting SG2D, I launched QP64 vRC4 allowing the 'default' stanza in its boot-menu. To my surprise the boot-process pause to ask me which of the session files for prior QP64 uses I preferred...or None. (there are 6 priors from 2024 on this PC)
"Surprise?" you may ask: YES because it is listing prior sessions for QP64 from BOTH the old Persist partition AND the new Persistence partition.

I believe (aka KNOW from prior WoofCE distros over the years) that the system, at boot time, it to use the directions contained within SAVESPEC when present, so I enclosed it here for your review:

Code: Select all

# Partition where Sessions to go
SS_ID='Persistence'
# Folder where Sessions to go
SS_DIR='/Sessions'
# Media where Sessions to go
SS_MEDIA='atahd'

I am reluctant to call this a bug because, I am unsure if there is any documentation that exist indicating that the system has no ability to determine the difference between disks labeled Persist versus Persistence?
AND, I am unsure if there is boot system intelligence to have multiple 'session' locations to be used or specified?

I know @gyrog is the architect and I know you and he are on WoofCE Github so I am asking either to comment by correcting my understanding of SAVESPEC operations as it pertains to this phenomenon.

Thoughts?