Responses to Coming changes in impending MX 25 release.

For interesting topics. But remember this is a Linux Forum. Do not post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.

No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.

Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.

You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
Message
Author
User avatar
asqwerth
Developer
Posts: 8027
Joined: Sun May 27, 2007 5:37 am

Re: Responses to Coming changes in impending MX 25 release.

#191 Post by asqwerth »

alcornoqui wrote: Sun Aug 10, 2025 1:57 pm Congrats to the team and community!

After reading the thread I have a few questions on upgrading. First, my recollection, mostly from asqwerth:
.....
And my questions:
....
Now, some of the machines don't have separate /home partition: Will the "Preserve /home" option work in that case? If not, what would you recommend doing?

And just to be sure, is it expected that most stuff works after a fresh install preserving /home or problems are frequent? Which are the most frequent?

Thanks for the great work, awesome distro!
Only answering these parts.

The last time I preserved /home that was in the root partition was an install of MX18 or 19. It worked fine.

I believe that if you choose this option, the installer will go through the process of manually deleting the contents of the whole partition except whatever is in /home, before writing (ie installing) MX25 contents into the said partition.

***I haven't done it since because I decided I had tons of disk space so could just create a new partition for the new MX install, then selectively copy over which ever parts of the old install's /home into the new install's /home. I understand @Stevo uses the "preserve home" method still. Perhaps he can confirm it still works fine.

Just beware that I have also seen mentions in this forum that if your /home was encrypted, it might not be so easy to preserve home during the install, though I don't really know if this is true or not.

As for whether stuff works after a fresh install preserving home, I think the main thing to consider would be whether there been a drastic change in Desktop environment version between old and new MX install? If so, the config files and settings may be very different so preserving them may lead to the new DE version in the new install not being set up properly.

Thus, since XFCE in MX23 is ver 4.20 while the latest XFCE is still merely a point release of 4.20, it should be ok to preserve home for MX XFCE.

However, since Plasma in MX23 is 5.++++ while MX25 will have Plasma 6, preserving home for MX KDE with PLasma 5 configs, may lead to some wonkiness in PLasma 6. But if you set your customisation in the Plasma 5 install back to as default as you can (themes, icons, plasma desktop theme, sddm theme, remove third party widgets/plasmoids) before you do an install which preserves /home, it should go much better.

Certainly, if you are running the Event Calendar plasmoid or Latte Dock in Plasma 5, remove/uninstall them first before the install that preserves home. These 2 do not work in Plasma 6, so having a config that tries to start these 2 things will likely crash your desktop when you log into your new install for the first time.


Similar issues will affect the usual user applications you use. But they mostly should work. And if they don't, it's pretty easy to reset the configs. Just close the app that's wonky, move the config files/folders to Trash (or rename them something else), then open your app. It should now be reset to default, and a clean new config file/folder created in your $HOME.


It tends to be harder to remove configs for the DE using graphical tools, because you are in the midst of its graphical environment while trying to delete parts of its configs. You would probably need to do it in terminal to be safe. Also, the DE config files are all over the place in $HOME, so it would be best to ask for forum help if you ever think this is something you need to do.


***NOTE: That's the reason I mainly copy over data/media from HOME, and do selective copying over of only SOME config files now. Less potential issues. I copy the $HOME/.mozilla folder for my Firefox, configs for geany, strawberry and qmplay2 (my media players) and some other apps. I tend not to copy over DE config files, and do the customisation of the new DE from scratch in the new install.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
FullScale4Me
Posts: 1123
Joined: Fri Jan 08, 2021 11:30 pm

Re: Responses to Coming changes in impending MX 25 release.

#192 Post by FullScale4Me »

alcornoqui wrote: Sun Aug 10, 2025 1:57 pm
Regarding UEFI vs BIOS, does the installer offer a choice or do we have to do some previous partitioning in a machine that is UEFI capable but is currently partitioned/formatted for BIOS? I seem to remember some hand-holding by the installer but I'm not sure. What I know is some of my machines boot to UEFI and some don't, and again, I'd like to make sure to select UEFI if possible this time.

I've checked https://mxlinux.org/wiki/system/uefi/ and the manual but still not fully sure...
A lot of how the installation flows (BIOS vs UEFI) depends on how the PC firmware is set up. A UEFI installation will boot in UEFI *mode* until something goes wrong. Now *if* the PC has CSM aka Legacy/UEFI enabled a partially broken UEFI installation will boot in MBR/BIOS mode.

If the PC was set up with MX Linux in UEFI Mode, there will be an EFI/ESP partition in addition to the Root / partition. Boot the PC with an MX Linux USB. At the blue boot screen in the lower left will show *UEFI* if that is the boot mode. See Below.

Image

The very last line in Quick System Info is 'Boot Mode: UEFI'. If the PCs hard drive is NOT booting in CSM Mode, these two should be the same.

The installer tries to detect the Boot Mode and picks a Grub installation mode based on what it detects. Most times it gets it right. There are Grub choices offered (see below) during installation: MBR, PBR and ESP. The ESP choice would be for the UEFI installation mode. Likewise, the MBR is for the BIOS, aka Legacy.

If the PC has multiple disks, there is a [small] potential (if an old PCs disk has been added to a new PC) for the installer to get BOTH the Boot Mode and the correct ESP/EFI partition wrong. Think of the old disk (Windows7/Vista) as having user data in addition to the MX Linux disk Home folder.

Image

Boot with an MX Linux USB, run GParted and TAKE GOOD NOTES. Change the Disk Partition Labels for clarity. Ex: change 'ESP' to 'ESP-oldDisk'. Also In GParted go into the View menu and check Device Information. Then flip thru the disks in the pulldown on the upper right to get the Device Information info (even select & copy) text.

Below you can see where I made changes to the default root partition labels; usually 'root MX23'.

Image

One caution - if Dual Booting with Windows, do NOT mix BIOS and UEFI booting. Supporting it is a VERY difficult matter. [1]

1) In the Windows search bar type msinfo32. Scroll to Boot Mode. If it says Legacy, it is in BIOS aka MBR mode.
Michael O'Toole
MX Linux facebook group moderator
Dell OptiPlex 7050 i7-7700, MX Linux 23 Xfce & Win 11 Pro
HP Pavilion P2-1394 i3-2120T, MX Linux 23 Xfce & Win 10 Home
Dell Inspiron N7010 Intel Core i5 M 460, MX Linux 23 Xfce & KDE, Win 10

rambo919
Posts: 248
Joined: Sat Sep 24, 2022 1:32 pm

Re: Responses to Coming changes in impending MX 25 release.

#193 Post by rambo919 »

When it comes to UEFI.... just say nay.

But being serious if you boot UEFI... my impression is the kernel being signed only matters if you enable secure boot so you can boot with any kernel if you just don't enable it?

alcornoqui
Posts: 3
Joined: Wed Aug 08, 2018 8:34 am

Re: Responses to Coming changes in impending MX 25 release.

#194 Post by alcornoqui »

Many many thanks @FullScale4Me & @asqwerth for your detailed explanations, they help me a lot!

I should have provided more info, like all 7 machines are Xfce (for the /home needs), only one dual boot (for the UEFI/boot needs), etc., but your answers are more than enough to get me (and surely others) going, so I won't ask further questions now.

I'll gather the info in the next days/weeks and make sure to take good notes when the time comes. Thanks again, you're a helpful and savvy bunch!

alcornoqui
Posts: 3
Joined: Wed Aug 08, 2018 8:34 am

Re: Responses to Coming changes in impending MX 25 release.

#195 Post by alcornoqui »

rambo919 wrote: Mon Aug 11, 2025 3:14 am When it comes to UEFI.... just say nay.

But being serious if you boot UEFI... my impression is the kernel being signed only matters if you enable secure boot so you can boot with any kernel if you just don't enable it?
Thanks lol, but I've made up my mind already... And secure boot is not a problem either. Cheers!

User avatar
debianix
Posts: 185
Joined: Fri May 31, 2024 4:03 pm

Re: Responses to Coming changes in impending MX 25 release.

#196 Post by debianix »

Adrian wrote: Sun Aug 10, 2025 1:01 am
debianix wrote: Sun Aug 10, 2025 12:38 am As a KDE user, who used sysV and X11 all the time with MX23, is there a way i can find out if systemd and Wayland with MX25 KDE will work for my use case, other than trying it out and „learn the hard way“ that it does not? :-)
Legitimate questions, for X11 it's just a matter of a switch at the log in, and I think it's going to remember the last selection, so it's super easy.
For syvinit it's a bit more complicated because it's a bit harder to switch the running init system, but I think we should be able to provide a how-to for that -- or if you don't even want to touch systemd (lest you feel impure) you can always install Xfce or Fluxbox flavor with sysvinit and just install KDE on top.

well my use case I woudl describe as the average linux user that wants a rock solid and stable system that is loyal and out of the way, but everything on ur fingertip when u need it. Thats what I have now with KDE MX23 and SysVinit... I used debian about 7 years or so and it used systemd, one day I had boot problems, and then I tried MX linux, the boot problems disappeared, but I cannot say if the problems were rooted in systemd or anything else... anyhow, I love MX Linux and love everything that makes my system more stable and snappy.... But Im not sure if thats the case with Wayland because I always hear that the development of wayland is not yet as far as it should be to be rock solid and reliable for every applications?

I have a dual monitor setup here..if that does matter?


my QSI:

Code: Select all

Snapshot created on: 20250123_2022
System:
  Kernel: 6.1.0-37-amd64 [6.1.140-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.1.0-37-amd64 root=UUID=<filter> ro nosplash
    resume=UUID=<filter> resume_offset=626688
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_KDE_x64 Libretto May
    19 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: B560M DS3H V2 serial: <superuser required> UEFI: American
    Megatrends LLC. v: F11 date: 12/19/2023
CPU:
  Info: model: 11th Gen Intel Core i7-11700 bits: 64 type: MT MCP arch: Rocket Lake gen: core 11
    level: v4 note: check built: 2021+ process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
    microcode: 0x64
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 640 KiB
    desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 4351 high: 4646 min/max: 800/4800:4900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 4530 2: 4589 3: 4581 4: 4557 5: 4589 6: 4594 7: 4580 8: 4610
    9: 4615 10: 4594 11: 4528 12: 4600 13: 4646 14: 800 15: 4592 16: 4623 bogomips: 79872
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: indirect_target_selection mitigation: Aligned branch/return thunks
  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 mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: Enhanced IBRS
  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; PBRSB-eIBRS: SW
    sequence; BHI: SW loop, KVM: SW loop
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 23 WKS-XL [Radeon PRO W6600] vendor: Dell driver: amdgpu v: kernel
    arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: DP-1,DP-2 empty: DP-3,DP-4 bus-ID: 03:00.0 chip-ID: 1002:73e3
    class-ID: 0300
  Device-2: AIRHUG 02 type: USB driver: uvcvideo bus-ID: 3-4:4 chip-ID: 2f9d:1101 class-ID: 0e02
    serial: <filter>
  Device-3: RODE Microphones RØDE VideoMic GO II type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4:2 chip-ID: 19f7:001c class-ID: 0300
    serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1354x381mm (53.31x15.00")
    s-diag: 1407mm (55.38")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left model: AOC AG275QZN serial: <filter>
    built: 2024 res: 2560x1440 hz: 240 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400
  Monitor-2: DP-2 mapped: DisplayPort-1 pos: right model: AOC AG275QZN serial: <filter>
    built: 2024 res: 2560x1440 hz: 240 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400
  API: OpenGL v: 4.6 Mesa 25.0.7-2~mx23ahs renderer: AMD Radeon Pro W6600 (radeonsi navi23 LLVM
    15.0.6 DRM 3.49 6.1.0-37-amd64) direct-render: Yes
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel bus-ID: 3-2:2 pcie: gen: 4
    chip-ID: 0d8c:0014 speed: 16 GT/s class-ID: 0300 lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: C-Media Audio Adapter (Unitek Y-247A) type: USB
    driver: cmedia_hs100b,snd-usb-audio,usbhid
  Device-3: RODE Microphones RØDE VideoMic GO II type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4:2 chip-ID: 19f7:001c class-ID: 0300
    serial: <filter>
  API: ALSA v: k6.1.0-37-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: 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: 3000 bus-ID: 06:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 3.17 TiB used: 1.82 TiB (57.5%)
  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 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 47.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung model: SSD 970 EVO Plus 2TB size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 42.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 60.1 scheme: GPT
Partition:
  ID-1: / raw-size: 68.34 GiB size: 66.72 GiB (97.62%) used: 37.52 GiB (56.2%) fs: ext4
    dev: /dev/dm-0 maj-min: 253:0 mapped: luks-<filter>
  ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 281.8 MiB (29.0%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-3: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%) used: 288 KiB (0.0%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:2
  ID-4: /home raw-size: 861.14 GiB size: 846.54 GiB (98.31%) used: 271.25 GiB (32.0%) fs: ext4
    dev: /dev/dm-2 maj-min: 253:2 mapped: luks-<filter>
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A gpu: amdgpu temp: 53.0 C mem: 56.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 1436
Repos:
  Packages: 3288 pm: dpkg pkgs: 3265 libs: 1766 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 23
  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://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb https://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/syncthing.list
    1: deb https://apt.syncthing.net/ syncthing stable
Info:
  Processes: 392 Uptime: 11m wakeups: 1 Memory: 31.24 GiB used: 4.71 GiB (15.1%) Init: SysVinit
  v: 3.06 runlevel: 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

User avatar
Adrian
Developer
Posts: 9164
Joined: Wed Jul 12, 2006 1:42 am

Re: Responses to Coming changes in impending MX 25 release.

#197 Post by Adrian »

If Wayland doesn't work well for you in SDDM (login stage) you can select "Xorg" and that's it. I wish people would try things before theorizing about what might go wrong. If you do have a real problem, not a virtual one, then yes, there's a simple solution, you just need to change that once at the login prompt.

User avatar
tascoast
Posts: 520
Joined: Sat Aug 06, 2011 4:58 am

Re: Responses to Coming changes in impending MX 25 release.

#198 Post by tascoast »

As for the screensaver, yup that is a buggy one. But, if you install xscreensaver it rocks! zero issues that I have seen.

I am not saying xfce is faultless, it has issues - as do ALL DE's - but pound for pound ... I prefer xfce over anything I have found.
I agree and add xscreensaver.

A primary issue is just knowing lock-screen is working for security, as expected?
Inspiron 15 5000-5593- (i7-1065G7) MX 23..2 AHS/MX-21//W10 - Lenovo ThinkCentre A58 4GBRAM (64-bit), MX-23.2/MX21.3./antiX 23/Mint 21.3, Ubuntu 22.04.4, openSUSE Tumbleweed,

User avatar
debianix
Posts: 185
Joined: Fri May 31, 2024 4:03 pm

Re: Responses to Coming changes in impending MX 25 release.

#199 Post by debianix »

@Adrian thank u very much for ur help. I will try it. Sorry, to me it seemed as MX25 KDE will be only available with Wayland..

User avatar
Adrian
Developer
Posts: 9164
Joined: Wed Jul 12, 2006 1:42 am

Re: Responses to Coming changes in impending MX 25 release.

#200 Post by Adrian »

debianix wrote: Wed Aug 13, 2025 1:44 pm @Adrian thank u very much for ur help. I will try it. Sorry, to me it seemed as MX25 KDE will be only available with Wayland..
*sigh*
The KDE iso will default to wayland sessions. X11 sessions are also included.
It's a simple toggle.

Post Reply

Return to “General”