Update the kernel of Porteus v3.1

[francois]

Hello neko. You have nothing to say about the future of porteus?
http://forum.porteus.org/viewtopic.php?f=53&t=5187

[neko]

@francois

I will take a lot of time to understand postes of Porteus members.
For the future, there is no particular opinion to me.
I do not want to disturb interfere with Porteus members.
I'm just participating in the fun Porteus.

I will read using the language translation tool postes of Porteus members now.

Thanks.

[neko]

@francois
wrote

A simple question here. Is it possible to build linux-4.2.3 with the kernel headers that come with? And then could I use these kernel headers with another distribution with the same kernel version?

1.Is it possible to build linux-4.2.3 with the kernel headers that come with?
No, it is not enough.

For example, "/usr/include/sys/types.h" is needed to build.
This is not included in a kernel source 'linux-XXXXX.tar.xz'.
On Archlinux, this is included in 'glibc' package.

On Archlinux, build tools "'gcc','make','patch','git'" need the 'linux-api-headers' package that is one of dependencies.

Note:
At kernel build, the linker might use the static linkage library 'libgcc.a'.

2. Could I use these kernel headers with another distribution with the same kernel version?
Yes, you could use those to build kernel.
But, at kernel build, separated headers usually is not used.
A kernel source 'linux-XXXXX.tar.xz' that includes headers is used.

On Archlinux, the 'linux-headers' package includes the '.config' file.
Therefore it is used for a specific target (depending on distribution and architecture conditions).

--------------------------------------------------
Excuse me for very slow answer.

I needed to prepare some environments.
(Archlinux package tool,minimum Archlinux, build tool, kernel build test, for 32bit/64bit).
Please refer to the following related articles.

[Archlinux package tool]
http://forum.porteus.org/viewtopic.php? ... 997#p36687
http://forum.porteus.org/viewtopic.php? ... 997#p36688

[minimum Archlinux]
http://forum.porteus.org/viewtopic.php? ... 997#p36689

[build tool]
"6.4. get 'gcc compiler','make','patch','git' together with dependency packages." of
http://forum.porteus.org/viewtopic.php? ... =15#p38689


P.S.
Your "simple question" is a heavy question for poor skill me.


Thanks.

[bour59]

hello !
after activate live-usb-3.1-noarch-5.xzm nothing happens when clic 'create live usb'
so I open a terminal and launch /usr/share/live-usb/bin/live-usb
then it's ok

[neko]

@bour59
I think it is a bug.

Before bug fix,
please execute it from a terminal as following.

Code: Select all

% su
# /usr/share/live-usb/bin/live-usb

I am sorry.
I will fix the bug.


Thank you for your report.

[neko]

"upkernel4/upakernel4" command was updated to kernel version 4.2.6.
Please refer to the top article of this thread.

Thanks.

[neko]

@bour59

Problem:
live-usb can not be executed without /opt/porteus-scripts/xorg/psu.

improvement:
live-usb can be executed without /opt/porteus-scripts/xorg/psu.

live-usb-3.1-noarch-6.xzm (340 K)
http://www.mediafire.com/download/ednuz ... arch-6.xzm
md5sum: e10168df8e19ff671ef853be75a6e947 live-usb-3.1-noarch-6.xzm


Thanks.

[bour59]

All's fine now with live-usb-3.1-noarch-6.xzm . Thanks

[Bogomips]

Do not see why this is not working:

Code: Select all

guest@porteus:~$ md5sum upkernel-4.2.6-noarch-1.xzm 
5fe60909cb29070cd434183d0fa3c45c  upkernel-4.2.6-noarch-1.xzm
5fe60909cb29070cd434183d0fa3c45c upkernel-4.2.6-noarch-1.xzm

root@porteus:/home/guest/p10/tmp/iso_tmp# upkernel4 Por-KDE4-v3.1-4.2.5-i486.iso
mount: block device /home/guest/p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
Setting input-charset to 'UTF-8' from locale.
3.01a16 (i686-pc-linux-gnu)
Scanning UP.Por-KDE4-v3.1-4.2.5-i486
...
Max brk space used 44000
150159 extents written (293 MB)

Setting up Iso for Grub

Code: Select all

guest@porteus:~$ ls -lh p10/tmp/iso_tmp/UP.*.iso
-rw-r--r-- 1 root root 294M Nov 13 19:30 p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
ln p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso

Extracting kernel and initrd

Code: Select all

sudo mount p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso z -t iso9660 -o loop
cp -a z/boot/syslinux/vmlinuz /mnt/sda1/por/up3.1/k4.2.6
cp -a z/boot/syslinux/initrd.xz /mnt/sda1/por/up3.1/k4.2.6
ls -lh /mnt/sda1/por/up3.1/k4.2.6
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 15:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 04:27 vmlinuz

Verifying:

Code: Select all

guest@porteus:~$ ls -i p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
2941700 p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
guest@porteus:~$ ls -i p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
2941700 p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso

guest@porteus:~$ ls -lh /mnt/sda1/por/up3.1/k4.2.{5,6}
/mnt/sda1/por/up3.1/k4.2.5:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 15:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 04:27 vmlinuz

/mnt/sda1/por/up3.1/k4.2.6:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 15:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 04:27 vmlinuz

Think from the time stamp it can be seen that we have 4.2.5 again.

P.S. While trying to debug this is very confusing:

DESCRIPTION
upkernel4/upakernel4 is the tool of Updating the Kernel of Porteus ISO.
upkernel4/upakernel4 must be executed by root.

Because I'm thinking for 4.2.6 need to run

Code: Select all

upkernel4/upakernel4  Por-KDE4-v3.1-4.2.5-i486.iso

Just as a suggestion

DESCRIPTION
upkernel4 & upakernel4 are the tool of Updating the Kernel of Porteus ISO.
upkernel4 & upakernel4 must be executed by root.

[neko]

@Bogomips
1.update NG
I followed your operations.

I used a fake "Por-KDE4-v3.1-4.2.5-i486.iso" replaced by "FVWM_ja-kernel.v4.2.5-i486-1.iso".
I replaced "/mnt/sda1/por/" by "/mnt/sda13/porteus/".

Code: Select all

root@porteus:/home/guest/p10/tmp/iso_tmp# ls
FVWM_ja-kernel.v4.2.5-i486-1.iso  upkernel-4.2.6-noarch-1.xzm
root@porteus:/home/guest/p10/tmp/iso_tmp# md5sum upkernel-4.2.6-noarch-1.xzm
5fe60909cb29070cd434183d0fa3c45c  upkernel-4.2.6-noarch-1.xzm
root@porteus:/home/guest/p10/tmp/iso_tmp# mv FVWM_ja-kernel.v4.2.5-i486-1.iso Por-KDE4-v3.1-4.2.5-i486.iso
root@porteus:/home/guest/p10/tmp/iso_tmp# activate upkernel-4.2.6-noarch-1.xzm
Updating shared library links:  /sbin/ldconfig
root@porteus:/home/guest/p10/tmp/iso_tmp# upkernel4 Por-KDE4-v3.1-4.2.5-i486.iso
mount: block device /mnt/sda3/live/porteus/persist/home/guest/p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
3.01a16 (i686-pc-linux-gnu)
Scanning UP.Por-KDE4-v3.1-4.2.5-i486
...
Max brk space used 1d000
99588 extents written (194 MB)

Code: Select all

guest@porteus:~$ ls -lh p10/tmp/iso_tmp/UP.*.iso
-rw-r--r-- 1 root root 195M Nov 15 10:37 p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso
guest@porteus:~$ ln p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
ln: failed to create hard link 'p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso' => 'p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso': No such file or directory
guest@porteus:~$ mkdir -p p10/tmp/iso/
guest@porteus:~$ ln p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso
guest@porteus:~$ mkdir z
guest@porteus:~$ sudo mount p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso z -t iso9660 -o loop
Password:
mount: block device /mnt/sda3/live/porteus/persist/home/guest/p10/tmp/iso/Por-KDE4-v3.1-4.2.6-i486.iso is write-protected, mounting read-only
guest@porteus:~$ mkdir -p /mnt/sda13/porteus/up3.1/k4.2.6
guest@porteus:~$ cp -a z/boot/syslinux/vmlinuz /mnt/sda13/porteus/up3.1/k4.2.6
guest@porteus:~$ cp -a z/boot/syslinux/initrd.xz /mnt/sda13/porteus/up3.1/k4.2.6
guest@porteus:~$ ls -lh /mnt/sda13/porteus/up3.1/k4.2.6
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Nov 11 16:49 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Nov 11 16:41 vmlinuz
guest@porteus:~$ mkdir -p /mnt/sda13/porteus/up3.1/k4.2.5
guest@porteus:~$ sudo umount z
Password:
guest@porteus:~$ sudo mount p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso z -t iso9660 -o loop
mount: block device /mnt/sda3/live/porteus/persist/home/guest/p10/tmp/iso_tmp/Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
guest@porteus:~$ cp -a z/boot/syslinux/vmlinuz /mnt/sda13/porteus/up3.1/k4.2.5
guest@porteus:~$ cp -a z/boot/syslinux/initrd.xz /mnt/sda13/porteus/up3.1/k4.2.5
guest@porteus:~$ ls -lh /mnt/sda13/porteus/up3.1/k4.2.{5,6}
/mnt/sda13/porteus/up3.1/k4.2.5:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Oct 28 14:51 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Oct 28 03:27 vmlinuz

/mnt/sda13/porteus/up3.1/k4.2.6:
total 4.2M
-rw-r--r-- 1 guest guest 1.6M Nov 11 16:49 initrd.xz
-rw-r--r-- 1 guest guest 2.6M Nov 11 16:41 vmlinuz
guest@porteus:~$ md5sum /mnt/sda13/porteus/up3.1/k4.2.5/*
92491bffaff77934080e8194c9cc7363  /mnt/sda13/porteus/up3.1/k4.2.5/initrd.xz
547a504a8da635af0b63e1d1413a18e3  /mnt/sda13/porteus/up3.1/k4.2.5/vmlinuz
guest@porteus:~$ md5sum /mnt/sda13/porteus/up3.1/k4.2.6/*
0087edd3d4561580ad54579b33e30dc9  /mnt/sda13/porteus/up3.1/k4.2.6/initrd.xz
cfecb7913394543a6e7f270fb545e050  /mnt/sda13/porteus/up3.1/k4.2.6/vmlinuz

The kernel of your Por-KDE4-v3.1-4.2.6-i486.iso may be not k4.2.6.

Please check the tool before executing it as following.

Code: Select all

root@porteus:/home/guest/p10/tmp/iso_tmp# which upkernel4
/usr/local/sbin/upkernel4
root@porteus:/home/guest/p10/tmp/iso_tmp# ls -l /usr/local/sbin/upkernel4
lrwxrwxrwx 1 root root 36 Nov 11 16:50 /usr/local/sbin/upkernel4 -> ../share/upkernel/bin/upkernel.4.2.6*

2.The command description is confusing mistake.
I am sorry.
I updated the description.
Thank you to poit out.


Thanks.

[Bogomips]

@neko

Much appreciated that you took the time to check everything for me. Normally edit all statements in a text editor before pasting into terminal. So used same statements, but just up to creation of new iso, then checked:

Code: Select all

guest@porteus:~$ sudo mount  p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso  z -t iso9660 -o loop
mount: block device /home/guest/p10/tmp/iso_tmp/UP.Por-KDE4-v3.1-4.2.5-i486.iso is write-protected, mounting read-only
guest@porteus:~$ ls -lh z/boot/syslinux/vmlinuz z/boot/syslinux/initrd.xz 
-rw-r--r-- 1 root root 1.6M Nov 11 17:49 z/boot/syslinux/initrd.xz
-rw-r--r-- 1 root root 2.6M Nov 11 17:41 z/boot/syslinux/vmlinuz
guest@porteus:~$ md5sum z/boot/syslinux/vmlinuz z/boot/syslinux/initrd.xz 
cfecb7913394543a6e7f270fb545e050  z/boot/syslinux/vmlinuz
0087edd3d4561580ad54579b33e30dc9  z/boot/syslinux/initrd.xz

Cannot understand how 4.2.5 could have been activated. Must have been the Friday 13th energy.
Thanks again.

[brokenman]

People wanting to update to latest kernel 4.3 (x86_64 only) can download the latest Nemesis version and replace vmlinuz and 000-kernel.xzm with the current version.

BE AWARE that you will need to unpack 000-kernel and place /usr/lib/modules into /lib/modules (remove /lib symlink) then repack. I have included much more firmware in this 000-kernel module.

[neko]

============================================================================
@Bogomips
Thank you for your report.

Thanks.

============================================================================
@brokenman
Thank you for your advice.

'upnkernel' commnad was uploaded for Nemesis ISO.

Thanks.

============================================================================
@all
'upnkernel' - Updating the Kernel of Nemesis v3.2 ISO file
'upkernel4.3', - Updating the Kernel of Porteus ISO file
'upakernel4.3' - Updating the Kernel of Porteus ISO file and formatting 000-kernel.xzm on the ArchLinux style.

were uploaded.

Please refer to top article of this thread.

Thanks.

[Bogomips]

@neko

4.2.6 32 bit. Noticed irregularities, particularly with restoring minimised window. There is noticeable delay after drawing the frame, before the window filled in (gtk+3). Finally stuck in open dialog of text editor, when trying to open 'menu.lst' for 4.3 update. 100% cpu, Alt+SysRq+F did not work. Had to reisub.

[brokenman]

I am trying to implement an 'update kernel' feature in Nemesis so that one may boot into copy2ram and update there live system. There will also be the option to update an ISO file. Perhaps you should be 'the kernel guy'.