Vanilla Dpup 9.2.0 Preview

[dimkr]

A preview build of 9.2.0 is uploaded to https://github.com/vanilla-dpup/release ... -preview16 (x86_64) and https://github.com/vanilla-dpup/release ... -preview16 (x86).

9.2.0 will combine the features in 9.1.x with the form factor of 9.0.x:

• Traditional ISO image with initrd.gz

• Nearly identical x86_64 and x86 builds (the x86 build uses GTK+ 3 and ConnMan, too)

• overlay instead of aufs

• Built-in support for apt and out-of-tree drivers via DKMS; no need for devx (just apt install gcc, etc')

• X.Org (no Xwayland) and GTK+ 3 everywhere, with 5 themes that support both GTK+ 2 and GTK+ 3

• Good selection of built-in fonts, including emoji support

9.2.0.png (68.53 KiB) Viewed 4677 times

Feedback is welcome and appreciated.

[radky]

@dimkr,

Testing Vanilla Dpup 9.2.0 Preview on a legacy Toshiba laptop, Pentium Dual-Core CPU T4400 @ 2.20GHz with 3GB RAM.

Boots without difficulty to desktop and modesetting video driver.
Initial thoughts: smooth and responsive on this old Toshiba laptop.

I did notice powerapplet_tray displays the status of my Logitech wireless mouse battery (hidpp_battery_0), rather than the laptop battery (BAT0).

capacity_level: Normal
manufacturer: Logitech
model_name: Wireless Mouse M325
online: 1
scope: Device
serial_number: 400a-b3-83-6c-53
status: Discharging
type: Battery

/sys/class/power_supply/hidpp_battery_0/uevent

POWER_SUPPLY_NAME=hidpp_battery_0
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_SCOPE=Device
POWER_SUPPLY_MODEL_NAME=Wireless Mouse M325
POWER_SUPPLY_MANUFACTURER=Logitech
POWER_SUPPLY_SERIAL_NUMBER=400a-b3-83-6c-53
POWER_SUPPLY_CAPACITY_LEVEL=Normal

---

/sys/class/power_supply/BAT0/uevent

POWER_SUPPLY_NAME=BAT0
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_STATUS=Full
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=10800000
POWER_SUPPLY_VOLTAGE_NOW=10800000
POWER_SUPPLY_POWER_NOW=0
POWER_SUPPLY_ENERGY_FULL_DESIGN=43200000
POWER_SUPPLY_ENERGY_FULL=13964000
POWER_SUPPLY_ENERGY_NOW=13964000
POWER_SUPPLY_CAPACITY=100
POWER_SUPPLY_CAPACITY_LEVEL=Full
POWER_SUPPLY_MODEL_NAME=PA3534U-1BRS
POWER_SUPPLY_MANUFACTURER=
POWER_SUPPLY_SERIAL_NUMBER=01D9

[dimkr]

I did notice powerapplet_tray displays the status of my Logitech wireless mouse battery (hidpp_battery_0), rather than the laptop battery (BAT0).

Wow, this is a super old bug that affects any Puppy. Can you share the output of ls -l /sys/class/power_supply/hidpp_battery_0/?

EDIT: uploaded preview2, it's preview1 plus https://github.com/puppylinux-woof-CE/woof-CE/pull/3100

[bigpup]

Just a suggestion.

This is the stages of software or a operating system release.
viewtopic.php?t=3683

These terms are understood and accepted as the way to identify software development.

I find it helpful to understand what I am downloading, using, and what to expect it to do.

This also tells me if you may need some help.
Example:
Alpha stage release.
This person needs some help identifying any bugs or issues.
Beta stage release.
Start looking for any little stuff that still needs fixing.
See if earlier reported issues are actually fixed.

Identifying as a preview version.
OK.
But what should I expect to find?
A fully working operating system?
A lot of bugs?
No bugs or if any, not important to bother with?
Is testing needed?
Is everything just going to work?
???

[radky]

Wow, this is a super old bug that affects any Puppy. Can you share the output of ls -l /sys/class/power_supply/hidpp_battery_0/?

EDIT: uploaded preview2, it's preview1 plus https://github.com/puppylinux-woof-CE/woof-CE/pull/3100

@dimkr

Testing: vanilladpup-x86_64-9.2.0-preview2

With your fix in preview2, powerapplet_tray works great now on my old Toshiba laptop.

Thanks for the quick response !

alarm: 0
capacity: 100
capacity_level: Full
cycle_count: 0
energy_full: 13964000
energy_full_design: 43200000
energy_now: 13964000
manufacturer:
model_name: PA3534U-1BRS
power_now: 0
present: 1
serial_number: 01D9
status: Full
technology: Li-ion
type: Battery
voltage_min_design: 10800000
voltage_now: 10800000

---

In case you still need it, here is the requested information:

WIRELESS MOUSE BATTERY:

ls -l /sys/class/power_supply/hidpp_battery_0/
total 0
-r--r--r-- 1 root root 4096 May 20 09:14 capacity_level
lrwxrwxrwx 1 root root 0 May 20 09:12 device -> ../../../0003:046D:400A.0004
drwxr-xr-x 3 root root 0 May 20 09:12 hwmon1
-r--r--r-- 1 root root 4096 May 20 09:14 manufacturer
-r--r--r-- 1 root root 4096 May 20 09:14 model_name
-r--r--r-- 1 root root 4096 May 20 09:14 online
drwxr-xr-x 2 root root 0 May 20 09:14 power
lrwxrwxrwx 1 root root 0 May 20 09:14 powers -> ../../../0003:046D:400A.0004
-r--r--r-- 1 root root 4096 May 20 09:14 scope
-r--r--r-- 1 root root 4096 May 20 09:14 serial_number
-r--r--r-- 1 root root 4096 May 20 09:14 status
lrwxrwxrwx 1 root root 0 May 20 09:12 subsystem -> ../../../../../../../../../../class/power_supply
-r--r--r-- 1 root root 4096 May 20 09:14 type
-rw-r--r-- 1 root root 4096 May 20 09:12 uevent
drwxr-xr-x 2 root root 0 May 20 09:12 wakeup31

SYSTEM BATTERY:

ls -l /sys/class/power_supply/BAT0/
total 0
-rw-r--r-- 1 root root 4096 May 19 21:13 alarm
-r--r--r-- 1 root root 4096 May 19 21:13 capacity
-r--r--r-- 1 root root 4096 May 19 21:13 capacity_level
-r--r--r-- 1 root root 4096 May 19 21:13 cycle_count
lrwxrwxrwx 1 root root 0 May 20 09:12 device -> ../../../PNP0C0A:00
-r--r--r-- 1 root root 4096 May 19 21:13 energy_full
-r--r--r-- 1 root root 4096 May 19 21:13 energy_full_design
-r--r--r-- 1 root root 4096 May 19 21:13 energy_now
drwxr-xr-x 3 root root 0 May 20 09:12 hwmon3
-r--r--r-- 1 root root 4096 May 19 21:13 manufacturer
-r--r--r-- 1 root root 4096 May 19 21:13 model_name
drwxr-xr-x 2 root root 0 May 19 21:13 power
-r--r--r-- 1 root root 4096 May 19 21:13 power_now
-r--r--r-- 1 root root 4096 May 19 21:13 present
-r--r--r-- 1 root root 4096 May 19 21:13 serial_number
-r--r--r-- 1 root root 4096 May 19 21:13 status
lrwxrwxrwx 1 root root 0 May 19 21:13 subsystem -> ../../../../../../class/power_supply
-r--r--r-- 1 root root 4096 May 19 21:13 technology
-r--r--r-- 1 root root 4096 May 19 21:13 type
-rw-r--r-- 1 root root 4096 May 20 09:12 uevent
-r--r--r-- 1 root root 4096 May 19 21:13 voltage_min_design
-r--r--r-- 1 root root 4096 May 19 21:13 voltage_now

[dimkr]

Uploaded preview4. It uses zstd instead of xz, like 9.1.x and 9.0.x.

I switched to xz before preview1, because xz seems to work well for existing Puppy users (nobody complains?) and it's nicer to have a smaller main SFS if you use pfix=ram, because that saves some RAM.

But I've noticed that application startup times (especially Firefox) are horrible even with pfix=ram, and 9.2.x feels slow. Seems that decompression speeds have a huge impact on responsiveness even with pfix=ram. I switched back to zstd, with the same compression level as in 9.1.x: the ISO is 8% bigger, but everything feels so much faster. Most applications start ~immediately on this old laptop and and CPU consumption is lower.

(I also see that RAM consumption after first boot is lower than what I remember, but I don't think it's related.)

[Duprate]

Hi Dimkr! in this your new version of Dpup you don't use Xwayland. I thought this was the highlight of its development (it was in 9.0.x), which would be a future trend in other linux. As I use version 9.0.x daily, I had already gotten used to it.... Good luck in your work!

[dimkr]

Hi Dimkr! in this your new version of Dpup you don't use Xwayland. I thought this was the highlight of its development (it was in 9.0.x), which would be a future trend in other linux. As I use version 9.0.x daily, I had already gotten used to it.... Good luck in your work!

Debian Bullseye is simply too old to keep up with the latest wlroots version. In 9.1.x, I already had to backport some newer packages, but the next version of wlroots will be impossible to backport to Bullseye without upgrading dependencies of GTK+.

The Wayland effort has moved to http://forum.puppylinux.com/viewtopic.php?t=5290: Vanilla Upup uses dwl instead of Cage, and it can run Wayland and X applications side-by-side. I'm working on gradually moving key bindings and window management from JWM to dwl, and at some point, JWM will be dropped.

[dimkr]

Good also that it uses overlayfs though I wish a version would be produced that would use upstream Ubuntu kernel since my HP secure boot system, that boots via Ubuntu/Zorin grub2, will not boot the unsigned kernel and upstream ubuntu kernel would be perfect (also I prefer to use well-tested upstream kernels really - why not?). I can boot using Puppy provided grub2, from usb stick, but that's a pain for my internal nvme SSD drive situation. Of course I understand Puppy always builds huge kernel to make initrd tiny, but I'd like the option to use standard upstream kernels for reasons stated, and since not using aufs no such patch necessitates special kernel build. I have same issue with KLV-Airedale, though relatively easy for me to work around the issue there - not so easy for me at least doing so with Puppy.

Though I've used rox filer plenty, I much prefer pcmanfm as it happens so all in all this distro works very well for me (aside from that unsigned kernel issue).

You should try viewtopic.php?t=5290: it uses an enormous kernel, almost identical to the Ubuntu 22.04 one. It doesn't have any of the aufs patches, but it's not signed and you should be able to use it if you have a signed shim. And it uses pcmanfm

EDIT: forgot to mention, there's no need for that run-as-spot: Chromium should be automatically configured to run as spot if the executable name is "chromium".

[wiak]

Sorry, my last post was meant for Vanilla Upup thread. I've moved it there now: viewtopic.php?p=57895#p57895

[retiredt00]

@dimkr thank you for this classic puppy with full apt integration.
It even runs fine on an ancient Pentium M laptop from early 2000s!!!

However, the sfs_load utility is a bit confusing to me.
Is not clear when something is (to be loaded) and when not.
The fact that the SFS opens when added in the queu confuses me even more.
You may want to add some wording on the top of the different shades of gray (or color).

To use/test my various SFSs without rebooting every time I noticed this proposed change that makes vanilladpup-x86_64-9.2.0-preview4 run with AUFS.
After limited use I can tell that applying it makes Dpup9.2 behave as any puppy of yesteryears (but with apt )
However, I see that you do not approve of this change/hack
Any chance that you provide a Dpup 9.2 with AUFS?

Thanks again you for your efforts
Bets

PS: I installed an older pet (in the original overlay version) with "puppy package handler" that broke the entire system.
Nothing worked after that.
I had to force power-off but it did not worked again.
Eventually I booted another puppy remove the installed files (in /bin and /lib) from the savefolder and then booted OK.
Does "puppy package handler" problematic somehow?

[dimkr]

However, the sfs_load utility is a bit confusing to me.
Is not clear when something is (to be loaded) and when not.
The fact that the SFS opens when added in the queu confuses me even more.

Yes, overlay doesn't allow layers to be added or removed without unmounting first. It's a limitation of overlay compared to aufs. In the case of Puppy, this means no dynamic SFS loading, only at boot time.

I can add an aufs variant, or even switch back to it. The "cost of doing business" of using aufs is that sometimes aufs is broken or buggy, and we'll probably have to switch away from it at some point.

I want to put Vanilla Dpup in some frozen state that makes most users happy (that's why 9.2.x combines the well-received parts of 9.1.x and 9.0.x), with weekly or monthly builds that cherry-pick bug fixes (as today, with 9.1.x and 9.0.x), but I'm still not sure about overlay. It gives me some peace of mind as a developer (because it's never broken, it's stable, and it's the future-proof choice), but users will need to adjust, and I'm sure some UI improvements are needed to reflect that. On the other hand, aufs is unstable (sometimes it doesn't build at all), but people use its dynamic layer change feature.

PS: I installed an older pet (in the original overlay version) with "puppy package handler" that broke the entire system.
Nothing worked after that.
I had to force power-off but it did not worked again.
Eventually I booted another puppy remove the installed files (in /bin and /lib) from the savefolder and then booted OK.

Old .pet packages where /bin, /lib, etc' are directories, can break your system. You'll need to rebuild these packages with bin* and lib* under /usr, to make them safe for use in a Puppy where these directories are replaced with symlinks.

Does "puppy package handler" problematic somehow?

PPM is generally stupid and dangerous to use, and I think it's a waste of time to fix it. (Nowadays, apt support in woof-CE is in very good shape, and now I'm investing in better Flatpak support.)

[Grey]

better Flatpak support.)

Ubuntu made a bet on Snap. Mint, not wanting to fall under the influence of Canonical, chose Flatpak.

It seems you have chosen the second way. I don't really like both options (except AppImage ). But you went the right way

[retiredt00]

Old .pet packages where /bin, /lib, etc' are directories, can break your system. You'll need to rebuild these packages with bin* and lib* under /usr, to make them safe for use in a Puppy where these directories are replaced with symlinks.

Does "puppy package handler" problematic somehow?

PPM is generally stupid and dangerous to use, and I think it's a waste of time to fix it. (Nowadays, apt support in woof-CE is in very good shape, and now I'm investing in better Flatpak support.)

I’m sure you can judge the intelligence and security of PPM much better than me.
However, pets are parts of Puppy’s legacy, as is Pyppy’s efforts to protect new users or (way too) old ones that are not fully familiar with the internals of puppy..
Maybe you can tweak PPM to just deny installation of these malformed pets and suggest rebuilding, as you just described above.
I think would be important the system not to break so easily, particularly if this is going to be a mainstream Puppy.

[dimkr]

better Flatpak support.)

Ubuntu made a bet on Snap. Mint, not wanting to fall under the influence of Canonical, chose Flatpak.

It seems you have chosen the second way. I don't really like both options (except AppImage ). But you went the right way

Don't get me wrong: I'm not a big fan of Flatpak. But I can't deny the fact most popular applications (including browsers and things like Spotify) are available on Flathub. And, I think it's a good idea to allow the users of a specific Puppy release to install the latest applications, even as the Puppy they use is getting old. At least, I think Flatpak should be an option.

Maybe you can tweak PPM to just deny installation of these malformed pets and suggest rebuilding, as you just described above.
I think would be important the system not to break so easily, particularly if this is going to be a mainstream Puppy.

Can you share the problematic package? I'll see if I can do some small and safe patch to PPM.

EDIT: preview5 will have aufs, let's see how this goes

[retiredt00]

My pets are too big for the forum so I constructed a simple one so you can test.

Looking around I found that the -h option in tar will force it to follow symbolic links and indeed adding this option in the tar extraction commands in installpkg.sh solves the problem.
However, you cannot uninstall the pet as the file list shows them installed in the wrong place.
I thought that this should not be a problem since symbolic links are followed by the rm command but apparently the removal script looks at the savefile and not the root of the file tree. The lib, bin and sbin symbolic links are not present in the savefile so nothing is deleted (though PPM claims is removed). If the symbolic links are added in the savefile then removal works.

I can not tell if instructing tar to follow symbolic links or adding the lib, bin and sbin symbolic links in the savefile a priori, will generate other problems, but they worked for me and protected that system.
Hopefully you can provide an more appropriate solution.
Best

Edit: trying to look at the puppy internals during first shutdown I modified rc.shutdown to generate the symbolic links in /tmp/save1stpup/ when in PUPMODE 128 and only when a link for /initrd/pup_ro2/lib is detected and before the actual copying of the $RDIRS.
Combined with the tar modification above, any pet can be installed and removed without a problem (that I could identify)

[TDRR]

Does this Puppy still only install formatting the whole drive and not frugally, as "Getting Started with Vanilla DPup" mentions? It seems amazing and certainly a Puppy worth trying out, but frugal installs are a good part of what really "sells" Puppy for me.

[williwaw]

A preview build of 9.2.0 is uploaded to https://github.com/vanilla-dpup/release ... 0-preview5 (x86_64) and https://github.com/vanilla-dpup/release ... 0-preview5 (x86).

[*] Traditional ISO image with initrd.gz

hi TDRR
frugal worked fine for me on usb with single partition and grub4dos
did have to change the pmedia parameter in menulst for a cleaner boot up
see the readme.txt for particulars

[dimkr]

Does this Puppy still only install formatting the whole drive and not frugally, as "Getting Started with Vanilla DPup" mentions? It seems amazing and certainly a Puppy worth trying out, but frugal installs are a good part of what really "sells" Puppy for me.

It's a traditional ISO image: install it the way you install any other Puppy.

[dogcat]

Booted the 9.2.0 x86 32-bit just like a normal puppy by extracting the .iso into its own folder and using Grub4DOS to boot. Started up quickly.

On the desktop I can move the tray and even hide it, I can't figure out how to move the JWM Menu to the lower-left of the screen where I like it. That has either been obsoleted or maybe its just my fault that I can't find where to make that adjustment.

[dimkr]

That has either been obsoleted or maybe its just my fault that I can't find where to make that adjustment.

Nope.

You can use ptheme (Desktop -> Desktop settings -> Theming) to change the tray preset:

ptheme.png (87.45 KiB) Viewed 3031 times

Or, you can edit the tray (Desktop -> Desktop setting -> Tray).

[dogcat]

That has either been obsoleted or maybe its just my fault that I can't find where to make that adjustment.

Nope.

You can use ptheme (Desktop -> Desktop settings -> Theming) to change the tray preset:

Thank You, (Desktop -> Desktop settings -> Theming) adjusted how I wanted it.
I would never have bumped into that!

[TDRR]

It's a traditional ISO image: install it the way you install any other Puppy.

Thank you, it indeed works just fine. Wonderful Puppy by the way! It's phenomenal, of the most recent Pups around, this might be one of the very best. Clean and especially lightweight, everything runs so well. Having APT is also a huge plus, and I haven't had any issues at all with downloading from the repos, unlike PPM on some recent Pups.

Only real issue I've had so far, is that both my NTFS partitions are always read-only. What could be causing that, and could it be fixed? Haven't had any issues with that in most other Puppies.

EDIT: Oops, nevermind! Just had to install ntfs-3g. Wasn't expecting it to not be included like usual.

[dimkr]

preview9 will be uploaded soon. It includes Osmo, WeeChat, libfuse2 (required by AppImages) and ntfs-3g.

[dimkr]

preview10 will be uploaded soon and adds three pull requests:

• A fix for IPv6 internet connectivity - https://github.com/puppylinux-woof-CE/woof-CE/pull/3122

• man is no longer a symlink to pman, (for example, man ncdu should work after apt install ncdu) - https://github.com/puppylinux-woof-CE/woof-CE/pull/3116: please let me know if you prefer the old behavior

• A new (a super small one, 80K) application, gplaces - https://github.com/puppylinux-woof-CE/woof-CE/pull/3117: please let me know what you think

[mikeslr]

Well, you've done it this time. A Puppy which OOTB does almost everything I want.

No problems configuring Wifi, creating a SaveFolder, nor rebooting with it being used. I wanted Puppy's TAS screenshot application. Clicking the pet to install it I was warned that it needed ffmpeg. Opened synaptic via menu, updated and used it to install ffmpeg. Worked like a charm so I now have a functional TAS, thanks to synaptic.

Screenshot.png (377.8 KiB) Viewed 2761 times

A couple important AppImages I tried (gimp, LibreOffice) worked OOTB. MikeWalsh's Waterfox-portable also worked. I like it for 'general --i.e. not Ultra-Secure-- browsing because it can use the old firefox addons including videodownload-helper. Downloaded a video. Then used synaptic to install mpv to play it.

To see if firefox portable worked (it does) I clicked the 'ff' script. That also worked.

Osmo lacks contacts. I guess I'll have to live with that. But it's 'Notes' module works. I guess I could transfer addresses, etc. into a note.

pwidgets installed. But will only display the default analog clock even though others are available. IIRC, its a xonclock thing. May not be fixable --I can live with that. Something to play with in my spare time.

Right-Clicking a LibreOffice SFS did not offer SFS-Load; only Disimage Mounter. The latter offered to install it which I declined. Only later did I find SFS-Load on the menu which worked. I thought you had mentioned intending not to include auf. Glad you did. I could get used to just overlays. But think the ability to load and unload applications on the fly is a very valuable capability to have in older systems with limited RAM.

Do suggest that 'run in terminal' be added to the right-click menu.

Well, this Puppy has given me a lot to explore.

By the way, you last posted about version 10 being available soon. But the one I downloaded was version 11.

[williwaw]

A new (a super small one, 80K) application, gplaces - https://github.com/puppylinux-woof-CE/woof-CE/pull/3117: please let me know what you think

I found https://github.com/dimkr/gplaces/blob/gemini/README.md and am still looking for man gplaces, if it exists?

[dimkr]

I found https://github.com/dimkr/gplaces/blob/gemini/README.md and am still looking for man gplaces, if it exists?

Puppy comes without man pages. You can either install docx (it's in the "extras" tarball, included in the release), or:

wget -O /tmp/gplaces.1 https://raw.githubusercontent.com/dimkr/gplaces/gemini/gplaces.1 && busybox man /tmp/gplaces.1

[wiak]

Sorry, my last post was meant for Vanilla Upup thread. I've moved it there now: https://forum.puppylinux.com/viewtopic. ... 895#p57895

I've finally tried this Vanilla Dpup 9.2.0 preview too, and it is also pretty good and has that traditional Pup feel but not requiring use of dodgy old PPM.

Out-of-the-box, sound isn't working for me though - played around with pulseaudio config (looks like pavcontrol) quickly, and also alsamixer, but doesn't seem to find my laptop soundcard as provided.

I have no idea if relevant, but lspci reports:

Code: Select all

00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)

Laptop is an HP Probook 430 G8 with intel i7 processor of some sort. dmesg gives a "error: failed to load DSP firmware"

Code: Select all

~$ dmesg | grep audio
[   12.800700] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[   12.800716] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[   12.800750] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002)
[   12.800954] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   12.801054] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   12.807864] sof-audio-pci 0000:00:1f.3: use msi interrupt mode
[   12.839450] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5
[   12.839452] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[   12.839457] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2
[   12.839500] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2
[   12.839502] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2
[   12.839503] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2
[   12.839996] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2

The Vdpup I've downloaded uses aufs, and contrary to some others I prefer overlayfs despite some limitations it has, but aufs is fine until such time until, and if, it becomes more trouble trying to support it than it is worth - it only has one lead developer and probably less stability longterm than overlay, but I guess it proves to not be a big issue changing between the two.

Personally, I find Vupup more interesting since it uses dwl and wayland is surely going to take over everywhere sooner rather than later, but again, depending on how everything is bolted together it may not be a lot of work taking the structure of Vupup and using that for later Vdpup. I can certainly see why traditional Pup users like this one, but also the problem they inevitably face with the merged into /usr situation most all upstream distros have now adopted - old pets will all need rebuilt in the end, as you say. I feel however that many old pets, in terms of what they provide, have reached their end of life now anyway. I'm not myself convinced that gtkdialog is still worth supporting into the future GTK+4 world, which is inevitably creeping in now also. Yad, possibly a better longterm bet despite being less flexible, and maybe better to move to other frontends than the likes of gtkdialog anyway (as many other small distros did years ago). But these gtkdialog/yad-based apps are all small utilities anyway, so not critical overall one way or the other - so many good apps out there on the repos that often do the job better anyway and not particularly resource-demanding either. Overall, from both a developer perspective, but particularly for a user of the systems I install, the less items that need constant tweaking and maintenance the better! - life is too short and ease of use and longterm reliability saves that precious life/time resource more than all the fiddling about trying to keep minimally maintained apps/utilities all working.

What I don't ever want is something like a Windows or Android-like constant updating environment, endless waits for these updates to occur, constant nagging by adverts and in-app advertising too. The one thing I really fear from the big Linux distros like Ubuntu or Red Hat is that they will insert core components that make that sort of situation unavoidable... thus far we escape it else I'll really give up using computers altogether!!! Part of me misses reading newspapers and novels because of the huge amount of time I sit in front of computer, though I still do read newspapers and especially books now and then - particularly reading an actual paper book to help me fall asleep at night... Some might think that late night reading would tend to keep me awake, but actually it doesn't and in fact I often wake up in the morning with the book lying on the floor having fallen out of my hands due to my crashing into sudden sleep. What does keep me terribly awake is if I do any last minute late night programming... that is a seriously bad idea, though I do sometimes then wake up with solution to a programming problem I thought I'd never solve.

[dimkr]

preview13 will be uploaded soon and features:

• Built-in man pages - https://github.com/puppylinux-woof-CE/woof-CE/pull/3116 and https://github.com/puppylinux-woof-CE/woof-CE/pull/3127

• A fix for cursor theme inconsistency after changing the theme - https://github.com/puppylinux-woof-CE/woof-CE/pull/3124

• A Puppy-style default icon for applications without an icon - https://github.com/puppylinux-woof-CE/woof-CE/pull/3128

• A modernized Flat-grey theme (with an old-style tray on the bottom) instead of Dark Gray - https://github.com/puppylinux-woof-CE/woof-CE/pull/3128 - it's less compact than Dark Gray, lighter, more traditional and has better contrast

@wiak Try apt install firmware-sof-signed