Contribute
Register

[GUIDE] OC 10.13.6 Z490 Gigabyte Aorus Xtreme + Core i5 10400 + Nvidia GTX 1060

Joined
Nov 20, 2011
Messages
8
Motherboard
Gigabyte z490m
CPU
i7-10700
Graphics
RX 560
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. iOS
I tried to use Migration Assistant, can it be that do not works on the same drive?
sorry, I was on 11.5.2 vs 11.0.1, after update and migrating in 2/3 hours it seems it came back working, in a new installation on the same disk.

It seems that you can install directly on the non bootable to restore it, but I tested only on the fresh new installation and not the original one, I can not guarantee no data loss.

Anyway migration assistan seems working for me ;)
In the next days I can tell by sure

Thanks ;)
 
Last edited:
Joined
May 11, 2011
Messages
1,736
Motherboard
Gigabyte B550 Vision D
CPU
Ryzen 5900X
Graphics
RX 6800
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. Power Mac
  2. PowerBook
Mobile Phone
  1. iOS
really thanks for your reply!
I think my problem here is related to the fact that high sierra tried to do something on the other disc (reading, trim, indexing, I don't know...).
The same operetion on a macbook pro 2019 doesn't cause this.
On this computer I initially created my hack directly for big sure and i was quitly proud of it :(

I'm really the only one that suffer this?

Ps. I never tried to boot big sur from high sierra, I used an usb open core 0.6.8 for it and for big sur I had a complete installation with OC 0.7.2 and port mapping.

This means that next time I want to use my hSierra I need to disconnect every BigSur drive from the system?

Anyway on a different bigsur installation I can read correctly and see the partitions in finder, but is a little messed in disk utility or in Open core menu :(

I had reread your earlier post to see what it was you were trying to achieve. So you were basically trying to read/install an existing native macOS Macbook High Sierra install using a hackintosh?

Okay. Your problem with as to why it didn't work was threefold. First was the system format. While HFS+ and APFS can be read by High Sierra, Big Sur doesn't use HFS+ anymore. High Sierra was indeed the first macOS to implement APFS, but the implementation has since been updated with Big Sur. The biggest difference between HFS+ and APFS is the use of 'containers' to separate user data and system data. If you've not got the correct credentials the system simply will not allow you in. In addition, data encryption (FileVault) has been added with Big Sur which probably explains why your High Sierra install has difficulty reading a Big Sur drive.

Secondly, Mac native systems do not use any EFI folders for booting, only Clover and Opencore.

Thirdly a hackintosh drive will contain an EFI partition, whereas on a Mac native drive this partition may exist but will be mostly empty. These are the reasons why the partitions are not being read correctly under Disk Utility.
Either that or the drive data has been corrupted. That's why you must always install with a fresh drive on a hackintosh build.

Anyways good to hear you finally solved it.
 
Joined
Nov 20, 2011
Messages
8
Motherboard
Gigabyte z490m
CPU
i7-10700
Graphics
RX 560
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. iOS
yeah, but honestly I dind't understood correctly.

1) sure, I was reading and existent exernal High sierra, with a OC bootloader on USB key (v 0.6.8). Installed using APFS first version (I tried it soon).
2) thanks to your guide I was able to boot it and use it with intel gen 10 cpu and z490m
3) it's expeted it founds some incompatibility with the existent BigSur drive, but strangely it can read it messing up with the partitions and the problem is recursive (if I enter highsierra with bigsur drive connected I will lose the bootability)
4) the internal drive with BigSur has it's own OC v 0.7.2

the same operation betweens 2 differnet bigsure drive go smooth with no problem at all.

I think like you said that the problem was related to new apfs used in bigsur, but really it was delusional for me (I think it's Apple that released a premature file system)


I have to find a way to boot from high sierra without unmont fisical nvme drive (with bigsur), I will try to disable by bios (i'm a little scared :D)


Anyway really thanks for you help!
and sorry for my not so good english ;)
 
Joined
Aug 29, 2021
Messages
18
Motherboard
Gigabyte Z490 Vision D
CPU
i9-10850K
Graphics
GTX1080ti
Hi, @Middleman! I am using your build to run High-Sierra with GTX1080ti graphics card. I am unable to fully launch hardware acceleration on the integrated video adapter. Can you help? Nvidia driver loaded and working.
Another question about the opencore build number. The Hackintool program reports that kernel 0.5.9 is loaded, and you write that the assembly is on version 0.6.5.
 

Attachments

  • Screen Shot 2021-09-06 at 18.56.50.png
    Screen Shot 2021-09-06 at 18.56.50.png
    95.2 KB · Views: 7
  • Screen Shot 2021-09-06 at 18.50.11.png
    Screen Shot 2021-09-06 at 18.50.11.png
    19.1 KB · Views: 7
  • config.plist
    29.1 KB · Views: 7
  • EFI.zip
    25.3 MB · Views: 7
Joined
Aug 29, 2021
Messages
18
Motherboard
Gigabyte Z490 Vision D
CPU
i9-10850K
Graphics
GTX1080ti
I was able to run hardware acceleration on the iGPU with these settings. But when working on an integrated video card, a lot of artifacts appear (window shaking, disappearing icons, etc.). Is it possible to solve this problem?
 

Attachments

  • config.plist.workigpu.plist
    27.8 KB · Views: 9
  • Screen Shot 2021-09-07 at 00.04.34.png
    Screen Shot 2021-09-07 at 00.04.34.png
    63.8 KB · Views: 8

UtterDisbelief

Moderator
Joined
Feb 13, 2012
Messages
6,583
Motherboard
Gigabyte Z490i Aorus Ultra - OC 0.6.8
CPU
i5-10600K
Graphics
GT710 - 1920x1080
Mac
  1. iMac
  2. Mac mini
Classic Mac
  1. eMac
  2. iBook
Mobile Phone
  1. iOS
I was able to run hardware acceleration on the iGPU with these settings. But when working on an integrated video card, a lot of artifacts appear (window shaking, disappearing icons, etc.). Is it possible to solve this problem?

Hi there.

Bear in mind that if you are running the iGPU as a secondary graphics processor to the GTX1080 for rendering tasks only then you need to set the ig-platform-id to one of the "headless" variety like: 0300C89B.

For Comet Lake this is the correct ID rather than spoofing an earlier one.
 
Joined
Aug 29, 2021
Messages
18
Motherboard
Gigabyte Z490 Vision D
CPU
i9-10850K
Graphics
GTX1080ti
I tried booting in headless configuration (monitor connected to NVidia) with settings:
AAPL,ig-platform-id 03009BC5
device-id 9BC50000

I also tried such combinations:
AAPL,ig-platform-id 0300C89B
device-id 9BC50000

AAPL,ig-platform-id 0300C89B
device-id C89B0000

There is still no support for H264 and HEVC. At the same time, there is no iGPU in the system properties. iGPU is enabled in BIOS.
 

Attachments

  • Screen Shot 2021-09-07 at 00.46.02.png
    Screen Shot 2021-09-07 at 00.46.02.png
    51.4 KB · Views: 10
  • Screen Shot 2021-09-07 at 00.49.22.png
    Screen Shot 2021-09-07 at 00.49.22.png
    58.8 KB · Views: 10

UtterDisbelief

Moderator
Joined
Feb 13, 2012
Messages
6,583
Motherboard
Gigabyte Z490i Aorus Ultra - OC 0.6.8
CPU
i5-10600K
Graphics
GT710 - 1920x1080
Mac
  1. iMac
  2. Mac mini
Classic Mac
  1. eMac
  2. iBook
Mobile Phone
  1. iOS
I tried booting in headless configuration (monitor connected to NVidia) with settings:
AAPL,ig-platform-id 03009BC5
device-id 9BC50000

I also tried such combinations:
AAPL,ig-platform-id 0300C89B
device-id 9BC50000

AAPL,ig-platform-id 0300C89B
device-id C89B0000

There is still no support for H264 and HEVC. At the same time, there is no iGPU in the system properties. iGPU is enabled in BIOS.

Okay ...

Well I suspect that High Sierra has never heard of Comet Lake iGPUs so using those ig-platform-id's is probably not going to work, headless or otherwise. My oversight. I should have thought about that earlier.

So I'd recommend using older IDs, spoofing them in config.plist such as a Kaby Lake or Coffee Lake iGPU device-ID as you did originally, but as headless. For example CL = 03009B3E etc. You might also spoof the CPU correctly too - Cpuid1Data = EA060900 00000000 00000000 00000000. Cpuid1Mask = FFFFFFFF 00000000 00000000 00000000.

Worth trying.

:)
 
Joined
Aug 29, 2021
Messages
18
Motherboard
Gigabyte Z490 Vision D
CPU
i9-10850K
Graphics
GTX1080ti
Hooray!
The following settings worked for me:
AAPL, ig-platform-id 00009B3E
AAPL, slot-name Internal @ 0.2.0
device-id 9B3E0000
framebuffer-fbmem 00009000
And reset after that nvram

Interestingly, in the configuration with the head (the monitor is connected to the iGPU), there are many artifacts in the image.
But with a monitor connected to nvidia, everything works.
 

Attachments

  • Screen Shot 2021-09-07 at 01.21.06.png
    Screen Shot 2021-09-07 at 01.21.06.png
    72 KB · Views: 7
Joined
May 11, 2011
Messages
1,736
Motherboard
Gigabyte B550 Vision D
CPU
Ryzen 5900X
Graphics
RX 6800
Mac
  1. iMac
  2. MacBook
  3. MacBook Air
  4. MacBook Pro
  5. Mac mini
  6. Mac Pro
Classic Mac
  1. Power Mac
  2. PowerBook
Mobile Phone
  1. iOS
Hi, @Middleman! I am using your build to run High-Sierra with GTX1080ti graphics card. I am unable to fully launch hardware acceleration on the integrated video adapter. Can you help? Nvidia driver loaded and working.
Another question about the opencore build number. The Hackintool program reports that kernel 0.5.9 is loaded, and you write that the assembly is on version 0.6.5.
Firstly congrats on your setup! It’s nice to see it work on a first try.

As to enabling the integrated adapter with the Nvidia shouldn’t be a problem. Just make sure that it is enabled in BIOS and your IGPU device-id corresponds to 3E9B0003 and AAPL,ig-platform-id is 03009B3E. Our admin Utterdisbelief is absolutely correct - High Sierra will not recognise Comet Lake IGPU so you must use a Coffee Lake device id in this case.

If at a later date you plan to upgrade (say Catalina/Big Sur), just remember to change the above values to C59B0003 and 03009BC5. This value is derived from your Intel i9 CPU's Ark info page > https://ark.intel.com/content/www/u...0850k-processor-20m-cache-up-to-5-20-ghz.html

As for the OC version, that is not surprising. User VectorSeven (whom I derived the build from originally) never stated the exact version of OC he had used. I just estimated that from the dates of the files. But my later builds were built on OC 0.6.2 and OC 0.6.5.
 
Top