Announcements about LxPup, SPups, UPups, VPups, Chromium, LXQt & Xfce addons, Kernels etc.

[mow9902]

Thanks for updating the link Peebee.

I've been using your chromium builds for ages without any issues ..until now.

I am running a frugal install of fossapup64-CE. All of your chromium versions up to and including 114.0.5735.90 have worked flawlessly for me.
However - this latest version 115.0.5790.170 does not work on my system because of the GLIBC version required.
I suspect this is not something I can personally 'fix' without stuffing other apps. If there is any advice you can give I would be grateful, if not, then unfortunately it looks like I will have to part ways with your regular chromium builds.

115 error.png (92.52 KiB) Viewed 8374 times

Thanks for the service to this point.

[peebee]

I am running a frugal install of fossapup64-CE. All of your chromium versions up to and including 114.0.5735.90 have worked flawlessly for me.
However - this latest version 115.0.5790.170 does not work on my system because of the GLIBC version required.

There is an alternative build from Alien-Bob which works on older glibc:
https://sourceforge.net/projects/lxpup/ ... s/download

[peebee]

Kernel Build 6.4.14-lxpup64 (x86_64)
Build Date Sat Sep 2 18:16:11 BST 2023
Build GCC 13.2.0

aufs6.x-rcN
uconn.c reverted to 6.4.6 (drm/nouveau/disp)

needs firmware (e.g. by fdrv)

from here

[peebee]

chromium.sfs (RUNS-AS-SPOT) both 32-bit and 64-bit versions from AlienBob & Snap (& Debian & Void) packaged for Puppy

via Menu -> Internet -> Get Web Browser

but see below .... 32-bit 120.0.6099.224 ** https://sourceforge.net/projects/lxpup/ ... s/download

64-bit 124.0.6367.60_snap (and 124.0.6367.60_alien version for older glibc) https://sourceforge.net/projects/lxpup/ ... /browsers/

**WARNING: Login to Google services with the 32-bit version is blocked

.... Alien-Bob has decided that his 32-bit builds will no longer be updated as frequently - if you want a more up-to-date 32-bit version these
Alternative 32-bit Chromium builds are also available:
Debian (or Mint) based for LxPupSc32, NoblePup32 and VoidPup32 - 124.0.6367.60 **
Void based for LxPupSc32, NoblePup32 and VoidPup32 - 124.0.6367.60 **

[peebee]

https://sourceforge.net/projects/lxpup/ ... /browsers/ (64-bit https://sourceforge.net/projects/lxpup/ ... /browsers/)

The browsers in this folder are provided as add-ons for LxPupSc, S15Pup, UPup & VoidPup 32bit builds

The versions of the browsers as of 31-Aug-2023 with their md5sums are:

see above links

[peebee]

Kernel Build 6.5.9-lxpup64 (x86_64)
Build Date Thu Oct 26 07:52:24 BST 2023
Build GCC 13.2.0

aufs6.5

needs firmware (e.g. by fdrv)

from here

[mow9902]

Thanks again for keeping these updated peebee. Works fine on my F96-4

[peebee]

A testing version of BookwormPup32 is available to download

viewtopic.php?t=9766

[peebee]

64 bit but can be used on 32 bit builds if CPU is 64-bit compatible
aufs enabled
NON-usrmerge
LTS (Long Term Support) version

Kernel Build 6.6.17-lxpup64 (x86_64)
Build Date Sat Feb 17 07:56:57 GMT 2024
Build GCC 13.2.0

aufs6.6.4

needs firmware (e.g. by fdrv)

from here

[peebee]

231111 Latest S15Pup, VoidPup, UPup32 (Bionic, Focal, Jammy) builds:
https://sourceforge.net/projects/pb-gh-releases/files/

Kernel change for Bionic32 and Focal32 to 5.10
4.19 and 5.4 are no longer built on Github ( https://github.com/puppylinux-woof-CE/w ... 6ab2984568 )

[ozsouth]

@bigpup - my above posts refer to overlayfs in s15pup64. Overlayfs is different from the past aufs options. Since aufs has issues now & won't be worked on for months, overlayfs - warts & all - must be an option.

[peebee]

240125
Built on Woof-CE - transferred to SourceForge updates:
https://sourceforge.net/projects/pb-gh-releases/files/

[peebee]

240208
Built on Woof-CE - transferred to SourceForge updates:
https://sourceforge.net/projects/pb-gh-releases/files/

[peebee]

64 bit but can be used on 32 bit builds if CPU is 64-bit compatible
aufs & overlayfs enabled
NON-usrmerge
LTS (Long Term Support) version

6.6.22 can be downloaded from: https://github.com/puppylinux-woof-CE/w ... 8289777128

Kernel Build 6.6.19-lxpup64 (x86_64)
Build Date Sat Mar 2 11:39:13 GMT 2024
Build GCC 13.2.0
aufs6.6.4

also
Kernel Build 6.7.7-lxpup64 (x86_64)
Build Date Fri Mar 1 18:33:03 GMT 2024
aufs6.7

needs firmware (e.g. by fdrv)

from here

[peebee]

240223
Built on Woof-CE Github - transferred to SourceForge updates:
https://sourceforge.net/projects/pb-gh-releases/files/

[peebee]

240309
Built on Woof-CE Github - transferred to SourceForge updates:
https://sourceforge.net/projects/pb-gh-releases/files/

(VoidPup had to be re-uploaded on 240310 at 07.00 GMT)

[peebee]

64 bit but can be used on 32 bit builds if CPU is 64-bit compatible
aufs & overlayfs enabled
NON-usrmerge

Kernel Build 6.8.8-lxpup64 (x86_64)
Build Date Sat Apr 27 18:38:25 BST 2024
Build GCC 13.2.0
aufs6.8

needs firmware (e.g. by fdrv)

from here

[peebee]

240323
Built on Woof-CE Github - transferred to SourceForge updates:
https://sourceforge.net/projects/pb-gh-releases/files/

[TubaToothpaste]

@peebee
Where should we post discussion / issues / questions about NoblePup32 ?

More specifically, issues with USRMERGE and un-safe packages ?

Code: Select all

smartmontools_7.3-1+b1 [plus-bookworm-debs]
xfsdump_3.1.11-0.1     [plus-bookworm-debs]
xfsprogs_6.6.0         [ubuntu-noble-main]

I've searched through most active forums, but don't see an obvious thread.

Thanks.
-- Will (TubaToothpaste)

[peebee]

@peebee
Where should we post discussion / issues / questions about NoblePup32 ?

Hi

There is no thread yet for NoblePup32 as it hasn't been released ...... and there are still doubts over whether it will be due to the "t64" problem.

You can post problems in: viewtopic.php?t=472

[peebee]

240413
Built on Woof-CE Github - transferred to SourceForge updates:
https://sourceforge.net/projects/pb-gh-releases/files/

[peebee]

240420
Built on Woof-CE Github - transferred to SourceForge updates:
https://sourceforge.net/projects/pb-gh-releases/files/

[Clarity]

Problems booting 240420 64bit versions in a VM

Failures

1. Direct ISO boot fails immediate on startup

2. Booting when launched from Ventoy USB fails attempting to show desktop

PC used for testing
Dell i5
8GB RAM
nVidia adapter
Ventoy USB stick
HDMI to TV
Comment: On my test PCs, if an ISO doesn't boot in the VMs I use, they WONT BOOT on bare-metal as they yield the identical same results.

VM Stanza - QEMU emulator version 7.2.9 (Debian 1:7.2+dfsg-7+deb12u5)

Code: Select all

qemu-system-x86_64 -name "S15 v420 ISO file direct-boot" -enable-kvm -smp 2 -m 2048 -vga cirrus -device AC97 -net nic -net user -rtc base=localtime /mnt/sdg1/BOOTISOS/S15Pup64-22.12-240420.iso

Forum	-------- Bare-Metal --------	----------- QEMU (VM) -----------	PXE

Distro	Ventoy	SG2D	Native	Ventoy	SG2D	PXE
S15Pup64-22.12-240420	N(6)	N(6)	N(1)	N(2)	N(2)	N
VoidPup64-22.02-240420	N(6)	N(6)	N(1)	N(2)	N(2)	N
						N

Legend for 'N' 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 PSAVE manually added to GRUB2 Menu stanza at boot

• (6) - Not tested

Wont Boot(2).jpg (26.23 KiB) Viewed 691 times

S15 via Ventoy

Wont Boot(1).jpg (13.35 KiB) Viewed 691 times

Void via Ventoy

Wont Boot.jpg (13.49 KiB) Viewed 691 times

[peebee]

Problems booting 240420 64bit versions in a VM

@dimkr - is this likely to be a consequence of:
https://github.com/puppylinux-woof-CE/woof-CE/pull/4272
??

[dimkr]

@peebee It's a PR, not merged yet. It can't affect anything until it's merged.

[peebee]

Oops - you're right!

@Clarity did the previous versions 240413 (still available) boot correctly?

I don't see anything in the Woof-CE commits in the last 7 days to explain a difference..... maybe kernels have had a bump.....
https://github.com/puppylinux-woof-CE/w ... s/testing/

[Clarity]

Thanks @peebee and @dimkr
Will check when at home this eve and report back. I did provide the QEMU stanza so others could also verify.

This eve, I will download a prior version from GIT and try again. BTW: I did verify the checksums to be sure I had good downloaded ISO files for each v420 distros.

Later

[Clarity]

Results of WoofCE ISO and IMG files I have downloaded iin 2024. Added Fatdog, a non-WoofCE ISO

Results

Forum	------ Bare-Metal ------	------- QEMU (VM) -------	PXE

Distro	Ventoy	SG2D	Native	Ventoy	SG2D	PXE
F96-CE_5-alpha3 ISO	Y(5)	Y	Y	Y	Y	N(6)
quickpup64_24.01-rc-4 ISO	N(6)	N(6)	Y	N(1)	Y	N(6)
s15pup64-22.12-231209-ovrly-4t ISO	N(6)	N(6)	N(1)	N(2)	N(2)	N(6)
S15Pup64-22.12-240309 ISO	N(6)	N(6)	N(1)	N(2)	N(2)	N(6)
S15Pup64-22.12-240420 ISO	N(6)	N(6)	N(1)	N(2)	N(2)	N(6)
VoidPup64-22.02-240309 ISO	N(6)	N(6)	N(1)	N(2)	N(2)	N(6)
VoidPup64-22.02-240420 ISO	N(6)	N(6)	N(1)	N(2)	N(2)	N(6)
vanilladpup-10.0.41-xwayland ISO	N(6)	N(6)	Y	Y	Y	N(6)
vanilladpup-11.0.91-ext4-2gb-bios IMG	N(6)	N(6)	Y	N(1)	N(4)	N(6)
Fatdog64-901 ISO	Y	Y	Y	Y	Y	Y
BookwormPup64_10.0.6 ISO	Y(5)	Y	Y	Y	Y	N(6)

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

[peebee]

Can only think it's something to do with the kernel config.
Determining what kernel config needs to be changed is probably best achieved by posts on other threads.
viewforum.php?f=107
viewforum.php?f=65

[Clarity]

Thanks @peebee. I feel you are correct as this occurs when the distro is in control after its own Menu processing. Not sure which option in the kernel-build is the culprit.

BUT, I dont run traditional frugals. ISO boots with persistence are the frugal I only used for last 5 years. Thus no extractions or rebuilds/retooling drive boot menu system are ever used. Merely download ISO file and boots are direct from distro's ISO file.

Some other member(s) could step in to do a switch, if someone else could help. Several developers run VMs to test their work.

EDIT: My report has an amendment added for clear understanding.