PorteuX 2.1 bug reports

[porteux]

Is it possible to boot from a clean USB stick in Always Fresh? Maybe your infrastructure is introducing some issues.

[Ed_P]

Code: Select all

~#  cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/PorteuX/porteux-v2.1-current-cinnamon-6.4.10-x86_64.iso volume=33 reboot=cold extramod=/porteux/Modules;/porteux/modsavedat kmap=us norootcopy noload=mychanges;My

Added in 44 minutes 30 seconds:

Is it possible to boot from a clean USB stick in Always Fresh? Maybe your infrastructure is introducing some issues.

Same situation in AF mode. You think your ISO is the problem? It's always worked before.

This a contributing factor?

Unfortunately, Microsoft has changed Github's API

Or this?

The default NTFS driver has been changed from `ntfs-3g` to `ntfs3` (kernel native).

[porteux]

Is it possible to boot from a clean USB stick in Always Fresh? Maybe your infrastructure is introducing some issues.

Same situation in AF mode. You think your ISO is the problem? It's always worked before.

Not just AF, but using a clean USB stick with just PorteuX, with no grub, nothing; the normal way as described here: https://github.com/porteux/porteux/blob ... nstall.txt

[Ed_P]

USB EFI boot same situation.

[porteux]

Have you tried to plug an external unit (not necessarily the one with PorteuX) formatted in NTFS and check if it's writable?

[Ed_P]

Have you tried to plug an external unit (not necessarily the one with PorteuX) formatted in NTFS and check if it's writable?

No. My USB drive are either FAT32 or exFAT formatted, no hard drive formats.

I have tried booting the USB drive's porteux system live verses via EFI and got this when trying to add firefox support modules.


And I can assure you there is no 000-kernel-6.15 module in my Modules folder.

My grub2 live boot menu:

Code: Select all

if [ -e (hd0,msdos1)/porteux/base/000-kernel-6.15.xzm ]; then
menuentry " PorteuX 2.1 USB - AF'" --class slackware   --class user-icon-usb  {

     set bootparms="volume=33 reboot=cold "   # extramod=/Modules noload=50;pipe;wm"  

     set bootdrv=$root
     search -f /boot/syslinux/vmlinuz --set=root
     if [ $root != $bootdrv ]; then
        linux  /boot/syslinux/vmlinuz $bootparms
        initrd /boot/syslinux/initrd.zst
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }
fi

[porteux]

@Ed_P, this is not a default boot.

Please, try without any cheatcode, without grub, without saving sessions. Just copy the ISO content to a USB stick formatted in FAT32 and boot in Always Fresh. Let's do baby steps

[Ed_P]

Grub is how I boot my notebook. Windows, porteux, porteus, ISOs, USBs, EFI, direct.

Yes, with the USB direct boot I used a couple of simple boot parms, which should have 0 impact on NTFS. With the USB EFI boot no boot parms were used, straight chainloader to the USB's EFI module.

Code: Select all

if [ -e (hd0,msdos1)/porteux/base/000-kernel-6.15.xzm ]; then
menuentry " PorteuX 2.1 USB - EFI" --class slackware   --class user-icon-usb  {

     set bootmgr=/EFI/boot/bootx64.efi          #grubx64.efi    # bootx64.efi

     set bootdrv=$root
     search -f $bootmgr --set=root
     echo USB: $root
     sleep -v -i 4
     if [ $root != $bootdrv ]; then
        chainloader $bootmgr
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }
fi

[rych]

from=/ISOs/PorteuX/porteux-v2.1-current-cinnamon-6.4.10-x86_64.iso

Thanks for the GParted screenshot. Since it doesn't show anything unusual (right click on partition for more Information or flags?), could you run for example

Code: Select all

mount | grep ntfs

I just want to understand: is it or is it not mounted read-only, and why.

I have both porteuS/X installed on the system NVMe SSD (like you?) and I can always write on the common NTFS partition, regardless which of those two I boot. (I haven't booted into Windows for months though.)

[Ed_P]

BTW & FWIW Those 2 USB grub2 menus boot porteux 2.0 fine with no boot errors, even with the 2 boot parms in the direct menu, and no NTFS read problems on either boot.

I have both porteuS/X installed on the system NVMe SSD (like you?) and I can always write on the common NTFS partition, regardless which of those two I boot.

porteuX 2.1? As noted above USB 2.0 works fine with NTFS for me.

Added in 19 minutes 28 seconds:

could you run for example

Code: Select all

mount | grep ntfs

I just want to understand: is it or is it not mounted read-only, and why.

2.1 Cinnamon AF EFI boot.

[rych]

porteuX 2.1

Yes.

1. Could be that ntfs3 doesn't like something. Maybe unmount and mount from CLI to see error messages?

2. Also, interesting to see ownership of files on that partition: is it root or guest?

( 3. Also, Windows encrypted or compressed disks might not be fully accessible in Linux.)

[rych]

I've got a little bug of my own. After waking up from screen-timeout, LXDE doesn't render its GUI, and the top command shows lxpanel using 100% CPU.

There must have been reasons I chose porteus's OpenBox over LXDE But for PorteuX I'm looking for my next DE. I just hope I won't end up giving in to KDE

[Ed_P]

2. Also, interesting to see ownership of files on that partition: is it root or guest?

( 3. Also, Windows encrypted or compressed disks might not be fully accessible in Linux.)

No encryption or compression involved, ever.

Code: Select all

guest@porteux:~$ echo PorteuX 2.1 Cinnamon x64_86 AF mode
PorteuX 2.1 Cinnamon x64_86 AF mode
guest@porteux:~$ ls -lon --color=never /mnt/nvme0n1p4
total 36
drwxr-xr-x 1 0    0 May 24 06:59 $RECYCLE.BIN/
drwxr-xr-x 1 0 4096 May 25 06:11 acer/
drwxr-xr-x 1 0 4096 Apr 25 06:03 Brother/
-rwxr-xr-x 1 0  411 Jun 21  2024 EFIdirs.txt*
drwxr-xr-x 1 0    0 Apr 25 06:03 grub2/
drwxr-xr-x 1 0 4096 Apr 25 06:03 HomeMovies/
drwxr-xr-x 1 0 4096 Jun  4 06:01 ISOs/
drwxr-xr-x 1 0    0 Apr 25 05:59 nemesis/
drwxr-xr-x 1 0 4096 May 26 14:58 porteus5.0/
drwxr-xr-x 1 0 4096 May 17 00:34 porteus5.1/
drwxr-xr-x 1 0 4096 Jun  6 08:51 porteux/
drwxr-xr-x 1 0    0 Apr 25 06:00 Recovery/
drwxr-xr-x 1 0 4096 Jun  7 06:24 System\ Volume\ Information/
drwxr-xr-x 1 0    0 Jun  7  2025 Temp/
drwxr-xr-x 1 0 4096 Apr 25 06:00 Users/
-rwxr-xr-x 1 0  308 Jun 13  2024 wsl.txt*
guest@porteux:~$