Porteus Kernel Builder

[neko]

setting of test 1,2

confirm of test 1, 2

@Ed_P
These testing are easy.

1. testing the most recent kernel
Kernel version 5.17-rc8

2. testing config depending on your PC hardware
"compile with the config of only your PC driver"`

Pictures show how to testing 1&2

3. testing new 001, 002
OverlayFS Porteus (Post by neko #87406)
This ISO was built with new 001&002.

md5sum: 7cd7d9461c9377b1651b4ff2deaf1c52 001-core.xzm
md5sum: add34bba25ddc2534f063d231a13c79d 002-xorg.xzm
md5sum: aa79302400efcd68a2411084cff01ef4 002-xtra.xzm


This ISO includes "Kernel Builder" and "devel" tool.
You can build kernel by this ISO.


Thanks.

[raja]

neko,

I normally use k-5.4.126 and wanted to update to v-5.4.185.

But, AUFS-5 series does not support that kernel version anymore. But I made 5.4.126 long ago with aufs-5x patch. Any way out now?

[neko]

@raja
Thank you for the bug report.

It occurred from git network security enhancement.
Please refer to https://github.blog/2021-09-01-improvin ... ty-github/


--------------------------------------------------
"Kernel Builder" was updated to version 22.03.18.
Please refer to the top article of this thread.

It was updated depending on git network security enhancement.


Thanks.

[raja]

Thanks neko for providing aufs5-standalone.kit for k-5.4.185. kernel done.cheers.

[Ed_P]

This ISO includes "Kernel Builder" and "devel" tool.
You can build kernel by this ISO.

The ISO boots on my NVMe drive system neko, the wifi network works and the Firefox browser, though it took me awhile to get it to the forum.

Code: Select all

~#  uname -a
Linux porteus.example.net 5.16.15-porteus #1 SMP PREEMPT Thu Mar 17 06:19:16 UTC 2022 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux

~#  cat /etc/porteus/*
001-core.xzm:20220224
002-xorg.xzm:20220224
002-xtra.xzm:20220224
003-cinnamon.xzm:20220305
initrd.xz:20201102

~#  ls -l /mnt/live/memory/images
000-kernel.xzm : Mar 12 15:04
001-core.xzm : Feb 24 12:49
002-xorg.xzm : Feb 24 12:52
002-xtra.xzm : Feb 24 12:57
003-cinnamon-20220305.xzm : Mar 5 09:03
004-firefox-en-US-98.0.1-x86_64-1.xzm : Mar 17 08:02
05-devel.xzm : Feb 24 13:12
05-mkKernel-22.03.01-noarch-1.xzm : Jul 13 2020

ISO: /ISOs/OV.Porteus-CINNAMON-20220305-x86_64-k5.16.15.iso

[babam]

The ISO boots on my NVMe drive system neko

Because of this CONFIG_VMD=y

[Ed_P]

Unable to test vnc support. When attempting to load my tightvnc-1.3.10-x86_64-1_slonly.xzm module I got this error msg:

Not in the live mode, can't continue. Try xzm2dir /mnt/nvme0n1p7/porteus5.0/Optional/Tightvnc-1.3.10-x86_64-1_slonly.xzm/

Added in 21 minutes 24 seconds:
The ISO boots on my SATA drive system, and the wifi network works also.

Added in 2 hours 25 minutes 42 seconds:
I have started the Kernel Builder app and only looked at the test 1 screen.

I think these two lines

The directory must be in the file system that allows symbolic linkage.
Therefore FAT/NTFS can not be used.

should be tweaked like so:

The directory must be on a file system that allows symbolic linkage,
therefore FAT32/NTFS formats can not be used.

As for the other stuff I'm still a little confused. Like what does "Create FW mean? I haven't looked at test 2.

[neko]

@Ed_P
Like what does "Create FW mean? I haven't looked at test 2.
--->
Some drivers need thier firmwares.
And these firmwares should be set in "/lib/firmware/".
If the "Creat FW" item is checked,
"Kernel Builder" checkes all drivers, gether needed firmwares from outside firmware database and set in "/lib/firmware/".

Current outside firmware database:
kernel-firmware-20220228_ee0667a-noarch-1plus.xzm

Please use most recent version "Kernel Builder".
refer to the top article of this thread.

Thanks.

[Ed_P]

Thank you neko. I recommend changing "Create FW" to be "Add FirmWare" for newbies like me. Unless I'm being overly picky.

Please use most recent version "Kernel Builder".

I can't. The ISO doesn't support the adding of modules. See the error message I posted above.

[neko]

@Ed_P
"I can't. The ISO doesn't support the adding of modules. See the error message I posted above."
--->
"Kernel Builder" can be same as most recent version by editing /usr/local/share/mkKernel/bin/getAUFS.sh .

$ sudo xed /usr/local/share/mkKernel/bin/getAUFS.sh


line 39: git clone git://github.com/sfjro/aufs${V4_5}-standalone.git aufs${V4_5}-standalone.git
----->
line 39: git clone https://github.com/sfjro/aufs${V4_5}-standalone.git aufs${V4_5}-standalone.git


Thanks.

[beny]

hi Ed_P you can add the software on your iso with the make_iso.sh script that is in porteus and why you use a software that is too old 2015, linux have a better way to manage vnc and you know a system that work is a good system....do not upgrade it.

[Ed_P]

$ sudo xed /usr/local/share/mkKernel/bin/getAUFS.sh

When I tried to xed the file using the OV.Porteus-CINNAMON-20220305-x86_64-k5.16.15.iso ISO you created:

Code: Select all

Password: 

(xed:1852): libpeas-WARNING **: 13:33:38.818: Failed to load module 'python3loader': libpython3.10.so.1.0: cannot open shared object file: No such file or directory

(xed:1852): libpeas-WARNING **: 13:33:38.818: Could not load plugin loader 'python3'

** (xed:1852): WARNING **: 13:33:38.820: Failed to load builtin plugin: Text Size

** (xed:1852): WARNING **: 13:33:38.820: Failed to load builtin plugin: Open URI

** (xed:1852): WARNING **: 13:33:38.820: Failed to load builtin plugin: Join Lines

I'll try with my ISO with an older nucleus.

why you use a software that is too old 2015,

Because it's worked for years and what USM shows for vnc. What "better way" are you referring to.

[beny]

https://mirrors.slackware.com/slackware ... 6_64-3.txz
tigervnc: tigervnc (VNC server and client)
tigervnc:
tigervnc: Virtual Network Computing (VNC) is a remote display system which
tigervnc: allows you to view a desktop environment from anywhere on the Internet
tigervnc: and from a wide variety of machine architectures.
tigervnc: TigerVNC is a suite of VNC servers and clients that have a focus on
tigervnc: performance and remote display functionality.
tigervnc:
tigervnc: Homepage: http://tigervnc.org
tigervnc:
tigervnc:

[raja]

I stick to kernel-5.4.x series, for the exclusive reason that config changes to include "ZSTD" compress/decompress directly into the kernel , resulted in "huge numbers of error messages(depending on modules in use) regarding "capacity change noticed from xxx to yyy.

Squashfs module included in kernel (line no 6150) can handle zstd . And no need for this config changes.

I normally have all base and modules compressed in zstd. Just excellent.

My porteus-5.0 with current updated base, boots flat in 10.5 seconds,with many applications. DMESG is without any errors.(7 seconds)

Xorg.log:

Code: Select all

[    10.520] 
X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[    10.520] Build Operating System: Slackware 15.0 Slackware Linux Project
[    10.520] Current Operating System: Linux porteus.example.net 5.4.185-porteus #1 SMP Fri Mar 18 21:30:23 UTC 2022 x86_64
[    10.520] Kernel command line: quiet BOOT_IMAGE=/boot/vmlinuz-5.4.185 ipv6.disable=1 i915.modeset=1 mds=full,nosmt

neko, can you please add one more proto type 'config' kernel zstd=n ,selected in your future kernel builder. ?

( may be line nos 39,46,218,1678,1683)

[Ed_P]

https://mirrors.slackware.com/slackware ... 6_64-3.txz
tigervnc: tigervnc (VNC server and client)

Code: Select all

guest@porteus:~/Downloads$ txz2xzm *.txz
Verifying package tigervnc-1.12.0-x86_64-3.txz.
Installing package tigervnc-1.12.0-x86_64-3.txz:
PACKAGE DESCRIPTION:
# tigervnc (VNC server and client)
#
# Virtual Network Computing (VNC) is a remote display system which
# allows you to view a desktop environment from anywhere on the Internet
# and from a wide variety of machine architectures.
# TigerVNC is a suite of VNC servers and clients that have a focus on
# performance and remote display functionality. 
#
# Homepage: http://tigervnc.org
#
Executing install script for tigervnc-1.12.0-x86_64-3.txz.
Package tigervnc-1.12.0-x86_64-3.txz installed.
Creating /home/guest/Downloads/tigervnc-1.12.0-x86_64-3.xzm

guest@porteus:~/Downloads$ vncviewer 192.168.200.100
vncviewer: error while loading shared libraries: libfltk_images.so.1.3: cannot open shared object file: No such file or directory
guest@porteus:~/Downloads$ 

I don't have that error with the one I was using.

I stick to kernel-5.4.x series

I understand. If it works, don't change it. That's why I would never got a Arch system.