MX 25 Beta 1 Feedback thread

[siamhie]

@fehlix I booted over to my MX-25 XFCE beta ISO and when I ran my nala upgrade, it didn't want to update hardinfo2.

Code: Select all

╔═[siamhie@xfce25-beta]═[01 10 2025]══════════════════════════════════════════════[~]
╚═> apt policy hardinfo2
hardinfo2:
  Installed: 1:2.2.10-1.1mx25+1
  Candidate: 1:2.2.10-1.1mx25+1
  Version table:
 *** 1:2.2.10-1.1mx25+1 100
        100 /var/lib/dpkg/status
     2.2.13-1~mx25+1 500
        500 http://la.mxrepo.com/mx/repo trixie/main amd64 Packages
     2.2.10-1 500
        500 http://deb.debian.org/debian trixie/main amd64 Packages
        

╔═[siamhie@xfce25-beta]═[01 10 2025]══════════════════════════════════════════════[~]
╚═> sudo nala upgrade
[sudo] password for siamhie:         
No Change: http://deb.debian.org/debian trixie InRelease
No Change: http://deb.debian.org/debian trixie-updates InRelease
No Change: http://security.debian.org/debian-security trixie-security InRelease
No Change: http://deb.xanmod.org trixie InRelease
No Change: http://la.mxrepo.com/mx/repo trixie InRelease
No Change: https://repo.librewolf.net librewolf InRelease
Fetched 0 Bytes in 0s (0 bytes/s)                                                    
All packages are up to date.

Aside from these two differences, both of my beta installs (XFCE/fluxbox) are running flawlessly.

[fehlix]

Going from memory here, not in 25 at the moment...

edit: I seem to have lost a line. In MX updater - preferences.
There is an option there to update the kernel automatically. Something automatically in any case. I believe it was ticked by default.

In "MX Updater" "[x] automatic upgrade", would do kind of what "basic upgrade" (i.e not "full upgrade") would do, so no new packages will be installed,
just existing packages get upgraded w/o any new dependency get installed.
And kernel upgrades would requires a new kernel packages. which won't be done by auto-upgrade and nor by "basic upgrade"

[fehlix]

@fehlix I booted over to my MX-25 XFCE beta ISO and when I ran my nala upgrade, it didn't want to update hardinfo2.

Yes, but this was already explained, not? Hmme not sure, still not fully clear to you?

[siamhie]

@fehlix I booted over to my MX-25 XFCE beta ISO and when I ran my nala upgrade, it didn't want to update hardinfo2.

Yes, but this was already explained, not? Hmme not sure, still not fully clear to you?

Both beta installs get updated in the terminal with nala (stock config).
What I'm pointing out is that fluxbox updated hardinfo2 and XFCE didn't update hardinfo2. That's all.
No confusion on my end.

[fehlix]

@fehlix I booted over to my MX-25 XFCE beta ISO and when I ran my nala upgrade, it didn't want to update hardinfo2.

Yes, but this was already explained, not? Hmme not sure, still not fully clear to you?

Both beta installs get updated in the terminal with nala (stock config).
What I'm pointing out is that fluxbox updated hardinfo2 and XFCE didn't update hardinfo2. That's all.
No confusion on my end.

Yes, as explained, hardinfo2 was not "upgraded" to a newer version, b/c you have used
"nala upgrade"
instead of
"nala full-upgrade", or "nala upgrade --full"
and that's the expected behaviour, for package upgrades, which require new dependencies get installed.

[i_ri]

fluxbox sysV iso
live usb maker
dd bootable usb the boot screen shows a line, Virtual box video

full-feature bootable usb boot screen does not have that line, Virtual box Video

[wdscharff]

Strange Behavior with Nvidia (Incl. Workaround)
I connected the second monitor three days after installation Nvidia driver.
a. At first, it wasn't recognized at all and was also disabled in the Nvidia Xserver settings. i activate it.
b. Upon reboot, the second monitor was displayed, but was only partially usable—not as a single, shared screen, but only as two separate ones. If you wanted to use it, you had to move the mouse over it and start the programs there. Simply moving it didn't work. This was a very unfortunate behavior that made it difficult to work effectively. No matter what settings you changed, nothing changed.
arandr also only recognized the monitor on which the mouse pointer was positioned, and different settings in the fluxbox startup file didn't change anything. Everything worked fine from MX 23 up to MX 19!
Workaround: Uninstalled and reinstalled Nvidia while both monitors were connected; it worked right away.
It still irritates me, though.

qsi now with nvidia

Code: Select all

Snapshot created on: 20250930_0943
System:
  Kernel: 6.16.9-1-liquorix-amd64 [6.16-8.1~trixie] arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: tsc
    avail: hpet,acpi_pm parameters: audit=0 intel_pstate=disable amd_pstate=disable
    BOOT_IMAGE=/boot/vmlinuz-6.16.9-1-liquorix-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Fluxbox v: 1.3.7 with: tint2 tools: avail: light-locker vt: 7 dm: LightDM v: 1.32.0
    Distro: MX-fluxbox_sysvinit_beta1_x64 Infinity September 21 2025 base: Debian GNU/Linux 13
    (trixie)
Machine:
  Type: Desktop System: Gigabyte product: B550M S2H v: N/A serial: <superuser required>
  Mobo: Gigabyte model: B550M S2H serial: <superuser required> uuid: <superuser required>
    BIOS: American Megatrends LLC. v: F15a date: 02/16/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 gen: 2 level: v3 note: check
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113) stepping: 0
    microcode: 0x8701034
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB L3: 64 MiB desc: 4x16 MiB
  Speed (MHz): avg: 2795 min/max: 2200/4673 boost: enabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 2795 2: 2795 3: 2795 4: 2795 5: 2795 6: 2795 7: 2795 8: 2795 9: 2795
    10: 2795 11: 2795 12: 2795 13: 2795 14: 2795 15: 2795 16: 2795 17: 2795 18: 2795 19: 2795
    20: 2795 21: 2795 22: 2795 23: 2795 24: 2795 bogomips: 182055
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection 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: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  Type: spec_rstack_overflow mitigation: Safe RET
  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; STIBP: always-on; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI driver: nvidia v: 555.42.02
    non-free: 550-570.xx+ status: current (as of 2025-04; EOL~2026-12-xx) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.0
    chip-ID: 10de:1c82 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.16 compositor: Picom v: 12.5 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 6400x2160 s-dpi: 139 s-size: 1169x400mm (46.02x15.75")
    s-diag: 1236mm (48.64")
  Monitor-1: DP-0 pos: right res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 109
    size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
  Monitor-2: HDMI-0 pos: primary,left res: mode: 3840x2160 hz: 60 scale: 100% (1) dpi: 140
    size: 697x392mm (27.44x15.43") diag: 800mm (31.48") modes: N/A
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm:
    drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.42.02 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 memory: 3.91 GiB
  Info: Tools: api: eglinfo,glxinfo gpu: nvidia-settings,nvidia-smi x11: xdriinfo, xdpyinfo,
    xprop, xrandr
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 10de:0fb9 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 07:00.4
    chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.16.9-1-liquorix-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.5 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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: TP-Link Archer T2U PLUS [RTL8821AU] driver: rtw88_8821au type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2.1:4 chip-ID: 2357:0120 class-ID: 0000
    serial: <filter>
  IF: wlan0 state: down mac: <filter>
  Info: services: NetworkManager,wpa_supplicant
Drives:
  Local Storage: total: 6.82 TiB used: 3.32 TiB (48.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 42.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 033
    scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: PSSD T7 size: 1.82 TiB block-size:
    physical: 512 B logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: SSD serial: <filter> scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1
    mode: 3.2 gen-1x1 tech: SSD serial: <filter> fw-rev: 0223 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1
    mode: 3.2 gen-1x1 tech: SSD serial: <filter> fw-rev: 0204 scheme: MBR
  ID-6: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 860 QVO 1TB size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1
    mode: 3.2 gen-1x1 tech: SSD serial: <filter> fw-rev: 0223 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 79.28 GiB size: 77.48 GiB (97.73%) used: 15.99 GiB (20.6%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
  Kernel: swappiness: 100 (default 60) cache-pressure: 50 (default 100) zswap: no
  ID-1: swap-1 type: zram size: 3.13 GiB used: 0 KiB (0.0%) priority: 100 comp: lz4
    avail: lzo-rle,lzo,lz4hc,zstd,deflate,842 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 45.8 C mobo: 34.0 C gpu: nvidia temp: 40 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 35%
Repos:
  Packages: 2427 pm: dpkg pkgs: 2416 libs: 1346 tools: apt, apt-get, aptitude, nala, synaptic
    pm: rpm pkgs: 0 pm: flatpak pkgs: 11
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/liquorix.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian trixie main
    2: deb-src [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian trixie main
  Active apt repos in: /etc/apt/sources.list.d/debian.sources
    1: deb http://deb.debian.org/debian/ trixie main  contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ trixie-security main  contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ trixie-updates  main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/fetch.sources
    1: deb http://ftp.ch.debian.org/debian/ trixie main
    2: deb https://mirror.plusline.net/debian/ trixie main
    3: deb https://de.mirrors.clouvider.net/debian/ trixie main
  Active apt repos in: /etc/apt/sources.list.d/mx.sources
    1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ trixie main  non-free
    2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ trixie ahs
Info:
  Memory: total: N/A available: 31.25 GiB used: 2.29 GiB (7.3%)
  Processes: 432 Power: uptime: 22m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.4 GiB
    services: upowerd Init: SysVinit v: 3.14 runlevel: 5 default: 5 tool: service
  Compilers: gcc: 14.2.0 Client: shell wrapper v: 5.2.37-release inxi: 3.3.38
Boot Mode: BIOS (legacy, CSM, MBR)

[Eadwine Rose]

Strange Behavior with Nvidia (Incl. Workaround)

My idea.. leave the monitor connected, then fully reinstall mx25. Don't keep stuff, so it is a fully clean install.
In display put the monitors in their correct spots, and select the primary screen.
Then install nvidia.

That way the whole system knows from the getgo there is a second monitor.

[wdscharff]

@Eadwine Rose

A complete reinstallation was unnecessary; my workaround worked just fine.
Completely uninstall the driver, unplug the computer, restart the computer with both monitors connected, and reinstall the Nvidia driver. It's significantly faster than a clean install, especially if you've already installed everything you installed in MX 23.
I'm testing my beta as a fully functional working installation, and aside from issues with Nvidia, everything's working fine for me.

[Eadwine Rose]

Ahhh ok, I guess I read too much into the irritated still bit, that something was still being annoying. My brain, wired a little different :) Glad that worked!