VoidPup Woof-CE builds (32bit and 64bit versions)

[peebee]

WARNING - Void is a rolling release distro, each VoidPup release is a snapshot and will become out of date over time.
"vpm up" will indicate how out of date.
installing apps with vpm may download items into the savearea
it is better to update to the latest release (snapshot) before installing new apps

See this post for date of latest build on Github available from Sourceforge

VoidPup32-22.02.iso + devx + nlsx kernel 5.10.x + LXDE + XFCE

VoidPup64-22.02.iso + devx + nlsx kernel 5.15.x + LXDE + XFCE

World download map for VoidPup64: https://sourceforge.net/projects/pb-gh- ... /stats/map

Constructed to experiment with the replacement of PPM with VPM (Void Package Manager)......... a "Woof-CE" Puppy build......

Thanks to @jamesbond & @wiak & @rockedge for assistance in getting to this stage.
.

Screenshot.png (113.13 KiB) Viewed 32855 times

.

Screenshot.png (112.03 KiB) Viewed 32855 times

[peebee]

VoidPup build recipes are on GitHub:

https://github.com/puppylinux-woof-CE/w ... /voidpup32
https://github.com/puppylinux-woof-CE/w ... /voidpup64

[peebee]

Youtube review by Gosh-It's-Arch.....

[Marv]

Updated my 64b VoidPup install (with ydrv LXDE) from v22.02 +4 to 22.02 +5. As usual, booted both pristine and with a scrubbed savefile on the i5 based Fujitsu S761. Clean boot both ways, all settings preserved with the savefile. One thing noted in dmesg, present both in a pristine boot and in the updated savefile version:

# dmesg | grep -i fail
[ 6.478646] button: module verification failed: signature and/or required key missing - tainting kernel

Not present if I revert to the 5.15.30 Ozsouth kernel.

I'll continue to use this as my daily.

Thanks,

Update as of 18 June, 2022: Updated from the 64b v22.02 +5 to +6 using the delta generated iso, md5sum checked as usual. As above, a perfectly smooth update. The notes on the dmesg above still apply with the stock kernel. Another thing noted in both +5 and +6 with the stock kernels is that I have to add a network restart line to the suspend.sh script in /etc/ACPI/actions (I'm using peasywifi 4.6). No addition or modification needed there with Ozsouths' 5.15.30 kernel. Using that with +6 as my daily driver now. A snappy and solid daily driver it is!

Thanks again,

Update as of 25 July, 2022: Updated from VoidPup64 22.02 +6 to +7 on the Fujitsu S761 laptop install using the delta generated iso, md5sum checked. I have been running VoidPup with the 5.18.6 kernel on the i5 based laptops and with Ozsouths 5.15.50 on my two Bay Trail based desktops. Both flawless. First updated using the +7 stock kernel. Smooth update, no issues noted. Then bumped the kernel to 5.18.14 (did LxPupSc64 first to test) on my daily use laptop. Clean Dmesg, good idle resource use, and unchanged rock solid operation so far. I continue to use synaptics drivers for all touchpads and all browsers, email, word & spreadsheet processing run as portables. Currently at Slimjet64 Version 35.0.1.0 (based on Chromium 101.0.4951.34) and ungoogled chromium Version 103.0.5060.68 in VoidPup with a slightly older Slimjet in LxPupSc64 (version 34.0.1.0) in LxPupSc64.

VoidPup64 with LXDE and PCManFM continues to be my dependable daily.

and again

[Clarity]

I view this as important information for PUP development as they understand how a user PC sees booting VoidPUP64.

The bootinit.log:

Code: Select all

Using sdb1:/boot-isos/VoidPup64-22.02+7.iso
Using sdb1:/boot-isos/SAVESPEC
0: PMEDIA=atahd PDRV= PSUBDIR= pfix=fsck
1: PDRV= P_BP_ID=loop0 P_BP_FN=
2: ONE_PART=loop0 ONE_FN=/puppy_vpup64_22.02.sfs ONE_MP=/mnt/pdrv
6: ONE_PART=loop0 ONE_TRY_FN=/puppy_vpup64_22.02.sfs PDRV=loop0,iso9660,/puppy_vpup64_22.02.sfs
fdisk: can't open '/dev/mmcblk0': No such file or directory
mount -t aufs -o udba=reval,diropq=w,br=/mnt/tmpfs/pup_rw=rw,xino=/mnt/tmpfs/.aufs.xino unionfs /pup_new
mount -o remount,append:/pup_ro2=rr /pup_new
mount -o remount,append:/pup_f=rr /pup_new
mount -o remount,append:/pup_z=rr /pup_new
mount -o remount,add:1:/pup_a=rr /pup_new
--------------------
SAVE_MP=/mnt/dev_save
PRAMONLY=
BOOTDRV=
rootfs on / type rootfs (rw,size=3502212k,nr_inodes=875553,inode64)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3502240k,nr_inodes=875560,mode=755,inode64)
/dev/sdb1 on /mnt/idrv type ext4 (rw,noatime)
/dev/loop0 on /mnt/pdrv type iso9660 (ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8)
tmpfs on /mnt/tmpfs type tmpfs (rw,relatime,inode64)
/dev/loop1 on /pup_ro2 type squashfs (ro,noatime,errors=continue)
unionfs on /pup_new type aufs (rw,relatime,si=6aa41cae8361d91e)
/dev/loop2 on /pup_f type squashfs (ro,noatime,errors=continue)
/dev/loop3 on /pup_z type squashfs (ro,noatime,errors=continue)
/dev/loop4 on /pup_a type squashfs (ro,noatime,errors=continue)
/dev/sda7 on /mnt/dev_save type ext4 (rw,noatime)
--------------------
FND_MULTIFOLDER=
PUP_SAVES=sda7,ext4,/Sessions/vpup64save-v...7_pristine
sda7,ext4,/Sessions/vpup64save-v226
NUMPUP_SAVES=2

----
Have selected pupsave 1
PSPATH=/mnt/dev_save//Sessions/vpup64save-v...7_pristine
PUPSAVE=sda7,ext4,/Sessions/vpup64save-v...7_pristine
Setting PUPMODE 12
SAVE_LAYER=/pup_rw
--SAVEFOLDER-- /mnt/dev_save/Sessions/vpup64save-v...7_pristine
'/pup_rw' -> '/mnt/dev_save/Sessions/vpup64save-v...7_pristine'
mount -o remount,prepend:/pup_rw=rw,mod:/mnt/tmpfs/pup_rw=ro,del:/mnt/tmpfs/pup_rw /pup_new
Moving mountpoints to /pup_new/initrd for after switch...
mount -o move /pup_ro2 /pup_new/initrd/pup_ro2
mount -o move /pup_f /pup_new/initrd/pup_f
mount -o move /pup_z /pup_new/initrd/pup_z
mount -o move /pup_a /pup_new/initrd/pup_a
mount -o move /mnt/tmpfs /pup_new/initrd/mnt/tmpfs
mount -o move /mnt/dev_save /pup_new/initrd/mnt/dev_save
--------------------
rootfs on / type rootfs (rw,size=3502212k,nr_inodes=875553,inode64)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=3502240k,nr_inodes=875560,mode=755,inode64)
tmpfs on /pup_new/initrd/mnt/tmpfs type tmpfs (rw,relatime,inode64)
/dev/loop1 on /pup_new/initrd/pup_ro2 type squashfs (ro,noatime,errors=continue)
unionfs on /pup_new type aufs (rw,relatime,si=6aa41cae8361d91e)
/dev/loop2 on /pup_new/initrd/pup_f type squashfs (ro,noatime,errors=continue)
/dev/loop3 on /pup_new/initrd/pup_z type squashfs (ro,noatime,errors=continue)
/dev/loop4 on /pup_new/initrd/pup_a type squashfs (ro,noatime,errors=continue)
/dev/sda7 on /pup_new/initrd/mnt/dev_save type ext4 (rw,noatime)
--------------------
SAVE_FN=/mnt/dev_save/Sessions/vpup64save-v...7_pristine
SAVE_LAYER=/pup_rw
'/pup_new/initrd/pup_rw' -> '/initrd/mnt/dev_save/Sessions/vpup64save-v...7_pristine'
'/pup_new/tmp' -> '/initrd/mnt/tmpfs/tmp'
cp: can't create '/pup_new/initrd/sbin/functions_x': File exists

Notice: the several files not found

Hope this info is useful as it explains what happens on a ISO file boot.

[TDRR]

Hey. Very nice pup! Installed the 64-bit version with LXDE and it works wonderfully. Only issue- the DEVX SFS (both versions currently out) can't be installed for some reason. "This sfs should not be loaded because it has the wrong file structure". Tried redownloading a few times but no dice.

[artemis]

Hey. Very nice pup! Installed the 64-bit version with LXDE and it works wonderfully. Only issue- the DEVX SFS (both versions currently out) can't be installed for some reason. "This sfs should not be loaded because it has the wrong file structure". Tried redownloading a few times but no dice.

i got this error if i tried to load the sfs by clicking it in the file manager. but if i went into PupControl -> Software -> SFS Load i could load it from there just fine.

[TDRR]

i got this error if i tried to load the sfs by clicking it in the file manager. but if i went into PupControl -> Software -> SFS Load i could load it from there just fine.

Yep, that worked. Thank you!
Still, might be worth looking into? Kinda unfortunate since that's pretty much the usual method for me at least.

[williams2]

In my BionicPup64, clicking an SFS file in Rox offers to mount the SFS file system,
or to install the SFS (sfs_load)

If you right click an SFS file in a Rox filer window,
you can select sfs_load in the menu.

The default action is to allow you to choose whether to mount the SFS file or whether to install the SFS as a layer in the Aufs layered file system.

[williams2]

If VoidPup uses OverlayFS for the layered file system, then
as far as I know, OverlayFS does not support adding and removing SFS files on the fly (Aufs does not need a reboot after loading or unloading an SFS layer. OverlayFS does need a reboot, but is built into the kernel. Aufs is not built into the kernel, it is a patch to the kernel source, which writes over part of the source of the kernel, and the patch needs to be modified for each kernel version, which is a lot of work by the person maintaining the aufs code.)

Which might be the answer to your question.

[peebee]

Only issue- the DEVX SFS (both versions currently out) can't be installed for some reason.

Sorry - missed this report.......

Only affects VoidPup64 (does not affect VoidPup32)

Nothing wrong with the devx - the problem is the checks in sfs_load from @mistfire

Woof-CE issue raised:
https://github.com/puppylinux-woof-CE/w ... ssues/3320

A temporary fix is to delete y on line 68 of /usr/sbin/sfs_load but this removes all symlink overwriting checks so an sfs with real /lib64 or /usr/lib64 might have nasty consequences

[peebee]

Rebuild:
4b8219fbb5f70119baefe7e855db75b4 VoidPup64-22.02+8a.iso

fixes sfs_load

[Marv]

VoidPup64 +8a bumped to +9 using the delta. md5sum correct. My standard frugal install to SSD on the 2nd gen i5 based Fujitsu S761 laptop (circa 2012). The usual drill; pristine boot set up through wifi connection (SNS and kernel supported Atheros card), then 'pristine' with the 5.19.1 kernel swapped in, then the LXDE ydrv added in, then finally my cleaned savefile added in with synaptics touchpad drivers, symlinks to portable browsers and apps etc.

Nice clean boots in all. One message in the pristine boot dmesg which goes away as soon as the 5.19.1 kernel is used:

Code: Select all

# dmesg | grep -i fail
[    4.638411] zsmalloc: module verification failed: signature and/or required key missing - tainting kernel

Excellent idle resource continues in this version and feel continues to be 'snappy' on this hardware. Libinput continues to over-ride my wish to have tapping off -thinks I have no physical buttons on this hardware though I do- but the synaptics driver package I have installed continues to function perfectly

Overall, VoidPup64 has pretty much replaced LxPupSc64 for me. In general I have fewer glitches running current chromium based browsers and generally it feels 'cleaner' at this time. Kind of surprised me but I'll take it!

Update 20 September. 2022: Kernel bumped to 5.19.10 in the install above. Clean boot and dmesg, unchanged (excellent) idle resource use. Continues to feel snappy in daily use with LXDE and my customizations on ydrv and all browsers, email, Office etc. run as portables. The synaptics driver package I use to manage the touchpad continues to work very well. Using this install as my daily with no issues seen so far.

Thanks,

[Duprate]

Hi! Back to Game. Updated to VoidPup64-22.02+9. Excellent operating system!
My modifications: As a browser, Firefox 104.0.1; Kernel 5.10.140 overlayfs.

[Marv]

Reverted to the 5.19.14 kernel from the newest 6.0 kernel. Normal boot, dmesg etc. No 'white flashing' seen on this older intel hardware using 6.0 but thanks for the heads up @peebee

[peebee]

50b666bcd5b8ec605939e1ccf209d8c0 VoidPup32-22.02+10.iso
14a7ad375af17f053db2a7fbce97fd50 VoidPup64-22.02+10.iso

see post #1

[Marv]

+9 64b install bumped to +10 on my main i5 based all intel Fujitsu S761 laptop.

First a pristine boot (adrv not used), normal boot and setup through SNS connection using the Atheros card. Kernel supported, so no fdrv required. Libinput continues to insist I use tap-to-click though I have physical buttons. It still has mediocre touchpad speed and acceleration control at best. One fail in dmesg, as in the previous boots with the 5.15.xx kernels:

# dmesg | grep -i fail
[ 4.647385] zsmalloc: module verification failed: signature and/or required key missing - tainting kernel

Then the LXDE ydrv added in, no issues noted. Then my scrubbed savefile and the most recent 5.19.14 kernel. All seems just fine in this, my full configuration. No dmesg fails, expected warnings. Good synaptics touchpad control from my reversion. All symlinked applications up and running. I'll continue to use this as my daily.

Posting from Slimjet Version 35.0.1.0 (chromium 101 based) run as a portable although some sites are now requiring chromium 105. For them I use the ungoogled-chromium portable application based on 105.

All in all seems just fine on this circa 2012 hardware.

Thanks,

[rockedge]

VoidPup64 running well on a Dell Vostro 1500 built 2008. I just boosted the RAM to 4 GiB and this old laptop is totally usable running VoidPup

[amethyst]

So does this distribution require specific Void built packages (I suppose) and how accessible and comprehensive are the available packages (again compared to ubuntu/debian packages)? Actually, I want to know if the latest Palemoon32 will work (I only see ubuntu and debian specific releases). The other browsers are normally released as official linux tarballs which I suppose will run on all the major linux systems (also Void). Is that correct. Also, apart from the package manager, does this distribution hold any performance advantages compared to ubuntu/debian based Puppys and is it generally smaller or bigger in size? Also - I suppose the system operation is similar to other Puppys I am used to? Overlay or AUFS? I have a lot of extra sfs files to be loaded/unloaded on the fly....

[rockedge]

The latest palemoon 32 bit runs well on Void based 32 bit distro's. Also easy to check the Void repos for packages here, which will run on VoidPup as well.

All of the SFS file will be loaded at boot that are in the OS's root directory. I believe the SFS-Load does work but I've been working a lot on a different Void based distro so I can not say for sure where that stands.

Overall I found many Puppy Linux applications work well on VoidPup's as well as those from the Void Linux repos. Also I have used something like xdeb to convert .deb packages to .xbps packages to install those. I was surprised how many worked out of the box that way directly from Ubuntu/Debian repos. This should also be the case with VoidPup's

[mikeslr]

amethyst, under Voidpup64 I've used your Suite's Save2SFS module to built either an adrv or ydrv of Puppy applications so as to isolate them from the general operating system. The result works well.

Boot into a pristine system first. See what it's missing. Note particularly which small Puppy Utilities aren't there. Other than that, off hand, I just recall that void does not support Qt4.

[Marv]

Back to the 6.0.1 kernel after reverting to 5.19.14 from 6.0 in my VoidPup64 frugal install on the all intel Fujitsu S761 (no adrv, ydrv with LXDE, some essential programs and my look-n-feel), synaptics touchpad drivers replacing libinput. As with 5.19.14 and 6.0 for me (no flashing video issues), clean boot and dmesg, excellent idle resource use, and 'snappy' feel. All major programs run as portables at this point.

Thanks,

Update on October 16: I just now noticed one niggle going from +9 to +10 (VoidPup64b frugal install, Fujitsu S761 all intel hardware). In +9, the shutdown dialog box to save or not save displays normally. In +10, the horizontal lines show as q's and the vertical lines show as x's. Seen with a fresh savefile from a pristine boot and in my usual savefile. Kernel independent. Box functions correctly, it is just the line display that's off. I seldom reboot other than to bump kernel or version so I didn't see it til now. Display is correct in LxPupSc64 +5 also.

[one]

[...]
Update on October 16: I just now noticed one niggle going from +9 to +10 (VoidPup64b frugal install, Fujitsu S761 all intel hardware). In +9, the shutdown dialog box to save or not save displays normally. In +10, the horizontal lines show as q's and the vertical lines show as x's. Seen with a fresh savefile from a pristine boot and in my usual savefile. Kernel independent. Box functions correctly, it is just the line display that's off. I seldom reboot other than to bump kernel or version so I didn't see it til now. Display is correct in LxPupSc64 +5 also.

The same applies to voidpup32 +10 ...

peace

[peebee]

@one @Marv

I don't see the reported problem........... Nvidia graphics here......... no "locale" changes on 1st boot - are you making any?

Screenshot171022.png (92.01 KiB) Viewed 22033 times

[Marv]

@peebee

Sorry, it isn't in the 'First Shutdown: save session box', it is only in the dialog box asking whether to save or not when a savefile previously made exists. That is after X shuts down so I couldn't easily capture it. I did run through a pristine boot with no locale change made, create a test save file on first shutdown (normal first shutdown... dialog box), then reboot and shut down again to check the save/nosave dialog box . It still shows up with q's and x's.

[peebee]

I can replicate by dropping out to terminal and running xorgwizard........

ncurses was updated on 1-Oct-2022 so there is a new version in +10

https://github.com/void-linux/void-pack ... bef06cb122
says:
ncurses: Resolve conflicts with -terminfo packages
ncurses-term provides terminfo entries only for terminals which don't
have their own -terminfo subackage now.

So this may be the cause?

https://voidlinux.org/packages/?arch=x86_64&q=terminfo

I wonder what might be needed??

Current build line is:
yes|ncurses|ncurses,ncurses-libs,ncurses-base,ncurses-term,ncurses-libtinfo-libs|exe,dev,doc,nls

[peebee]

@Marv & @one

The problem is ncurses - /usr/share/terminfo is very different in +10 from +9

The attached sfs contains the +9 terminfo

Now need to find out why this has happened.

[Marv]

@peebee Downloaded and tested. Didn't work just loading the SFS in my daily, didn't over-write the +10 info. Worked just fine directly overwriting manually, then testing, then rebooting without saving to keep my savefile '+10'.

Thanks,

[peebee]

I think
https://github.com/puppylinux-woof-CE/w ... d61019511d
is what caused the change

[Clarity]

Hi @peebee

On my test PC, a 2010 Intel Core2 DUO desktop, your most recent v10b as well as ALL of @dimkr recent VanillaPUP64s start this popping noise (attached) immediately before pristine desktop start. It continues on desktop and in console.

if I exit desktop to console, the popping continues. It will only stops if one of your apps starts a momentary audio but will restart as soon as your audio stops (example; after FirstRUN steps complete as it goes to desktop).

One of @mistfire's distros months ago had this problem but he resolved it in a subsequent release.

Any ideas of why OR how to stop this noisy popping would be most helpful.

EDIT: Took hours to find: Retrovol selection is the ONLY thing that fixed this annoyance

Retrovol2RESCUE.jpg (17.9 KiB) Viewed 21891 times