Puppy Linux Discussion Forum

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

Kernel 4.14 End-Of-Life has been extended 4 years, to Jan 2024 - excellent!

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

I've made a 32bit 4.14.134 i686 pae kernel via Puppy kernel-kit, with firmware - no fdrv needed. Is mostly Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in DpupStretch_7.5. Use at own risk. Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.134-32oz.tar.bz2

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

I've made a 32bit 4.14.133 NO PAE (for older systems) kernel via Puppy kernel-kit, with firmware - no fdrv needed. Is mostly Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in Tahrpup 6.0.5. Use at own risk.
Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.133-noPAE.tar.bz2

kschewe · Joined: 02 Aug 2019 Posts: 16 Location: Winnipeg Canada

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

I've made a 64bit 4.14.158 Slacko64 compatible kernel via Puppy kernel-kit, with no firmware - fdrv needed. Is partially Zombieload mitigated (needs microcode - see this howto: http://murga-linux.com/puppy/viewtopic.php?p=1030115#1030115
Is Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in ScPup64. Use at own risk.
Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.158-s64oz.tar.bz2
NOTE: Cannot be used in ubuntu clones or with 32bit pups on 64 bit cpu unless path /usr/lib64 changed to /usr/lib in kernel-modules.sfs-... file (add .sfs to end) via this: http://murga-linux.com/puppy/viewtopic.php?p=1028687#1028687

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

EDIT - download server not working at present SEE BELOW

Dry Falls · Joined: 16 Dec 2014 Posts: 616 Location: Upper Columbia

On download link, file size is reported (35.02 MB). first try was 403 and then " Uh, Oh! This file does not exist."

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

I've made a 64bit 5.3.15 Slacko64 compatible kernel via Puppy kernel-kit, with no firmware - fdrv needed. Is partially Zombieload mitigated (needs microcode - see this howto: http://murga-linux.com/puppy/viewtopic.php?p=1030115#1030115
Is Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in ScPup64. Use at own risk.
Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-5.3.15-64oz.tar.bz2
NOTE: Cannot be used in ubuntu clones or with 32bit pups on 64 bit cpu unless path /usr/lib64 changed to /usr/lib in kernel-modules.sfs-... file (add .sfs to end) via this: http://murga-linux.com/puppy/viewtopic.php?p=1028687#1028687

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

I've made a 64bit 5.4.7 Slacko64 compatible kernel via Puppy kernel-kit, with no firmware - fdrv needed. Is partially Zombieload mitigated (needs microcode - see this howto: http://murga-linux.com/puppy/viewtopic.php?p=1030115#1030115
Is Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in ScPup64. Use at own risk.
Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-5.4.7-64oz.tar.bz2
NOTE: Cannot be used in ubuntu clones or with 32bit pups on 64 bit cpu unless path /usr/lib64 changed to /usr/lib in kernel-modules.sfs-... file (add .sfs to end) via this: http://murga-linux.com/puppy/viewtopic.php?p=1028687#1028687

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

I've made a 32bit 4.14.162 i686 pae kernel via Puppy kernel-kit, with firmware - no fdrv needed. Is mostly Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in lxpupbionic19.03. Use at own risk.
Once downloaded, expand in an empty folder with tar -jxvf, & rename kernel-modules.sfs-4.14.162-pae to zdrv ... (same as one to be replaced) &
rename vmlinuz-4.14.162-pae to vmlinuz & then substitute for originals.

Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-4.14.162-pae.tar.bz2
.

bigpup · Joined: 11 Oct 2009 Posts: 13953 Location: S.C. USA

ozsouth,

Want a challenge?

A lot of people, with Chromebooks, have no sound when running Puppy versions on them.

GalliumOS is a Linux made for Chromebooks.
Sound works in it.
I think the key is what is provided by the kernel in GalliumOS.

I have been working with Bionicpup64 8.0

I found this in GalliumOS kernel and not in the Bionicpup64 8.0 kernel.
lib/modules/4.12.0-galliumos-baytrail/kernel/sound/soc/
That soc directory is not in the Bionicpup kernel.

It contains basically a bunch of sound related files for the intel processor audio hardware.

Maybe, a Puppy Linux kernel package, with this stuff in it, would fix sound in Chromebooks.

Probably the kernel config also needs to have specific settings.

I was wondering if a Puppy kernel package could be made out of the GalliumOS kernel package Idea

I found the download repository for GalliumOS kernels.
https://apt.galliumos.org/pool/main/l/
Notice they have ones for different processors.

Looking at how these kernels are packaged. They are not packaged like Puppy kernels.
Looks like everything needed is here.
It is just scattered around in different deb packages.
Example:
Click on one of the kernels listed.
It shows several deb packages for download.
In Puppy, Uextract can be used to unpack the deb packages, to access their contents.

Do you want to try and make a kernel package out of this stuff for Puppy?
Please! Please! Please!

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

After several false starts, have sound modules loading for Baytrail, Haswell, Broadwell, Skylake Chromebooks via kernel 4.14.161 for bionicpup64. Needed firmware was loaded too. Still no sound though. Out of ideas.

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

WITHDRAWN - DUE TO USB ISSUE, VIDEO ISSUE & HARD LOCKUP. Pity - was faster than previous kernels.

I've made a 64bit 5.4.10 Slacko64 compatible kernel via Puppy kernel-kit, with no firmware - fdrv needed. Is partially Zombieload mitigated (needs microcode - see this howto: http://murga-linux.com/puppy/viewtopic.php?p=1030115#1030115
Is Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in ScPup64. Use at own risk. Kernel here:

ozsouth · Joined: 01 Jan 2010 Posts: 855 Location: S.E Australia

Agreeing with BK that recent 5.4 kernels have issues, I've made a 64bit 5.4.8 kernel, in both Ubuntu and Slacko compatible flavours, via Puppy kernel-kit, with no firmware - needs fdrv. Is partially Zombieload mitigated - needs microcode - see this
howto: http://murga-linux.com/puppy/viewtopic.php?p=1030115#1030115
Is Spectre/Meltdown mitigated. Is TCP_SACK mitigated. Tested OK in Bionicpup64-8.0 & ScPup64-19.09. Used gcc 8.3.0 (my priors used 7.3.0).
Once downloaded, expand in an empty folder with tar -jxvf, & rename kernel-modules.sfs-5.4.8-64oz to zdrv ... (same as one to be replaced) &
rename vmlinuz-5.4.8-64oz to vmlinuz & then substitute for originals. Use at own risk.
Ubuntu Derivative Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-5.4.8-ubun64oz.tar.bz2
Slacko Derivative Kernel here: https://archive.org/download/Puppy_Linux_Huge-Kernels/huge-5.4.8-slac64oz.tar.bz2
fdrv here (rename to suit your system): https://archive.org/download/Puppy_Linux_Huge-Kernels/fdrv_jan2020.sfs

davids45 · Joined: 26 Nov 2006 Posts: 1325 Location: Chatswood, NSW

G'day ozsouth,

I've tried your 5.4.8 kernel in a test BionicPup64 in place of its 4.19.23 kernel - switched vmlinuz and zdrv versions.

Boots well and looks fine for most things.

But no wifi access - my usb dongle requires several ath9k files which I imagine are not in the main puppy sfs nor your new kernel?

Is there a simple way to get wifi running, say, add the athk9 files from another Pup. How kernel-specific are such driver files?

BionicPup80 doesn't have an fdrv so where can I get one that would work?

I've a strong feeling I've had this problem before but can't find where**. Sorry if it's something obvious. Embarassed

.

Thanks for any advice.

David S.
ozmiddle-ish.

**[Deja Vu (again)]
In looking at my directory of Huge Kernels, I finally noticed two sfs titled 'firmware-(date)'.
Looking in my 5.4.8 BionicPup64 I also finally noticed that the /lib/firmware directory was virtually empty, nothing like either of the firmware sfs, or other Pups.
I mounted the later firmware sfs (2019 vintage) and copied to BionicPup64's /lib/firmware/ directory the ath9k sub-directory from the sfs.
Rebooted the 5.4.8-kerneled BionicPup64 and now I have wifi so I can print, scan, and now update this post with its [SOLVED] because I also now have the Internet with this Pup.