Porteus Kernel Builder

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
neko
DEV Team
DEV Team
Posts: 1726
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#1141 by neko » 29 Jan 2021, 11:26

@M. Eerie

Porteus-XFCE-v5.0rc2-k5.10.11.auf-x86_64.iso
includes kernel 5.10.11 vmlinuz & 000-kernel.xzm(slackware style).
Porteus Kernel Builder (Post by neko #81258)

aufs-util-5.10-20210111-x86_64.xzm
is built from AUFS that was used for patching to kernel 5.10.11.
Porteus Kernel Builder (Post by neko #81248)


Thanks.

roadie
Full of knowledge
Full of knowledge
Posts: 315
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 5.0-RC1
Location: In a hayfield

Porteus Kernel Builder

Post#1142 by roadie » 29 Jan 2021, 23:37

neko wrote:
29 Jan 2021, 08:46
applied with AUFS patch (Ver. 5.10-20210111)

@neko,
Is there a link to this patch?
The most recent I can find is Ver. 5.10-20210108.

Thanks

neko
DEV Team
DEV Team
Posts: 1726
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#1143 by neko » 30 Jan 2021, 05:19

@roadie

You can get the recent AUFS patch by using /usr/local/share/mkKernel/bin/getAUFS.sh that is included in
mkKernel-21.01.20-noarch-1.xzm.
Porteus Kernel Builder (Post by neko #52232)

example:
# /usr/local/share/mkKernel/bin/getAUFS.sh 5.10.11


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 3118
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#1144 by Blaze » 30 Jan 2021, 10:13

neko wrote:
29 Jan 2021, 08:46
=== The ISO for testing AUFS function ===

This ISO is intended to study how to "deactivate".
I use your vmlinuz, 000-kernel.xzm, initrd.xz (2020-01-08) and Slackware-current base with tweak of /opt/porteus-scripts/xorg/aufs-insert

Code: Select all

# grep append /opt/porteus-scripts/xorg/aufs-insert
mount -no remount,append:"$MOD"=rr aufs /
from this post Porteus Kernel Builder (Пост neko #81258)

Image

1) Function of deactivate xzm modules is not work for me.
When I try to deactivate xzm module via GUI or CLI my PC is freezing (at this moment, I cannot do anything, since everything is frozen) and only long press Power button is shutdown my PC.

2) All xzm modules are loaded in reverse order (by default it must boots up as 000, 001, 002, 003, etc..., but not otherwise)

3) I like a new small size with your old neko-64bit.config
Linux 5.10.11-porteus #1 SMP Thu Jan 28 11:33:44 UTC 2021 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

neko
DEV Team
DEV Team
Posts: 1726
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#1145 by neko » 30 Jan 2021, 11:37

@Blaze
Thank you for your report.
I think that it is better to use the new config (created by Blaze) than to use old config (named neko-*config).
Because it keeps ordinary AUFS interface even if a litte size bigger.


=== The ordinary AUFS interface ISO ===

This ISO can be used on the ordinary AUFS interface.

Porteus-XFCE-v5.0rc2-k5.10.11-x86_64.iso (389 M)
https://www.mediafire.com/file/exa8iqk5 ... x86_64.iso
md5sum: 114d8ccbb7b6acffe4c015d2534e4386 Porteus-XFCE-v5.0rc2-k5.10.11-x86_64.iso

This ISO was updated from Porteus-XFCE-v5.0rc2-x86_64.iso.
ISO/boot/syslinux/vmlinuz & ISO/porteus/base/000-kernel.xzm
were replaced with the kernel 5.10.11 that was

applied with AUFS patch (Ver. 5.10-20210111)
and
built with new config (64bit.config).

---> I think that as follow.
Kernel with AUFS patch has to be built by using the new config.
If by using old config, "deactivate" command usage has to be study more.

Note:
By using new config, the result kernel (vmlinuz, 000-kernel.xzm) size is bigger 29 M than by using old config.


Thanks.

User avatar
M. Eerie
Shogun
Shogun
Posts: 272
Joined: 31 Aug 2017, 21:18
Distribution: Nemesis Xfce x64

Porteus Kernel Builder

Post#1146 by M. Eerie » 30 Jan 2021, 13:32

neko wrote:
30 Jan 2021, 11:37
=== The ordinary AUFS interface ISO ===
Thanks neko, this one works for me in Nemesis as well. The previous one stopped at boot time with a "Killed" message.

:)
Cheers!

User avatar
Blaze
DEV Team
DEV Team
Posts: 3118
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#1147 by Blaze » 30 Jan 2021, 19:17

neko, I have tried mkKernel-21.01.20-noarch-1.xzm to build kernel 5.10.12 and I have this issue again Image
Image
Image

Any future AUFS patch fix of this issue?

My 64bit-ALL-kernel5.10.12.tar
Linux 5.10.11-porteus #1 SMP Thu Jan 28 11:33:44 UTC 2021 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

roadie
Full of knowledge
Full of knowledge
Posts: 315
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 5.0-RC1
Location: In a hayfield

Porteus Kernel Builder

Post#1148 by roadie » 30 Jan 2021, 21:43

@Blaze,

Possibly the Kernel Builder is getting the wrong patch, but I just compiled 5.10.12 using AUFS patch (Ver. 5.10-20210111) and it boots well. Module activation and deactivation works as it should too, with the standard initrd.

Code: Select all

porteus:[guest]:~$ uname -a
Linux porteus.example.net 5.10.12-porteus #1 SMP Sat Jan 30 12:51:42 Local time zone must be set--see zic  x86_64 AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G AuthenticAMD GNU/Linux
I used neko's script to get the patch.

Code: Select all

/usr/local/share/mkKernel/bin/getAUFS.sh 5.10.11

neko
DEV Team
DEV Team
Posts: 1726
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#1149 by neko » 31 Jan 2021, 04:00

@Blaze

The config that was used at Porteus-XFCE-v5.0rc2-k5.10.11-x86_64.iso
(Porteus Kernel Builder (Post by neko #81270))
is the /usr/local/share/mkKernel/lib/v5.10/64bit.config.

The config that was used at kernel 64bit-ALL-kernel5.10.9.tar
(Porteus Kernel Builder (Post by Blaze #81166))
is differ with /usr/local/share/mkKernel/lib/v5.10/64bit.config.

If the config that was used at kernel 5.10.12 is same as
the config that was used at 64bit-ALL-kernel5.10.9.tar,
please one more try build by using /usr/local/share/mkKernel/lib/v5.10/64bit.config.
Or please try build by updated "Kernel Builder".

"Kernel builder" was updated from mkKernel-21.01.20-noarch-1.xzm to mkKernel-21.01.30-noarch-1.xzm.
(1) updated Firmware database to kernel-firmware-20210119_0578970-noarch-1plus.xzm
(2) added aufs-util build
Note: 64bit.config is not yet changed.

Porteus Kernel Builder (Post by neko #52232)


--------------------------------------------------
@roadie

There was an error in getting the AUFS patch before.
(Porteus Kernel Builder (Post by neko #81127))
However, it has been fixed in the mkKernel-21.01.20-noarch-1.xzm version.


--------------------------------------------------
[How to update "Kernel Builder" of APorteus]
"Kernel Builder" is included in 002-z.xorg.xzm.
You need to decompose 002-z.xorg.xzm and replace "Kernel Builder" in it.

Example:
APorteus: APorteus-CINNAMON_de-v21.01.21-x86_64.iso
(ArchLinux packages manager for Porteus (Post by neko #81146))

New "Kernel Builder" : mkKernel-21.01.30-noarch-1.xzm
(Porteus Kernel Builder (Post by neko #52232))

operation in APorteus environment.

Code: Select all

% su
# ls -1
APorteus-CINNAMON_de-v21.01.21-x86_64.iso
mkKernel-21.01.30-noarch-1.xzm
# dISO APorteus-CINNAMON_de-v21.01.21-x86_64.iso
# dXZM APorteus-CINNAMON_de-v21.01.21-x86_64/porteus/base/002-z.xorg.xzm
# sep2pkg 002-z.xorg
# rm -fr pkgs.002-z.xorg/mkKernel*
# dXZM mkKernel-21.01.30-noarch-1.xzm
# mv mkKernel-21.01.30-noarch-1 pkgs.002-z.xorg/
# pkgs2xzm pkgs.002-z.xorg
# rm -fr pkgs.002-z.xorg
# mv 002-z.xorg.xzm APorteus-CINNAMON_de-v21.01.21-x86_64/porteus/base/
# mv APorteus-CINNAMON_de-v21.01.21-x86_64 APorteus-CINNAMON_de-v21.01.31-x86_64
# mkISO APorteus-CINNAMON_de-v21.01.31-x86_64
# rm -fr APorteus-CINNAMON_de-v21.01.31-x86_64
# ls -1
APorteus-CINNAMON_de-v21.01.21-x86_64.iso
APorteus-CINNAMON_de-v21.01.31-x86_64.iso
mkKernel-21.01.30-noarch-1.xzm
#


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 3118
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#1150 by Blaze » 31 Jan 2021, 09:43

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

[5.10.12] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.10.12.tar (~160 M)
https://files.sberdisk.ru/s/Kez2MfaYseFztRb
2b01c2339281f6bc064bf1e37e142784 64bit-ALL-kernel5.10.12.tar

Image

Note : Compiler that was used.
for kernel 5.10.12: 10.2.0-x86_64

Thanks to neko for his support.

neko, why we have 07-kernel-header-5.10.12.xzm module?
Not bad if all content of hearder will be in the 06-crippled_sources.
Linux 5.10.11-porteus #1 SMP Thu Jan 28 11:33:44 UTC 2021 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
Ed_P
Contributor
Contributor
Posts: 5939
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 & 5.0rc2 Cinnamon 64 ISOs
Location: Western NY, USA

Porteus Kernel Builder

Post#1151 by Ed_P » 31 Jan 2021, 18:24

Touchpad tapping doesn't work. Have to use right clicks.

:wall: It works fine in AF mode. My stupid error. :sorry: Sorry. :(
Ed

neko
DEV Team
DEV Team
Posts: 1726
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#1152 by neko » 01 Feb 2021, 06:10

@Blaze
1. "why we have 07-kernel-header-5.10.12.xzm module?"
---->
Because it is needed to build aufs-util.

"README" in aufs-util.git
- CPPFLAGS
specify the include path if necessary.
Some of linux kernel header files are necessary including
linux/aufs_type.h. If you have installed kernel header files to
/usr/include, then you may not need to specify CPPFLAGS.
Otherwise you need to do something like this sample.
+ run "make headers_install" in your kernel source tree, and
$LinuxSrc/usr/include is created and header files are installed
there by default.
+ if you build aufs4 as module from aufs4-standalone.git, then
$AufsStdalone/usr/include is created and header files are
installed there.
+ and specify
CPPFLAGS="-I $LinuxSrc/usr/include -I $AufsStdalone/usr/include"
Note that your distribution may contain an obsoleted version of
aufs_type.h in /usr/include/linux or something. When you build aufs
utilities, make sure that your compiler refers the correct aufs header
file which is built by "make headers_install."

2. "all content of hearder"
It was created by the command
"make O=../kernel-header-5.10.12 headers_install" under linux-5.10.12.

07-kernel-header-5.10.12.xzm is differ with 06-crippled_sources-5.10.12-64bit.xzm.

# diff -r 07-kernel-header-5.10.12/usr/include 06-crippled_sources-5.10.12-64bit/usr/src/linux-5.10.12/include
many differences...


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 3118
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#1153 by Blaze » 06 Feb 2021, 17:45

neko wrote:
01 Feb 2021, 06:10
1. "why we have 07-kernel-header-5.10.12.xzm module?"
---->
Because it is needed to build aufs-util.
Well, but now I am not able to compile any source because of this hack:

Code: Select all

fatal error
...
No such file or directory
...
compilation aborted. 

Code: Select all

gcc -DHAVE_CONFIG_H -I. -I..    -I../lib -O2 -fPIC -MT epson_escpr-filter.o -MD -MP -MF .deps/epson_escpr-filter.Tpo -c -o epson_escpr-filter.o `test -f 'filter.c' || echo './'`filter.c
In file included from /usr/include/bits/errno.h:26,
                 from /usr/include/errno.h:28,
                 from filter.c:31:
/usr/include/linux/errno.h:1:10: фатальная ошибка: asm/errno.h: Нет такого файла или каталога
    1 | #include <asm/errno.h>
      |          ^~~~~~~~~~~~~
компиляция прервана.


# ln -s /usr/include/asm-generic/errno.h /usr/include/asm/errno.h

gcc -DHAVE_CONFIG_H -I. -I..    -I../lib -O2 -fPIC -MT epson_escpr-linux_cmn.o -MD -MP -MF .deps/epson_escpr-linux_cmn.Tpo -c -o epson_escpr-linux_cmn.o `test -f 'linux_cmn.c' || echo './'`linux_cmn.c
In file included from /usr/include/sys/ioctl.h:26,
                 from linux_cmn.c:40:
/usr/include/bits/ioctls.h:23:10: фатальная ошибка: asm/ioctls.h: Нет такого файла или каталога
   23 | #include <asm/ioctls.h>
      |          ^~~~~~~~~~~~~~
компиляция прервана.


# ln -s /usr/include/asm-generic/ioctl.h /usr/include/asm/ioctl.h

gcc -DHAVE_CONFIG_H -I. -I..    -Wall -DCUPS_FILTER_NAME=\"epson-escpr\" -DCUPS_FILTER_PATH=\"/usr/lib64/cups/filter\"  -O2 -fPIC -MT epson_escpr_wrapper-wrapper.o -MD -MP -MF .deps/epson_escpr_wrapper-wrapper.Tpo -c -o epson_escpr_wrapper-wrapper.o `test -f 'wrapper.c' || echo './'`wrapper.c
In file included from /usr/include/sys/socket.h:33,
                 from /usr/include/cups/http.h:34,
                 from /usr/include/cups/ipp.h:18,
                 from /usr/include/cups/cups.h:27,
                 from wrapper.c:25:
/usr/include/bits/socket.h:354:11: фатальная ошибка: asm/socket.h: Нет такого файла или каталога
  354 | # include <asm/socket.h>
      |           ^~~~~~~~~~~~~~
компиляция прервана.


# ln -s /usr/include/asm-generic/socket.h /usr/include/asm/socket.h
# ln -s /usr/include/asm-generic/sockios.h /usr/include/asm/socket.h
WTF? :ROFL:

Only my manual symlinks help me.

A non-working solution that points to the root of the problem resolution

Code: Select all

ln -s /usr/include/asm-generic/*.h /usr/include/asm/*.h
# or
mv /usr/include/asm-generic/*.h /usr/include/asm/
Any solution or fix are welcome :)
Linux 5.10.11-porteus #1 SMP Thu Jan 28 11:33:44 UTC 2021 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

neko
DEV Team
DEV Team
Posts: 1726
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#1154 by neko » 13 Feb 2021, 04:35

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

1. Old configs (neko-32/64bit.config) for kernel version of 5.10 & 5.11 were updated.
old
CONFIG_LOCALVERSION="-porteus"
new
CONFIG_LOCALVERSION="-newAUFif"

2. Add new functions that create "AUFS IF" / "OVERLAYFS" initrd
Updateing the kernel of ISO with "keep org" (keep original initrd.xz) flag OFF.

(1)update initrd for old interface AUFS kernel.
[old interface AUFS kernel]
build kernel with AUFS patch by 32bit.config/64bit.config (ordinary config).

Note 1:
This case does not need "keep org" OFF.
So, set "keep org" ON.
(But, for APorteus ISO, set OFF is better)

(2)update initrd for new interface AUFS kernel.
[new interface AUFS kernel]
build kernel with AUFS patch by neko-32bit.config/neko-64bit.config (old config).

(3)update initrd for OVERLAY FS kernel.
[OVERLAY FS kernel]
build kernel without AUFS patch.

Note 2:
If the ISO updated with "keep org" flag OFF is not Porteus v5.0rc2, add the cheatcode "cfgfile=xxxx" to a boot config.
Example: "cfgfile=porteus-v4.0-i586.cfg" for 32bit Porteus v4.0 ISO.
For APorteus, this care not be needed.


Note 3:
APorteus-XFCE_de-v21.02.12-x86_64.iso can be used as updated "Kernel Builder" ISO.
ArchLinux packages manager for Porteus (Post by neko #81408)


--------------------------------------------------------------------------
Image
setting window

[Example operations]
running environment: APorteus-XFCE_de-v21.02.12-x86_64.iso
directories/files:
/buildDIR/
/isoDIR/Porteus-XFCE-v5.0rc2-x86_64.iso
/isoDIR/Porteus-XFCE-v4.0-i586.iso

1. update kernel of Porteus-XFCE-v5.0rc2-x86_64.iso to kernel 5.11-rc7 with AUFS patch
<GUI>
menu ---> "Kernel Builder"
"Kernel Builder Directory" : /buildDIR/
"Kernel Version" : 5.11-rc7
"64Bit" : select
"download : check ON
"expand & AUFS patch" : select
"compile" : check ON
"Create FW" : check ON
"ISO whose kernel will be updated" : /isoDIR/Porteus-XFCE-v5.0rc2-x86_64.iso
"keep org" : check ON
"crippled_sources" : check OFF
"000-kernel" : check OFF

push "OK" button.
&
push "OK" button of confirm window.

result:
/buildDIR/UP.Porteus-XFCE-v5.0rc2-x86_64.iso

2. update kernel of Porteus-XFCE-v5.0rc2-x86_64.iso to kernel 5.10.16 with AUFS patch (New IF)
<GUI>
menu ---> "Kernel Builder"
"Kernel Builder Directory" : /buildDIR/
"Kernel Version" : 5.10.16
"64Bit" : select
"download : check ON
"expand & AUFS patch" : select
"compile" : check OFF
"Create FW" : check OFF
"ISO whose kernel will be updated" :
"crippled_sources" : check OFF
"000-kernel" : check OFF

push "OK" button.
&
push "OK" button of confirm window.

<CUI>

Code: Select all

% su
# cd /buildDIR/
# cp v5.10.16/neko-64bit.config v5.10.16/64/linux-5.10.16/.config
<GUI>
menu ---> "Kernel Builder"
"Kernel Builder Directory" : /buildDIR/
"Kernel Version" : 5.10.16
"64Bit" : select
"download : check OFF
"none expand" : select
"compile" : check ON
"Create FW" : check ON
"ISO whose kernel will be updated" : /isoDIR/Porteus-XFCE-v5.0rc2-x86_64.iso
"keep org" : check OFF
"crippled_sources" : check OFF
"000-kernel" : check OFF

push "OK" button.
&
push "OK" button of confirm window.

result:
/buildDIR/UP.Porteus-XFCE-v5.0rc2-x86_64.iso

3. update kernel of Porteus-XFCE-v5.0rc2-x86_64.iso to kernel 5.11-rc7 without AUFS patch
<GUI>
menu ---> "Kernel Builder"
"Kernel Builder Directory" : /buildDIR/
"Kernel Version" : 5.11-rc7
"64Bit" : select
"download : check ON
"expand only" : select
"compile" : check ON
"Create FW" : check ON
"ISO whose kernel will be updated" : /isoDIR/Porteus-XFCE-v5.0rc2-x86_64.iso
"keep org" : check OFF
"crippled_sources" : check OFF
"000-kernel" : check OFF

push "OK" button.
&
push "OK" button of confirm window.

result:
/buildDIR/UP.Porteus-XFCE-v5.0rc2-x86_64.iso

4. update kernel of Porteus-XFCE-v4.0-i586.iso
4.1. update kernel of Porteus-XFCE-v4.0-i586.iso to kernel 5.11-rc7 with AUFS patch
4.2. update kernel of Porteus-XFCE-v4.0-i586.iso to kernel 5.10.16 with AUFS patch (New IF)
4.3. update kernel of Porteus-XFCE-v4.0-i586.iso to kernel 5.11-rc7 without AUFS patch
replace 1,2,3 as followed.
"64Bit" : select ---> "32Bit" : select
"ISO whose kernel will be updated" : /isoDIR/Porteus-XFCE-v5.0rc2-x86_64.iso ---> /isoDIR/Porteus-XFCE-v4.0-i586.iso
# cp v5.10.16/neko-64bit.config v5.10.16/64/linux-5.10.16/.config ---> v5.10.16/neko-32bit.config v5.10.16/32/linux-5.10.16/.config
result:
/buildDIR/UP.Porteus-XFCE-v5.0rc2-x86_64.iso ---> /buildDIR/UP.Porteus-XFCE-v4.0-i586.iso

for 4.2 & 4.3,
add cheatcode "cfgfile=porteus-v4.0-i586.cfg" into UP.Porteus-XFCE-v4.0-i586.iso@/boot/syslinux/porteus.cfg


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 3118
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#1155 by Blaze » 14 Feb 2021, 08:41

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

[5.10.16] <-- NEW : "All patches" patching was done. (neko-64bit.config was not used)
64bit-ALL-kernel5.10.16.tar (~160 M)
https://files.sberdisk.ru/s/9nQqc8dbk6CKFWf
41a5562eb17b00194f8bee6e0612e25d 64bit-ALL-kernel5.10.16.tar

Note : Compiler that was used.
for kernel 5.10.16: 10.2.0-x86_64

Thanks to neko for his support.


_____________________

UPDATE

neko, the issue with asm headers is still (for more info click on the spoiler)
:dl-purple:
and pysmbc is build well.

You can look these errors when you build pysmbc from source (this is only one example with asm headers issue)

Code: Select all

cd /tmp
git clone -q https://github.com/TurboBlaze/slackbuilds.git
cd /tmp/slackbuilds/python/pysmbc
chmod +x pysmbc.SlackBuild
wget -q --show-progress https://files.pythonhosted.org/packages/e1/22/528f5cead9765dccd7a0573f701c4b2806cc18a312269560ea93828fedf6/pysmbc-1.0.23.tar.gz
./pysmbc.SlackBuild
Thanks.

UPDATE
About 07-kernel-header-NNN.xzm again :D
07-printing-$(arch)-$(date +%Y-%m-%d).xzm is have 07 name and your kernel-header goes with 07 in the name too.
Linux 5.10.11-porteus #1 SMP Thu Jan 28 11:33:44 UTC 2021 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

Post Reply