Porteus 4.0 and a NVMe drive

Technical issues/questions of an intermediate or advanced nature.
User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 4.0 and a NVMe drive

Post#1 by Ed_P » 22 Mar 2022, 20:22

What's needed to boot the 4.0 ISO on a NVMe SSD drive on a new Dell notebook. The ISO boots fine on the old SATA SSD drive on my old Dell. The problem is it doesn't find the porteus .cfg file when booting. Using the same approach Porteus 5.0 ISO boots fine.

My grub2 menus.

Code: Select all

menuentry " Porteus 5.0rc3 ISO - AF+"  --class slackware   --class icon-porteus  {

     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules;$linux_folder/rc3Modules noload=kde;jinn;lxqt;xfce;lxde;mate;open;mychanges;menu3" 

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.xz
     }

Code: Select all

menuentry " Porteus 4.0 ISO - AF+" --class slackware   --class icon-porteus  {

     set boot_parms="volume=33 reboot=cold $extramods$linux_folder/Modules noload=cinnamon"

     search -f $iso --set=root
     loopback loop $iso
     linux  (loop)/boot/syslinux/vmlinuz from=$iso $boot_parms
     initrd (loop)/boot/syslinux/initrd.xz
     }
Do I need a different initrd.xz or a different vmlinuz?

It would be nice to boot Porteus 4.0 without having to pull out my old Dell. :)
Ed

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus 4.0 and a NVMe drive

Post#2 by babam » 22 Mar 2022, 22:22

Use a kernel that supports booting on nvme
Sorry, my English is bad.

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus 4.0 and a NVMe drive

Post#3 by beny » 22 Mar 2022, 22:35

hi Ed_P this is ok? from=$iso $boot_parms the porteus4 boot line and this is the porteus5 boot line from=$iso $bootparms maybe is not

raja
Shogun
Shogun
Posts: 434
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and Porteus-Artix-64
Location: Chennai,India

Porteus 4.0 and a NVMe drive

Post#4 by raja » 23 Mar 2022, 08:49

Ed_P,

Rename vmlinuz and initrd.xz in porteus-4.0 ISO, and copy same from porteus-5.0-rc3 ISO. copy *.cfg file also to porteus folder and try. Most probably you will succeed.

Assuming both ISOs remain in different partitions & in root.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 4.0 and a NVMe drive

Post#5 by Ed_P » 23 Mar 2022, 15:03

Thank you guys. :beer:
babam wrote:
22 Mar 2022, 22:22
Use a kernel that supports booting on nvme
Actually I've tried 2 that I use with Porteus 5.0. Neither works.

Code: Select all

Porteus-CINNAMON-v4.0-x86_64-5.16.11.iso*
Porteus-CINNAMON-v4.0-x86_64-5.16.15.iso*
beny wrote:
22 Mar 2022, 22:35
hi Ed_P this is ok? from=$iso $boot_parms the porteus4 boot line and this is the porteus5 boot line from=$iso $bootparms maybe is not
Yea, they're ok, just user created names given to a variable.
raja wrote:
23 Mar 2022, 08:49
Rename vmlinuz and initrd.xz in porteus-4.0 ISO, and copy same from porteus-5.0-rc3 ISO. copy *.cfg file also to porteus folder and try.
Oh raja I think you've nailed the problem. The nucleus files that I copied to the 4.0 ISO are created on my 5.0 system and from the 5.0 ISO and the *.cfg files are most likely named porteus-v5.0*. :o Thank you raja. :beer:
Ed

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus 4.0 and a NVMe drive

Post#6 by babam » 23 Mar 2022, 15:41

Ed_P wrote:
23 Mar 2022, 15:03
Thank you guys. :beer:
babam wrote:
22 Mar 2022, 22:22
Use a kernel that supports booting on nvme
Actually I've tried 2 that I use with Porteus 5.0. Neither works.

Code: Select all

Porteus-CINNAMON-v4.0-x86_64-5.16.11.iso*
Porteus-CINNAMON-v4.0-x86_64-5.16.15.iso*
Use a kernel and initrd that supports booting on Nvme
Sorry, my English is bad.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 4.0 and a NVMe drive

Post#7 by Ed_P » 23 Mar 2022, 21:07

Well, I tried renaming the /porteus/porteus-v5.0*.cfg file and that didn't help. :o :wall:
I should have tried tome's cfgfile= cheatcode idea.
babam wrote:
23 Mar 2022, 15:41
Use a kernel and initrd that supports booting on Nvme
Ok. Are you referring to the one from my Porteus 5.0 ISO? The kernel I'm using with Porteus 5.0 is created by fulalas's Simple Kernel Script and it only creates 000-nucleus.xzm, vmlinuz and 06-crippled-sources*.xzm files. No initrd file.
Ed

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus 4.0 and a NVMe drive

Post#8 by beny » 23 Mar 2022, 21:51

hi Ed_P we have to know the steps for the boot of the iso, the file system that hosting the iso maybe the initrd do not have the nvme driver inside,but i can go wrong on this....

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 4.0 and a NVMe drive

Post#9 by Ed_P » 23 Mar 2022, 22:44

The ISO files are on a Windows NTFS partition along with many Modules and save.dat files used by the Porteus systems. This arrangement has worked for years on a Acer notebook and an older Dell notebook. The ISOs are booted when I boot the computer and get a grub2 menu system that allows me to select which and how to boot the ISOs.

The same configurations and layouts were copied 3 months ago to a new Dell notebook I received and that's when the problems started. The new Dell has a HVMe harddrive. Actually it's an SSD drive, and my old Dell had a SSD drive also and it is a SATA system. And both Dell's have Windows 10 systems driving them.

When booting the ISOs all booting starts within the ISO via the grub2 loopback linux (loop) and initrd (loop) functions.

Added in 4 hours 39 minutes 20 seconds:
Neither cfgfile=porteus-v5.0-x86_64.cfg nor cfgfile=porteus-v4.0-x86_64.cfg worked with Porteus-CINNAMON-v4.0-x86_64-5.16.15.iso. :(
Ed

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus 4.0 and a NVMe drive

Post#10 by babam » 24 Mar 2022, 06:57

@Ed_P,

Code: Select all

zgrep CONFIG_VMD /proc/config.gz
Sorry, my English is bad.

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus 4.0 and a NVMe drive

Post#11 by beny » 24 Mar 2022, 12:49

hi Ed_P take the porteus 5 initrd.xz and use it to porteus 4 mount the iso and change the inirtd.xz from porteus 5 to porteus 4 the initrd seem that have a different way to manage ntfs partition,btw i am not shure for this but that worth a try,don't change the vmlinuz that is kernel related only the initrd.xz

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 4.0 and a NVMe drive

Post#12 by Ed_P » 24 Mar 2022, 15:52

babam wrote:
24 Mar 2022, 06:57

Code: Select all

zgrep CONFIG_VMD /proc/config.gz

Code: Select all

guest@porteus:~$ zgrep CONFIG_VMD /proc/config.gz
gzip: /proc/config.gz: No such file or directory
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# zgrep CONFIG_VMD /proc/config.gz
gzip: /proc/config.gz: No such file or directory
root@porteus:/home/guest# 
beny wrote:
24 Mar 2022, 12:49
take the porteus 5 initrd.xz and use it to porteus 4 mount the iso
It's quite possible the porteus 4 init.xz is the same one.

Code: Select all

~#  uname -a
Linux porteus.example.net 5.16.15-porteus #1 SMP PREEMPT Thu Mar 17 01:46:17 EDT 2022 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux

~#  cat /etc/porteus/*
001-core.xzm:202-----
002-xorg.xzm:202-----
002-xtra.xzm:202-----
003-cinnamon.xzm:202-----
initrd.xz:20201102
The one in 5.0 is not new. I'll boot the old Dell and bring up 4.0 and see what it's using.

Added in 40 minutes 56 seconds:
Aw, my Porteus 4.0 system.

Code: Select all

~#  uname -a
Linux porteus 4.16.3-porteus #1 SMP PREEMPT Sat Apr 21 12:42:52 Local time zone must be set-- x86_64 Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz GenuineIntel GNU/Linux

~#  cat /etc/porteus/*
001-core.xzm:20180422
002-xorg.xzm:20180422
003-cinnamon.xzm:20180702
initrd.xz:20180311
Such old, old dates.

But the initrd.xz does proceed the one in 5.0. :happy62:
Ed

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus 4.0 and a NVMe drive

Post#13 by babam » 24 Mar 2022, 16:54

Ed_P wrote:
24 Mar 2022, 16:33

Code: Select all

guest@porteus:~$ zgrep CONFIG_VMD /proc/config.gz
gzip: /proc/config.gz: No such file or directory
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# zgrep CONFIG_VMD /proc/config.gz
gzip: /proc/config.gz: No such file or directory
root@porteus:/home/guest# 

Code: Select all

su
modprobe configs
zgrep CONFIG_VMD /proc/config.gz
Sorry, my English is bad.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 4.0 and a NVMe drive

Post#14 by Ed_P » 24 Mar 2022, 20:38

Porteus 5.0 on the new Dell.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# modprobe configs
root@porteus:/home/guest# zgrep CONFIG_VMD /proc/config.gz
CONFIG_VMD=m
root@porteus:/home/guest# 
Ed

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus 4.0 and a NVMe drive

Post#15 by babam » 24 Mar 2022, 21:06

If Porteus 5.0 can boot on nvme then you can use initrd.xz, vmlinuz and 000-kernel.xzm from 5.0 to 4.0
Sorry, my English is bad.

Post Reply