Porteus Kernel Builder

[neko]

"Kernel Builder" was updated to version 21.07.30. (Please refer to the first article.)

Firmware database was updated to kernel-firmware-20210719_168452e-noarch-1plus.xzm
that was created with

slackware package "kernel-firmware-20210719_168452e-noarch-1.txz"
and
following arcklinux pakages.

ipw2100-fw-1.3-noarch-10.xzm
ipw2200-fw-3.1-noarch-8.xzm
linux-firmware-20210716.b7c134f-noarch-1.xzm
wireless-regdb-2021.04.21-noarch-1.xzm
alsa-firmware-1.2.4-noarch-2.xzm
linux-atm-2.5.2-x86_64-6.xzm
nvidia-utils-470.57.02-x86_64-3.xzm
sof-firmware-1.8-x86_64-1.xzm


Note:
The kernel version of APorteus-v21.07.30-x86_64.iso / APorteus-v21.07.30-i486.iso
is 5.14-rc3 with AUFS patch "5.x-rcN-20210719".
And these "ISO Builder" ISOs can be used as "Kernel Builder 21.07.30" ISO.
ArchLinux packages manager for Porteus (Post by neko #36689)


Thanks.

[raja]

neko, You have built a porteus-5.0rc2.iso with a 001.overlay.xzm module, in the absence of aufs.

I found that iso boots very fast 10 seconds with quite a few add on modules.

Can I use 001.overlay.xzm along with your initrd.zstd, for 5.0rc3-QT build?

iso:Porteus-XFCE-v5.0rc2-k5.9rc3-x86_64.iso

[neko]

[AUFS patch "5.x-rcN-20210719" to kernel 5.14-rc4]

It is restricted;
Only kbuild.patch, base.patch, and mmap.patch are adopted.

Thanks.

-------------------------------
@raja

I will check overlayFS about your question.
(I have forgotten 001.overlay.xzm)

Thanks.

[neko]

@raja
"Can I use 001.overlay.xzm along with your initrd.zstd, for 5.0rc3-QT build?"
---->
Yes, you can.
Please refer to OverlayFS Porteus (Post by neko #83583)


Thanks.

[raja]

neko, fine, OV version. but, like k5.12.18 from ncmp and v-5.14rc4 from you, show "premature end" error, on boot. Any problem with kernel builder or source?

Replaceing with older kernel, boots without error.

[neko]

@raja
That is beyond my skill.
If you study more and get the answer by yourself, would you tell us.

Thanks.

[neko]

[AUFS patch "5.13-20210705" to kernel 5.13.8]

It is restricted;
Only kbuild.patch, base.patch, and mmap.patch are adopted.

Thanks.

[beny]

hi, AcnapyxoB have you solved the virtualbox install issue? this version work on porteus5rc3 VirtualBox-6.1.97-146047-Linux_amd64.run,with the last 5.13.10 version with devel packages,well the stripped kernel version isn't enough to build the kernel modules i have done this using the kernel builder when you build the last kernel you have the source builded into a directory,you have to copy into the usr/src directory into the changes directory if you don't have one make it install the .run and build the module for virtualbox in /usr/src/vboxhost after run /sbin/vboxconfig,with changes activates the system is a bit slow to do this task but you have your virtualbox running.

[AcnapyxoB]

hi, AcnapyxoB have you solved the virtualbox install issue? this version work on porteus5rc3 VirtualBox-6.1.97-146047-Linux_amd64.run,with the last 5.13.10 version with devel packages,well the stripped kernel version isn't enough to build the kernel modules i have done this using the kernel builder when you build the last kernel you have the source builded into a directory,you have to copy into the usr/src directory into the changes directory if you don't have one make it install the .run and build the module for virtualbox in /usr/src/vboxhost after run /sbin/vboxconfig,with changes activates the system is a bit slow to do this task but you have your virtualbox running.

beny, I succesifuly build VirtualBox 6.1.22 with Porteus 5.0rc3 kernel 5.12.14.
But without succes with VirtualBox 6.1.26 (same kernel)

Also VirtualBox have a starts and closes bug (if Check for Updates is on), I read here and there and solved the problem by pre-creating a settings file in /home/guest/.config/VirtualBox/VirtualBox.xml

Code: Select all

<?xml version="1.0"?>
<!--
** DO NOT EDIT THIS FILE.
** If you make changes to this file while any VirtualBox related application
** is running, your changes will be overwritten later, without taking effect.
** Use VBoxManage or the VirtualBox Manager GUI to make changes.
-->
<VirtualBox xmlns="http://www.virtualbox.org/" version="1.12-linux">
  <Global>
    <ExtraData>
      <ExtraDataItem name="GUI/Details/Elements" value="general,system,preview,display,storage,audio,network,usb,sharedFolders,description"/>
      <ExtraDataItem name="GUI/LastItemSelected" value="n=GLOBAL"/>
      <ExtraDataItem name="GUI/LastWindowPosition" value="360,225,720,450"/>
      <ExtraDataItem name="GUI/SplitterSizes" value="189,530"/>
      <ExtraDataItem name="GUI/Toolbar/MachineTools/Order" value="None"/>
      <ExtraDataItem name="GUI/Tools/LastItemsSelected" value="Welcome,Details"/>
      <ExtraDataItem name="GUI/UpdateCheckCount" value="2"/>
      <ExtraDataItem name="GUI/UpdateDate" value="never"/>
    </ExtraData>
    <MachineRegistry/>
    <NetserviceRegistry>
      <DHCPServers>
        <DHCPServer networkName="HostInterfaceNetworking-vboxnet0" IPAddress="192.168.56.100" networkMask="255.255.255.0" lowerIP="192.168.56.101" upperIP="192.168.56.254" enabled="1"/>
      </DHCPServers>
    </NetserviceRegistry>
    <SystemProperties defaultMachineFolder="/home/guest/VirtualBox" defaultHardDiskFormat="VDI" VRDEAuthLibrary="VBoxAuth" webServiceAuthLibrary="VBoxAuth" LogHistoryCount="3" proxyMode="0" exclusiveHwVirt="true"/>
    <USBDeviceFilters/>
  </Global>
</VirtualBox>

[Blaze]

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

[5.12.19] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.12.19.tar (~115M)
https://files.sberdisk.ru/s/b8fpx5Jgz6cGgGX
4d0831d4941dd98fb5310d5ad3885d33 64bit-ALL-kernel5.12.19.tar

Note 1: Compiler that was used.
for kernel 5.12.19: 10.3.0-x86_64

Thanks to neko for his support.


Download VirtualBox-6.1.26-k5.12.19-x86_64-1prt.xzm with /home/guest/.config/VirtualBox/VirtualBox.xml shared by AcnapyxoB

If skip VirtualBox.xml I have segmentation error

Code: Select all

# VirtualBox

(process: 9467): GLib-GObject-WARNING **: 17: 16: 39.483: cannot register existing type 'NMAgentManagerError'

(process: 9467): GLib-CRITICAL **: 17: 16: 39.483: g_once_init_leave: assertion 'result! = 0' failed

(process: 9467): GLib-GObject-WARNING **: 17: 16: 39.483: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation error

[AcnapyxoB]

Blaze, beny
Building (and starting after build) of VirtualBox is OK, tried with kernel 5.12.14 and 5.12.19.
But restart with VirtualBox and ExtensionPack modules freeze the system on:

Code: Select all

vboxdrv.sh: Starting VirtualBox Services.
vboxdrv.sh: Building VirtualBox kernel modules.

...tried with self-builded vbox and with the one above from Blaze

[beny]

https://ibb.co/4MRr07s is a screenshot i have used the changes linked to text mode is more fast for the loading if you don have
/lib/modules/5.13.10-porteus/misvboxdrv.ko.zst
/lib/modules/5.13.10-porteus/misc/vboxnetadp.ko.zst
/lib/modules/5.13.10-porteus/misc/vboxnetflt.ko.zst
virtualbox do not start i have installed also the extension pack without issue

[maia]

Download VirtualBox-6.1.26-k5.12.19-x86_64-1prt.xzm with /home/guest/.config/VirtualBox/VirtualBox.xml shared by AcnapyxoB

thanks Blaze. It worked smooth.

[Blaze]

@neko, a new fw

Code: Select all

Thu Aug 19 05:17:32 UTC 2021
a/kernel-firmware-20210818_c46b8c3-noarch-1.txz:  Upgraded.

kernel-firmware-20210818_c46b8c3-noarch-1.txz

[neko]

@Blaze
"Kernel Builder" was updated to version 21.08.21. (Please refer to the first article.)


Thanks.