5.4.284 64bit Kernel Non-Usrmerge Aufs/Overlayfs

[ozsouth]

09Nov24. This kernel has a spectre v2 vulnerability (shouldn't be catastrophic). Sorry, I missed it.
Good reason for using major distro kernels. There is a fix, but I've made adjusted 6.6 & 6.1 kernels now.
Apparently, this vulnerability is very difficult to exploit.

re- fix see: viewtopic.php?p=135369#p135369

-------------------------------------------------------------------------------------------

I made a 64bit 5.4.284 Non-Usrmerge, Aufs/Overlayfs Kernel. This is aimed at older PCs.
Thanks to jamesbond for his updated DOTconfig, to which I made only 6 changes.
Has snd_soc_intel_skylake unset - caused hangups on all my PCs. rtw88-8821ce unset (but rtl8821ce as a .pet).

Is in both Ubuntu and Slacko compatible flavours. CANNOT be used for Jammypup64 & later (USRMERGE Pups),
UNLESS these Ubuntu derivative kernel-modules & kernel_sources (& non-usrmerge fdrvs) are run through
a converter like this one: viewtopic.php?p=116744#p116744

Has Voluntary Preemption, older ntfs-3g, vmd builtin, standard 300Hz frequency. Is TCP_SACK mitigated.
Is mostly Spectre/Meltdown mitigated (needs microcode too - see viewtopic.php?p=9658#p9658).
Used gcc 10.2.0 & glibc 2.30. Used 2018 Kernel-Kit Master, with only my essential-for-operation fixes.

Although this should work on standard puppies (probably xenialpup64 & later) as is, to use it with overlayfs, need a specifc initrd.gz, or (if your puppy is more recent, like S15Pup64-22.12) have punionfs=overlay in the grub/syslinux linux/kernel line.

Briefly tested, OK in fossa64-small (new version, unreleased, in aufs & overlayfs). Use at own risk.
For best results when using a savefile/savefolder, it is advisable to have that on an ext3 (or 4) partition.

wl & rtl8821ce wireless drivers are in forum Drivers section.
NOTE: many broadcom devices can use in-kernel b43 drivers. fdrv below has newer broadcom firmware to work with that.

Once downloaded, expand in an empty folder with tar -jxvf, & rename kernel-modules.sfs-5.4.284-64oz-nskl-ao to zdrv ... (same as one to be replaced) & rename vmlinuz-5.4.284-64oz-nskl-ao to vmlinuz & then substitute for originals.
Important Note: when switching kernels, if you have an ...initmodules.txt file (i.e. fossapup64initmodules.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.

Notes for Overlayfs: either kernel derivative below works on any system. Devx, if named in same convention as puppy sfs for that pup, will load on boot, if in the same folder as puppy sfs. If devx loaded on the fly, compiling will fail, so best to have a separate install just for compiling, with no savefile/savefolder, naming kernel sources as ydrv & rebooting.
Also, savefolders/files cannot be shared by aufs & overlayfs, due to different structures.

Ubuntu derivative: https://archive.org/download/Puppy_Linu ... ao.tar.bz2

Slacko derivative: https://archive.org/download/Puppy_Linu ... ao.tar.bz2

Kernel Sources: https://archive.org/download/Puppy_Linu ... skl-ao.sfs

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

My 28oct24 lowmed fdrv (36mb): https://www.mediafire.com/file/twyvf8eb ... 4.sfs/file

[Jasper]

@ozsouth

That was a quick turn around and thanks guys for testing!!!

Kernel Build: 5.4.284-64oz-nskl-ao (x86_64)
Build Date: Sat Sep 21 16:22:53 AEST 2024
Build GCC: 10.2.0

I grabbed all the files except the Slackware one.

I am using the new kernel with the earlier provided fdrv.sfs which contained the i915 & BT updates.

From memory, I must have the RTL8821ce wireless drivers already saved within my 'Save' file.

However, can you share this as well, just a precautionary measure for me ........ 'promise' I will keep it in a 'safe place' ...... more importantly somewhere, where I can them with ease

Thanks in advance

[ozsouth]

@Jasper - wl & rtl8821ce drivers now in forum Drivers section.

[Jasper]

@ozsouth

I keep on forgetting to ask this and finally remembered today

Can you explain which 'older ntfs-3g' is being used?

Is this application ntfs-progs ?

[ozsouth]

@Jasper ntfs-3g is the default if you don't enable the newer option, ntfs3. It's the open-source implementation of MS ntfs. Copying large files is slower with ntfs-3g, but I feel safer. See link (tree & then explanation at bottom): https://github.com/tuxera/ntfs-3g

[Jasper]

@ozsouth

Thanks for the clarification, it was what I had guessed.

It provides safe and fast handling of the Windows XP, Windows Server 2003, Windows 2000, Windows Vista, Windows Server 2008, Windows 7, Windows 8, Windows Server 2012,Windows Server 2016, Windows 10 and Windows Server 2019 NTFS file systems.

[Jasper]

@ozsouth

I forgot to take a screen grab before I made this change.

Fossapup95

Looking at my Jammypup64 I can see that it has an older version.

So, I am guessing that Fossapup95 also had an older build? Or the same one as JammyPup64 shown above?

I have been using this and not had any difficulties.

[ozsouth]

@Jasper - seems relate to puppy's base, not kernel. As it works, I haven't dug deeper. My observations are below:

fossapup-small:
ntfs-3g 2017.3.23AR.3 integrated FUSE 28 - Third Generation NTFS Driver
Configuration type 7, XATTRS are on, POSIX ACLS are on

jammypup-e1:
ntfs-3g 2021.8.22 integrated FUSE 28 - Third Generation NTFS Driver
Configuration type 7, XATTRS are on, POSIX ACLS are on

bookwormpup:
ntfs-3g 2022.10.3 integrated FUSE 28 - Third Generation NTFS Driver
Configuration type 7, XATTRS are on, POSIX ACLS are on

s15pup:
ntfs-3g 2022.10.3 integrated FUSE 27 - Third Generation NTFS Driver
Configuration type 1, XATTRS are on, POSIX ACLS are off

[Jasper]

Thanks for checking this out and providing examples.

I did recompile to keep with the Debian/Ubuntu format