Porteus Kernel Builder

[fulalas]

The only way to fix this high memory consumption is to change this in the kernel .config file:

Code: Select all

# CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y

[Blaze]

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

6.6.17 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.6.17-madvise.tar (~157 M)
https://www.mediafire.com/file/wx5x4uzj ... advise.tar
b9d6e4949c2f02ca97d957302c21355e 64bit-ALL-kernel6.6.17-madvise.tar

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

6.7.5 <-- NEW : "All patches" patching was done.
64bit-ALL-kernel6.7.5-madvise.tar (~196 M)
https://www.mediafire.com/file/j887oiyj ... advise.tar
f6e73cf4eb5e0ed1402d988d12d44f58 64bit-ALL-kernel6.7.5-madvise.tar

Note 1: Compiler that was used.
for kernel 6.6.17 and 6.7.5: 11.2.0-x86_64

Note 2: Compilated under Porteus 5.01 (Slackware 15.0 base. Note. glibc-2.33 replaced on glibc-2.35)

Note 3: A new cryptsetup (version 2.3.5: presented by @ncmprhnsbl)

Note 4: for hugepages was activated madvise (thanks to fulalas)

Code: Select all

# CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y

for check this option use this command

Code: Select all

cat /sys/kernel/mm/transparent_hugepage/enabled

if you want to change it in the current session use this hack

Code: Select all

echo always >/sys/kernel/mm/transparent_hugepage/enabled
echo madvise >/sys/kernel/mm/transparent_hugepage/enabled
echo never >/sys/kernel/mm/transparent_hugepage/enabled

Note 5:

RAM:

Code: Select all

# uname -r
6.6.17-porteus
# free -h
               total        used        free      shared  buff/cache   available
Mem:            15Gi       739Mi        13Gi        18Mi       995Mi        14Gi
Swap:             0B          0B          0B

# uname -r
6.7.5-porteus
# free -h
               total        used        free      shared  buff/cache   available
Mem:            15Gi       758Mi        13Gi        18Mi       1.0Gi        14Gi
Swap:             0B          0B          0B

Size:

6.7.5 = 196 M
VS
6.6.17 = 157 M

WTF Any thoughts are welcome?

Note 6: neko can you update kernel config to

Code: Select all

# CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y

?

Thanks to neko and fulalas for support

[M. Eerie]

I have tried 64bit-ALL-kernel6.6.17-madvise.tar and 64bit-ALL-kernel6.7.5-madvise.tar versions.
I can't boot with either on a PC with Ryzen + AMD and I CAN boot on another with Intel.

The only new kernel I have been able to boot my PC with Ryzen 4800u + AMDGPU , is 6.5.7 from Fulalas.

[Blaze]

M. Eerie, do you have any errors? dmesg or xorg logs?

[M. Eerie]

do you have any errors? dmesg or xorg logs?

Hi Blaze.

Unfortunately I can't get any logs, as the system won't boot. It stays at the startup screen with these messages:

/boot/syslinux/vmlinuz... ok
/boot/syslinux/initrd.zst...ok


Tested in both PorteuX and Nemesis.

INTEL MACHINE
PorteuX boots OK with kernel*-madvise
Nemesis with kernel*-madvise (Still untested. Will report back)

AMD RYZEN MACHINE
PorteuX DOES NOT boot with kernel*-madvise
Nemesis DOES NOT boot with kernel*-madvise
Nemesis boots OK with kernel 6.7.5 (vmlinuz sha256sum=abfb1315c468f89dda73d032e78cae7b6f63df13f8a278555bf0389cc4fbebf3

[porteux]

@M. Eerie, could you try this one and let us now the result? I haven't tried on Porteus, only on PorteuX 1.0 current.

https://www.mediafire.com/file/ulhd8l8c ... advice.zip

[M. Eerie]

could you try this one and let us now the result?

THIS ONE BOOTS both PorteuX & Nemesis
Also free -h shows "normal" values.

What's the sorcery behind?

Thanks!

[roadie]

@M. Eerie, could you try this one and let us now the result? I haven't tried on Porteus, only on PorteuX 1.0 current.

https://www.mediafire.com/file/ulhd8l8c ... advice.zip

@porteux,
More a heads up than a problem as I was only testing it with my AMD hardware.

It boots on Porteus v5.01, but dmesg is not working, nor on PorteuX. I realize that dmesg is restricted to root user, but it's not working even for root, I get only a return prompt. This is with both booted in Always Fresh mode.



@M. Eerie,
Does dmesg work for you?

[beny]

hi yes confirmed dmesg not work,nor with sudo nor with su root..

[M. Eerie]

Does dmesg work for you?

Was about to report it... as I've noticed this message at boot

"dmesg: read kernel buffer failed: Function not implemented"

[roadie]

Does dmesg work for you?

Was about to report it... as I've noticed this message at boot

"dmesg: read kernel buffer failed: Function not implemented"

My eyes are too old to spot that message on booting....guessing it may be caused by this:

Code: Select all

# CONFIG_PRINTK is not set

Should be:

CONFIG_PRINTK=y

It's the only difference between 6.7.4 and 6.7.5 regarding printk

EDIT: Yes, a compile with # CONFIG_PRINTK is not set results in not being able to run dmesg

[porteux]

@roadie, yes. Here's a build with PRINTK enabled

https://www.mediafire.com/file/ebbxktuy ... vice-2.zip

[porteux]

THIS ONE BOOTS both PorteuX & Nemesis
Also free -h shows "normal" values.

What's the sorcery behind?

Great!

There's no sorcery. PorteuX is open source

[M. Eerie]

There are a lot of different configurations from the 6-7-5 version I was using:

https://pastebin.com/1mdULsnQ

[Blaze]

neko I only saw what my previous requests (look at this post) are was ignored

Plus you didn't added

Code: Select all

CONFIG_WIREGUARD=m

We need all of these options.
Please add all of them.