Page 1 of 1
Restarting with PorteuX. Problems with 0.7
Posted: 06 Nov 2023, 04:45
by Ed_P
I lost my Porteux system a couple of months ago so I'm starting over, basically from scratch.
I'm booting the porteux-v0.7-xfce-4.18-stable-x86_64.iso and find that bash scripts, that run in Porteus, don't run when I click on them. What do I need to do to make them runable?
Added in 47 minutes 45 seconds:
And Porteux 0.7 isn't picking up my extramod= cheatcode.
Code: Select all
menuentry " PorteuX " --class slackware --class icon-porteus {
set linux_folder=/porteusx
set iso=/ISOs/porteux/porteux-v0.7-xfce-4.18-stable-x86_64.iso
set bootdrv=$root
search -f $iso --set=root
set porteus_parms="extramod=$linux_folder/Modules;$linux_folder/modsavedat noload=save.dat volume=33 reboot=cold"
loopback loop $iso
linux (loop)/boot/syslinux/vmlinuz from=$iso $porteus_parms
initrd (loop)/boot/syslinux/initrd.zst
echo "Booting PorteuX"
}
Added in 16 hours 36 minutes 29 seconds:
Same problems with porteux-v0.7-xfce-4.18-current-x86_64.iso.

Restarting with PorteuX. Problems with 0.7
Posted: 06 Nov 2023, 23:18
by beny
hi Ed_P, this is the extramod on cheatcode:where is the path of yours directory or am i wrong
extramod=/path/folder_with_modules
extramod=/path/folder_with_modules;/path2/folder_with_modules
... This cheatcode lets you load modules from one or more external
folders that are located outside of the /porteux directory.
Multiple folders can be specified, with full paths separated by
a semicolon without any spaces.
Examples:
'extramod=/mnt/sdb3/porteux-modules'
'extramod=/mnt/sdb3/porteux-modules;/mnt/sdc4/inkscape_modules'
Restarting with PorteuX. Problems with 0.7
Posted: 07 Nov 2023, 03:59
by Ed_P
Thank you
beny, I am aware of the syntax.
Code: Select all
guest@porteux:~$ cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/porteux/porteux-v0.7-xfce-4.18-current-x86_64.iso extramod=/porteusx/Modules;/porteusx/modsavedat noload=save.dat volume=33 reboot=cold
guest@porteux:~$
And since the /porteux folder is on the same drive as the ISOs folder root is pointing to the folders referenced.
Code: Select all
guest@porteux:~$ ls -on /mnt/nvme0n1p7
total 76
drwxrwxrwx 1 1000 0 Oct 7 17:47 $RECYCLE.BIN/
drwxrwxrwx 1 1000 4096 Jan 24 2018 Dell/
drwxrwxrwx 1 1000 0 Jan 26 2018 Dell-Recovery/
drwxrwxrwx 1 1000 0 Mar 12 2018 efi/
drwxrwxrwx 1 1000 4096 Apr 28 2018 emoticons/
drwxrwxrwx 1 1000 0 Nov 28 2022 grub2/
drwxrwxrwx 1 1000 32768 Nov 5 06:03 ISOs/ <<<<<<<<<<<<<<<<<<<
drwxrwxrwx 1 1000 4096 Jan 11 2018 porteus3.0/
drwxrwxrwx 1 1000 4096 Jan 25 2020 porteus3.2/
drwxrwxrwx 1 1000 8192 Mar 25 2022 porteus4.0/
drwxrwxrwx 1 1000 8192 Oct 26 05:31 porteus5.0/
drwxrwxrwx 1 1000 0 Nov 6 02:55 porteux/ <<<<<<<<<<<<<<<<<<<
drwxrwxrwx 1 1000 0 Nov 3 04:07 Recovery/
-rwxrwxrwx 1 1000 1019 Nov 6 18:07 syntax.report.txt*
drwxrwxrwx 1 1000 4096 Nov 4 22:48 System\ Volume\ Information/
drwxrwxrwx 1 1000 4096 Oct 15 18:20 Users/
guest@porteux:~$
Code: Select all
guest@porteux:~$ ls -on /mnt/nvme0n1p7/porteux
total 0
drwxrwxrwx 1 1000 0 Nov 6 19:57 Guest/
drwxrwxrwx 1 1000 0 Nov 6 02:54 modsavedat/ <<<<<<<<<<<<<<
drwxrwxrwx 1 1000 0 Nov 6 05:21 Modules/ <<<<<<<<<<<<<<
guest@porteux:~$
Restarting with PorteuX. Problems with 0.7
Posted: 07 Nov 2023, 16:07
by beny
ok, but where is porteusx directory? If it is the path of extramod
Restarting with PorteuX. Problems with 0.7
Posted: 07 Nov 2023, 19:18
by Ed_P
Hi
beny. As seen in the 2nd code box in my prior posting above, the extramod directories are in the porteux directory.
I tried this last night with PorteuX 0.6 ISOs and same problem. I think when I lost my files I had only tested up to PorteuX 0.5 so I guess I will try it next, because I used to be able to boot Porteux with extramods. The grub2 approach I'm using is the same one I've used for years with Porteus and other Linux ISOs and since the ISOs and support directories are all on the same drive it works.
Added in 53 minutes 44 seconds:
Well this is getting stranger and stranger. I was able to take a picture of the boot screen with my phone. And in the picture porteux is seen stating:
Code: Select all
loading additional modules in /porteux/Modules
loading additional modules in /porteux/modsavedat
And in /porteux/Modules is:
Code: Select all
guest@porteus:/mnt/nvme0n1p7/porteux$ ls -on Modules
total 105048
-rwxrwxrwx 1 1000 33947648 Nov 5 00:31 003-cinnamon-5.8.0-current-20230630.xzm*
-rwxrwxrwx 1 1000 73023488 Oct 31 16:05 firefox-119.0-x86_64-en-US.xzm*
-rwxrwxrwx 1 1000 598016 Nov 5 00:29 keepassx-20230529-x86_64-1.xzm*
guest@porteus:/mnt/nvme0n1p7/porteux$
So why aren't they being loaded?

Because /mnt/nvme0n1p7/porteux is on a NTFS drive? Because porteux doesn't work with .xzm modules?

Restarting with PorteuX. Problems with 0.7
Posted: 07 Nov 2023, 21:22
by beny
hi Ed_P the slpkg with all deps are loaded without trouble in porteux, i don't have a ntfs system the ext4 path work
LABEL text
MENU LABEL Text Mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.zst
APPEND changes=/porteux 3 extramod=/mnt/sda1/tmp/vcpkg
Restarting with PorteuX. Problems with 0.7
Posted: 08 Nov 2023, 06:29
by Ed_P
Same situation with porteux-v0.5-xfce-4.18-current-x86_64.iso which I'm sure worked before I lost all my files.
New problem: with porteux running I closed the lid on my notebook and when I opened it a few minutes later I got:
Code: Select all
None of the screen lock tools ran successfully, the screen will not be locked.
Restarting with PorteuX. Problems with 0.7
Posted: 08 Nov 2023, 09:49
by Rapha_
Ed_P wrote: ↑07 Nov 2023, 03:59
guest@porteux:~$ cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz
from=/ISOs/porteux/porteux-v0.7-xfce-4.18-current-x86_64.iso extramod=
/porteusx/Modules;
/porteusx/modsavedat noload=save.dat volume=33 reboot=cold
guest@porteux:~$
from=your.iso No, in this way it search in the path inside the iso !
In extramod it should be
with full path like this :
extramod=
/mnt/nvme0n1p7/porteusx/Modules;
/mnt/nvme0n1p7/porteusx/modsavedat
Restarting with PorteuX. Problems with 0.7
Posted: 08 Nov 2023, 16:43
by Ed_P
Thanks
Rapha. This is how I boot Porteus 5.01:
Code: Select all
guest@porteus:~$ cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus-CINNAMON-v5.01-x86_64.iso volume=33 reboot=cold extramod=/porteus5.0/Modules noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm
guest@porteus:~$
(and 5.0rc3 and 4.0 and 3.2 and 3.0 and ..... which is why this problem is so strange for me.)
BTW The value of root for /mnt/nvme0nip7 is hd0,gpt7.
I am thinking of trying your, and
beny's, suggestion, later today.
Added in 4 hours 29 minutes 36 seconds:
Here's what I got using extramod=/mnt/nvme0n1p7/porteusx/Modules;/mnt/nvme0n1p7/porteusx/modsavedat.

Restarting with PorteuX. Problems with 0.7
Posted: 08 Nov 2023, 22:45
by Rapha_
Ed_P wrote: ↑08 Nov 2023, 21:13
Thanks
Rapha. This is how I boot Porteus 5.01:
Code: Select all
guest@porteus:~$ cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus-CINNAMON-v5.01-x86_64.iso volume=33 reboot=cold extramod=/porteus5.0/Modules noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm
guest@porteus:~$
I don't see
initrd 
Restarting with PorteuX. Problems with 0.7
Posted: 09 Nov 2023, 01:09
by Ed_P
Do you see it here?
Ed_P wrote: ↑06 Nov 2023, 22:09
Code: Select all
menuentry " PorteuX " --class slackware --class icon-porteus {
set linux_folder=/porteusx
set iso=/ISOs/porteux/porteux-v0.7-xfce-4.18-stable-x86_64.iso
set bootdrv=$root
search -f $iso --set=root
set porteus_parms="extramod=$linux_folder/Modules;$linux_folder/modsavedat noload=save.dat volume=33 reboot=cold"
loopback loop $iso
linux (loop)/boot/syslinux/vmlinuz from=$iso $porteus_parms
initrd (loop)/boot/syslinux/initrd.zst
echo "Booting PorteuX"
}
What does your cat /proc/cmdline look like?
Added in 5 hours 5 minutes 29 seconds:
Progress
I found an old grub2 PorteuX menu on a USB stick.
Code: Select all
menuentry " PorteuX 0.5 ISO - Cinnamon" --class slackware --class icon-porteux {
set linux_folder=/porteux
set iso="/ISOs/porteux/porteux-v0.5-xfce-4.18-stable-x86_64.iso"
set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules \
kmap=us noload=mate;lxqt;xfce;-test norootcopy" # cinn"
search -f $iso --set=root
loopback loop $iso
linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms
initrd (loop)/boot/syslinux/initrd.zst
}
And it reads the extramod=$linux_folder/Modules folder.
Unfortunately, it doesn't boot.
Code: Select all
porteux login: /usr/sbin/lxdm-binary: /lib64/libc.so.6: version 'GLIBC_2.34' not found (required by /usr/sbin/lxdm-binary)
Followed by a bunch of 'not found' msgs which end with INIT: Id "x1" respawning too fast: disabled for 5 minutes
And at the end of 5 minutes the errors repeat.
But this is using Porteux 0.5.

Next to try this menu with Porteux 0.6 and 0.7.
Added in 25 minutes 15 seconds:
Same problem with PorteuX 0.6 and 0.7.

Restarting with PorteuX. Problems with 0.7
Posted: 09 Nov 2023, 09:40
by porteux
@Ed_P, please don't mix stable and current modules.
Restarting with PorteuX. Problems with 0.7
Posted: 09 Nov 2023, 14:50
by Ed_P
porteux wrote: ↑09 Nov 2023, 09:40
@Ed_P, please don't mix stable and current modules.
Code: Select all
guest@porteux:~$ cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/PorteuX/porteux-v0.6-xfce-4.18-current-x86_64.iso volume=33 reboot=cold extramod=/porteux/Modules;/porteux/modsavedat kmap=us noload=mate;lxqt;xfce;-test norootcopy
guest@porteux:~$ ls -l /mnt/live/memory/images
total 0
drwxr-xr-x 5 root root 61 Sep 4 12:40 000-kernel-6.5.1.xzm/
drwxr-xr-x 21 root root 317 Sep 9 09:20 001-core-current-20230906.xzm/
drwxr-xr-x 11 root root 154 Sep 6 19:16 002-xorg-current-20230906.xzm/
drwxr-xr-x 5 root root 60 Feb 3 2023 002-xtra-current-20230906.xzm/
drwxr-xr-x 10 root root 117 Jul 1 21:16 003-cinnamon-5.8.0-current-20230630.xzm/
drwxr-xr-x 4 root root 37 Oct 31 20:05 firefox-119.0-x86_64-en-US.xzm/
drwxr-xr-x 3 root root 26 May 28 22:48 keepassx-20230529-x86_64-1.xzm/
guest@porteux:~$

Thank you.
I did not pick up on the 003 module's release in it's name.
Now to test 0.7. Thank you
porteux.
Added in 20 minutes 47 seconds:
As always, the most difficult computer problems have the simplest solutions.
Added in 2 hours 15 minutes 55 seconds:
A new problem.
Code: Select all
#!/bin/sh
# https://forum.porteus.org/viewtopic.php?p=94878#p94878
if [ `whoami` != "root" ]; then
echo -e "Enter root's password\033[1;31m"
su -c "sh $0 $1"
exit
fi
echo -e "\033[0m"; echo -en "\033]0;Make a Mod\a"
if [ -d /tmp/mod/ ]; then
rm -rf /tmp/mod
fi
mkdir -p /tmp/mod
xzm2dir /mnt/nvme0n1p7/porteux/Modules/003-* -o=/tmp/mod
#xzm2dir /mnt/live/memory/images/003-* -o=/tmp/mod
#set -x
# https://forum.porteus.org/viewtopic.php?p=94844#p94844
# all settings in Cinnamon are stored in ~/.config/dconf/user
cp -a -p --parents /home/guest/.config/dconf/* /tmp/mod/
# https://forum.porteus.org/viewtopic.php?p=94892#p94892 - wallpaper
cp -a -p --parents /home/guest/Pictures/pxfuel.jpg /tmp/mod/
dir2xzm /tmp/mod -o=/tmp/mycinnamon.xzm && rm -rf /tmp/mod
echo
echo "COPY the .xzm file to the folder you boot your modules from."
ls -on /tmp
sleep 20
exit
A simply script to save the change to the DE's taskbar location and it's wallpaper as a user module. But when executed produces:
Code: Select all
guest@porteux:~$ ./MyCinnamon.sh
bash: ./MyCinnamon.sh: cannot execute: required file not found

What simple thing am I missing now???

A couple of other bash scripts run fine.
Added in 5 hours 45 minutes 38 seconds:
dos2unix fixed the problem. Apparently I had made a change while in Windows.
Added in 1 hour 55 minutes 28 seconds:
Finally able to move on to other PorteuX 0.7 pproblems.
