MX-21 installation freezes after initial set-up
- Eadwine Rose
- Administrator
- Posts: 15163
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-21 installation freezes after initial set-up
I never got a tag, but know that I do not offer support via PM, folks. Your best bet is to google or find a manual, as I have no idea how to do that anymore, it was too long ago.
Well, y'all hit lucky, I have it written down. So this is what I had to do, that is all I can offer.
Go into the Advanced Mode (F7)
Go into ‘Secure Boot’ option under the Boot section
Select Windows UEFI mode, and go into Key Management
Delete Platform Key (PK) to disable secure boot. (Note: Do not delete other keys)
Save and restart to apply settings (F10) and boot with ‘secure boot’ disabled
To restore the key go to ‘Load Default PK’ and press enter, you can reload the default key there
https://www.technorms.com/45538/disable ... os-utility
Well, y'all hit lucky, I have it written down. So this is what I had to do, that is all I can offer.
Go into the Advanced Mode (F7)
Go into ‘Secure Boot’ option under the Boot section
Select Windows UEFI mode, and go into Key Management
Delete Platform Key (PK) to disable secure boot. (Note: Do not delete other keys)
Save and restart to apply settings (F10) and boot with ‘secure boot’ disabled
To restore the key go to ‘Load Default PK’ and press enter, you can reload the default key there
https://www.technorms.com/45538/disable ... os-utility
MX-23.6_x64 July 31 2023 * 6.1.0-38amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-21 installation freezes after initial set-up
First of, thank You, Eadwine Rose, for your input and help.
Unfortunately the outcome or result had been the same as before with one exception but first of to what I found out, experienced:
- Due to my old graphics card CSM can not be deactivated or better said, when deactivated on the very next reboot it will be activated again as the GTX 275 doesn't support UEFI.
- As for secure boot, the setting for Windows UEFI leads to a freeze as discribed in my posts before. Setting it to "Other OS" leads either to a reboot or a freeze. Why, I don't know.
So, now one might ask but where is the new?
As I had been so frustrated with the experiences I had to made, I downloaded other Linux distros and had no success with anyone of those which I tried and which had been based on AntiX or Arch but I could boot through to the installation desktop on one which is based on Debian/Ubuntu.
As I'm still very much a beginner when it comes down to Linux, I don't know where the differences are here but for now this unfortunately means that I will have to stick with the one which I could get booted to the installation desktop.
Once again, many thanks for all the suggestions and offered help!
Unfortunately the outcome or result had been the same as before with one exception but first of to what I found out, experienced:
- Due to my old graphics card CSM can not be deactivated or better said, when deactivated on the very next reboot it will be activated again as the GTX 275 doesn't support UEFI.
- As for secure boot, the setting for Windows UEFI leads to a freeze as discribed in my posts before. Setting it to "Other OS" leads either to a reboot or a freeze. Why, I don't know.
So, now one might ask but where is the new?
As I had been so frustrated with the experiences I had to made, I downloaded other Linux distros and had no success with anyone of those which I tried and which had been based on AntiX or Arch but I could boot through to the installation desktop on one which is based on Debian/Ubuntu.
As I'm still very much a beginner when it comes down to Linux, I don't know where the differences are here but for now this unfortunately means that I will have to stick with the one which I could get booted to the installation desktop.
Once again, many thanks for all the suggestions and offered help!
- linexer2016
- Posts: 733
- Joined: Thu Dec 15, 2016 8:15 pm
Re: MX-21 installation freezes after initial set-up
Yoshio, I empathise with your problem because I have to say that such issues have beset me with the latest iterations of debian/ubuntu derivates. You see, initially I had a terrible time getting MX21KDE installed from a liveusb which I had gone through all of the steps recommended here regarding burning different usbs' via differing methodologies. I still think the issue resides in graphics cards and in particularly the Nvidia drivers and how they interact with the most modern kernels. Have you tried (forgive me if you've already mentioned it as there's a bit of dialogue in this thread now) using one of the very oldest kernels?
Re: MX-21 installation freezes after initial set-up
Yoshio It's been my experience using ASUS motherboards that the quality has dropped like a rock. You either have one of the settings set wrong somewhere in the BIOS or a defective motherboard. Make sure all power settings are set to off because it causes freezes with Ryzen CPU's. If it's not that then you have the same problem I had which eventually showed up as a defective motherboard. In my case the freezing started after 11 months but I couldn't find the problem until 13 months which was conveniently for ASUS that it was out of warranty by then.
I use to like ASUS as I used them for all my computer builds, but I will never buy another ASUS product because of how I was treated by ASUS and that ASUS lied to me by falsely claiming the motherboard I had from them had RAID which it didn't have and the short life of the motherboard. I have since then use only Gigabyte motherboards and I recommend you do the same in the future.
I use to like ASUS as I used them for all my computer builds, but I will never buy another ASUS product because of how I was treated by ASUS and that ASUS lied to me by falsely claiming the motherboard I had from them had RAID which it didn't have and the short life of the motherboard. I have since then use only Gigabyte motherboards and I recommend you do the same in the future.
I am command line illiterate.
I copy & paste to the terminal. Liars, Wiseguys, Trolls, and those without manners will be added to my ignore list. 


- linexer2016
- Posts: 733
- Joined: Thu Dec 15, 2016 8:15 pm
Re: MX-21 installation freezes after initial set-up
Almost makes me glad my Asus motherboard is 8 years old :)
Re: MX-21 installation freezes after initial set-up
@linexer2016 In this thread @Huckleberry Finn recommended a similar approach but going for the latest kernel. As for now, I only tried both the MX-21_ahs_x64 and the MX-21_x64 as they are provided in the download. I didn't try any older or newer kernels. The only way to give this a try is to do so on my notebook. But it might be worth a try as now the two of you recommended a somewhat similar solution.
@Mauser A defect motherboard had been and still is one of my fears as well. In the very beginning of this thread I wrote about this and what I did to somewhat check it. Unfortunately, I couldn't find a way which completely nullifies the possibility of a broken motherboard, especially if it is something not obvious. For now I flashed the Bios itself and up-dated it to the latest version and changed the CMOS battery.
For now I will give it one more try by checken for different kernels and see if this is doing the "trick". If not, I will have to install the Debian-Ubuntu "alternative" as buying a new graphics cards is out of my price range for now.
@Mauser A defect motherboard had been and still is one of my fears as well. In the very beginning of this thread I wrote about this and what I did to somewhat check it. Unfortunately, I couldn't find a way which completely nullifies the possibility of a broken motherboard, especially if it is something not obvious. For now I flashed the Bios itself and up-dated it to the latest version and changed the CMOS battery.
For now I will give it one more try by checken for different kernels and see if this is doing the "trick". If not, I will have to install the Debian-Ubuntu "alternative" as buying a new graphics cards is out of my price range for now.
Re: MX-21 installation freezes after initial set-up
To not leave this topic here without a final sort of sum-up even with the now available MX-21.1 revision of MX-Linux I had no success. By now I'm using another distro which is an independent on. Furthermore I tried many different distros and as a summary of all that I haven't been able to find any real similarities between those which worked and those which didn't. What I think I can say is that Arch based distros don't work in my current PC configuration as none of which I tried I could get to boot into live environment. Of the independent ones the results had been mixed, some worked, some didn't. The same goes for Debian based distros.
I then tried to "specify" why some work and others not by checking the kernel but also here I couldn't find any logical connections or similarities. The distro is now running on the kernel 5.15.32-213.current. Other distros I tried also had a 5.15.XX kernel but I couldn't get them to boot into live environment with only one exception. Other kernels, be they higher or lower, didn't show any commonalities either.
What I could find had been the information about the support of the driver which I would need for my graphics card. The graphics card I have is only supported up to the nvidia driver version 340.108 and this is driver version seems to be supported only up to kernel 5.4 LTS. This makes me guess that the problem with being able to boot through to a live environment might have to do with the set-up of the Nouveau driver!?
As for now and to end this thread, I'm waiting for reasonable prices on the graphic card market and once I could buy a new card I will try again to get MX-Linux installed and running.
Many thanks for all the effort and help!
I then tried to "specify" why some work and others not by checking the kernel but also here I couldn't find any logical connections or similarities. The distro is now running on the kernel 5.15.32-213.current. Other distros I tried also had a 5.15.XX kernel but I couldn't get them to boot into live environment with only one exception. Other kernels, be they higher or lower, didn't show any commonalities either.
What I could find had been the information about the support of the driver which I would need for my graphics card. The graphics card I have is only supported up to the nvidia driver version 340.108 and this is driver version seems to be supported only up to kernel 5.4 LTS. This makes me guess that the problem with being able to boot through to a live environment might have to do with the set-up of the Nouveau driver!?
As for now and to end this thread, I'm waiting for reasonable prices on the graphic card market and once I could buy a new card I will try again to get MX-Linux installed and running.
Many thanks for all the effort and help!
Re: MX-21 installation freezes after initial set-up
Just
on any distro it boots and please post within code tags using this icon </>
Also I wish you tried 21.1 Ahs that has 5.16 by default (... yes I know you tried 21.1 MX and 21 Ahs )
Code: Select all
inxi -Fxxxza
Also I wish you tried 21.1 Ahs that has 5.16 by default (... yes I know you tried 21.1 MX and 21 Ahs )
You do not have the required permissions to view the files attached to this post.
Re: MX-21 installation freezes after initial set-up
Hey Huckleberry Finn,
I will try the 21.1 Ahs right after this post and see if I can get it booted into live environment.
Right now I'm post from my installed distro and here is the result for the inxi -Fxxxza command:
I will try the 21.1 Ahs right after this post and see if I can get it booted into live environment.
Right now I'm post from my installed distro and here is the result for the inxi -Fxxxza command:
Code: Select all
System:
Kernel: 5.15.32-213.current arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: initrd=\EFI\com.solus-project\initrd-com.solus-project.current.5.15.32-213
root=PARTUUID=612d928f-339c-49ba-9c80-6a0d60960351 quiet loglevel=3
splash systemd.show_status=false rw radeon.si_support=0
radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1
resume=UUID=1c3edf01-942b-410e-833f-7f8bb264e206
Desktop: Budgie v: 10.6.1 info: budgie-panel, plank wm: budgie-wm
dm: LightDM v: 1.30.0 Distro: Solus 4.3
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING B550M-PLUS v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 2423
date: 08/10/2021
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3
family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2715 high: 4353 min/max: 2200/4650 boost: enabled
scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 2584 2: 4353
3: 2918 4: 3578 5: 2554 6: 2783 7: 2184 8: 2194 9: 2178 10: 2191 11: 2866
12: 2207 bogomips: 88637
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GT200b [GeForce GTX 275] driver: nouveau v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-1,DVI-I-2 empty: none
bus-ID: 07:00.0 chip-ID: 10de:05e6 class-ID: 0300
Display: x11 server: X.Org v: 1.20.14 compositor: budgie-wm driver: X:
loaded: nouveau unloaded: fbdev,modesetting,vesa alternate: nv gpu: nouveau
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
s-diag: 1055mm (41.54")
Monitor-1: DVI-I-1 pos: primary,left model: Idek Iiyama PL2530H
serial: <filter> built: 2019 res: 1920x1080 hz: 60 dpi: 90 gamma: 1.2
size: 544x303mm (21.42x11.93") diag: 623mm (24.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: DVI-I-2 pos: right model: Idek Iiyama PL2530H serial: <filter>
built: 2021 res: 1920x1080 hz: 60 dpi: 90 gamma: 1.2
size: 544x303mm (21.42x11.93") diag: 623mm (24.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
OpenGL: renderer: NVA0 v: 3.3 Mesa 21.3.8 direct render: Yes
Audio:
Device-1: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound Server-1: ALSA v: k5.15.32-213.current running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: JACK v: 1.9.14 running: no
Sound Server-4: PulseAudio v: 15.0 running: yes
Sound Server-5: PipeWire v: 0.3.50 running: no
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 8.67 TiB used: 1.24 TiB (14.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNVS500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: EDFK0N01
temp: 48.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Intenso
model: External USB 3.0 size: 3.64 TiB block-size: physical: 4096 B
logical: 4096 B type: N/A serial: <filter> rev: 5438 scheme: MBR
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate
model: ST330006 51AS size: 2.73 TiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: CC45 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 type: USB vendor: Intenso model: Alu Line
size: 29.69 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: <filter> scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 55.88 GiB size: 54.75 GiB (97.98%)
used: 23.92 GiB (43.7%) fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: /home raw-size: 11.01 GiB size: 10.78 GiB (97.86%)
used: 2.94 GiB (27.3%) fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 5.59 GiB used: 1024 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p1 maj-min: 259:1
Sensors:
System Temperatures: cpu: 45.5 C mobo: N/A
Fan Speeds (RPM): cpu: 1449 fan-2: 0 fan-3: 0
Power: 12v: N/A 5v: N/A 3.3v: 3.38 vbat: N/A
Info:
Processes: 315 Uptime: 4h 37m wakeups: 0 Memory: 31.33 GiB
used: 4.2 GiB (13.4%) Init: systemd v: 249 runlevel: 5 tool: systemctl
Compilers: gcc: 11.2.0 Packages: 1338 eopkg: 1298 lib: 388 flatpak: 20
snap: 20 Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.14
Re: MX-21 installation freezes after initial set-up
Till then (and off-topic) Why did you use these? Your card is Nvidia.
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1