Porteus Kernel Builder

[fulalas]

I was playing around with some kernel builds without firmwares and I couldn't see anything odd. Have you guys tried the same?

EDIT: just tested on a laptop and with no firmware files the wifi card isn't detected. I wonder if there's any other kind of device that requires firmware

[neko]

"Kernel Builder" was updated to version 21.12.18. (Please refer to the first article of this thread.)

1.AUFS patch procedure updated
AUFS patch of kernel 5.10.82, 83, 84,,... is gotton by "git checkout origin/auf5.10.82" command.
AUFS patch of kernel 5.15.5, 6, 7,... is gotton by "git checkout origin/auf5.15.5" command.

refer to Kernel builder script -- simple version (Post by roadie #86191)
Thank roadie very much.

2. config updated
AUFS patches for kernel5.10.87 and kernel5.15.10 are no error.
Therefore prototype configs of kernel5.10.87 and kernel5.15.10 are updated.

[CONFIG_NTFS3_64BIT_CLUSTER] off set
kernel5.15.10 64bit.config

[CONFIG_NVME_HWMON] on set
kernel5.10.87 32bit/64bit.config
kernel5.15.10 32bit/64bit.config

Note:
About kernel 5.15 and kernel 5.16, drivers/staging/r8188eu/os_dep/os_intfs.c is not yet updated.
Therefore everytime check and patch it manually by using
/usr/local/share/mkKernel/lib/v5.15/drivers@staging@r8188eu@os_dep@os_intfs.c
or
/usr/local/share/mkKernel/lib/v5,16/drivers@staging@r8188eu@os_dep@os_intfs.c


Thanks.

[beny]

ih fulalas i have used often a tbs usb satellite receiver and this hardware have firmware and driver linked to the kernel version,we have to know if the firmware is standalone or embedded to the hardware.

[Blaze]

Hi AcnapyxoB.
Can you try this kernel?

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

[5.15.11] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.15.11.tar (~115 M)
https://files.sberdisk.ru/s/iXt6tCaTqKGrHZD
74ba290f7a383eaf45725e9973f5181f 64bit-ALL-kernel5.15.11.tar

Code: Select all

-# CONFIG_MODULE_COMPRESS_NONE is not set
+CONFIG_MODULE_COMPRESS_NONE=y
 # CONFIG_MODULE_COMPRESS_GZIP is not set
 # CONFIG_MODULE_COMPRESS_XZ is not set
-CONFIG_MODULE_COMPRESS_ZSTD=y
+# CONFIG_MODULE_COMPRESS_ZSTD is not set

Note 1: Compiler that was used.
for kernel 5.15.11: 11.2.0-x86_64
A new x86_64 05-devel.xzm (GCC version 11.2.0)

Thanks to neko for his support.

[AcnapyxoB]

@Blaze, thanks!
Yes I confirm that my encrypted dat file works with kernel 5.15.11.

Merry Christmas
С Рождеством

[Blaze]

AcnapyxoB, awesome
Merry Christmas Вас и Ваших близких

neko, I know that you like ZSTD compression, but we have request is to discard ZSTD modules compression

Code: Select all

CONFIG_MODULE_COMPRESS_NONE=y

Thanks and Merry Christmas

[Ed_P]

Code: Select all

~#  uname -a
Linux porteus.example.net 5.15.11-porteus #1 SMP Sat Dec 25 13:08:57 MSK 2021 x86_64 Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz GenuineIntel GNU/Linux

003-cinnamon.xzm:20211118
initrd.xz:20201102

003-cinnamon-20211118.xzm : Nov 18 03:58
07-printing-x86_64-2021-11-07.xzm : Nov 7 08:57
firefox-94.0.2-x86_64-en-US.xzm : Nov 24 02:06
mychanges.xzm : Dec 21 19:18

ISO: /porteus5.0/rc3ISOModules/Porteus-CINNAMON-v5.0rc3-x86_64-20211223-5.15.11.iso

It is working with my Cinnamon system. A nice Christmas present Blaze. Thank you.

[neko]

@Blaze
At next "Kernel Builder" update,
the configs will be changed not to compress kernel modules as same as "your" config changing.


Thanks.

-----------------
Note:
There is the zstd compress problem at booting.
It causes from the lack of zstd compress in /bin/busybox of initrd.
It might be fixed by one of following approaches.
1. update /bin/busybox of initrd to adding zstd compress ability
--->It needs building busybox(ELF 32-bit LSB executable, statically linked)
2. change kernel driver to uncompressed kernel modules
3. delete the functions that need adding kernel module at booting
functions:
(1) changes=/path/(encrypted file.dat)
(2) booting from network
(3) mounting file system that needs adding kernel module and mounting at booting

I expected that the rebuilt busybox would be introduced.
And I planed that these functions would be deleted from APorteus.
I don't like that "000-kernel.xzm" is included/de-included at booting.

APorteus is simplized more than Porteus.
For example, the function of "changes=EXIT:" already is deleted.

------------------------------------------------------------------------------
"Kernel Builder" was updated to version 21.12.26. (Please refer to the first article of this thread.)

Configs of 5.16, 5.16 were update.
old:
CONFIG_MODULE_COMPRESS_ZSTD=y
new:
CONFIG_MODULE_COMPRESS_NONE=y

------------------------------------------------------------------------------
"ISO Builder" was updated with kernel 5.16-rc7 that was built using the new config.
refer to ArchLinux packages manager for Porteus (Post by neko #36689)


Thanks.

[Blaze]

neko, thanks and Happy New Year
A new kernel-firmware-20211229_57d6b95-noarch-1.txz
+ need to add iwlwifi-QuZ-a0-hr-b0-63.ucode to 000-kernel/lib/firmware/ for a new laptop Dell Inspiron 14 of Ed_P

Code: Select all

guest@porteus:~$ dmesg | grep firmware
[    4.273971] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    4.302720] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_12.bin (v2.12)
[    4.318494] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-66.ucode failed with error -2
[    4.318566] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-65.ucode failed with error -2
[    4.318629] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-64.ucode failed with error -2
[    4.327900] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    4.385227] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[    4.390425] iwlwifi 0000:00:14.3: loaded firmware version 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode op_mode iwlmvm
[    6.004307] Bluetooth: hci0: Waiting for firmware download to complete
guest@porteus:~$ 

BTW a new initrd.xz with BusyBox v1.35.0 thanks to ncmprhnsbl

[neko]

@Blaze
[iwlwifi-QuZ-a0-hr-b0-63.ucode issue]

The firmware database "kernel-firmware-20211216_f682ecb-noarch-1plus.xzm" includes
iwlwifi-QuZ-a0-hr-b0-48.ucode
iwlwifi-QuZ-a0-hr-b0-48.ucode.xz
iwlwifi-QuZ-a0-hr-b0-50.ucode
iwlwifi-QuZ-a0-hr-b0-50.ucode.xz
iwlwifi-QuZ-a0-hr-b0-53.ucode
iwlwifi-QuZ-a0-hr-b0-53.ucode.xz
iwlwifi-QuZ-a0-hr-b0-55.ucode
iwlwifi-QuZ-a0-hr-b0-55.ucode.xz
iwlwifi-QuZ-a0-hr-b0-59.ucode
iwlwifi-QuZ-a0-hr-b0-59.ucode.xz
iwlwifi-QuZ-a0-hr-b0-62.ucode
iwlwifi-QuZ-a0-hr-b0-62.ucode.xz
iwlwifi-QuZ-a0-hr-b0-63.ucode
iwlwifi-QuZ-a0-hr-b0-63.ucode.xz
iwlwifi-QuZ-a0-hr-b0-67.ucode

The driver "usr/lib/modules/5.16.0-rc7-porteus/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko" needs firmwares

Code: Select all

# modinfo -F firmware /usr/lib/modules/5.16.0-rc7-porteus/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
iwlwifi-100-5.ucode
iwlwifi-1000-5.ucode
iwlwifi-135-6.ucode
iwlwifi-105-6.ucode
iwlwifi-2030-6.ucode
iwlwifi-2000-6.ucode
iwlwifi-5150-2.ucode
iwlwifi-5000-5.ucode
iwlwifi-6000g2b-6.ucode
iwlwifi-6000g2a-6.ucode
iwlwifi-6050-5.ucode
iwlwifi-6000-6.ucode
iwlwifi-7265D-29.ucode
iwlwifi-7265-17.ucode
iwlwifi-3168-29.ucode
iwlwifi-3160-17.ucode
iwlwifi-7260-17.ucode
iwlwifi-8265-36.ucode
iwlwifi-8000C-36.ucode
iwlwifi-9260-th-b0-jf-b0-46.ucode
iwlwifi-9000-pu-b0-jf-b0-46.ucode
iwlwifi-gl-a0-fm7-a0-67.ucode
iwlwifi-bz-a0-fm-a0-67.ucode
iwlwifi-bz-a0-mr-a0-67.ucode
iwlwifi-bz-a0-gf4-a0-67.ucode
iwlwifi-bz-a0-gf-a0-67.ucode
iwlwifi-bz-a0-hr-b0-67.ucode
iwlwifi-SoSnj-a0-mr-a0-67.ucode
iwlwifi-ma-a0-fm-a0-67.ucode
iwlwifi-ma-a0-mr-a0-67.ucode
iwlwifi-ma-a0-gf4-a0-67.ucode
iwlwifi-ma-a0-gf-a0-67.ucode
iwlwifi-ma-a0-hr-b0-67.ucode
iwlwifi-SoSnj-a0-jf-b0-67.ucode
iwlwifi-SoSnj-a0-hr-b0-67.ucode
iwlwifi-SoSnj-a0-gf-a0-67.ucode
iwlwifi-SoSnj-a0-gf4-a0-67.ucode
iwlwifi-ty-a0-gf-a0-67.ucode
iwlwifi-so-a0-gf-a0-67.ucode
iwlwifi-so-a0-hr-b0-67.ucode
iwlwifi-so-a0-jf-b0-67.ucode
iwlwifi-cc-a0-67.ucode
iwlwifi-QuQnj-b0-jf-b0-67.ucode
iwlwifi-QuZ-a0-jf-b0-67.ucode
iwlwifi-QuZ-a0-hr-b0-67.ucode
iwlwifi-Qu-b0-jf-b0-67.ucode
iwlwifi-Qu-c0-hr-b0-67.ucode
iwlwifi-QuQnj-b0-hr-b0-67.ucode
iwlwifi-Qu-b0-hr-b0-67.ucode
#

Therefore the firmware "iwlwifi-QuZ-a0-hr-b0-63.ucode" is not set in "lib/firmware".

If it is needed that the firmware "iwlwifi-QuZ-a0-hr-b0-63.ucode" is set in "lib/firmware",
(1)it is set manually from the firmware database to "lib/firmware".
Or
(2)(this approach is not assurance to have no side effect.)
the firmware "modinfo" of the driver "iwlwifi.ko" will be needed changing
from iwlwifi-QuZ-a0-hr-b0-67.ucode to iwlwifi-QuZ-a0-hr-b0-63.ucode
by modifyng source code.

for example kernel 5.15.12
linux-5.15.12/drivers/net/wireless/intel/iwlwifi/cfg/22000.c
[new]
/* Highest firmware API version supported */
#define IWL_22000_UCODE_API_MAX 63


"Kernel builder" will be not modified by this issue.


---------------------------------------------------------------------
"Kernel Builder" was updated to version 22.01.03. (Please refer to the first article of this thread.)


------------------------------------------------------------------------------
"ISO Builder" & Example ISOs were updated with kernel 5.16-rc8.
These ISOs include updated "Kernel Builder".
(Example ISOs are LXDE Russian language version)
refer to ArchLinux packages manager for Porteus (Post by neko #36689)


Thanks.

[neko]

"Kernel Builder" was updated to version 22.01.10. (Please refer to the first article of this thread.)

New firmware is built with "kernel-firmware-20220106_4aa2c65-noarch-1.txz".

---------------------------------------------------------------------
"ISO Builder" & Example ISOs were updated with kernel 5.16.
These ISOs include updated "Kernel Builder".
Please refer to ArchLinux packages manager for Porteus (Post by neko #36689)



Thanks.

[Blaze]

I am not able to compile a new kernel, coz aufs out of date https://github.com/sfjro/aufs5-linux

[neko]

"ISO Builder" & Example ISO were updated with kernel 5.16.1.
These ISOs include the most recent version "Kernel Builder".

refer to ArchLinux packages manager for Porteus (Post by neko #36689)

---------
@Blaze
New "ISO Builder" can download AUFS patches.


Thanks.

[Blaze]

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

[5.16.1] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.16.1.tar (~117 M)
https://files.sberdisk.ru/s/y8M8gJXZrb5GFtB
7eabf1f63d7a90e203d2d92aeadd1a4e 64bit-ALL-kernel5.16.1.tar

Note 1: Compiler that was used.
for kernel 5.16.1: 11.1.0-x86_64 (Note. 11.1.0 from Arch Linux)
A new x86_64 05-devel.xzm (GCC version 11.2.0)

Thanks to neko for his support.

[Ed_P]

Very weird situation.

5.16.1 a no go.

1. No video hardware acceleration.
2. No wifi.
3. SSD's nvme0n1 drives not even showing.

Code: Select all

~#  uname -a
Linux porteus.example.net 5.15.1-porteus #1 SMP Sat Nov 6 19:26:29 MSK 2021 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux

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

~#  ls -l /mnt/live/memory/images
000-kernel.xzm : Jan 16 12:35
001-core.xzm : Jan 9 03:54
002-xorg.xzm : Jan 7 20:16
002-xtra.xzm : Jan 5 23:03
003-cinnamon-20220109.xzm : Jan 9 08:47
07-printing-x86_64-2021-11-07.xzm : Nov 7 08:57
firefox-94.0.2-x86_64-en-US.xzm : Nov 24 02:06
mychanges.xzm : Jan 12 14:53

Same in AF mode too.

The problem seems to be the USB drive's FAT32 format.
I installed Porteus with the 5.15.1 kernel to the USB drive a couple of weeks ago. I works, it boots, etc on my old Dell notebook. I had problems with it on a new Dell notebook I got for Christmas, like unable to connect to my wifi and unable to access the new Dell's harddrive partitions, some bitlocked, some nvme0n format(?). With help from the forum I got the wifi to work and the bitlocked drive unlocked. So the USB drive system was very functional.

With the new 5.16.1 kernel I thought I would try it to see if it addressed the wifi and nvme0n problems on the new Dell.

I first added the new kernel to my Porteus 5.0rc3 ISO and booted the ISO on my old Dell. It boots fine. I then copied the 000-kernel module from the ISO to the USB's /porteus/base folder after I deleted the 000-kernel that was there. The results of that are posted above. In addition to the new hardware problems I noticed the USB drive was booting with the prior 5.15.1 kernel. I suspected it was a stupid error on my part and went to bed.

Today after fixing some rl problems I worked on this one again. Whether I delete the 000-kernel on the USB drive using Windows or Porteus, delete the files on the USB's /porteus/base and .Trash-1000 folders when I copy the 000-kernel from the ISO with the 5.16.1 kernel to the USB drive's /porteus/base folder and boot the USB drive the kernel shows as being the 5.15.1 kernel.

Code: Select all

System Memory: 3802M
Boot device:   /mnt/sdb1
Device format: "vfat"
Boot folder:   /porteus/
Boot mode:     /mnt/sdb1/porteus
OS:       Porteus-v5.0
ARCH:     x86_64
Linux:    Slackware 15.0
Kernel:   Linux porteus 5.15.1-porteus
Desktop:  cinnamon-20220109.xzm  Cinnamon 5.2.7
Cmdline:  quiet BOOT_IMAGE=///boot/syslinux/vmlinuz extramod=UUID:FE1A-6D02/Modules noload=save.dat

I could understand if the kernel failed because I copied it wrong, but how the ghost of the prior kernel remains blows my mind.