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...
neko
DEV Team
DEV Team
Posts: 1450
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Porteus Kernel Builder

Post#496 by neko » 14 Mar 2019, 17:02

@user0815
Could you upload the ISO that booted successful from you PC SD card ?
If you will do, I will download it and study the its kernel.
And then I report you about the result.

Thanks.

User avatar
user0815
Black ninja
Black ninja
Posts: 63
Joined: 22 Jan 2019, 11:46
Distribution: CINNAMON-v4.0-x86_64

Porteus Kernel Builder

Post#497 by user0815 » 14 Mar 2019, 17:55

@neko,
it’s porteus v3.2.2 from here
http://dl.porteus.org/x86_64/Porteus-v3 ... x86_64.iso
Thank you
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

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

Porteus Kernel Builder

Post#498 by neko » 15 Mar 2019, 14:54

@user0815

1. I do confirm again.
----------------
Replace
Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso@boot/syslinux/vmlinuz
Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso@porteus/base/000-kernel.xzm
with
Porteus-XFCE-v3.2.2-x86_64.iso@boot/syslinux/vmlinuz
Porteus-XFCE-v3.2.2-x86_64.iso@porteus/base/000-kernel.xzm

This NEW.iso booted successful from your PC SD card.
----------------
Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso
http://www.mediafire.com/file/0dz5sutrt ... .01.12.iso

Porteus-XFCE-v3.2.2-x86_64.iso
http://dl.porteus.org/x86_64/Porteus-v3 ... x86_64.iso


2. The kernel of Porteus-XFCE-v3.2.2-x86_64.iso
is kernel version 4.9.0.
I got the config (4.9.0-64bit.config) from Porteus-XFCE-v3.2.2-x86_64.iso running.


3. AUFS patch for 4.9 line (AUFS_VERSION "4.9-20180730")
is not adapted correctly to "drivers/block/loop.c & mm/shmem.c" of kernel 4.9.163.

It might not be maintenanced more.

I prepared own patches of "drivers/block/loop.c & mm/shmem.c" for avoiding syntax error.
own.patch.drivers+block+loop.c
own.patch.mm+shmem.c
Therefore these none-official patches are not assured.

[AUFS patch error]

Code: Select all

# patch -p1 < ../../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/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
patching file drivers/block/loop.c
Hunk #1 succeeded at 729 with fuzz 1 (offset 28 lines).
patching file fs/dcache.c
Hunk #1 succeeded at 1198 (offset 34 lines).
patching file fs/fcntl.c
patching file fs/inode.c
Hunk #1 succeeded at 1643 (offset 1 line).
patching file fs/namespace.c
Hunk #1 succeeded at 799 (offset 12 lines).
patching file fs/read_write.c
Hunk #1 succeeded at 517 (offset 2 lines).
patching file fs/splice.c
Hunk #1 succeeded at 856 (offset 1 line).
Hunk #2 succeeded at 873 (offset 1 line).
patching file fs/sync.c
patching file include/linux/file.h
patching file include/linux/fs.h
Hunk #1 succeeded at 1299 (offset 8 lines).
Hunk #2 succeeded at 1725 (offset 9 lines).
Hunk #3 succeeded at 1779 (offset 9 lines).
Hunk #4 succeeded at 2157 (offset 9 lines).
Hunk #5 succeeded at 2437 (offset 9 lines).
patching file include/linux/mnt_namespace.h
patching file include/linux/splice.h
patching file fs/Kconfig
patching file fs/Makefile
patching file include/uapi/linux/Kbuild
patching file drivers/block/loop.c
Hunk #1 succeeded at 552 (offset 1 line).
Hunk #2 succeeded at 578 (offset 1 line).
Hunk #3 succeeded at 591 (offset 1 line).
Hunk #4 FAILED at 615.
Hunk #5 succeeded at 686 (offset 34 lines).
Hunk #6 FAILED at 669.
Hunk #7 succeeded at 718 (offset 35 lines).
Hunk #8 FAILED at 884.
Hunk #9 succeeded at 928 (offset 29 lines).
Hunk #10 succeeded at 970 (offset 13 lines).
Hunk #11 succeeded at 1003 (offset 13 lines).
Hunk #12 succeeded at 1051 (offset 13 lines).
Hunk #13 succeeded at 1083 (offset 13 lines).
Hunk #14 succeeded at 1128 with fuzz 1 (offset 13 lines).
3 out of 14 hunks FAILED -- saving rejects to file drivers/block/loop.c.rej
patching file drivers/block/loop.h
patching file fs/aufs/f_op.c
Hunk #1 succeeded at 367 (offset 10 lines).
patching file fs/aufs/loop.c
Hunk #1 succeeded at 145 (offset 13 lines).
patching file fs/aufs/loop.h
Hunk #1 succeeded at 38 (offset 13 lines).
Hunk #2 succeeded at 50 (offset 13 lines).
patching file fs/aufs/super.c
Hunk #1 succeeded at 848 (offset 13 lines).
patching file include/linux/fs.h
Hunk #1 succeeded at 1832 (offset 9 lines).
patching file fs/proc/base.c
Hunk #1 succeeded at 1990 (offset 37 lines).
patching file fs/proc/nommu.c
patching file fs/proc/task_mmu.c
Hunk #2 succeeded at 1633 (offset 3 lines).
patching file fs/proc/task_nommu.c
patching file include/linux/mm.h
Hunk #1 succeeded at 1271 (offset 5 lines).
patching file include/linux/mm_types.h
patching file kernel/fork.c
Hunk #1 succeeded at 633 (offset 9 lines).
patching file mm/Makefile
patching file mm/filemap.c
Hunk #1 succeeded at 2311 (offset 7 lines).
patching file mm/memory.c
Hunk #1 succeeded at 2124 (offset 7 lines).
patching file mm/mmap.c
Hunk #2 succeeded at 893 (offset 14 lines).
Hunk #3 succeeded at 1773 (offset 46 lines).
Hunk #4 succeeded at 2602 (offset 69 lines).
Hunk #5 succeeded at 2621 (offset 69 lines).
Hunk #6 succeeded at 2772 (offset 69 lines).
Hunk #7 succeeded at 2847 (offset 69 lines).
Hunk #8 succeeded at 3143 (offset 70 lines).
patching file mm/nommu.c
patching file mm/prfile.c
patching file fs/dcache.c
Hunk #1 succeeded at 1306 (offset 34 lines).
Hunk #2 succeeded at 2925 (offset 69 lines).
patching file fs/exec.c
patching file fs/fcntl.c
patching file fs/file_table.c
patching file fs/inode.c
Hunk #1 succeeded at 1652 (offset 1 line).
patching file fs/namespace.c
Hunk #1 succeeded at 467 (offset 1 line).
Hunk #2 succeeded at 805 (offset 12 lines).
Hunk #3 succeeded at 1902 (offset 71 lines).
patching file fs/notify/group.c
patching file fs/notify/mark.c
patching file fs/open.c
patching file fs/read_write.c
Hunk #1 succeeded at 527 (offset 2 lines).
Hunk #2 succeeded at 539 (offset 2 lines).
patching file fs/splice.c
Hunk #1 succeeded at 869 (offset 1 line).
Hunk #2 succeeded at 899 (offset 1 line).
patching file fs/sync.c
patching file fs/xattr.c
patching file kernel/task_work.c
patching file security/commoncap.c
patching file security/device_cgroup.c
patching file security/security.c
patching file include/linux/lockdep.h
patching file kernel/locking/lockdep_internals.h
patching file include/linux/shmem_fs.h
patching file mm/shmem.c
Hunk #2 succeeded at 1085 (offset 39 lines).
Hunk #3 succeeded at 2128 (offset 31 lines).
Hunk #4 FAILED at 2145.
Hunk #5 succeeded at 3250 (offset 31 lines).
Hunk #6 succeeded at 3261 (offset 31 lines).
Hunk #7 succeeded at 3277 (offset 31 lines).
Hunk #8 succeeded at 3349 (offset 31 lines).
Hunk #9 succeeded at 3414 (offset 31 lines).
Hunk #10 succeeded at 3463 (offset 31 lines).
Hunk #11 succeeded at 3557 (offset 31 lines).
Hunk #12 succeeded at 3577 (offset 31 lines).
Hunk #13 succeeded at 3686 (offset 31 lines).
Hunk #14 succeeded at 3827 with fuzz 1 (offset 31 lines).
1 out of 14 hunks FAILED -- saving rejects to file mm/shmem.c.rej
patching file fs/inode.c
Hunk #1 succeeded at 856 (offset 1 line).
Hunk #2 succeeded at 870 (offset 1 line).
#

4. config was updated by "make oldconfig" command with the following spec.

Code: Select all

Permanently enable BPF JIT and remove BPF interpreter (BPF_JIT_ALWAYS_ON) [N/y/?] (NEW) N
Avoid speculative indirect branches in kernel (RETPOLINE) [Y/n/?] (NEW) n
Distributed Switch Architecture (NET_DSA) [N/m/y/?] (NEW) N
Workaround for rename(2)-ing a directory (AUFS_DIRREN) [N/y/?] (NEW) y
Remove the kernel mapping in user mode (PAGE_TABLE_ISOLATION) [Y/n/?] (NEW) Y

5. build kernel 4.9.163
64bit-kernel4.9.163.tar (78 M)
http://www.mediafire.com/file/29135d7pc ... .9.163.tar
md5sum: 6a66f22ca380fceeb263b7ad7e970237 64bit-kernel4.9.163.tar

[contents]
vmlinuz
000-kernel.xzm
06-crippled_sources-4.9.163-64bit.xzm

64bit.config:............updated config
4.9.0-64bit.config:......original config

aufs.patch:........................Aufs patch (AUFS_VERSION "4.9-20180730")
org.drivers+block+loop.c:..........original source file of drivers/block/loop.c
org.mm+shmem.c:....................original source file of mm/shmem.c
auf.patch.drivers+block+loop.c:....aufs error patched source file of drivers/block/loop.c
auf.patch.mm+shmem.c:..............aufs error patched source file of mm/shmem.c
own.patch.drivers+block+loop.c:....new source file of drivers/block/loop.c
own.patch.mm+shmem.c:..............new source file of mm/shmem.c


Note:
firmware of 000-kernel.xzm is overwitten with 3 kind firmware.
base : the firmware of Porteus-XFCE-v3.2.2-x86_64.iso
2rd : firmware from firmware pool
top : make-building firmware


6. update of 4.9 line kernel
Please update by yourself with "Kernel builder" tool,
using items.
64bit-kernel4.9.163.tar@own.patch.drivers+block+loop.c
64bit-kernel4.9.163.tar@own.patch.mm+shmem.c
64bit-kernel4.9.163.tar@64bit.config


Thanks.

User avatar
user0815
Black ninja
Black ninja
Posts: 63
Joined: 22 Jan 2019, 11:46
Distribution: CINNAMON-v4.0-x86_64

Porteus Kernel Builder

Post#499 by user0815 » 15 Mar 2019, 21:02

@neko, you are awesome, Sir.

Code: Select all

guest@porteus:~$ uname -r
4.9.163-porteus
guest@porteus:~$ 
now I have the latest kernel 4.9.xxx booting from my sd card. Thank you very much. Will try to learn how to compile next kernel myself.
Cheers
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

User avatar
user0815
Black ninja
Black ninja
Posts: 63
Joined: 22 Jan 2019, 11:46
Distribution: CINNAMON-v4.0-x86_64

Porteus Kernel Builder

Post#500 by user0815 » 17 Mar 2019, 15:28

Dear @neko,
Can I request you for another test to fix the issue with SD card in the latest kernel?
neko wrote:
12 Mar 2019, 04:07
@jssouza
"Would it be possible to make CONFIG_MFD_RTSX_PCI=y in the kernel? "
---> No, it would not.
I believe the reason for your answer is that the config option CONFIG_MFD_RTSX_PCI does not exist anymore in linux kernel 4.16 and later. This was also indicated by the output of your

Code: Select all

$ grep CONFIG_MFD_RTSX_PCI /usr/local/share/mkKernel/lib/v*/*config
in this post #478.
After searching around the net, I found this solution from someone having similar problem with SD card like I do:
https://forums.funtoo.org/topic/1693-he ... rd-reader/
So would it possible that we do another try by enabling the config CONFIG_MISC_RTSX_PCI and CONFIG_MMC_REALTEK_PCI to y?
According to the the post in funtoo forum, the CONFIG_MMC_REALTEK_PCI was only revealed after enabling the config CONFIG_MISC_RTSX_PCI

Thanks a lot in advance.
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

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

Porteus Kernel Builder

Post#501 by neko » 18 Mar 2019, 06:29

"Porteus Kernel Builder" was updated to mkKernel-19.03.18-noarch-1.xzm
Please refer to Porteus Kernel Builder (Post by neko #52232)

mkKernel-19.03.18-noarch-1.xzm (5 M)
http://simosnet.com/livecd/isobuilder/k ... arch-1.xzm
md5sum: ab3b27db47d9a2b50673ad958213199a mkKernel-19.03.18-noarch-1.xzm

(1) 5.0, 4.20, & 4.19 configs were changed.

Code: Select all

1523c1523
< CONFIG_MISC_RTSX=m
---
> CONFIG_MISC_RTSX=y
1594c1594
< CONFIG_MISC_RTSX_PCI=m
---
> CONFIG_MISC_RTSX_PCI=y
5053c5053
< CONFIG_MMC_REALTEK_PCI=m
---
> CONFIG_MMC_REALTEK_PCI=y
(2) 5.1-rc line was added.
(2-1) AUFS patch is not yet ready. Therefore "5.x-rcN" will be used.
AUFS_VERSION "5.x-rcN-20190311" are not yet adapted correctly to patch to kernel/locking/lockdep.c.

Code: Select all

# patch -p1 < ../../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 2698 (offset 63 lines).
patching file drivers/block/loop.c
patching file fs/dcache.c
patching file fs/fcntl.c
patching file fs/inode.c
patching file fs/namespace.c
Hunk #1 succeeded at 769 (offset 1 line).
patching file fs/read_write.c
patching file fs/splice.c
Hunk #1 succeeded at 833 (offset -4 lines).
Hunk #2 succeeded at 850 (offset -4 lines).
patching file fs/sync.c
patching file include/linux/fs.h
Hunk #1 succeeded at 1324 (offset 14 lines).
Hunk #4 succeeded at 2311 (offset 5 lines).
Hunk #5 succeeded at 2600 (offset 6 lines).
patching file include/linux/lockdep.h
Hunk #1 succeeded at 320 (offset 14 lines).
Hunk #2 succeeded at 460 (offset 26 lines).
patching file include/linux/mnt_namespace.h
patching file include/linux/splice.h
patching file kernel/locking/lockdep.c
Hunk #1 succeeded at 151 (offset 8 lines).
Hunk #2 succeeded at 162 (offset 8 lines).
patching file fs/Kconfig
Hunk #1 FAILED at 255.
1 out of 1 hunk FAILED -- saving rejects to file fs/Kconfig.rej
patching file fs/Makefile
Hunk #1 succeeded at 129 (offset 1 line).
patching file drivers/block/loop.c
Hunk #13 succeeded at 1193 (offset 14 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 859 (offset 13 lines).
patching file include/linux/fs.h
patching file fs/proc/base.c
Hunk #1 succeeded at 2018 (offset 4 lines).
patching file fs/proc/nommu.c
patching file fs/proc/task_mmu.c
Hunk #2 succeeded at 1745 (offset 2 lines).
patching file fs/proc/task_nommu.c
patching file include/linux/mm.h
Hunk #1 succeeded at 1473 (offset -45 lines).
patching file include/linux/mm_types.h
Hunk #1 succeeded at 250 (offset 6 lines).
Hunk #2 succeeded at 325 (offset 6 lines).
patching file kernel/fork.c
Hunk #1 succeeded at 546 (offset -1 lines).
patching file mm/Makefile
patching file mm/filemap.c
Hunk #1 succeeded at 2764 (offset 87 lines).
patching file mm/mmap.c
Hunk #4 succeeded at 2674 (offset -1 lines).
Hunk #5 succeeded at 2693 (offset -1 lines).
Hunk #6 succeeded at 2883 (offset -1 lines).
Hunk #7 succeeded at 2958 (offset -1 lines).
Hunk #8 succeeded at 3268 (offset -1 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 #3 succeeded at 372 (offset 5 lines).
patching file fs/inode.c
patching file fs/namespace.c
Hunk #1 succeeded at 435 (offset 1 line).
Hunk #2 succeeded at 775 (offset 1 line).
Hunk #3 succeeded at 1848 with fuzz 2 (offset 4 lines).
patching file fs/notify/group.c
patching file fs/notify/mark.c
Hunk #1 succeeded at 290 (offset 1 line).
Hunk #2 succeeded at 445 (offset 1 line).
Hunk #3 succeeded at 688 (offset 28 lines).
Hunk #4 succeeded at 812 (offset 28 lines).
patching file fs/open.c
patching file fs/read_write.c
patching file fs/splice.c
Hunk #1 succeeded at 846 (offset -4 lines).
Hunk #2 succeeded at 876 (offset -4 lines).
patching file fs/sync.c
patching file fs/xattr.c
patching file kernel/locking/lockdep.c
Hunk #1 succeeded at 162 (offset 8 lines).
patching file kernel/task_work.c
patching file security/device_cgroup.c
patching file security/security.c
Hunk #1 succeeded at 992 (offset 426 lines).
Hunk #2 succeeded at 1009 (offset 426 lines).
Hunk #3 succeeded at 1018 (offset 426 lines).
Hunk #4 succeeded at 1046 (offset 426 lines).
Hunk #5 succeeded at 1054 (offset 426 lines).
Hunk #6 succeeded at 1062 (offset 426 lines).
Hunk #7 succeeded at 1163 (offset 426 lines).
Hunk #8 succeeded at 1335 (offset 426 lines).
patching file include/linux/lockdep.h
patching file include/linux/rculist.h
patching file kernel/locking/lockdep.c
Hunk #1 succeeded at 1075 with fuzz 1 (offset 338 lines).
Hunk #2 FAILED at 833.
Hunk #3 succeeded at 4760 with fuzz 1 (offset 584 lines).
Hunk #4 FAILED at 4185.
2 out of 4 hunks FAILED -- saving rejects to file kernel/locking/lockdep.c.rej
patching file kernel/locking/lockdep_internals.h
Hunk #1 succeeded at 71 (offset 4 lines).
patching file include/linux/shmem_fs.h
patching file mm/shmem.c
Hunk #1 succeeded at 113 (offset 1 line).
Hunk #2 succeeded at 1093 (offset 5 lines).
Hunk #3 succeeded at 2232 (offset 83 lines).
Hunk #4 succeeded at 2281 (offset 83 lines).
Hunk #5 succeeded at 3305 (offset 84 lines).
Hunk #6 succeeded at 3325 (offset 84 lines).
Hunk #7 succeeded at 3341 (offset 84 lines).
Hunk #8 succeeded at 3413 (offset 84 lines).
Hunk #9 succeeded at 3478 (offset 84 lines).
Hunk #10 succeeded at 3527 (offset 84 lines).
Hunk #11 succeeded at 3551 (offset 84 lines).
Hunk #12 succeeded at 3571 (offset 84 lines).
Hunk #13 succeeded at 3680 (offset 84 lines).
Hunk #14 succeeded at 3819 (offset 84 lines).
patching file fs/inode.c
# 
(2-2) config of 5.1-rc
It was converted from the config of 5.0 by "make oldconfig" command with specs as following.

=== 32Bit

Code: Select all

Enable IO uring support (IO_URING) [Y/n/?] (NEW) n
Timer events oriented (TEO) governor (for tickless systems) (CPU_IDLE_GOV_TEO) [N/y/?] (NEW) n
Network physical/parent device Netlink interface (NET_DEVLINK) [N/y/?] (NEW) n
Intel HDCP2.2 services of ME Interface (INTEL_MEI_HDCP) [N/m/?] (NEW) n
VOP Bus Driver (VOP_BUS) [N/m/y/?] (NEW) n
HabanaAI accelerators (habanalabs) (HABANA_AI) [N/m/y/?] (NEW) n
TI CPSW Phy mode Selection (DEPRECATED) (TI_CPSW_PHY_SEL) [N/y/?] (NEW) n
MediaTek MT7603E (PCIe) and MT76x8 WLAN support (MT7603E) [N/m/?] (NEW) m
Qualcomm MSM vibrator driver (INPUT_MSM_VIBRATOR) [N/m/y/?] (NEW) n
Automatically load TTY Line Disciplines (LDISC_AUTOLOAD) [Y/n/?] (NEW) n
NXP Flex SPI controller (SPI_NXP_FLEXSPI) [N/m/y/?] (NEW) n
SiFive SPI controller (SPI_SIFIVE) [N/m/y/?] (NEW) n
GPIO support for AMD Fusion Controller Hub (G-series SOCs) (GPIO_AMD_FCH) [N/m/y/?] (NEW) n
TQ-Systems IO controller TQMX86 (MFD_TQMX86) [N/m/y/?] (NEW) n
Enable IR raw decoder for the RC-MM protocol (IR_RCMM_DECODER) [N/m/y/?] (NEW) n
OmniVision OV9640 sensor support (VIDEO_OV9640) [N/m/y/?] (NEW) n
ETNAVIV (DRM support for Vivante GPU IP cores) (DRM_ETNAVIV) [N/m/y/?] (NEW) n
ViewSonic/Signotec (HID_VIEWSONIC) [N/m/y/?] (NEW) n
Maltron L90 keyboard (HID_MALTRON) [N/m/y/?] (NEW) n
Default autosuspend delay (USB_AUTOSUSPEND_DELAY) [2] (NEW) 
Support for Freescale on-chip EHCI USB controller (USB_EHCI_FSL) [N/m/y/?] (NEW) y
Abracon AB-RTCMC-32.768kHz-EOZ9 (RTC_DRV_ABEOZ9) [N/m/y/?] (NEW) n
Micro Crystal RV3028 (RTC_DRV_RV3028) [N/m/y/?] (NEW) n
ZXW Crystal SD3078 (RTC_DRV_SD3078) [N/m/y/?] (NEW) n
PC Engines APUv2/3 front button and LEDs driver (PCENGINES_APU2) [N/m/?] (NEW) n
NXP PTN5150 CC LOGIC USB EXTCON support (EXTCON_PTN5150) [N/m/y/?] (NEW) n
On-Chip Interconnect management support (INTERCONNECT) [N/m/y/?] (NEW) n
Validate filesystem parameter description (VALIDATE_FS_PARSER) [Y/n/?] (NEW) y
Ordered list of enabled LSMs (LSM) [yama,loadpin,safesetid,integrity,selinux,smack,tomoyo,apparmor] (NEW) 
Show caller information on printks (PRINTK_CALLER) [N/y/?] (NEW) n
Test module for stress/performance analysis of vmalloc allocator (TEST_VMALLOC) [N/m/?] (NEW) n
Test level of stack variable initialization (TEST_STACKINIT) [N/m/y/?] (NEW) n
=== 64Bit

Code: Select all

Enable IO uring support (IO_URING) [Y/n/?] (NEW) n
Timer events oriented (TEO) governor (for tickless systems) (CPU_IDLE_GOV_TEO) [N/y/?] (NEW) n
Network physical/parent device Netlink interface (NET_DEVLINK) [N/y/?] (NEW) n
Intel HDCP2.2 services of ME Interface (INTEL_MEI_HDCP) [N/m/?] (NEW) n
HabanaAI accelerators (habanalabs) (HABANA_AI) [N/m/y/?] (NEW) n
TI CPSW Phy mode Selection (DEPRECATED) (TI_CPSW_PHY_SEL) [N/y/?] (NEW) n
MediaTek MT7603E (PCIe) and MT76x8 WLAN support (MT7603E) [N/m/?] (NEW) m
Qualcomm MSM vibrator driver (INPUT_MSM_VIBRATOR) [N/m/y/?] (NEW) n
Automatically load TTY Line Disciplines (LDISC_AUTOLOAD) [Y/n/?] (NEW) n
NXP Flex SPI controller (SPI_NXP_FLEXSPI) [N/m/y/?] (NEW) n
SiFive SPI controller (SPI_SIFIVE) [N/m/y/?] (NEW) n
GPIO support for AMD Fusion Controller Hub (G-series SOCs) (GPIO_AMD_FCH) [N/m/y/?] (NEW) n
TQ-Systems IO controller TQMX86 (MFD_TQMX86) [N/m/y/?] (NEW) n
Enable IR raw decoder for the RC-MM protocol (IR_RCMM_DECODER) [N/m/y/?] (NEW) n
OmniVision OV9640 sensor support (VIDEO_OV9640) [N/m/y/?] (NEW) n
ETNAVIV (DRM support for Vivante GPU IP cores) (DRM_ETNAVIV) [N/m/y/?] (NEW) n
ViewSonic/Signotec (HID_VIEWSONIC) [N/m/y/?] (NEW) n
Maltron L90 keyboard (HID_MALTRON) [N/m/y/?] (NEW) n
Default autosuspend delay (USB_AUTOSUSPEND_DELAY) [2] (NEW) 
Support for Freescale on-chip EHCI USB controller (USB_EHCI_FSL) [N/m/y/?] (NEW) y
Abracon AB-RTCMC-32.768kHz-EOZ9 (RTC_DRV_ABEOZ9) [N/m/y/?] (NEW) n
Micro Crystal RV3028 (RTC_DRV_RV3028) [N/m/y/?] (NEW) n
ZXW Crystal SD3078 (RTC_DRV_SD3078) [N/m/y/?] (NEW) n
PC Engines APUv2/3 front button and LEDs driver (PCENGINES_APU2) [N/m/?] (NEW) n
NXP PTN5150 CC LOGIC USB EXTCON support (EXTCON_PTN5150) [N/m/y/?] (NEW) n
On-Chip Interconnect management support (INTERCONNECT) [N/m/y/?] (NEW) n
Validate filesystem parameter description (VALIDATE_FS_PARSER) [Y/n/?] (NEW) y
Ordered list of enabled LSMs (LSM) [yama,loadpin,safesetid,integrity,selinux,smack,tomoyo,apparmor] (NEW) 
Show caller information on printks (PRINTK_CALLER) [N/y/?] (NEW) n
Test module for stress/performance analysis of vmalloc allocator (TEST_VMALLOC) [N/m/?] (NEW) n
Test level of stack variable initialization (TEST_STACKINIT) [N/m/y/?] (NEW) n

Thanks.

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

Porteus Kernel Builder

Post#502 by neko » 18 Mar 2019, 06:34

@user0815
New version "Porteus Kernel Builder" was uploaded.
5.0, 4.20, & 4.19 configs were changed depending on your demand.
Please update kernel by yourself.

-------------------------------------------------------
[How to use "Kernel Builder"]

step 1. prepare compile environment.
get 05-devel.xzm for your architecture from Porteus release site.
activate "05-devel.xzm".

Image
setting window

==== 1st RUN ====
step 2. set working direcory.
First, prepare the directory for 'Porteus Kernel Builder'.
This direcory must be in LINUX file system (ext4 etc.,).
Select this in "Kernel Builder directory" of "setting window"

step 3. select kernel version.
select kernel version line in left item of "Kernel Version" of "setting window".
left item will display the latest version of the line.
if older version is needed, select kernel version in right item.
(5.0.2/4.20.16/4.19.29)

step 4. "Build kernel" circle
"32Bit/64Bit" item: (first, display running PC architecture)
---->select compiling architecture.
(64Bit)

"download" item:
---->(if) check it on, download kernel source and get AUF patch and prototype config.
(check it on)

"expand & patch" item:
---->(if) check it on, expand commpressed kernel source, adapt AUF patch, and set config.
(check it on)

step 5. push "OK" button and confirm "OK"

5.0 case
Please confirm that "aufs.patch" was created.
4.20/4.19 case
Please confirm that "NG-aufs.patch" was created.

==== 2nd RUN (only for 4.20/4.19 case)====
(after set same as step 2, step 3 of 1st RUN)
step 6. "Build kernel" circle
"32Bit/64Bit" item: (first, display running PC architecture)
---->select compiling architecture. (same as 1st RUN)
(64Bit)

"own patch" item:
---->(if) check it on, "own patch" is adapted.
(check it on)

step 7. push "OK" button and confirm "OK"

==== Your own modifications of source/config ====
if a config change be needed, refer to [update config by "make menuconfig" command].

==== 3nd RUN ====
(after set same as step 2, step 3 of 1st RUN)
step 8. "Build kernel" circle
"32Bit/64Bit" item: (first, display running PC architecture)
---->select compiling architecture. (same as 1st RUN)
(64Bit)

"compile" item: (this action needs 05-devel.xzm for building kernel)
---->(if) check it on, build kernel and set vmlinuz & lib.
(check it on)

"Create FW" item:
---->(if) check it on, copy firmwares from firmware packages
(check it on)

step 9. (option) "Create crippled_sources or 000-kernel modules" circle
"crippled_sources" item:
---->(if) check it on, create crippled_sources module.
(check it on)

step 10. push "OK" button and confirm "OK"


==== 4th RUN ====
(after set same as step 2, step 3 of 1st RUN)
step 11. "Build kernel" circle
"32Bit/64Bit" item: (first, display running PC architecture)
---->select compiling architecture. (same as 1st RUN)
(64Bit)

step 12. (option) "ISO whose kernel will be update" circle
select ISO whose kernel will be update. (Original ISO must be in the directory differ from kernel build work directory.)
"keep org" item: (default "check on")
---->check it on, Target ISO will be treated as "Porteus" ISO.
---->check it off, The intrd of new ISO will be integrated initrd.
(check it off)

step 13. push "OK" button and confirm "OK"


Note 1: "2nd RUN"
if "NG-aufs.patch" was not created (AUFS patch might be fixed),
2nd RUN doesn't be needed.

-------------------------------------------------------
[update config by "make menuconfig" command]]
Example: 5.0 config change (already uploaded).

1. search the position of "CONFIG_MISC_RTSX & CONFIG_MISC_RTSX_PCI"
After execute "make menuconfig", input "/" character.
Then search window opens.
Set search string and input return key.

Code: Select all

/CONFIG_MISC_RTSX
Symbol: MISC_RTSX [=m]                                                                                                                                │  
  │ Type  : tristate                                                                                                                                      │  
  │   Defined at drivers/misc/Kconfig:512                                                                                                                 │  
  │                                                                                                                                                       │  
  │                                                                                                                                                       │  
  │ Symbol: MISC_RTSX_PCI [=m]                                                                                                                            │  
  │ Type  : tristate                                                                                                                                      │  
  │ Prompt: Realtek PCI-E card reader                                                                                                                     │  
  │   Location:                                                                                                                                           │  
  │     -> Device Drivers                                                                                                                                 │  
  │ (1)   -> Misc devices                                                                                                                                 │  
  │   Defined at drivers/misc/cardreader/Kconfig:12                                                                                                       │  
  │   Depends on: PCI [=y]                                                                                                                                │  
  │   Selects: MFD_CORE [=y]                                                                                                                              │  
  │                                                                                                                                                       │  
  │                                                                                                                                                       │  
  │ Symbol: MISC_RTSX_USB [=m]                                                                                                                            │  
  │ Type  : tristate                                                                                                                                      │  
  │ Prompt: Realtek USB card reader                                                                                                                       │  
  │   Location:                                                                                                                                           │  
  │     -> Device Drivers                                                                                                                                 │  
  │ (2)   -> Misc devices                                                                                                                                 │  
  │   Defined at drivers/misc/cardreader/Kconfig:23                                                                                                       │  
  │   Depends on: USB [=y]                                                                                                                                │  
  │   Selects: MFD_CORE [=y]                                                                                                                              │  
  │                                                                                                                                                       │  

/CONFIG_MISC_RTSX_PCI
Symbol: MISC_RTSX_PCI [=m]                                                                                                                            │  
  │ Type  : tristate                                                                                                                                      │  
  │ Prompt: Realtek PCI-E card reader                                                                                                                     │  
  │   Location:                                                                                                                                           │  
  │     -> Device Drivers                                                                                                                                 │  
  │ (1)   -> Misc devices                                                                                                                                 │  
  │   Defined at drivers/misc/cardreader/Kconfig:12                                                                                                       │  
  │   Depends on: PCI [=y]                                                                                                                                │  
  │   Selects: MFD_CORE [=y]                                                                                                                              │  
  │                                                                                                                                                       │  
 
/CONFIG_MMC_REALTEK_PCI
  Symbol: MMC_REALTEK_PCI [=m]                                                                                                                          │  
  │ Type  : tristate                                                                                                                                      │  
  │ Prompt: Realtek PCI-E SD/MMC Card Interface Driver                                                                                                    │  
  │   Location:                                                                                                                                           │  
  │     -> Device Drivers                                                                                                                                 │  
  │ (1)   -> MMC/SD/SDIO card support (MMC [=y])                                                                                                          │  
  │   Defined at drivers/mmc/host/Kconfig:888                                                                                                             │  
  │   Depends on: MMC [=y] && MISC_RTSX_PCI [=m] 
2. Change config paramater value from M to Y.
After position search, using the position information, move to the paramater, and then input space key.
Value <M> is changed to value <*>.

Code: Select all

 > Device Drivers > Misc devices 
<M> Realtek PCI-E card reader
--->
<*> Realtek PCI-E card reader

> Device Drivers > MMC/SD/SDIO card support 
<M>   Realtek PCI-E SD/MMC Card Interface Driver
--->
<*>   Realtek PCI-E SD/MMC Card Interface Driver
3. confirm updated config

Code: Select all

# diff .config.old .config
3c3
< # Linux/x86 5.0.0-rc6 Kernel Configuration
---
> # Linux/x86 5.0.2 Kernel Configuration
1523c1523
< CONFIG_MISC_RTSX=m
---
> CONFIG_MISC_RTSX=y
1594c1594
< CONFIG_MISC_RTSX_PCI=m
---
> CONFIG_MISC_RTSX_PCI=y
5053c5053
< CONFIG_MMC_REALTEK_PCI=m
---
> CONFIG_MMC_REALTEK_PCI=y
6299a6300
> CONFIG_KASAN_STACK=1
#



Thanks.

User avatar
user0815
Black ninja
Black ninja
Posts: 63
Joined: 22 Jan 2019, 11:46
Distribution: CINNAMON-v4.0-x86_64

Porteus Kernel Builder

Post#503 by user0815 » 18 Mar 2019, 08:28

@neko,
1st RUN done as you advised, but get message “missing /home/guest/kernel/v5.0/lib”. The home/guest/kernel is what I set as working directory. Where should I get this missing lib?
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

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

Porteus Kernel Builder

Post#504 by neko » 18 Mar 2019, 11:13

@user0815
I do confirm your operation.

------------------------------------------------
==== 1st RUN ====
step 2. set working direcory.

prepare
% cd
% pwd
/home/guest
% mkdir kernel

set
/home/guest/kernel

step 3. select kernel version.
set
5.0.2

step 4. "Build kernel" circle
"32Bit/64Bit" item:
---->select
64Bit

"download" item:
ON

"expand & patch" item:
ON

"Create FW"
OFF

step 5. push "OK" button and confirm "OK"
------------------------------------------------
missing explaining: at step 4
"Create FW"
OFF


Question:
1. Did you do same operation as confirmation ?

2. Did you see kernel source downloading in the auto opened terminal ?

3. Did you see the "aufs.patch" in /home/guest/kernel/v5.0.2 ?


Thanks.

User avatar
user0815
Black ninja
Black ninja
Posts: 63
Joined: 22 Jan 2019, 11:46
Distribution: CINNAMON-v4.0-x86_64

Porteus Kernel Builder

Post#505 by user0815 » 18 Mar 2019, 12:33

@neko, thanks for the hint, create FW on was the reason.
Now, I am at step 10, 3rd run. There were lots of questions which had to be answered by y or n. I did it to my best knowledge, but I am not sure, sorry, I am not familiar with kernel compilation, still have to learn a lot. 3rd Run is still running, hope it will not take long. Is it possible to save everything and do 4th Run later on?
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

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

Porteus Kernel Builder

Post#506 by neko » 18 Mar 2019, 14:23

@user0815

Is it possible to save everything and do 4th Run later on?
--->
Yes, it is.

-------------------------------
A kernel build is not complex. It is simple.
But "Kernel Builder" tool need a little usage skill.
Tool usage knowledge is not essential.

[Kernel build process]
1. get kernel source.
2. get AUFS patch.
3. expand compressed kernel source.
4. applay AUFS patch to kernel source.
5. prepare "config" of kernel build.
6. perform kernel build.
7. gather the firmwares that were needed by the built kernel.
8. replace "vmlinuz & 000-kernel.xzm" of target ISO with new one.

Please refer to
http://www.porteus.org/component/conten ... ernel.html

All parts of "Kernel Builder" have been made with shell scripts.
If you have a little skill to read shell script, everything are opened for you. And you can tune it to fit your need.

Thanks.

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

Porteus Kernel Builder

Post#507 by neko » 18 Mar 2019, 14:52

1. current kernel version
[from https://www.kernel.org/finger_banner]
The latest stable version of the Linux kernel is: 5.0.2
The latest mainline version of the Linux kernel is: 5.1-rc1 <---NEW
The latest stable 5.0 version of the Linux kernel is: 5.0.2
The latest stable 4.20 version of the Linux kernel is: 4.20.16
The latest longterm 4.19 version of the Linux kernel is: 4.19.29
The latest longterm 4.14 version of the Linux kernel is: 4.14.106
The latest longterm 4.9 version of the Linux kernel is: 4.9.163
The latest longterm 4.4 version of the Linux kernel is: 4.4.176
The latest longterm 3.18 version of the Linux kernel is: 3.18.136 (EOL)
The latest linux-next version of the Linux kernel is: next-20190318


2. NEW Example of updated kernel that was built by "Porteus Kernel builder" was updated.

"copy firmwares from firmware packages" function was used when build kernel.


ov.v5.1-rc1.tar.xz (95 M)
http://www.mediafire.com/file/83l26x8ca ... rc1.tar.xz
md5sum: 0e5a02072be1a92e693820f26fc15608 ov.v5.1-rc1.tar.xz

crippled_sources-5.1-rc1-32bit.xzm (22 M)
http://www.mediafire.com/file/xta2rce4t ... -32bit.xzm
md5sum: e0a225e566541ada795c6ea6a2061b43 crippled_sources-5.1-rc1-32bit.xzm

crippled_sources-5.1-rc1-64bit.xzm (22 M)
http://www.mediafire.com/file/hdgft9rsq ... -64bit.xzm
md5sum: 6c4841b9867ba69d6d7a99e1993f9dc7 crippled_sources-5.1-rc1-64bit.xzm


Note 1: AUFS patch is not yet ready for kernel 5.1-rc1.
"5.x-rcN" was used.
AUFS_VERSION "5.x-rcN-20190311" are not yet adapted correctly to patch to kernel/locking/lockdep.c.
Therefore the kernel 5.1-rc1 was built without AUFS patch.


3. Porteus 4.0 Overlay FS trial version

OV.Porteus-CINNAMON-v4.0-x86_64-19.03.18.iso (359 M: Kernel 5.1-rc1)
http://www.mediafire.com/file/a0p153e5o ... .03.18.iso
md5sum: 3a68e7bdf056cecffa13f64a64225f4f OV.Porteus-CINNAMON-v4.0-x86_64-19.03.18.iso


Note 1:
crippled_sources is included in ISO@/porteus/optional.

Note 2:
The intrd of this ISO is integrated initrd.
Please refer to Re: Porteus Kernel Builder (Post by neko #68746)


Thanks.


-------------------------------------------
@user0815
If you have built kernel with new version "Kernel Builder",
and the ISO whose kernel is replaced with the new one could boot from your SD card,

OV.Porteus-CINNAMON-v4.0-x86_64-19.03.18.iso too, maybe, could boot from the SD card.


Thanks.

User avatar
user0815
Black ninja
Black ninja
Posts: 63
Joined: 22 Jan 2019, 11:46
Distribution: CINNAMON-v4.0-x86_64

Porteus Kernel Builder

Post#508 by user0815 » 18 Mar 2019, 15:39

neko wrote:
18 Mar 2019, 14:52
If you have built kernel with new version "Kernel Builder",
and the ISO whose kernel is replaced with the new one could boot from your SD card,
I am kind of freaking out. Kernel build was completed successfully, both CONFIG_MISC_RTSX_PCI and MMC_REALTEK_PCI checked and found set to y in 64bit.config. New iso "UP.Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso" was created (no idea why it was named like this). And I can indeed boot from my micro SD card, kernel 5.0.2. My first self-built kernel (well, actually, I didn´t build it myself, but just used the GUI from neko and following his instructions). @neko, thank you again a lot.

However, the new iso that can now boot from the micro SD card (with adapter), cannot boot from another SD card. But this SD card was able to boot with porteus v3.2.2. I am really puzzled. Is there also dependency not only on the card reader, but also on manufacturer of the sd card itself? why could the sd card boot with porteus v3.2.2?

Cheers

edit: additional detail: the iso I took whose kernel shall be replaced was "Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso" from here
neko wrote:
12 Jan 2019, 17:21
Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso (358 M: Kernel 4.19.14)
http://www.mediafire.com/file/0dz5sutrt ... .01.12.iso
md5sum: d71de02cc6171c640a0afe3df619804c Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

User avatar
user0815
Black ninja
Black ninja
Posts: 63
Joined: 22 Jan 2019, 11:46
Distribution: CINNAMON-v4.0-x86_64

Porteus Kernel Builder

Post#509 by user0815 » 20 Mar 2019, 03:44

@neko, I tested again with a standard sd card from Kingston, and it finally works, boot was successful.
So may I request to have the settings for CONFIG_MISC_RTSX_PCI and CONFIG_MMC_REALTEK_PCI set to y for future kernel releases?
Many thanks.
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

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

Porteus Kernel Builder

Post#510 by neko » 20 Mar 2019, 04:44

@user0815
Thank you very much for your test and report.
It is very useful for other "SD card" users.

And configs of kernel 5.1-rc, 5.0, 4.20, & 4.19 lines are already set to

CONFIG_MISC_RTSX=y
CONFIG_MISC_RTSX_PCI=y
CONFIG_MMC_REALTEK_PCI=y

in "Kernel Builder" mkKernel-19.03.16-noarch-1.xzm.

Following uploaded example kernels were built with the config set as so.


Thanks.


-----------------------------
1. current kernel version
[from https://www.kernel.org/finger_banner]
The latest stable version of the Linux kernel is: 5.0.3
The latest mainline version of the Linux kernel is: 5.1-rc1
The latest stable 5.0 version of the Linux kernel is: 5.0.3 <---NEW
The latest stable 4.20 version of the Linux kernel is: 4.20.17 <---NEW
The latest longterm 4.19 version of the Linux kernel is: 4.19.30 <---NEW
The latest longterm 4.14 version of the Linux kernel is: 4.14.107 <---NEW
The latest longterm 4.9 version of the Linux kernel is: 4.9.164 <---NEW
The latest longterm 4.4 version of the Linux kernel is: 4.4.176
The latest longterm 3.18 version of the Linux kernel is: 3.18.136 (EOL)
The latest linux-next version of the Linux kernel is: next-20190319


2. NEW Example of updated kernel that was built by "Porteus Kernel builder" was updated.

"copy firmwares from firmware packages" function was used when build kernel.


=== Simple package (vmlinuz, 000-kernel.xzm, 06-crippled_sources-NNN-XXbit.xzm) ===
[5.0.3]
32bit-kernel5.0.3.tar (86 M)
http://www.mediafire.com/file/mg6sixm2o ... l5.0.3.tar
md5sum: 23f2e32bd1bfbc19fc0e5e8a269f5e48 32bit-kernel5.0.3.tar

64bit-kernel5.0.3.tar (92 M)
http://www.mediafire.com/file/8qg6nrxxh ... l5.0.3.tar
md5sum: 0d489aa96cf95982f31c43e7c34656c0 64bit-kernel5.0.3.tar

[4.20.17]
32bit-kernel4.20.17.tar (86 M)
http://www.mediafire.com/file/242lmypj4 ... .20.17.tar
md5sum: 0040d4499c5323948d890c8b9fd24f5d 32bit-kernel4.20.17.tar

64bit-kernel4.20.17.tar (91 M)
http://www.mediafire.com/file/20uqjwdl7 ... .20.17.tar
md5sum: c3163d6270fd4da55ae25204567ab36e 64bit-kernel4.20.17.tar

[4.19.30]
32bit-kernel4.19.30.tar (86 M)
http://www.mediafire.com/file/x441g97rq ... .19.30.tar
md5sum: 2acc33d20e21a67021d84bafe550c5f9 32bit-kernel4.19.30.tar

64bit-kernel4.19.30.tar (91 M)
http://www.mediafire.com/file/ws10g6epr ... .19.30.tar
md5sum: 7d10d69d92729f5fe09ddfaeb4bea603 64bit-kernel4.19.30.tar


Note 1:
Compiled by gcc-8.2.1+20181127-x86_64-1

Note 2: [AUFS patch error as same as 4.20.4/4.19.17]
Kernel 4.20.17 was patched with AUFS_VERSION "4.20-20190311".
Kernel 4.19.30 was patched with AUFS_VERSION "4.19-20190311".
These version AUFS patches are not yet adapted correctly
to patch to drivers/block/loop.c of kernel 4.20.17/4.19.30.
Kernel 4.20/4.19 own patch of drivers/block/loop.c was applied with "Kernel builder".

Note 3:
Kernel 5.0.3 was patched with AUFS_VERSION "5.0-20190311".


Thanks.

Post Reply