Puppy Linux Discussion Forum

esos wrote: ↑Sat Apr 20, 2024 3:40 am

@Mistfire
pmedia bootstanza problem:
Pmedia=ataflash, booting stop at "create ramdisk(1262M)...." pls see screenshot.
Pmedia=atahd, I can see only cursor(blank desktop).

What is your computer specs?
Did you try to boot without pmedia parameter?

Thanks for your reply.
Computer Profile:
Machine Hewlett-Packard HP Pavilion dm4 Notebook PC (version: 058B110000242B10000020100)
Mainboard Hewlett-Packard 146A (version: 58.1F)
• BIOS Hewlett-Packard F.11 | Date: 07/08/2010 | Type: Legacy
• CPU Intel(R) Core(TM) i5 CPU M 450 @ 2.40GHz (2 cores)
• RAM Total: 3706 MB |
Graphics Resolution: 1440x900 pixels | Display Server: X.Org 1.20.14
• device-0 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

"boot without pmedia parameter", Yes System boots without problem, but How I can activate pupmode13?

@esos to forcefully activate pupmode 13 try to use pfix=rwcache boot parameter

pfix=rwcache has the same error like pmedia=ataflash

esos wrote: ↑Mon Apr 22, 2024 10:53 pm

pfix=rwcache has the same error like pmedia=ataflash

Well that's weird. Did you try to the kernel and zdrv file as long as in 6.x series?

Posted that problem a while ago:
viewtopic.php?t=3171&start=420

"Did you try to the kernel and zdrv file as long as in 6.x series?" No.

QuickPup64 24.01 RC5 released

Changes:
* Improvements on initrd
* Improved boot and shutdown process
* Linux kernel 6.8.9-lxpup64
* Added gworldclock, gadmin-samba, gadmin-proftpd (GTK+3 compiled)
* srain replaced hexchat
* hardinfo2 replaced hardinfo
* drawing replaced gnu paint
* Removed pidgin, gtklp, gksu, and ircp-tray
* proftpd replaced pure-ftpd
* gmeasures, isomaster, paman, gtorrentview, are replaced with GTK+3 version
* More bugfixes

Download: https://1drv.ms/u/s!As14nV96TZw0gX90Lwh ... Z?e=M6XE0M
MD5 Checksum: 8cc12d95f099c319f38e7597848a3034

Next 3 screens show test result when booting in a VM
1st - direct via ISO file
2nd - launched via SG2D
3rd - launched via Ventoy

VM stanza - ISO file direct. Success to desktop

qemu-system-x86_64  -name "QuickPup64 v2401RC5 via Ventoy USB in QEMU" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -cdrom quickpup64_24.01-rc-5.iso

VM stanza - Boot SG2D, launch ISO file. Success to desktop
qemu-system-x86_64 -name "QuickPup64 v2401RC5 via Ventoy USB in QEMU" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -hda /dev/sdb

VM stanza - Boot Ventoy, launch ISO file. Unsuccessful
qemu-system-x86_64 -name "QuickPup64 v2401RC5 via Ventoy USB in QEMU" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -hda /dev/sdb

BUG: On the Fatal Error screen, above, if a user chooses option "2", option 2 does the same thing as options "0".

Thus, a user who does NOT want a report that option 0 provides, cannot abandon as option 2 is suppose to provide.

Results ... Moved to RC6's announcement area of this thread, below

QuickPup64 24.01 RC6 released

Changes:
* Linux kernel 6.9-lxpup64
* Improved initrd. Error diagnotics now works if QuickPup64 failed to boot
* Added and fixed WSDD (Web Services Dynamic Discovery) network discovery. It now shows devices on the network section of thunar if the device supports WSDD protocol
* Improved start/stop of services
* Removed fltk
* Remmina VNC plugin and gnome-remote-desktop server replaced tigervnc and x11vnc server

Download: https://1drv.ms/u/s!As14nV96TZw0ggBxAV2 ... c?e=AIOwDM
MD5 Checksum: c10a31068e27982d2b658dc722a17910

Results

Legend for 'N' (No) in table

• (1) - Drops out to GRUB prompt

• (2) - Stops at Console w/o Desktop

• (3) - TRAP/Abend during boot

• (4) - IMG Not Supported by Launcher

• (5) - Requires session-save parm, manually added, to GRUB2 Menu stanza for boot

• (6) - Not tested

• (7) - SAVESPEC will NOT be honored; if 'PSAVE' boot parm specified, boot will drop to GRUB prompt

@mistfire the table shows a "Y(7)" which is easy to replicate on your end.

I think it is easily understood. If not, QP vRC6 ISO boots when launched from Ventoy, but one cannot direct where to save the session via change to boot menu. Further if a SAVESPEC is present it will not be respected.

BUT, if you want me to capture a debugsave, I can.

Clarity wrote: ↑Tue May 14, 2024 10:44 am

@mistfire the table shows a "Y(7)" which is easy to replicate on your end.

I think it is easily understood. If not, QP vRC6 ISO boots when launched from Ventoy, but one cannot direct where to save the session via change to boot menu. Further if a SAVESPEC is present it will not be respected.

BUT, if you want me to capture a debugsave, I can.

Actually I tried to integrate SAVESPEC support however the init script of QuickPup64 was a hybrid of old Puppy and newer Puppy. I'm still struggling figuring out how to implement the SAVESPEC because that routine on the script was cryptic without explanation how SAVESPEC works. Also it weird that when adding boot parameters on ventoy it dropped to GRUB prompt.

P.S.: Can you give the log files located at /initrd/tmp if QuickPup64 failed to load the savefile?

Hello @mistfire. I hope this picture is complete and simple to follow.

Here's the VM that I use. AS you know it creates the same virtual PC from the stanza, no matter which Host PC your run it on. I include the stanzas to remove any hardware differences that exist in the various bare-metals. The QEMU VM (virtual PC) is standard no matter which host is used to run the stanza.

qemu-system-x86_64 -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "QP64 vRC6 via Ventoy USB in QEMU VM" -hda /dev/sdb

"sdb' is a Ventoy USB where its 1st partition has a folder name "BOOTISOS' containing QP64 ISOs and a SAVESPEC file within. SAVESPEC file must reside in the folder with the ISOs.

The SAVESPEC contents, as you know, tells WoofCE PUPs where to find/store the session (persistence). SAVESPEC ===>

SS_ID='Persistence' # partition's label
SS_DIR='/Sessions' # Folder to place sessions
SS_MEDIA='atahd' # type device the partition resides

The debugsave is attached to this post.

Any thing/info you need, to help, I will provide.

P.S. The 'drop to GRUB console' boot failure outcome is, exactly, the same on bare-metal. And GRUB (linux bash) commands can be entered on the terminal.

@Clarity

I found something weird on the last part of the bootlog

Probing partitions...
/dev/sda1|exfat|39028680
/dev/sda2|vfat|32768
/dev/sda3|ext4|39061504
/dev/sdb1|ntfs|122879872
/dev/sr0|none|0
Probing USB storage devices...
Starting pre-process stage...
Checking if the kernel version was qualified...
Minimum version: 2.6
Checking puppy files inside initrd...
Searching for Puppy files on ATA devices...
Search puppy file on ATA skipped. Probe USB devices only
Wait for USB devices to get ready...
Waiting for USB completed
FATAL ERROR: puppy_quickpup64_24.01.sfs file not found!

What is the boot parameter of QuickPup64 in your ventoy?

Here's a view of virtual PC booting the USB and launching the ISO file.
The PC is started from the terminal here

.
A GIF of the VM steps to boot QP64 is contained in this link

As you can see, no parms used/changed

Changes:
* Bugfixes on sleep
* Updated efi image for live-cd
* Added binfmt registration
* Bugfixes on wsdd protocol support

Download: https://1drv.ms/u/s!As14nV96TZw0ggFwUbA ... J?e=DGMbug
MD5 Checksum: 6eb0f833978853a7f8b0da807f03ad92

Preliminary tests: Ventoy and SG2D on bare-metal boots to desktop on AMD PC. Have not tested beyond desktop. Will report later or tomorrow on session management attempts in bare-metal on Intel test PCs.

hi folks
i was DL the quickpup64 rc7 cos ticoo1 said shutdownconfig get delay (4-5s) when press on save/no button at the first window at 1. shutdown ... this happen when glibc greater than 2.37... I was found the problem in the gtkdialog... anyway get broken pipe fail in the terminal ...

When i remove the progressbar widget evrything ok around buttons, and no error in terminal ...
(may need replace that code in woof-ce...)

some commands here difrent erros

I used stickpup on fossapup64 to make a usb of quickpup64 and when I try to boot from it I get /quickpup64/initrd.gz not found. I am trying this operating system because I heard it works for Dropbox.

LANdpLAN wrote: ↑Sat May 25, 2024 4:02 am

I used stickpup on fossapup64 to make a usb of quickpup64 and when I try to boot from it I get /quickpup64/initrd.gz not found. I am trying this operating system because I heard it works for Dropbox.

quickpup use initrd.xz , edit your bootloader config ... (tricky)

KuLuSz wrote: ↑Sat May 25, 2024 5:15 am

LANdpLAN wrote: ↑Sat May 25, 2024 4:02 am

I used stickpup on fossapup64 to make a usb of quickpup64 and when I try to boot from it I get /quickpup64/initrd.gz not found. I am trying this operating system because I heard it works for Dropbox.

quickpup use initrd.xz , edit your bootloader config ... (tricky)

Easier - rename initrd.xz to initrd.gz

I know how to rename files. Where do I find initrd?

I found initrd.xz in the .iso that stickpup used and copied it to the new usb /mnt/sdc1/quickpup64/initrd.xz renamed it to gz and it's working.