PorteuX data not found - Resolved

[Ed_P]

ISOs boot on NTFS drives, even ones with .zst files, just not ISO's with .zst files on this stupid Acer system's harddrive. grub2 can read the ISO's vmlinuz file and porteux starts, so I don't think ISO fragmentation is the problem. And since the same grub2 can boot the same ISO on my Dell I don't think it's a grub2 problem.

It would be nice to know what porteux's vmlinuz can see when it can't see the /porteux folder. And any error messages it encountered looking for it.

[Ed_P]

Ok, still getting this:

on all attempts to boot porteux cinnamons 1.8, 1.9 and 2.0 on the Acer notebook. What linux/porteux commands can I run to help clarify the problem?

Added in 20 hours 11 minutes 32 seconds:
This grub2 menu:

Code: Select all

menuentry " PorteuX 1.8 ISO - Cinnamon AF"  --class slackware   --class user-icon-porteux  {
#    https://github.com/porteux/porteux/releases & https://github.com/porteux/porteux/blob/main/boot/boot/docs/cheatcodes.txt

     set linux_folder=/porteux
#     set iso="/My_Files/ISOs/PorteuX/porteux-v1.8-current-cinnamon-6.4.2-x86_64.iso"
     set iso="/ISOs/PorteuX/porteux-v1.8-current-cinnamon-6.4.2-x86_64.iso"
#     set iso="/ISOs/PorteuX/porteux-v1.9-current-cinnamon-6.4.6-x86_64.iso"
#     set iso="/ISOs/PorteuX/porteux-v2.0-current-cinnamon-6.4.9-x86_64.iso"
     
     set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules;$linux_folder/modsavedat \
       kmap=us norootcopy noload=-test;my;My"   # noload mate if mycinnamon mod in play

     search -f $iso --set=root
     echo root:$root

     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz      from=$iso # $bootparms
     initrd (loop)/boot/syslinux/initrd.zst
     
     echo "ls" 
     ls
     echo "ls (proc)"
     ls (proc)
     echo "ls (loop)"
     ls (loop)
     echo "ls (loop,msdos1)"
     ls (loop,msdos1)
     echo "ls (hd0,gpt4)"
     ls (hd0,gpt4)
     echo "ls (hd0,gpt4)/ISOs/PorteuX/"
     ls (hd0,gpt4)/ISOs/PorteuX/
     echo iso:iso=$iso
     echo
     echo Checks to see if the initrd command was successful, then press Enter
     read
     }

produces this when booting:

and yields this:


Similar results with porteux 1.9 and 2.0 ISOs which all work on my Dell Windows 11 system.

What is wrong with my Acer system?????

Added in 15 hours 51 minutes 49 seconds:
Same problem with the new porteux 2.1 ISO.

Any porteux commands I can run that would help explain the problem?


Added in 9 hours 14 minutes 15 seconds:
With porteux 2.1 ISO's boot problem dmesg shows this:



ls /var/log shows nothing.