MX Linux Forum

Posted: **Tue Apr 01, 2025 7:37 pm**

Hi,

I am very encouraged by the interest RC1 got but the thread was getting long and muddled so I'm starting a new one for release RC2. Thanks to all posters and testers of RC1!
For newcomers: viewtopic.php?t=84241
*RC1 has been taken down due to limited space on my VPS

RC2 Changelog:

- Update to Liquorix 6.13.4 Kernel (hopefully fixes WiFi issues that were in previous ISO 6.6.12 Kernel).
- Update to Moksha with new integrated scaling of GTK/QT applications (please test). Thanks to Moksha dev 'the_waiter'!
- Tightened up GTK theming to bring it closer to matching Moksha's Green theme.
- Switch to Papirus Icons with custom MX Moksha theme.
- Added previously forgotten Pager to Panel (shelf).
- Place Digital Clock gadget on Desktop.
- Swapped neofetch for fastfetch.
- Added environment variable for Systray Width.
- Added Compositor module, it is named 'ComptonMod' but actually uses picom now. It can be found in Menu-->Settings-->Modules-->Look
*Compositing not enabled by default, the module must be loaded to work.
- Added picom 12.5.1 from MX Test and picom-conf to help with graphical picom settings.
- Added preview of in-development 'Zenithal' theme with matching Skewaita-Zenithal GTK theme.
- HOTKEYS: Win gets you searchable menu, Win+T gets you a terminal.

TO-DO:

- Fix name in GRUB Menu when installed, it falls back to Debian (I had a look and I'm a bit stumped why it isn't working now).
* this issue has a temp fix; in terminal; sudo mousepad /etc/lsb-release and edit line 2 and put 'MX Moksha' in full quotes ie; DISTRIB_ID="MX Moksha" then run sudo update-grub. Will be fixed in next ISO update
- First run Moksha keyboard wizard for setting keyboard at first boot.

ISSUES:

This ISO has a VERY recent kernel, for me booting in Virtualbox 7.1.6 results in multiple freezes and pegs the execution meter and the VM goes unresponsive.
Gnome Boxes is better but not perfect either, bare metal testing seemed fine on a couple of systems I tried so I think the ISO is fine. YMMV!
*If you run into package conflicts between Bodhi Repos and MX Repos I would suggest using MX-Tools-->Repo Manager and disabling the Bodhi Repos and install Applications from MX Repos and rely on Bodhi's Repos for Bodhi and Moksha components only.

DOWNLOADS:

https://downloads.bandshed.net/MX-MOKSHA/

Posted: **Tue Apr 01, 2025 7:58 pm**

Posted: **Tue Apr 01, 2025 10:13 pm**

Verified that wifi is working (it is)

Code: Select all

/etc/lsb-release: line 2: Moksha: command not found
System:
  Kernel: 6.13.8-4-liquorix-amd64 [6.13-9~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=(loop)/antiX/vmlinuz
    buuid=72c84fb0-f541-4393-93b5-2db0d93d2c7c fromiso=/MX_MOKSHA-23-RC2_x64.iso quiet splasht
    nosplash kbd=us lang=en_US tz=America/New_York splasht= live_swap=off
  Desktop: Moksha v: 0.4.1.18446 vt: 7 dm: LightDM v: 1.32.0 Distro: MX_MOKSHA-23-RC2_x64 Out of
    Bodhi TBD base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: AZW product: EQ v: N/A serial: <superuser required>
  Mobo: AZW model: EQ serial: <superuser required> UEFI: American Megatrends LLC. v: N95V106
    date: 12/15/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: Intel N100 bits: 64 type: MCP arch: Alder Lake level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0xBE (190) stepping: 0 microcode: 0xE
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB
    L2: 2 MiB desc: 1x2 MiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1361 high: 3042 min/max: 700/801 boost: enabled scaling: driver: acpi-cpufreq
    governor: performance cores: 1: 3042 2: 801 3: 801 4: 801 bogomips: 6451
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Vulnerable: No microcode
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel alternate: xe arch: Gen-12.2
    process: Intel 10nm built: 2021-22+ ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:46d1 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Acer HX1953L serial: <filter> built: 2013
    res: 1600x900 hz: 60 dpi: 94 gamma: 1.2 size: 432x239mm (17.01x9.41") diag: 494mm (19.4")
    ratio: 16:9 modes: max: 1600x900 min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel Graphics (ADL-N)
    direct-render: Yes
Audio:
  Device-1: Intel driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:54c8 class-ID: 0403
  API: ALSA v: k6.13.8-4-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel driver: iwlwifi v: kernel modules: wl port: N/A bus-ID: 00:14.3
    chip-ID: 8086:54f0 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Intel Ethernet I225-V driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    port: N/A bus-ID: 01:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Intel Ethernet I225-V driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth1 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 chip-ID: 8087:0026
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 362e hci-v: 5.2 rev: 362e
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 476.94 GiB used: 25.78 GiB (5.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 model: 512GB SSD size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: SN09843 temp: 34.9 C
    scheme: GPT
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 38.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2211 libs: 1252 tools: apt,apt-get,aptitude pm: rpm pkgs: 0 pm: flatpak
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/bodhi-repo.list
    1: deb http://packages.bodhilinux.com/bodhi bookworm b7debbie
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 209 Uptime: 5m wakeups: 2 Memory: 15.4 GiB used: 1.27 GiB (8.2%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Probably not a big deal, but also note the error message at the start of the QSI "/etc/lsb-release: line 2: Moksha: command not found"

Also you might consider running an 'update-pciids' to update the PCI ID list.
For my hardware the "Intel CNVi: Wi-Fi" description after updating is a bit more informative than just "Intel".
Here's before and after

Code: Select all

demo@mx-moksha-live:~
$ inxi -nxxx
Network:
  Device-1: Intel driver: iwlwifi v: kernel port: N/A bus-ID: 00:14.3
    chip-ID: 8086:54f0 class-ID: 0280
  IF: wlan0 state: up mac: f0:d4:15:b7:4b:11
  Device-2: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 7c:83:34:b9:2a:a4
  Device-3: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth1 state: down mac: 7c:83:34:b9:2a:a5

demo@mx-moksha-live:~
$ sudo update-pciids
[sudo] password for demo:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  316k  100  316k    0     0   266k      0  0:00:01  0:00:01 --:--:--  266k
Done.

demo@mx-moksha-live:~
$ inxi -nxxx
Network:
  Device-1: Intel CNVi: Wi-Fi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:54f0 class-ID: 0280
  IF: wlan0 state: up mac: f0:d4:15:b7:4b:11
  Device-2: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 7c:83:34:b9:2a:a4
  Device-3: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth1 state: down mac: 7c:83:34:b9:2a:a5
demo@mx-moksha-live:~

Posted: **Tue Apr 01, 2025 11:32 pm**

@kmathern

Thanks yet again! Your keen eye solved 2 problems! Apparently lines that aren't quoted in /etc/lsb-release can't have whitespaces, I probably should have known this but I hand-edited it rather hastily... So (1) changing the line to 'MX_Moksha' allowed QSI to not fuss and (2) it fixed the GRUB Boot name problem, the GRUB boot list is generated from lsb-release but if it fails it defaults to 'Debian'. Now I want to upload a new ISO...

The 'update-pciids' is a new one on me, I'm not sure where along the line I would run that. Where does it normally run on a system..?

Posted: **Wed Apr 02, 2025 1:45 am**

I just confirmed that adding the " " to that file, saving it, and running update-grub fixed the Grub menu name issue.

Posted: **Wed Apr 02, 2025 7:43 am**

FullScale4Me wrote: Wed Apr 02, 2025 1:45 am I just confirmed that adding the " " to that file, saving it, and running update-grub fixed the Grub menu name issue.

Thanks for the confirmation, a silly detail for me to have missed..

Posted: **Wed Apr 02, 2025 10:48 am**

AVLinux wrote: Tue Apr 01, 2025 11:32 pm The 'update-pciids' is a new one on me, I'm not sure where along the line I would run that. Where does it normally run on a system..?

I think you could run it pretty much anytime before you do a remaster.
The list 'update-pciids' updates is at /usr/share/misc/pci.ids.
If you look at it you'll see it's about two years old (2023-04-10), at this time running the update brings in a 2025-03-09 version.

Posted: **Wed Apr 02, 2025 11:03 am**

kmathern wrote: Wed Apr 02, 2025 10:48 am
AVLinux wrote: Tue Apr 01, 2025 11:32 pm The 'update-pciids' is a new one on me, I'm not sure where along the line I would run that. Where does it normally run on a system..?
I think you could run it pretty much anytime before you do a remaster.
The list 'update-pciids' updates is at /usr/share/misc/pci.ids.
If you look at it you'll see it's about two years old (2023-04-10), at this time running the update brings in a 2025-03-09 version.

Thanks for the info. These aren't really 'remasters' they are built like MX is with the build-iso-mx script one pkg at a time in a chroot. I suppose if it is essentially a definitions kind of file I could place an updated file in /usr/share/misc/pci.ids but I would need to generate the updated definitions on a running system I guess...? Until you mentioned it I didn't even know this was a thing...lol. I have learned my 'something new' today.. I'm kind of surprised that QSI and inxi don't simply run that command this as part of their info retrieval routine..

Posted: **Thu Apr 03, 2025 11:53 am**

I installed the RC2 version, and it looks great.

I made the two published fixes and everything is correct.

Congratulations on your good work.

Since you piqued my curiosity, I tried Debian 12 with Moksha 7 and Debian 13 with Moksha 8, manually using the commands in the GitHub scripts. Without the MxLinux base, they were pathetic.

Code: Select all

System:
  Kernel: 6.13.8-4-liquorix-amd64 [6.13-9~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.13.8-4-liquorix-amd64
    root=UUID=<filter> ro quiet threadirqs splash
  Desktop: Moksha v: 0.4.1.18446 vt: 7 dm: LightDM v: 1.32.0 Distro: MX_MOKSHA-23-RC2_x64 Out of
    Bodhi TBD base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2 serial: <superuser required>
    Chassis: Oracle Corporation type: 1 serial: <superuser required>
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required> UEFI: innotek GmbH
    v: VirtualBox date: 12/01/2006
CPU:
  Info: model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen/Zen+
    note: check gen: 1 level: v2 built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
    stepping: 1 microcode: N/A
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 192 KiB desc: d-2x32 KiB; i-2x64 KiB
    L2: 1024 KiB desc: 2x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 3635 min/max: N/A cores: 1: 3635 2: 3635 bogomips: 14541
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not
    affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: Virtual-1
    empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, Virtual-8
    bus-ID: 00:02.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: vmware
    unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 358x202mm (14.09x7.95") s-diag: 411mm (16.18")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1360x768 hz: 60 size: N/A modes: max: 1280x800
    min: 640x480
  API: OpenGL v: 4.5 Mesa 24.2.8-1mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
    direct-render: Yes
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus-ID: 00:05.0
    chip-ID: 8086:2415 class-ID: 0401
  API: ALSA v: k6.13.8-4-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: c1a0 bus-ID: 00:03.0
    chip-ID: 8086:100e class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A
    modules: i2c_piix4 port: N/A bus-ID: 00:07.0 chip-ID: 8086:7113 class-ID: 0680
Drives:
  Local Storage: total: 80 GiB used: 10.12 GiB (12.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: VirtualBox model: VBOX HARDDISK size: 80 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1.0 scheme: GPT
Partition:
  ID-1: / raw-size: 39.06 GiB size: 38.15 GiB (97.67%) used: 9.32 GiB (24.4%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%) used: 288 KiB (0.0%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 29.3 GiB size: 28.67 GiB (97.86%) used: 823.8 MiB (2.8%) fs: ext4
    dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3
    maj-min: 8:3
  ID-2: swap-2 type: zram size: 256 MiB used: 189.8 MiB (74.1%) priority: 100 dev: /dev/zram0
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: 2216 pm: dpkg pkgs: 2211 libs: 1252 tools: apt,apt-get,aptitude pm: rpm pkgs: 0
    pm: flatpak pkgs: 5
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/bodhi-repo.list
    1: deb http://packages.bodhilinux.com/bodhi bookworm b7debbie
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.netlinux.cl/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.netlinux.cl/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 197 Uptime: 14m wakeups: 1379 Memory: 1.91 GiB used: 1.26 GiB (65.9%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Thu Apr 03, 2025 12:22 pm**

Gabriel_M wrote: Thu Apr 03, 2025 11:53 am I installed the RC2 version, and it looks great.

I made the two published fixes and everything is correct.

Congratulations on your good work.

Since you piqued my curiosity, I tried Debian 12 with Moksha 7 and Debian 13 with Moksha 8, manually using the commands in the GitHub scripts. Without the MxLinux base, they were pathetic.

While I appreciate the comments and encouragement let's not pit one against another. Bodhi Linux is a great and highly regarded Distro on it's own merits and because of their unique work I was inspired to try it and then blend it. To be clear the Bodhi scripts are designed to integrate with an existing Debian-based install and give as bare-bones an install as possible as to not interfere with anything. I actually asked the developers to chop it down to what it is now to minimize potential pkg conflicts. A Bodhi script install is not like a 'proper' Bodhi install from their own ISO's. Sure MX has their own great utility toolset but Bodhi has some cool stuff too like their web-based Package installer etc.. The idea here is to blend two great ideas without taking away from either.

Posted: **Thu Apr 03, 2025 12:46 pm**

AVLinux wrote: Wed Apr 02, 2025 11:03 am Thanks for the info. These aren't really 'remasters' they are built like MX is with the build-iso-mx script one pkg at a time in a chroot. I suppose if it is essentially a definitions kind of file I could place an updated file in /usr/share/misc/pci.ids but I would need to generate the updated definitions on a running system I guess...? Until you mentioned it I didn't even know this was a thing...lol. I have learned my 'something new' today.. I'm kind of surprised that QSI and inxi don't simply run that command this as part of their info retrieval routine..

I just made a request for a backport of the sid/trixie pci.ids package. Having a updated pci.ids package installed will result in having a updated PCI ID list without needing to run the 'update-pciids' script. And it might work better with how you create your ISO with the build-iso-mx script.

Posted: **Thu Apr 03, 2025 12:50 pm**

kmathern wrote: Thu Apr 03, 2025 12:46 pm
AVLinux wrote: Wed Apr 02, 2025 11:03 am Thanks for the info. These aren't really 'remasters' they are built like MX is with the build-iso-mx script one pkg at a time in a chroot. I suppose if it is essentially a definitions kind of file I could place an updated file in /usr/share/misc/pci.ids but I would need to generate the updated definitions on a running system I guess...? Until you mentioned it I didn't even know this was a thing...lol. I have learned my 'something new' today.. I'm kind of surprised that QSI and inxi don't simply run that command this as part of their info retrieval routine..
I just made a request for a backport of the sid/trixie pci.ids package. Having a updated pci.ids package installed will result in having a updated PCI ID list without needing to run the 'update-pciids' script. And it might work better with how you create your ISO with the build-iso-mx script.

Great stuff! Thank you!

Posted: **Sun Apr 06, 2025 11:21 am**

Working toward a final release, trying out some stuff adapting my E-Modulus modular Conky, obviously it will look a bit more integrated with picom running but if we're going skeumorphic might as well go all the way!

Posted: **Mon Apr 07, 2025 9:07 pm**

AVLinux wrote: Sun Apr 06, 2025 11:21 am Working toward a final release, trying out some stuff adapting my E-Modulus modular Conky, obviously it will look a bit more integrated with picom running but if we're going skeumorphic might as well go all the way!

wow...this moksha variant of yours has better aesthetics than AVL MXE and is also miles better than the images on bodhi's page...

I'll have to test this out to see how it performs...

also could you check if everything is fine if you hook up your laptop to a monitor over VGA/HDMI...this maybe unrelated, my laptop screen got bad and I slaved my laptop to a monitor over VGA but I don't see any taskbars or panel on the monitor, everything else works fine...I have not had the time to scour the web if this is a bug or it is just how enlightenment operates...

Posted: **Mon Apr 07, 2025 11:18 pm**

Aceediq wrote: Mon Apr 07, 2025 9:07 pm also could you check if everything is fine if you hook up ypur laptop to a monitor over VGA/HDMI...this maybe unrelated, my laptop screen got bad and I slaved my laptop to a monitor over VGA but I don't see any taskbars or panel on the monitor, everything else works fine...I have not had the time to scour the web if this is a bug or it is just how enlightenment operates...

Set the external monitor as the Primary display.

Applications ---> Preferences ---> Monitor Settings. Right click on external display and check the 'Primary check box.

Log out, then log back in.

Posted: **Tue Apr 08, 2025 6:21 pm**

should I just wait for RC3

???

LOL

Posted: **Tue Apr 08, 2025 9:51 pm**

blast0id wrote: Tue Apr 08, 2025 6:21 pm should I just wait for RC3 ???

LOL

There probably won't be an RC3, most likely a finished release fairly soon... Some things to be aware of:

- This is coming along late in MX-23/Debian Bookworm's lifespan, there will only be one release of MX Moksha on Bookworm and all future development will move to MX-25/Debian Trixie, this release should be looked at as a proof-of-concept working demo of Moksha on MX but not as a long term support prospect.
- At this point this isn't a drop-in replacement for AV Linux, There are a lot of reasons to like or even prefer Moksha to Enlightenment but until I'm confident that it makes a reliable production platform there is no definite plan to make major changes.

Posted: **Tue Apr 08, 2025 11:09 pm**

FullScale4Me wrote: Mon Apr 07, 2025 11:18 pm
Aceediq wrote: Mon Apr 07, 2025 9:07 pm also could you check if everything is fine if you hook up ypur laptop to a monitor over VGA/HDMI...this maybe unrelated, my laptop screen got bad and I slaved my laptop to a monitor over VGA but I don't see any taskbars or panel on the monitor, everything else works fine...I have not had the time to scour the web if this is a bug or it is just how enlightenment operates...
Set the external monitor as the Primary display.

Applications ---> Preferences ---> Monitor Settings. Right click on external display and check the 'Primary check box.

Log out, then log back in.

there was no option of monitor settings in AVL MXE 23.5

@AVLinux

Posted: **Tue Apr 08, 2025 11:23 pm**

Aceediq wrote: Tue Apr 08, 2025 11:09 pm
there was no option of monitor settings in AVL MXE 23.5

@AVLinux

Set the external monitor as the Primary display.

Right click on the desktop ---> Applications ---> Preferences ---> Monitor Settings. Right click on external display and check the 'Primary' check box.

Log out, then log back in.

Posted: **Tue Apr 08, 2025 11:26 pm**

AVLinux wrote: Tue Apr 08, 2025 9:51 pm
blast0id wrote: Tue Apr 08, 2025 6:21 pm should I just wait for RC3 ???

LOL
There probably won't be an RC3, most likely a finished release fairly soon... Some things to be aware of:

- This is coming along late in MX-23/Debian Bookworm's lifespan, there will only be one release of MX Moksha on Bookworm and all future development will move to MX-25/Debian Trixie, this release should be looked at as a proof-of-concept working demo of Moksha on MX but not as a long term support prospect.
- At this point this isn't a drop-in replacement for AV Linux, There are a lot of reasons to like or even prefer Moksha to Enlightenment but until I'm confident that it makes a reliable production platform there is no definite plan to make major changes.

well, I am a huge fan of DE's with good aesthetics, not average, so I am already tilting to your moksha variant since it is aesthetically more cohesive and uniform, for example the taskbar icons...

other DE's that do a good job of serving looks are KDE and gnome...gnome is cringe with their wokeness and KDE is built with QT...

composition and rendering wise, there are only two plauers, IMO, KDE and enlightenment...

moksha is a variant of enlightenment, making it easy to get accustomed to...

so if everything under the hood of AVL MXE is the same as your moksha variant, I believe your moksha variant can see high mileage before being concerned with DE-specific updates...since non-DE specific updates can be done through mxpin or buy grabbing a deb file from your server...

the only major concern are dependencies but if there are still power users using mx19, then there are a lot of optimistic possibilities too...

I just hope compositions on moksha is as good as enlightenment in the very least it even better, if not, moksha would have to remain a prototype

Posted: **Tue Apr 08, 2025 11:31 pm**

FullScale4Me wrote: Tue Apr 08, 2025 11:23 pm
Aceediq wrote: Tue Apr 08, 2025 11:09 pm
there was no option of monitor settings in AVL MXE 23.5

@AVLinux
Set the external monitor as the Primary display.

Right click on the desktop ---> Applications ---> Preferences ---> Monitor Settings. Right click on external display and check the 'Primary' check box.

Log out, then log back in.

I am not seeing the option of monitor settings...

edit: I am trying to attach an image but I am getting a submission invalid error...

Posted: **Wed Apr 09, 2025 12:16 am**

Again, Right Click on the Desktop - no clicky on anything on the bar thingie at the bottom....

Posted: **Wed Apr 09, 2025 3:52 am**

Aceediq wrote: Tue Apr 08, 2025 11:31 pm
edit: I am trying to attach an image but I am getting a submission invalid error...

You can also upload the image to an external service of post image or board attachment is not working. Just be mindful of the rules on image sizes when posting linked images.

Posted: **Wed Apr 09, 2025 4:06 am**

FullScale4Me wrote: Wed Apr 09, 2025 12:16 am Again, Right Click on the Desktop - no clicky on anything on the bar thingie at the bottom....

oh, you already on moksha...

I am still on AVL MXE

Posted: **Wed Apr 09, 2025 4:20 am**

FullScale4Me wrote: Wed Apr 09, 2025 12:16 am Again, Right Click on the Desktop - no clicky on anything on the bar thingie at the bottom....

@AVLinux I guess this would be another strong reason to switch to moksha and maybe keep it...I can't remember a time I slaved my laptop to a monitor, I was averagely mobile...so never came across issues using external monitors on enlightenment...

I would have to say only KDE is doing a decent job of having a nutritionally balanced diet always served when it comes to Linux DE's...the older we get the more appealing such offerings are...

Posted: **Wed Apr 09, 2025 11:35 am**

OK, we're getting into the weeds here quickly..

On "MX Moksha" a patched version of 'arandr' is used for monitor settings, Moksha itself doesn't have a monitor settings application so the Bodhi devs cleverly adapted arandr.

In AV Linux 23.X Enlightenment is used and of course there is a Monitor settings application, it is built into Enlightenment and easily found in Menu-->Settings-->Screen Setup

Please keep this thread about MX Moksha and post AV Linux issues in a new thread..

Posted: **Wed Apr 09, 2025 2:46 pm**

AVLinux wrote: Wed Apr 09, 2025 11:35 am OK, we're getting into the weeds here quickly..

On "MX Moksha" a patched version of 'arandr' is used for monitor settings, Moksha itself doesn't have a monitor settings application so the Bodhi devs cleverly adapted arandr.

In AV Linux 23.X Enlightenment is used and of course there is a Monitor settings application, it is built into Enlightenment and easily found in Menu-->Settings-->Screen Setup

Please keep this thread about MX Moksha and post AV Linux issues in a new thread..

oh alright, let's stay out of the weeds and talk on moksha, I read in your RC1 thread that moksha's compositing isn't as good as enlightenment but they made available a workaround using picom...

but you added that, in line with the capabilities of picom as we know, picom does it's job...I want to ask if picom doing what picom does is as good as enlightenment's compositing?

what does enlightenment use to handle compositing if not picom?

and is there any reason why the moksha devs did not carry over enlightenment's compositing over to moksha?

Posted: **Thu Apr 10, 2025 4:32 pm**

Aceediq wrote: Wed Apr 09, 2025 2:46 pm ...

oh alright, let's stay out of the weeds and talk on moksha, I read in your RC1 thread that moksha's compositing isn't as good as enlightenment but they made available a workaround using picom...

but you added that, in line with the capabilities of picom as we know, picom does it's job...I want to ask if picom doing what picom does is as good as enlightenment's compositing?

what does enlightenment use to handle compositing if not picom?

and is there any reason why the moksha devs did not carry over enlightenment's compositing over to moksha?

Native enlightenment compositing was stripped out of e17 code when Jeff Hoogland forked e17 and called it moksha. That was before I took over as lead dev for Bodhi. But the reason is clear e17 composting was problematic and buggy. Enlightenment compositing is less buggy now, BUT it is still problematic for Bodhi. The issue is that it does not work on really old video cards. Bodhi is one of a small handful of distros that one can install on these older machines it is best for us if it works out of the box as much as possible.

Posted: **Thu Apr 10, 2025 4:59 pm**

@ylee2130

Thanks for the clarification on that, having used both I would say that picom works great and with a few settings it feels very much like E's compositing.. Another note about Enlightenment's compositing is that it really can't be turned 'off' and with Moksha you can opt out completely. Enlightenment offers emulated 'Software' compositing and openGL-based compositing and on older systems it's software compositing can be very CPU hungry to the point of causing poor Video performance and other system lags. To be fair on a modern system with a good openGL supported Video card Enlightenment's compositing is very smooth.

Posted: **Thu Apr 10, 2025 5:20 pm**

Yes Enlightenment composting is very nice and very smooth on my laptop. It does not work at all on an old netbook I have, half the screen is black the and other half unusable. And as noted composting can not be turned off in Enlightenment now as it could in e17.

Posted: **Thu Apr 10, 2025 8:13 pm**

ylee2130 wrote: Thu Apr 10, 2025 4:32 pm
Aceediq wrote: Wed Apr 09, 2025 2:46 pm ...

oh alright, let's stay out of the weeds and talk on moksha, I read in your RC1 thread that moksha's compositing isn't as good as enlightenment but they made available a workaround using picom...

but you added that, in line with the capabilities of picom as we know, picom does it's job...I want to ask if picom doing what picom does is as good as enlightenment's compositing?

what does enlightenment use to handle compositing if not picom?

and is there any reason why the moksha devs did not carry over enlightenment's compositing over to moksha?
Native enlightenment compositing was stripped out of e17 code when Jeff Hoogland forked e17 and called it moksha. That was before I took over as lead dev for Bodhi. But the reason is clear e17 composting was problematic and buggy. Enlightenment compositing is less buggy now, BUT it is still problematic for Bodhi. The issue is that it does not work on really old video cards. Bodhi is one of a small handful of distros that one can install on these older machines it is best for us if it works out of the box as much as possible.

then it's a no brainer to go with this moksha variant since @AVLinux has confirmed picom is as good as enlightenment to an extent...what really sold me is divergent option linux offers to those who want to add a spin to a distro is found in the option of bodhi devs allowing for compositing to be toggled on/off...though such options might have been rampant in the past...currently, those options are like both fresh air and nostalgia nowadays when the act of nerfing user options, painfully without real valid reasons is becoming defacto circumstance

but what bothers me is moksha's future concerning the client that may be used in future - wayland...though like @AVLinux pointed out, a lot of creative linux softwares still cater primarily for x11 but x11 being overthrown by wayland is something I still consider...like pipewire is subtly usurping the audio routing throne from pulseaudio and jack

nothing wrong with distro hopping but the more linux becomes my daily driver, the more I am entrenched in linux workflows, the more I seek stabilities in linux distros...

so if moksha isn't on the wayland ship, I hope it is, what's the benefit of trying out moksha, if all this is temporary?

I love good aesthetics and moksha has that over enlightenment but as @AVLinux AVL perks are becoming distro agnostic, other candidates, a worthy mention would be @Freja extrox, are becoming viable options for a well built creative/creator distro...

I hope my assumptions aren't off t

Posted: **Thu Apr 10, 2025 9:13 pm**

Well,

I was also a bit put off at first by the lack of Wayland support and then I thought about Fluxbox having no Wayland support and the reality that XFCE4 has just started with preliminary support, LXQT is somewhere in the middle and yes of course Gnome and KDE are pretty much there so yes, Wayland is inevitable but it is also NOT imminent. Debian is usually one of the last to drop core libraries and they will not be dropping Xorg any time soon. So being conservative X will be here in Debian Trixie and I would imagine the next Debian after Trixie would quite likely not drop X either so we're talking like 5-6 years in the future, I don't know about you but I have about 863 more important concerns than Wayland in the next 5 years. At this point I would not turn my back on something as unique, efficient and fun as Moksha because of far-off future Wayland concerns.

Posted: **Thu Apr 10, 2025 10:12 pm**

AVLinux wrote: Thu Apr 10, 2025 9:13 pm Well,

I was also a bit put off at first by the lack of Wayland support and then I thought about Fluxbox having no Wayland support and the reality that XFCE4 has just started with preliminary support, LXQT is somewhere in the middle and yes of course Gnome and KDE are pretty much there so yes, Wayland is inevitable but it is also NOT imminent. Debian is usually one of the last to drop core libraries and they will not be dropping Xorg any time soon. So being conservative X will be here in Debian Trixie and I would imagine the next Debian after Trixie would quite likely not drop X either so we're talking like 5-6 years in the future, I don't know about you but I have about 863 more important concerns than Wayland in the next 5 years. At this point I would not turn my back on something as unique, efficient and fun as Moksha because of far-off future Wayland concerns.

yeah that's quite the take

we don't pass on on icecream because it melts away quickly

but I still gear towards stability as the days go by...and the issue is not really about debian or mx dropping support, it's how most apps and DE's have made wayland top priority and how quickly the transitioning is going on...though there had been opinion wars and arguments for years...

I wouldn't pick icecream no matter how out of this world it may be over a meal that would have me going for hours...so I wouldn't want to have a blast with moksha only to end up transitioning 6years later, when it could have been done I would say subtly and w/o so much focus from my end...

that's if we even have 6years, it may be less or more...also, I don't personally get the vibe when linux devs rightly refuse to jump ship to things that have or would eventually become defacto over ideological reasons...in my head, it reads one knows death is coming and instead of taking steps to get rid of it, completely if possible, one rather takes steps to, as much as possible, ease in to death?

I am trying to install moksha using ventoy but I am getting hangs and init not found error (/ventoy/busybox/sh: can't access tty; job control turned off.)

mbr boot though

but I think it is a ventoy issue coping with the newer moksha iso though I am on the latest ventoy version...

Posted: **Fri Apr 11, 2025 7:03 am**

Hopefully X.org will "never" go away. It would mean the death of a lot of Linux functionality including desktops and window managers. SysVinit is still here despite systemd so I think the situation will be similar with X.org and Wayland. You will likely be able to avoid systemd-only and Wayland-only applications if you aren't too picky.

Posted: **Fri Apr 11, 2025 12:43 pm**

dreamer wrote: Fri Apr 11, 2025 7:03 am Hopefully X.org will "never" go away. It would mean the death of a lot of Linux functionality including desktops and window managers. SysVinit is still here despite systemd so I think the situation will be similar with X.org and Wayland. You will likely be able to avoid systemd-only and Wayland-only applications if you aren't too picky.

I sincerely hope you are right! The "if you aren't too picky" part was cute though... I don't know anyone more picky than Linux Users... People here post because they can't handle an animated bootsplash for .05 seconds and that's just the beginning.. I routinely see people uninstall a completely functional OS just to get an update for or obtain some incidental program or in my AVL case some random Audio Plugin. Linux people's pickiness is their undoing..

Posted: **Fri Apr 11, 2025 3:15 pm**

Aceediq wrote: Tue Apr 08, 2025 11:26 pmwell, I am a huge fan of DE's with good aesthetics, not average, so I am already tilting to your moksha variant since it is aesthetically more cohesive and uniform, for example the taskbar icons...

I'm just going to need a "blue" variant... lol... "#0008D0"

damn those HTC Energy ROMs... haha

Posted: **Fri Apr 11, 2025 7:51 pm**

blast0id wrote: Fri Apr 11, 2025 3:15 pm
Aceediq wrote: Tue Apr 08, 2025 11:26 pmwell, I am a huge fan of DE's with good aesthetics, not average, so I am already tilting to your moksha variant since it is aesthetically more cohesive and uniform, for example the taskbar icons...
I'm just going to need a "blue" variant... lol... "#0008D0"

damn those HTC Energy ROMs... haha

Haha, the whole green thing is me being faithful to the default look and colors of Bodhi Linux, it's not really my design I'm just trying to maintain that look in the default setup so it's clearly identifiable. There are a lot of alternate Moksha themes installable from MXPI but I will say at this point there is not a dark blue/orange 'Diehard' color scheme like AV Linux has.

Posted: **Fri Apr 11, 2025 8:36 pm**

Aceediq wrote: Thu Apr 10, 2025 10:12 pm I am trying to install moksha using ventoy but I am getting hangs and init not found error (/ventoy/busybox/sh: can't access tty; job control turned off.)

mbr boot though

but I think it is a ventoy issue coping with the newer moksha iso though I am on the latest ventoy version...

I just did a bare metal install of Moksha to a Dell N7010 laptop (MBR) with Ventoy 1.1.05 ... Several reboots post-install with no noticeable errors.

Code: Select all

System:
  Kernel: 6.13.8-4-liquorix-amd64 [6.13-9~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.13.8-4-liquorix-amd64
    root=UUID=<filter> ro quiet threadirqs splash
  Desktop: Moksha v: 0.4.1.18446 vt: 7 dm: LightDM v: 1.32.0 Distro: MX_MOKSHA-23-RC2_x64 Out of
    Bodhi TBD base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Portable System: Dell product: Inspiron N7010 v: A11 serial: <superuser required>
  Mobo: Dell model: 08VFX1 v: A11 serial: <superuser required> BIOS: Dell v: A11 date: 03/31/2011
Battery:
  ID-1: BAT0 charge: 5.4 Wh (100.0%) condition: 5.4/5.3 Wh (100.7%) volts: 11.9 min: 11.1
    model: PANASONIC Dell type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i5 M 460 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
    built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 5 microcode: 0x7
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2262 high: 2534 min/max: 1199/2534 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 1448 2: 2534 3: 2534 4: 2534 bogomips: 20217
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel
    arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
  Device-2: Microdia 1.3 MPixel Integrated Webcam type: USB driver: uvcvideo bus-ID: 1-1.4:3
    chip-ID: 0c45:641d class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: intel
    dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
  Monitor-1: LVDS-1 mapped: LVDS1 model: Seiko Epson 0x544b built: 2009 res: 1600x900 hz: 60
    dpi: 106 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3") ratio: 16:9 modes: 1600x900
  API: OpenGL v: 2.1 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel HD Graphics (ILK)
    direct-render: Yes
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell 5 driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403
  API: ALSA v: k6.13.8-4-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Dell Inspiron M5010 / XPS
    8300 driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
    chip-ID: 14e4:4727 class-ID: 0280
  IF: wlan0 state: dormant mac: <filter>
  Device-2: Qualcomm Atheros AR8152 v1.1 Fast Ethernet vendor: Dell driver: atl1c v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 04:00.0 chip-ID: 1969:2060 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 119.24 GiB used: 11.5 GiB (9.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Verbatim model: Vi550 S3 size: 119.24 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 840N scheme: MBR
Partition:
  ID-1: / raw-size: 19.53 GiB size: 19.06 GiB (97.57%) used: 11.5 GiB (60.3%) fs: ext4
    dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
  ID-2: swap-2 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2213 libs: 1253 tools: apt,apt-get,aptitude pm: rpm pkgs: 0 pm: flatpak
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/bodhi-repo.list
    1: deb http://packages.bodhilinux.com/bodhi bookworm b7debbie
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 230 Uptime: 4m wakeups: 4 Memory: 7.56 GiB used: 834.8 MiB (10.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Sat Apr 12, 2025 1:06 pm**

FullScale4Me wrote: Fri Apr 11, 2025 8:36 pm

Aceediq wrote: Thu Apr 10, 2025 10:12 pm I am trying to install moksha using ventoy but I am getting hangs and init not found error (/ventoy/busybox/sh: can't access tty; job control turned off.)

mbr boot though

but I think it is a ventoy issue coping with the newer moksha iso though I am on the latest ventoy version...

I just did a bare metal install of Moksha to a Dell N7010 laptop (MBR) with Ventoy 1.1.05 ... Several reboots post-install with no noticeable errors.

Code: Select all

System:
  Kernel: 6.13.8-4-liquorix-amd64 [6.13-9~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.13.8-4-liquorix-amd64
    root=UUID=<filter> ro quiet threadirqs splash
  Desktop: Moksha v: 0.4.1.18446 vt: 7 dm: LightDM v: 1.32.0 Distro: MX_MOKSHA-23-RC2_x64 Out of
    Bodhi TBD base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Portable System: Dell product: Inspiron N7010 v: A11 serial: <superuser required>
  Mobo: Dell model: 08VFX1 v: A11 serial: <superuser required> BIOS: Dell v: A11 date: 03/31/2011
Battery:
  ID-1: BAT0 charge: 5.4 Wh (100.0%) condition: 5.4/5.3 Wh (100.7%) volts: 11.9 min: 11.1
    model: PANASONIC Dell type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i5 M 460 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
    built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 5 microcode: 0x7
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2262 high: 2534 min/max: 1199/2534 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 1448 2: 2534 3: 2534 4: 2534 bogomips: 20217
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel
    arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
  Device-2: Microdia 1.3 MPixel Integrated Webcam type: USB driver: uvcvideo bus-ID: 1-1.4:3
    chip-ID: 0c45:641d class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: intel
    dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
  Monitor-1: LVDS-1 mapped: LVDS1 model: Seiko Epson 0x544b built: 2009 res: 1600x900 hz: 60
    dpi: 106 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3") ratio: 16:9 modes: 1600x900
  API: OpenGL v: 2.1 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel HD Graphics (ILK)
    direct-render: Yes
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell 5 driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403
  API: ALSA v: k6.13.8-4-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Dell Inspiron M5010 / XPS
    8300 driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
    chip-ID: 14e4:4727 class-ID: 0280
  IF: wlan0 state: dormant mac: <filter>
  Device-2: Qualcomm Atheros AR8152 v1.1 Fast Ethernet vendor: Dell driver: atl1c v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 04:00.0 chip-ID: 1969:2060 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 119.24 GiB used: 11.5 GiB (9.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Verbatim model: Vi550 S3 size: 119.24 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 840N scheme: MBR
Partition:
  ID-1: / raw-size: 19.53 GiB size: 19.06 GiB (97.57%) used: 11.5 GiB (60.3%) fs: ext4
    dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
  ID-2: swap-2 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2213 libs: 1253 tools: apt,apt-get,aptitude pm: rpm pkgs: 0 pm: flatpak
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/bodhi-repo.list
    1: deb http://packages.bodhilinux.com/bodhi bookworm b7debbie
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 230 Uptime: 4m wakeups: 4 Memory: 7.56 GiB used: 834.8 MiB (10.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

booting from usb drive, legacy boot, bare metal, gives the first image before restrarting and showing the second image

does anyone know of other ways to attach pictures to a post? postimages or the forum file attachment options aren't working for me...

Posted: **Sat Apr 12, 2025 1:54 pm**

dreamer wrote: Fri Apr 11, 2025 7:03 am Hopefully X.org will "never" go away. It would mean the death of a lot of Linux functionality including desktops and window managers. SysVinit is still here despite systemd so I think the situation will be similar with X.org and Wayland. You will likely be able to avoid systemd-only and Wayland-only applications if you aren't too picky.

yeah, x11 going away would mean the death of linux components that decide not to switch over...

if alsa could move to PA and now pipewire, the linux landscape would evolve to stability and distro immutable functions...

the linux ecosystem has evolved from dev, geek only users to a wide variety of users which is why GUI interfaces are on the rise, though there are cmdesque users who detest such evolution but that is a necessary evolution and they would have to come to terms with that, if they want a cmd geeky devy distro, that option is still available...standing against such evolution because they don't like it doesn't make sense any longer...

look at debian and sysD, they moved forward, why? they are becoming user centric which is the way forward for having the year of the linux...devuan tried to make a sysd free distro but they couldn't do that completely...we have sysv on mxlinux because of serious efforts from the mxdevs but at the same time, they allowed for a sysd option, which has proven to be a very good decision down the line...

currently sysd compatibility is just a step from being hardcoded into linux apps...last I checked, if I am not wrong, either inkscape or gimp has prioritized a sysd compatibility development milestone...why would we then choose to kick against a rock while leaving no room for other options for those who do not agree to kick against the rocks?

a lot of linux contentions is basically founded upon making the distro more comfortable for devs or for home users...now I believe prioritizing home users is the way forward why? devs are more likely to work around issues on linux than a lot of home users and making distros more comfortable for devs seem counterintuitive if they want to maintain the devy tinkering nature because they have the skillset and toolset...they basically , in lay mans terms, don't want things to get easier...sysd would make things easier for home end users but MIGHT be nerve wracking for devs... there is no issue, let them stick to distros that caters solely for them and allow the other distros cater for other users

secondly, devs most likely won't pay devs, it's end users that have a high chance of doing that...you are not doing this for the money? then devs should stop asking for starbucks when users lay their complains...you can't offer solutions just for yourself when you feel like it and then ask l the world to foot your bills...

@AVLinux once said he preferred the tty booting option of AVL, me I don't, since I don't think it is beneficial to me, if I need to diagonize my PC, there are steps to take and enabling a tty boot is always an option, if not, just boot up and let me get working...

what did @AVLinux do, he made both options available since we would both like to use AVL, he did not lord his preference of tty boot, over those willing to use AVL...

now, I do not undermine dev work...I am trying to understand the reasoning behind moksha's devs decision to not ever transition to wayland due to supporting old chips, even cobol and fortan, despite how simple they may be, aren't widely used any longer, things are meant to phase out where there are options with better workflows...

why moksha devs? if AVL would have a moksha variant, I would use the moksha variant but the decision of moksha devs insinuates that I follow them till the end of the road even when wayland might become a far better option...

moksha accepts sysd but refuse wayland...

you see Linuxers throwing stones against distros who decide to mimick windows and macos GUI and workflows under non beneficial statements like Linux isn't windows or macos, so? I want my distro to look and feel like windows or macos without the telemetry and ram hogging, what's wrong with that?

If I want the distro I use to look like macos but have a windows workflow, I should be applauded like one who would want to go through the cmdline instead of a GUI...in the very least, there shouldn't be opposition or obstacles

if x11 want to remain on the scene, then they should fix the bugs not demanding an acceptance of the bugs in x11...

@ylee2130

Posted: **Sat Apr 12, 2025 2:42 pm**

I use offsite sites to upload images which offer resizing and thumbnail links.

https://postimages.org/

Posted: **Sat Apr 12, 2025 2:43 pm**

@Aceediq
A lot to unpack there..

I don't recall the tty booting conversation, sorry.. Don't give me too much credit though I just know enough to be dangerous and 'Developer' is too big of a hat for me..

To be clear Moksha is not avoiding or rejecting Wayland at all, their fork of Enlightenment (E-17) simply has no Wayland-ready code in it. Wayland was an addition to later versions of Enlightenment and Bodhi serving a large amount of their users on older machines and hardware simply haven't addressed Wayland yet, so they aren't being stubborn about it because it hasn't even been on their radar yet. They have quite a few years to decide if and how they will address it. I can't foresee people who have put as much sweat and toil in something like Bodhi are just going to close shop and quit because of Wayland, I'm sure over time they will figure something out.

Also AV Linux is not leaving MX or becoming a Bodhi version so the Moksha Desktop Environment on it's own is not a determining factor as to whether there is an AV Linux or not. As long as all these pieces fit and work together that's great, if something major changes I will adapt.. I've been doing this one way or another since 2008..

Posted: **Sat Apr 12, 2025 6:22 pm**

Computer has no sound jack port. But is done through hdmi. Quick system info will show that.
I get a port with a usb sound dongle. Included lsusb -t to show this in QSI report.
I change over using the dongle with the F6 key in alsamixer.
Adjust and have sound.
That is it. Dual booting with antiX 23.2 on here but I am letting MX handle grub and boot loading.
Just trying out new things is all.
is /etc/lsb-release supposed to have " " on line 2? Instead of Moeshka?
I haven't read over the whole thread yet.
apt upgrade && apt dist-upgrade is already finished.
Pretty much a fresh install.
Live usb was made with antiX live usb maker.
dd is good enough for this scooter tramp.

at least i can write to it since antiX live and mx live saves changes on a live run

Posted: **Sat Apr 12, 2025 6:35 pm**

Ran update-pcids and seemed to fix lsb release problem

Code: Select all

$ inxi -S
System:
  Host: shop Kernel: 6.13.8-4-liquorix-amd64 arch: x86_64 bits: 64
    Desktop: Moksha v: 0.4.1.18446 Distro: MX_MOKSHA-23-RC2_x64 Out of Bodhi TBD
hary@shop:~

was wrong, Grub screen still says Debian,

Posted: **Sat Apr 12, 2025 6:50 pm**

AVLinux wrote: Sat Apr 12, 2025 2:43 pm @Aceediq
A lot to unpack there..

I don't recall the tty booting conversation, sorry.. Don't give me too much credit though I just know enough to be dangerous and 'Developer' is too big of a hat for me..

To be clear Moksha is not avoiding or rejecting Wayland at all, their fork of Enlightenment (E-17) simply has no Wayland-ready code in it. Wayland was an addition to later versions of Enlightenment and Bodhi serving a large amount of their users on older machines and hardware simply haven't addressed Wayland yet, so they aren't being stubborn about it because it hasn't even been on their radar yet. They have quite a few years to decide if and how they will address it. I can't foresee people who have put as much sweat and toil in something like Bodhi are just going to close shop and quit because of Wayland, I'm sure over time they will figure something out.

Also AV Linux is not leaving MX or becoming a Bodhi version so the Moksha Desktop Environment on it's own is not a determining factor as to whether there is an AV Linux or not. As long as all these pieces fit and work together that's great, if something major changes I will adapt.. I've been doing this one way or another since 2008..

this is better, I thought moksha had made an unchanging stance on the issue of adopting wayland, you prefer jack but look at the solid option you gave by allowing pipewire blossom on AVLinix

I assumed that AVLinux would remain on MX base nevertheless my comments about moksha were made known because no matter how solid mx is, using moksha as the mainstream DE on AVL (assumption) means future decisions by moksha would have an impact on us users of AVLinux

...it wasn't a tty coversation, it was your reply in another thread, not in the respin section, you kinda stated that you preferred tty because it allowed your to see the booting process...

Posted: **Sat Apr 12, 2025 7:20 pm**

rokytnji.1 wrote: Sat Apr 12, 2025 6:35 pm Ran update-pcids and seemed to fix lsb release problem
Code: Select all
$ inxi -S
System:
  Host: shop Kernel: 6.13.8-4-liquorix-amd64 arch: x86_64 bits: 64
    Desktop: Moksha v: 0.4.1.18446 Distro: MX_MOKSHA-23-RC2_x64 Out of Bodhi TBD
hary@shop:~
was wrong, Grub screen still says Debian,

Hi,

Thanks for kicking the tires! Yes this RC2 release had missing quotes in line 2 of lsb-release, that is now fixed. I'd be kind of interested in knowing how Moksha compares to antiX in RAM consumption.

Posted: **Sat Apr 12, 2025 9:00 pm**

Something I noticed as a part of installing MX Moksha - the kernel parameter 'quiet' is missing from the live session.

People new to Linux may feel a need to pay attention to it (at bootup), assuming they are getting a mass of 'errors' when it's actually just Linux being its 'normal talkative self'.

Posted: **Sun Apr 13, 2025 12:48 pm**

. I'd be kind of interested in knowing how Moksha compares to antiX in RAM consumption.

Will show you with firefox running since it consumes the ram.

Code: Select all

harry@shop:~
$  ps ax | head -2 ; sudo ps_mem.py
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:00 init [2]
[sudo] password for harry: 
 Private  +   Shared  =  RAM used	Program

128.0 KiB +  24.5 KiB = 152.5 KiB	sleep
140.0 KiB +  33.5 KiB = 173.5 KiB	run-parts
152.0 KiB +  30.5 KiB = 182.5 KiB	seatd
104.0 KiB +  82.5 KiB = 186.5 KiB	sh
116.0 KiB +  85.5 KiB = 201.5 KiB	apt-compat
196.0 KiB +  16.5 KiB = 212.5 KiB	gpm
216.0 KiB +  43.5 KiB = 259.5 KiB	init
224.0 KiB +  36.5 KiB = 260.5 KiB	anacron
312.0 KiB +  28.5 KiB = 340.5 KiB	acpid
292.0 KiB +  58.5 KiB = 350.5 KiB	cron
256.0 KiB + 189.5 KiB = 445.5 KiB	startup
396.0 KiB +  86.5 KiB = 482.5 KiB	dbus-launch
376.0 KiB + 120.5 KiB = 496.5 KiB	icewm-session
360.0 KiB + 145.5 KiB = 505.5 KiB	udevil
432.0 KiB +  98.5 KiB = 530.5 KiB	rpc.statd
520.0 KiB +  33.5 KiB = 553.5 KiB	rpc.idmapd
496.0 KiB +  94.5 KiB = 590.5 KiB	rpcbind
540.0 KiB + 161.5 KiB = 701.5 KiB	xcompmgr
164.0 KiB + 542.0 KiB = 706.0 KiB	saned (2)
484.0 KiB + 402.0 KiB = 886.0 KiB	avahi-daemon (2)
664.0 KiB + 335.5 KiB = 999.5 KiB	devmon
832.0 KiB + 277.0 KiB =   1.1 MiB	dbus-daemon (2)
820.0 KiB + 330.5 KiB =   1.1 MiB	desktop-session
832.0 KiB + 469.0 KiB =   1.3 MiB	getty (6)
  1.6 MiB +  20.5 KiB =   1.6 MiB	smartd
  1.7 MiB +  23.5 KiB =   1.7 MiB	sshd
  1.0 MiB + 764.0 KiB =   1.8 MiB	sudo (2)
  1.8 MiB + 120.5 KiB =   1.9 MiB	connmand
  1.5 MiB + 380.5 KiB =   1.9 MiB	bash
  1.8 MiB + 218.5 KiB =   2.1 MiB	bluetoothd
  2.5 MiB + 719.5 KiB =   3.2 MiB	cupsd
  3.1 MiB +  20.5 KiB =   3.2 MiB	udevd
  3.2 MiB +  15.5 KiB =   3.2 MiB	haveged
  2.7 MiB + 653.5 KiB =   3.4 MiB	at-spi-bus-launcher
  2.8 MiB + 634.5 KiB =   3.4 MiB	wpa_supplicant
  4.1 MiB + 472.5 KiB =   4.6 MiB	conky
  4.1 MiB + 546.5 KiB =   4.7 MiB	slimski
  4.2 MiB + 674.5 KiB =   4.8 MiB	pipewire-pulse
  5.6 MiB +   1.1 MiB =   6.7 MiB	pipewire
  3.6 MiB +   3.6 MiB =   7.2 MiB	volumeicon
  6.4 MiB +   1.4 MiB =   7.8 MiB	icewm
 12.0 MiB +   1.5 MiB =  13.5 MiB	wireplumber
 12.3 MiB +   4.0 MiB =  16.3 MiB	roxterm
 45.7 MiB +  23.2 MiB =  68.9 MiB	Xorg
681.6 MiB + 152.3 MiB = 834.0 MiB	firefox-esr (11)
---------------------------------
                          1.0 GiB
=================================

time to reboot

Posted: **Sun Apr 13, 2025 12:56 pm**

Not a big difference

Code: Select all

ary@shop:~
$ ps ax | head -2 ; sudo ps_mem.py
    PID TTY      STAT   TIME COMMAND
      1 ?        Ss     0:01 /sbin/init splash
[sudo] password for hary:
 Private  +   Shared  =  RAM used	Program

144.0 KiB +  22.5 KiB = 166.5 KiB	fusermount3
188.0 KiB +  21.5 KiB = 209.5 KiB	acpid
228.0 KiB +  31.5 KiB = 259.5 KiB	anacron
240.0 KiB +  59.5 KiB = 299.5 KiB	acpi_fakekeyd
240.0 KiB +  63.5 KiB = 303.5 KiB	agetty
296.0 KiB +  49.5 KiB = 345.5 KiB	cron
284.0 KiB +  77.5 KiB = 361.5 KiB	blkmapd
360.0 KiB +  55.5 KiB = 415.5 KiB	rtkit-daemon
304.0 KiB + 141.5 KiB = 445.5 KiB	x-window-manage
352.0 KiB + 104.5 KiB = 456.5 KiB	rpc.idmapd
428.0 KiB +  78.5 KiB = 506.5 KiB	rpc.statd
540.0 KiB +  14.5 KiB = 554.5 KiB	rpc.mountd
656.0 KiB + 201.5 KiB = 857.5 KiB	rpcbind
484.0 KiB + 502.0 KiB = 986.0 KiB	avahi-daemon (2)
832.0 KiB + 183.5 KiB =   1.0 MiB	xdg-permission-store
  1.0 MiB +  10.5 KiB =   1.0 MiB	ssh-agent
  1.0 MiB +  89.5 KiB =   1.1 MiB	speech-dispatcher
968.0 KiB + 277.5 KiB =   1.2 MiB	at-spi-bus-launcher
932.0 KiB + 319.5 KiB =   1.2 MiB	gvfsd-fuse
  1.0 MiB + 262.5 KiB =   1.3 MiB	at-spi2-registryd
  1.0 MiB + 288.5 KiB =   1.3 MiB	xdg-document-portal
  1.1 MiB + 205.5 KiB =   1.3 MiB	accounts-daemon
  1.2 MiB + 175.5 KiB =   1.4 MiB	upowerd
956.0 KiB + 504.5 KiB =   1.4 MiB	dbus
600.0 KiB + 874.0 KiB =   1.4 MiB	chronyd (2)
  1.1 MiB + 446.5 KiB =   1.5 MiB	gvfsd
  1.4 MiB +  96.5 KiB =   1.5 MiB	nfsdcld
984.0 KiB + 790.0 KiB =   1.7 MiB	sudo (2)
  1.4 MiB + 708.5 KiB =   2.1 MiB	systemd-logind
  2.1 MiB + 111.5 KiB =   2.2 MiB	smartd
  2.1 MiB +  69.5 KiB =   2.2 MiB	rsyslogd
  2.1 MiB + 490.5 KiB =   2.6 MiB	pipewire-pulse
  2.2 MiB + 536.5 KiB =   2.7 MiB	cupsd
  2.7 MiB +  98.5 KiB =   2.8 MiB	bash
  2.2 MiB + 686.5 KiB =   2.8 MiB	systemd-networkd
  1.8 MiB +   1.1 MiB =   2.8 MiB	enlightenment_fm
  2.2 MiB + 743.0 KiB =   2.9 MiB	lightdm (2)
  2.4 MiB + 511.5 KiB =   2.9 MiB	sd_espeak
  2.6 MiB + 525.5 KiB =   3.1 MiB	dbus-daemon (3)
  3.0 MiB + 154.5 KiB =   3.1 MiB	wpa_supplicant
  3.2 MiB +  21.5 KiB =   3.2 MiB	haveged
  2.7 MiB + 805.5 KiB =   3.5 MiB	cups-browsed
  3.4 MiB + 241.5 KiB =   3.6 MiB	polkitd
  3.2 MiB + 863.5 KiB =   4.0 MiB	xdg-desktop-portal
  4.1 MiB + 130.5 KiB =   4.2 MiB	systemd-udevd
  3.2 MiB +   1.5 MiB =   4.7 MiB	xdg-desktop-portal-gtk
  4.1 MiB +   1.3 MiB =   5.4 MiB	efreetd
  2.7 MiB +   2.9 MiB =   5.6 MiB	nmbd
  5.2 MiB + 449.5 KiB =   5.7 MiB	ModemManager
  6.2 MiB + 473.5 KiB =   6.6 MiB	udisksd
  6.0 MiB +   1.4 MiB =   7.4 MiB	pipewire (2)
  6.6 MiB +   1.2 MiB =   7.8 MiB	NetworkManager
  5.3 MiB +   5.4 MiB =  10.7 MiB	systemd (3)
 10.3 MiB + 635.5 KiB =  10.9 MiB	systemd-journald
  4.3 MiB +   7.9 MiB =  12.2 MiB	smbd (3)
 12.0 MiB +   1.7 MiB =  13.7 MiB
   unattended-upgr
 15.0 MiB +   3.6 MiB =  18.6 MiB
   wireplumber
 13.1 MiB +  11.7 MiB =  24.8 MiB
   polkit-gnome-authentication-agent-1
 20.9 MiB +  18.9 MiB =  39.9 MiB
   nm-applet
 43.6 MiB +   3.7 MiB =  47.3 MiB
   python3.11
 35.4 MiB +  13.6 MiB =  49.0 MiB
   Xorg
 51.1 MiB +   7.1 MiB =  58.2 MiB
   terminology
 70.3 MiB +   7.9 MiB =  78.2 MiB
   enlightenment
676.0 MiB + 133.5 MiB = 809.6 MiB
   firefox-bin (11)
---------------------------------
                          1.3 GiB
=================================
hary@shop:~
$

Posted: **Sun Apr 13, 2025 5:39 pm**

Nice! I'm pleasantly surprised! Moksha gives a lot in appearance without asking for much RAM. Thanks for taking time to share that info!

Posted: **Mon Apr 14, 2025 6:08 am**

AVLinux wrote: Sun Apr 13, 2025 5:39 pm Nice! I'm pleasantly surprised! Moksha gives a lot in appearance without asking for much RAM. Thanks for taking time to share that info!

I have been able to install avl moksha...

it was tasking and a conglomeration of different issues...

ventoy installs avl mxe 23.5 well but I have issues installing avl moksha and even @Freja extrox...so I switched to easy2boot, rufus worked but you can only have one iso...

ram issues, not sure yet...booted the laptop on avl mxe 23.5, all fine and good...alright, let's try out avl moksha and extrox...teeny tiny pandora like box...

@AVLinux your move from enlightenment to moksha, I would say is more impactful and more of a leap than from xfce to enlightenment, really, so a DE can be this robust, flexible and LIGHT?

@ylee2130 kudos

can there be a guide, video tutorial preferably on how to create themes or improving ui/ux for moksha?

@AVLinux I am not having icons on RC2, it can be fixable by installing iconpacks?

@AVLinux would we be having your concise but adjustable conky back? as functional as possible?

the quality of life using moksha is evident seriously...can't wait for an official release of AVL moksha

we should have a minimalistic and mature logo for the startup button

ubuntu's startup button and logo, for me, is the only standard

Posted: **Mon Apr 14, 2025 7:48 am**

@AVLinux I don't see available wifi on AVL moksha...I usually have to create the connection...is that a bug or moksha's way of doing things?

@ylee2130

Posted: **Mon Apr 14, 2025 12:56 pm**

@Aceediq

I'm having trouble keeping up..lol

First if you have no icons that is very odd and is not normal and yes there are several Icon themes installed. Moksha does not use Connman like Enlightenment does and you should have a Network Manager applet in your systray to connect to WiFi, are you sure you have a good download of the ISO?

As far as Moksha themes it is like Enlightenment and the themes are very complex pieces of software on their own and are nothing like theming XFCE4, KDE etc. It is not a trivial thing at all to create a Moksha theme. When you talk about 'improving UX/UI' you are 100% in the realm of opinion, and before making such observations look in the Package Manager, there are at least 20 maintained Moksha themes. Moksha is Moksha and it's beauty is that it doesn't look like everything else, if you don't like any of the existing themes and want unlimited choice then Moksha is probably not for you.

Posted: **Mon Apr 14, 2025 3:42 pm**

I've ran a simple ~/.conky.rc file in e17 years ago.

Have yet to try in Moshka . Just a conky-all or standard away.
Make your hidden file.
Make sure it is in startup.
Done.

Got other stuff like spammers on antiX forum to take of instead

Posted: **Tue Apr 15, 2025 6:51 am**

AVLinux wrote: Mon Apr 14, 2025 12:56 pm @Aceediq

I'm having trouble keeping up..lol

First if you have no icons that is very odd and is not normal and yes there are several Icon themes installed. Moksha does not use Connman like Enlightenment does and you should have a Network Manager applet in your systray to connect to WiFi, are you sure you have a good download of the ISO?

As far as Moksha themes it is like Enlightenment and the themes are very complex pieces of software on their own and are nothing like theming XFCE4, KDE etc. It is not a trivial thing at all to create a Moksha theme. When you talk about 'improving UX/UI' you are 100% in the realm of opinion, and before making such observations look in the Package Manager, there are at least 20 maintained Moksha themes. Moksha is Moksha and it's beauty is that it doesn't look like everything else, if you don't like any of the existing themes and want unlimited choice then Moksha is probably not for you.

you have trouble keeping up?

you doing a good job, that's why

the only other AV distro that can be compared to you is ubuntu studio, do you know how many developers are on the project? of course you should have trouble keeping up

for good though

as for having a good download of the ISO, if my downloaded ISO had issues, I don't think it will install at all...well, let me try the ISO live and see if the icons show...

and as for moksha's themes, what I am gunning for isn't too change the title icons or changes the edges to curves, what I want is more theme colour schemes, at least a used already wants a blue variant of the moksha themes, you've got AVLinux being stable on a lockdown, and personally, I don't think it's bad if there are incremental and non technical improvements like

- more colour options in moksha's themes
- being able to directly apply wallpapers of your choice from wherever they are in your file manager
- more uniform icons both in scale and looks
- options for start logo

and other little things...

@ylee2130

and I didn't know there were moksha themes in mxpi, AVL MXe didn't have, right? or we there enlightenment themes in mxpi too?

and as for the WiFi, I'd like to wait for a final release of AVL moksha before getting my hands dirty, I have other things I need to deal with with more priority...

Posted: **Tue Apr 15, 2025 8:52 am**

Aceediq wrote: Tue Apr 15, 2025 6:51 am
AVLinux wrote: Mon Apr 14, 2025 12:56 pm @Aceediq

I'm having trouble keeping up..lol

First if you have no icons that is very odd and is not normal and yes there are several Icon themes installed. Moksha does not use Connman like Enlightenment does and you should have a Network Manager applet in your systray to connect to WiFi, are you sure you have a good download of the ISO?

As far as Moksha themes it is like Enlightenment and the themes are very complex pieces of software on their own and are nothing like theming XFCE4, KDE etc. It is not a trivial thing at all to create a Moksha theme. When you talk about 'improving UX/UI' you are 100% in the realm of opinion, and before making such observations look in the Package Manager, there are at least 20 maintained Moksha themes. Moksha is Moksha and it's beauty is that it doesn't look like everything else, if you don't like any of the existing themes and want unlimited choice then Moksha is probably not for you.
you have trouble keeping up? you doing a good job, that's why

the only other AV distro that can be compared to you is ubuntu studio, do you know how many developers are on the project? of course you should have trouble keeping up for good though

as for having a good download of the ISO, if my downloaded ISO had issues, I don't think it will install at all...well, let me try the ISO live and see if the icons show...

and as for moksha's themes, what I am gunning for isn't too change the title icons or changes the edges to curves, what I want is more theme colour schemes, at least a used already wants a blue variant of the moksha themes, you've got AVLinux being stable on a lockdown, and personally, I don't think it's bad if there are incremental and non technical improvements like

- more colour options in moksha's themes
- being able to directly apply wallpapers of your choice from wherever they are in your file manager
- more uniform icons both in scale and looks
- options for start logo

and other little things...

Happy Birthday!

Well. yes for sure there are never enough hours in the day..

As far as coloring of themes that is one of the major differences between Moksha and Enlightenment and as far as colors Moksha is less flexible outside of it's theme. Enlightenment has an additional feature of palettes so for example if you have a GTK theme you like but not an exact matching Enlightenment theme you can at least change the regular Enlightenment theme palette to match your GTK theme and Moksha doesn't really allow this, there is a 'Color' setting but it is not really the same as using palettes. If you notice in my MX Moksha the Green-based GTK theme is different than in the @Senpai Bodhi Respin, this is because I've made customized a Skewaita GTK theme to match the skeumorphic look of Moksha. Anyway Bodhi maintains lots of themes but they are not easy to color and not easy to match with GTK themes and they have one guy (the_waiter) maintaining all the themes and coming up with new ones when time allows and it takes weeks to create a Moksha theme.

As far as Icons and the Start Logo I agree, many Icons are embedded in the Moksha theme and cannot be changed and will not match your selected Icon theme, this is simply a way Moksha differs from other DE's.

AV Linux has a few themes and palettes installed and there is more here:

https://bandshed.net/packages/AVL_MXe-2 ... /OPTIONAL/

Posted: **Wed Apr 16, 2025 4:12 am**

AVLinux wrote: Tue Apr 15, 2025 8:52 am
Aceediq wrote: Tue Apr 15, 2025 6:51 am
AVLinux wrote: Mon Apr 14, 2025 12:56 pm @Aceediq

I'm having trouble keeping up..lol

First if you have no icons that is very odd and is not normal and yes there are several Icon themes installed. Moksha does not use Connman like Enlightenment does and you should have a Network Manager applet in your systray to connect to WiFi, are you sure you have a good download of the ISO?

As far as Moksha themes it is like Enlightenment and the themes are very complex pieces of software on their own and are nothing like theming XFCE4, KDE etc. It is not a trivial thing at all to create a Moksha theme. When you talk about 'improving UX/UI' you are 100% in the realm of opinion, and before making such observations look in the Package Manager, there are at least 20 maintained Moksha themes. Moksha is Moksha and it's beauty is that it doesn't look like everything else, if you don't like any of the existing themes and want unlimited choice then Moksha is probably not for you.
you have trouble keeping up? you doing a good job, that's why

the only other AV distro that can be compared to you is ubuntu studio, do you know how many developers are on the project? of course you should have trouble keeping up for good though

as for having a good download of the ISO, if my downloaded ISO had issues, I don't think it will install at all...well, let me try the ISO live and see if the icons show...

and as for moksha's themes, what I am gunning for isn't too change the title icons or changes the edges to curves, what I want is more theme colour schemes, at least a used already wants a blue variant of the moksha themes, you've got AVLinux being stable on a lockdown, and personally, I don't think it's bad if there are incremental and non technical improvements like

- more colour options in moksha's themes
- being able to directly apply wallpapers of your choice from wherever they are in your file manager
- more uniform icons both in scale and looks
- options for start logo

and other little things...

Happy Birthday!

Well. yes for sure there are never enough hours in the day..

As far as coloring of themes that is one of the major differences between Moksha and Enlightenment and as far as colors Moksha is less flexible outside of it's theme. Enlightenment has an additional feature of palettes so for example if you have a GTK theme you like but not an exact matching Enlightenment theme you can at least change the regular Enlightenment theme palette to match your GTK theme and Moksha doesn't really allow this, there is a 'Color' setting but it is not really the same as using palettes. If you notice in my MX Moksha the Green-based GTK theme is different than in the @Senpai Bodhi Respin, this is because I've made customized a Skewaita GTK theme to match the skeumorphic look of Moksha. Anyway Bodhi maintains lots of themes but they are not easy to color and not easy to match with GTK themes and they have one guy (the_waiter) maintaining all the themes and coming up with new ones when time allows and it takes weeks to create a Moksha theme.

As far as Icons and the Start Logo I agree, many Icons are embedded in the Moksha theme and cannot be changed and will not match your selected Icon theme, this is simply a way Moksha differs from other DE's.

AV Linux has a few themes and palettes installed and there is more here:

https://bandshed.net/packages/AVL_MXe-2 ... /OPTIONAL/

will the AVL MXe themes work for AVL moksha?

how nerfed is the colours setting compared to palettes?

I would love if in YOUR SPARE TIME do a video tutorial showing how you tweaked the skewaita theme to your tastes...

I believe also that @ylee2130 could help to request that the waiter dev should out of the magnanimity of the moksha devs, do a tutorial or two showing how to create moksha themes too...

@AVLinux also when will AVL moksha's final version be coming out?

Posted: **Mon Apr 21, 2025 6:21 am**

Hello MX guys :)

Stefan here, Bodhi linux developer. Nice to meet you. I saw my nick name in relation to Moksha themes. Yes, I should make a tutorial about how to create Moksha themes. Frankly as AVL noted, it is very complex process. There are some tools but I mostly use Geany editor with edc syntax hilights. I have never created my own theme from scratch. Actually it is impossible. You need a theme skelet based on Moksha signals and basic shapes. I can mention raster (E lead dev) and his new theme. It took him more than 1 year! Anyway if you want some info @Aceediq , feel free to ask me on our discord channel. I will guide you...

Stefan

Posted: **Mon Apr 21, 2025 12:42 pm**

the_waiter wrote: Mon Apr 21, 2025 6:21 am Hello MX guys :)

Stefan here, Bodhi linux developer. Nice to meet you. I saw my nick name in relation to Moksha themes. Yes, I should make a tutorial about how to create Moksha themes. Frankly as AVL noted, it is very complex process. There are some tools but I mostly use Geany editor with edc syntax hilights. I have never created my own theme from scratch. Actually it is impossible. You need a theme skelet based on Moksha signals and basic shapes. I can mention raster (E lead dev) and his new theme. It took him more than 1 year! Anyway if you want some info @Aceediq , feel free to ask me on our discord channel. I will guide you...

Stefan

Hi Stefan! Great to have you here!

I need to clarify something I said in an earlier post.. As far as Moksha and GTK themes, Stefan works very hard on creating matching GTK themes for the various Moksha themes so it is better to start with a Moksha theme you like and then either use the provided matching GTK theme or add your own.. My earlier comments were in the context of if you go to a popular GTK theme site and randomly pick a theme (ie the Nord theme) you will probably not find a Moksha theme that matches all that well, but selecting a Moksha theme first and working from that angle will yield better results..

Posted: **Mon Apr 21, 2025 3:13 pm**

It is worth noting that Agustin J. Verdegal T wrote an article, E17: Create Your Own Custom Themes, which originally appeared in PCLinuxOS Magazine, Volume 51, April 2011. At one point, I altered it for Bodhi's usage (with permission). It used to be on our old wiki and available as part of our old E17 Guide, which could be read in full on our wiki and installed from our repos. One can find this Bodhi Guide on GitHub, for example, here. The page on creating your own e17 theme is located at bodhiGuide/E17/e17guideEN. Naturally this article is dated and the theme it uses as an example is no longer maintained nor in our repos. The basic ideas are the same tho for any theme.

This is a very intro level discussion of themes, tho as to fully cover the creation and customization of Moksha or Elementary/Enlightenment themes is a complex topic and could easily fill a mid-sized book.

Posted: **Sat May 17, 2025 3:38 pm**

@the_waiter @ylee2130 please don't be mad at me for not responding to your replies when I saw them, mentally, I just sunk...having the frustration on why is linux this difficult to personalize GUI wise?

developing a theme for a year? I joked that it may have been better to not even give details and just say that that was a senior devs task to get the job well done

I mean what?!?!?!

I have not solely undertaken the task of theming from scratch or from building blocks on windows but I think a years effort on windows theming and personalizations would yield more than a theme

at this point, I think linux has to develop some way of securing funds with a high level of certainty rather than expecting what's left of the goodness in people's heart without restricting access to linux...

and let me state it clearly, it is just the colours/shades I want to tweak nothing else, would I still need that much significant effort?

MX Linux Forum

MX Moksha "Out of Bodhi" Testing Release RC2

MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2

Re: MX Moksha "Out of Bodhi" Testing Release RC2