I've got Catalina running on my Asus Crosshair VIII Impact board...but only if I boot Opencore from a USB key or SATA drive, because without one of those the system doesn't see the m.2 drive Catalina is installed on.
I've installed Catalina on a nice, fast Corsair 2TB PCIE Gen 4 drive. Works great. Except, you know, for the whole "motherboard doesn't see the drive" thing.
If I go into the BIOS and select Advanced->NVME Configuration, I'm told "No NVME drive found". In fact there are two, the Catalina install drive and a scratch drive. If I boot Opencore from a USB key or SATA drive, and can boot Catalina from the 2TB drive, and both it and the scratch drive appear on my desktop.
But since the motherboard BIOS seems blissfully unaware of either drive, I can't boot directly...and yes, there's a valid EFI partition with an Opencore configuration on it.
Here's the timeline:
1. Boot from installer USB and install Catalina. Reboot into Catalina.
2. Mount EFI partition of the NVME drive and copy configured EFI folder.
3. Hm. Can't boot from the NVME drive. Drive not seen by motherboard BIOS. No obvious settings to change this.
4. Maybe there's something wrong with the drive. Install additional 500GB NVME scratch drive and install Catalina on that. Mount EFI partition and copy folder.
5. Huh. Suddenly everything works. I can even boot from the 2TB drive I couldn't before. Drive shows up in BIOS and in F8 boot selector screen.
6. Boot from 2TB drive and erase scratch drive. Continue with tweaks to get things working.
Here's what seems to have screwed things up: I tried a new **.aml file to get more USB ports working. The system started to boot but froze after the boot progress bar under the Apple logo had completely filled in.
And after that I couldn't boot from NVME any more. The drive stopped showing up in the BIOS. The F88 boot selector screen is empty.
I've made sure CSM is turned off and that the operating system is set to "Other OS".
I'd appreciate any ideas. Google searches revealed a lot of inapplicable Windows techniques. Odd that I've been running off an NVME drive on an ASUS Intel motherboard for over a year now and never seen this issue.
I've installed Catalina on a nice, fast Corsair 2TB PCIE Gen 4 drive. Works great. Except, you know, for the whole "motherboard doesn't see the drive" thing.
If I go into the BIOS and select Advanced->NVME Configuration, I'm told "No NVME drive found". In fact there are two, the Catalina install drive and a scratch drive. If I boot Opencore from a USB key or SATA drive, and can boot Catalina from the 2TB drive, and both it and the scratch drive appear on my desktop.
But since the motherboard BIOS seems blissfully unaware of either drive, I can't boot directly...and yes, there's a valid EFI partition with an Opencore configuration on it.
Here's the timeline:
1. Boot from installer USB and install Catalina. Reboot into Catalina.
2. Mount EFI partition of the NVME drive and copy configured EFI folder.
3. Hm. Can't boot from the NVME drive. Drive not seen by motherboard BIOS. No obvious settings to change this.
4. Maybe there's something wrong with the drive. Install additional 500GB NVME scratch drive and install Catalina on that. Mount EFI partition and copy folder.
5. Huh. Suddenly everything works. I can even boot from the 2TB drive I couldn't before. Drive shows up in BIOS and in F8 boot selector screen.
6. Boot from 2TB drive and erase scratch drive. Continue with tweaks to get things working.
Here's what seems to have screwed things up: I tried a new **.aml file to get more USB ports working. The system started to boot but froze after the boot progress bar under the Apple logo had completely filled in.
And after that I couldn't boot from NVME any more. The drive stopped showing up in the BIOS. The F88 boot selector screen is empty.
I've made sure CSM is turned off and that the operating system is set to "Other OS".
I'd appreciate any ideas. Google searches revealed a lot of inapplicable Windows techniques. Odd that I've been running off an NVME drive on an ASUS Intel motherboard for over a year now and never seen this issue.