Porteus Kernel Builder

[Blaze]

or cliexec cheatcode

Code: Select all

cliexec=my_script
cliexec=my_script;reboot

... Execute specified command(s) in runlevel 3 (before logging
in to a graphical interface).
Use semicolons (;) as command separators with no spaces.
... If you need to use spaces in the command line, replace them
with '~'. For example, 'cliexec=echo~Shutting~power;poweroff'
will echo your text with spaces instead of '~'.
NOTE: to start graphical applications please use 'guiexec='
cheatcode instead.

[AcnapyxoB]

or cliexec cheatcode

Thanks again Blaze,
but for me, I think 'rootcopy' is the best choice

[Blaze]

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 32bit.config)

6.12.5 <-- NEW : "All patches" patching was done.
32bit-ALL-kernel6.12.5.tar (~176 M)
https://www.mediafire.com/file/v3gqjmxh ... 6.12.5.tar
c9e35d8a4831091098352bfa37de71e7 32bit-ALL-kernel6.12.5.tar

==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

6.12.5 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.12.5.tar (~197 M)
https://www.mediafire.com/file/6kjkjmcd ... 6.12.5.tar
e515ad59668d6bef0072dc0a8a02aca7 64bit-ALL-kernel6.12.5.tar

Note 1: Compiler that was used.
for kernel 6.12.5: 14.2.0-x86_64

Note 2: Compilated under Porteus 5.1 (Slackware-current base)

Note 3: Cryptsetup 2.6.1

[RookieAdventures]

Hi Blaze, thanks for the addition.

the updated kernel seems to be working fine.

I tried to compile the kernel(6.12.5) using latest kernel builder, and was able to compile it(UI was super easy to go through)
the system boots with the kernel that i compiled by myself, but i'm unable to use keyboard, it's completely unresponsive, touchpad works.

I tried using the kernel that you compiled (same version 6.12.5) and that works without any issues. i don't know what i did wrong.

this is what i did.
- Downloaded mkKernel-24.12.16-noarch-1.xzm and 05-devel.xzm https://mirrors.dotsrc.org/porteus/x86_ ... -devel.xzm
- booted into live porteus environment using porteus 5.01-lxqt
- activated devel and mkKernel one by one
- opened mkKernel and followed below steps
- Selected a folder in "kernel builder directory"(drive type was ext4)
- in "Kernel Version" Selected latest stable kernel of the linux kernel : 6.12.6 from left dropdown and selected 6.12.5 from right dropdown
- in, Build Kernel checked "Download" option, selected "64Bit" "Expand & AUFS PATCH:AUFS" and "compile with prototype config :PROTO" and also checked "Create FW" (clean up option kept unchecked)
- selected iso location in "Select ISO whose kernel will be updated", keeping "keep org" checked.
- checked "crippled_sources" and "000-kernel" and kept "Zstd compress" and "cryptsetup" unchecked, selected "Placement:Slackware"


this builds kernel fine, but it seems that ISO was not modified with latest kernel and also as mentioned, built kernel with these steps renders keyboard unusable.

although kernel provided by you worked fine, i wanted to try to build the kernel by myself. what have i missed here?

also one more thing, the config provided in the mkKernel by default for 6.12 isn't upto date i believe, i tried compiling the kernel with the default config provided in the mkKernel and also with the config provided in the compiled kernel (6.12.5) both didn't work.

[Blaze]

Hi RookieAdventures and Happy New Year
I don't use kernel builder by neko
I use my script for it

UPDATE

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

6.12.8 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.12.8.tar (~197 M)
https://www.mediafire.com/file/psq8vtf9 ... 6.12.8.tar
e813d511d158e164689f8a1ba779a434 64bit-ALL-kernel6.12.8.tar

Note 1: Compiler that was used.
for kernel 6.12.8: 14.2.0-x86_64

Note 2: Compilated under Porteus 5.1 alpha 1 (Slackware-current base)

Note 3: Cryptsetup 2.6.1

[RookieAdventures]

Hi Blaze,

Thanks for the updated kernel and reply.
Can you post the script that you're using to build the kernel if possible? it would be great start for me to start building the kernel and understand the things.

[Blaze]

Hi RookieAdventures,
at this moment no but if you want you can use PorteuX script for build kernel
https://github.com/porteux/porteux/tree/main/000-kernel
Probably I will add ability to update kernel out of the box in the future.

UPDATE

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

6.13.5 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.13.5.tar (~198 M)
https://www.mediafire.com/file/9bn1pfjx ... 6.13.5.tar
8bb6d05e3340ad9c19fd3324de4accd8 64bit-ALL-kernel6.13.5.tar

Note 1: Compiler that was used.
for kernel 6.13.5: 14.2.0-x86_64

Note 2: Compilated under Porteus 5.1 alpha 2 (Slackware-current base)

Note 3: Cryptsetup 2.6.1

[Blaze]

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

6.13.6 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.13.6.tar (~198 M)
https://www.mediafire.com/file/mbccmdys ... 6.13.6.tar
bb5272f71cb6aa6195c741f926d8dd61 64bit-ALL-kernel6.13.6.tar

Note 1: Compiler that was used.
for kernel 6.13.6: 14.2.0-x86_64

Note 2: Compilated under Porteus 5.1 alpha 2 (Slackware-current base)

Note 3: Cryptsetup 2.6.1

[seed_clapper]

Starting from 6.13.5 KDE just waits at login credentials and LXQT is black occasionally blinking with the booting text.
Maybe something is bugged in Porteus 5.1 alpha 2 which is breaking booting kernel in Porteus 5.01.

UPD: the problem was on my side.

[AcnapyxoB]

Starting from 6.13.5 KDE just waits at login credentials

I've had no problems starting/login in KDE (2024-09-24) with latest 001-core and 002-xorg updates.
I have a problem only with building VirtualBox module, but for this purpose I use Porteus 5.1.

[Blaze]

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

6.13.7 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.13.7.tar (~198 M)
https://www.mediafire.com/file/qvttvx2c ... 6.13.7.tar
d992c0caaffd4d9b8691cb510dac20c2 64bit-ALL-kernel6.13.7.tar

Note 1: Compiler that was used.
for kernel 6.13.7: 14.2.0-x86_64

Note 2: Compilated under Porteus 5.1 alpha 2 (Slackware-current base)

Note 3: Cryptsetup 2.6.1

[seed_clapper]

AcnapyxoB, the problem was in my stupidity.
I am booting porteus using ventoy's custom grub menu /ventoy/ventoy_grub.cfg and forgot about using updated vmlinuz file.

Code: Select all

menuentry "Porteus 6.8.10 default KDE from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=lxqt;000-kernel-6.10.5;000-kernel-6.12.8;000-kernel-6.13.7 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.8.10 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}
menuentry "Porteus 6.10.5 compiled in 5.01 KDE from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=lxqt;000-kernel-6.8.10;000-kernel-6.12.8;000-kernel-6.13.7 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.10.5 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}
menuentry "Porteus 6.12.8 alpha 1 KDE from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=lxqt;000-kernel-6.8.10;000-kernel-6.10.5;000-kernel-6.13.7 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.12.8 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}
menuentry "Porteus 6.13.7 alpha 2 KDE from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=lxqt;000-kernel-6.8.10;000-kernel-6.10.5;000-kernel-6.12.8 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.13.7 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}
menuentry "Porteus 6.8.10 LXQT from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=kde;000-kernel-6.10.5;000-kernel-6.12.8;000-kernel-6.13.7 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.8.10 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}
menuentry "Porteus 6.10.5 LXQT from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=kde;000-kernel-6.8.10;000-kernel-6.12.8;000-kernel-6.13.7 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.10.5 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}
menuentry "Porteus 6.12.8 LXQT from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=kde;000-kernel-6.8.10;000-kernel-6.10.5;000-kernel-6.13.7 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.12.8 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}
menuentry "Porteus 6.13.7 LXQT from=LABEL:prt" {
	set root="$vtoy_iso_part"
	set bootparms="noload=kde;000-kernel-6.8.10;000-kernel-6.10.5;000-kernel-6.12.8 from=LABEL:prt"
	linux /porteus/boot/syslinux/vmlinuz-6.13.7 $bootparms
	initrd /porteus/boot/syslinux/initrd.xz
}

menuentry "<-- Return to previous menu [Esc]" VTOY_RET {
    echo "Return ..."
}

I wish porteus could just auto-detect multiple kernels and ask which one to load.

[Blaze]

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel-NNN-XXbit.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

6.14 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.14.tar (~200 M)
https://www.mediafire.com/file/vptk8o5i ... el6.14.tar
5b4346a598de8e6d3eae95939e4f9387 64bit-ALL-kernel6.14.tar

Note 1: Compiler that was used.
for kernel 6.14: 14.2.0-x86_64

Note 2: Compilated under Porteus 5.1 alpha 2 (Slackware-current base)

Note 3: Cryptsetup 2.6.1

Note 4: Tweaks for zram parameters:

Code: Select all

 CONFIG_ZRAM=m
-# CONFIG_ZRAM_BACKEND_LZ4 is not set
+CONFIG_ZRAM_BACKEND_LZ4=y
 # CONFIG_ZRAM_BACKEND_LZ4HC is not set
-# CONFIG_ZRAM_BACKEND_ZSTD is not set
+CONFIG_ZRAM_BACKEND_ZSTD=y
 # CONFIG_ZRAM_BACKEND_DEFLATE is not set
 # CONFIG_ZRAM_BACKEND_842 is not set
-CONFIG_ZRAM_BACKEND_FORCE_LZO=y
-CONFIG_ZRAM_BACKEND_LZO=y
-CONFIG_ZRAM_DEF_COMP_LZORLE=y
-# CONFIG_ZRAM_DEF_COMP_LZO is not set
-CONFIG_ZRAM_DEF_COMP="lzo-rle"
+# CONFIG_ZRAM_BACKEND_LZO is not set
+# CONFIG_ZRAM_DEF_COMP_LZ4 is not set
+CONFIG_ZRAM_DEF_COMP_ZSTD=y
+CONFIG_ZRAM_DEF_COMP="zstd"
 # CONFIG_ZRAM_WRITEBACK is not set
 # CONFIG_ZRAM_TRACK_ENTRY_ACTIME is not set
 # CONFIG_ZRAM_MEMORY_TRACKING is not set

thanks to agroferia
Report Porteus 5.1 enable zstd for zram