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#481 by neko » 12 Mar 2019, 13:18

@user0815
I did same operation as you.
I got NEW.iso.
NEW.iso boots and runs on my PC.

But on your report NEW.iso doesn't boot from "Realtek PCI-E Memory Card Reader Driver".

I guess that kernel build was wrong.
Something more is needed.
Now I do not know what is lack. Sorry.
Somebody who knows it, tell me please.


[ operation of replacing vmlinuz & 000-kernel.xzm ]

Code: Select all

% su
# ls
64bit-kernel5.0.1-RTSX_USB.tar Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso
# mkdir mnt
# mount -t iso9660 -o loop Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso mnt
# mkdir NEW
# cp -a mnt/* NEW/.
# cp -a /mnt/.[0-9A-Za-z]* NEW/. 2>/dev/null
# umount -f mnt
# rm -fr mnt
#
# mkdir w
# cd w
# tar -xf ../64bit-kernel5.0.1-RTSX_USB.tar
# cd ../
# mv w/vmlinuz NEW/boot/syslinux/
# mv w/000-kernel.xzm NEW/porteus/base/
#
# mkisofs -o NEW.iso -v -l -J -joliet-long  -R -D -A Porteus -V Porteus \
-no-emul-boot -boot-info-table -boot-load-size 4 \
-b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot NEW
# rm -fr NEW w
# ls 
64bit-kernel5.0.1-RTSX_USB.tar NEW.iso Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso

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#482 by user0815 » 12 Mar 2019, 14:15

neko wrote:
12 Mar 2019, 13:18
NEW.iso boots and runs on my PC
Yes, it will boot from usb flash drive, no doubt, I tried again with usb flash drive and it works. But the problem I have described in this post
Install Porteus on SD card (Post by jssouza #70027)
is to boot porteus from SD card, it´s a built-in card reader in Dell laptop, connected via PCIe. While this worked with porteus v3.2.2, I do get this error message when trying with newer porteus versions. Screenshot here: https://ibb.co/ctftk2p
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#483 by neko » 13 Mar 2019, 04:15

@user0815

I set some firmware into initrd.
Please replace & try run.

Replace
NEW.iso@boot/syslinux/initrd.xz
NEW.iso@porteus/kernel-v4.19.14-1-x86_64.cfg
NEW.iso@porteus/optional/06-crippled_sources-4.19.14-64bit.xzm
with
v5.0.1-2.tar@initrd.xz
v5.0.1-2.tar@kernel-v5.0.1-2-x86_64.cfg
64bit-kernel5.0.1-RTSX_USB.tar@06-crippled_sources-5.0.1-64bit.xzm

v5.0.1-2.tar (2 M)
http://www.mediafire.com/file/s71e4duu4 ... .0.1-2.tar
md5sum: 9797e797c497fab2ae6af699b8ce72ab v5.0.1-2.tar

NEW.iso is the ISO that you have updated from Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso.


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#484 by user0815 » 13 Mar 2019, 06:49

@neko
done so but still the same error: porteus data not found...

edit: I also replace the original vmlinuz from Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso with 64bit-kernel5.0.1-RTSX_USB.tar@vmlinuz, is it correct?
some more details that hopefully help to identify the root cause: the sd card is in fat32 format. With porteus v3.2.2, both classic and efi boots are working. With later porteus version, I get this error: https://ibb.co/9vjsVs4 when trying efi boot.
For all porteus version, it is not possible to use Porteus-installer-for-Linux.com under Porteus to set up another sd card, I get this error code 2: https://ibb.co/58n8qm8
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#485 by neko » 13 Mar 2019, 11:38

@user0815

Thank you for your report.

"edit: I also replace the original vmlinuz from Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso with 64bit-kernel5.0.1-RTSX_USB.tar@vmlinuz, is it correct?"
--->
Yes, it is.


(1)CONFIG_MISC_RTSX=y & CONFIG_MISC_RTSX_USB=y
result: NG
(2)CONFIG_MISC_RTSX=y & CONFIG_MISC_RTSX_USB=y + firmware into initrd
result: NG

(3)old version (4.14.2)
I tried build kernel 4.14.105.
It was in the fail result.(AUFS patch error ---> compile error)
Then, I searched 4.14.nn version. Kernel 4.14.2 was found.

Please replace & try run.

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
Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso@porteus/optional/06-crippled_sources-4.19.14-64bit.xzm
with
64bit-kernel4.14.2.tar@vmlinuz
64bit-kernel4.14.2.tar@000-kernel.xzm
64bit-kernel4.14.2.tar@06-crippled_sources-4.14.2-64bit.xzm


64bit-kernel4.14.2.tar (83 M)
http://www.mediafire.com/file/kkm647flo ... 4.14.2.tar
md5sum: 574f5aeb914d9312953f530e9a4db2b5 64bit-kernel4.14.2.tar


[contents]
vmlinuz
000-kernel.xzm
06-crippled_sources-4.14.2-64bit.xzm
aufs.patch
64bit.config:........used config
repo_getFW-v4.14.2-64:...collected firmware information


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#486 by user0815 » 13 Mar 2019, 13:25

hi neko,
neko wrote:
13 Mar 2019, 11:38
aufs.patch
64bit.config:........used config
repo_getFW-v4.14.2-64:...collected firmware information
I shall leave those files untouched, means not copying them to somewhere on sd card, correct?
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#487 by neko » 13 Mar 2019, 13:48

@user0815
"I shall leave those files untouched, means not copying them to somewhere on sd card, correct?"
--->
Yes, it correct.

aufs.patch, 64bit.config:
When you will build kernel 4.14.2 by yourself with same spec again, these will be needed.
repo_getFW-v4.14.2-64:
firmware were collected from big firmware pool.
This is the report.

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#488 by user0815 » 13 Mar 2019, 14:00

@neko,
neko wrote:
13 Mar 2019, 11:38
Please replace & try run.

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
Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso@porteus/optional/06-crippled_sources-4.19.14-64bit.xzm
with
64bit-kernel4.14.2.tar@vmlinuz
64bit-kernel4.14.2.tar@000-kernel.xzm
64bit-kernel4.14.2.tar@06-crippled_sources-4.14.2-64bit.xzm
done as advised and tested again, unfortunately, to no avail :cry:
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#489 by neko » 13 Mar 2019, 14:49

@user0815

Thank you for your report.

(1)CONFIG_MISC_RTSX=y & CONFIG_MISC_RTSX_USB=y
result: NG
(2)CONFIG_MISC_RTSX=y & CONFIG_MISC_RTSX_USB=y + firmware into initrd
result: NG
(3)old version (4.14.2)
result: NG

(4)kernel of "OK Porteus 64bit ISO that can boot from your SD".
Please replace & try run.

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
OK.iso@boot/syslinux/vmlinuz
OK.iso@porteus/base/000-kernel.xzm

Note:
If (4) will be NG, this issue might not be concerned with kernel CONFIG_MFD_RTSX_PCI.


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#490 by user0815 » 13 Mar 2019, 15:30

neko wrote:
13 Mar 2019, 14:49
(4)kernel of "OK Porteus 64bit ISO that can boot from your SD".
Please replace & try run.

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
OK.iso@boot/syslinux/vmlinuz
OK.iso@porteus/base/000-kernel.xzm
Sorry, where can I find the OK.iso? Thanks.
edit: oh ok now I understand. will do so
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#491 by user0815 » 13 Mar 2019, 16:22

neko wrote:
13 Mar 2019, 14:49
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
OK.iso@boot/syslinux/vmlinuz
OK.iso@porteus/base/000-kernel.xzm
Ok, done and booted successfully. By the way, forgot to mention, I did this already before upon jssouza advise (see this post). So the official Porteus-v4.0 can be booted from my sd card when replacing 000-kernel from v3.2.2. And now it is tested again with Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso. What would be your advise, should I continue using it like this? Thanks.
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

User avatar
Ed_P
Contributor
Contributor
Posts: 4878
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus Kernel Builder

Post#492 by Ed_P » 13 Mar 2019, 22:36

user0815 wrote:
13 Mar 2019, 16:22
should I continue using it like this? Thanks.
I would think it's your call but if you experience problems do note when reporting them that you are running a customized version of Porteus not the standard 3.2.2 or 4.0 .iso downloads. Not sure what the impact on USM will be. 3.2.2 version with 4.0 databases or 4.0 version with 3.2.2 databases?
Ed

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#493 by user0815 » 14 Mar 2019, 12:09

neko wrote:
13 Mar 2019, 14:49
result: NG
, btw, what does "NG" mean?
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#494 by neko » 14 Mar 2019, 14:14

@user0815
'what does "NG" mean?'
--->
No (Not) good.

Thanks.


-------------------------------------------
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.0
The latest stable 5.0 version of the Linux kernel is: 5.0.2 <---NEW
The latest stable 4.20 version of the Linux kernel is: 4.20.16 <---NEW
The latest longterm 4.19 version of the Linux kernel is: 4.19.29 <---NEW
The latest longterm 4.14 version of the Linux kernel is: 4.14.106 <---NEW
The latest longterm 4.9 version of the Linux kernel is: 4.9.163 <---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-20190306


2. NEW Example of updated kernel that were built by "Porteus Kernel builder" were 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.2]
32bit-kernel5.0.2.tar (86 M)
http://www.mediafire.com/file/bbjz4qvva ... l5.0.2.tar
md5sum: fcccb6fd865806e68aa534be7b30ff9b 32bit-kernel5.0.2.tar

64bit-kernel5.0.2.tar (92 M)
http://www.mediafire.com/file/r1dzc6apr ... l5.0.2.tar
md5sum: aeaf248f17a24ed467c5aa0dc688fa7a 64bit-kernel5.0.2.tar

[4.20.16]
32bit-kernel4.20.16.tar (86 M)
http://www.mediafire.com/file/80gfs0q7k ... .20.16.tar
md5sum: 2c4dfcd07e7a2aa0a9227eb4580d27cd 32bit-kernel4.20.16.tar

64bit-kernel4.20.16.tar (91 M)
http://www.mediafire.com/file/s5zb65957 ... .20.16.tar
md5sum: e3cc201f159db6d3ca0e1c577b372864 64bit-kernel4.20.16.tar

[4.19.29]
32bit-kernel4.19.29.tar (86 M)
http://www.mediafire.com/file/4tw29b6eg ... .19.29.tar
md5sum: c305dba35a6b2d614cf6d9aef6516c0b 32bit-kernel4.19.29.tar

64bit-kernel4.19.29.tar (91 M)
http://www.mediafire.com/file/plwzv1yap ... .19.29.tar
md5sum: 021ecaada59c8a60013eb495ec19174f 64bit-kernel4.19.29.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.16 was patched with AUFS_VERSION "4.20-20190311".
Kernel 4.19.29 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.16/4.19.29.
Kernel 4.20/4.19 own patch of drivers/block/loop.c was applied with "Kernel builder".

Note 3: AUFS Patch for 5.0 can be gotten.
AUFS_VERSION "5.0-20190311"

The shell script (get.aufs.patch) that makes the "AUFS Patch for 5.0" is as followed.

Code: Select all

#!/bin/sh

mkdir auf
cd auf

git clone https://github.com/sfjro/aufs5-standalone.git aufs5-standalone.git
cd aufs5-standalone.git
if ! ( git checkout origin/aufs5.0 )
then
	echo "get aufs5.x-rcN"
	git checkout origin/aufs5.x-rcN
fi

mkdir ../a ../b
cp -r {Documentation,fs,include} ../b
rm ../b/include/uapi/linux/Kbuild 2>/dev/null || rm ../b/include/linux/Kbuild
cd ..
diff -rupN a/ b/ > ../aufs.patch

cat aufs5-standalone.git/*.patch >> ../aufs.patch

cd ../
rm -r auf

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

The shell script (get.aufs.patch) that makes the "AUFS Patch for 5.0" is updated.

mkKernel-19.03.14-noarch-1.xzm (4.8 M)
http://simosnet.com/livecd/isobuilder/k ... arch-1.xzm
md5sum: 9f13d348ee053b0532e19a330c8572f1 mkKernel-19.03.14-noarch-1.xzm


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#495 by user0815 » 14 Mar 2019, 14:22

neko wrote:
13 Mar 2019, 14:49
Note:
If (4) will be NG, this issue might not be concerned with kernel CONFIG_MFD_RTSX_PCI.
Now that the boot test was successful, do we have a chance to get this fixed with latest kernel 5.xx? If not possible, I am also happy with the latest lts kernel 4.9.163, on which porteus v3.2.2 is based on. Thanks in advance.
using CINNAMON-v4.0-x86_64 with updated kernel porteus-4.16.8

Post Reply