VoidPup32 and VoidPup64 Discussion

[Clarity]

Just tested VoidPUP64 in a KVM. All seems well in operations..."findsmb" utility present, as well. THANKS, as this update operates without issue, thus far.

Samba-VoidPUP.jpg (38.71 KiB) Viewed 5877 times

Samba-VoidPUP2.jpg (32.95 KiB) Viewed 5877 times

[Clarity]

Added LibreOffice, Celluloid and

Added terminal needs

VoidPUP-add.jpg (4.39 KiB) Viewed 5870 times

[peebee]

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

[Clarity]

Hello @peebee

This is a report

• Your 64bit ISO files, including VoidPUP64 boot to desktop via OOTB Ventoy.

• The Ventoy OOTB USB's filesystem which contain the ISO files is an exFAT partition

• This poses no problem in the WoofCE PUPs ability to get to their desktop

• BUT, each distro, I've tested today do NOT have exFAT ability and without it we cant use the OS to add other forum ISO files including updated ISOs that you periodically post on GITHUB. And GParted doesn't have the ability to interrogate or format the partition.

This is not just a Ventoy things as all of my new USB V3 sticks over the past couple years come pre-formatted from the manufacturers as exFAT. (I know you already know this).

This missing filesystem is probably an oversight. Is there any chance this could be corrected for future PUPs from you or WoofCE?

Thanks for any understanding

[peebee]

This missing filesystem is probably an oversight. Is there any chance this could be corrected for future PUPs from you or WoofCE?

Please try:
vpm i exfatprogs

and tell me if that fixes. and if any other dependencies are installed?

[Clarity]

Hello @peebee

This is a report

This report is flawed as the issue has absolutely NOTHING to do with the exFAT support. The report was based upon a symtomatic observation. Further detail surfaces an issue with WoofCE distro operation as it is found in several other ISOs, too.

A much more accurate description of this issue is reported here on the F96CE thread.

@peebee your command allow me to dig deeper to understand the behavior where the distro at desktop will not allow use of the USB. My observation was based upon the past when PUPs were unable to use any exFAT. I made the assumption it was missing since the external symptom was the same.

I am sure development, knowing this understands "why". The report on the F96 thread is as far as I can go in my limited ability.

[Marv]

Updated my VoidPup64-22.02-230701 install to VoidPup64-22.02-231111 on the usual 2nd generation i5 based Fujitsu S761. The install is frugal to SSD and uses ydrv based LXDE and PCManFM as previously. No issues noted in a couple of days daily use, Nothing of note checking dmesg and idle resource use and glxgears FPS continue to be excellent.

A double header and bonus. Tested @peebees' 6.6.1-lxpup64 (x86_64) kernel in the updated VoidPup (and also in LxPupSc64 23.01 +4-T and BW64 10.0.3 -usrmerge structure adjusted-).

In VoidPup64 since the first CE version running on the hardware above I have carried a line in the ACPI suspend script to restart the PWF wifi on resume. No longer necessary with the 6.6.1 kernel, the stock lidsuspend works completely and correctly. Good.

In BW64 10.0.3, compared to the stock kernel on this hardware, 6.6.1 doesn't require restarting connman on resume whereas the stock kernel does. Resource use, dmesg checks, normal use all ok. Good.

Operation in LxPupSc64 continues rock solid and normal with this kernel bump. There I have been steadily testing and using @peebee kernels as released with 6.6.0 being the most recent.

Not tested in the ydrv'd install of @ozsouths' fossapup64-9.5-23, an update of his fossapup64-9.5-less-1. That one's a toaster, perfect toast every time, so no need.

Thanks,

[mikeslr]

Marv "In BW64 10.0.3, compared to the stock kernel on this hardware, 6.6.1 doesn't require restarting connman on resume whereas the stock kernel does. Resource use, dmesg checks, normal use all ok. Good."
Thanks for the report. May not be related to the problems I've had with wifi under BW64 --frequent loss of connection-- but trying peebee's 6.6.1-lxpup64 (x86_64) kernel is worth the effort.

[one]

Hi @peebee,

there is a problem with the mime-handling of *.iso files in voidpup64 (and also s15pup64 voidpup32).

A *.iso file, when seen in ROX-Filer, should display with it's mime-type icon, and (left-)clicking on it should open it with filemnt, so the iso is mounted and you can inspect/copy/whatever the containing files (or right-click on it, there should be the offer to open it with filemnt, pupmd5sum should be offered etc).

peace

PS: screenshot attached ...

[Marv]

Marv "In BW64 10.0.3, compared to the stock kernel on this hardware, 6.6.1 doesn't require restarting connman on resume whereas the stock kernel does. Resource use, dmesg checks, normal use all ok. Good."
Thanks for the report. May not be related to the problems I've had with wifi under BW64 --frequent loss of connection-- but trying peebee's 6.6.1-lxpup64 (x86_64) kernel is worth the effort.

Careful to adjust the zdrv structure to usrmerge if you do.

[peebee]

there is a problem with the mime-handling of *.iso files in voidpup64

S15Pup is OK....

VoidPup the mime type has changed from application/x-cd-image to application/vnd.efi.iso presumably from a change in Void Linux - and this "new" type is not recognised by Puppy.

[peebee]

VoidPup version 231118 is available to fix the mime problems........

https://sourceforge.net/projects/pb-gh- ... 2_release/
https://sourceforge.net/projects/pb-gh- ... 4_release/

[one]

Hi @peebee,

the latest releases of voidpup (both 32 and 64 bit) give me problems with internet connection. I use enp2s0 (eth0).
Nearly all of my personal bookmarks don't resolve correct and end with "server not found" message, so ....
(strangely enough, some links are accessible - the guardian's homepage, politico.com and some others work!?)

The last fully working release for me was 231118 - so I reverted to that.
I notice that dhcpcd has changed from 10.0.4 to 10.0.5 - so maybe that is the culprit?

peace

[peebee]

Hi @peebee,

the latest releases of voidpup (both 32 and 64 bit) give me problems with internet connection. I use enp2s0 (eth0).
Nearly all of my personal bookmarks don't resolve correct and end with "server not found" message, so ....
(strangely enough, some links are accessible - the guardian's homepage, politico.com and some others work!?)

The last fully working release for me was 231118 - so I reverted to that.
I notice that dhcpcd has changed from 10.0.4 to 10.0.5 - so maybe that is the culprit?

peace

231221 version?

Which connection manager?

There was a problem with dhcpcd-10.0.4 and frisbee but that should have been fixed by 10.0.5

[one]

Yes - 231221 (edit: and 231209.

Ethernet is automatically active (normally) - so can't tell for sure which connection manager is used.

Dec 26 15:08:15 puppypc19586 daemon.err dhcpcd[6462]: dhcpcd_fork_cb: Connection reset by peer
Dec 26 15:08:16 puppypc19586 daemon.info dhcpcd[6462]: dhcpcd exited
Dec 26 15:08:16 puppypc19586 daemon.err dhcpcd: enp2s0 [ip4] [ip6][6462]: main: write: Bad file descriptor

I think I tried all (networkmanagers) after discovering the problem.

peace

[peebee]

Ah - the problem was with 10.0.5 - has been fixed in 10.0.6........

You could try running dhcpcd in a terminal - that works for wifi - I don't have an ethernet connection to test.

Otherwise you could try reverting to 10.0.4

or try 10.0.6 from Slackware Current e.g.:
https://slackware.uk/slackware/slackwar ... 6_64-1.txz

[one]

Thanks @peebee,

so the next releases will have dhcpcd 10.0.6?

What would be the preferred method in "reverting back to 10.0.4?

I am currently in voidpup32_231221 and did this:

# vpm info dhcpcd
[vpm] (xbps-query -v -R dhcpcd):
architecture: i686
build-options: _privsep
changelog: https://github.com/NetworkConfiguration/dhcpcd/releases
conf_files:
/etc/dhcpcd.conf
filename-sha256: b6776121a375288c5cc24d34b74f340a8902245d8ccd12112caf8dcc99f30912
filename-size: 202KB
homepage: https://roy.marples.name/projects/dhcpcd
installed_size: 464KB
license: BSD-2-Clause
maintainer: Orphaned orphan@voidlinux.org
pkgname: dhcpcd
pkgver: dhcpcd-10.0.2_1
repository: https://repo-default.voidlinux.org/current
run_depends:
eudev-libudev>=1.6_1
glibc>=2.36_1
shlib-requires:
libc.so.6
libudev.so.1
short_desc: RFC2131 compliant DHCP client
source-revisions: dhcpcd:bed27343ed
[vpm] Execution finished (xbps-query -v -R dhcpcd), return code was: 0

dhcpcd --version

dhcpcd 10.0.5
Copyright (c) 2006-2023 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH

vpm i dhcpcd

[vpm] Installing packages: dhcpcd (xbps-install -S dhcpcd) ...
[*] Updating repository `https://repo-default.voidlinux.org/curr ... 6-repodata' ...
i686-repodata: 1844KB [avg rate: 2274KB/s]

Name Action Version New version Download size
dhcpcd update 9.4.0_1 10.0.5_1 203KB

Size to download: 204KB
Size required on disk: 464KB
Space available on disk: 9050MB

Do you want to continue? [Y/n]

[*] Downloading packages
dhcpcd-10.0.5_1.i686.xbps.sig2: 512B [avg rate: 29MB/s]
dhcpcd-10.0.5_1.i686.xbps: 203KB [avg rate: 3009MB/s]
dhcpcd-10.0.5_1: verifying RSA signature...

[*] Collecting package files
dhcpcd-10.0.5_1: collecting files...

[*] Unpacking packages
dhcpcd-9.4.0_1: updating to 10.0.5_1 ...
dhcpcd-10.0.5_1: unpacking ...
File ./etc/dhcpcd.conf' exists, installing configuration file to./etc/dhcpcd.conf.new-10.0.5_1'.

[*] Configuring unpacked packages
dhcpcd-10.0.5_1: configuring ...
Created _dhcpcd system group.
Created _dhcpcd system user.
dhcpcd-10.0.5_1: updated successfully.

1 downloaded, 0 installed, 1 updated, 1 configured, 0 removed.
[vpm] [xbps-install -S dhcpcd] return code: 0

I am a bit confused by the different versions but that seems to help also - at least my requested sites are accessible.
I will now shut down the system and see if it works after a restart (changes saved or not).

edit: yes, changes stick ...

Anyway: would you please explain how to roll back to version 10.0.4?

peace

[Clarity]

Hi @peebee

Just booted VoidPup64 v1223 ISO file via SG2D

Problem to report: Pristine boot, FirstRUN complete, network operational. Next step: Open a terminal and entered vpm update ... Segfault during update.

Hope this helps

[peebee]

Major Void infrastructure changes mean that all older VoidPup's are broken - do not run vpm update!

Resolution may take some time .....

231231: new .iso's now uploaded

[Clarity]

Thanks @peebee
Testing SG2D booted ISO file v231231

Code: Select all

# vpm update
     o
     o
     o
mesa-23.3.2_1: configuring ...
mesa-23.3.2_1: updated successfully.
mesa-dri-23.3.2_1: configuring ...
mesa-dri-23.3.2_1: updated successfully.

57 downloaded, 48 installed, 9 updated, 57 configured, 0 removed.
[vpm]  [xbps-install -Suv] return code: 0 
# 
# vpm i vlc
     o
     o
     o
vlc-3.0.20_1: configuring ...
Updating GTK+ icon cache for /usr/share/icons/hicolor...
Updating MIME database...
Error in file "usr/share/applications/pmediainfo.desktop": "application_vnd.ms-asf" is an invalid MIME type ("application_vnd.ms-asf" does not contain a subtype)
Warning in file "usr/share/applications/xarchive.desktop": usage of MIME type "multipart/x-zip" is discouraged ("multipart" is a media type that probably does not make sense in this context)
Rebuilding VLC plugins cache file...
vlc-3.0.20_1: installed successfully.

27 downloaded, 27 installed, 0 updated, 27 configured, 0 removed.
[vpm]  [xbps-install -S vlc] return code: 0 
# 

Session saved upon shutdown as expected and defined by SAVESPEC. ISO file reboot finds its saved-session upon default menu reboot.

Problem:
Used Menu>Setup>VoidPUP App Install to add several packages to the system from that list. Celluloid is one of them. Started from the lxterminal I get this:

Code: Select all

# celluloid 
celluloid: error while loading shared libraries: libdb-5.3.so: cannot open shared object file: No such file or directory

In fact this, gnome-mplayer, and VLC will NOT start from the root user Menu>Multimedia selections.

---

Additional note
Also, SAMBA and its utils seem fine!

[peebee]

240112
Another significant update due Void changes - recommended to update VoidPup

https://sourceforge.net/projects/pb-gh-releases/files/

[Marv]

64b 231118 install updated to 240112 on the Fujitsu S761 laptop. Pretty standard frugal install to SSD using a smallish (256MB) savefile and an LXDE/PCManFM ydrv. Looks fine, dmesg, idle resource use etc all OK, CDs play well using pmusic, No video player installed here so DVDs not checked. Portable browsers (Brave, Slimjet, un-googled chromium) start and run correctly as does the portable Sylpheed accessing gmail via imap4. Your 6.6.8 kernel with AUFS patches swapped in and running well. I have had no issues in fairly extended daily use of that kernel in LxPupSc64, fossapup23, fossapup64-less, and Bookworm64 10.0.4. Am I just a lucky rascal or do the 6.6.4 AUFS patches work in that for others?

Thanks,

[peebee]

240202
More significant updates due Void changes - recommended to update VoidPup

https://sourceforge.net/projects/pb-gh-releases/files/

[Marv]

Update to 240202 went smoothly. My frugal install to SSD with a small savefile continues to run well but VPM or xbps are being quite troublesome for me. xbps and repo updated as requested but trying to install either MPV or gnome-mplayer for a user fails with them being found in repo but then with a dependency circle involving libharfbuzz. I've tried searching for libharfbuzz.so.73 and it exists in the repo but an install fails due to a libicuuc problem. Trying to update that library also fails as it isn't found in repo. Sort of typical failure is:

Code: Select all

[vpm]  Installing packages: mpv (xbps-install -S mpv) ... 
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
libharfbuzz-8.3.0_1 in transaction breaks installed pkg `harfbuzz-3.2.0_1'
Transaction aborted due to unresolved dependencies.
[vpm]  [xbps-install -S mpv] return code: 19 

Any thoughts? I'm not terribly proficient with these installers but they have worked for me in the past.

[peebee]

Any thoughts? I'm not terribly proficient with these installers but they have worked for me in the past.

Hi @Marv

Tried on a pristine frugal install of VoidPup64 and mpv installed (had to do "vpm fi libdb" but that's something I need to sort)....

Perhaps there's something in your savefile or in something else you're loading??

Code: Select all

# vpm i mpv
[vpm]  Installing packages: mpv (xbps-install -S mpv) ... 
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
58 packages will be downloaded:

58 packages will be installed:
  libass-0.17.1_1 celt-0.11.3_3 lame-3.100_2 libaom-3.7.1_1 
  libva-2.20.0_1 libvdpau-1.5_1 ocl-icd-2.3.2_2 libavutil-4.4.4_6 
  libdav1d-1.3.0_1 libspeex-1.2.1_1 libsvt-av1-1.7.0_1 
  libswresample-4.4.4_6 xvidcore-1.3.7_1 libavcodec-4.4.4_6 
  libdecor-0.1.1_1 libasyncns-0.8_9 libgomp-13.2.0_2 libfftw-3.3.10_2 
  libjack-1.9.22_1 libsoxr-0.1.3_2 libtdb-1.4.9_2 sbc-2.0_1 
  speexdsp-1.2.1_1 webrtc-audio-processing-0.3.1_1 libpulseaudio-16.1_1 
  SDL2-2.28.5_3 libmodplug-0.8.9.0_1 mbedtls-2.16.12_1 
  librist-0.2.7_1 librtmp-2.4.20161210_10 libsrt-1.5.3_1 
  libavformat-4.4.4_6 libavresample-4.4.4_6 libbs2b-3.1.0_3 
  libpostproc-4.4.4_6 libswscale-4.4.4_6 libvidstab-1.1.0_2 
  vmaf-2.3.1_1 libavfilter-4.4.4_6 v4l-utils-1.24.1_1 
  libavdevice-4.4.4_6 libbluray-1.3.4_1 gstreamer1-1.22.9_1 
  libcanberra-0.30_12 libserd-0.30.16_1 libsord-0.16.14_1 
  sratom-0.6.14_1 liblilv-0.24.12_4 libmysofa-1.3.1_1 
  libpipewire-1.0.3_1 glslang-11.11.0_1 shaderc-2022.2_1 
  libplacebo-5.264.1_1 libvamp-plugin-sdk-2.10.0_1 librubberband-3.3.0_1 
  lua52-5.2.4_12 uchardet-0.0.8_1 mpv-0.36.0_4 

Size to download:               32MB
Size required on disk:          99MB
Space available on disk:      3955MB

Do you want to continue? [Y/n] 

# mpv
mpv 0.36.0 Copyright © 2000-2023 mpv/MPlayer/mplayer2 projects
 built on Tue Nov 14 08:04:25 2023
libplacebo version: v5.264.1
FFmpeg version: 4.4.4
FFmpeg library versions:
   libavutil       56.70.100
   libavcodec      58.134.100
   libavformat     58.76.100
   libswscale      5.9.100
   libavfilter     7.110.100
   libswresample   3.9.100

Usage:   mpv [options] [url|path/]filename

[Marv]

@peebee, Thanks, got it back on track.

The VPM install worked in a pristine, in a pristine plus your LXDE ydrv of 07/06/2023 16:28, and in a pristine plus my ydrv (yours plus PWF, HPLIP, lx_right_clicks-0.7, desktop_drive_icons_x86_64-0.0.5, peasyscan-2.13, panel setup, symlinks and .desktops to portables etc.)

It failed using a savefile that dated back prior to the last two major Void upheavals but only really had my synaptics driver package and a bit of look'n'feel added. There was a fair amount of xbps stuff in there, probably the cause.

Fresh savefile started using your ydrv and putting my adds above (rechecked the library structure in my synaptics pet) in the savefile.

MPV then installs OK using vpm i mpv, vpm fi libdb is required for it (or pmusic) to run.

Once that is done and the default applications set (I use mpv --player-operation-mode=pseudo-gui for mediaplayer, pmusic -B for Audio Player, and pmusic_CD for CD Player) and auto-launch 'handler' enabled in Puppy Event Manager, it's ready for userland again.

[Clarity]

Hello @peebee

@BarryK has "PKGget" for use of his Void adaptation. Is that package manager applicable to this WoofCE PUP?

Curious

[peebee]

@BarryK has "PKGget" for use of his Void adaptation. Is that package manager applicable to this WoofCE PUP?

A different approach as I understand it - and only 64-bits..... unlikely to be applicable to VoidPup

[Marv]

Updated my 03 Feb VoidPup64 install (see 2 posts above) using the 240202 build to the 240208 build. All system checks good, no issues seen in a days normal use. Posting from it now using the current Brave portable. Too many good pups in the kennel right now! How to choose

Thanks,

Update: An update from the 240208 build to the 240223 build went smoothly. The savefile for the install was relatively fresh, only dating back to the 240202 install, scrubbed as usual pre-update. No issues noted, booted and run sucessfully both with the included 5.15.148 kernel and with @peebees' 6.6.17 kernel.

[jrb]

Hi @peebee, just thought I'd let you know how much I'm enjoying the VoidPups. Nicely done.

I played with the stock versions for a while and then downloaded woof-CE-2024-03-14 and started building. Once I had figured I needed the xml2 package using BookwormPup64 for the first successful build everything went very smoothly.

There is an issue that has come up however, I use a portable FireFox as my main browser and there was no sound. Perhaps if I had installed Voids version of Firefox it would have caught the problem. Turns out that Firefox now requires pulseaudio. So, after installing pulseaudio-16.1_2.x86_64.xbps and libpulseaudio-16.1_2.x86_64.xbps and changing the default audio blocking in Firefox the sound worked.

Then I opened deadbeef (the Void package), my preferred audioplayer, and..no sound. Once you install pulseaudio, deadbeef needs the alsa-plugins-pulseaudio-1.2.7.1_2.x86_64.xbps package. With that everything is good to go.

I'm using an ffmpeg-deadbeef-mpv.sfs package for my ydrv. Works quite nicely. I know you included an ffmpeg.pet in your latest build but I prefer to use Voids package so I don't have to worry about dep conflicts in my future builds. Have also built packages for gnome-mplayer and vlc. They work well too.

I built an SFS building installer script accessible on the Setup menu. See attached.

Thanks for all your hard work. Cheers, J