Porteus

babam wrote: ↑

02 Nov 2020, 01:05

@Rava
All versions of Porteus can use the kernel created by Blaze.
I even use it for Porteus 3.2.2 and it works great.

How did he work that magic?
Did you try to compile a NVidia driver on it?
Cause that needs the exact same compiler version as there is in the system.

Did you try running rc.FireWall start and did it start up correctly? Also here it is about the correct kernel vs compiler, but not as tricky as with the NVidia driver compiling.

@Rava
I never compile NVidia driver.
Maybe the compiler version should match the compiler version on which to build the kernel.

@Blaze
Looks like the 'fsck' cheatcode doesn't work on kernel 5.9.2 (peebee config).

babam wrote: ↑

02 Nov 2020, 06:42

I never compile NVidia driver.
Maybe the compiler version should match the compiler version on which to build the kernel.

The compiler in the system must be the very same as the compiler that was used when compiling the kernel, or the NVidia driver compilation will fail.

Rava wrote: ↑

02 Nov 2020, 10:05

The compiler in the system must be the very same as the compiler that was used when compiling the kernel, or the NVidia driver compilation will fail.

It's simple, use the same kernel for different version of Porteus.

For example, I was able to build a NTFS3 kernel module on Porteus 5.0rc2 (kernel 5.4.57 and gcc 10.2.0) then I used that NTFS3 kernel module for Porteus 3.2.2

If I compile it on Porteus 3.2.2 (kernel 5.4.57 and gcc 5.3.0) then it will fail.

babam wrote: ↑

02 Nov 2020, 14:32

It's simple, use the same kernel for different version of Porteus.

010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm is the newest NVidia driver I was able to create for the 340 version that I (and others) need for older hardware.
My first setup for Porteus 5.0rc2 was with that kernel but it utterly crashed during bootup, so I changed it back to the ugly standard X and try rc2 out as it is, and will try using my kernel once again when I learned a bit more about rc2.

babam wrote: ↑

02 Nov 2020, 06:59

@Blaze
Looks like the 'fsck' cheatcode doesn't work on kernel 5.9.2 (peebee config).

I have noticed this behavior since newer kernel versions ex: 5.6. I can only use fsck after boot.

Blaze wrote: ↑

01 Nov 2020, 09:37

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

The compilation kernel did not present this ext4 error message. Do you believe it may be related to your card's chipset or some configuration in the .config file?

maia,

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

[5.4.81] <-- NEW : "All patches" patching was done.
64bit-ALL-kernel5.4.81.tar (~98 M)
https://disk.admlr.lipetsk.ru/s/nDPAptocQeXsbsf
2e8a01778321d73ae516e6fc44a95bd5 64bit-ALL-kernel5.4.81.tar

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

Thanks to neko for his support.

Blaze thanks for your support.

Blaze wrote: ↑

05 Dec 2020, 09:04

maia,

<<<< there is no need

Any news about aufs5 for kernel 5.10 ?

hi blaze, neko seem to work on overlayfs, aufs maintainer is not operative yet.....

Blaze wrote: ↑

13 Dec 2020, 16:59

Any news about aufs5 for kernel 5.10 ?

Junjiro R. Okajima has been heard from.....
He is working on 5.8 and has requested feedback on the aufs-users email list : https://sourceforge.net/p/aufs/mailman/ ... /37174765/
He has also produced some unofficial patch material for 5.10 :
https://github.com/sfjro/aufs5-standalo ... -736706823
which can be downloaded from :
https://sourceforge.net/projects/lxpup/ ... s-changes/

5.10 has been released https://www.kernel.org/