Puppy Linux Discussion Forum

I made a 64bit 6.12.7 2018 KIT USRMERGE Overlayfs-Only kernel, using a modified Debian config.
Like all 6.11 & 6.12 so far, this does NOT allow fallback for newer iwlwifi firmware versions.
(means you have to have the latest, so my fdrvs below ok for now).
This has the spectre v2 BPF fix.

This is for Jammypup64 & later (USRMERGE Pups) & CANNOT be used for Fossapup64 or S15pup64 & older.
'umovd' means usrmerge, overlayfs. d = Debian config.

Used gcc 11.2 & glibc 2.33. Has Voluntary Preemption & Frequency 300Hz. Use at own risk.

Has no firmware - fdrvs linked at bottom of post have some rtw88, rtw89, b43 & mediatek wifi firmware.
Kernel has some rtw88, rtw89, b43 & mediatek wifi drivers. Has vmd & Blake2s builtin.

Missing firmware is a big issue these days. That will stop devices running, even if driver is present.
To see if any is missing, in a maximised terminal run: dmesg | grep irmware
A source of extra firmware is here: https://github.com/endlessm/linux-firmware
For usrmerge pups (jammypup64, bookwormpup64, noblepup64 etc), files go in /usr/lib/firmware.
For all other pups, files go in /lib/firmware.

Is mostly Spectre/Meltdown mitigated (needs microcode too - see viewtopic.php?p=9658#p9658), BUT
if this kernel used for Bookwormpup64, use Bookwormpup fdrv at link below & add .no to end of kbuild.sfs.
Briefly tested, OK in BookwormPup64_10.0.9_nkb.
For best results when using a savefile/savefolder, it is advisable to have that on an ext3 (or 4) partition.

wl wireless driver in forum Drivers section. NOTE: many broadcom devices can use
in-kernel b43 drivers, but needs firmware (links below).

Once downloaded, expand in an empty folder with tar -jxvf, & rename kernel-modules.sfs-6.12.7-64oz-umovd to
zdrv ... (same as one to be replaced) & rename vmlinuz-6.12.7-64oz-umovx to vmlinuz & then substitute for originals. If kbuild... sfs exists, must be disabled before first bootup (I add .no to end of filename).

Important Note: when switching kernels, if you have an ...initmodules.txt file (i.e. dpupbw64initmodules.txt or
similar, in same folder as puppy sfs), must delete it before first boot into new kernel. Otherwise it may try to load modules that don't exist, causing failure.

For compiling, a separate install should be used, with no savefile/savefolder & devx in same folder
as puppy...sfs & Kernel Sources (or Headers) should be named as ydrv, so both will load on boot.

Kernel: https://archive.org/download/Puppy_Linu ... vd.tar.bz2

Sources: https://archive.org/download/Puppy_Linu ... -umovd.sfs

Headers: https://archive.org/download/Puppy_Linu ... x86_64.sfs

A collection of my latest fdrvs is here (must rename fdrvs to suit puppy to be used):
viewtopic.php?p=121635#p121635

@ozsouth
Thanks for the work you are doing for the Kernels.

I have a question concerning firmware needed for them particularly wifi firmware.
New computers seem to require new firmware continuously as processors change.
Does firmware that is developed pretty much remain the same unless problems occur?

Then can a piece of firmware be used for different kernel revisions?
I would think once the firmware is developed for a particular new kernel, that from that point on,
it could be used for newer revised kernels after that.

I also would think that once firmware is made, it doesn't change much from then on.

Thanks again for the hard work you are doing for all of us.

@JusGellin - computer hardware manufacturers release firmware when new hardware is released. It is generally hardware specific. Firmware versions change as time goes on, often for the requirements of newer kernels, or minor hardware improvements, but even that is not a given - fairly often the same firmware can be used for later kernels. Unfortunately, we only find out by trial. Fallback was great in that you didn't necessarily need the latest firmware, but kernel 6.11+ seems to have stopped that (for iwlwifi at least).