Puppy Linux Discussion Forum

VoidPup64-22.02+2.iso generated using the current delta, md5sum checked, installed to the main Fujitsu S761, first as a pristine frugal install, then adding in LXDE via @peebee ydrv, then adding in my savefile -mostly look'n'feel, symlinks to portable applications, SFS browsers, printers, synaptics touchpad driver etc. All boots and shutdowns were clean, wifi connections without problems using the Atheros AR9287 (supported by kernel, no fdrv needed), idle resource use excellent, snappy and useable. Some fails in dmesg, no warnings of note there.

pristine boot:

# dmesg | grep -i fail
[    9.612194] zsmalloc: module verification failed: signature and/or required key missing - tainting kernel
[   14.906628] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   14.906635] cfg80211: failed to load regulatory.db
 
add in ydrv:

# dmesg | grep -i fail
[    6.783996] zsmalloc: module verification failed: signature and/or required key missing - tainting kernel
[   12.182172] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   12.182179] cfg80211: failed to load regulatory.db
 
add in my savefile:

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

switch to ozsouth 5.15.27 kernel:

# dmesg | grep -i fail
# 

Since my rendering bug is vanquished, the frog-with-bug yields to my current pup.

Cheers,

Thanks again, peebee, for your great work.

Upgraded from VoidPup64 VoidPup64-22.02+0 to VoidPup64-22.02+2 without any problems. All the applications I had for VoidPup64-22.02+0 function under VoidPup64-22.02+2 and this despite that some are in a Save Folder* and others (created for Puppys and thus having libraries not available from void's repos) had been placed in a ydrv.sfs.

-=-=--
* To a large extent, these applications are just menu-entries with associated files creating links to portables and AppImages.

Marv wrote: ↑Fri Mar 18, 2022 11:07 pm

[ 14.906628] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 14.906635] cfg80211: failed to load regulatory.db

Thanks - will fix in next update - it's in the wrong place - /usr/lib/firmware - should be /lib/firmware

@peebee You might want to switch away from the ancient xdg_puppy_jwm .pet to the woof-CE version, which has fixes for bugs that plague Puppy for years (https://github.com/puppylinux-woof-CE/w ... -puppy-jwm). To do this, you'll need to remove the gnome-menus and xdg_puppy_jwm packages, and add xdg-puppy-jwm to PETBUILDS.

The new xdg-puppy-jwm removes extra separators like the separator at the top of the Multimedia menu and protects against duplicate menu entries when installing packages that match more than one category. Also, it make menus entries for console applications like htop and Midnight Commander (where Terminal=true) work without the manual intervention of adding Exec=urxvt -e ....

It works very very very well with Debian and Ubuntu packages, and the menu always looks sane and doesn't have broken menu entries after apt install, without having to "puppify" the .desktop files. It will work with VPM as well.

(The fixmenusd petbuild complements the improved menu generator, by automatically running fixmenus when a .desktop file is added, modified or deleted, and automatically setting problematic applications to run as spot - I think it could be a nice addition to VoidPup)

(And I see you're using old .pet packages for the tray applets ... if you run forkstat you'll see that the old firewall status tray icon runs iptables every 2 seconds, instead of updating only when rc.firewall runs: this is a huge waste of CPU time - the updated firewallstatus built by the petbuild is much more efficient)

resolved

Deltas from +2 to +2+ to add the improvements suggested by @dimkr - thanks

https://smokey01.com/peebee/downloads/t ... .iso.delta
https://smokey01.com/peebee/downloads/t ... .iso.delta

Will also be in the next update.

@Marv

7a8dea3e111f82da62ceb832058e0296 VoidPup32-22.02+2+.iso
278b634e6fcd21336cdf36ed0248c411 VoidPup64-22.02+2+.iso

Not the best test mule here as I run VoidPup64 with the LXDE ydrv but 22.02 +2 bumped to 22.02 +2+ in my standard install. Boot etc clean, update to firewallstatus noted, no issues at all seen otherwise in light daily use,

Thanks,

f9659ec417b8d8c084a5e93b9f0b2fea VoidPup32-22.02+3.iso
956fdd8d60b3770af893e44a0de01076 VoidPup64-22.02+3.iso

see viewtopic.php?t=5270

Hi! Updated to VoidPup64-22.02+3.iso.
In addition to the smooth operation, I received an extra bonus:
Terminal transparency did not work in previous versions. To my surprise, it now works normally!
It's not essential, but it gives an air of modernity.... Congratulations Peebee!

Note: One way of working with transparency in previous versions was to change the background in the "wallpaper Setter". After that, it worked.

ydrvs for LXDE and Xfce4 desktops are now available for both VoidPup32 and VoidPup64

n.b. the Xfce4 ydrvs bump glibc to version 2.33

About a day on +3 in my normal 64b install, Ydrv LXDE, synaptics touchpad driver, browsers run-as-spot -Slimjet from SFS, ungoogled-chromium as a portable- . The usual all intel Fujitsu S761s and S762s. No issues seen on boot, shutdown with savefile save, idle resource use, or dmesg check. Light daily use of browsers, Sylpheed, file unpacking and squashing, PDF printing. Both the stock kernel and @ozsouth 5.15.30 run, both good. As @mikewalsh would say, "like oiled silk".

Thanks,

VoidPup32 22.02+3
I believe the script /usr/bin/inst-xbps still needs at line 41
mkdir -p $INDEXDIR
Otherwise there is an error because /var/cache/xbps directory does not exist

Hi Peebee! Using and testing VoidPup64-22.02+3 + devx. I tried to compile the 5.17.1 kernel but was unsuccessful due to error messages in the terminal. It was the first time using VoidPup to compile and it was a test to verify functionality.
Later, I did the same using VanillaDpup64 and the compilation occurred normally. Weekly, I download the newest 5.10.x kernel tarball (Kernel.org) and make my compilation.

OscarTalks wrote: ↑Sun Mar 27, 2022 3:49 pm

VoidPup32 22.02+3
I believe the script /usr/bin/inst-xbps still needs at line 41
mkdir -p $INDEXDIR
Otherwise there is an error because /var/cache/xbps directory does not exist

Sorry OT - I didn't get a notification of this post by email so missed it till now - will add the mkdir to the next release.

Duprate wrote: ↑Sun Apr 03, 2022 12:17 am

Hi Peebee! Using and testing VoidPup64-22.02+3 + devx. I tried to compile the 5.17.1 kernel but was unsuccessful due to error messages in the terminal. It was the first time using VoidPup to compile and it was a test to verify functionality.
Later, I did the same using VanillaDpup64 and the compilation occurred normally. Weekly, I download the newest 5.10.x kernel tarball (Kernel.org) and make my compilation.

Hi @Duprate
Please try:
ln -sfv ../../lib/libc.so.6 /usr/lib/libc.so.6

Thanks
p.s. I hate 64-bit incompatible and not-standardised lib structures!!!

VoidPup32-22-02+3 with devx loaded
I am seeing some errors relating to version mismatch between perl executable and perl modules (libraries).

Perl lib version (5.34.1) doesn't match executable '/usr/bin/perl' version (5.34.0) at /usr/lib/perl5/core_perl/Config.pm

"vpm i perl" does fix it

Duprate wrote: ↑Wed Feb 02, 2022 1:15 am

Thanks! Just curious... Vivaldi works fine on VoidPup64 and is way better and safer than its "rich cousin"...

Not quite certain how you ascertained that vivaldi is safer than chrome.?..all of vivaldi's security comes from google whether they like it or not

It is merely a react javascript application placed on top of chromium and it uses google safe browsing and the chromium sandboxing so it will be on par with chromium.

Don't get me wrong it is a nice browser in terms of customisation which incidentally they have achieved by baking in extensions into the browser but this presents the future problem of feature creep.

Hi! Nothing is safe on the internet! Our behavior is that it has to be as safe as possible! I'm not using Vivaldi now I'm using Google Chrome provided by "Peebee". The reason I use Chrome: It is the only browser, besides Vivaldi, that is translating the pages of this forum from English to Portuguese, quickly and without complications.

With some customizations....

@Duprate
Wonderful looking desktop good sir.

Justice be done! I had stopped using Firefox to translate forum pages, because of a bug in the "To Google Translate" extension. However, now using Firefox, in version 99.0.1 and with the "To Google Translate" extension updated and corrected, the translation of the forum pages was "papaya with sugar". Goodbye Google Chrome! Back in the game with Firefox!

Thanks to your "Xenial" post, I got the idea to retest Firefox, thanks!

Duprate wrote: ↑Mon Apr 25, 2022 12:15 am

Justice be done! I had stopped using Firefox to translate forum pages, because of a bug in the "To Google Translate" extension. However, now using Firefox, in version 99.0.1 and with the "To Google Translate" extension updated and corrected, the translation of the forum pages was "papaya with sugar". Goodbye Google Chrome! Back in the game with Firefox!

Thanks to your "Xenial" post, I got the idea to retest Firefox, thanks!

The Simple Translate add-on is also functional. Like 'google-translate' it is 'recommended'. It's also available for firefox-esr. It uses 'google-translate' but enables both full-page or selected text translation. Not sure plain 'google-translate' offers both.

Thanks, Duprate for encouraging me to revisit translation using firefox.

Hey!

After the clean installation of VoidPup64, I did not manage to install a browser using the Gert Web Browser. I tried to use the VoidPup App Installer menu item. But when you press the Web Browsers button, nothing happens. Then I completed commands in the terminal

vpm sync

vpm up

Then he repeated the steps described at the beginning of this post. Did not work out. I had to download web_browser.sfs manually. It's not so convenient

From Dmitry (Russia)

Please tell me what ways can Zoom use in VoidPup? I tried through the Zoom application in the Chrome browser, but the sound does not work in it. Portable version of Zoom Mike does not work for me either

From Dmitry (Russia)

af75681bfc13809e72d688fe966f31b6 VoidPup32-22.02+4.iso
4df856e552dff369a0b473341070b371 VoidPup64-22.02+4.iso

see viewtopic.php?t=5270

Just to report that the upgrade to VoidPup64-22.02+4.iso went easily and without a hitch even despite my use of a 'peculiar' ydrv.sfs explained in previous posts. Thanks, again peebee.

Another ydrv pup checking in. The update to +4 in VoidPup64 went smoothly here also. All settings and my synaptics touchpad driver reversion survived. The usual i5 based all intil laptops. VoidPup64 has become my daily.

Thanks,

i tried to load the 64bit VoidPup64-22.02+4.iso on my thinkpad x220 with isoloader. i got into the grub menu for voidpup but when it tries to boot it says it loads the kernel and then freezes after it says its trying to load the initrd file. doesn't do anything.

so i tried to dd the iso directly onto my flash drive instead and that just booted into my normal fossapup install. idk what's going on with it

Hello @artemis

"puppy_vpup sfs.... Done" message remains on-screen for a long time if booting from USBs. But, after RAM loading is completed, the boot process does continue on to desktop. On my system booting the ISO file from SG2D and merely hitting the enter key upon VoidPUP64's Menu it proceeds to the 1st message, ... waits awhile ..., and continues to desktop with ALL normal boot messages posted during the progression. For me, this took approx 2 minutes. Upon desktop the system is responsive and fast! And session persistence work to our satisfaction.

My ISO file boot yields:

Voidrup64 22.02 Linux 5.15.24 1x86_641 ***
Waiting 5 seconds for slow storage devices......
Loading the 'puppy_vpup64_22.02.sfs' main file... copying to ram	done
Loading the fdru_upup64_22.02.sfs' fdru file... copying to ram	done
Loading the 'zdru_upup64_22.02.sfs' zdru file... copying to ram	done
Loading the 'adru_upup64_22.02.sfs' adru file... copying to ram	done
Performing a 'switch_root' to the layered filesystem...
Making the filesystem usable...
Loading swap partition /dev/sda4 (8.06)...
Updating... gtk-icon-cache_

Then on to desktop

.
Question
Before you copied contents to system disk, did you wait as some messages (success or boot failure) should have resulted from your ISO file boot attempts?

@Clarity I never get to the stage of loading sfs files. the boot freezes immediately after initramfs. see pictures.

and yeah i did wait for files to write when making the boot stick, ran sync, ejected properly and all that. that bit has all the right files on it i double checked today

@artemis
Can you boot/run other puppies?