- Joined
- Jan 30, 2018
- Messages
- 6
- Motherboard
- MSI Z170A GAMING M7
- CPU
- Intel i7-6700K 4.0GHz (SKYLAKE)
- Graphics
- EVGA GeForce GTX 970 SSC
- Mac
- Mobile Phone
I managed to get my first install of High Sierra 10.13.3 onto a Skylake machine (see my specs below). I was a bit excited that I did it, and when I ran MultiBeast, I may have selected some incorrect options from the get-go, and I talk about more of that in the second paragraph. Anyways, I was having issues getting the system to recognize my EVGA Geforce GTX 970 SSC. I did some research and found out that 100 series builds don't support the NVRAM. I followed multiple threads and found this one, and problem #6 is my exact issue. But then I started thinking... I probably messed up some of my MultiBeast settings, so maybe I should clear them and restart. I've seen other Skylake builds with 17.1(even though it's optional) and I'm using 14.2. But I like the challenge of this whole thing and I won't feel accomplished unless I can do everything I can to full potential.
Here's what I had done.
The first time I ran MultiBeast, (in Bootloaders tab) I selected Clover UEFI Boot Mode and later found out that with my 100 series build I need the Clover UEFI Boot Mode + Emulated NVRAM. I saved my original MultiBeast settings in my Documents folder. Then after I found my issue, I went to go update the changes and MultiBeast told me that the updated MultiBeast settings file (that I just made) was corrupted.
What I want to know is:
Is there any way to clear all MultiBeast settings and restart? Or... should I follow the steps on the guide as listed above and not worry about updating the MultiBeast settings? I was continually having issues booting into the EFS drive from Clover and I kept having to include "slide=0 debug=0x100" to my boot args every time I restarted since I was booting from the USB screen. I've been afraid to boot directly from the HDD that I have High Sierra installed on because I've been trying to fix my graphics card problem before I went further.
I'm very new to all of this, and I've read so many threads that I'm overwhelmed and confused. I spent 6 hours doing troubleshooting on my own + researching where I had gone wrong. And I'm just lost now. Any help or direction on where I should go next would be much appreciated.
Here's what I had done.
The first time I ran MultiBeast, (in Bootloaders tab) I selected Clover UEFI Boot Mode and later found out that with my 100 series build I need the Clover UEFI Boot Mode + Emulated NVRAM. I saved my original MultiBeast settings in my Documents folder. Then after I found my issue, I went to go update the changes and MultiBeast told me that the updated MultiBeast settings file (that I just made) was corrupted.
What I want to know is:
Is there any way to clear all MultiBeast settings and restart? Or... should I follow the steps on the guide as listed above and not worry about updating the MultiBeast settings? I was continually having issues booting into the EFS drive from Clover and I kept having to include "slide=0 debug=0x100" to my boot args every time I restarted since I was booting from the USB screen. I've been afraid to boot directly from the HDD that I have High Sierra installed on because I've been trying to fix my graphics card problem before I went further.
I'm very new to all of this, and I've read so many threads that I'm overwhelmed and confused. I spent 6 hours doing troubleshooting on my own + researching where I had gone wrong. And I'm just lost now. Any help or direction on where I should go next would be much appreciated.