QuickPup64 24.01 RC 14

[Geek3579]

Hi @TerryH ,

If this bit of info does not help you it might help others who have trouble booting QuickPup64 23.01 RC3.

In my case the ISO booted fine in a QEMU virtual machine. A frugal install booted fine in a 5 year old laptop.

But I had issues booting with a relatively new (2023) laptop - an HP + AMD / Radeon.
The puppy_quickpup64...sfs could not be found. Actually I was booting from an SD card, with the Puppy frugal folders in a ext4 SSD partition. This was solved by changing pmedia=usbflash in the GRUB2 code to : pmedia=satahd as I was booting from an SSD hard drive partition.

Following that the boot continued further until the video would not load (whatever the term is) and xorgwizard sent me around in circles getting nowhere. Finally I checked the README-extra_sfs text file in the ISO and consequently downloaded the updated firmware fdrv from http://www.fishprogs.software/puppy/firmware-sfs/ and swapped out the old fdrv.

Problem solved, although this meant that pupmode=12 was used, whereas I prefer pupmode=13 ). But at least I had a working frugal install.

[TerryH]

Hi @TerryH ,

If this bit of info does not help you it might help others who have trouble booting QuickPup64 23.01 RC3.

In my case the ISO booted fine in a QEMU virtual machine. A frugal install booted fine in a 5 year old laptop.

But I had issues booting with a relatively new (2023) laptop - an HP + AMD / Radeon.
The puppy_quickpup64...sfs could not be found. Actually I was booting from an SD card, with the Puppy frugal folders in a ext4 SSD partition. This was solved by changing pmedia=usbflash in the GRUB2 code to : pmedia=satahd as I was booting from an SSD hard drive partition.

Following that the boot continued further until the video would not load (whatever the term is) and xorgwizard sent me around in circles getting nowhere. Finally I checked the README-extra_sfs text file in the ISO and consequently downloaded the updated firmware fdrv from http://www.fishprogs.software/puppy/firmware-sfs/ and swapped out the old fdrv.

Problem solved, although this meant that pupmode=12 was used, whereas I prefer pupmode=13 ). But at least I had a working frugal install.

Thanks for the suggestion, I downloaded the latest firmware(both, worth having for other installs as well), unfortunately still won't boot to desktop.

[Geek3579]

The only other thing I try sometimes is to add/extend the wait time in the GRUB2 code: nousbwait=10
I always have nousbwait=5 for all Puppy OS, BTW.

[Clarity]

In my case the ISO booted fine in a QEMU virtual machine. A frugal install booted fine in a 5 year old laptop.

But I had issues booting with a relatively new (2023) laptop - an HP + AMD / Radeon.
The puppy_quickpup64...sfs could not be found. ...

Hello.

I ask

• Are you using UEFI QEMU feature to mimic your laptop?

• Can I see your QEMU boot stanza?

Thanks.

[Geek3579]

In my case the ISO booted fine in a QEMU virtual machine. A frugal install booted fine in a 5 year old laptop.

But I had issues booting with a relatively new (2023) laptop - an HP + AMD / Radeon.
The puppy_quickpup64...sfs could not be found. ...

Hello.

I ask

• Are you using UEFI QEMU feature to mimic your laptop?

• Can I see your QEMU boot stanza?

Thanks.

That's a good question. I was booting the ISO using QEMU WITHOUT the EFI stanza ( -bios /usr/share/ovmf/OVMF.fd ). Its the lazy way to run a virtual Puppy OS, you just create a virtual drive with one ext4 partition for the save folder. If I really wanted to create a standalone EFI frugal install I would have had to run a virtual Puppy OS, use it to partition to virtual drive, run grub2-config to set up the GRUB + EFI in a FAT32 partition and create the second partition with the added frugal files. Then edit the grub.conf file.

Anyhow, I just tried booting quickpup64_23.01-rc-3.iso WITH the EFI stanza but it would not boot.
My older laptop has EFI, and a SSD, and it had a typical frugal install. No problems.
The newer laptop also has an SSD, but needed pmedia=satahd to find the main puppy...sfs. Go figure.

[Clarity]

I was booting the ISO using QEMU WITHOUT the EFI stanza ( -bios /usr/share/ovmf/OVMF.fd ). ... Anyhow, I just tried booting quickpup64_23.01-rc-3.iso WITH the EFI stanza but it would not boot.

My older laptop has EFI, and a SSD, and it had a typical frugal install. No problems.
The newer laptop also has an SSD, but needed pmedia=satahd to find the main puppy...sfs. Go figure.

Thanks for that useful info!

I was curious if the UEFI stanza would mimic your newest laptop for booting the ISO file.

BTW: Which version of QEMU are you using with QP64? I'm using v7.2 from @norgo (I think, IIRC)

[Geek3579]

I was booting the ISO using QEMU WITHOUT the EFI stanza ( -bios /usr/share/ovmf/OVMF.fd ). ... Anyhow, I just tried booting quickpup64_23.01-rc-3.iso WITH the EFI stanza but it would not boot.

My older laptop has EFI, and a SSD, and it had a typical frugal install. No problems.
The newer laptop also has an SSD, but needed pmedia=satahd to find the main puppy...sfs. Go figure.

Thanks for that useful info!

I was curious if the UEFI stanza would mimic your newest laptop for booting the ISO file.

BTW: Which version of QEMU are you using with QP64? I'm using v7.2 from @norgo (I think, IIRC)

I am using the version which was compiled for Fossapup64 and bundled with a GUI:
QEMU emulator version 7.0.50 (v7.0.0-679-g9cf289af47), which has been my open door to using QEMU. I just use the scripts now, but without that version I coundn't get started as it seems the scripts are very sensitive to syntax differences, which may depend on how the QEMU package was put together. On odd occasions where I am unsure of the scripting I also run AQEMU.

[mistfire]

QuickPup64 23.01 RC 4 released

Changes:
* Glibc 2.38
* Linux kernel 6.5.7
* Some bugfixes

Download:https://drive.google.com/file/d/1KANS9w ... O3Ja_BmdHT
MD5 Checksum: a2140b86739697d414be45c7526e6e28

[one]

QuickPup64 23.01 RC 4 released

Changes:
* Glibc 2.38
* Linux kernel 6.5.7
* Some bugfixes

Hi @mistfire,

thank you for the updated version (Glibc 2.38) -

I notice a problem with the save_session mechanism:

i have a frugal installation on ssd in pupmode 13.
- when i use a savefolder (old or new) the session is saved - no matter if i say yes or no in the save session dialog!

Shutdown - Xdialog save current session - yes or no?
I choose "no" --> closing network connections --> stop background services --> acpid

But then a second time the question comes up if I want to save the session (yes/no) or if 60 sec. should pass without saving.

Here I can't change with TAB to "no" - and even if I let the 60 sec. pass - the session is saved!

Can someone reproduce this behaviour?

PS: First shutdown does work correct - you can choose yes/no at shutdown.

peace

[mistfire]

QuickPup64 23.01 RC 4 released

Changes:
* Glibc 2.38
* Linux kernel 6.5.7
* Some bugfixes

Hi @mistfire,

thank you for the updated version (Glibc 2.38) -

I notice a problem with the save_session mechanism:

i have a frugal installation on ssd in pupmode 13.
- when i use a savefolder (old or new) the session is saved - no matter if i say yes or no in the save session dialog!

Shutdown - Xdialog save current session - yes or no?
I choose "no" --> closing network connections --> stop background services --> acpid

But then a second time the question comes up if I want to save the session (yes/no) or if 60 sec. should pass without saving.

Here I can't change with TAB to "no" - and even if I let the 60 sec. pass - the session is saved!

Can someone reproduce this behaviour?

PS: First shutdown does work correct - you can choose yes/no at shutdown.

peace

@one what is your settings on Save Session tab in Puppy Event Manager? Also may I see the content of your /etc/eventmanager file?

[one]

Hi @mistfire,

everything seems ok for me ...

[mistfire]

QuickPup64 23.01 RC5 released

Changes:
* PUPMODE 13 ask to save function bugfix
* Pipewire 0.3.82

Download:https://drive.google.com/file/d/1cQEa9Z ... XuOsWWgRjQ
MD5 Checksum: d38884e74b160b37b06f80e7324f05ef

[mistfire]

Hi @mistfire,

everything seems ok for me ...

This issue has been fixed on QuickPup64 23.01 RC5

[one]

Hi @mistfire,

everything seems ok for me ...

This issue has been fixed on QuickPup64 23.01 RC5

Hi @mistfire,

Sorry - but no, not on my side.

I took rc5, created a new savefolder during the first shutdown and the session is always saved during the following shutdowns.

Are you saying that on your side save session works as expected?

peace

[mistfire]

Hi @mistfire,

everything seems ok for me ...

This issue has been fixed on QuickPup64 23.01 RC5

Hi @mistfire,

Sorry - but no, not on my side.

I took rc5, created a new savefolder during the first shutdown and the session is always saved during the following shutdowns.

Are you saying that on your side save session works as expected?

peace

May I see the content of your /etc/eventmanager file?

[TerryH]

QuickPup64 23.01 RC 4 released

Changes:
* Glibc 2.38
* Linux kernel 6.5.7
* Some bugfixes

Hi @mistfire,

thank you for the updated version (Glibc 2.38) -

I notice a problem with the save_session mechanism:

i have a frugal installation on ssd in pupmode 13.
- when i use a savefolder (old or new) the session is saved - no matter if i say yes or no in the save session dialog!

Shutdown - Xdialog save current session - yes or no?
I choose "no" --> closing network connections --> stop background services --> acpid

But then a second time the question comes up if I want to save the session (yes/no) or if 60 sec. should pass without saving.

Here I can't change with TAB to "no" - and even if I let the 60 sec. pass - the session is saved!

Can someone reproduce this behaviour?

PS: First shutdown does work correct - you can choose yes/no at shutdown.

peace

Quickpup won't boot on my laptop. I tried rc4 on an older desktop. I had the same experience on shutting down.

[one]

This issue has been fixed on QuickPup64 23.01 RC5

Hi @mistfire,

Sorry - but no, not on my side.

I took rc5, created a new savefolder during the first shutdown and the session is always saved during the following shutdowns.

Are you saying that on your side save session works as expected?

peace

May I see the content of your /etc/eventmanager file?

Hi @mistfire,

it's the same file I posted in my previous post ...

peace

[ljlj]

greetings
alpine apk
opera mini apk
can you install on quickpup
and does it work?
thanks.

[d3Xt3r]

I'm unable to get Xorg working on my Ryzen laptop. [ ThinkPad Z13 Gen 1 | Ryzen 7 PRO 6850U | Radeon 680M iGPU ]

I tried all the display drivers and modes (via xorgwizard) in the stock RC5 ISO and nothing worked, so I updated the ISO with the latest firmware sfs. With the updated drivers, the resolution of the console looks much better - appears to be running at the native resolution now, but X still doesn't load. No luck with xorgwizard either.

Xorg.log says:

Code: Select all

(WW) Open ACPI failed (var/run/acpid.socket) (No such file or directory)
(WW) AMDGPU(0): 8 ZaphodHeads crtcs unavailable. Some outputs will stay off.
(WW) AMDGPU(0): Unable to find initial modes
(EE) AMDGPU(0): Output eDP enabled but has no modes
(EE) AMDGPU(0): No modes.
(EE) Screen(s) found, but none have a usable configuration.
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

I don't have this issue with any other distro, but then again, they all use Wayland. Is there any way I can try Wayland in QuickPup? I really don't want to get back to writing custom Xorg.conf files like we used to 20 years ago (and besides, that would defeat the purpose of Puppy being an easy-to-use distro).

[mistfire]

@d3Xt3r
May I see the your /etc/X11/xorg.conf file?

Yes you can try Wayland. You need to find a suitable DE with wayland support. XFCE wayland support was currently work in progress

[d3Xt3r]

@d3Xt3r
May I see the your /etc/X11/xorg.conf file?

Thank you, here's my xorg.conf: https://paste.centos.org/view/805531bc

[mistfire]

@d3Xt3r
May I see the your /etc/X11/xorg.conf file?

Thank you, here's my xorg.conf: https://paste.centos.org/view/805531bc

Thanks for sending. it's weird that the xorg-autoconf generated output was ati. Can you send the /var/log/Xorg.0.log file and the contents of /var/hwdata. If you cannot found the /var/hwdata folder. Just send the terminal output of your computer using this command

Code: Select all

busybox lscpi

[d3Xt3r]

Thanks for sending. it's weird that the xorg-autoconf generated output was ati. Can you send the /var/log/Xorg.0.log file and the contents of /var/hwdata. If you cannot found the /var/hwdata folder. Just send the terminal output of your computer using this command

Code: Select all

busybox lscpi

Xorg.0.log: https://paste.centos.org/view/d9913b77
hwdata: https://paste.centos.org/view/af70e642

[Vverve]

Nice work mistfire !
RC5 here , frugal install ,after adding iwlwifi-8000C-36.ucode ,wifi works .
Know your familly,fear no big brother....installed gg-chrome-latest debian , all ok , hmm , interesting password options with warnings on first run.
Do got ,as in most ''puppy variant/derivative'' got to tweak this wacom-capacitive touch device settings for finger touch to work as it should ,pen worked ootb.
Applause for pipewire integration (no bluetooth test ) ,great ,fun,got to turn off xvkb key-clicks off ,first time i eard it working !!!!
Intel 6th gen 8Gb/ram here ,it sure run light xfce fine... jwm/rox fan here ,tried your ''native'' jwm desktop environment change , i see its not getting it for now , will you work on it?
Fast enough after save folder created , just testing ,running it now with rockedge rt kernel ...faster, did not took time to check settings, but it sure with original kernel recognised/optimized cpu speed on battery !
Let my usual pmedia=ataflash argument , do get save to flash,get warning,notification , work ,but still confused with ''log out'' reboot option no save still end up with the wait 60 sec script, annoying 1minute if you dont use a keyboard... details ,and RC .
A whole lot in there ! i like it . A pleasure to dig and test some more !

[Clarity]

QuickPup64 23.01 RC5 released ...

Booted ISO in following vehicles: QEMU, Ventoy, SG2D, and bare-metal. No boot stanzas were adjusted nor modified.

Boot progress report can be seen in this photo album

This distro's operations on desktop continues to be stable and speedy.

Thanks as I begin tests and use of audio with your replacement with Pipewire.

[sieger007]

Just 2 Lil
-- ALL MY CONFIGS & extra programs are installed into Fossapup 9.5 partition which is how I started off using Puppy . I want to be able to use the 2FS file I created for 9.5 with this 22 version. I tired it out of the box but , the program hangs ( after boot everything will freeze or sometimes it just wont boot ). I figure I have to some how painstakingly , copy Foss 2FS to this versions 2FS all the programs that I am interested in .. in which case an approach like if it exists on 22 DONT rsync or else go ahead and rsycn all those newer programs I installed ? Has anyone had luck with this ? How do I do this .

-- I downloaded the original 22.x version whence the thread 1st started. Any guide to upgrade to 23.x without the need to install another partition or additional grub line for 23 ( if it makes sense. If not then prolly end up having an extra 23 op in my grub )

[mistfire]

Just 2 Lil
-- ALL MY CONFIGS & extra programs are installed into Fossapup 9.5 partition which is how I started off using Puppy . I want to be able to use the 2FS file I created for 9.5 with this 22 version. I tired it out of the box but , the program hangs ( after boot everything will freeze or sometimes it just wont boot ). I figure I have to some how painstakingly , copy Foss 2FS to this versions 2FS all the programs that I am interested in .. in which case an approach like if it exists on 22 DONT rsync or else go ahead and rsycn all those newer programs I installed ? Has anyone had luck with this ? How do I do this .

-- I downloaded the original 22.x version whence the thread 1st started. Any guide to upgrade to 23.x without the need to install another partition or additional grub line for 23 ( if it makes sense. If not then prolly end up having an extra 23 op in my grub )

In order to migrate from Fossapup to QuickPup64. Try this:

* Create a new save file on QuickPup64 then load it.
* Mount your Fossapup64 save file by double clicking it
* Copy the /home and /root folder from Fossapup64 save file to "/" of QuickPup64 File system.
* Unmount your Fossapup64 save file clicking the Eject button on the sidebar of Thunar

Take note: Only personal files and setting can be migrated from Fossapup64. Extra programs will not include on migration. You need to reinstall it on QuickPup64

-- I downloaded the original 22.x version whence the thread 1st started. Any guide to upgrade to 23.x without the need to install another partition or additional grub line for 23 ( if it makes sense. If not then prolly end up having an extra 23 op in my grub)

If QuickPup64 22.x was frugal install. Just delete the kernel, initrd, and SFS files of QuickPup64 22.x and replace with latest one.

[Vverve]

I just wished i follow quickpup64 development earlier ,missed 2years of beta+rc,but hey ,so many interesting projects going on ! The real devs do seems to follow the pace of most of them,i cant and stay that smiling end-user-system-breaker.

Had a glitch, install an sfs including xvkbd , worked, unloading the sfs to next queue ,saved,reboot , install a pet ,same bundle,with xvkbd in it ,warning,no usr/bin/xvkbd ,but its there !!!?!! hmm ,ok,uninstalled the pet , now ''iso's included xvkbd'' is see ,exec ok ,
normal behaviour ? as an sfs "overlay" and pet "install" ,if i can say so? not a problem ,just try to understand .
Lot of helping notifications ...but not about if you install a pkg over an ''iso's included one'' with a pet would break it , i did not yet go trough 13 pages of forum , could have been state somewhere or a fact knew by most of you .
An online automated pkg updater ,with options , wow !
Got to dig some more to get xvkbd the one and only composer pkg affected(transparency) i successfully do with xcompmgr ,elsewhere .

Well done and interesting puppy .
edit; what's the window compositor used here ? no compton ,picom?!?
ok,GNOME is a desktop environment which comes with a compositor of it's own...solved
edit 2; so used to get transparency with xcompmgr , had it in a one pet ,removing it did it .

[mistfire]

what's the window compositor used here ? no compton ,picom?!?

It uses xfwm4 as window compositor (builtin to xfce desktop environment). but you can also use other window compositor if you want.

[one]

Hi @mistfire,

Sorry - but no, not on my side.

I took rc5, created a new savefolder during the first shutdown and the session is always saved during the following shutdowns.

Are you saying that on your side save session works as expected?

peace

May I see the content of your /etc/eventmanager file?

Hi @mistfire,

it's the same file I posted in my previous post ...

peace

Hi @mistfire,

I ask again: does save session in pupmode 13 work as expected on your side?

peace