Jump to content

OS X compatible motherboard -> QUO


meklort
4,397 posts in this topic

Recommended Posts

On 7/4/2019 at 3:55 AM, jkim74 said:

I recently installed Sapphire Nitro RX580 card, and then experienced significant slow downs and freezes, especially when using Photos.

 

I didn't make the connection with the RX580 card and the issue right away.  I have a large Photos library (500gb) and first performed repair of Photos library, and even recreated the Library (and imported the master images). Then I reformatted the startup drive with clean install of High Sierra, but still had issues with slow down and freezing.  Finally, after I pulled the RX580 card and used integrated graphics again, the computer was back to its stable self.

 

I found reported cases of freezing with this card and Photos which was related to mediaanalysisd in background with fix using the following:

sudo rm /System/Library/LaunchAgents/com.apple.mediaanalysisd.plist"

 

Others stated resolution with upgrade to Mojave.  I tried updating to Mojave, but got stuck mid-install due to my inability to add disable_nvflags=1 option to  fsx:\macos Install Data\Locked Files\Boot Files\com.apple.boot.plist.  So for now I am still using High Sierra.

 

Anyone else experience similar issues with this card?

 

 

These are the cards that support Metal and are compatible with macOS Mojave:

  • MSI Gaming Radeon RX 560 128-bit 4GB GDRR5
  • Sapphire Radeon PULSE RX 580 8GB GDDR5
  • Sapphire Radeon HD 7950 Mac Edition
  • Nvidia Quadro K5000 for Mac
  • Nvidia GeForce GTX 680 Mac Edition

I'm using the MSI RX560 ITX without problems.

Edited by ntsmkfob
  • Like 1
Link to comment
Share on other sites

On ‎7‎/‎5‎/‎2019 at 6:30 AM, jkim74 said:

I had the same problem of getting a black screen after booting Mojave installer USB.  What specific BIOS changes did you have to make for the Mojave installer to work?

Sorry for the late reply.

The only way to get it working seems to be: install supported card (ex. RX5xx), disable iGPU.

Link to comment
Share on other sites

  • 4 weeks later...

Hiya guys,

 

I want to update my Mac to the latest version of Mojave (10.14.6), as I'm still running the first developer release of Mojave 10.14. So far I've sorted out some basic issues I may encounter such as converting my boot SSD to APFS and backing up all my data.

 

But could someone help me out with an updated iMac defaults.plist template? Or at least the necessary updated values such as BiosDate and Firmware values.

 

It has to be the iMac .plist as others such as the MacMini and MacPro have usb compatibility issues for me.

 

Thanks in advance!!

Link to comment
Share on other sites

These are working for me on 10.14.6:   

 

    <key>BiosDate</key>
        <string>04/16/2019</string>
        <key>BiosVersion</key>
        <string>IM131.88Z.F000.B00.1904161750</string>
        <key>FirmwareFeatures</key>
        <integer>0xE00DE137</integer>
        <key>FirmwareFeaturesMask</key>
        <integer>0xFF1FFF3F</integer>

        <key>ProductId</key>
        <string>Mac-FC02E91DDD3FA6A4</string>
        <key>ProductFamily</key>
        <string>iMac</string>
        <key>ProductName</key>
        <string>iMac13,2</string>

 

Edited by ntsmkfob
Link to comment
Share on other sites

So I changed the necessary values such as bios date and bios version, and now Software Update in System Preferences detects the latest version is compatible with my computer. 

 

But, as I try to install it, after the whole process completes, my Mac boots, but it hasn't really updated. I have tried with different updated .plist files (MacMini6.1, iMac13.1, iMac14.1, etc.) but to no avail.

 

I have also tried updating via an installer rather than updating directly from System Preferences, and it has the exact same effect.

 

Right now, I'm booted up with the iMac14.1 Defaults file.

 

 

Screenshot 2019-08-06 at 02.29.24.png

Link to comment
Share on other sites

You need to read back in this thread. Basically, when the update fails you need to edit a file in a subdirectory of the macos Install Data folder to add stuff below, and then immediately reboot, press F12 to get into the shell and use the boot.efi in that same folder to complete the install.

 

Use sudo nano from the command line or from the shell:

 

Add flagsnv_disable=1 to kernel flags line in:
fsx:edit "macOS Install Data\Locked Files\Boot Files\com.apple.boot.plist"

 

after reboot type:

fsx:\macOS\macOS Install Data\Locked Files\Boot Files\boot.efi  and hit enter

 

where fsx is the filesystem with the macos Install Data folder. You will need sudo to do the edit from the command line. I use the nano editor. Make sure you leave a space before and after the added text.

 

Thanks to IronManFF and others for working it out and documenting it (probably better than I have, so search back for the messages discussing it)

Link to comment
Share on other sites

On 8/5/2019 at 8:30 PM, Casm101 said:

But, as I try to install it, after the whole process completes, my Mac boots, but it hasn't really updated. I have tried with different updated .plist files (MacMini6.1, iMac13.1, iMac14.1, etc.) but to no avail.

Were you using a Nvidia Card prior to the RX 580?

If so .. you may need remove the Nvidia Web drivers from your system ...Open Uninstaller ...

image.png.8e115e17110243b9b343bc616b57235a.png

 

Link to comment
Share on other sites

11 hours ago, ntsmkfob said:

You need to read back in this thread. Basically, when the update fails you need to edit a file in a subdirectory of the macos Install Data folder to add stuff below, and then immediately reboot, press F12 to get into the shell and use the boot.efi in that same folder to complete the install.

 

I've been looking though the old posts, and I can't seem to find it, I'm pretty sure I saw it at some point before... :rolleyes:

 

11 hours ago, ntsmkfob said:

Add flagsnv_disable=1 to kernel flags line in:
fsx:edit "macOS Install Data\Locked Files\Boot Files\com.apple.boot.plist"

 

Thanks, it seems like a pretty easy fix, but where is the macOS Install Data folder?

 

On the install drive I created this is what I get:

 

1243893018_Screenshot2019-08-07at11_05_30.png.31fd000e6f98b95b7ad12045d4cd649d.png

 

Or do you mean on my boot SSD once I have started the installation?

 

8 hours ago, IronManJFF said:

Were you using a Nvidia Card prior to the RX 580?

If so .. you may need remove the Nvidia Web drivers from your system ...Open Uninstaller

 

I was using a Nvidia card, but I never had to install drivers, it just worked straight out of the box as if it were native to Mac, it was almost 10 years old, so there wasn't that much I could do with it anyways. -_-

 

11 hours ago, ntsmkfob said:

Thanks to IronManFF and others for working it out and documenting it (probably better than I have, so search back for the messages discussing it)

 

If it weren't for people like IronMan (but mainly just IronMan :D), this forum would be a lot more hectic and half of the problems we have would take forever to be fixed, so as always thanks for all the help @ntsmkfob and @IronManJFF for you help with this particular problem.

Link to comment
Share on other sites

Okay so I re-read your post after waking-up with a cup of tea, and understood what I didn't before.... :whistle:

 

So I started the update process, let it fail, sudo nano'd the com.apple.boot.plist to add the kernel flag, rebooted and selected the boot.efi from the installer files.

 

And now I'm happy to say that I'm running 10.14.6!! :thumbsup_anim:

 

569488305_Screenshot2019-08-07at12_54_22.png.10a0da932a850c9d48c070e7e222e4f3.png

 

So you can pretty much forget about my previous post hehehe

 

And thanks again, for your help! 

Link to comment
Share on other sites

Update ... High Sierra SecurityUpdate 2019-004 contains some firmware update so we have to adjust Defaults.plist (my guess is that the latest Mojave Update contains it also)

 

 

Example iMac13,2

<key>BiosDate</key>

<string>06/13/2019</string>

<key>BiosVersion</key>

<string>IM131.88Z.F000.B00.1906132045</string>

 

 

EFIPayloads:

 

EFIPayloads:

 

- IM101.88Z.F000.B00.1906141458

- IM111.88Z.F000.B00.1906132358

- IM112.88Z.F000.B00.1906132310

- IM121.88Z.F000.B00.1906140041

- IM131.88Z.F000.B00.1906132045

- IM141.88Z.F000.B00.1906132045

- IM142.88Z.F000.B00.1906131923

- IM143.88Z.F000.B00.1906131924

- IM144.88Z.F000.B00.1906131929

- IM151.88Z.F000.B00.1906132222

- IM161.88Z.F000.B00.1906140921

- IM162.88Z.F000.B00.1906140921

- IM171.88Z.F000.B00.1906171551

- IM181.88Z.F000.B00.1906171613

- IM183.88Z.F000.B00.1906171613

- MB101.88Z.F000.B00.1906171613

- MB61.88Z.F000.B00.1906140014

- MB71.88Z.F000.B00.1906140026

- MB81.88Z.F000.B00.1906140921

- MB91.88Z.F000.B00.1906171551

- MBA31.88Z.F000.B00.1906132254

- MBA41.88Z.F000.B00.1906140715

- MBA51.88Z.F000.B00.1906132037

- MBA61.88Z.F000.B00.1906131925

- MBA71.88Z.F000.B00.1906140921

- MBP101.88Z.F000.B00.1906131920

- MBP102.88Z.F000.B00.1906131816

- MBP111.88Z.F000.B00.1906132059

- MBP112.88Z.F000.B00.1906132051

- MBP114.88Z.F000.B00.1906140921

- MBP121.88Z.F000.B00.1906140921

- MBP131.88Z.F000.B00.1906171613

- MBP132.88Z.F000.B00.1907242326

- MBP133.88Z.F000.B00.1907242326

- MBP141.88Z.F000.B00.1906171613

- MBP142.88Z.F000.B00.1907250028

- MBP143.88Z.F000.B00.1907242326

- MBP61.88Z.F000.B00.1906132235

- MBP71.88Z.F000.B00.1906132329

- MBP81.88Z.F000.B00.1906132217

- MBP91.88Z.F000.B00.1906131919

- MM41.88Z.F000.B00.1906132344

- MM51.88Z.F000.B00.1906131918

- MM61.88Z.F000.B00.1906131921

- MM71.88Z.F000.B00.1906140923

- MP61.88Z.F000.B00.1906132222

 

and EFIVersion is now at

<key>EfiVersion</key>

<string>287.0.0.0.0</string>

You can see this when looking at the FirmwareUpdate file

Link to comment
Share on other sites

Hi All, and thanks for the valuable thread!

May anybody share step by step guide to enable both HD4000 graphics and discrete card? with bios setup for graphics? Is it possible at all with HighSierra on QUO motherboard?

OsX HighSierra, firmware Z77MXQUOAOS.H20.CPWN-APFS-10.13.5.ROM, iMac 13.1 with default.plist from this forum.

The reason I'm asking is that I have black screen when playing back clips with HEVC in FinalCut. Otherwise quicktime plays HEVC files just fine. My card is Saphire Pulse Amd Radeon RX 580. Any suggestions would be appreciated.

Thanks!

Link to comment
Share on other sites

With dual monitors ? or you only want 1 display but with Intel Quick Sync still enabled on iGPU? (made it work recently on 10.13.6 but haven't published anything because Mojave does not boot that setup )

 

Note : HEVC (H.265) support is not there in 3rd Gen Intel Core CPU.

Edited by IronManJFF
Link to comment
Share on other sites

3 hours ago, IronManJFF said:

With dual monitors ? or you only want 1 display but with Intel Quick Sync still enabled on iGPU? (made it work recently on 10.13.6 but haven't published anything because Mojave does not boot that setup )

 

Note : HEVC (H.265) support is not there in 3rd Gen Intel Core CPU.

Hello IronManJFF!

Thanks! Yes, single monitor and just to have Intel QuickSynk enabled on iGPU. Noted that I should rather double check the processor and upgrade it firstly. All this for having HEVC clips viewable at FCP X. Other reason of black screen for HEVC clips might be that my RX580 is not recognised by FCP X properly thus not operating properly. QuickTime plays the clips without any issues though. I will try to upgrade processor anyway. Thanks!

Link to comment
Share on other sites

You cannot upgrade CPU to a newer generation. But you can still get Intel QuickSync with H.264  and another good side effect is that you will be able to AirPlay and play DRM protected movies (I was not able to play my IronMan 2 movie on my hack before this) but first you need to upgrade the firmware to the latest

because you will need DBounce (which I built into this one) to invoke DevProp.efi to inject the device properties then Lilu + WhateverGreen in /L/E and a couple of tweaks into BIOS settings.

Hopefully it will work the same with RX580 than with my GTX970

Edited by IronManJFF
Link to comment
Share on other sites

5 hours ago, IronManJFF said:

You cannot upgrade CPU to a newer generation. But you can still get Intel QuickSync with H.264  and another good side effect is that you will be able to AirPlay and play DRM protected movies (I was not able to play my IronMan 2 movie on my hack before this) but first you need to upgrade the firmware to the latest

because you will need DBounce (which I built into this one) to invoke DevProp.efi to inject the device properties then Lilu + WhateverGreen in /L/E and a couple of tweaks into BIOS settings.

Hopefully it will work the same with RX580 than with my GTX970

Thanks again, IronManJFF! I will try this firstly then.

Link to comment
Share on other sites

First attempt @ Catalina Developer Beta... it installing now on a external SSD drive..good news is Installer is running ...Install Completed... First Boot in Progress...stuck to where the UI would start IMG_0055.thumb.jpg.067b13aaad12e70669086912ac3dd6bb.jpg ...

 

to be continued...

Edited by IronManJFF
Link to comment
Share on other sites

23 hours ago, alberto21 said:

@IronManJFF would you give a try to opencore ? I am about to give it a try, I’m just wondering if I’ll have to deal with SSDT/DSDT.

First attempt unsuccessful .. (using binary packages)

Stuck @ Loaded Configuration .. not sure if I should get a message when it is done parsing the config file...

 

I think because Ozmosis is already in firmware .. that might be conflicting

Edited by IronManJFF
Link to comment
Share on other sites

Yes definitely because of what’s in the firmware. From what I understood so far it should be alone in the EFI partition. I don’t have my Quo next to me, so no way to try yet.

 

Edited by alberto21
Link to comment
Share on other sites

On 8/15/2019 at 1:21 AM, IronManJFF said:
You cannot upgrade CPU to a newer generation. But you can still get Intel QuickSync with H.264  and another good side effect is that you will be able to AirPlay and play DRM protected movies (I was not able to play my IronMan 2 movie on my hack before this) but first you need to upgrade the firmware to the latest
because you will need DBounce (which I built into this one) to invoke DevProp.efi to inject the device properties then Lilu + WhateverGreen in /L/E and a couple of tweaks into BIOS settings.
Hopefully it will work the same with RX580 than with my GTX970


Hey, I cracked my wallet and went for a RX580.
So about your topic, could it work with: lilu + whatevergreen loaded from EFI/OZ/DARWIN/EXTENSIONS/COMMON, instead of /L/E ? And about the tweaks in the bios you’re talking about: what are they ?
About Quicksync: do you have the use of the shiki kext in mind to activate it or something else?
So far when I’m trying to play DRM protected streamed content I’ve got a red screen instead of the video + sound playing.

Thanks for your help.

Edited by alberto21
Link to comment
Share on other sites

Yes it could work if you put Lilu and WEG in EFI partition (i have not tested it but I see no reason why not).

BIOS tweaks are iGPU=Enabled and Init DisplayFirst=PEG

For Lilu/WEG to kick in you need to inject the iGPU id... normally You could do that with Defaults.plist but it did not work for me (probably because it sees the dGPU and does not bother ) that is why I resorted to Devprop.efi to inject a headless id for my iGPU.

About OpenCore: I will experiment a bit more for educational purpose... still trying to to get it to present me a boot picker.

Link to comment
Share on other sites

×
×
  • Create New...