Page 12 of 17

Porteus Kernel Builder

Posted: 01 Aug 2017, 10:42
by neko
@amplatfus
"The questions regarding Kernel are for me?"
--->
Yes, I asked you.

Excuse me that I replied to 2 persons at one article.
This part is reply for you.
----------------------------------
@amplatfus
=== About VBOX:
I apologize that unfortunately I am ignorant about VBOX.
Following the advice of fulalas,
crippled_sources generation function, 000-kernel generation function etc. have been added.
I expect that you will receive an advice from someone on this matter.

=== About "Kernel Builder" tool: needs more exactly information.
Currently the latest version of this tool is "mkKernel-17.07.22-noarch-1.xzm".

1. the case where your own build
What is the version of mkKernel ?

2. the case where using the kernel package provided as a build example

2.1. the case where the build example tar.xz is decomposed and used directly?

2.2. the case where using it via the mkKernel tool?
What is the version of mkKernel ?
and
How to get 000-kernel.xzm (via replacing one of ISO or creating 000-kernel.xzm) ?


Thanks.
Thanks.

Porteus Kernel Builder

Posted: 01 Aug 2017, 13:32
by fulalas
@amplatfus, I'm not sure if this is the case, but I noticed that Vbox doesn't like /opt folder ownership to be anything different from root. Sometimes we use some bad modules that have wrong ownership or we even use /rootcopy/etc from inside a non-Linux partition. If you're not sure, try this:

Code: Select all

echo guest | sudo -S chown -R root:root /opt
One more thing: usually I get the module created by vboxbuilder (inside /tmp), copy it to my modules folder and then reboot. I don't why, but before rebooting Vbox doesn't work. By doing that I can create and use VBox built against neko's kernel with no problem :good:

@neko, thanks for the reply. No need to hurry :)

Porteus Kernel Builder

Posted: 01 Aug 2017, 13:54
by amplatfus
neko wrote:
01 Aug 2017, 10:42
@amplatfus
"The questions regarding Kernel are for me?"
--->
Yes, I asked you.

Excuse me that I replied to 2 persons at one article.
This part is reply for you.
----------------------------------
@amplatfus
=== About VBOX:
I apologize that unfortunately I am ignorant about VBOX.
Following the advice of fulalas,
crippled_sources generation function, 000-kernel generation function etc. have been added.
I expect that you will receive an advice from someone on this matter.

=== About "Kernel Builder" tool: needs more exactly information.
Currently the latest version of this tool is "mkKernel-17.07.22-noarch-1.xzm".

1. the case where your own build
What is the version of mkKernel ?

2. the case where using the kernel package provided as a build example

2.1. the case where the build example tar.xz is decomposed and used directly?

2.2. the case where using it via the mkKernel tool?
What is the version of mkKernel ?
and
How to get 000-kernel.xzm (via replacing one of ISO or creating 000-kernel.xzm) ?


Thanks.
Thanks.
@neko
My VirtualBox module was build using VirtualBox builder from menu on Kernel: 4.9.0 original Porteus kernel on MATE from 3.2.2 version.
I have tried with this entered sudo chown root:root /opt/VirtualBox/VirtualBox and sudo chmod 4511 /opt/VirtualBox/VirtualBox and I runned as root. Same error.

I have tried with 000-kernel-4.10.8, same error.
In both scenarios I did not use mkKernel tool.

@fulalas,
Nice tip. I will try later on and post the update.

Thank you all,
amplatfus

Porteus Kernel Builder

Posted: 01 Aug 2017, 14:08
by fulalas
@amplatfus, if you're not using neko's kernel, maybe you should open a new topic so we won't pollute this one with a parallel subject. :good:

Porteus Kernel Builder

Posted: 01 Aug 2017, 14:34
by amplatfus
@fulalas you are right. I will do so. But I have tried with 000-kernel-4.11.4 x64 version from #119. It seems to be very little 19mb instead of more than 40mb 000-kernel-4.10.8.
I guess I am missing something.
I came here because I saw almost the same error like post here #115 Re: Porteus Kernel Builder (Post by fulalas #55928)
I will update this #170 with if I will do a separate thread.
For now I will try your suggestion and after I want to try 000-kernel-4.11.4 x64 but do not know how to manage it because of only 19mb. Could you please help?

Edit: solved using http://dl.porteus.org/x86_64/kernel/porteus-4.9.12/(crippled_sources.xzm and vmlinuz) and devel from vbox build script.

Thank you,
amplatfus

Porteus Kernel Builder

Posted: 01 Aug 2017, 14:45
by donald
@ amplatfus

Have you already tried this one?...(kernel 4.9.0)
viewtopic.php?p=55940&sid=c3699a56893e9 ... 887#p55940

Porteus Kernel Builder

Posted: 01 Aug 2017, 17:18
by amplatfus
donald wrote:
01 Aug 2017, 14:45
@ amplatfus

Have you already tried this one?...(kernel 4.9.0)
Re: Virtual Box (Post by donald #55940)
Thank you @donald. I from this I have below error.
I wil open another thread I think

Code: Select all

Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100) (rc=-10)
Please try reinstalling VirtualBox.
where: SUPR3HardenedMain what: 2 VERR_PERMISSION_DENIED (-10) - Permission denied.
Edit: solved using http://dl.porteus.org/x86_64/kernel/porteus-4.9.12/(crippled_sources.xzm and vmlinuz) and devel from vbox build script.

Porteus Kernel Builder

Posted: 05 Aug 2017, 01:31
by neko
"Porteus Kernel Builder" was updated to mkKernel-17.08.04-noarch-1.xzm.
Please refer to Porteus Kernel Builder

(1) "b43" kernel module was deleted from blacklist.

(2) "b43-firmware" was ported from ArchLinux AUR and offered.

---------------------------------------------------------
On "broadcom" issue, all cards cannot be covered.
Therefore only kernel module "b43" will be activated (by deleting from blacklist).
And firmware module "b43-firmware" & "b43-firmware-classic" that were gotten from Archlinux AUR was uploaded.
Merge one of "b43-firmware" or "b43-firmware-classic" to 000-kernel module.

Note:
BCM4306 rev.3, BCM4311, BCM4312 and BCM4318 rev.2 have been noticed to experience problems with b43-firmware.
---> Use b43-firmware-classic for these cards instead.
BCM4331 noticed to have problems with b43-firmware-classic.
---> Use b43-firmware for this card instead.

For none covered cards, please tune by yourself.
refer to https://wiki.archlinux.org/index.php/broadcom_wireless

Example: merge b43-firmware to 000-kernel (Porteus 3.2.2)

Code: Select all

% su
# ls -1
000-kernel.xzm
b43-firmware-6.30.163.46-noarch-slk1.xzm
# mkdir new.000-kernel
# mloop 000-kernel.xzm
# cp -a /mnt/loop/* new.000-kernel
# uloop
# mloop b43-firmware-6.30.163.46-noarch-slk1.xzm
# cp -a /mnt/loop/* new.000-kernel/
# uloop
# mksquashfs new.000-kernel new.000-kernel.xzm -b 256K -comp xz -Xbcj x86 -noappend
# rm -fr new.000-kernel
# ls -1
000-kernel.xzm
b43-firmware-6.30.163.46-noarch-slk1.xzm
new.000-kernel.xzm

Thanks.

Porteus Kernel Builder

Posted: 07 Aug 2017, 02:20
by neko
[Current Example of updated kernels that were built by "Porteus Kernel builder"]
v4.15-rc3.tar.xz (86 M) <---NEW
http://www.mediafire.com/file/a788r4833 ... rc3.tar.xz
md5sum: af43aa1ba4c92251664f52699ea9bd33 v4.15-rc3.tar.xz

v4.14.5.tar.xz (84 M) <---NEW
http://www.mediafire.com/file/zzwtqs2z1 ... 4.5.tar.xz
md5sum: 275ca9422af3cd2f280c129a83f66196 v4.14.5.tar.xz

v4.9.68.tar.xz (79 M) <---NEW
http://www.mediafire.com/file/9egcxi1ak ... .68.tar.xz
md5sum: 06f3b9868457ca0f880c0e641476e5cf v4.9.68.tar.xz

v4.4.105.tar.xz (70 M) <---NEW
http://www.mediafire.com/file/k82lbxxxs ... 105.tar.xz
md5sum: 7ce0ddb18965cc492b3173d03cc102e8 v4.4.105.tar.xz

=== crippled_sources module Example ===
crippled_sources-4.15-rc3-32bit.xzm (20 M)
http://www.mediafire.com/file/3rojaqqyj ... -32bit.xzm
md5sum: c9b284765d744b6eac556652b175b507 crippled_sources-4.15-rc3-32bit.xzm

crippled_sources-4.15-rc3-64bit.xzm (20 M)
http://www.mediafire.com/file/161wzljcc ... -64bit.xzm
md5sum: cf85330ba93add16e3519e3e6d014ae3 crippled_sources-4.15-rc3-64bit.xzm

crippled_sources-4.14.5-32bit.xzm (19 M)
http://www.mediafire.com/file/e9d1db1nv ... -32bit.xzm
md5sum: 111b55922faf36a774d4f9ccd80c99b3 crippled_sources-4.14.5-32bit.xzm

crippled_sources-4.14.5-64bit.xzm (20 M)
http://www.mediafire.com/file/ydljnka0x ... -64bit.xzm
md5sum: ce737d55d4a7d727db4c1fe55c5f8cb8 crippled_sources-4.14.5-64bit.xzm

crippled_sources-4.14.2-32bit.xzm (19 M)
http://www.mediafire.com/file/pz7jo1z5p ... -32bit.xzm
md5sum: f4dbf6d11a2998c3cf53e0da1f153c46 crippled_sources-4.14.2-32bit.xzm

crippled_sources-4.14.2-64bit.xzm (20 M)
http://www.mediafire.com/file/2j5z8a5q7 ... -64bit.xzm
md5sum: 36d14cf8e8303fac10522ee119c440f9 crippled_sources-4.14.2-64bit.xzm

crippled_sources-4.9.68-32bit.xzm (18 M)
http://www.mediafire.com/file/r4d60p5yz ... -32bit.xzm
md5sum: 704722b40eefcd6152c2518ff6c3c5cb crippled_sources-4.9.68-32bit.xzm

crippled_sources-4.9.68-64bit.xzm (18 M)
http://www.mediafire.com/file/824363lrz ... -64bit.xzm
md5sum: 89a8616c1e377c624d11457cf42b891e crippled_sources-4.9.68-64bit.xzm

crippled_sources-4.9.67-32bit.xzm (18 M)
http://www.mediafire.com/file/d12f0qu6k ... -32bit.xzm
md5sum: fd847634f1a70bd25ba4291bca0209de crippled_sources-4.9.67-32bit.xzm

crippled_sources-4.9.67-64bit.xzm (18 M)
http://www.mediafire.com/file/9d8dxopte ... -64bit.xzm
md5sum: ff2dceebf292a403086ecfd41274f3fd crippled_sources-4.9.67-64bit.xzm

crippled_sources-4.9.66-32bit.xzm (18 M)
http://www.mediafire.com/file/f099pe94y ... -32bit.xzm
md5sum: 884461a6b91b56fada238bdae42988dd crippled_sources-4.9.66-32bit.xzm

crippled_sources-4.9.66-64bit.xzm (18 M)
http://www.mediafire.com/file/s6p0d27rd ... -64bit.xzm
md5sum: 62cbeeeaa0f14ad3e90e37912d4ead5e crippled_sources-4.9.66-64bit.xzm

crippled_sources-4.4.105-32bit.xzm (16 M)
http://www.mediafire.com/file/qsn9zg7ns ... -32bit.xzm
md5sum: e1630dea6bbb1a61ffa6221457e6dd74 crippled_sources-4.4.105-32bit.xzm

crippled_sources-4.4.105-64bit.xzm (16 M)
http://www.mediafire.com/file/0wyf4ufu5 ... -64bit.xzm
md5sum: 57c6103219ab60687435afd9e7476b48 crippled_sources-4.4.105-64bit.xzm

-----------------------
At the time of building version 4.9.68 & 4.4.105 kernel,
the patch to drivers/acpi/sleep.c
and
the patch to drivers/mfd/intel-lpss-pci.c
were applied.

At the time of building version 4.15-rc3 & 4.14.5 kernels,
the patch to drivers/acpi/sleep.c was applied.

32 Bit kernel were built with config "CONFIG_TOSHIBA=y"


Thanks.

Porteus Kernel Builder

Posted: 12 Aug 2017, 13:06
by neko
NEW Example of updated kernels that were built by "Porteus Kernel builder" were updated.

Refer to Porteus Kernel Builder (Post by neko #57468)
or
refer to Porteus Kernel Builder (Post by neko #52232)


Thanks.

Porteus Kernel Builder

Posted: 13 Aug 2017, 15:43
by neko
WARNING !!

4.12.6 ---> 4.12.7
4.9.42 ---> 4.9.43
4.4.81 ---> 4.4.82
3.18.64 ---> 3.18.65
These update span were very short. (1 day)

Thanks

Porteus Kernel Builder

Posted: 13 Aug 2017, 21:14
by brokenman
Thanks again for this AWESOME tool!

Porteus Kernel Builder

Posted: 13 Aug 2017, 22:08
by neko
@brokenman

Thank you for encouraging words.

By the way, AUFS patches for version line 4.12 and 4.13-rc need a little modify (own patch).
I have made this own patch in order to avoid the compile error without understanding AUFS context.
I am expecting an official AUFS patch to be offered.
And I am investigating overlay FS as an alternative to AUFS

Thanks.

Porteus Kernel Builder

Posted: 14 Aug 2017, 08:33
by raja
Neko,

You have been updating Kernels regularly. Do you have page where changes incorporated from one to another version are recorded.

Shut down/reboot problems surfaced in 2016, some said it is due to changes made in Kernel, some said it may be due to Systemd. Kernel version has reached 4.13, still Computers like mine suffer from this bug.

Gianpaolo 2016-11-07, analysed this problem and identified, a bad commit,
2c85025c75dfe7ddc2bb33363a998dad59383f94 - ACPI: Execute _PTS before system reboot
as the source of trouble.
ACPI: Execute _PTS before system reboot

The _PTS control method is defined in the section 7.4.1 of acpi 6.0
spec. The _PTS control method is executed by the OS during the sleep
transition process for S1, S2, S3, S4, and for orderly S5 shutdown.

The _PTS control method provides the BIOS a mechanism for performing
some housekeeping, such as writing the sleep type value to the embedded
controller, before entering the system sleeping state. Note that some
Lenovo Server BIOS use this mechanism to detect reboot event and
prompt user by popped dialog box.

According to section 7.5 of acpi 6.0 spec, _PTS should run after _TTS.
Add a _PTS evaulation to the existing _TTS reboot notifier and change
the notifier name to reflect the fact that it's not for _TTS only any
more.
A patch was offered by kernel.org and supposed to have been rectified in subsequent versions, after 4.7. But my Laptop works fine only with v4.4.76. and anything above made to hang, after systemd comment "Reached target Shutdown".

Code: Select all

https://patchwork.kernel.org/patch/9041141/

Patch

diff --git a/drivers/acpi/sleep.c b/drivers/acpi/sleep.c
index 2a8b596..8b290fb 100644
--- a/drivers/acpi/sleep.c
+++ b/drivers/acpi/sleep.c
@@ -55,6 +55,26 @@  static struct notifier_block tts_notifier = {
 	.priority	= 0,
 };
 
+static int pts_notify_reboot(struct notifier_block *this,
+			unsigned long code, void *x)
+{
+	acpi_status status;
+
+	status = acpi_execute_simple_method(NULL, "\\_PTS", ACPI_STATE_S5);
+	if (ACPI_FAILURE(status) && status != AE_NOT_FOUND) {
+		/* It won't break anything. */
+		printk(KERN_NOTICE "Failure in evaluating _PTS object\n");
+	}
+
+	return NOTIFY_DONE;
+}
+
+static struct notifier_block pts_notifier = {
+	.notifier_call	= pts_notify_reboot,
+	.next		= NULL,
+	.priority	= 0,
+};
+
 static int acpi_sleep_prepare(u32 acpi_state)
 {
 #ifdef CONFIG_ACPI_SLEEP
@@ -896,5 +916,12 @@  int __init acpi_sleep_init(void)
 	 * object can also be evaluated when the system enters S5.
 	 */
 	register_reboot_notifier(&tts_notifier);
+
+	/*
+	 * According to section 7.5 of acpi 6.0 spec, _PTS should run after
+	 * _TTS when the system enters S5.
+	 */
+	register_reboot_notifier(&pts_notifier);
+
 	return 0;
 }
Can you confirm if this patch is applied to your kernels?

For your other query on openchrome,

versions, 0.4.1, 0.5.1, and 0.5.3 don't work (deb packages). Version 0.6.0, a rpm package works in Debian Stretch and Apoteus too is okay. But video copy benchmark is too low compared to version 0.3.3.

Porteus Kernel Builder

Posted: 14 Aug 2017, 15:34
by neko
@raja

[ Q & A]
1.Do you have page where changes incorporated from one to another version are recorded.
No, I do not have.
Anybody can check the changes on the kernel page and AUFS page.

2.Can you confirm if this patch is applied to your kernels?
Yes, I can. (And you can too.)
For example, on the case version 4.12.7, this patch is not applied.


[How to apply your own patch]
Please refer to Porteus Kernel Builder (Post by neko #52232)
step 1. prepare tools.
(1)get recent version Kernel Builder.
activate mkKernel-NN.NN.NN-noarch-N.xzm
(2)get 05-devel.xzm for your architecture from Porteus release site.
activate "05-devel.xzm".

step 2. set working direcory.
First, prepare the directory for 'Porteus Kernel Builder'.
This direcory must be in LINUX file system (ext4 etc.,).
From GUI I/F, execute Kernel Builder.
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".
right item will display the latest version of the line.
if older version is needed, select kernel version in right item.

step 4. "Build kernel" circle
"download" item:
---->check it on.

"expand & patch" item:
---->check it on.

"own patch" item:
---->if version is v4.12 line or v4.13-rc line, check it on.

step 5. push OK.

step 6.
(You can confirm if this patch is applied to kernel.)
modify "Kernel Builder directory"/v"Kernel Version"/"architecture"/linux-"Kernel Version"/sleep.c

step 7. (option)
modify kernel configuration.
excute "make menuconfig" command in "Kernel Builder directory"/v"Kernel Version"/"architecture"/linux-"Kernel Version"/ directory.

step 8. compile
From GUI I/F, execute Kernel Builder.
Select "Kernel Builder directory".
Select "kernel version".
"Build kernel" circle "compile" item: ---->check it on
push OK.


-----------------------------
Example:
This patch was applied to kernel version 4.12.7.

v4.12.7-2.tar.xz (41 M)
http://www.mediafire.com/file/odrl9fa8f ... 7-2.tar.xz
md5sum: c21d40f24affdf6b44f234787f74a3fd v4.12.7-2.tar.xz

crippled_sources-4.12.7-2-32bit.xzm (19 M)
http://www.mediafire.com/file/oug1er7u2 ... -32bit.xzm
md5sum: 9d309e7ca7ecc1f487d21fc582a95ddf crippled_sources-4.12.7-2-32bit.xzm

crippled_sources-4.12.7-2-64bit.xzm (19 M)
http://www.mediafire.com/file/r7p454cd7 ... -64bit.xzm
md5sum: 497c40049ed4819a4728db9c2823db0a crippled_sources-4.12.7-2-64bit.xzm



Thanks.