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

[kevino83]

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 )


Anyway really thanks for you help!
and sorry for my not so good english

 

[marth]

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.

 

[marth]

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?

 

[UtterDisbelief]

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.

 

[marth]

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.

 

[UtterDisbelief]

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.

 

[marth]

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.

 

[Middleman]

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.

 

[marth]

@Middleman, thank you for assembling. I was guided by it when I bought the z490D.
I am using your version from the first post (EFI for High Sierra) and configurator for 0.6.5. The version number is not important to me. The main thing is that everything works. Only annoying messages at system startup.

 

[Middleman]

@Middleman, thank you for assembling. I was guided by it when I bought the z490D.
I am using your version from the first post (EFI for High Sierra) and configurator for 0.6.5. The version number is not important to me. The main thing is that everything works. Only annoying messages at system startup.

Great!
As for the annoying messages, you can remove the -v boot-arg under the NVRAM section.

You’re welcome!