Porteus

I was not lucky to compile.




I used the neko script and then tried to apply the patch modified by you.
I received several chunk error messages.

What steps did you use?
Did you apply only the patch modified by you?

Hi
I am not familiar with the workings of the "neko script" I'm afraid.
Applying the patch obtained from aufs on github gives 3 chunk errors for:
fs.h
mnt_namespace.h
read_write.c
Therefore, the github version of the patch has to be replaced by the amended version before the aufs patches are applied.
In the script that I am using, I did this by putting a read pause just before the aufs patches were applied and manually copied over the amended patches before proceeding.
If you are still getting chunk errors then I would surmise that the original github patch is being applied.
If the amended patch cannot be utilised by the "neko script" then you will have to wait for the official aufs-5.8 github download to become available. But I do know that neko has been able to utilise amended patches in the past, so you may find clues elsewhere in this thread on how to do so.

Thanks for the answer

Further testing of 5.8.3 with the amended patch shows a problem with Chromium throwing "bus errors" so patch is withdrawn - sorry!

Thanks for the feedback.
Anyway, the kernel I compiled with the patch crashed immediately after reading the first modules.

5.8.4 is released... seems to fix the problems seen with 5.8.3
+ there was a problem with the amended aufs patch I posted (sorry) - a new version is at:
https://u.pcloud.link/publink/show?code ... AqChaW2XoV

I applied the modified patch.
Compiled without appearing errors.
Dmesg without errors.
Apparently it's working properly
Tks.

I will continue watching the logs for a few days.

Does anyone want to try building NTFS3 kernel module for kernel 5.8.x
I found it here https://aur.archlinux.org/packages/ntfs3-dkms/

babam wrote: ↑

27 Aug 2020, 04:43

Does anyone want to try building NTFS3 kernel module for kernel 5.8.x

Hi babam I don't have experience using dkms

peebee wrote: ↑

26 Aug 2020, 16:00

5.8.4 is released... seems to fix the problems seen with 5.8.3

Hi peebee Are you managing to activate modules?
Activation of modules after boot is not working here.
I'm using it to get around: mloop and then copy the directory to root.

maia wrote: ↑

27 Aug 2020, 13:39

Hi babam I don't have experience using dkms

Hi maia, dkms is optional dependencies.

maia wrote: ↑

27 Aug 2020, 13:43

Activation of modules after boot is not working here.
I'm using it to get around: mloop and then copy the directory to root.

maia, Try activating a module outside of aufs (put a module on ext2/3/4, vfat or ntfs and then activate)

babam wrote: ↑

27 Aug 2020, 14:02

Hi maia, dkms is optional dependencies.

Not work...
root@porteus:/tmp/aaa# ./configure
configure: Building module name ufsd
configure: error: "Can't find kernel source files"
root@porteus:/tmp/aaa# ./configure --srcdir=/usr/src/linux
configure: Building module name ufsd
configure: error: "Can't find kernel source files"
root@porteus:/tmp/aaa#

babam wrote: ↑

27 Aug 2020, 14:09

maia, Try activating a module outside of aufs (put a module on ext2/3/4, vfat or ntfs and then activate)

Work outside of aufs, on ext4. tks

maia wrote: ↑

27 Aug 2020, 13:43

peebee wrote: ↑

26 Aug 2020, 16:00

5.8.4 is released... seems to fix the problems seen with 5.8.3

Hi peebee Are you managing to activate modules?
Activation of modules after boot is not working here.
I'm using it to get around: mloop and then copy the directory to root.

I seem to remember that I had to apply the aufs5-loopback.patch to the kernel. Then I was able to activate modules in the live system.