PorteuX - The Next Experience. It's inspired by Slax and Porteus but with heaps of improvements
-
porteux
- Shogun

- Posts: 271
- Joined: 12 Mar 2023, 22:10
- Distribution: PorteuX
Post#1
by porteux » 22 May 2023, 12:39
- fixed a bug where in some cases the cheatcode 'from' was not working properly
- turned on low battery alert in LXQt
- changed vm.max_map_count from 65530 (default) to 16777216. This fixes issues in games with higher memory map limit, such as DayZ, Hogwarts Legacy, Counter Strike 2, etc
- GNOME is set to use wayland by default. Limitations: PorteuX keyboard application and cheatcode won't work; if nvidia proprietary driver is loaded X11 will run instead of wayland
- fixed a bug where Xfce 4.16+ was not always updating the application menu when a module is activated/deactivated
- dropped qpdfview in favor of atril for better PDF compatibility. LXQt is still missing a better Qt PDF reader
- in GNOME added adwaita backgrounds (light and dark styles)
- changed LXDM (login manager) style
- dropped Xfce 4.16 ISOs (it can still be built from source)
- GNOME updated to 44.1 (current only)
- KDE updated to 5.27.5 (current only)
- some critical packages have been updated, like mesa 23.1.0 (current only) and sysvinit (current only)
https://github.com/porteux/porteux/releases/tag/v0.4
porteux
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#2
by Ed_P » 22 May 2023, 13:35
No new 009 module?
Working so far.
Code: Select all
~# uname -a
Linux porteux.example.net 6.3.3-porteux #1 SMP PREEMPT_DYNAMIC Mon May 22 17:35:46 NZST 2023 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
~# cat /etc/porteux/*
001-core.xzm:20230520
002-xorg.xzm:20230520
002-xtra.xzm:20230520
initrd.zst:20230426
~# ls -l /mnt/live/memory/images
000-kernel-6.3.3.xzm : May 22 05:57
001-core-stable-20230520.xzm : May 20 01:21
002-xorg-stable-20230520.xzm : May 20 01:35
002-xtra-stable-20230520.xzm : Feb 3 09:59
003-cinnamon.xzm : Sep 25 2022
009-porteus5-compatibility-stable.xzm : Jan 23 22:14
changes-2023-05-17.xzm : May 17 17:11
firefox-latest-111.0.1-x86_64-1.xzm : Mar 23 01:01
mynemobkmks.xzm : May 17 19:17
printing-porteux-stable-x86_64.xzm : Mar 17 13:48
~# cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/PorteuX/porteux-v0.4-lxqt-1.3.0-stable-x86_64.iso volume=33 reboot=cold extramod=/porteux0.4/Modules kmap=us noload=mate;lxqt
ISO: /ISOs/PorteuX/porteux-v0.4-lxqt-1.3.0-stable-x86_64.iso
Ed_P
-
Kulle
- Warlord

- Posts: 704
- Joined: 28 Jan 2017, 10:39
- Distribution: v4.0 64bit Xfce
- Location: Berlin
Post#3
by Kulle » 22 May 2023, 19:34
dropped Xfce 4.16 ISOs
Why?
4.16 is compatible with Porteus 5.0
And the de-xfce_locales.xzm module from Porteus 5 also works in PorteuX ! (essentially)
Can I also use module 003-xfce-4.16-stable-20230416.xzm in PorteuX 0.4 ??
Kulle
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#4
by Ed_P » 22 May 2023, 20:31
Kulle wrote: ↑22 May 2023, 19:34
Can I also use module 003-xfce-4.16-stable-20230416.xzm in PorteuX 0.4 ??
Should work if you use the 009-porteus5-compatibility-stable.xzm module.
Ed_P
-
porteux
- Shogun

- Posts: 271
- Joined: 12 Mar 2023, 22:10
- Distribution: PorteuX
Post#5
by porteux » 23 May 2023, 02:48
@Kulle, I added Xfce 4.16 modules (just the modules!) for both stable and current in the release page. But answering your question: you probably wouldn't find any problem using a desktop environment from 0.3 in 0.4 as long as you're using the stable version.
@Ed_P, thanks for the feedback!
porteux
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#6
by Ed_P » 23 May 2023, 15:54
For Ventoy users this grub2 menu supports my ISO booting:
Code: Select all
menuentry " PorteuX 0.4 ISO - Cinnamon" --class slackware --class icon-porteux2 {
set iso="/ISOs/PorteuX/porteux-v0.4-lxqt-1.3.0-stable-x86_64.iso"
set bootparms="volume=33 reboot=cold extramod=/porteux0.4/Modules \
kmap=us noload=mate;lxqt" # cinn"
search -f $iso --set=root
loopback loop $iso
linux (loop)/boot/syslinux/vmlinuz from=$iso $bootparms
initrd (loop)/boot/syslinux/initrd.zst
}
Obviously the names of the ISO, location of the ISO, and extramod= folder must be changed to match the user's system.

Ed_P
-
Kulle
- Warlord

- Posts: 704
- Joined: 28 Jan 2017, 10:39
- Distribution: v4.0 64bit Xfce
- Location: Berlin
Post#7
by Kulle » 25 May 2023, 09:04
I've tried v0.4 now:
000-kernel-6.3.3.xzm 001-core-stable-20230520.xzm 002-xorg-stable-20230520.xzm 002-xtra-stable-20230520.xzm 003-xfce-4.16-stable-20230523.xzm
But did not work: Xorg failed to start up - ...
I then replaced the kernel 6.3.3 with 6.2.11
Now the system works
Why doesn't the new kernel work?
Kulle
-
porteux
- Shogun

- Posts: 271
- Joined: 12 Mar 2023, 22:10
- Distribution: PorteuX
Post#8
by porteux » 25 May 2023, 11:25
Did you remember to also update vmlinux in /boot/syslinux?
porteux
-
Kulle
- Warlord

- Posts: 704
- Joined: 28 Jan 2017, 10:39
- Distribution: v4.0 64bit Xfce
- Location: Berlin
Post#9
by Kulle » 25 May 2023, 13:25
yes, I used everything original from v0.4,
but the kernel 6.3.3 gives me the error : Xorg failed to start up - ...
That's why I now use the kernel 6.2.11
But why doesn't the new kernel work on my hardware?
Kulle
-
seed_clapper
- Black ninja

- Posts: 48
- Joined: 17 Oct 2022, 13:22
- Distribution: Porteus 5
Post#10
by seed_clapper » 26 May 2023, 05:31
compared ram usage after boot (stable)
kde 5.23.5 ---- 880mb
gnome 42.10 - 782mb
xfce 4.18 ----- 638mb
mate 1.27.1 -- 619mb
xfce 4.12 ----- 564mb
lxqt 1.3.0 ----- 520mb
lxde 0.10.1 --- 224mb
porteuS (220924)
seed_clapper
-
porteux
- Shogun

- Posts: 271
- Joined: 12 Mar 2023, 22:10
- Distribution: PorteuX
Post#11
by porteux » 26 May 2023, 09:35
@seed_clapper, that's a really nice test!
The huge difference in LXQt is probably because you're checking the memory usage using qps, and I have patched it in PorteuX 0.4 to get the real memory consumption, not the incorrect one provided by default.
If you want a more reliable way to check RAM usage across different desktop environments I recommend using the kernel information:
Code: Select all
echo $(( ($(grep MemTotal /proc/meminfo | awk '{print $2}') - $(grep MemAvailable /proc/meminfo | awk '{print $2}')) / 1024 )) MB
Because PorteuX uses zstd (instead of xz) it's expected that it takes a bit more RAM. I tried my best to optimize other things to compensate but in some cases it's still not quite there yet, as seen in KDE. Gonna check this later.
Thanks!

porteux
-
porteux
- Shogun

- Posts: 271
- Joined: 12 Mar 2023, 22:10
- Distribution: PorteuX
Post#12
by porteux » 26 May 2023, 09:38
@Kulle, this is really odd. Can you try a ISO boot in AF? Put the original PorteuX 0.4 ISO in a known place and in the boot screen press TAB and add this (adapting the path accordingly, of course):
porteux
-
Kulle
- Warlord

- Posts: 704
- Joined: 28 Jan 2017, 10:39
- Distribution: v4.0 64bit Xfce
- Location: Berlin
Post#13
by Kulle » 26 May 2023, 13:15
iso will not boot
I downloaded porteux-v0.4-xfce-4.12-stable-x86_64.iso
saved it to sda4.
renamed it to porteux.iso
On the boot screen I press TAB and add
from=/mnt/sda4/porteux.iso
"INIT entering runlevel 4" appears
and then it takes quite a long time:
blinking cursor, screen flashing now and then
and finally
Xorg failed to start up - ...
Kulle
-
Karmi
- Samurai

- Posts: 164
- Joined: 03 Apr 2022, 19:46
- Distribution: Linux
- Location: Old Town, Florida USA
Post#14
by Karmi » 26 May 2023, 20:28
I just tried to use Clonezilla to make a backup image of PorteuX 4 xfce 4.12 (Cinnamon DE added) and Clonezilla said there was a problem — run fdisk or something? I mostly avoid fdisk 'n etc. Clonezilla works for Porteus 5 Cinnamon. It's a 16 GB SanDisk USB — 33MiB fat32 & the rest ext4. No biggie, just a point...
Karmi
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#15
by Ed_P » 26 May 2023, 20:41
If you have access to a Windows system try running a chkdsk command on the drive's partition.
Ed_P