AVLinux: Important finishing touches and differences

[Aceediq]

the qsi of the current rig

Code: Select all

System:
  Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.12-1-liquorix-amd64
    root=UUID=<filter> ro threadirqs quiet
  Desktop: Enlightenment v: 0.25.4 vt: 7 dm: LightDM v: 1.32.0 Distro: AVL_MXE_BASE-23.5_x64
    Greatest Hits October 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Hewlett-Packard product: HP EliteBook 8460p v: A0001D02
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Hewlett-Packard model: 161C v: KBC Version 97.4E serial: <superuser required>
    BIOS: Hewlett-Packard v: 68SCF Ver. F.67 date: 02/13/2018
Battery:
  ID-1: BAT0 charge: 37.7 Wh (94.7%) condition: 39.8/39.8 Wh (100.0%) volts: 12.5 min: 10.8
    model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: charging
CPU:
  Info: model: Intel Core i5-2520M bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  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: 2689 high: 2904 min/max: 800/2501 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 2494 2: 2904 3: 2869 4: 2492 bogomips: 19954
  Flags: avx 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: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  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
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0126 class-ID: 0300
  Device-2: Chicony Integrated HP HD Webcam type: USB driver: uvcvideo bus-ID: 1-1.4:4
    chip-ID: 04f2:b230 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: LVDS-1 model: LG Display LP140WH2-TLN2 built: 2009 res: 1366x768 hz: 60 dpi: 112
    gamma: 1.2 size: 310x174mm (12.2x6.85") diag: 355mm (14") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 3.3 Mesa 24.2.2-1~mx23ahs renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Hewlett-Packard 6
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
  API: ALSA v: k6.6.12-1-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 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
    port: 4060 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 24:00.0 chip-ID: 8086:0085 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: HP Broadcom 2070 Bluetooth Combo type: USB driver: btusb v: 0.8 bus-ID: 1-1.6:5
    chip-ID: 03f0:231d class-ID: fe01
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 1.2 lmp-v: 2.1
    sub-v: 4203 hci-v: 2.1 rev: 132
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 298.09 GiB used: 55.28 GiB (18.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD032 size: 298.09 GiB block-size:
    physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 2F
    scheme: MBR
Partition:
  ID-1: / raw-size: 39.06 GiB size: 38.15 GiB (97.67%) used: 12.5 GiB (32.8%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
  ID-2: /home raw-size: 247.07 GiB size: 242.13 GiB (98.00%) used: 42.78 GiB (17.7%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 11.96 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: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 61.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2387 libs: 1392 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/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 https://mirror.liquidtelecom.com/mxlinux/packages/mx/repo/ bookworm main non-free
    2: deb https://mirror.liquidtelecom.com/mxlinux/packages/mx/repo/ bookworm ahs
Info:
  Processes: 314 Uptime: 8m wakeups: 1 Memory: 7.66 GiB used: 2.24 GiB (29.3%) 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)

moksha trumps enlightenment when it comes to ui/ux @ylee2130

moksha DE pros:

- HIBERNATION WORKS ootb
- SUPERB ability to select a different wallpaper from user folders
- SUPERB connectivity ui, very similar to win 7 .
- SUPERB dialog box sizes, for example, the wifi password dialog box is well shaped, rectangular-like
- user can make changes or corrections to the wifi password dialog box before clicking connect AFTER CLICKING SHOW PASSWORD
- tasks setting/configuration is BEEFED UP in comparison to that of enlightenment
- overall better jgmenu onmoksha, for example, you can change moksha themes from the jgmenu


moksha DE cons:

- changing the shelf to invisible results in an ERROR DIALOG BOX that user can close but editing the contents on the invisible shelf bring up that error
- wifi disconnects more often than on enlightenment at about ~8ft and it doesn't reconnect easily...even, when the hotspot device is in the same vicinity, connection isn't as stable as enlightenment
- logging out of moksha RESETS desktop customizations, wallpaper, everything to that of a fresh install
- LACKS per app volume control on app titlebar, enlightenment has this
- arranging/moving gadgets/contents on the shelf is more GLITCHY than on enlightenment
- on qpwgraph, doing a livestream record setup using chrome and audacity/tenacity, when I connect chrome directly to audacity cutting out pipewire middleman, it resets, which causes audio from my environment to taint the audacity/tenacity recording)





enlightenment DE pros:

- changing the shelf to invisible works well
- MORE STABLE wifi connectivity
- logging out doesn't reset desktop customizations
- SUPERB per app volume control on app titlebar
- arranging/moving gadgets/contents on the shelf is more STABLE


enlightenment DE cons:

- LACKING ability to select a different wallpaper from user folders
- LACKING superb connectivity ui...I believe this can be corrected shipping/installing cmst gui @AVLinux
- BAD dialog boxes sizes, for example, the wifi password dialog box is square-like
- user CANNOT make changes or corrections to the wifi password dialog box AFTER CLICKING SHOW PASSWORD
- DE ERRORS that user can either recover from or restart from


not confirmed but it seems moksha can't handle disk being full or almost full as I get an initramfs message which led me to distro hop, loose data and check out other distros...@anticapitalista I checked out antiX with WMs and the memory usage difference on cold boot between it and avlinux is less than 150mb, would it be a hurdle to desystemD moksha or enlightenment and make it an option on antiX?

since I do screen recording the lack of fine desktop scaling, at least as good as enlightenment/moksha is what ejected me from antiX (simplescreenrecorder refuses to record the screen on any other scaling on xfce and the likes, I haven't tried that on kde but on enlightenment/moksha, it works) but the no systemd/elogind is alluring...unfortunately, I am too focused of an individual to keep to OSes, though I installed antiX vlc offering, I attempted to desystemd avlinux using antiX repos and I had to do a fresh install

@ylee2130 thanks for fixing the window resizing bug I couldn't reply on that thread due to work constraints and the reply on the effort from your devs on theme development is still quite shocking

[Aceediq]

I am not out for anyone, if my post comes off like that, that wasn't intended

[AVLinux]

Hi,

You've identified some 'need-to-grow' areas for sure. A great majority of them are within the DE's themselves and not solvable by me at all. Your time and attention will be much better spent asking the respective DE devs. To be clear Bodhi has it's own forum and Discord channel and it's developers may rarely check in here but they are also busy right now with Bodhi Linux 8 in development. You won't get meaningful bug-reporting time with them here. I take their work as-is and build ISO's, I'm not a developer or a DE Coder. Dialogs and any other part of the DE are far above my pay grade and infinitely farther above my abilities.

As far as networking Enlightenment uses Connman and it's systray doesn't support 'libappindicator' apps so 'Network Manager' is not easy to use in a convenient way. I did some testing and looking into it and the best answer for E is still to ship CMST which I do. Moksha uses Network Manager like most regular DE's do so it is familiar and more intuitive to use. For most people either work fine and your actual hardware and chipsets may behave differently with either, connectivity is much more a hardware/firmware/Kernel driver thing than a DE thing anyway.

As far as the wallpaper thing, really? Is it that important? They work how they work. Both DE's take the image and convert it to an .edj file and the import automatically resizes and duplicates your image in various resolutions. When you select an image in E/Moksha and make it a wallpaper you're not simply viewing the jpg, png or whatever, you're now looking at an edj file and that's why there is a difference. It is true Moksha has taken the trouble to patch Thunar so you can select an image file and convert it from Thunar BUT... you need to install 'thunar-bl' not MX's Thunar package. Enlightenment's developer is brilliant and tends to over-engineer things, the wallpaper thing is a good example.. My advice.... live with it (or don't) it won't be changing..

Hibernation is often more of a kernel thing than a DE thing, I never use it, I never test it I have too many other things to pay attention to.

If logout on Moksha is losing your settings than something unplanned has gone wrong, I have one dedicated Moksha laptop for testing and logout works as expected, there are no other reports of this and a fair number of people have tried out MX Moksha, more info is needed how to reproduce this.

Lastly, I've run out of time.. I use the init system the DE is designed with and designed for, I've said many times I have absolutely no opinion or favourites when it comes to init systems I simply use the one recommended to work best with the DE at hand. I'm not a political Linux person at all so I have no strongly held beliefs pulling me away from the established status quo things that are widely accepted (although Wayland may test this...lol). Both E and Moksha can have their system actions modified to work with other inits but I see no reason to change them and make more troubleshooting work for myself. I actually agree with you that antiX and Moksha could be a powerful match-up if the antiX folks took some time to make the system mods. Perhaps you would like to try Artix Linux a systemd-less Arch derivative that provides Moksha as an installable DE option?

I'm just a part-time musician who enjoys Linux and wants to design a system for my needs first.. From there I share it because it's not that hard to share and I assume other people may find it useful and benefit from what I've already done. I think this is a key puzzle piece you may be missing. I don't build AVL to order, I build it for myself and sure when I share it I throw in some extras because I'm knowledgeable about music production on Linux and I want it to be useful.. But that's as far as it goes.

Projects like MX are far less 'self-centered' and work very hard to make a product as useful to as many people as possible and as a fairly large team they excel at it and are extremely User-driven. That is the major difference and I think your many posts about your dislikes and missing things are kind of guided by the hope that AVL is equally User-driven. For multiple reasons it is quite different in this regard.

[Aceediq]

Hi,

You've identified some 'need-to-grow' areas for sure. A great majority of them are within the DE's themselves and not solvable by me at all. Your time and attention will be much better spent asking the respective DE devs. To be clear Bodhi has it's own forum and Discord channel and it's developers may rarely check in here but they are also busy right now with Bodhi Linux 8 in development. You won't get meaningful bug-reporting time with them here. I take their work as-is and build ISO's, I'm not a developer or a DE Coder. Dialogs and any other part of the DE are far above my pay grade and infinitely farther above my abilities.

As far as networking Enlightenment uses Connman and it's systray doesn't support 'libappindicator' apps so 'Network Manager' is not easy to use in a convenient way. I did some testing and looking into it and the best answer for E is still to ship CMST which I do. Moksha uses Network Manager like most regular DE's do so it is familiar and more intuitive to use. For most people either work fine and your actual hardware and chipsets may behave differently with either, connectivity is much more a hardware/firmware/Kernel driver thing than a DE thing anyway.

As far as the wallpaper thing, really? Is it that important? They work how they work. Both DE's take the image and convert it to an .edj file and the import automatically resizes and duplicates your image in various resolutions. When you select an image in E/Moksha and make it a wallpaper you're not simply viewing the jpg, png or whatever, you're now looking at an edj file and that's why there is a difference. It is true Moksha has taken the trouble to patch Thunar so you can select an image file and convert it from Thunar BUT... you need to install 'thunar-bl' not MX's Thunar package. Enlightenment's developer is brilliant and tends to over-engineer things, the wallpaper thing is a good example.. My advice.... live with it (or don't) it won't be changing..

Hibernation is often more of a kernel thing than a DE thing, I never use it, I never test it I have too many other things to pay attention to.

If logout on Moksha is losing your settings than something unplanned has gone wrong, I have one dedicated Moksha laptop for testing and logout works as expected, there are no other reports of this and a fair number of people have tried out MX Moksha, more info is needed how to reproduce this.

Lastly, I've run out of time.. I use the init system the DE is designed with and designed for, I've said many times I have absolutely no opinion or favourites when it comes to init systems I simply use the one recommended to work best with the DE at hand. I'm not a political Linux person at all so I have no strongly held beliefs pulling me away from the established status quo things that are widely accepted (although Wayland may test this...lol). Both E and Moksha can have their system actions modified to work with other inits but I see no reason to change them and make more troubleshooting work for myself. I actually agree with you that antiX and Moksha could be a powerful match-up if the antiX folks took some time to make the system mods. Perhaps you would like to try Artix Linux a systemd-less Arch derivative that provides Moksha as an installable DE option?

I'm just a part-time musician who enjoys Linux and wants to design a system for my needs first.. From there I share it because it's not that hard to share and I assume other people may find it useful and benefit from what I've already done. I think this is a key puzzle piece you may be missing. I don't build AVL to order, I build it for myself and sure when I share it I throw in some extras because I'm knowledgeable about music production on Linux and I want it to be useful.. But that's as far as it goes.

Projects like MX are far less 'self-centered' and work very hard to make a product as useful to as many people as possible and as a fairly large team they excel at it and are extremely User-driven. That is the major difference and I think your many posts about your dislikes and missing things are kind of guided by the hope that AVL is equally User-driven. For multiple reasons it is quite different in this regard.

I understand you, which is why I switched back to default AVL, as the cons of moksha AVL are bigger dealbreakers than the cons of default AVL, though I would rate moksha higher...

I just put it out here due to the new distro releases coming out across board, if they can be worked on time or over time, fine and good...

personally, if there weren't issues with logging out on moksha, I would have remained there and maybe the volume control on titlebars...but since you said you experience no logout issues, I would try moksha again on AVL 25 and if it still reoccurs there, I would do a video

as for init section, that was for antiX lead dev though

the biggest reason why I did this is so to make a suggestion that we might need to keep enlightenment as the default DE for a while, moksha being a variant...

[blast0id]

my only real gripe with moksha is the per app volume control... I'm not sure what or how to change the way it defaults to which "device" receives volume change input from the keyboard but it only seems to choose the right "device" or "app" part of the time... half the time when I roll the volume knob up or down on the keyboard i see a window stating the volume is changing, but the actually volume coming out of the speaker doesn't change. looking forward to the next release whenever/whatever that may be!