Porteus Kernel Builder

[raja]

Where I can download peebee config?

I think kernel-5.9.1 by peebee, a Debian stuff has got the file /proc/config.gz in it.

[Blaze]

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

[5.10.3]<-- NEW : restricted version base on peebee config
https://disk.admlr.lipetsk.ru/s/cPPfmfaJZWzB8jm
1cf0fd8286e5491753528aad0353ee85 64bit-RES-kernel5.10.3.tar.tar

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

Om my PC

Code: Select all

[    1.695641] EXT4-fs (sdb1): mounting ext2 file system using the ext4 subsystem
[    1.697809] EXT4-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
[    1.699770] EXT4-fs (sdb1): mounted filesystem without journal. Opts: (null)
[    1.702459] EXT4-fs (sdc1): mounting ext2 file system using the ext4 subsystem
[    1.702672] random: fast init done
[    1.722867] EXT4-fs (sdc1): warning: mounting unchecked fs, running e2fsck is recommended
[    1.730005] EXT4-fs (sdc1): mounted filesystem without journal. Opts: (null)
[    1.811643] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)

Code: Select all

# e2fsck /dev/sdb1
e2fsck 1.45.6 (20-Mar-2020)
/dev/sdb1 is mounted.
e2fsck: Cannot continue, aborting.

Thanks to neko and peebee for his support.

P.S. Use at your own risk!!!

[babam]

[5.10.3]<-- NEW : restricted version base on peebee config

Om my PC

Code: Select all

[    1.695641] EXT4-fs (sdb1): mounting ext2 file system using the ext4 subsystem
[    1.697809] EXT4-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
[    1.699770] EXT4-fs (sdb1): mounted filesystem without journal. Opts: (null)

Does the 'fsck' cheatcode work?
Are there any errors?

Code: Select all

# dmesg --level=err

I think we should focus on kernel 5.10 and higher because the next Porteus will have to use kernel 5.10 or higher (based on Slackware-Current)

[Blaze]

Yes, fsck is workfor me:

Code: Select all

# umount /dev/sdc2
# fsck /dev/sdc2
fsck из util-linux 2.36.1
e2fsck 1.45.6 (20-Mar-2020)
/dev/sdc2: clean, 2739/47366144 files, 5533378/189439744 blocks
# e2fsck /dev/sdc2
e2fsck 1.45.6 (20-Mar-2020)
/dev/sdc2: clean, 2739/47366144 files, 5533378/189439744 blocks

The same errors how at all kernels - this is issue of BIOS of my motherboard. Non-compliance with specification of MS.

Code: Select all

# dmesg --level=err
[    0.858883] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.858899] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    0.860105] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.860121] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    0.862739] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.862754] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    0.863282] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.863298] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    0.864559] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.864575] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    0.874111] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.874126] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    0.877008] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.877024] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    0.878681] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
[    0.878697] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)

[babam]

[5.10.3]<-- NEW : restricted version base on peebee config

I have tried it and so far it is running normally.
But the boot time is a bit slower.

Thanks.

[Blaze]

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

[5.10.4]<-- NEW : restricted version base on peebee and neko config
64bit-RES-kernel5.10.4.tar (~148 M)
https://www.mediafire.com/file/rtxplnvr ... 5.10.4.tar
e2f24c9ec6b0afffa4025125167c83c0 64bit-RES-kernel5.10.4.tar

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

I checked my /dev/sdb and now everything is fine - no errors with FS in dmesg:


Happy New Year to all

[babam]

[Updated kernel Examples]
==== AUFS Kernel only for Porteus ====
[5.10.4]<-- NEW : restricted version base on peebee and neko config

5.10.3 --> 133 MB
5.10.4 --> 140 MB
Can you please tell me what the difference in config is between 5.10.3 vs 5.10.4.

Thanks.

[neko]

@babam
It might be mainly depending on the difference between "CONFIG_KERNEL_XZ=y" (5.10.3) and "CONFIG_KERNEL_ZSTD=y" (5.10.4).

If you have a time, please try to rebuild kernel 5.10.4 with config changed from "CONFIG_KERNEL_ZSTD=y" to "CONFIG_KERNEL_XZ=y".
I am waiting for your that result.

Thanks.

[babam]

@neko, Yes I understand, changing "CONFIG_KERNEL_XZ=y" to "CONFIG_KERNEL_ZSTD=y" only increases the kernel image size (vmlinuz)

Thanks.

[TTT]

No! It also increases the speed of decompression!
Would it be possible to enable conditional on syscall.x32=y CONFIG_X86_X32 enabled, the same way Debian has it?

[babam]

No! It also increases the speed of decompression!

Yes

[babam]

[5.10.4]<-- NEW : restricted version base on peebee and neko config

Confused, what are you using, Porteus or APorteus? Kernel 5.10.4 or 5.11.0-rc1?

[Blaze]

I use Porteus (Slackware) with kernel 5.10.4 and APorteus (Arch) with 5.11.0-rc1 as farm for build kernels

[cad]

Apparently something has changed in the kernel source for 5.10. When booting 5.10.0-rc7, I got a black screen right after starting udev and the only recourse was a hard shutdown. This has never happened with the 5.9 series up to 5.9.12. I was able to get the screen back with "nomodeset" on the command line, but it's unusable as X won't start.

The problem turned out to be my AMD graphics card and the fix that worked for me is putting the following on the command line:

Code: Select all

amdgpu.dc=0

Hopefully this will help someone else with AMD graphics.

I am getting exactly the same behavior with my last generation Lenovo IdeaPad with AMD graphics card, with Blaze's latest kernel Porteus Kernel Builder (Post by Blaze #80754)
Thank you for your fix, roadie, which worked in my case as well!

[maia]

[5.10.3]<-- NEW : restricted version base on peebee config
https://disk.admlr.lipetsk.ru/s/cPPfmfaJZWzB8jm
1cf0fd8286e5491753528aad0353ee85 64bit-RES-kernel5.10.3.tar.tar

Tks Blaze, work on my PC

XZM is activated on the tmpfs

After the boot, I had a few seconds of hisss on the sound card, followed by a snap and after the sound worked normal

Nextcloud is nice