I have experimented with boot order, to the point of eliminating all but one boot method, with no success. How did you manage to load SuSe? I'm trying to install Debian. No luck with a Debian install image, no luck with a live image on a USB flash drive. And no luck even loading Winki3, which would be a step forward for me - did you use a USB device or a SATA DVD ROM? From the LEDs built into the USB flash and the USB DVD ROM, I can see that they are accessed but there seems to be something missing, causing a failure. In keeping with excellent software system design, that failure is not reported to the user - a silent error. Sure, the hex driver enumeration codes are displayed ("B4 hangup" anyone?), but there is no failure message for something as high level as boot failure. And not a single line of documentation at MSI for their UEFI BIOS. Not that a lot of this is actually MSI's doing, it is all AMI's bogus code, and I know what kind of hacks work at BIOS companies (I would rather do the work myself than hire one). But it is apparent that MSI couldn't even be bothered to properly customize it ("OEM String here").
Interestingly, the "set" command shows "path" set to ".;cd13b0a1:\efi\tools;cd13b0a1:\efi\boot;cd13b0a1:" where "cd13b0a1:" is the USB DVD ROM drive, but those directories do not exist. I think I will try wiping all CMOS data to clear the NVRAM and start over again.
In the meantime, since I have gotten zero traction with MSI, it looks like the board is getting closer to being shipped back to NewEgg and 1 star awarded to it. MSI's "solve it among yourselves" apparent attitude is not cutting it with me.