installed MX 2.1 MX-21.1_x64 so slow [Solved]

[j2mcgreg]

@sisqonrw wrote:

do you mean that i have to try booting with systemd? would it be better?

if yes, what should i use 32 bit or 64. which version. xfce, fluxbox, ahs ...

Yes, you should try booting with SystemD. I can't swear it will definitely improve things but given your laptop's abysmal performance so far, it couldn't do any harm.

Your laptop dates from 2017 so you do not need the AHS version of MX as it is squarely aimed at machines that are less than a year old. You should be using the 64 bit version and for best results you should use either MX's Live USB Maker configured to use GPT partitioning or Rufus on Windows again with GPT partitioning. If you want to try Rufus you might ask a friend, family member or colleague if you can briefly borrow their Windows computer (provided you don't have one of your own). On Win 10 and 11 Rufus is a quick install and a just as quick removal after the fact. You would of course have to copy the MX ISO onto a second usb drive beforehand so that you can take it with you to the borrowed computer's site.

Edited to add that you should do a fresh install of MX.

[sisqonrw]

Start out with yes. If your system is 64 bit capable, then that one. If it is really new then ahs, otherwise just pick between what you like.. xfce, kde, fluxbox.

Personally I would stick with the 64bits standard xfce and see what that does booted in systemd first. You can always install anew later with what you prefer. Now you need to determine if systemd is the solution or not.

You can boot into it in the grub screen, selecting advanced, it should then be there if I recall correctly.

it is 2-3 years old and 64 bit. should i ahs or not?

[j2mcgreg]

@sisqonrw wrote:

it is 2-3 years old and 64 bit. should i ahs or not?

From your QSI that you posted earlier:

Code: Select all

Type: Laptop System: ASUSTeK product: X541UAK v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: X541UAK v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: X541UAK.303 date: 03/30/2017 

This tells us that your laptop's bios was activated on March 30, 2017, so your laptop is just over five years old and there will be no benefit derived from using the AHS version.

[pbear]

On Win 10 and 11 Rufus is a quick install and a just as quick removal after the fact.

No need to install, even. It's available as a portable.

[sisqonrw]

On Win 10 and 11 Rufus is a quick install and a just as quick removal after the fact.

No need to install, even. It's available as a portable.

i do not have Windows. I am using balena etcher

[j2mcgreg]

@sisqonrw wrote:

i do not have Windows. I am using balena etcher

Yes, and that's a red herring since you have also stated here that you have a working, albeit slow, install of MX 21 which means that MX's own Live USB Maker should be in play. In addition to my suggestion of asking a friend for help, you could also do a search for a Linux User Group in your area. Linux User Groups (LUGS) are dedicated to promoting the use of Linux and would be sure to help you out if asked kindly. I found this list of LUGS in Germany to help you get started:

https://libreplanet.org/wiki/Category:Groups_in_Germany

[Huckleberry Finn]

@sisqonrw since it's ok with antiX : No need to lose time, you can install that and then if you like any Desktop Environments (maybe Xfce) .. I'd do that.

[sisqonrw]

@sisqonrw since it's ok with antiX : No need to lose time, you can install that and then if you like any Desktop Environments (maybe Xfce) .. I'd do that.

sadly antix is also not ok. same problem. slow slow slow.

[Huckleberry Finn]

It really looks like a hardware problem (yes, I hear you say it's ok with other distros).

If you can do this: Take the Rams out, then re-seat . (Many times Mem-Test shows they're ok, and this solves such frustrating (also unknown freezing etc.) issues).

Also , the aforementioned GSmartControl is in Menu, you can start it on live session (of course if that doesn't take minutes to start/run ... Alternatively, you can first install it on another distro that works fine, then run on live session)

But, since it's the same on live session, it's probably something with the Rams, not the disk.

[pbear]

My advice would be different. Try booting with SystemD, as was suggested several times. If that works, hurray. If not, use whatever Linux version does work and move on.