Page 91 of 135

Porteus Kernel Builder

Posted: 21 Aug 2021, 09:24
by Blaze
[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Simple package (vmlinuz, 000-kernel.xzm, 06-crippled_sources-NNN-XXbit.xzm, 64bit.config)

[5.13.12] <-- NEW : "Only kbuild.patch, base.patch, and mmap.patch are adopted.
64bit-RES-kernel5.13.12.tar (~124M)
https://files.sberdisk.ru/s/qWPajTxGCzPJLt2
b261036b83772c585e97dc37ddaffe40 64bit-RES-kernel5.13.12.tar

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

Thanks to neko for his support.

P.S. Warning! I don't test this kernel.

Porteus Kernel Builder

Posted: 21 Aug 2021, 09:50
by beny
hi blaze i have build this one 5.13.12 with the new gcc 11.2.0 version in current applied to porteus and run fine i have build also some software via slackbuild without issue too.

Porteus Kernel Builder

Posted: 21 Aug 2021, 11:59
by babam
@beny, maybe you can't activate the xzm modules located in aufs.

Porteus Kernel Builder

Posted: 21 Aug 2021, 16:09
by beny
hi babam activate work but not deactivate i have devel module in optional folder so only when i have to use with mkernel or sbo i use it,with the porteus python script i have the error no module named gi,we have to dig in it.

guest@porteus:~$ activate '/mnt/sdh1/porteus/optional/06-devel.xzm'
Updating shared library links: /sbin/ldconfig
Traceback (most recent call last):
File "/usr/share/porteus/gtkdialog.py", line 7, in <module>
import gi
ImportError: No module named gi
Updating MIME database: /usr/bin/update-mime-database /usr/share/mime
Updating GTK immodules: /usr/bin/update-gtk-immodules
guest@porteus:~$

Porteus Kernel Builder

Posted: 21 Aug 2021, 18:31
by beny
well i have build this:

Code: Select all

   guest@porteus:~$ uname -a
Linux porteus.example.net 5.10.60-porteus #1 SMP Sat Aug 21 18:33:39 Local time zone must be set--see zic  x86_64 AMD FX(tm)-6300 Six-Core Processor AuthenticAMD GNU/Linux
guest@porteus:~$ 
guest@porteus:~$ su root
Password: 
root@porteus:/home/guest# activate '/mnt/sdh1/porteus/modules/sbopkg-0.38.1-noarch-1_wsr.xzm' 
Updating shared library links:  /sbin/ldconfig
Traceback (most recent call last):
  File "/usr/share/porteus/gtkdialog.py", line 7, in <module>
    import gi
ImportError: No module named gi
root@porteus:/home/guest# sbopkg

The following directories do not exist:

Variable                   Assignment
--------                   ----------
REPO_{ROOT,NAME,BRANCH} -> /var/lib/sbopkg/,SBo/,14.2
LOGFILE directory -------> /var/log/sbopkg
QUEUEDIR ----------------> /var/lib/sbopkg/queues
SRCDIR ------------------> /var/cache/sbopkg
TMP ---------------------> /tmp/SBo

You can have sbopkg create them or, if these values are incorrect, you can
abort to edit your config files or pass different flags.

(C)reate or (A)bort?: A
root@porteus:/home/guest# deactivate '/mnt/sdh1/porteus/modules/sbopkg-0.38.1-noarch-1_wsr.xzm' 
Updating shared library links:  /sbin/ldconfig
Traceback (most recent call last):
  File "/usr/share/porteus/gtkdialog.py", line 7, in <module>
    import gi
ImportError: No module named gi
root@porteus:/home/guest# sbopkg
bash: /usr/sbin/sbopkg: No such file or directory
root@porteus:/home/guest   
so the error of module gi is here but the porteus scripts work well,seem the aufs patch with the last 5.13 kernel not full work or....

Porteus Kernel Builder

Posted: 22 Aug 2021, 13:00
by babam
beny wrote:
21 Aug 2021, 16:09
hi babam activate work
Sorry for my bad english,
Can you copy the xzm module to /tmp and then activate it.

Porteus Kernel Builder

Posted: 22 Aug 2021, 15:25
by beny
hi babam

Code: Select all

 root@porteus:/home/guest# activate '/tmp/alien-8.95-x86_64-1ponce.xzm' 
Updating shared library links:  /sbin/ldconfig
Traceback (most recent call last):
  File "/usr/share/porteus/gtkdialog.py", line 7, in <module>
    import gi
ImportError: No module named gi
root@porteus:/home/guest# alien
You must specify a file to convert.

Usage: alien [options] file [...]
  file [...]                Package file or files to convert.
  -d, --to-deb              Generate a Debian deb package (default).
     Enables these options:
       --patch=<patch>      Specify patch file to use instead of automatically
                            looking for patch in /var/lib/alien.
       --nopatch	    Do not use patches.
       --anypatch           Use even old version os patches.
       -s, --single         Like --generate, but do not create .orig
                            directory.
       --fixperms           Munge/fix permissions and owners.
       --test               Test generated packages with lintian.
  -r, --to-rpm              Generate a Red Hat rpm package.
      --to-slp              Generate a Stampede slp package.
  -l, --to-lsb              Generate a LSB package.
  -t, --to-tgz              Generate a Slackware tgz package.
     Enables these options:
       --description=<desc> Specify package description.
       --version=<version>  Specify package version.
  -p, --to-pkg              Generate a Solaris pkg package.
  -i, --install             Install generated package.
  -g, --generate            Generate build tree, but do not build package.
  -c, --scripts             Include scripts in package.
      --target=<arch>       Set architecture of the generated package.
  -v, --verbose             Display each command alien runs.
      --veryverbose         Be verbose, and also display output of run commands.
  -k, --keep-version        Do not change version of generated package.
      --bump=number         Increment package version by this number.
  -h, --help                Display this help message.
  -V, --version		    Display alien's version number.

root@porteus:/home/guest# deactivate '/tmp/alien-8.95-x86_64-1ponce.xzm' 
Updating shared library links:  /sbin/ldconfig
Traceback (most recent call last):
  File "/usr/share/porteus/gtkdialog.py", line 7, in <module>
    import gi
ImportError: No module named gi
root@porteus:/home/guest# alien
bash: /usr/bin/alien: No such file or directory
root@porteus:/home/guest# 

            
seem ok i have done a module in /tmp and activate it from /tmp but the error no module gi is here again....

Porteus Kernel Builder

Posted: 22 Aug 2021, 16:10
by babam
beny,
That seems good, Kernel 5.13.12+Aufs is working fine.

Porteus Kernel Builder

Posted: 22 Aug 2021, 16:25
by beny
hi babam mine isn't 5.13.12 with this kernel i have a lot of trouble also the cpu load is too high i have build the last lts kernel well not in slackware 5.10.60 with the whole aufs patch .
guest@porteus:~$ uname -a
Linux porteus.example.net 5.10.60-porteus #1 SMP Sat Aug 21 18:33:39 Local time zone must be set--see zic x86_64 AMD FX(tm)-6300 Six-Core Processor AuthenticAMD GNU/Linux
guest@porteus:~$

Porteus Kernel Builder

Posted: 22 Aug 2021, 16:59
by babam
beny,
I think you are using Kernel 5.13.12
Porteus Kernel Builder (Post by beny #83774)

Porteus Kernel Builder

Posted: 22 Aug 2021, 17:48
by beny
Post#1355 by beny » 21 Aug 2021, 18:31
well i have build this:

Code: Select all

guest@porteus:~$ uname -a
Linux porteus.example.net 5.10.60-porteus #1 SMP Sat Aug 21 18:33:39 Local time zone must be set--see zic x86_64 AMD FX(tm)-6300 Six-Core Processor AuthenticAMD GNU/Linux
guest@porteus:~$
guest@porteus:~$ su root
Password:
root@porteus:/home/guest# activate '/mnt/sdh1/porteus/modules/sbopkg-0.38.1-noarch-1_wsr.xzm'
Updating shared library links: /sbin/ldconfig
Traceback (most recent call last):
File "/usr/share/porteus/gtkdialog.py", line 7, in <module>
import gi
ImportError: No module named gi
root@porteus:/home/guest# sbopkg

The following directories do not exist:

Variable Assignment
-------- ----------
REPO_{ROOT,NAME,BRANCH} -> /var/lib/sbopkg/,SBo/,14.2
LOGFILE directory -------> /var/log/sbopkg
QUEUEDIR ----------------> /var/lib/sbopkg/queues
SRCDIR ------------------> /var/cache/sbopkg
TMP ---------------------> /tmp/SBo

You can have sbopkg create them or, if these values are incorrect, you can
abort to edit your config files or pass different flags.

(C)reate or (A)bort?: A
root@porteus:/home/guest# deactivate '/mnt/sdh1/porteus/modules/sbopkg-0.38.1-noarch-1_wsr.xzm'
Updating shared library links: /sbin/ldconfig
Traceback (most recent call last):
File "/usr/share/porteus/gtkdialog.py", line 7, in <module>
import gi
ImportError: No module named gi
root@porteus:/home/guest# sbopkg
bash: /usr/sbin/sbopkg: No such file or directory
root@porteus:/home/guest

so the error of module gi is here but the porteus scripts work well,seem the aufs patch with the last 5.13 kernel not full work or....
Top
i have build but with issue after some try.....

Porteus Kernel Builder

Posted: 26 Aug 2021, 11:42
by babam
Blaze wrote:
21 Aug 2021, 09:24
[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
Can in the next kernel build to set this

Code: Select all

CONFIG_RANDOM_TRUST_CPU=y
Thanks.

Porteus Kernel Builder

Posted: 26 Aug 2021, 16:20
by raja
blaze,

Please refer to post,
Porteus Kernel Builder (Post by raja #82673)

The error repeats in v-5.0rc3 also with zstd-1.5. More loop devices mean, kernel wastes more time in this useless message of "capacity change"
Post by Blaze » 16 Jun 2021, 01:35

raja, look at this https://pastebin.com/KpTryrBc :book:
# In Kernel 5.4.57 is not have these options:
> CONFIG_HAVE_KERNEL_ZSTD=y
> CONFIG_KERNEL_ZSTD=y
As I said before need to test it on Porteus RC3 or you can try to manual update ZSTD:
These two CONFIG additions are required only if you use zstd compression for initrd , kernel and kernel modules. neko uses that in APorteus.

There is no real benefit it.

Config file already has zstd=y for squashfs compression.

In fact, I use kernel- v-5.4.126 without zstd compression and , zstd compression for for base and modules in 5.0rc3.

Kernel finishes its job in 7 seconds and xorg with "intel" driver does end its work in another 4 or 5 seconds*. seconds.

So in next kernel release say in version 5.14, you may consider to change from "y" to "n" in those two lines.

* new login consumes more time than previous releases.

Porteus Kernel Builder

Posted: 29 Aug 2021, 07:02
by Blaze
babam, done.
Image
but I think it's not a good idea coz
about:

Code: Select all

CONFIG_RANDOM_TRUST_CPU=y
The option defaults to n. Prior to this commit adding the option, it was effectively always n, with no user choice possible. If you want to retain the same semantics you have used to date, answer n. If you want faster RNG setup and are willing to take the risk that your CPU is hostile, answer y.
https://forums.gentoo.org/viewtopic-t-1 ... art-0.html
raja, I can't set 'n' via make menuconfig for the

Code: Select all

CONFIG_HAVE_KERNEL_ZSTD=y
CONFIG_KERNEL_ZSTD=y
I can change kernel compression mode only (about CONFIG_KERNEL_ZSTD)
Image

********************

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

[5.14-rc7] <-- NEW : "Only kbuild.patch, base.patch, and mmap.patch are adopted. ZSTD version.
64bit-RES-kernel5.14-rc7.tar (~127.2M)
https://files.sberdisk.ru/s/YxrbxH6GFEknrFg
8317d00032d42f2da5353117d9680351 64bit-RES-kernel5.14-rc7.tar

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

Code: Select all

# diff .old-config .new-config
3c3
< # Linux/x86 5.14.0-rc3 Kernel Configuration
---
> # Linux/x86 5.14.0-rc7 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
3093c3093
< # CONFIG_RANDOM_TRUST_CPU is not set
---
> CONFIG_RANDOM_TRUST_CPU=y
7294d7293
< # CONFIG_STRING_SELFTEST is not set
7536a7536
> # CONFIG_STRING_SELFTEST is not set
Image

Thanks to neko for his support.

Porteus Kernel Builder

Posted: 01 Sep 2021, 16:56
by beny
hi blaze the last kernel build of 5.14.0 fail with a loop error on firmware build i think i try without now and report.....
without the firmware package build option compile well,i don't know why the error,maybe if needed the slackware current have upgrade the kernel to 5.14 version so the firmware is on slackware current too.
well seem we have a weird modules weight...too light