Just built new system (mobo: ASUS TUF B450-PLUS / cpu: AMD RYZEN 7 2700) and am trying to install MX-19. It starts to install then just gives me a bunch of errors and says it can't. I tried different flash drives and checked the md5sum but no luck. I did use the flash drive to install MX-19 to a 4 year old Dell Laptop. I had an old flash drive with MX-15-32-bit on it and that loaded and installed OK on the new system. I am also able to run a very old version of PartedMagic but not a new version. After trying various combinations in Secure Boot / CSM settings and getting nowhere (I tried everything that the admins at MX had me try and just got nowhere. So I took the computer in to a computer shop and they ran some diagnostic tests and didn't find anything. So they installed Win10 with no problems. But when they tried Linux they ran into the same things I did. Does anyone have any suggestions???

My suggestion is to tell us which error messages are issued, what exactly it can't, and which combinations in secure boot settings you have tried.
Optionally, you could unveil the meaning of CSM. Wikipedia gives me a few definitions, none of which seem to be related to installing an operating system.

Here is what I get:
It got to saving random seed then hung for a bit more than a minute then got this:
Last 10 lines of dmsg output:
>>>>>>>>>>>>>
Error: mount: mounting /dev/loop0 on /live/linux failed input/output error
[124.488608] printing_req_error: I/O error, dev sdb, sector 2048
[124.488608] Buffer I/O error on sdb1, logical block0, lost sync page write
[124.488618] Ext4-fs (sdb1): I/O error while writing superblock
[124.488626] Ext4-fs error (device sdb1): ext4_find_extent: 909: inode #86022: comm loop0: pblk 2129921: pblk2129921 bad header/extent: invalid magic -magic aff, entries 2062, max 45052(0), depth 2062(0)
[124.488641] print_req_error: I/O error, dev sdb, sector 2048
[124.488642] Buffer I/O error on dev /sdb1, logical block 0, lost sync page write
[124.488646] Ext4-fs (sdb1): I/O error while writing superblock
[124.488650] print_req_error: I/O error, dev loop0, sector 0
[124.488660] SQUASHFS error: squashfs_read_data failed to read block 0x0
[124.488661] squashfs: SQUASHFS error: unable to read squashfs_super_block
<<<<<<<<<<<<<
Kernel: 4.19.0-6_amd64

Fatal Error
Could not mount /live/boot-dev/antiX/linuxfs as a squashfs file system


I also tried antiX and got this:
Fatal Error
Could not find file antiX/linuxfs
Searcheddevices: /dev/sr0
Searched types: usb,cd
All block devices - and it lists all the block devices
then asks to power down or reboot

CSM is Compatibility Support Module:
Launch CSM: Auto / Enabled / Disabled
Boot Device Control: UEFI & Legacy OPROM / Legacy OPROM only / UEFI only
Boot from Network Devices: Ignore / Legacy only / UEFI driver first
Boot from Storage Devices Ignore / Legacy only / UEFI driver first
Boot from PCI-E Expansion Devices: Legacy only / UEFI drivers first

The ones I thought would work:
Launch CSM: I tried Auto and then Enabled
Boot Device Control: Legacy OPROM only
Boot from Network Devices: Legacy only
Boot from Storage Devices Legacy only
Boot from PCI-E Expansion Devices: Legacy only

Then just tried different combinations just out of frustration to see if anything would work.

This is pretty long, sorry.

I am afraid you have to say good-bye to that disk. Or the connector or the interface to which the disk is connected.
Or perhaps it's simply a bad contact.

CSM: Compatibility Support Mode. Legacy (MBR) mode for UEFIs.

1 members found this post helpful.

Try the MX-19.1 ahs version. It is supposed to support latest Ryzen unlike the 'standard' release.

"I am afraid you have to say good-bye to that disk. Or the connector or the interface to which the disk is connected.
Or perhaps it's simply a bad contact"

At that point it is working with the flash drive that I used to install to a laptop. And then yesterday a computer shop was able to install win10 on the computer.

anticapitalista:
"Try the MX-19.1 ahs version. It is supposed to support latest Ryzen unlike the 'standard' release."

I did try the ahs version and got this:

Waiting for dev to be fully populated ....
Configuring
Then a whole lot of errors & warnings & I/O errors
INIT: Id "5" respawning too fast: disabled for 5 minutes
INIT: No more processes left in this run level
INIT: Cannot execute "/sbin/getty"
(this was repeated several times)
INIT: Id "2" respawning too fast: disabled for 5 minutes
then I kept getting the same things for ID "3" and ID "6" and 1, 2, 4, 5. 3
and I just stopped it.

But I also sometimes get the message to contact BitJam at antiX or MX depending upon which version I am trying to install.

Sometime last night while trying to find maybe some clue on the internet, some post mentioned something about stopping Fast Boot. Is that something I should try?
I am going to contact Asus and see if they can provide a clue. Other than that I am at a complete loss.

Seems like a hardware issue

You should certainly deactivate Fast Boot. It might not solve the problem but you should do it anyway. Fast Boot is the Windows hibernate option and it causes massive corruptions in Linux.

I contacted Asus about the problem and got this response:
I have the same board as another person and they were able to install MX-19 on it. But she does have Win10 also. So why would that make a difference??

Asus always only officially supports Windows, but I have never seen a problem using their motherboards with Linux.
I don't have your board or processor though so can't give first-hand advice.

I do know that having CSM enabled can cause problems with Linux installs as can secure boot. I always disable both for my Linux machines.

How did this become "solved"?

You are correct in that this really did not get "solved". I still cannot load Linux on it. Even Ubuntu was not able to be loaded. Asus is hiding behind their answer that the board is only for Windows. So my fight is with Asus as I can't use the board as it is. So should I change it back to unsolved and let every one know how Asus handles my complaint?

Mark it unsolved.

I have 4 fully functional multiboot 64bit PCs with Asus motherboards as new as 2018. In Feb. I built one for someone else with Asus B450-F and 3200G Ryzen 3. I did find it necessary to use a 5.3 or newer kernel for everything to work right with the B450. Initially I didn't actually do any installation on either my own 2018 Asus B250M-C or the B450. I stuck a cloned SSD from a Gigabyte B250 in my Asus B250 to use until I migrated it to NVME, but before the switch to NVME, I did add a new Fedora 31 installation to the 8 OSes already on the cloned SSD. In the B450 I kept the two HDDs already in the case in which the owner's old Asus motherboard died and had very recently been upgraded to recent OS versions. When delivered the B450 had openSUSE Tumbleweed, Leap 15.1 and Leap 15.2beta working satisfactorily, and Debian Buster or Bullseye booting but with non-working X. This thread and this thread cover some of that build process.

IOW, IME, if you can't get an OS to install, you just haven't applied appropriate procedures. Both Bob's ROG STRIX B450-F GAMING and your TUF B450-PLUS GAMING provide the identical OS specification of either Win7 or Win10. Where there's a will, there's a way. In this case, given the need for 5.3 or newer kernel on Bob's B450, in my estimation the 4.19.67 MX 19.1 kernel is probably an obstacle you need to get around. If you must use a Debian derivative, I suggest Ubuntu 20.04 (with 5.4 kernel), which I already have installed on at least 4 PCs, including my Asus B250.

Where did you get the 20.04 version? The latest version I can see is 19.04.