(old)Puppy Linux Discussion Forum

woof-ce kernel kit has been updated considerably. SUKK should be updated to benefit users with the advances.

@Belham2 is having problems with 32-bit 4.9 etc kernels built with kernel-kit whereas he says he does not have problems with the 64-bit kernels

Comparing the 32-bit and 64-bit 4.9 configs from kernel-kit
https://github.com/puppylinux-woof-CE/w ... onfigs_x86
https://github.com/puppylinux-woof-CE/w ... igs_x86_64
there are quite a lot of differences - more than I would expect just for the difference in bit length....

Just wondering if anybody knows why they are so different and this thread seemed to be the best place to ask.

Also....
@Belham2 says he does have success with Slacko's 32-bit 3.14.78 kernel...

Comparing the kernel-kit configs for 32-bit 3.14 and 4.9 shows a huge number of differences.....

3.14 went EOL backend of 2016 and is no longer updated

3.16 has the longest life - see:
https://www.kernel.org/category/releases.html

but kernel-kit doesn't have a 3.16 config....

and there are no 3.16 kernels at:
http://distro.ibiblio.org/puppylinux/huge_kernels/

Shouldn't Puppy have a 32-bit 3.16 kernel? If so would it be best to base the config on the 3.14 one or on the 4.1 one (both currently in kernel-kit)??

Update on kernel 3.16.....

Woof-ce kernel-kit does now have a config for 3.16.43 + the patches needed to aufs-3.16 to make it work with 3.16.35 onwards - see:
https://github.com/puppylinux-woof-CE/w ... 1e2f10cb47

I compiled 4.10.11-x64 yesterday using sukk, but keeps locking up on FD.

huge-4.10.11-x64 kernel package for try out! I used it on FD but kept locking up. Set to 1000mhz. Also exposes hardware to virtualised machine.

https://drive.google.com/file/d/0B8-coZ ... DZreVJzTzA

sources
https://drive.google.com/file/d/0B8-coZ ... 29CZjNVMlk

Hi stemsee,

I installed your huge-4.10.11-x64 kernel in Fatdog64 710. Everything seems to be working. Thanks for building this.

@WillM

You're welcome. Thanks for testing, and posting feedback!

Huge-kernel-4.10.11-PuPpY-32-pae
https://drive.google.com/file/d/0B8-coZ ... TFURjNjemc

sources
https://drive.google.com/file/d/0B8-coZ ... DVJV0NCQ0k

stemsee wrote:Huge-kernel-4.10.11-PuPpY-32-pae
https://drive.google.com/file/d/0B8-coZ ... TFURjNjemc

sources
https://drive.google.com/file/d/0B8-coZ ... DVJV0NCQ0k

Thanks, stemsee.

How people will choose the kernel that is butter for their computer ? it would be useful to give information about one kernel does what another does not.
My LxPupXenial has some sounds problems, it seems only oss available in the kernel 4.5.2. How to know that before the choice, that is my question.
And what kernel will be choosen when iso released as public final version

Hello all.

I agree with pelo on this one.

We developers can do research about a new kernel, but middle-of-the-road
users will appreciate finding a brief explanation of the features of any new
kernel and why it is better than the one published before it.

BFN.

musher0 wrote:.... a brief explanation ....

there are brief explanations all over the web.

feel free to educate yourself for in-depth informations

I ususally look here at the changelog

https://cdn.kernel.org/pub/linux/kernel ... og-4.10.11

http://news.softpedia.com/news/linux-ke ... 4952.shtml

That's quite technical.
Isn't there an explanation in "layman's terms" somewhere?

musher0 wrote:That's quite technical.
Isn't there an explanation in "layman's terms" somewhere?

The problem is that everything in the kernel is technical (and greek to the layman) I think.

So I have recently re-arranged ubuild.sh and forked it to nubuild.sh

The script is much shorter with only one build function which builds x86_64 32-pae and 32-nopae kernels and modules, switching each build arch according to arc variable.

The directory structure is different now with sources and vanilla and patches all in the parent directory. The only remaining sub directories are in dist where the packages are finalised. This makes it easier to navigate and view, and also for locating files etc.

There are no more build.conf files! Also only 3 DOTconfig files for x64 pae nopae, which can be reconfigure internally with 'nubuild.sh' '888' option.

I have not yet added recent improvements from woof-ce>kernel-kit , because sukk-2 seems fine without them for the moment.

Still testing.

EDIT: built 4.10.12 and 4.10.13 successfully.

Oops! Nubuild couldn't build a 3.x kernel. Now it can.

I was just re-configureing the DOTconfig for x64 and I noticed the option to specify path to files or dirs for the kernel compile to build (in?) the cpio (initrd) with the kernel build.

I just built a x64 4.10.13 kernel with initrd built in @ 40mb. Works fine.

In my initrd tree there were modules from previous 4.10.13 build which had not been configured fully for my hardware.

I also booted same kernel with external initrd with modules.sfs inside and everything worked fine too.

So it is possible to build the kernel with kernel modules inside the initrd, inside the kernel. As it is possible to specify several directories and/or files for the cpio archive at kernel compile time, it seems possible to also build in the main sfs, probably just need to code initrd init to look for it.

So now we are realistically and easily able to compile a puppy linux distribution as one vmlinuz file.

grub cfg/menu/lst

Re-compiled with full compliment of modules and kernel-modules.sfs put in initrd tree; removed initrd from grub.cfg boot entry. Installed new kernel (56MB) and re-booted flawlessly to desktop.
The kernel booted more verbosely.

eth0 is now sit0.


I did tried compiling the main sfs in, but @ 2GB compilation stopped at cpio phase and failed.
should work with a smaller main sfs.