Puppy Linux Discussion Forum

SUKK - stems unattended kernel kit.....

This update changes the user interface by using whiptail dialogues in the terminal, resembling ncurses. Options have been removed. Option added to specify aufs branch to use.

Option for usrmerge ... which means using /usr/lib instead of /lib.

only tested on fatdog!

@stemsee

Thanks for sharing this ............ I really didn't know how to follow all the steps to get a final kernel.

However, it didn't seem to take too long to work through.

I did decide to use my existing firmware to be on the safe side.

I did not manage to end up with a finalised kernel but a series of directories.

To be honest, I think I must have just clicked on <ENTER> for all options.

Any pointers?

Hi Jasper

SUKK is not really for beginners to kernel compiling! Some previous knowledge is assumed.

After entering the sukk directory, right click on empty space and open a terminal here. In the terminal type

./nubuild.sh

press enter.

Connect to internet. Load your devx

First option is to clean previous directories and files. This pause is so that you can check if you want to keep anything....usually not....press enter....Compulsory

Second option is to choose an arch, 1) 64 bit, 2) 32 bit pae 3) 32 bit no pae .... these depend on the configs_extra_user/ ... Dotconfig-64, DOTconfig-pae, DOTconfig-nopae.....which you have to configure in step 8....Compulsory!

for 64bit kernel enter 1

Third Enter the kernel version....e.g. 6.2.9 .... compulsory or default is 5.2.21.

Fourth .... add a custom extension 'jasper' this will be appended 5.2.21-jasper when checking kernel properties.
leave empty and press enter....

Fifth ... firmware option ... press enter to use your current firmware
Sixth ... press enter ... libre kernel remove nonfree blobs
Seventh ... press enter ... usrmerge ... modules in /lib or /usr/lib. enter A or B .... or Enter A.

Then the kernel is downloaded if not already in Vanilla/
Extracts kernel, downloads and patches aufs, applies Patches/* .... manually download rt patch for your selected kernel version.

Eighth ... configure kernel ... enter for 'make menuconfig' .... configure your options. Your config will be copied to user_configs directory. Use tab to navigate to Exit and press enter.

Kernel compiles with your config. If successful, Then builds sfs packages in dist/packages .... huge-*.tar.*, kernel-modules.sfs-*, kernel_sources-*.sfs, vmlinuz-* etc

If you read the options as they appear I think they are adequately self explanatory.

@stemsee

Thanks for the quick reply, it's appreciated.

I got to step 8 and it was unsuccessful.

I did all your previous steps before.

I might have chosen a different option re:deblob.

No harm done. I will try again.

Thank you

extra options ... pressing enter is to NOT choose them ... so the flow is basically enter after the first four options....
I added usrmerge recently , and thanks to this re-check, i saw a few simple improvements need doing.... usrmerge option needs default A on enter .... also arch selection should default to 1 on Enter ... then after first two options, Enter for everything else! I need to update Readme too....ugh!!

updated nubuild.sh script
No options need be entered. Every request has a timeout and default ... arch is 64 bit, version is 5.2.21, firmware is copy system's.
So you could just press enter all the way , or fire the script up in a terminal and leave it to run.

You need to first copy in your known good config files. The ones supplied are for my hardware. You can get some from woof-ce/kernel/ on github

Hi @stemsee

Thanks for the update

I downloaded the updated script and thought I would try it out using your default "time out" settings. I sat staring at my display for 10 minutes before deciding to act

Just wanted to report back that it hangs at the kernel conifg dialog box, you do need to provide input.

Regardless, I did carry on but it failed to compile successfully.

A build log is attached.

@jasper
sorry about that! I was in too much of a hurry. I've been compiling all night, messing around with the script. I still didn'T get build and source links correct .... oh well! Back to the drawing board.....but I'm quite positive next post will be inspirational

@stemsee

No worries, I realise that you have a number of projects on the go

I decide I would have another attempt myself and tried to compile 6.2.11 today. I did add the option of using ZSTD.

It took about a hour (+bit more) to do the work on my i3 cpu. Surprised it only used 1Gb of RAM for the process. I ended up with a 3.2gb output.

Got to the end and ..............

PMSL, I would have been okay if I had installed

https://drive.google.com/file/d/1MZRogs ... GyaQUzAfyp
A proper, tested update! but only tested on fatdog!

@stemsee

Hahahaha at some point I am going to have to download and install FatDog just to see what all the fuss is about

BTW my kernel compilation was not using your script, just using terminal.

SUKK is now being updated to handle newer kernels which may not have an aufs branch yet. such as now we see kernel-6.3 but aufs is at 6.2....so the option to manually input the '.'2 aufs branch is in place.

Thank you for sharing @stemsee
I used it on Fatdog last week , it worked . It made a 6.1.79 kernel .

SUKK-2024 is nearly ready. I had a thorough audit of the code and found some startling things. Particularly patching the aufs and the kernel. In the case of realtime patches, I have encountered problems patching aufs kernel sources. Then it occurred to me - we are supposed to patch the rt patch before doing anything else! After that apply the aufs, after that other patches! It makes a difference: the order of patches....needs investigating further. We need to examine the patches particularly to see if the same lines are targeted.

I straightened out the code, and made a few improvements! Something I want to improve further is in the case of getting to 75% compilation complete and then failing due to errors. I want to grab the errors, open the config at the relevant modules, make changes and RESUME COMPILATION ... ! You know it makes sense. Well I do not think that will be difficult. The mechanism I develope will be useful for woof-ce in the case of packages not found etc.