Page 94 of 135

Porteus Kernel Builder

Posted: 11 Oct 2021, 18:43
by beny
hi neko and blaze the rc5 of 5.15. have a new section seem iommu,maybe is needed in configure?

Porteus Kernel Builder

Posted: 12 Oct 2021, 10:17
by neko
@beny

You can see "iommu" about 5.15-rc prototype config.
And
You can see it about 5.15-rc neko's PC config too.

Code: Select all

% grep -i iommu /usr/local/share/mkKernel/lib/v5.15/*64bit.config
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IRQ_MSI_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_GART_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IOMMU_IOVA=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IOMMU_API=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IOMMU_SUPPORT=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# Generic IOMMU Pagetable Support
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IOMMU_IO_PGTABLE=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# end of Generic IOMMU Pagetable Support
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_IOMMU_DEBUGFS is not set
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_IOMMU_DEFAULT_DMA_STRICT is not set
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IOMMU_DEFAULT_DMA_LAZY=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IOMMU_DMA=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_AMD_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_AMD_IOMMU_V2=m
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_INTEL_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_INTEL_IOMMU_SVM is not set
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_INTEL_IOMMU_FLOPPY_WA=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON is not set
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_VIRTIO_IOMMU is not set
/usr/local/share/mkKernel/lib/v5.15/64bit.config:CONFIG_IOMMU_HELPER=y
/usr/local/share/mkKernel/lib/v5.15/64bit.config:# CONFIG_IOMMU_DEBUG is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IRQ_MSI_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_GART_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IOMMU_IOVA=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IOMMU_API=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IOMMU_SUPPORT=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# Generic IOMMU Pagetable Support
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IOMMU_IO_PGTABLE=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# end of Generic IOMMU Pagetable Support
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_IOMMU_DEBUGFS is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_IOMMU_DEFAULT_DMA_STRICT is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IOMMU_DEFAULT_DMA_LAZY=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IOMMU_DMA=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_AMD_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_AMD_IOMMU_V2 is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_INTEL_IOMMU=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_INTEL_IOMMU_SVM is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_INTEL_IOMMU_FLOPPY_WA=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON is not set
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:CONFIG_IOMMU_HELPER=y
/usr/local/share/mkKernel/lib/v5.15/myPC-64bit.config:# CONFIG_IOMMU_DEBUG is not set
%
mkKernel-21.10.08-noarch-1.xzm includes myPC-64bit.config.

Please refer to the top article of this thread.


Thanks.

Porteus Kernel Builder

Posted: 12 Oct 2021, 11:23
by babam
raja wrote: โ†‘
26 Aug 2021, 16:20
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.
You mean the compressed kernel modules (*.ko.zst)
Yes I agree, compressed kernel modules are useless and actually make performance decrease.

Porteus Kernel Builder

Posted: 12 Oct 2021, 14:40
by beny
ho blaze sorry i don't have build the rc5 in porteus only in slackware,well all ok.

Porteus Kernel Builder

Posted: 17 Oct 2021, 11:30
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.14.13] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.14.13.tar (~123 M)
https://files.sberdisk.ru/s/YbBZkJ859ZoHKzp
d73cbb4f44e1b0e79c00bc872f65e8ce 64bit-ALL-kernel5.14.13.tar

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

Thanks to neko for his support.

Porteus Kernel Builder

Posted: 17 Oct 2021, 13:02
by AcnapyxoB
Thanks Blaze, but again I can't use encrypted (ext4) dat file with new 5.14.13 kernel (like in previous 5.14.10)

I say it not as a problem a rather as information feedback!

Porteus Kernel Builder

Posted: 18 Oct 2021, 10:20
by babam
AcnapyxoB wrote: โ†‘
17 Oct 2021, 13:02
I can't use encrypted (ext4) dat file with new 5.14.13 kernel (like in previous 5.14.10)
Does using Kernel 5.12.14 work.

Porteus Kernel Builder

Posted: 18 Oct 2021, 15:52
by AcnapyxoB
babam wrote: โ†‘
18 Oct 2021, 10:20
Does using Kernel 5.12.14 work.
Yes, no problems with 5.12.14 and older kernels

Porteus Kernel Builder

Posted: 06 Nov 2021, 17:22
by Blaze
AcnapyxoB, how about to try encrypted (ext4) dat file with kernel 5.15.1? :)

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

[5.15.1] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.15.1.tar (~124 M)
https://files.sberdisk.ru/s/ibkYa8CTokzi7Df
60ca36b10ac99c47dea9512a0279aea8 64bit-ALL-kernel5.15.1.tar

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

Image

Bonus. VirtualBox-6.1.28-k5.15.1-x86_64-1prt.xzm for the kernel 5.15.1 x86_64

Thanks to neko for his support.

Porteus Kernel Builder

Posted: 08 Nov 2021, 14:46
by AcnapyxoB
AcnapyxoB, how about to try encrypted (ext4) dat file with kernel 5.15.1?
Unfortunately situation is the same with new kernel!

Lines from dmesg if they can help:

Code: Select all

[    1.772716] /dev/mapper/crypt: Can't open blockdev
[    1.772729] /dev/mapper/crypt: Can't open blockdev
[    1.772740] /dev/mapper/crypt: Can't open blockdev
[    1.772748] /dev/mapper/crypt: Can't open blockdev
[    1.772755] /dev/mapper/crypt: Can't open blockdev

Porteus Kernel Builder

Posted: 08 Nov 2021, 16:31
by beny
hi AcnapyxoB maybe you have to add the encryption module to initrd,i have seen in config we have a lot of m what is the encryption module that you use for....

Porteus Kernel Builder

Posted: 08 Nov 2021, 16:48
by AcnapyxoB
Sorry beny I don`t understand you!
I use encrypted dat file container (ext4 formated) for changes. I use it for years in diferent PCs without problems.

Porteus Kernel Builder

Posted: 08 Nov 2021, 17:00
by beny
how you open the dat container?

Porteus Kernel Builder

Posted: 08 Nov 2021, 17:12
by AcnapyxoB
how you open the dat container?
Entering password during boot
http://www.porteus.org/component/conten ... d-one.html

Porteus Kernel Builder

Posted: 08 Nov 2021, 17:20
by beny
ok but if you have encrypted the dat i suppose that you have a software that open this dat,ok or i am wrong,i don't use changes so.... if you have the module into the kernel you have to run this module before you use the dat container like other module file system or driver..