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: 8015
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: 1119
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!

Post Reply

Return to “General”