Porteus Kernel Builder
Porteus Kernel Builder
hi Ed_P my bad you need also this: https://mirrors.slackware.com/slackware ... 6_64-1.txz
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
tigervnc-1.12.0-fltk-1.3.8-x86_64-3.xzm works with Porteus 5.0 beny. Thank you. 

-
- DEV Team
- Posts: 2113
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Porteus Kernel Builder
"Kernel Builder" was updated to version 22.03.24-2. (Please refer to the first article of this thread.)
1. Firmware database was updated.
[Firmware database : kernel-firmware-20220318_681281e-noarch-1plus.xzm (372 M)]
that was created with
slackware package "kernel-firmware-20220318_681281e-noarch-1.txz (213 M)" and following pakages.
alsa-firmware-1.2.4-noarch-2
b43-firmware-6.30.163.46-fw-1_SBo
bluetooth
ipw2100-fw-1.3-noarch-10
ipw2200-fw-3.1-noarch-8
zydas
2. Update v5.0rc3 Porteus ISO by replacement initrd.xz, vmlinuz, and 000-kernel.xzm

Setting Window
[ISO whose kernel will be updated]
"Select ISO whose kernel will be updated." ---> v5.0rc3 Porteus ISO (example: /ISOplace/Porteus-KDE-v5.0rc3-i586.iso)
"keep org" item ---> off (no check)
=== result ===
UP.ISO@/boot/syslinux/initrd.xz
UP.ISO@/boot/syslinux/vmlinuz
UP.ISO@/porteus/base/000-kernelxzm
If built kernel without AUFS patch, UP.ISO@/porteus/optional/001-overlayAct.xzm is set.
Note 1: UP.ISO@/boot/syslinux/initrd.xz
is an integrated initrd.xz that can be used for both AUFS and OV.
Note 2: UP.ISO@/porteus/optional/001-overlayAct.xzm
At startup by specifying the cheat code "load=overlayAct",
the "activate/deactivate" command for temporary use will be enable.
--------------------------------------
@raja
Please change these
CONFIG_ZSTD_COMPRESS=y ---> CONFIG_ZSTD_COMPRESS=n
CONFIG_ZSTD_DECOMPRESS=y ---> CONFIG_ZSTD_DECOMPRESS=n
by yourself.
Thanks.
1. Firmware database was updated.
[Firmware database : kernel-firmware-20220318_681281e-noarch-1plus.xzm (372 M)]
that was created with
slackware package "kernel-firmware-20220318_681281e-noarch-1.txz (213 M)" and following pakages.
alsa-firmware-1.2.4-noarch-2
b43-firmware-6.30.163.46-fw-1_SBo
bluetooth
ipw2100-fw-1.3-noarch-10
ipw2200-fw-3.1-noarch-8
zydas
2. Update v5.0rc3 Porteus ISO by replacement initrd.xz, vmlinuz, and 000-kernel.xzm

Setting Window
[ISO whose kernel will be updated]
"Select ISO whose kernel will be updated." ---> v5.0rc3 Porteus ISO (example: /ISOplace/Porteus-KDE-v5.0rc3-i586.iso)
"keep org" item ---> off (no check)
=== result ===
UP.ISO@/boot/syslinux/initrd.xz
UP.ISO@/boot/syslinux/vmlinuz
UP.ISO@/porteus/base/000-kernelxzm
If built kernel without AUFS patch, UP.ISO@/porteus/optional/001-overlayAct.xzm is set.
Note 1: UP.ISO@/boot/syslinux/initrd.xz
is an integrated initrd.xz that can be used for both AUFS and OV.
Note 2: UP.ISO@/porteus/optional/001-overlayAct.xzm
At startup by specifying the cheat code "load=overlayAct",
the "activate/deactivate" command for temporary use will be enable.
--------------------------------------
@raja
Please change these
CONFIG_ZSTD_COMPRESS=y ---> CONFIG_ZSTD_COMPRESS=n
CONFIG_ZSTD_DECOMPRESS=y ---> CONFIG_ZSTD_DECOMPRESS=n
by yourself.
Thanks.
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
Porteus Kernel Builder
Thanks neko.. I tried with what I suggested. But "capacity change error remains. next time I will change compress/decompress also.
Ed_P,
Here is the link for Kernel-5.17. Try for your nvme. It boots ok for me.
Kernel-5.17.tar.gz..size=198.14mb
https://www.mediafire.com/file/e3dvutza ... ar.gz/file
Ed_P,
Here is the link for Kernel-5.17. Try for your nvme. It boots ok for me.
Kernel-5.17.tar.gz..size=198.14mb
https://www.mediafire.com/file/e3dvutza ... ar.gz/file
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
-
- DEV Team
- Posts: 2113
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
Porteus Kernel Builder
@raja
I understand your Kernel-5.17.tar.gz (kernel version 5.17 64bit with AUFS patch).
[diff "prototype config" "your Kernel-5.17.tar.gz config"]
Thanks.
I understand your Kernel-5.17.tar.gz (kernel version 5.17 64bit with AUFS patch).
[diff "prototype config" "your Kernel-5.17.tar.gz config"]
Code: Select all
3c3
< # Linux/x86 5.17.0-rc5 Kernel Configuration
---
> # Linux/x86 5.17.0 Kernel Configuration
5c5
< CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.1.0"
---
> CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.2.0"
7c7
< CONFIG_GCC_VERSION=110100
---
> CONFIG_GCC_VERSION=110200
10c10
< CONFIG_AS_VERSION=23601
---
> CONFIG_AS_VERSION=23700
12c12
< CONFIG_LD_VERSION=23601
---
> CONFIG_LD_VERSION=23700
40c40
< # CONFIG_KERNEL_GZIP is not set
---
> CONFIG_KERNEL_GZIP=y
46c46
< CONFIG_KERNEL_ZSTD=y
---
> # CONFIG_KERNEL_ZSTD is not set
218c218
< CONFIG_RD_ZSTD=y
---
> # CONFIG_RD_ZSTD is not set
1687,1688c1687,1688
< CONFIG_ZRAM_DEF_COMP_ZSTD=y
< # CONFIG_ZRAM_DEF_COMP_LZ4 is not set
---
> # CONFIG_ZRAM_DEF_COMP_ZSTD is not set
> CONFIG_ZRAM_DEF_COMP_LZ4=y
1692c1692
< CONFIG_ZRAM_DEF_COMP="zstd"
---
> CONFIG_ZRAM_DEF_COMP="lz4"
6464d6463
< # CONFIG_COMMON_CLK_LAN966X is not set
7373d7371
< CONFIG_DECOMPRESS_ZSTD=y
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
raja I finally tested your kernel. Porteus 4.0 boots to a black screen with a large mouse pointer. I closed the lid, did other stuff, opened the lid and I had my 4.0 DE but no taskbar.raja wrote: ↑26 Mar 2022, 12:14Ed_P,
Here is the link for Kernel-5.17. Try for your nvme. It boots ok for me.
Kernel-5.17.tar.gz..size=198.14mb
https://www.mediafire.com/file/e3dvutza ... ar.gz/file
When booting an error initially appeared indicating Kinitrd was missing. I've never seen that error before.
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
Porteus Kernel Builder
Black screen --- X session has not been initiated,
ctl+alt+f1 shall take you to login window. login and in your prompt command 'startx'. You should be ok with your desktop.
After logout, when you get the desktop without panel, press alt+f2---give command to open terminal.
In terminal , if you are using cinnamon, give the following command
Source: https://frameboxxindore.com/android/how ... linux.html
login in porteus-4.0 and porteos-5.0-rc3 are different ( I think slim and elogin)that may be causing trouble with your saved setting for autostart of desktop session.
Once you have your desktop, look for settings in /etc/xdg/autostart and make suitable corrections.
ctl+alt+f1 shall take you to login window. login and in your prompt command 'startx'. You should be ok with your desktop.
After logout, when you get the desktop without panel, press alt+f2---give command to open terminal.
In terminal , if you are using cinnamon, give the following command
Code: Select all
gsettings reset-recursively org.cinnamon
login in porteus-4.0 and porteos-5.0-rc3 are different ( I think slim and elogin)that may be causing trouble with your saved setting for autostart of desktop session.
Once you have your desktop, look for settings in /etc/xdg/autostart and make suitable corrections.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
The error is "error: can't find command `Xinitrd' Press any key to continue...", not Kinitrd as I originally posted.
I will try rebooting in some of my other modes to see what I get.
Thank you raja.
I will try rebooting in some of my other modes to see what I get.
Thank you raja.
Porteus Kernel Builder
hi Ed_P this kernel work on porteus4 : https://www.mediafire.com/folder/xa7nxc ... 36-porteus or i have to upload the 5.17.1?
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
My error in my grub2 menu.

Booting with your files raja in AF mode I get the porteus unable to cfg file whether I use "cfgfile=porteus-v5.0-x86_64.cfg" or "cfgfile=porteus-v4.0-x86_64.cfg".
Code: Select all
set extramods="extramod="
menuentry " Porteus 4.0 ISO - AF" --class slackware --class icon-porteus {
set boot_parms="volume=33 reboot=cold $extramods cfgfile=porteus-v5.0-x86_64.cfg"
search -f $iso --set=root
loopback loop $iso
linux (loop)/boot/syslinux/vmlinuz from=$iso $boot_parms
initrd (loop)/boot/syslinux/initrd.xz
# Xinitrd /porteus5.0/initrd/2021-03-25/initrd.xz
}
Thanks beny. I'll look into it later. You're link is fine for me.
Added in 2 hours 58 minutes 46 seconds:
beny, same result as raja's. Searching for porteus-v5.0-x86_64.cfg or porteus-v4.0-x86_64.cfg neither one found.

Added in 1 hour 6 minutes 31 seconds:
BTW How are you guys booting your 4.0 systems?? As you can see from the menu above I'm booting ISOs via grub2.
Porteus Kernel Builder
well if the iso don't boot the solution is put the iso into a usb key and run or use a notebook that can manage porteus4 or like i have tell you usm is dead we need other solution, ok good luck.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Porteus Kernel Builder
What do you use for an initrd file on your USB drives beny?
Porteus Kernel Builder
hi Ed_P the stock initrd:29/04/2018 and with the mediafire kernel run like a charm, the usb key is the only way to use an old porteus or a cdrom but i don't think the new notebook have one?
Porteus Kernel Builder
hi neko this is a link for the 88x2bu.ko wifi driver for the 5.17.1 kernel inside the folder there is also a readme for the supported device list:
https://www.mediafire.com/folder/h98933 ... .17.1-port
ps: i have build it with the whole kernel of your mkernel builder directory the crippled source isn't enough to build all the modules.
https://www.mediafire.com/folder/h98933 ... .17.1-port
ps: i have build it with the whole kernel of your mkernel builder directory the crippled source isn't enough to build all the modules.