Discussion, talk and tips
https://forum.puppylinux.com/
QuickPup64 24.01 RC9 released
Changes:
* Linux kernel 6.9.5
* Fix VPN connections
* Easyeffects replaced pulseaudio-equalizer
Download: https://1drv.ms/u/s!As14nV96TZw0ggMuW_o ... i?e=24bIVE
MD5 Checksum: 092743891dd7f4806cf3c3b671abbdb8
Hi @one
one wrote: Tue Dec 05, 2023 10:55 amHi @Clarity ... Attached savespec, where 'Ventoy' is the label of the first partition (ext3). ...
In review of this post from you, I should have offered this.
There is nothing wrong with what you have, BUT, for me, as you may have notice in some/many of my past posting, I suggest to never place any forum's persistence on a USB. Too many issues to cover in a post, here and I do not want to derail the good work @mistfire offers us.
Just a note (in my case). Create a partition on a system drive if space is available and keep ALL of your forum's persistence for all the distros you boot in that system drive partition. To me, our sessions is the MOST important file-folder outside of the ISO files. And we benefit from the integrity and consistency of your system drive.
Just a note.
Booting Results Testings
Bare Metal (Using a Lenovo Mini M90n:)
Ventoy without boot parms additions - boots to desktop. As expected for current WoofCE PUPs, does not use the SAVESPEC file for directing persistence at shutdown..
Ventoy with PSAVE parm - boots to desktop. UNexpected does not use the PSAVE info for directing persistence at shutdown.
SG2D - booting errors out and drops to GRUB prompt no matter which menu stanza selected. The 'debug' file is attached, below.
Booting Results Testings
QEMU VMs
ISO file - boots to desktop. All expected behavior works including providing persistence at shutdown as prescribed in SAVESPEC file.
Ventoy USB launch of ISO file - does not get to desktop. Stops at QP64's console. "xorgwizard" is no help to get to the desktop. Multiple vga parms were tested.
SG2D USB launch of ISO file - boots to desktop. All expected behavior works including providing persistence at shutdown as prescribed in SAVESPEC file.
QEMU Stanzas
Via ISO file direct
Code: Select all
# qemu-system-x86_64 -name "QP64 vRC9 ISO file" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -cdrom quickpup64_24.01-rc-9.isoVia USB
Code: Select all
qemu-system-x86_64 -name "QP64 vRC9 ISO from Ventoy or SG2D USB" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime /dev/sdcCan not install any package with the package manager, it displays messages "package no available". refreshing database do not help. Is something wrong with mirrors? How can I fix this?
mikolaj_q wrote: Thu Jun 27, 2024 8:28 amCan not install any package with the package manager, it displays messages "package no available". refreshing database do not help. Is something wrong with mirrors? How can I fix this?
Check your internet connection first. I tested Quickpup64 on a VM with active connection, the PPM works fine
Network connection is OK. Packages updater works, but packages manager unfortunetaly do not like at screenshot.
Any idea how can i fix this?
mikolaj_q wrote: Thu Jun 27, 2024 12:58 pmNetwork connection is OK. Packages updater works, but packages manager unfortunetaly do not like at screenshot.
Any idea how can i fix this?
What repo did you select on PPM?
UPDATE: It turns out that slackel repo does not update the package database against upstream slackware-current. To fix this problem just edit /var/packages/DISTRO_COMPAT_REPOS file to prioritize the upstream slackware repo
Sorry for being a noob but could you be more specific which line should I move to the top of the list?
mikolaj_q wrote: Fri Jun 28, 2024 10:24 amSorry for being a noob but could you be more specific which line should I move to the top of the list?
If you are noob, the easiest way to was look that package in pkgs.org select the package under Slackware category. Copy the download URL. Paste on the browser the press enter key
Update: Slackel repo database was finally updated. Just update the package database and it will just works
Thanks
Using quickpup with chrome portable for a while now. It's great! Just wanted to say thanks.
.
The Table of Mistfire's distros ISO boot results, by distro-version, are posted here.
.
QuickPup64 24.10 RC 10 released
Changes:
* Glibc 2.40
* Linux kernel 6.10.2
* Improve initrd: Now supports SAVESPEC file and fixed PSAVE boot parameters
* Optimized boot process
* Added nvidia GSP firmware drivers for Nvidia RTX 30/40 series
Download: https://1drv.ms/u/c/349c4d7a5f9d78cd/Ec ... w?e=G9XUwe
MD5 Checksum: 3345d7dec48404b8465545568c44a47e
Hello @mistfire, can I have your compiled GLibc 2.40 please?
Salamat, po!
sonny wrote: Thu Aug 01, 2024 2:40 amHello @mistfire, can I have your compiled GLibc 2.40 please?
Salamat, po!
@mistfire
Kernel Panic.
BookwormPup64.
If you want a compiled glibc 2.40 you must go the debian sid repo
Whoa, @mistfire
Lemme see if I can 'pet' it.
No KP, but no compile...
No, I didn't. Where can I get those dev files?
I have a bad habit of 'causing troubles' by doing stuff organically.
Salamat again.
sonny wrote: Thu Aug 01, 2024 2:22 pmNo, I didn't. Where can I get those dev files?
I have a bad habit of 'causing troubles' by doing stuff organically.
Salamat again.
Just read this one on how to compile the pipewire. it must satisfy the source dependencies before you start compiling
mistfire wrote: Thu Aug 01, 2024 3:35 pmJust read this one on how to compile the pipewire. it must satisfy the source dependencies before you start compiling
No, I managed to compile pipewire & stuff
without issues BEFORE upgrading to GLibc 2.40.
I guess I'll stick to whatever GLibc that came
with vanilla BP64.
Salamat, po.
Hello @mistfire
Took a few moments to test the current vRC10 ISO file booting. The results (improvements) are shown in the table here.
Improvements noted: On SG2D booting, the SAVEFILE contents are used to guide saving session.
I note the following:
TLDR not included
BTOP not included
findsmb is not showing the other LAN SAMBA hosts
smbclient -U% -L localhost results in error.
(I am able to use smbclient to reach other LAN samba units without problems), but other units cannot get access to this PC's shared folder. AND, YES, the Samba Simple Management was used to define the shared resource and it was started (green)
QP64 did shutdown, saving the session as expected properly.
BUT on this pristine boot, the user is given the 'option' to copy the PUP's SFS. Clicking "NO" will copy the SFS anyhow during shutdown???
Otherwise a snappy experience in desktop use.
Update on Sessions Management
Even though a session is saved on the proper drive, it is NOT saved in the proper folder that is specified in the SAVESPEC. Thus upon reboot, the session that was saved is NOT found. Looks like there are some remaining issues. Too late to investigate further; I'll need to get back to session management with SAVESPEC as well as, separately, tests using boot-menu parm "PSAVE" later this weekend if possible.
Clarity wrote: Sat Aug 03, 2024 8:17 amUpdate on Sessions Management
Even though a session is saved on the proper drive, it is NOT saved in the proper folder that is specified in the SAVESPEC. Thus upon reboot, the session that was saved is NOT found. Looks like there are some remaining issues. Too late to investigate further; I'll need to get back to session management with SAVESPEC as well as, separately, tests using boot-menu parm "PSAVE" later this weekend if possible.
Can you please send the contents /initrd/tmp folder? thank you
Boot scenario - Pristine
Boot SG2D
Launch QP64 vRC10
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
Tailoring completed,
Captured requested folder of logs for @mistfire's review
Open Menu to click icon to Reboot
Shutdown wizard guides with steps
Final Screen before the Copy SFS screen is presented. It is incomplete, though.
Shows proper partition
But, does not show proper folder. The screen shows it will place the save in the partition's root
Manually changed the folder path adding the 'Session' directory to show /Sessions/qp64save...
The Copy SFS screen is presented and "NO" was selected
I saw a message during the shutdown that the SFS was copied???
1st Reboot scenario
Boot SG2D
Launch QP64 vRC10
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.
Reboot the system: Plan to use the PSAVE parm at boot time to force a search for the session
Captured another folder of logs for @mistfire's review
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
Boot SG2D
Launch QP64 vRC10
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