Update the kernel of Porteus v3.1

[neko]

@Bogomips
Excuse me for my poor English.

I wanted to express that I was researching a better "kernel configuration" than my offered one.

If you use another one, I am interested it.
But if your own tuning is about NVIDIA, I can't evaluate it.
I don't have a NVIDIA.

Thanks.

[neko]

Update Kernel version.

[New tool module]
upkernel-4.2.7-noarch-1.xzm
upkernel-4.3.2-noarch-1.xzm
upnkernel-4.3.2-noarch-1.xzm

Please refer to the top article of this thread.

Thanks.

---------------------
mainline: 4.4-rc4 2015-12-06
stable: 4.3.2 2015-12-10
stable: 4.2.7 2015-12-09
longterm: 4.1.14 2015-12-09
longterm: 3.18.24 2015-10-31

[neko]

Update Kernel version.

[New tool module]
upkernel-3.18.25-noarch-1.xzm
upkernel-4.2.8-noarch-1.xzm
upkernel-4.3.3-noarch-1.xzm
upnkernel-4.3.3-noarch-1.xzm

Please refer to the top article of this thread.

Thanks.


--------------------------------------
mainline: 4.4-rc5 2015-12-14
stable: 4.3.3 2015-12-15
stable: 4.2.8[EOL] 2015-12-15
longterm: 4.1.15 2015-12-15
longterm: 3.18.25 2015-12-25

[Ed_P]

Hi.

I tried the upgrade and got this:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# activate /home/guest/Downloads/upkernel-*.xzm
Updating shared library links:  /sbin/ldconfig
/sbin/ldconfig: /usr/lib/libv4lconvert.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib/libv4l2.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib/libv4l1.so.0 is not a symbolic link

root@porteus:/home/guest# upkernel /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso
bash: upkernel: command not found

What am I doing wrong??

[Bogomips]

^ Checked the md5sum?

[neko]

@Ed_P
I followed your operation depending on Bogomips's advice.

Porteus-LXQT-v3.1-x86_64.iso from the site
http://dl.porteus.org/x86_64/current/Po ... x86_64.iso

upkernel-3.18.25-noarch-1.xzm from the site
http://www.mediafire.com/download/nlboh ... arch-1.xzm

Code: Select all

% ls -1
Porteus-LXQT-v3.1-x86_64.iso
upkernel-3.18.25-noarch-1.xzm
% md5sum *
92855e540675ba43fcf7c17607b899d2  Porteus-LXQT-v3.1-x86_64.iso
d905a2d98c97160d38efe4c14bce4d9b  upkernel-3.18.25-noarch-1.xzm
% su
# activate upkernel-3.18.25-noarch-1.xzm
# upkernel Porteus-LXQT-v3.1-x86_64.iso
# ls -1
Porteus-LXQT-v3.1-x86_64.iso
UP.Porteus-LXQT-v3.1-x86_64.iso
UP.Porteus-LXQT-v3.1-x86_64.iso.md5
upkernel-3.18.25-noarch-1.xzm

Updated ISO 'UP.Porteus-LXQT-v3.1-x86_64.iso' was gotten.

Thanks.
------------------------------

@Bogomips
Thank you for your advice.

[Ed_P]

Thanks guys.

I wasn't very clear in what I posted previously. Sorry.

Code: Select all

guest@porteus:~$ md5sum /home/guest/Downloads/upkernel*.xzm
fc742b36809568e0a8d93bcb8f812b57  /home/guest/Downloads/upkernel-4.2.8-noarch-1.xzm
guest@porteus:~$ 

I will redownload the module and try again.

[Ed_P]

Redownloaded, retried.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# md5sum /home/guest/Downloads/upkernel-*.xzm
fc742b36809568e0a8d93bcb8f812b57  /home/guest/Downloads/upkernel-4.2.8-noarch-1-B4.xzm
fc742b36809568e0a8d93bcb8f812b57  /home/guest/Downloads/upkernel-4.2.8-noarch-1.xzm
root@porteus:/home/guest# activate /home/guest/Downloads/upkernel-4.2.8-noarch-1.xzm
Updating shared library links:  /sbin/ldconfig
/sbin/ldconfig: /usr/lib/libv4lconvert.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib/libv4l2.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib/libv4l1.so.0 is not a symbolic link

root@porteus:/home/guest# ls /mnt/sda5/ISOs/Porteus-LXQT-*.iso
/mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso*  /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64.iso*
root@porteus:/home/guest# upkernel /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso
bash: upkernel: command not found
root@porteus:/home/guest# 

[Ed_P]

Retried again, this time under Porteus LXQT 3.1.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# ls    /mnt/sda5/porteus.3.0/Guest/Downloads/upkernel-*.xzm
/bin/ls: cannot access /mnt/sda5/porteus.3.0/Guest/Downloads/upkernel-*.xzm: No such file or directory
root@porteus:/home/guest# ls    /mnt/sda5/porteus3.0/Guest/Downloads/upkernel-*.xzm
/mnt/sda5/porteus3.0/Guest/Downloads/upkernel-4.2.8-noarch-1.xzm*
root@porteus:/home/guest# md5sum /mnt/sda5/porteus3.0/Guest/Downloads/upkernel-*.xzm
fc742b36809568e0a8d93bcb8f812b57  /mnt/sda5/porteus3.0/Guest/Downloads/upkernel-4.2.8-noarch-1.xzm
root@porteus:/home/guest# activate /mnt/sda5/porteus3.0/Guest/Downloads/upkernel-*.xzm
Updating shared library links:  /sbin/ldconfig
root@porteus:/home/guest# ls /mnt/sda5/ISOs/Porteus-LXQT-*.iso
/mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso*  /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64.iso*
root@porteus:/home/guest# upkernel /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso
mount: block device /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso is write-protected, mounting read-only
Setting input-charset to 'UTF-8' from locale.
3.01a16 (x86_64-unknown-linux-gnu)
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/porteus
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/porteus/rootcopy
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/porteus/optional
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/porteus/modules
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/porteus/base
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/boot
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/boot/syslinux
Excluded by match: /tmp/Porteus-LXQT-v3.1-x86_64-nu/boot/syslinux/isolinux.boot
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/boot/docs
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/EFI
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/EFI/BOOT
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/EFI/BOOT/icons
Scanning /tmp/Porteus-LXQT-v3.1-x86_64-nu/EFI/BOOT/drivers_x64
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)    15
Writing:   Joliet directory tree                   Start Block 44
Done with: Joliet directory tree                   Block(s)    14
Writing:   Directory tree cleanup                  Start Block 58
Done with: Directory tree cleanup                  Block(s)    0
Writing:   Extension record                        Start Block 58
Done with: Extension record                        Block(s)    1
Writing:   The File(s)                             Start Block 59
  5.23% done, estimate finish Sun Dec 27 00:34:57 2015
 10.48% done, estimate finish Sun Dec 27 00:34:57 2015
 15.70% done, estimate finish Sun Dec 27 00:34:57 2015
 20.94% done, estimate finish Sun Dec 27 00:34:57 2015
 26.16% done, estimate finish Sun Dec 27 00:35:00 2015
 31.40% done, estimate finish Sun Dec 27 00:35:00 2015
 36.63% done, estimate finish Sun Dec 27 00:34:59 2015
 41.87% done, estimate finish Sun Dec 27 00:34:59 2015
 47.09% done, estimate finish Sun Dec 27 00:34:59 2015
 52.33% done, estimate finish Sun Dec 27 00:34:58 2015
 57.56% done, estimate finish Sun Dec 27 00:34:58 2015
 62.79% done, estimate finish Sun Dec 27 00:34:58 2015
 68.01% done, estimate finish Sun Dec 27 00:34:58 2015
 73.25% done, estimate finish Sun Dec 27 00:34:58 2015
 78.48% done, estimate finish Sun Dec 27 00:34:58 2015
 83.72% done, estimate finish Sun Dec 27 00:34:58 2015
 88.95% done, estimate finish Sun Dec 27 00:34:58 2015
 94.19% done, estimate finish Sun Dec 27 00:34:58 2015
 99.42% done, estimate finish Sun Dec 27 00:34:58 2015
Total translation table size: 2048
Total rockridge attributes bytes: 9888
Total directory bytes: 28672
Path table size(bytes): 184
Done with: The File(s)                             Block(s)    95360
Writing:   Ending Padblock                         Start Block 95419
Done with: Ending Padblock                         Block(s)    150
Max brk space used 24000
95569 extents written (186 MB)
root@porteus:/home/guest# 

Previous attempts were run under Porteus RazorQT 3.0.1.

So now the question is:

Code: Select all

root@porteus:/home/guest# ls /mnt/sda5/ISOs/Porteus-LXQT-*.iso
/mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso*  /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64.iso*
root@porteus:/home/guest# ls /tmp
keyring-6v9iWv/  keyring-PoQIyI/  keyring-burpmp/  qtsingleapp-qlippe-2dfb-3e8=
keyring-8Y4iGd/  keyring-R0mcqX/  keyring-h45O3y/  qtsingleapp-qlippe-2dfb-3e8-lockfile
root@porteus:/home/guest# ls /mnt/sda5/ISOs/*Porteus-LXQT-*.iso
/mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64-nu.iso*  /mnt/sda5/ISOs/Porteus-LXQT-v3.1-x86_64.iso*
root@porteus:/home/guest# 

where's the new .iso file??

[Bogomips]

^ Careful reading of the instructions will reveal that

• the iso to be updated be in a directory which has free space twice the size of the iso
• Change directory to directory containing iso
• Upkernel and new iso will be found in said directory

Code: Select all

root@porteus:/home/guest# activate /home/guest/Downloads/upkernel-*.xzm

@Ed_P btw might be an idea to use tab completion. It's a mite faster and more compleat (sez i to a windoze man)

[Ed_P]

Change directory to directory containing iso

Oops. But I found the .iso, it was in the /home/guest/ directory.

[Bogomips]

Change directory to directory containing iso

Oops. But I found the .iso, it was in the /home/guest/ directory.

Wasn't sure if /home/guest had been checked. Anyway good to know.

[neko]

@Ed_P
There are 6 commands in "Update the kernel of Porteus V3.1"

'upkernel' and 'upakernel' commands are offered by the 'upkernel-3.18.NN-noarch-N.xzm' module.
'upkernel4' and 'upakernel4' commands are offered by the 'upkernel-4.2.N-noarch-N.xzm' module.
'upkernel4.3' and 'upakernel4.3' commands are offered by the 'upkernel-4.3.N-noarch-N.xzm' module.

Therefore 'upkernel-4.2.8-noarch-1.xzm' does not include an 'upkernel' command.
It includes an 'upkernel4' commnad.

If you will update the kernel of Porteus V3.1 to version 4.2.N by the command that is included in 'upkernel-4.2.N-noarch-N.xzm' module,
you should execute the 'upkernel4' command.

Thanks.

[Ed_P]

you should execute the 'upkernel4' command.

Where did the upkernel command come from?? What is it updating??? It is creating an UP. .iso file.

I am using the 4.3 version so let me rerun the update upkernel4.3 and see what I get this time.

Thanks neko

[Ed_P]

upkernel4.3 did work and updated the kernel to 4.3. But booting the UP LXQT system on my netbook I lost all network connections. And on the new laptop I didn't get that far.

Thanks for your help neko.