Update the kernel of Porteus v3.1

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...
Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Update the kernel of Porteus v3.1

Post#16 by Bogomips » 18 Jul 2015, 02:01

Download the iso from http://dl.porteus.org/, make the new iso. then
Jack wrote:unpack the iso on a ext4 formated thumb drive.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

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

Re: Update the kernel of Porteus v3.1

Post#17 by neko » 18 Jul 2015, 02:43

=============================================================================
@Jack

If you expanded ISO on the /mnt/sdb1/ext4-formated-thumb-drive-place,
you can update kernel with following steps.

-----------------------------------------
% su
# ls /mnt/sdb1/ext4-formated-thumb-drive-place
boot porteus
# mv /mnt/sdb1/ext4-formated-thumb-drive-place/boot/docs/cheatcodes.txt /mnt/sdb1/ext4-formated-thumb-drive-place/boot/docs/old.cheatcodes.txt
# mv /mnt/sdb1/ext4-formated-thumb-drive-place/boot/syslinux/initrd.xz /mnt/sdb1/ext4-formated-thumb-drive-place/boot/syslinux/old.initrd.xz
# mv /mnt/sdb1/ext4-formated-thumb-drive-place/boot/syslinux/vmlinuz /mnt/sdb1/ext4-formated-thumb-drive-place/boot/syslinux/old.vmlinuz
# mv /mnt/sdb1/ext4-formated-thumb-drive-place/porteus/base/000-kernel.xzm /mnt/sdb1/ext4-formated-thumb-drive-place/porteus/base/old.000-kernel.xzm

# activate upkernel-3.18.18-noarch-1.xzm

[32 bit]
# cp -a /usr/share/upkernel/Kernel.v3.18.18-i486-1/* /mnt/sdb1/ext4-formated-thumb-drive-place/.
[64 bit]
# cp -a /usr/share/upkernel/Kernel.v3.18.18-x86_64-1/* /mnt/sdb1/ext4-formated-thumb-drive-place/.

# deactivate upkernel-3.18.18-noarch-1.xzm
-----------------------------------------

If you want to recover old kernel,
you may move "old.cheatcodes.txt old.initrd.xz old.vmlinuz and old.000-kernel.xzm"
to "cheatcodes.txt initrd.xz vmlinuz and 000-kernel.xzm" .


=============================================================================
@Bogomips
I will try to evaluate a application performance too.

The main reasons that I have updated kernel
are
1. that 360 degree youtube can be watched,
and
2. that Porteus on HDD via USB3-SATA can be booted.



=============================================================================

Thanks.

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

Re: Update the kernel of Porteus v3.1

Post#18 by neko » 18 Jul 2015, 13:50

==== Evaluation Report ====
All results of old kernel's benchmark were better than ones of new.

[tested Computer] LIVA
Processor : 2x Intel(R) Celeron(R) CPU N2807 @ 1.58GHz
Memory : 1894MB (326MB used)
===========================================================
[Benchmarks]
-CPU Blowfish-
Results in seconds. Lower is better.
O old: 2166 MHz 11.169
X new: 2166 MHz 11.182

-CPU CryptoHash-
Results in MiB/seconds. Higher is better.
O old: 2166 MHz 113.351
X new: 2166 MHz 111.487

-CPU Fibonacci-
Results in seconds. Lower is better.
O old: 2166 MHz 1.655
X new: 2166 MHz 1.657

-CPU N-Queens-
Results in seconds. Lower is better.
O old: 2166 MHz 15.510
X new: 2166 MHz 15.678

-FPU FFT-
Results in seconds. Lower is better.
O old: 2166 MHz 8.892
X new: 2166 MHz 8.974

-FPU Raytracing-
Results in seconds. Lower is better.
O old: 2166 MHz 44.367
X new: 2166 MHz 44.457

-GPU Drawing-
Results in HiMarks. Higher is better.
O old: 2166 MHz 8519.794
X new: 2166 MHz 8463.362

===========================================================
[Benchmarks test tool modules]
This article was integrated into the Tools of "Upkernel".
Please refer to
http://forum.porteus.org/viewtopic.php? ... 788#p34856

===========================================================

Thanks.
Last edited by neko on 10 Aug 2015, 03:55, edited 2 times in total.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Update the kernel of Porteus v3.1

Post#19 by Bogomips » 18 Jul 2015, 14:10

Which goes to show that new kernel benefits older, outdated machines with less memory and less power. :)
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

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

Re: Update the kernel of Porteus v3.1

Post#20 by neko » 19 Jul 2015, 04:50

==== Evaluation Report 2 ====
Following results of old kernel are better.
-CPU Blowfish-
-CPU CryptoHash-
-CPU Fibonacci-
-FPU Raytracing-

Following results of new kernel are better.
-CPU N-Queens-
-FPU FFT-
-GPU Drawing-

[tested Computer] EeePC900A (Old net book)
Processor : 2x Intel(R) Atom(TM) CPU N270 @ 1.60GHz
Memory : 2063MB (157MB used)
===========================================================
[Benchmarks]
-CPU Blowfish-
O old: 1600 MHz 18.777
X new: 1600 MHz 18.852

-CPU CryptoHash-
O old: 1600 MHz 57.909
X new: 1600 MHz 56.463

-CPU Fibonacci-
O old: 1600 MHz 2.686
X new: 1600 MHz 2.722

-CPU N-Queens-
X old: 1600 MHz 10.645
O new: 1600 MHz 10.431

-FPU FFT-
X old: 1600 MHz 19.937
O new: 1600 MHz 19.913

-FPU Raytracing-
O old: 1600 MHz 64.849
X new: 1600 MHz 66.313

-GPU Drawing-
X old: 1600 MHz 3024.400
O new: 1600 MHz 3056.545

===========================================================
["ISO to USB" conversion tool module]
This article was integrated into the Tools of "Upkernel".
Please refer to
http://forum.porteus.org/viewtopic.php? ... 788#p34856

===========================================================


Thanks.
Last edited by neko on 10 Aug 2015, 03:56, edited 5 times in total.

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

Re: Update the kernel of Porteus v3.1

Post#21 by neko » 21 Jul 2015, 11:41

====== kernel v3.18.18 + vivaldi browser ======
360 degrees youtube can be watched by vivaldi browser running on kernel v3.18.18.

[32 bit]
004-vivaldi-TP4.1.0.219.50-i386-1.xzm (47 M)
http://www.mediafire.com/download/74t0z ... i386-1.xzm
md5sum: 93acee41270db312a80f7f11b546fe98 004-vivaldi-TP4.1.0.219.50-i386-1.xzm

[64 bit]
004-vivaldi-TP4.1.0.219.50-amd64-1.xzm (46 M)
http://www.mediafire.com/download/va6zo ... md64-1.xzm
md5sum: 2d2a4aa2995c27498ca39e3627c6c98d 004-vivaldi-TP4.1.0.219.50-amd64-1.xzm

About vivaldi browser, please refer to
https://vivaldi.com/


Thanks.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Update the kernel of Porteus v3.1

Post#22 by Bogomips » 23 Jul 2015, 18:31

Question: Can upkernel be used to upgrade 3.18.18 iso to 3.18.19?
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

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

Re: Update the kernel of Porteus v3.1

Post#23 by neko » 23 Jul 2015, 23:40

@Bogomips wrote
"Can upkernel be used to upgrade 3.18.18 iso to 3.18.19?"

No,it can not be used to upgrade 3.18.18 iso.
It is used to upgrade to only Porteus V3.1 iso.

But, new 'upkernel.3.18.19' shell script can upgrade a upgraded ISO.

Activate upkernel-3.18.19-noarch-1.xzm,
and then execute new 'upkernel.3.18.19' shell script.
---------------------------------------------------------------------------------
% su
# activate upkernel-3.18.19-noarch-1.xzm
# chmod +x upkernel.3.18.19
# ./upkernel.3.18.19 upgraded-ISO
---------------------------------------------------------------------------------


[new 'upkernel.3.18.19' shell script]
upkernel.3.18.19 (1.6 K)
http://www.mediafire.com/download/xpobb ... el.3.18.19
---------------------------------------------------------------------------------
% diff /usr/share/upkernel/upkernel.3.18.19 upkernel.3.18.19
49c49
< ls /tmp/$BASE/porteus/porteus-v3.1-i486.sgn >/dev/null 2>&1
---
> ls /tmp/$BASE/porteus/*-i486.sgn >/dev/null 2>&1
51a52
> rm /tmp/$BASE/porteus/*-i486.sgn
53d53
< rm /tmp/$BASE/porteus/porteus-v3.1-i486.sgn
58c58
< ls /tmp/$BASE/porteus/porteus-v3.1-x86_64.sgn >/dev/null 2>&1
---
> ls /tmp/$BASE/porteus/*-x86_64.sgn >/dev/null 2>&1
60a61
> rm /tmp/$BASE/porteus/*-x86_64.sgn
62d62
< rm /tmp/$BASE/porteus/porteus-v3.1-x86_64.sgn
68c68
< echo "$1 is not Porteus V3.1 ISO file."
---
> echo "$1 is not Porteus ISO file."
---------------------------------------------------------------------------------

Thanks.

============================================================
[ updated to upkernel-3.18.20-noarch-1.xzm ]
example 3.
------------------------------------------------------
% ls
Porteus-KDE4-v3.1-x86_64.iso
upkernel-3.18.19-noarch-1.xzm
upkernel-3.18.20-noarch-1.xzm
% su
# activate upkernel-3.18.19-noarch-1.xzm
# upkernel Porteus-KDE4-v3.1-x86_64.iso
# ls
Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso
upkernel-3.18.19-noarch-1.xzm
upkernel-3.18.20-noarch-1.xzm
# deactivate upkernel-3.18.19-noarch-1.xzm
# activate upkernel-3.18.20-noarch-1.xzm
# upkernel UP.Porteus-KDE4-v3.1-x86_64.iso
# ls
Porteus-KDE4-v3.1-x86_64.iso
UP.Porteus-KDE4-v3.1-x86_64.iso
UP.UP.Porteus-KDE4-v3.1-x86_64.iso
upkernel-3.18.19-noarch-1.xzm
upkernel-3.18.20-noarch-1.xzm
------------------------------------------------------
note)
UP.Porteus-KDE4-v3.1-x86_64.iso is updated to kernel 3.18.19.
UP.UP.Porteus-KDE4-v3.1-x86_64.iso is updated to kernel 3.18.20 from 3.18.19.


Thanks.
Last edited by neko on 09 Aug 2015, 14:07, edited 2 times in total.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Update the kernel of Porteus v3.1

Post#24 by Bogomips » 24 Jul 2015, 21:38

Had a bit of difficulty:

Code: Select all

root@porteus:/home/guest/p10/tmp/iso_tmp# chmod +x upkernel.3.18.19
root@porteus:/home/guest/p10/tmp/iso_tmp# ./upkernel.3.18.19 UPrmPor-KDE4-v3.1-i486.iso 
mount: block device /home/guest/p10/tmp/iso_tmp/UPrmPor-KDE4-v3.1-i486.iso is write-protected, mounting read-only
cp: error writing ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/optional/3.1/DE/003-mate.xzm’: No space left on device
cp: failed to extend ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/optional/3.1/DE/003-mate.xzm’: No space left on device
cp: error writing ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/optional/3.1/DE/003-xfce.xzm’: No space left on device
cp: failed to extend ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/optional/3.1/DE/003-xfce.xzm’: No space left on device
cp: error writing ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/rootcopy/etc/rc.d/rc.local’: No space left on device
cp: failed to extend ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/rootcopy/etc/rc.d/rc.local’: No space left on device
cp: error writing ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/rootcopy/etc/sudoers’: No space left on device
cp: failed to extend ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/rootcopy/etc/sudoers’: No space left on device
cp: error writing ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/rootcopy/var/lib/alsa/asound.state’: No space left on device
cp: failed to extend ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/rootcopy/var/lib/alsa/asound.state’: No space left on device
cp: error writing ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/base/000-kernel.xzm’: No space left on device
cp: failed to extend ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/base/000-kernel.xzm’: No space left on device
cp: error writing ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/kernel-v3.18.19-i486.sgn’: No space left on device
cp: failed to extend ‘/tmp/UPrmPor-KDE4-v3.1-i486/./porteus/kernel-v3.18.19-i486.sgn’: No space left on device
Setting input-charset to 'UTF-8' from locale.
3.01a16 (i686-pc-linux-gnu)
Scanning /tmp/UPrmPor-KDE4-v3.1-i486
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/porteus
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/porteus/rootcopy
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/porteus/rootcopy/var
...
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/porteus/changes/etc/rc.d
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/porteus/changes/etc/cron.daily
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/porteus/base
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/boot
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/boot/syslinux
Excluded by match: /tmp/UPrmPor-KDE4-v3.1-i486/boot/syslinux/isolinux.boot
Scanning /tmp/UPrmPor-KDE4-v3.1-i486/boot/docs
Using VND_KDE_SERVICE_UPNP_MED000.XML;1 for  /tmp/UPrmPor-KDE4-v3.1-i486/porteus/changes/usr/share/mime/inode/vnd.kde.service.upnp.MediaRenderer1.xml (vnd.kde.service.upnp.MediaRenderer2.xml)
...
Using VND_OASIS_OPENDOCUMENT_S001.XML;1 for  /tmp/UPrmPor-KDE4-v3.1-i486/porteus/changes/usr/share/mime/application/vnd.oasis.opendocument.spreadsheet-template.xml (vnd.oasis.opendocument.spreadsheet-flat-xml.xml)
Using VND_OASIS_OPENDOCUMENT_C000.XML;1 for  /tmp/UPrmPor-KDE4-v3.1-i486/porteus/changes/usr/share/mime/application/vnd.oasis.opendocument.chart.xml (vnd.oasis.opendocument.chart-template.xml)
Writing:   Initial Padblock                        Start Block 0
Done with: Initial Padblock                        Block(s)    16
Writing:   Primary Volume Descriptor               Start Block 16
Done with: Primary Volume Descriptor               Block(s)    1
Writing:   Eltorito Volume Descriptor              Start Block 17
Size of boot image is 4 sectors -> No emulation
Done with: Eltorito Volume Descriptor              Block(s)    1
Writing:   Joliet Volume Descriptor                Start Block 18
Done with: Joliet Volume Descriptor                Block(s)    1
Writing:   End Volume Descriptor                   Start Block 19
Done with: End Volume Descriptor                   Block(s)    1
Writing:   Version block                           Start Block 20
Done with: Version block                           Block(s)    1
Writing:   Path table                              Start Block 21
Done with: Path table                              Block(s)    4
Writing:   Joliet path table                       Start Block 25
Done with: Joliet path table                       Block(s)    4
Writing:   Directory tree                          Start Block 29
Done with: Directory tree                          Block(s)    238
Writing:   Joliet directory tree                   Start Block 267
Done with: Joliet directory tree                   Block(s)    192
Writing:   Directory tree cleanup                  Start Block 459
Done with: Directory tree cleanup                  Block(s)    0
Writing:   Extension record                        Start Block 459
Done with: Extension record                        Block(s)    1
Writing:   The File(s)                             Start Block 460
  3.77% done, estimate finish Fri Jul 24 14:55:31 2015
  7.53% done, estimate finish Fri Jul 24 14:54:25 2015
...
 94.09% done, estimate finish Fri Jul 24 14:53:30 2015
 97.84% done, estimate finish Fri Jul 24 14:53:30 2015
Total translation table size: 2048
Total rockridge attributes bytes: 140802
Total directory bytes: 479232
Path table size(bytes): 2534
Done with: The File(s)                             Block(s)    132260
Writing:   Ending Padblock                         Start Block 132720
Done with: Ending Padblock                         Block(s)    150
Max brk space used 14f000
132870 extents written (259 MB)

root@porteus:/home/guest/p10/tmp/iso_tmp# ls -lh
total 801M
-rw------- 1 guest guest 210M Jun 14 22:26 Porteus-KDE4-v3.1up-i486.iso
-rw-r--r-- 1 root  root  260M Jul 24 14:53 UP.UPrmPor-KDE4-v3.1-i486.iso
-rw-r--r-- 1 root  root    64 Jul 24 14:53 UP.UPrmPor-KDE4-v3.1-i486.iso.md5
-rw------- 2 guest guest 330M Jul 23 22:03 UPrmPor-KDE4-v3.1-i486.iso
-rwxr-xr-x 1 guest guest 1.6K Jul 24 14:34 upkernel.3.18.19*
But managed it in the end :wink:

Code: Select all

dISO()
{
DIR=`basename $1 .iso`
mkdir /iso/${DIR} /iso/TMP
mount -o loop $1 /iso/TMP
cp -a /iso/TMP/* /iso/${DIR}/.
cp -a /iso/TMP/.[0-9A-Za-z]* /iso/${DIR}/. 2>/dev/null
umount /iso/TMP
rm -fr /iso/TMP
}
#--------------------< end of dISO >-----------------------------------#
#---------------------------------
mkISO()
{
CDLABEL=Porteus
ISO=`basename $1`
ISO=UP.${ISO}.iso

mkisofs -o ${ISO} -v -l -J -joliet-long  -R -D -A ${CDLABEL} -V ${CDLABEL} \
-no-emul-boot -boot-info-table -boot-load-size 4 \
-b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot $1

md5sum ${ISO} > ${ISO}.md5
}
#--------------------< end of mkISO >-----------------------------------#
upkernel()
{
if [ `whoami` != root ]
then
	echo "This command must be used by root."
	exit 1
fi
ARGISO="$1"
ARG="${ARGISO%.iso}"
if [ "$ARGISO" = "$ARG" ]
then
	echo "$1 is not ISO file."
	exit 1
fi
file $1 | grep -q 'ISO 9660 CD-ROM' 2>/dev/null
if [ $? -ne 0 ]
then
	echo "$1 is not ISO file."
	exit 1
fi
BASE=`basename $1 .iso`
#echo "$BASE"
#	frugal live	2015-07-24 17:15:11
! [[ -d /iso ]] && mkdir /iso
! [[ -f /iso/iso_tmp ]] && mount --bind /mnt/sda1/tmp/iso /iso
! [[ -f /iso/iso_tmp ]] && { echo Redirection failure!; exit 1; }
#	frugal prolog ends
dISO $1
ls /iso/$BASE/porteus/*-i486.sgn >/dev/null 2>&1
if [ $? -eq 0 ]
then
	rm  /iso/$BASE/porteus/*-i486.sgn
	cp -a /usr/share/upkernel/Kernel.v3.18.19-i486-1/* /iso/$BASE/.
	mkISO /iso/$BASE
	rm -fr /iso/$BASE
	umount /iso
	exit 0
fi
ls /iso/$BASE/porteus/*-x86_64.sgn >/dev/null 2>&1
if [ $? -eq 0 ]
then
	rm  /iso/$BASE/porteus/*-x86_64.sgn
	cp -a /usr/share/upkernel/Kernel.v3.18.19-x86_64-1/* /iso/$BASE/.
	mkISO /iso/$BASE
	rm -fr /iso/$BASE
	umount /iso
	exit 0
fi
rm -fr /iso/$BASE
echo "$1 is not Porteus ISO file."
	umount /iso
exit 1
}
Running the Update:

Code: Select all

guest@porteus:~$ touch /mnt/sda1/tmp/iso/iso_tmp

root@porteus:/home/guest/p10/tmp/iso_tmp# . upkernel.3.18.19                  
root@porteus:/home/guest/p10/tmp/iso_tmp# upkernel UPrmPor-KDE4-v3.1-i486.iso 
mount: block device /home/guest/p10/tmp/iso_tmp/UPrmPor-KDE4-v3.1-i486.iso is write-protected, mounting read-only
Setting input-charset to 'UTF-8' from locale.
3.01a16 (i686-pc-linux-gnu)
Scanning /iso/UPrmPor-KDE4-v3.1-i486
Scanning /iso/UPrmPor-KDE4-v3.1-i486/boot
...
Scanning /iso/UPrmPor-KDE4-v3.1-i486/porteus/changes/home/guest/.local/share/Trash
Scanning /iso/UPrmPor-KDE4-v3.1-i486/porteus/changes/home/guest/.local/share/Trash/info
Scanning /iso/UPrmPor-KDE4-v3.1-i486/porteus/changes/home/guest/.local/share/Trash/files
Scanning /iso/UPrmPor-KDE4-v3.1-i486/porteus/changes/root
Using VND_KDE_SERVICE_UPNP_MED000.XML;1 for  /iso/UPrmPor-KDE4-v3.1-i486/porteus/changes/usr/share/mime/inode/vnd.kde.service.upnp.MediaRenderer2.xml (vnd.kde.service.upnp.MediaRenderer1.xml)
...
Using VND_OASIS_OPENDOCUMENT_S001.XML;1 for  /iso/UPrmPor-KDE4-v3.1-i486/porteus/changes/usr/share/mime/application/vnd.oasis.opendocument.spreadsheet-flat-xml.xml (vnd.oasis.opendocument.spreadsheet.xml)
Writing:   Initial Padblock                        Start Block 0
Done with: Initial Padblock                        Block(s)    16
Writing:   Primary Volume Descriptor               Start Block 16
Done with: Primary Volume Descriptor               Block(s)    1
Writing:   Eltorito Volume Descriptor              Start Block 17
Size of boot image is 4 sectors -> No emulation
Done with: Eltorito Volume Descriptor              Block(s)    1
...
Writing:   Directory tree cleanup                  Start Block 459
Done with: Directory tree cleanup                  Block(s)    0
Writing:   Extension record                        Start Block 459
Done with: Extension record                        Block(s)    1
Writing:   The File(s)                             Start Block 460
  2.96% done, estimate finish Fri Jul 24 20:59:25 2015
  5.92% done, estimate finish Fri Jul 24 20:59:25 2015
...
 94.67% done, estimate finish Fri Jul 24 20:59:36 2015
 97.62% done, estimate finish Fri Jul 24 20:59:36 2015
Total translation table size: 2048
Total rockridge attributes bytes: 140802
Total directory bytes: 479232
Path table size(bytes): 2534
Done with: The File(s)                             Block(s)    168407
Writing:   Ending Padblock                         Start Block 168867
Done with: Ending Padblock                         Block(s)    150
Max brk space used 149000
169017 extents written (330 MB)
exit

guest@porteus:~$ ls -lh p10/tmp/iso_tmp
total 661M
-rw-r--r-- 1 root  root  331M Jul 24 20:59 UP.UPrmPor-KDE4-v3.1-i486.iso
-rw-r--r-- 1 root  root    64 Jul 24 20:59 UP.UPrmPor-KDE4-v3.1-i486.iso.md5
-rw------- 2 guest guest 330M Jul 23 22:03 UPrmPor-KDE4-v3.1-i486.iso
-rwxr-xr-x 1 guest guest 1.8K Jul 24 20:58 upkernel.3.18.19*

guest@porteus:~$ uname -a
Linux porteus 3.18.19-porteus #1 SMP PREEMPT Thu Jul 23 17:00:20 Local time zone must be set-- i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
First impression, seems a bit slower than 3.18.18, but could be wrong. :unknown:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

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

Re: Update the kernel of Porteus v3.1

Post#25 by neko » 25 Jul 2015, 09:20

@Bogomips

1. This tool is not enough to care errors.
Normal error cases must be cared.
I think that "No space left on device" error is a normal error.
So, at next update, I will care this case.

A very easy way is to limit usage.
The new 'upkernel' command needs to be executed in the working directory
that there is twice the size free of the size of the ISO of interest.


2. Evaluation of 3.18.19
I couldn't distinguish the difference between 3.18.18 and 3.18.19.
But I believe that 3.18.19 is more stable than 3.18.18.


Thanks.

---------------------------------------------
[updated to upkernel-3.18.20-noarch-1.xzm]

The current directory,
it is necessary there is a free space more than twice the target ISO.

Thanks.
Last edited by neko on 09 Aug 2015, 11:49, edited 1 time in total.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Update the kernel of Porteus v3.1

Post#26 by Bogomips » 26 Jul 2015, 23:51

Used new kernel from 15th July, and blissfully unaware of "running on empty" for five days, with Nouveau driving the Nvidia card, and not the Nvidia driver. :shock: The reason for this being that in Kernel 3.17.4 after activation of nVidia-304.123-porteus-v3.1-i486-1ftm.xzm, we have:

Code: Select all

Xorg.0.log
...
[    20.698] (II) LoadModule: "glx"
[    20.704] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    21.671] (II) Module glx: vendor="NVIDIA Corporation"
[    21.671]    compiled for 4.0.2, module version = 1.0.0
[    21.671]    Module class: X.Org Server Extension
[    21.671] (II) NVIDIA GLX Module  304.123  Wed Jul  2 11:29:39 PDT 2014
[    21.671] Loading extension GLX
[    21.671] (II) LoadModule: "nvidia"
[    21.671] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    21.764] (II) Module nvidia: vendor="NVIDIA Corporation"
[    21.764]    compiled for 4.0.2, module version = 1.0.0
[    21.764]    Module class: X.Org Video Driver
[    21.791] (II) NVIDIA dlloader X Driver  304.123  Wed Jul  2 11:09:51 PDT 2014
[    21.791] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
But with Kernel 3.18.18:

Code: Select all

kdm.log
...
Loading extension GLX
modprobe: FATAL: Module nvidia not found.
(EE)

Xorg.0.log.old
[    20.582] (II) LoadModule: "glx"
[    20.588] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    21.538] (II) Module glx: vendor="NVIDIA Corporation"
[    21.538] 	compiled for 4.0.2, module version = 1.0.0
[    21.538] 	Module class: X.Org Server Extension
[    21.538] (II) NVIDIA GLX Module  304.123  Wed Jul  2 11:29:39 PDT 2014
[    21.538] Loading extension GLX
[    21.538] (II) LoadModule: "nvidia"
[    21.538] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    21.631] (II) Module nvidia: vendor="NVIDIA Corporation"
[    21.631] 	compiled for 4.0.2, module version = 1.0.0
[    21.631] 	Module class: X.Org Video Driver
[    21.660] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
[    21.660] (EE) NVIDIA:     system's kernel log for additional error messages.
[    21.660] (II) UnloadModule: "nvidia"
[    21.660] (II) Unloading nvidia
[    21.660] (EE) Failed to load module "nvidia" (module-specific error, 0)
[    21.660] (EE) No drivers available.

Xorg.0.log
[    24.837] (II) LoadModule: "nouveau"
[    24.837] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    24.846] (II) Module nouveau: vendor="X.Org Foundation"
[    24.846] 	compiled for 1.14.5, module version = 1.0.11
[    24.846] 	Module class: X.Org Video Driver
[    24.846] 	ABI class: X.Org Video Driver, version 14.1
[    24.846] (II) LoadModule: "nv"
[    24.847] (WW) Warning, couldn't open module nv
[    24.847] (II) UnloadModule: "nv"
[    24.847] (II) Unloading nv
[    24.847] (EE) Failed to load module "nv" (module does not exist, 0)
...
[    41.982] (II) NOUVEAU driver 
[    41.982] (II) NOUVEAU driver for NVIDIA chipset families :
...
[    41.985] (--) NOUVEAU(0): Chipset: "NVIDIA NV4C"
[    41.985] (II) NOUVEAU(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    41.985] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
It is clear that this kernel was not compiled with NVIDIA modules, as a result of which it seems the old Nouveau driver from 2012 has taken over. Now, on the rc for 3.1 could use Nouveau for a bit until something went awry or worst case scenario screen memory got overwritten with some sort of pattern. In short, after a while the instability started to show. :( However, it appears that the newer kernels are able to hold Nouveau in check, and suppress this instability, which I have not noticed when running with the kernels 3.18.18 and 3.18.19. So, as far as I am concerned, I have no need for the Nvidia driver with these later kernels.

Also tried the acid test: a java browser applet with heavy graphics demand and minimum of four open windows, some of which are hierarchical. Quite a while back tried this using icedtea browser plugin, openjre and firefox, with nvidia driver, At end of application had trouble closing one of the windows, which meant applet could not be terminated. Tried again this time, using java browser plugin, Oracle java and PaleMoon. Again met problem closing same window, but seems to be intermittent. Does not look like it is graphics related, although cpu goes into overdrive 100% and not all apps being able to respond. Resorted to Magic SysRq (Alt+SysRq+f), which resolved situation by killing java browser plugin. Seems more than likely to be some sort of incompatibility with Porteus system.

On a brighter note, using a stopwatch and timing from moment of hitting Grub entry, and loading from iso with copy2ram, changes, rootcopy; activation of VLC, python, gtk+3; opening of Konsole, Kate, Nautilus windows; right up to final opening of PaleMoon window, took 1min 35sec with kernel 3.18.18 and 1min 34sec with kernel 3.18.19. Confirming that there does not seem to be any difference performance wise between the kernels.

neko, thanks for affording us the opportunity to enhance our systems, and for help in the enhancement itself. :beer:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

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

Re: Update the kernel of Porteus v3.1

Post#27 by neko » 27 Jul 2015, 10:21

@Bogomips

1. "NOUVEAU of kernel 3.18.xx"
I will thank you pointed out.
I was offered a new Kernel update tool without understanding the NOUVEAU.
I will study to read the following site from now.
http://gentoo-en.vfose.ru/wiki/Nouveau# ... tor_issues

2. "Quantitative evaluation of the new kernel"
Thanks to YOU of quantitative evaluation.
I did only sensuous qualitative evaluation.

Thanks.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Update the kernel of Porteus v3.1

Post#28 by Bogomips » 27 Jul 2015, 12:24

neko wrote:@Bogomips

1. "NOUVEAU of kernel 3.18.xx"
I will thank you pointed out.
I was offered a new Kernel update tool without understanding the NOUVEAU.
I will study to read the following site from now.
http://gentoo-en.vfose.ru/wiki/Nouveau# ... tor_issues
In that case don't miss the link: http://nouveau.freedesktop.org/wiki/InstallNouveau/

Code: Select all

[    40.906] (II) NOUVEAU driver for NVIDIA chipset families :
[    40.906] 	RIVA TNT        (NV04)
[    40.906] 	RIVA TNT2       (NV05)
[    40.906] 	GeForce 256     (NV10)
[    40.906] 	GeForce 2       (NV11, NV15)
[    40.906] 	GeForce 4MX     (NV17, NV18)
[    40.906] 	GeForce 3       (NV20)
[    40.906] 	GeForce 4Ti     (NV25, NV28)
[    40.906] 	GeForce FX      (NV3x)
[    40.906] 	GeForce 6       (NV4x)
[    40.906] 	GeForce 7       (G7x)
[    40.906] 	GeForce 8       (G8x)
[    40.906] 	GeForce GTX 200 (NVA0)
[    40.906] 	GeForce GTX 400 (NVC0)
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Kriss
Samurai
Samurai
Posts: 135
Joined: 06 Jul 2011, 07:07
Location: Russia

Re: Update the kernel of Porteus v3.1

Post#29 by Kriss » 29 Jul 2015, 03:03

neko, can you please provide 05-devel.xzm (x86 and x86_64) for 3.18.19 kernel?
Then I'll compile Nvidia 352.21 modules.
I tried to use standard 05-devel.xzm + kernel-3.18.19 sources but failed. Nvidia installer didn't find "/usr/src/linux/uart/include/linux/version.h".
This file doesn't exist in kernel-3.18.19 sources...
I'll try again soon, I just can't use porteus without nvidia driver. =)
Suggestions/corrections/additions are always welcome.

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

Re: Update the kernel of Porteus v3.1

Post#30 by neko » 29 Jul 2015, 09:01

@Kriss
Although (/usr/src/linux/uart/include/linux/version.h) something is unknown,

By analogy from the existing relationship
(/usr/src/linux/include/linux/version.h -> uapi/linux/version.h),

(linux-3.18.19/include/linux/version.h -> ../generated/uapi/linux/version.h) ,may be possible, could be used.

Please forgive my ignorance

---------------------------------------------------
# cd linux-3.18.19/include/linux
# ln -sf ../generated/uapi/linux/version.h .
---------------------------------------------------

Thanks.

Locked