Porteus Kernel Builder

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
User avatar
Blaze
DEV Team
DEV Team
Posts: 2676
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#691 by Blaze » 02 Oct 2019, 17:39

Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#692 by neko » 06 Oct 2019, 04:25

Most recent versions of build examples were updated.
5.3.4, 5.2.19, 4.19.77

The kernel version 5.3.3 has been missed.

Note: Updating configs

Code: Select all

$ diff v5.3.4/64bit.config v5.3.4/64/linux-5.3.4/.config
3c3
< # Linux/x86 5.3.1 Kernel Configuration
---
> # Linux/x86 5.3.4 Kernel Configuration
909,911c909,911
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1325a1326
> CONFIG_FIB_RULES=y
$
$
$ diff v5.3.4/32bit.config v5.3.4/32/linux-5.3.4/.config
3c3
< # Linux/x86 5.3.1 Kernel Configuration
---
> # Linux/x86 5.3.4 Kernel Configuration
895,897c895,897
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1311a1312
> CONFIG_FIB_RULES=y
$
$
$ diff v5.2.19/64bit.config v5.2.19/64/linux-5.2.19/.config
3c3
< # Linux/x86 5.2.18 Kernel Configuration
---
> # Linux/x86 5.2.19 Kernel Configuration
894,896c894,896
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1309a1310
> CONFIG_FIB_RULES=y
$
$
$ diff v5.2.19/32bit.config v5.2.19/32/linux-5.2.19/.config
3c3
< # Linux/x86 5.2.18 Kernel Configuration
---
> # Linux/x86 5.2.19 Kernel Configuration
881,883c881,883
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1296a1297
> CONFIG_FIB_RULES=y
$ 
$
$ diff v4.19.77/64bit.config v4.19.77/64/linux-4.19.77/.config
3c3
< # Linux/x86 4.19.76 Kernel Configuration
---
> # Linux/x86 4.19.77 Kernel Configuration
926,928c926,928
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1343a1344
> CONFIG_FIB_RULES=y
$
$
$ diff v4.19.77/32bit.config v4.19.77/32/linux-4.19.77/.config
3c3
< # Linux/x86 4.19.76 Kernel Configuration
---
> # Linux/x86 4.19.77 Kernel Configuration
914,916c914,916
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1331a1332
> CONFIG_FIB_RULES=y
$

Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#693 by neko » 07 Oct 2019, 01:55

1. "Porteus Kernel Builder" was updated.
19.10.06
Configs were updated.


2. Most recent versions of build examples were updated.
5.4-rc2

Note 1: AUFS patch is not yet ready for kernel version 5.4-rc.
Error at
linux-5.4-rc2/mm/shmem.c
linux-5.4-rc2/fs/Kconfig
linux-5.4-rc2/fs/notify/group.c
linux-5.4-rc2/fs/notify/mark.c
linux-5.4-rc2/fs/Makefile
linux-5.4-rc2/kernel/locking/lockdep_internals.h

Code: Select all

# patch -p1 < ../../v5.4-rc2/aufs.patch
patching file Documentation/ABI/testing/debugfs-aufs
patching file Documentation/ABI/testing/sysfs-aufs
patching file Documentation/filesystems/aufs/README
patching file Documentation/filesystems/aufs/design/01intro.txt
patching file Documentation/filesystems/aufs/design/02struct.txt
patching file Documentation/filesystems/aufs/design/03atomic_open.txt
patching file Documentation/filesystems/aufs/design/03lookup.txt
patching file Documentation/filesystems/aufs/design/04branch.txt
patching file Documentation/filesystems/aufs/design/05wbr_policy.txt
patching file Documentation/filesystems/aufs/design/06dirren.dot
patching file Documentation/filesystems/aufs/design/06dirren.txt
patching file Documentation/filesystems/aufs/design/06fhsm.txt
patching file Documentation/filesystems/aufs/design/06mmap.txt
patching file Documentation/filesystems/aufs/design/06xattr.txt
patching file Documentation/filesystems/aufs/design/07export.txt
patching file Documentation/filesystems/aufs/design/08shwh.txt
patching file Documentation/filesystems/aufs/design/10dynop.txt
patching file fs/aufs/Kconfig
patching file fs/aufs/Makefile
patching file fs/aufs/aufs.h
patching file fs/aufs/branch.c
patching file fs/aufs/branch.h
patching file fs/aufs/conf.mk
patching file fs/aufs/cpup.c
patching file fs/aufs/cpup.h
patching file fs/aufs/dbgaufs.c
patching file fs/aufs/dbgaufs.h
patching file fs/aufs/dcsub.c
patching file fs/aufs/dcsub.h
patching file fs/aufs/debug.c
patching file fs/aufs/debug.h
patching file fs/aufs/dentry.c
patching file fs/aufs/dentry.h
patching file fs/aufs/dinfo.c
patching file fs/aufs/dir.c
patching file fs/aufs/dir.h
patching file fs/aufs/dirren.c
patching file fs/aufs/dirren.h
patching file fs/aufs/dynop.c
patching file fs/aufs/dynop.h
patching file fs/aufs/export.c
patching file fs/aufs/f_op.c
patching file fs/aufs/fhsm.c
patching file fs/aufs/file.c
patching file fs/aufs/file.h
patching file fs/aufs/finfo.c
patching file fs/aufs/fstype.h
patching file fs/aufs/hbl.h
patching file fs/aufs/hfsnotify.c
patching file fs/aufs/hfsplus.c
patching file fs/aufs/hnotify.c
patching file fs/aufs/i_op.c
patching file fs/aufs/i_op_add.c
patching file fs/aufs/i_op_del.c
patching file fs/aufs/i_op_ren.c
patching file fs/aufs/iinfo.c
patching file fs/aufs/inode.c
patching file fs/aufs/inode.h
patching file fs/aufs/ioctl.c
patching file fs/aufs/lcnt.h
patching file fs/aufs/loop.c
patching file fs/aufs/loop.h
patching file fs/aufs/magic.mk
patching file fs/aufs/module.c
patching file fs/aufs/module.h
patching file fs/aufs/mvdown.c
patching file fs/aufs/opts.c
patching file fs/aufs/opts.h
patching file fs/aufs/plink.c
patching file fs/aufs/poll.c
patching file fs/aufs/posix_acl.c
patching file fs/aufs/procfs.c
patching file fs/aufs/rdu.c
patching file fs/aufs/rwsem.h
patching file fs/aufs/sbinfo.c
patching file fs/aufs/super.c
patching file fs/aufs/super.h
patching file fs/aufs/sysaufs.c
patching file fs/aufs/sysaufs.h
patching file fs/aufs/sysfs.c
patching file fs/aufs/sysrq.c
patching file fs/aufs/vdir.c
patching file fs/aufs/vfsub.c
patching file fs/aufs/vfsub.h
patching file fs/aufs/wbr_policy.c
patching file fs/aufs/whout.c
patching file fs/aufs/whout.h
patching file fs/aufs/wkq.c
patching file fs/aufs/wkq.h
patching file fs/aufs/xattr.c
patching file fs/aufs/xino.c
patching file include/uapi/linux/aufs_type.h
patching file MAINTAINERS
Hunk #1 succeeded at 2834 (offset 12 lines).
patching file drivers/block/loop.c
patching file fs/dcache.c
patching file fs/fcntl.c
patching file fs/inode.c
Hunk #1 succeeded at 1673 (offset 3 lines).
patching file fs/namespace.c
patching file fs/read_write.c
patching file fs/splice.c
patching file fs/sync.c
patching file include/linux/fs.h
Hunk #1 succeeded at 1349 (offset 18 lines).
Hunk #2 succeeded at 1836 (offset 25 lines).
Hunk #3 succeeded at 1907 (offset 25 lines).
Hunk #4 succeeded at 2333 (offset 27 lines).
Hunk #5 succeeded at 2622 (offset 27 lines).
patching file include/linux/lockdep.h
Hunk #1 succeeded at 331 (offset -3 lines).
Hunk #2 succeeded at 475 (offset -3 lines).
patching file include/linux/mnt_namespace.h
patching file include/linux/splice.h
patching file kernel/locking/lockdep.c
patching file fs/Kconfig
Hunk #1 FAILED at 261.
1 out of 1 hunk FAILED -- saving rejects to file fs/Kconfig.rej
patching file fs/Makefile
Hunk #1 FAILED at 130.
1 out of 1 hunk FAILED -- saving rejects to file fs/Makefile.rej
patching file drivers/block/loop.c
Hunk #10 succeeded at 1085 (offset 10 lines).
Hunk #11 succeeded at 1133 (offset 10 lines).
Hunk #12 succeeded at 1157 (offset 10 lines).
Hunk #13 succeeded at 1240 (offset 10 lines).
patching file drivers/block/loop.h
patching file fs/aufs/f_op.c
Hunk #1 succeeded at 369 (offset 10 lines).
patching file fs/aufs/loop.c
Hunk #1 succeeded at 146 (offset 13 lines).
patching file fs/aufs/loop.h
Hunk #1 succeeded at 39 (offset 13 lines).
Hunk #2 succeeded at 51 (offset 13 lines).
patching file fs/aufs/super.c
Hunk #1 succeeded at 857 (offset 13 lines).
patching file include/linux/fs.h
Hunk #1 succeeded at 1973 (offset 25 lines).
patching file fs/proc/base.c
patching file fs/proc/nommu.c
patching file fs/proc/task_mmu.c
Hunk #2 succeeded at 1822 with fuzz 2 (offset 12 lines).
patching file fs/proc/task_nommu.c
patching file include/linux/mm.h
Hunk #1 succeeded at 1515 (offset -23 lines).
patching file include/linux/mm_types.h
patching file kernel/fork.c
Hunk #1 succeeded at 562 (offset 9 lines).
patching file mm/Makefile
Hunk #1 succeeded at 42 (offset 3 lines).
patching file mm/filemap.c
Hunk #1 succeeded at 2695 (offset -26 lines).
patching file mm/mmap.c
Hunk #2 succeeded at 940 (offset 9 lines).
Hunk #3 succeeded at 1865 (offset 18 lines).
Hunk #4 succeeded at 2695 (offset 15 lines).
Hunk #5 succeeded at 2714 (offset 15 lines).
Hunk #6 succeeded at 2906 (offset 16 lines).
Hunk #7 succeeded at 2981 (offset 16 lines).
Hunk #8 succeeded at 3291 (offset 16 lines).
patching file mm/nommu.c
patching file mm/prfile.c
patching file fs/dcache.c
patching file fs/exec.c
patching file fs/fcntl.c
patching file fs/file_table.c
Hunk #2 succeeded at 313 with fuzz 2 (offset -15 lines).
Hunk #3 succeeded at 377 (offset 1 line).
patching file fs/inode.c
Hunk #1 succeeded at 1682 (offset 3 lines).
patching file fs/namespace.c
Hunk #3 succeeded at 1905 (offset 3 lines).
patching file fs/notify/group.c
Hunk #2 FAILED at 109.
Hunk #3 FAILED at 138.
2 out of 3 hunks FAILED -- saving rejects to file fs/notify/group.c.rej
patching file fs/notify/mark.c
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file fs/notify/mark.c.rej
patching file fs/open.c
patching file fs/read_write.c
patching file fs/splice.c
patching file fs/sync.c
patching file fs/xattr.c
patching file kernel/locking/lockdep.c
patching file kernel/task_work.c
patching file security/device_cgroup.c
patching file security/security.c
Hunk #1 succeeded at 1036 (offset 40 lines).
Hunk #2 succeeded at 1053 (offset 40 lines).
Hunk #3 succeeded at 1062 (offset 40 lines).
Hunk #4 succeeded at 1090 (offset 40 lines).
Hunk #5 succeeded at 1098 (offset 40 lines).
Hunk #6 succeeded at 1106 (offset 40 lines).
Hunk #7 succeeded at 1207 (offset 40 lines).
Hunk #8 succeeded at 1385 (offset 40 lines).
patching file include/linux/lockdep.h
patching file kernel/locking/lockdep.c
Hunk #1 succeeded at 4767 (offset 75 lines).
patching file kernel/locking/lockdep_internals.h
Hunk #1 FAILED at 93.
1 out of 1 hunk FAILED -- saving rejects to file kernel/locking/lockdep_internals.h.rej
patching file fs/mount.h
patching file fs/namespace.c
Hunk #1 succeeded at 1254 (offset 8 lines).
patching file fs/proc_namespace.c
patching file include/linux/shmem_fs.h
patching file mm/shmem.c
Hunk #1 succeeded at 128 (offset 15 lines).
Hunk #2 succeeded at 1115 (offset 15 lines).
Hunk #3 succeeded at 2244 (offset 15 lines).
Hunk #4 succeeded at 2294 (offset 15 lines).
Hunk #5 succeeded at 3318 (offset 15 lines).
Hunk #6 succeeded at 3338 (offset 15 lines).
Hunk #7 succeeded at 3354 (offset 15 lines).
Hunk #8 FAILED at 3411.
Hunk #9 FAILED at 3476.
Hunk #10 succeeded at 3594 (offset 69 lines).
Hunk #11 succeeded at 3618 (offset 69 lines).
Hunk #12 FAILED at 3569.
Hunk #13 succeeded at 3771 (offset 97 lines).
Hunk #14 succeeded at 3920 (offset 110 lines).
3 out of 14 hunks FAILED -- saving rejects to file mm/shmem.c.rej
patching file fs/inode.c
Hunk #1 succeeded at 885 (offset 3 lines).
Hunk #2 succeeded at 899 (offset 3 lines).
It was patched by manual as follow.
(1) same as /usr/local/share/mkKernel/bin/aufsBase.sh without patching aufs5-kbuild.patch.
(2) same as /usr/local/share/mkKernel/bin/aufsOption.sh
(3) change fs/Kconfig and fs/Makefile

Code: Select all

# diff old/fs/Kconfig new/fs/Kconfig
266a267
> source "fs/aufs/Kconfig"
#
#
# diff old/fs/Makefile new/fs/Makefile
134a135
> obj-$(CONFIG_AUFS_FS)           += aufs/

Note 2: Updating configs

Code: Select all

$ diff v5.4-rc2/32bit.config v5.4-rc2/32/linux-5.4-rc2/.config
3c3
< # Linux/x86 5.4.0-rc1 Kernel Configuration
---
> # Linux/x86 5.4.0-rc2 Kernel Configuration
902,904c902,904
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1318a1319
> CONFIG_FIB_RULES=y
6120a6122,6141
> CONFIG_AUFS_FS=y
> # CONFIG_AUFS_BRANCH_MAX_127 is not set
> CONFIG_AUFS_BRANCH_MAX_511=y
> # CONFIG_AUFS_BRANCH_MAX_1023 is not set
> # CONFIG_AUFS_BRANCH_MAX_32767 is not set
> CONFIG_AUFS_SBILIST=y
> CONFIG_AUFS_HNOTIFY=y
> CONFIG_AUFS_HFSNOTIFY=y
> CONFIG_AUFS_EXPORT=y
> CONFIG_AUFS_XATTR=y
> CONFIG_AUFS_FHSM=y
> CONFIG_AUFS_RDU=y
> CONFIG_AUFS_DIRREN=y
> CONFIG_AUFS_SHWH=y
> CONFIG_AUFS_BR_RAMFS=y
> CONFIG_AUFS_BR_FUSE=y
> CONFIG_AUFS_POLL=y
> CONFIG_AUFS_BR_HFSPLUS=y
> CONFIG_AUFS_BDEV_LOOP=y
> # CONFIG_AUFS_DEBUG is not set
$
$
$ diff v5.4-rc2/64bit.config v5.4-rc2/64/linux-5.4-rc2/.config
3c3
< # Linux/x86 5.4.0-rc1 Kernel Configuration
---
> # Linux/x86 5.4.0-rc2 Kernel Configuration
915,917c915,917
< # CONFIG_IP_MULTIPLE_TABLES is not set
< # CONFIG_IP_ROUTE_MULTIPATH is not set
< # CONFIG_IP_ROUTE_VERBOSE is not set
---
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_MULTIPATH=y
> CONFIG_IP_ROUTE_VERBOSE=y
1331a1332
> CONFIG_FIB_RULES=y
6146a6148,6168
> CONFIG_AUFS_FS=y
> # CONFIG_AUFS_BRANCH_MAX_127 is not set
> CONFIG_AUFS_BRANCH_MAX_511=y
> # CONFIG_AUFS_BRANCH_MAX_1023 is not set
> # CONFIG_AUFS_BRANCH_MAX_32767 is not set
> CONFIG_AUFS_SBILIST=y
> CONFIG_AUFS_HNOTIFY=y
> CONFIG_AUFS_HFSNOTIFY=y
> CONFIG_AUFS_EXPORT=y
> CONFIG_AUFS_INO_T_64=y
> CONFIG_AUFS_XATTR=y
> CONFIG_AUFS_FHSM=y
> CONFIG_AUFS_RDU=y
> CONFIG_AUFS_DIRREN=y
> CONFIG_AUFS_SHWH=y
> CONFIG_AUFS_BR_RAMFS=y
> CONFIG_AUFS_BR_FUSE=y
> CONFIG_AUFS_POLL=y
> CONFIG_AUFS_BR_HFSPLUS=y
> CONFIG_AUFS_BDEV_LOOP=y
> # CONFIG_AUFS_DEBUG is not set

3. The example of replacement the kernel of another distri which uses OverlayFS/AUFS was updated.
austrumi 4.0.8 + kernel 5.4-rc2


Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2676
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#694 by Blaze » 07 Oct 2019, 16:55

neko, these options:

Code: Select all

CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
are must to be enabled by default for all build of your kernels.

Thanks :thumbup:
Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#695 by neko » 07 Oct 2019, 23:53

@Blaze

The kernel configuration currently built as an example is as follows.

Code: Select all

% grep CONFIG_IP_ADVANCED_ROUTER /usr/local/share/mkKernel/lib/v*/*.config|grep -v not
/usr/local/share/mkKernel/lib/v4.19/32bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v4.19/64bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.2-rc/32bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.2-rc/64bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.2/32bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.2/64bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.3-rc/32bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.3-rc/64bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.3/32bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.3/64bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.4-rc/32bit.config:CONFIG_IP_ADVANCED_ROUTER=y
/usr/local/share/mkKernel/lib/v5.4-rc/64bit.config:CONFIG_IP_ADVANCED_ROUTER=y
%
%
% grep CONFIG_IP_MULTIPLE_TABLES /usr/local/share/mkKernel/lib/v*/*.config|grep -v not
/usr/local/share/mkKernel/lib/v4.19/32bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v4.19/64bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.2-rc/32bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.2-rc/64bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.2/32bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.2/64bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.3-rc/32bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.3-rc/64bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.3/32bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.3/64bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.4-rc/32bit.config:CONFIG_IP_MULTIPLE_TABLES=y
/usr/local/share/mkKernel/lib/v5.4-rc/64bit.config:CONFIG_IP_MULTIPLE_TABLES=y
%
%
% grep CONFIG_IP_ROUTE_MULTIPATH /usr/local/share/mkKernel/lib/v*/*.config|grep -v not
/usr/local/share/mkKernel/lib/v4.19/32bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v4.19/64bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.2-rc/32bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.2-rc/64bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.2/32bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.2/64bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.3-rc/32bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.3-rc/64bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.3/32bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.3/64bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.4-rc/32bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
/usr/local/share/mkKernel/lib/v5.4-rc/64bit.config:CONFIG_IP_ROUTE_MULTIPATH=y
%
%
% grep CONFIG_IP_ROUTE_VERBOSE /usr/local/share/mkKernel/lib/v*/*.config|grep -v not
/usr/local/share/mkKernel/lib/v4.19/32bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v4.19/64bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.2-rc/32bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.2-rc/64bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.2/32bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.2/64bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.3-rc/32bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.3-rc/64bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.3/32bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.3/64bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.4-rc/32bit.config:CONFIG_IP_ROUTE_VERBOSE=y
/usr/local/share/mkKernel/lib/v5.4-rc/64bit.config:CONFIG_IP_ROUTE_VERBOSE=y
in "Porteus Kernel Builder 19.10.06".


Thanks.

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#696 by neko » 08 Oct 2019, 10:27

Most recent versions of build examples were updated.
5.3.5, 5.2.20, 4.19.78

Note 1: Compiler that was used.
gcc-9.2.0-x86_64-2

Note 2: Firmware database that was used.
linux-firmware-20190923.417a9c6-noarch-1plus.xzm
It will be uploaded at the next "Porteus Kernel Builder" update.


Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

fulalas
DEV Team
DEV Team
Posts: 1454
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus Kernel Builder

Post#697 by fulalas » 10 Oct 2019, 06:48

Kernel 5.4 definitely fixes the black screen issue some users (including me) were facing (more info here). Cool! :)

fulalas
DEV Team
DEV Team
Posts: 1454
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus Kernel Builder

Post#698 by fulalas » 10 Oct 2019, 08:57

BTW, has anyone managed to build a Nvidia driver for this kernel 5.4 RC2?

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#699 by neko » 10 Oct 2019, 09:20

@fulalas
Thank you very much for your report.
AUFS patch for 5.4-rc2 has been applied by manual.
I expect its update at appling it to next 5.4-rc3.

I have no skill to introduce "Nvidia" into kernel.
Someone who will introduce Nvidia into kernel 5.4-rc,
please be care to patching "AUFS patch" by refering the #693 article.

Thanks.


BTW
Because the security issue of WEB access, yesterday my PC time (Japanese local time) was refused by Porteus forum site.
I think that it might be better to accept the world wide local time.

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#700 by neko » 12 Oct 2019, 06:09

1. "Porteus Kernel Builder" was updated.
19.10.09

Firmware database was updated with following packages.
ipw2100-fw-1.3-noarch-9
ipw2200-fw-3.1-noarch-7
linux-firmware-20190923.417a9c6-noarch-1
wireless-regdb-2019.06.03-noarch-1
alsa-firmware-1.0.29-noarch-2
linux-atm-2.5.2-x86_64-6

2. Most recent versions of build examples were updated.
5.3.6, 5.2.21, 4.19.79


Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2676
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#701 by Blaze » 13 Oct 2019, 10:29

Hi neko.
Can you set these parameters by default for your kernel builds?

make menuconfig ---> File Systems ---> Network File Systems (NEW) ---> SMB3 and CIFS support (advanced network filesystem) (NEW) ---> press m ---> ans set y for these options:

Image

Image

Code: Select all

CONFIG_CIFS=m
# CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y
CONFIG_CIFS_WEAK_PW_HASH=y
# CONFIG_CIFS_UPCALL is not set
# CONFIG_CIFS_XATTR is not set
CONFIG_CIFS_DEBUG=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_DEBUG_DUMP_KEYS is not set
CONFIG_CIFS_DFS_UPCALL=y
__________
BTW I not able to find these options:

Code: Select all

CONFIG_CIFS_SMB2=y
CONFIG_CIFS_SMB311=y
CONFIG_CIFS_FSCACHE=y
Probably in kernel 5 is dropped these options.

Thanks.

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#702 by neko » 14 Oct 2019, 08:26

1. Most recent versions of build examples were updated.
5.4.0-rc3

Note 1: AUFS patch "5.x-rcN-20191014" is not yet ready for kernel version 5.4-rc.
It was patched by manual as same as patching to kernel version 5.4.0-rc2.
Porteus Kernel Builder (Post by neko #74116)

Note 2: Updating configs

Code: Select all

$ diff v5.4-rc3/32bit.config v5.4-rc3/32/linux-5.4-rc3/.config
3c3
< # Linux/x86 5.4.0-rc2 Kernel Configuration
---
> # Linux/x86 5.4.0-rc3 Kernel Configuration
7c7
< # Compiler: gcc (GCC) 9.1.0
---
> # Compiler: gcc (GCC) 9.2.0
10c10
< CONFIG_GCC_VERSION=90100
---
> CONFIG_GCC_VERSION=90200
5179d5178
< CONFIG_USB_RIO500=m
5617d5615
< # CONFIG_FB_TFT is not set
6180,6181c6178,6180
< CONFIG_CIFS_STATS2=y
< # CONFIG_CIFS_ALLOW_INSECURE_LEGACY is not set
---
> # CONFIG_CIFS_STATS2 is not set
> CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y
> CONFIG_CIFS_WEAK_PW_HASH=y
6183,6185c6182,6186
< CONFIG_CIFS_XATTR=y
< # CONFIG_CIFS_DEBUG is not set
< # CONFIG_CIFS_DFS_UPCALL is not set
---
> # CONFIG_CIFS_XATTR is not set
> CONFIG_CIFS_DEBUG=y
> # CONFIG_CIFS_DEBUG2 is not set
> # CONFIG_CIFS_DEBUG_DUMP_KEYS is not set
> CONFIG_CIFS_DFS_UPCALL=y
$
$
$ diff v5.4-rc3/64bit.config v5.4-rc3/64/linux-5.4-rc3/.config
3c3
< # Linux/x86 5.4.0-rc2 Kernel Configuration
---
> # Linux/x86 5.4.0-rc3 Kernel Configuration
7c7
< # Compiler: gcc (GCC) 9.1.0
---
> # Compiler: gcc (GCC) 9.2.0
10c10
< CONFIG_GCC_VERSION=90100
---
> CONFIG_GCC_VERSION=90200
5183d5182
< CONFIG_USB_RIO500=m
5623d5621
< # CONFIG_FB_TFT is not set
6207,6208c6205,6207
< CONFIG_CIFS_STATS2=y
< # CONFIG_CIFS_ALLOW_INSECURE_LEGACY is not set
---
> # CONFIG_CIFS_STATS2 is not set
> CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y
> CONFIG_CIFS_WEAK_PW_HASH=y
6210,6212c6209,6213
< CONFIG_CIFS_XATTR=y
< # CONFIG_CIFS_DEBUG is not set
< # CONFIG_CIFS_DFS_UPCALL is not set
---
> # CONFIG_CIFS_XATTR is not set
> CONFIG_CIFS_DEBUG=y
> # CONFIG_CIFS_DEBUG2 is not set
> # CONFIG_CIFS_DEBUG_DUMP_KEYS is not set
> CONFIG_CIFS_DFS_UPCALL=y
$
$
$ grep CONFIG_CIFS_FSCACHE v5.4-rc3/32/linux-5.4-rc3/.config v5.4-rc3/64/linux-5.4-rc3/.config
v5.4-rc3/32/linux-5.4-rc3/.config:CONFIG_CIFS_FSCACHE=y
v5.4-rc3/64/linux-5.4-rc3/.config:CONFIG_CIFS_FSCACHE=y
$

2. The example of replacement the kernel of another distri which uses OverlayFS/AUFS was updated.
austrumi 4.0.9 + kernel 5.4-rc3



Please refer to the top article of this thread.
Porteus Kernel Builder


Thanks.
-----------------------------
@Blaze
The kernel configuration currently built as an example was updated as your request.

For 5.3 and 5.2, ones will be updated at kernel 5.3/5.2 update.


Thanks.
-----------------------------
@All
[Kernel config prototypes updating policy]
Updating the config is set with almost new spec items "N".
Because it prevent to grow the size of kernel.
Some spec items that were requested are set with "M" or "Y".
Setting with "Y" is only for boot devices.

The spec item concerning network is set with "M".
Because a network is set up after boot.
If network booting is used,
in initrd, 000-kernel.xzm module will be activated and the needed driver is included.
therefor naming "000-kernel.xzm" is reserved.
(I don't know that new Porteus initrd performs same.)

All spec items concerning debug are set with "N".


Thanks.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2676
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus Kernel Builder

Post#703 by Blaze » 14 Oct 2019, 19:13

neko, I just found these options in .config of Slackware for test.

Ok, I tested your a new build of kernel 5.4.0-rc3 and mount.cifs for mount shares.
Everything that I need for mount.cifs now works great. Thank you so much! :friends:

My conclusion is that you can disable these options:

Code: Select all

CONFIG_CIFS_WEAK_PW_HASH # Allows the cifs module to mount to older LANMAN based servers such as OS/2 and Windows 95
CONFIG_CIFS_DEBUG # All spec items concerning debug are set with "N".
Image
Image
Linux 5.4.0-rc7-porteus #2 SMP Tue Nov 12 17:45:45 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

fulalas
DEV Team
DEV Team
Posts: 1454
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Porteus Kernel Builder

Post#704 by fulalas » 17 Oct 2019, 20:22

Stupid question: when AUFS is not present, what does it mean to the user?

neko
DEV Team
DEV Team
Posts: 1540
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#705 by neko » 18 Oct 2019, 01:45

@fulalas

The cases where the AUFS function is not in the kernel are below.

1. Porteus can't boot, so users can't use Porteus.

2. Porteus can boot if initrd is modified to multiplex XZM modules with OverlayFS functionality.
In this case, however, the XZM module cannot be dynamically activated or deactivated after the boot.

3. A prototype version of the initrd that can be booted with OverlayFS without using AUFS is now available.
This modification is not yet done after the boot up.
For this reason, the function to dynamically insert and remove the XZM module does not work.
Nor does it care for utilities that have the process of activating or deactivating XZM.

Please refer to [How to replace kernel of ISO with Overlay FS Kernel] of
Porteus Kernel Builder (Post by neko #52232)


Thanks.

Post Reply