Solved Unable to install any linux distribution on ASUS motherboard

[CaffeineAddict]

If I was dual booting Linux/Windows I would use a distro that supported secure boot, so I don't have to go into the BIOS and enable/disable every time I wanted to change the OS.
In fact I am doing it this way now.

Not an option for Debian based distros, including Ubuntu, Kali, Debian etc. because current shim was blacklisted my MS and the key is in every UEFI firmware.

New shim will be available in Trixie, and that's not even for sure.

 

[dos2unix]

According to Ubuntu Docs, they support it.

UEFI/SecureBoot - Ubuntu Wiki

Given their partnership with Microsoft, I would be amazed if M$ disabled theirs.

 

[CaffeineAddict]

According to Ubuntu Docs, they support it.

UEFI/SecureBoot - Ubuntu Wiki

Given their partnership with Microsoft, I would be amazed if M$ disabled theirs.

On architectures or systems where pre-loaded signing certificates from Microsoft are not available or loaded in firmware, users may replace the existing signatures on shim or grub and load them as they wish, verifying against their own certificates imported in the system's firmware.

Except not in all cases.

Debian also supports secure boot, they also have wiki, yet I'm not able to secure boot because my mobo blacklisted it and provides no firmware updates.

 

[dos2unix]

Debian also supports secure boot, they also have wiki, yet I'm not able to secure boot because my mobo blacklisted it and provides no firmware updates.

Hmmm.... are the Debian shims self-signed? I find it very interesting that the hardware would stop them. I wonder why it doesn't stop redhat/fedora based distros? (I know the shims are licensed by Microsoft)

 

[CaffeineAddict]

Hmmm.... are the Debian shims self-signed? I find it very interesting that the hardware would stop them. I wonder why it doesn't stop redhat/fedora based distros? (I know the shims are licensed by Microsoft)

I don't know about other distros but I suppose distros manage their own shims, so if they provide updated one that's not blacklisted it would work.

Debian lacks behind with updated signed shim, signature of the current one is blacklisted in my mobo. it's right there in in dbx database. and I can't remove it due to a firmware bug.

 

[punklearninglinux]

So acpi message above is not an error but informational message.

The error is "Unable to find a medium containing a live file system"
This suggests you need use boot menu to boot from USB, or alternatively enter BIOS and set boot order so that USB is listed first.


If you already installed Linux from USB to drive the same procedure with boot menu, but making sure boot order starts with the drive.

Which stage leads you go grub menu? install from USB or boot from already installed Linux to drive?

Hi,

I am able to see the Grub menu and I select "Try or Install Ubuntu" after which I see the splash screen followed by the logs I mentioned that pop up, dropping me into initramfs. After that it asks me to boot from a network URL (which I have tried and it also fails), landing back initramfs.

 

[punklearninglinux]

This is from an AI engine but should be fairly accurate because I have done it myself and it's faster than having to type it out myself.


If that doesn't work you can try clearing your secure boot keys, this is also generated by an AI engine.

Followed these steps, ensured USB is connected and is the top boot order drive, but it does not change the outcomes. I have not yet cleared the keys, but hesitant to mess with it given Windows is working ok. Should I try that without Windows drive connected to the mobo?

 

[CaffeineAddict]

Hi,

I am able to see the Grub menu and I select "Try or Install Ubuntu" after which I see the splash screen followed by the logs I mentioned that pop up, dropping me into initramfs. After that it asks me to boot from a network URL (which I have tried and it also fails), landing back initramfs.

So you're having this problem with live ubutnu iso from usb?

Maybe try creating Debian USB. but not live ISO, use regular ISO or netinst for network install.

 

[f33dm3bits]

Followed these steps, ensured USB is connected and is the top boot order drive, but it does not change the outcomes. I have not yet cleared the keys, but hesitant to mess with it given Windows is working ok. Should I try that without Windows drive connected to the mobo?

I forgot about your Windows install, no idea if it would effect that since I don't dual boot. My instinct says no because there is a setting to reinstall the default keys. And Windows probably won't boot with secure boot disabled, but just don't do it then.

Can you try creating a live iso with Fedora workstation and try booting from that. To see if you then get further when booting since Fedora does support secure boot. As a test so we have a comparison with something that does support secure boot.

 

[punklearninglinux]

I forgot about your Windows install, no idea if it would effect that since I don't dual boot. My instinct says no because there is a setting to reinstall the default keys. And Windows probably won't boot with secure boot disabled, but just don't do it then.

Can you try creating a live iso with Fedora workstation and try booting from that. To see if you then get further when booting since Fedora does support secure boot. As a test so we have a comparison with something that does support secure boot.

ok, let me give Fedora a try. Do you think it has to do with USB ports? i.e. should I try burning it in a dvd and give that a try? I have a usb dvd drive I can connect it to?

 

[Fanboi]

@punklearninglinux
Just weighing in, I notice you installed Windows first. I'm a little behind now (current board's ~5yo) but since Windows was installed first, it may have cause issues with keys in your BIOS/UEFI. If you haven't done anything useful on your Windows install, I say disconnect the drive, wipe your keys, then reset all your settings (with the CMOS reset pins). Plug in the drive you want for Ubuntu or whatever, make sure it's all verified, not broken/corrupted/blah-blah... Then start from the top and adjust each setting as needed. Once you're up and running with Ubuntu, you can try and get the Windows disk to boot (os-prober should find it when updating GRUB).

Protip: I don't use anything besides dd to write stuff, but apparently you can use Rufus or Ventoy to disable Windows's security (somebody who uses Rufus, Ventoy, et al., please weigh in here) crap when you prepare the Windows Installer from USB. It may save headaches just getting rid of all the security features.

My POV: You can run Windows in a VM with direct disk access instead of an image file. My current Windows 10 install costs me 10GB memory and a 60GB partition. I get decent speeds with KVM. Unless you're gaming, it shouldn't be and issue. You could just pass the entire Windows drive through.

 

[APTI]

Hi,

Thank you for taking the time to read this post.

I am relatively new to Linux. I built a new PC with two drives. I first installed Windows and all is working with it. On the second drive I wanted to install Ubuntu. I removed the Windows drive to avoid issues but I am unable to get past the Grub menu. I have tried all sorts of boot menu commands I could find on this and other forums but am stuck and can't boot in. Here are the details:

System information:
Motherboard: ASUS Pro WS WRX80E-SAGE SE WIFI II
CPU: AMD Threadripper Pro 5955WX
GPU: RTX 3090
RAM: 2 ECC OWC 64 GB DDR4 sticks
Keyboard: Logitech Keyboard
Mouse: Logitech Trackball
NVME SSD: WD 2TB

Bios settings:
Secure Boot: Other OS (no option to disable it)
CSM: Disabled
All other options left same as default
Firmware updated to latest 1602 version

Following are the errors I get:

acpi: module verification failed: signature and/or required key missing - tainted kernel
(followed by other log messages)
Unable to find a medium containing a live file system

Then it drops into initramfs


There are no USB 2.0 headers in the rear, so I have tried with USB 3.0 rear of the board, along with a USB 2.0 header cable connected to the board; none of them work and same errors occur for all.

I have tried multiple USB drives with bootable set up from Rufus and balenaEtcher using both MBR and GPT versions. Exact same errors on both. I have tried Popl_OS and Ubuntu and both give similar acpi errors.

I have replicated this problem also by removing all drives and simply trying to boot with the USB, no difference in errors.

I am completely out of ideas; I believe it has to do with my board or some setting which I am not sure how to fix. Here is the Bios Manual (https://dlcdnets.asus.com/pub/ASUS/mb/Socket sTRX4/PRO_WS_WRX80E-SAGE_SE_WIFI_II/E22244_PRO_WS_WRX80E-SAGE_SE_WIFI_II_BIOS_Manual_EM_V2_WEB.pdf) if you can help identify it.

Thank you for your help. I want to get this up and running for an AI project I have been meaning to work on. I will revert to Windows sadly if I can't set it up, but it should not be this hard right?

Much appreciate your help.

you have a very simple issue to fix. below is a link to a post I made and follow this and you will have a perfect multi-boot system and never worry about grub or other issues. inexpensive purchase that makes the dual boot simple and safe

https://www.linux.org/threads/dual-and-multi-boot-systems.47320/

 

[f33dm3bits]

ok, let me give Fedora a try. Do you think it has to do with USB ports? i.e. should I try burning it in a dvd and give that a try? I have a usb dvd drive I can connect it to?

Btw I just remembered I've cleared my secure-boot keys several times and it never killed my installation, even though I am using secure boot. Whether you burn a dvd or the iso to a usb shouldn't matter but now days doing it with usb is better.

 

[punklearninglinux]

Btw I just remembered I've cleared my secure-boot keys several times and it never killed my installation, even though I am using secure boot. Whether you burn a dvd or the iso to a usb shouldn't matter but now days doing it with usb is better.

Ok will try it later tonight (both Fedora via USB + clearing keys)

 

[punklearninglinux]

ok, let me give Fedora a try. Do you think it has to do with USB ports? i.e. should I try burning it in a dvd and give that a try? I have a usb dvd drive I can connect it to?

Tried quickly Fedora Workstation (https://fedoraproject.org/workstation/download/) via Media Writer utility. Attempted to boot it. Selected option "Test and start Fedora..." it failed fairly quickly with the following error:

Supported ISO: no
Checking: 004.7%
The media check is complete, the result is: FAIL

It is not recommended to use this media.
[FAILED] Failed to start [email protected] - Media check on dev/sda

Going to try with another USB stick to rule out drive problems.

 

[punklearninglinux]

Ok will try it later tonight (both Fedora via USB + clearing keys)

Tried quickly Fedora Workstation (https://fedoraproject.org/workstation/download/) via Media Writer utility. Attempted to boot it. Selected option "Test and start Fedora..." it failed fairly quickly with the following error:

Supported ISO: no
Checking: 004.7%
The media check is complete, the result is: FAIL

It is not recommended to use this media.
[FAILED] Failed to start [email protected] - Media check on dev/sda

Going to try with another USB stick to rule out drive problems.

ok tried another USB, this time it passed the checks, however it stops on:

[OK] Started gdm.service - GNOME Display Manager

It then keeps flashing back and forth between the logs and a blank gray screen with a cursor. I let it do so for good 15 mins, it keeps going back and forth.

Sigh.

 

[The Duck]

Out of curiosity I cleared all of my secure boot settings to legacy.
I cleared all of the keys and anything else related to UEFI secure boot.

I was unable to boot into my Linux so I powered off my computer with the front panel switch and booted into bios and reset the bios to the oem factory defaults and saved everything.

I'm now able to boot into my Linux and all is well as it was before so everything can be set back to the oem factory defaults to get you back to where you started or leastwise I can on my computer.

 

[punklearninglinux]

Ok here is the summary of all things I have tried so far:



1. Removed all SSDs, Updated Bios to latest version

2. Set Secure Boot to Other OS (according ASUS website that is disabling it)

3. Booted into Windows with Secure Boot off, checked it in its System information as it said Secure Boot was Off



4. Cleared Secure Boot keys, tried booting in with Popl, Fedora, Ubuntu; no luck get the errors (listed below respectively for each)

5. Installed new Secure Boot Keys (default keys), tried booting in with Popl, Fedora, Ubuntu; no luck get the errors (listed below respectively for each)

6. Put the drives back in, tried it all again, same outcomes



7. I swapped RAM sticks + GPU from another system which are also DDR4 with working linux (ASROCK mobo), still get the same errors; The only diff now is the ASUS mobo + CPU (the other system as a 3995WX)

8. Turned off the VGA switch on the mobo (there is no VGA card but I think it is for IPMI support) + Switched monitors for Fedora's flashing screen problems; nope nothing it still does that



9. Reset the CMOS, got fTPM warnings, reset it (had to unlock Windows with Bitlocker)

10. Tried 2 existing USB sticks, tried a brand new USB stick

11. Swapped in a SSD with working Ubuntu, I get similar acpi errors (screenshots below)







Ubuntu USB Boot screens and errors (built with Rufus)

acpi: module verification failed: signature and/or required key missing - tainted kernel
(followed by other log messages)
Unable to find a medium containing a live file system


Popl Boot screen and errors (built with Rufus):

Similar acpi + xhc_hcd init: fail, -16 errors and then initrafs


Fedora Boot Screen and errors (built with Media Writer):

No errors, reaches the UI initialization, and then just flashes screen.


Ubuntu SSD with working version errors:

Same xhci -22 errors and then initrafs


And I also tried Mint Linux with Rufus, it does the same thing as Ubuntu, gives xhci errors, followed by many lines of stdin: Invalid argument and then drops into the dreaded initrafs. Followed by "Unable to find a medium containing a live file system"

I read on reddit, pulling out the usb when you get stdin errors and putting it back in fixes it, but no such luck for me.

I am now certain it is not the Secure Boot, but it is something else that is causing this. Faulty mobo, faulty cpu? Both are brand new and work perfectly with no problems on Windows. I have done a few benchmark and stress tests for the CPU and GPU on Windows, no errors so far.

All these boot errors are fairly consistent across distros, which is a good thing in a way, but what is causing them!? Is the board a defective one? Should I try to get a RMA? No way of knowing otherwise. I am just lost! It has to something basic and stupid that I am missing. This can't be the case for ASUS to straight up not let linux boot in. What am I missing

 

[Condobloke]

''Unable to find a medium containing a live file system"

While perusing the bios area is there a 'Raid' section/area there?

can it be set to AHCI as opposed to raid ?

 

[Condobloke]

AS well as taking a look at the above.....you suggested earlier using a DVD as the boot medium.... give that a try as well, please.