Jump to content
meklort

OS X compatible motherboard -> QUO

4,344 posts in this topic

Recommended Posts

Argh. Reading back, one of the things I saw recommended was to reset PRAM. So I did. On reboot got warning that my UEFI was corrupted and it was going to restore. So I did, and ROM went back to F2N. 
 

I then updated ROM to XMAX - as I mentioned above my intent was to get new ssd and start fresh. I had done that, and formatted it to macOS first. So no internal drive other than new ssd. Updated ROM. I assume it did things it needed to, but I cannot tell, because after I rebooted...
 

Will no longer boot the 10.11 installer USB. White Apple logo, no progress bar. 
 

So I reconnected the previous fusion drive and tried booting through the BIOS. 

 

That no longer boots either. 
 

Argh. 
 

I have regressed from a working 10.10 box to one that won’t boot. 
 

I’m taking tomorrow off from work to see if I can get this to work...

Share this post


Link to post
Share on other sites
Advertisement

You lost me ... you told us what you wanted, we told you what to do, you did something else, now are you trying to boot El Capitan with a Vega Card ? Minimum OS for Vega drivers in macOS is Mojave

 

Let’s take this from the top ... what do you want to do ?

Share this post


Link to post
Share on other sites
On 5/21/2019 at 2:36 AM, Bynas said:

Hi! I used a preinstalled system 10.14.5 and could not proceed (blind screen after fruit logo)
Finally, succeeded by adding the following options to Defaults.plist (It is possible that only some of them are directly necessary).

 

Z77MX-QUO-AOS@167X-XMAX-E
i7-3770k
32GB RAM
RX580 Sapphire

defaults.png

 

Hi.

 

Where did you find that plist editor? Is it Windows only? I'm on a Mac.... ;)

 

 

Share this post


Link to post
Share on other sites

Update on my progress:

 

So far complete failure. I've got about 20 hours into this so far, and no progress.

 

I had a glitch of some kind and had to restore from the secondary BIOS. Was that F2N?

 

I had forgotten how elegant that interface was.

 

Anyway, I restored 828 then confirmed I could still boot my Yosemite fusion working disk.

 

Then 894 and ditto.

 

Then 1479, then 1669, then MASS.

 

However when I updated to MAX-E the Yosemite wouldn't boot any more, so I downgraded to MASS.

 

Along the way I bought a new SSD and formatted it to blank/journaled/GUID. I put it on SATA 0. Apparently one of the ROM updates is supposed to create a EFI/Oz directory on the SATA 0 disk. That never happened. I don't know if that only works if you already have a working boot OS on the drive, which I don't. But no EFI folder, no Oz folder. Just the standard hidden files a disk has.

 

Also, I never got a vanilla installer to boot. At every stage I tried a 10.11, a 10.13 and a 10.14 installer. Using my laptop I confirmed that each of the installers actually worked to boot a real Mac, but not one of them would boot the QUO, no matter which ROM I had loaded.

 

So I am currently going through this thread from page 160 copying and pasting relevant posts into a notes file to try and reduce the noise (for instance I'm not interested in dual booting).

 

So many questions. Mostly about my sanity, at this point. 20 hours is a lot of time to put into something that hasn't moved forward an inch. I have nothing but respect for JFF and others who keep this project alive for the hours they must put in, but I just feel really confused and frustrated.

 

PS early on I found an old Clover 10.9 boot USB stick I made for another build, and it booted just fine (but really s-l-o-w).

 

Share this post


Link to post
Share on other sites

Can u post your Defaults.plist ?

 

So you want Mojave, RX580, MacOS only ?

 

Hi.

 

Where did you find that plist editor? Is it Windows only? I'm on a Mac....

 

 

Don’t use it , does not work properly

Share this post


Link to post
Share on other sites

 

Quote

Along the way I bought a new SSD and formatted it to blank/journaled/GUID. I put it on SATA 0. Apparently one of the ROM updates is supposed to create a EFI/Oz directory on the SATA 0 disk. That never happened. I don't know if that only works if you already have a working boot OS on the drive, which I don't. But no EFI folder, no Oz folder. Just the standard hidden files a disk has.

 

The EFI folder will be created in the ESP partition not the regular one ... this is not Clover.

Reformat the drive
Flash XMAX-E Firmware then boot to UEFI shell...
 

fs0:
ls
 

and you should see the EFI folder

cd EFI
ls
 


And you should see the Oz folder
This is where you should put Defaults.plist. After doing this, hit Command-Option-P-R
 


 Another thing you might not be aware of is that even tough Ozmosis can boot from APFS partitioned drive, it does not know how to detect them so you have to tell it ... I made a post some time ago about that ...

Edited by IronManJFF

Share this post


Link to post
Share on other sites
 

You lost me ... you told us what you wanted, we told you what to do, you did something else, now are you trying to boot El Capitan with a Vega Card ? Minimum OS for Vega drivers in macOS is Mojave

 

Let’s take this from the top ... what do you want to do ?


Sorry, I was unclear. Right now I have no video card installed, I’m just using intel HD4000 - but I now own the Vega with no option to return. What I want to do is boot Mojave and use the Vega with two 4K monitors. I used to have a gti770 but it maxes out at two 2560x1600 monitors.

 

After much pain I got it to boot the Mojave installer, install to a blank internal ssd, boot, and create a user. But when I restarted after that it would not boot, and when I went to bios config I did not see the ssd. 
 

I rebooted to Yosemite, and it did not mount the ssd, so I opened Disk Utility which saw the ssd, but the formatted portion was greyed out with a generic name. I could not mount it or boot it or use it, so eventually I just erased it and started again. I have not been able to get even that far since.

 

Also Christmas happened so I wasn’t able to spend more than about 2 hours a day trying to get things to work. 
 

But I may have figured out why the Mac thinks it’s a Macpro3,1. Today I watched a Russian YouTube about putting Mojave on quo. I didn’t understand the Russian, and he didn't do a step-by-step, but at one point he downloaded the ROM on page 160 and opened it with some kind of utility. He showed a setting near the end that says the Mac is a macpro3,1. That model maxes out at El Capitan 10.11. Maybe that’s why I can’t install Mojave? MAXX is the ROM that I’m using since I couldn’t boot back into Yosemite with XMAX.

Edited by valiant
Additional info.

Share this post


Link to post
Share on other sites
On 12/17/2019 at 4:34 AM, ntsmkfob said:

If it's not creating the Oz directory where you expect it to be, you should check any other disks you have for an EFI directory, which is being used as the boot device instead of the one you expect. Make sure the Mac drive is connected to SATA port 0 on the motherboard. That will then be the drive the BIOS goes to for the EFI.


I’m a dumb ass. I forgot that there’s a separate partition on the hard drive called EFI. I was seeing a folder in the working partition called EFI that must have been put there by a Clover attempt and looking for Oz in there. I finally found the EFI partition and sure enough there was an Oz directory in there. 
 

For my own future reference I write this here:

 

/EFI/* ≠ /boot/EFI/*

 

Thanks!

 

EDIT: I still haven’t figured out what /L/E stands for though...

Edited by valiant

Share this post


Link to post
Share on other sites

Thanks @IronManJFF I’ll try what you posted on Dec 23 and let you know how it goes.
 

Along the way I tried upgrading my working Yosemite 10.10 install to El Capitan 10.11 and it no longer boots, so I’m flying a bit blind... or digging the ssd out of the computer, moving it to an external case, and plugging it into my laptop then reversing the procedure to use my changes. That slows things down...

Share this post


Link to post
Share on other sites

Stream of consciousness…

 

One. Took out all drives. Took new SSD to laptop and reformatted it – as you said it was a APFS so the drive had a volume and a subvolume. I reformatted it to journaled/guid. 
 

Two. Took it out of the external case on the laptop and reinstall it into the Macintosh. Put in Oz thumb drive and upgraded UEFI to XMAX_E. On completion there was a logo flash of Hermit Crab and four progress words ending in “completed”. Then it restarted and I got the shell verbiage (unusually short because so few drives installed). 

 

Three. Typed “fs0:” (spelling matters). Got listing. Cd’d into “Efi” and listed. Sure enough there’s an APPLE, an Oz and a Quo directory. 
 

Four. Typed “exit”. Got an Apple progress bar that ended in a no entry sign. No surprise, there’s no OS on there.
 

Four: Removed the SSD from the hackintosh case again and put it back in the external case and put it back on the laptop and decided to do a clean vanilla install of Mojave. I did it that way rather than using a thumb drive because I read above somewhere somebody else had done it that way and it worked. Also I’ve had very little luck getting the quo to boot from thumb drives... 
 

Five: Several hours later and after much travail got Mojave to install on the ssd and booting the laptop. Clicked through and created user. Found defaults.plist on p161 and copied it to textwrangler and saved it to desktop. Got to the “insert your serial number here” section and had to chase down info on how to. Eventually got clover configurator to generate an unused imac13.2 s/n and board number. 

NOTE: THE SUPPLIED PLIST ON P162 HAS AN ERROR:
Line 16 ends with “ > ” — that’s “space closeanglebracket invisiblecharacter”.

I corrected that and inserted the s/ns (using the text editor, not clover configurator as per your observation above that it doesn’t work right).

 

I then went to put defaults.plist into /EFI/Oz/ and noticed the /EFI/ partition was empty. I double-checked using Terminal in case they were invisible for some reason but /EFI/ was empty. No APPLE, no Oz, no Quo. 
 

So I grabbed the QUOROM flash drive and copied the defaults.plist to it. 

 

Six: I took the SSD out of the portable case and re-mounted it back into the hackintosh. I then re-ran the flash bios procedure to reinstall XMAX-E. This time when I did the fs0: listings I saw that XMAX only created the Oz directory. There’s no APPLE directory, no Quo directory. Oz contains Darwin and ACPI directories which I did not investigate. 
 

QUESTION: are the /EFI/APPLE and /EFI/Quo directories necessary? If so can I put them back somehow or do I need to go back to Step One and this time try and figure out how to install from a thumb drive (that took me about 30 hours the last time before Christmas).

 

Seven: Used CP to copy defaults.plist from QUOROM thumb drive to the SSD /EFI/Oz/ directory. Rebooted to UEFI and... no sign of the SSD in the list of devices. And then I remembered:
 

On 12/23/2019 at 4:51 AM, IronManJFF said:

Another thing you might not be aware of is that even tough Ozmosis can boot from APFS partitioned drive, it does not know how to detect them so you have to tell it ... I made a post some time ago about that ...

 

I don’t suppose you remember how long ago? Or a keyword I could use for searching?

 

Thanks. 
 

Hmm. This forum doesn’t have very good search. I did a search by author on IronManJFF for APFS and got zero hits, not even the one above on this page... if someone could point me to that post I would be grateful...

 

PS Happy New Year to everyone!

Edited by valiant

Share this post


Link to post
Share on other sites

The Ozmosis BIOS has a built in Defaults.plist that contains the MacPro 3,1 definition, and to override that it needs to have loaded into NVRAM, a Defaults.plist from the EFI/Oz directory of the first drive it interrogates (SATA 0), with either a Mac mini or an iMac 13,2 definition. Command+Option+P+R at boot time (easier from the Shell prompt) will load an available /EFI/Oz/Defaults.plist into NVRAM and then restart the PC with the new definition.

 

It doesn't reload the Defaults.plist at every boot, only when the Cmd+Opt+P+R occurs or a new BIOS is uploaded.

 

You need to find the filesystem that has boot.efi present.

At the shell prompt type ls fs0:

If you see s System directory you've probably found it. If not try ls fs1:, ls fs2: etc until you do.

Once found, type 'bcfg boot dump' to list your boot list - let's say you already have 3 entries

 

Replace fsx: below with the fs1: or fs2: etc. where you found the \System folder

 

now type bcfg boot addp 4 fsx:\Sy and hit the tab key to select System

type Li and hit tab

type Co and hit tab

type Lo and hit tab

type Bo and hit tab

 

You should now have bcfg boot addp 4 fsx:\System\Library\CoreServices\Locked Files\Boot Files\

 

If it didn't work you may be on the wrong files system - try more ls fsx: commands increasing the number for x each time

 

add boot.efi then a space to the end and finally add your preferred name for the volume in quotes e.g. "Mojave"

 

You should now have (assuming 4 is the correct value for your system)

bcfg boot addp 4 fsx:\System\Library\CoreServices\Locked Files\Boot Files\boot.efi "Mojave"

 

Press enter. You can type bcfg boot dump to list the entries.

 

Type reset to reboot and hit F12 to get the boot list again and choose Mojave.

 

You can then set Mojave as the startup disk in SysPref once booted, and move it to the top in the BIOS boot options as well.

 

Remember you will also need the KernextPatch.plist in the EFI partition.

 

Connecting another disk that has an EFI partition may change the filesystem (fsx:) number and invalidate the above.

 

It's all different for Catalina.....

Edited by ntsmkfob
Several Errors

Share this post


Link to post
Share on other sites

Thanks @ntsmkfob!

 

More stream of consciousness…
 

Eight: I tried cmd-opt-p-r from boot since that’s what I’m used to with a Mac, got a screen I’d never seen before - three large colour blocks with a stylized chip in the upper right corner and “EDK>”.  So I went to the shell as you suggested and typed boot then held down cmd-opt-p-r. The whole screen flashed three colours - I think green then yellow then red but I was so startled I’m not really sure of the colours or the order. It was followed by the Hermit Crab splash screen and text ending in “complete”. Then it went back to the shell.

 

Nine. I discovered my System folder is on fs2:  And because I removed all the other drives I only have one option (as per the BCFG listing):

 

VenMedia(long number) “UEFI: Built-in EFI Shell “ OPT

 

I typed in the command you provided  bcfg boot addp 4 /System/Library/CoreServices/Locked Files/Boot Files/boot.efi "Mojave" (I’m using an old keyboard with a dysfunctional tab key so I typed it manually) and got an error saying
”unknown argument ‘Files/boot.efi’ “

I tried the same command with PC style backslashes “\” but got the same error.
I tried using the mac style of forward slashes “/“ but escaping spaces “\ “ and got the same error.

So I thought if I just navigated to the directory I might be able to issue the command there, but that didn’t work. I was only able to get to \CoreServices directory, there does not appear to be a Locked Files directory. In CoreServices I typed ls L* and got a listing of six items, none of which were Locked Files.

 

Ten. I went back to Eight and tried everything again. This time i discovered no need to type anything at shell prompt, holding down the keys just does it. I’m now sure the order the screen flashes is Red Yellow Green. But nothing else was different. I do not appear to have a /System/Library/CoreServices/Locked Files/ or /System/Library/CoreServices/Locked Files/Boot Files/ directory and thus cannot make changes to it. I did notice that I *do* have a /System/Library/CoreServices/boot.efi file however. Is that the one you meant to make changes to?

 

If not, do you have any other suggestions?

 

Thanks!

Share this post


Link to post
Share on other sites
Posted (edited)

My apologies, I missed part of a statement, and you're right it should be backslashes.

 

So if you say you found the boot.efi on \System\Library\CoreServices\Locked Files\Boot Files\ on fs2:

 

then you need to type into the shell:

bcfg boot addp 4 fs2:\System\Library\CoreServices\Locked Files\Boot Files\boot.efi "Mojave"

 

If you reboot and press F12 to get the boot menu, Mojave should be listed.

 

As long as you have the Defaults.plist in the /EFI/Oz folder it will have been read into NVRAM and saved when the screen flashed different colours.  You can type 'ls fs2:\EFI' to check for the Oz folder.

Edited by ntsmkfob

Share this post


Link to post
Share on other sites
3 hours ago, ntsmkfob said:

So if you say you found the boot.efi on \System\Library\CoreServices\Locked Files\Boot Files\ on fs2:

 

then you need to type into the shell:

bcfg boot addp 4 fs2:\System\Library\CoreServices\Locked Files\Boot Files\boot.efi "Mojave"


Unfortunately, I don’t seem to have that directory. 

I do not have \System\Library\CoreServices\Locked Files\Boot Files\boot.efi

 

But I do have \System\Library\CoreServices\boot.efi

 

Should I try to patch that boot.efi instead?
 

NB: I used edit \System\Library\CoreServices\SystemVersion.plist to confirm that the macOS is 10.14.6

 

Thanks. 

Share this post


Link to post
Share on other sites
Posted (edited)

I looked for fs2:\EFI but there wasn't one. However there was a fs0:\Efi, and a defaults.plist was in there.

 

So I just went ahead and patched the \System\Library\CoreServices\boot.efi that was there

 

bcfg boot ADP 4 fs2:\System\Library\CoreServices\boot.efi "MojaveSSD"

 

Then rebooted.
 

I used F12 to get a list of boot volumes, and sure enough there was MojaveSSD (that's what I named it).

 

So I selected it, and got a long string of verbosity on boot, that ended in a white square. I figured it had broken and I went to find my phone so I could take a picture. By the time I located it and got back to the computer, the Mojave login screen was on the monitor. 

 

YAY SUCCESS!!

 

Or at least I think it's Success... I haven't tried rebooting yet. But I am typing this reply using Safari on my new Mojave QUO. 

 

I will submit this reply and then reboot. But in the meantime, THANK YOU @IronManJFF and @ntsmkfob for being patient with my noob questions and hamfisted efforts. I am delighted to have gotten this far.

 

☺. 

Edited by valiant

Share this post


Link to post
Share on other sites

Ah well. Premature celebration. QUO will not boot to Mojave a second time. Not as a normal boot, not if I select it using F12, not if I go into the UEFI manager, load defaults (F7), set MojaveSSD as boot volume, nothing. 
 

I thought maybe I needed to zap PRAM again, so I did that. Evidently that’s not the right thing to do, because the QUO forgot the MojaveSSD.


So I repatched the boot.efi as per above, used bcfg boot dump to confirm it had taken, rebooted using F12 and selected it, and still no go. 


I also opened the defaults.plist edit fs0:\Efi\Oz\defaults.plist and confirmed it matched the one on page 161. 
 

rereading everything above, I came across 
 

On 12/31/2019 at 12:30 AM, ntsmkfob said:

Remember you will also need the KernextPatch.plist in the EFI partition.

 

Maybe that’s the problem? Where do I find the KernextPatch.plist?

 

Thanks!

Share this post


Link to post
Share on other sites
3 hours ago, valiant said:

Ah well. Premature celebration. QUO will not boot to Mojave a second time. Not as a normal boot, not if I select it using F12, not if I go into the UEFI manager, load defaults (F7), set MojaveSSD as boot volume, nothing. 
 

I thought maybe I needed to zap PRAM again, so I did that. Evidently that’s not the right thing to do, because the QUO forgot the MojaveSSD.


So I repatched the boot.efi as per above, used bcfg boot dump to confirm it had taken, rebooted using F12 and selected it, and still no go. 


I also opened the defaults.plist edit fs0:\Efi\Oz\defaults.plist and confirmed it matched the one on page 161. 
 

rereading everything above, I came across 
 

 

Maybe that’s the problem? Where do I find the KernextPatch.plist?

 

Thanks!

Hey there, thanks for all you help folks, I followed all this thread, and I confirm, it works for High Sierra 10.13.6 with Ozmosis Catalina rom.
@valiant, I was having the issue like you, booting only from boot menu after pressing F12.
It worked like a charm after add KernextPatcher.plist and Defaults.plist (edited with prefEdit to add my s/n and UUID) to Efi\Oz\ after that reboot to EFI Shell, add \System\Library\CoreServices\boot.efi entry like @ntsmkfob explained before here(

),  NVRAM time pressing Cmd+Opt+P+R, blinking screen three colors, >reset <enter> and Voilà! booting smooth...

Share this post


Link to post
Share on other sites
4 hours ago, valiant said:

Ah well. Premature celebration. QUO will not boot to Mojave a second time. Not as a normal boot, not if I select it using F12, not if I go into the UEFI manager, load defaults (F7), set MojaveSSD as boot volume, nothing. 
 

I thought maybe I needed to zap PRAM again, so I did that. Evidently that’s not the right thing to do, because the QUO forgot the MojaveSSD.


So I repatched the boot.efi as per above, used bcfg boot dump to confirm it had taken, rebooted using F12 and selected it, and still no go. 


I also opened the defaults.plist edit fs0:\Efi\Oz\defaults.plist and confirmed it matched the one on page 161. 
 

rereading everything above, I came across 
 

 

Maybe that’s the problem? Where do I find the KernextPatch.plist?

 

Thanks!

KernextPatch.plist the same from your previous post...

Share this post


Link to post
Share on other sites

Sorry - another error on my part! The Locked Files\Boot Files bit was to get the install restarted, and isn't present after the install completes. Glad you worked through it. You usually only need to zap the PRAM to load a modified Defaults.plist. If you install a new BIOS image, it zaps the PRAM and your BIOS settings anyway.

Share this post


Link to post
Share on other sites

@IronManJFF I'm starting to refresh on the process and i'm looking into your release.

 

I have two of these boards. The second was one of The King's prototypes that I've put together for my son. Understanding that The King's old board was probably flashed to death, I want to get the configuration perfect on my machine so I can do it once on his.

 

I'm doing a refresh on both. I do a fair amount of video editing and my son is starting to play games on his.  I hear the RX590 isn't too bad of a card. I know these things were very particular even between brands. Do you have any suggestions for particular cards that I should look into purchasing.

Share this post


Link to post
Share on other sites

Still not booting. 
 

I finally found the KernextPatches.plist and copied it to fs0:\Efi\Oz\ next to the defaults.plist. 

 

But I still can’t boot Mojave. 
 

I reflashed the BIOS to make sure I had the XMAX-E ROM loaded - version H20.1512242359, then reloaded optimized defaults. 
 

Now of course it lost the patched boot drive so I exited to shell and typed fs2:\System\Library\CoreServices\boot.efi to see if I could get it to boot that way. 
 

All I got was a black screen. I left it for 15 minutes in case it was really slow to boot, but that didn’t help. 


Then I found this on page 148:

 

On 6/30/2018 at 9:41 AM, IronManJFF said:

Step #3

Adding the new boot entry

 

Now issue theses commands (replacing italic by values we found earlier)
 
fsn:
bcfg boot addp highest number +1 System\Library\CoreServices\boot.efi "Name that you want to appear in F12 Menu"

 

I had previously used bcfg boot addp 4, but since I only have 1 SSD mounted right now, I only have one boot entry. So I did it with 2 instead. 

 

bcfg boot addp 2 fs2:\System\Library\CoreServices\boot.efi "MojaveSSD"

 

And confirmed with bcfg boot dump that it was there. I then did a reset and using F12 selected MojaveSSD to boot.

 

Still no luck. Just a blank screen. 

 

So.

 

• I have a vanilla install of Mojave on the only drive in the QUO.

• I have the XMAX-E ROM loaded. 

• I have defaults.plist and KernextPatcher.plist in /Efi/Oz/ partition.
But

• I do not have a video card installed, I’m just using the onboard HD4000, but I don’t think that’s a problem as Mojave 10.14.6 seems to have drivers for it since I had it running once before.

• I do not have /Efi/APPLE/ or /Efi/Quo/ directories. Is that a problem?

• I do not have any changes to the BIOS settings except for load defaults.

 

What am I overlooking? What should I try next?

 

Thanks. 

 

 

 

 

Share this post


Link to post
Share on other sites

Good catch! 
 

It didn’t solve the problem though.

 

I used mv to move KernextPatcher.plist out of \Efi\Oz\ to \Efi\

 

[Interesting note: there is now an /Efi/APPLE/ directory with an Extensions folder in it. I don’t know how or when that got added...]

 

I then reset and used F12 to boot to shell, reset the PRAM (no mention if that was necessary, but just to be safe), and then added the extra boot option back in again.

 

Rebooted to the UEFI manager, loaded optimal settings, set boot volume to MojaveSSD, rebooted, and...  nothing.

 

So.

 

• I have a vanilla install of Mojave on the only drive in the QUO.

• I have the XMAX-E ROM loaded. 

• I have defaults.plist in /Efi/Oz/ partition.

• I have KernextPatcher.plist in /Efi/ partition.

• I now have an /Efi/APPLE/ directory.

But

• I do not have /Efi/Quo/ directory. Is that a problem?

• I do not have any changes to the BIOS settings except for load defaults.

Also

• I created the SSD on a MacBookPro9,1 - not by using a USB installer. Is that a problem?

 

And the QUO still does not boot.

 

What am I doing wrong? What can I try next?

 

Thanks. 

 

Share this post


Link to post
Share on other sites

I've don't recall ever having a /EFI/QUO folder, so that's not it.

 

I don't have your graphics card, but it maybe that you need Lilu.kext and WhateverGreen.kext in your /Library/Extensions folder.

 

Make sure you chown -R root:wheel /Library/Extensions/* and chmod -R 755 /Library/Extensions/* after copying/moving them there.

 

Then touch /Library/Extensions to rebuild the cache.

 

Don't put them in /System/Library/Extensions

 

You could also add -v to the boot-args in your Defaults.plist (and do a Ctl+Opt+P+R to reload it into NVRAM). this might give us an idea of where your boot hangs. Give it at least 30 minutes to see if the boot continues.

 

You could also add nv_disable=1 to the boot-args as well. I have it but I don't remember if it is a legacy or a requirement. Worth a try anyway!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Tricchi
      Vorrei assemblare un nuovo hackintosh partendo dallo stretto necessario per poi aggiungere altri componenti nel tempo. Dato che la mobo penso sia fondamentale vorrei prenderne una che mi dia la possibilità di future espansioni ma che non costi troppo. Ho visto che su Amazon ci sono delle mobo come ad esempio la Asrock Z370 Taichi usate ad ottimi prezzi. Voi che ne pensate? Vale la pena o è rischioso? Nella descrizione c'è scritto "Come nuovo" o "Ottime condizioni".
      Riguardo alla compatibilità di questa scheda madre con hackintosh che mi dite? Il modulo wi-fi e bluetooth è compatibile?
      Grazie.
       
      Marco
    • By Surfman
      Ciao a tutti.
      dopo aver installato High Sierra il pc non può avviarsi dall'SSD mostrandomi la schermata nera che dice di scegliere il boot. facendo partire il pc con l'USB inserita, da dove ho installato il tutto, mi viene mostrata schermata di scelta dove posso effettivamente fare partire osx appena installato dal ssd ma con una lentezza mostruosa!. se provo con la chiavetta scollegata stessa schermata nera con la scelta del boot. inutile aggiungere che ho cercato di cambiare l'ordine di avvio dal BIOS, aggiornato il BIOS, ma senza successo. l'ssd funziona perché dopo ho installato da questo stesso anche linux o windows tranquillamente
      cosa posso fare? grazie a tutti

      MOBO: Gigabyte GA-B250M-DS3H
      CPU intel i5
      GPU NVIDIA MSI N750 Ti TF 2GD5 / OC  

    • By srmusico
      Hello guys.
      This is not my first hackintosh, but this will be the first time to create a hackintosh with thunderbolt.
      First of all, i have read some info about MoBos with Thunderbolt, but im a bit confused.
      I need to create a working hackintosh with Thunderbolt 2/3 .
       
      At this moment i know that we got 2 options (Correct me if im wrong),
      -we can get one MoBo and ad a Pcie Card with thunderbolt (only if the chipset is compatible)
      -we can get one MoBo with thunderbolt integrated via USB-C connectors (like the new Macbook Pro)
       
      What are the possible MoBos that have integrated Thunderbolt vía USB (or directly thundelbolt ports)?
      I have read a lot of buyers guides from some webs , but a lot of that MoBos with thunderbolt enabled, are "discontinued" or without stock
      Should we only choose Gigabyte MoBos? 
       
      I Have been too looking at Gigabyte website, and seems that the Chipset Z170 its the only one with Thunderbolt (vía USB-C)
      ports.
       
      Could you help me with these please?
       
      Thanks You So Much!
    • By Costanegra
      Hello.
       
      It's been about 3 or 4 years since I built my first, and so far only hackingtosh. I did so fallowing a guide written by good guy ^Andy^, witch came with hardware recommendations. I now feel it's time for me to upgrade to a faster system to keep up with heavier work loads. I'm strongly considering building a hackingtosh around the new i7-6700K Skylake processor, but I haven't come across guides for  this type of processor. I was wondering if any of you could recommend me a motherboard that's compatible and that won't become a hassle when trying to install OS X. Also, if there's a guide you know of, please let me know.
       
      Thanks in advance.
    • By FrankOshe389
      Hi,
      I'm currently running a Windows 7 x64 PC with:

      8GB DDR3 Ram

      AMD FX 4170 GPU

      AMD Radeon HD 7870 CPU

      1TB HDD (Windows 7)

      150GB HDD (Blank)
       
      Gigabyte GA-970A-DS3 Motherboard
      I am aware that getting OSX on an AMD machine is not an easy task, but can it be done with my setup?

      I am currently running OSX 10.8.3 in VMWare which is OK but lags a fair bit and lacks any kind of 3d acceleration and would like to be able to dual boot it natively alongside windows on the 150GB HDD.

      Thanks 
×