MX Moksha "Out of Bodhi" Testing Release RC2

[AVLinux]

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/

[Germ]

[kmathern]

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:~

[AVLinux]

@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..?

[FullScale4Me]

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

[AVLinux]

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..

[kmathern]

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.

[AVLinux]

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..

[Gabriel_M]

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

[AVLinux]

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.