Jump to content
Slice

[HOW TO] Make Radeon {Desktop or Mobility} be working by using Clover

423 posts in this topic

Recommended Posts

As I see many novices in the forum ask "How to make my Radeon working? I have bad resolution, no QE/CI...." and so on. They come to the section and have no find an answer here because all Radeons are different and they don't know where else they read about this.

I want to explain all steps needed for launching the Radeon family of videocards.

 

Bootloader.

I will speak about Clover because I maintain this bootloader to know recent hardware and modern OSX. Not sure if you will have the same result with other bootloaders. I am carefully checking the injecting of ATI card and correcting it times to times. I am also accessible for bug reports.

 

OSX version.

Older card require older system, newer cards require new system.

ATIRadeon9000 is possible to launch under Tiger.

ATIRadeonMobilityX1400 requires 10.5-10.6. See RadeonHD topic.

As I see RadeonHD3xxx was successful only in 10.5

For new AMDRadeonHD7xxx there must be 10.8.3+ system.

 

DeviceID.

This must be the first question before asking about the card.

You may know the device-id from Windows->DeviceManger->VideoCard.properties->compatibleIDs

You may boot into system in safe mode (key -x) and see system profiler

 

And you may boot into Clover GUI, press F2 and get preboot.log. Find here something like

2:709  0:000  PCI (00|01:00.00) : 1002 6758 class=030000
2:709  0:000  Found Radeon model=AMD Radeon HD 6670 Series

It means my DeviceID=6758 (these are hex numbers)

Then you must check that Apple's drivers support your DeviceID. If not then add it!

For example HD7850 has DeviceID=6819. If we look into ATI7000Controller (AMD7000... in new systems) we find 6818 here but no 6819!


 

IOName

AMD7000Controller
IOPCIMatch
0x26001002 0x22001002 0x67901002 0x67981002 0x679A1002 0x679E1002 0x67801002 0x68201002 0x68211002 0x68251002 0x68271002 0x682D1002 0x682F1002 0x68391002 0x683B1002 0x683D1002 0x683F1002 0x68001002 0x68061002 0x68081002 0x68181002
 

 

I show you how to do this with terminal commands. Launch /Application/Utilities/Terminal.app. Type in opened window:


cp /System/Library/Extensions/ATI7000Controller.kext/Contents/Info.plist ~/Desktop

So you get a copy of the Info.plist on Desktop. Edit it with TextEdit. Change 68181002 -> 68191002.

Don't edit this file directly in the system folder! 

Then copy back by terminal. Don't use finder to copy kexts! They will have wrong permissions in this case.

sudo cp ~/Desktop/Info.plist /System/Library/Extensions/ATI7000Controller.kext/Contents/
sudo rm -r -v /System/Library/Caches/com.apple.kext.caches/*

Second command make sure next reboot the kext will use your edited info.plist.

The same operation you must do with a kext AMDRadeonAccelerator or ATIRadeonX2000 or other one. Check all candidates if they contain such list of possible IDs and choose closest to you.

 

FakeID

Since Clover revision 1971+ you may just inject new DeviceID into DSDT instead of correcting kexts. See instruction here.

 

GraphicsEnabler or Injector

OSX needs to know some properties (Model name, Family, etc...) that must be somehow injected at boot time. Yes, also real Macs got DeviceProperties string from firmware.

Alternatives:

1. Set InjectATI=Yes in Clover (same as GE=y in Chameleon).

2. Use custom string made with gfxutil. For whom who knows.

3. Write _DSM into DSDT. You should know what to write.

4. Use some kext like ATY_init.kext or Natit.kext. If you are sure that the kext is for your card namely.

I want to say that all this methods make the same thing. Differencies in their tuning.

The Clover do this automatically for most known cards at this moment.

 

Connectors.

As you may see to start HD5000-7000 some strange names used: Pithecia, Orangutan, Elodea... What are they?

They are configs for framebuffer. Predefined configs how connectors are solded for cards used in real Macs. Strange but these configs rear coincide with PC card. Usually gurus make advice "choose a framebuffer that most appropriate for your card". The chances 1:10. In most cases you may find a FB name that gives you main monitor working. Or nothing at all.

Great respect to bcc9 who gives us a method to correct one of config to be exactly for you. See here.

My retelling for Clover is here

Success example in the thread in posts 44-52

 

Radeon Mobility

I tested Clover's methods with two users having Mobility Radeon HD5470 and HD5650M. We found that full memory and QE/CI will be achieved if we set in Clover's config

LoadVBios=Yes

even thou no file with bios is provided. This is the key to make Radeon Mobility working!

Other problem is bad gradients or artifacts. For this case Clover accept the key

InjectEDID=Yes

and sometimes you also need to inject CustomEDID.

See Clover instructions for details.

 

And my results.

Gigabyte Radeon HD6670

	<key>Graphics</key>
	<dict>
		<key>GraphicsInjector</key>
		<true/>
		<key>InjectEDID</key>
		<true/>
		<key>FBName</key>
		<string>Ipomoea</string>
		<key>LoadVBios</key>
		<false/>
		<key>VideoPorts</key>
		<integer>3</integer>
		<key>PatchVBios</key>
		<true/>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>KernelCpu</key>
		<false/>
		<key>ATIConnectorsController</key>
		<string>6000</string>
		<key>ATIConnectorsData</key>
		<string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string>
		<key>ATIConnectorsPatch</key>
		<string>040000000403000000010000100001061000000010000000000100000000000100080000040200000001000012040403</string>


VTX Radeon HD5570

	<key>Graphics</key>
	<dict>
		<key>PatchVBios</key>
		<false/>
		<key>FBName</key>
		<string>Baboon</string>
		<key>VideoPorts</key>
		<string>3</string>
		<key>GraphicsInjector</key>
		<string>Yes</string>
		<key>LoadVBios</key>
		<string>No</string>
	</dict>

	<key>KernelAndKextPatches</key>
	<dict>
		<key>Debug</key>
		<false/>
		<key>KernelCpu</key>
		<false/>
		<key>ATIConnectorsController</key>
		<string>5000</string>
		<key>ATIConnectorsData</key>
		<string>040000001400000000010000010201030008000000020000007100002205020110000000100000000001000000100002</string>
		<key>AppleRTC</key>
		<true/>
		<key>ATIConnectorsPatch</key>
		<string>040000001400000000010000010001040008000000020000007100002200020510000000100000000001000000000002</string>
		<key>AsusAICPUPM</key>
		<false/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Name</key>
				<string>AppleAHCIPort</string>
				<key>Find</key>
				<data>RXh0ZXJuYWw=</data>
				<key>Replace</key>
				<data>SW50ZXJuYWw=</data>
			</dict>
		</array>
	</dict>

See PatchVBios=No

for this card "yes" leads to black screen. Use with precautions.

 

A sample for Radeon R7 240

 

UPDATE for ElCapitan.

It seems has more problems. My HD6670 is not working in ElCapitan OOB unlike Mavericks.

I had to set FakeID=0x67401002 as correspond to real iMac12,2 and set this model in SMBIOS section.

It related to GraphicsPM or GraphicsControl.

Look these kexts to decide what you can do for your configuration.

 

HighSierra requires change these kexts by version from Sierra 10.12.6

for Radeon HD6xxx

AMDRadeonX3000.kext
AMDRadeonX3000GLDriver.bundle
IOAccelerator2D.plugin
IOAcceleratorFamily2.kext
for Radeon HD7xxx and up
AMDRadeonX4000.kext
AMDRadeonX4000GLDriver.bundle
IOAccelerator2D.plugin
IOAcceleratorFamily2.kext
 
Black screen after wake problem
resolved by follow method

radeon_bios_decode.0.2.zip

ati-personality.pl.0.15.zip

ati-personality.pl.0.15a.zip

Share this post


Link to post
Share on other sites
Advertisement

Hello and i thanks for your tuts.

please guid me for radeon 7650m .

i have vaio sve15117fdb and my graphics card is radeon 7650m
Graphics Card Manufacturer Powered by AMD
Graphics Chipset AMD Radeon HD 7500M/7600M Series
Device ID 6841
Vendor ID 1002
Subsystem ID 90AB
Subsystem Vendor ID 104D
Graphics Bus Capability PCI Express 2.0
Maximum Bus Setting PCI Express 2.0 x16
BIOS Version 013.012.000.041
BIOS Part Number HK5.019
BIOS Date 2012/07/10
Memory Size 1024 MB
Memory Type DDR3
Core Clock in MHz 500 MHz
Memory Clock in MHz 900 MHz
Total Memory Bandwidth in GByte/s 28.8 GByte/s
It is based on the same chip as the Radeon HD 6650M, but has a lower core clock of 450 – 550 MHz.
The power consumption of the chip and 3D performance is similar to the Radeon HD 6630M.

is this tuts worked for my graphics card?

if = yes

which of  kext and framebuffer is appropriate for i changed these for my Graphics card worked based in tusts?

please help me

I've spent a lot of time to do this please help me :help::)

Share this post


Link to post
Share on other sites

I think your card ID=6841 will be best with FBName=Pondweed.

This ID is native so you don't need Info.plist patch.

LoadVBios=true is required.

Share this post


Link to post
Share on other sites

My card is a 7850 what exactly do i need to do the card ID is 6819 also running Mavericks DP5 so i would say i have to edit different kext files ? 

Share this post


Link to post
Share on other sites

My card is a 7850 what exactly do i need to do the card ID is 6819 also running Mavericks DP5 so i would say i have to edit different kext files ? 

Yes, exactly that I said in topic. ATI7000Controller and AMDRadeonAccelerator or AMDRadeonX4000.kext

You may not set InjectATI because this card is natively supported by RadeonFramebuffer. See results             #22            

Share this post


Link to post
Share on other sites

Hello

i install maverick with my hack and update Bootloaders by Chameleon-2.2svn-r2256 but because not worked my lvsd and i have to install Clover_v2_r1958 (until base in tuts worked my garphics card and lvsd)(my partition is Guid and i install bootloader in installed mac drive)

but i cant boot to menu operation select and i see below screen and then clicked in continue i see this screen again (i change boot drive but not save change this below menu).

please giude me: how to install Clover? or how to Configured  (by Clover Configurator 2.6) until i can go to operation select menu of clover?

 

57627385478929559744.jpg

Share this post


Link to post
Share on other sites

Go to "Boot Maintanence Manager" -> Boot from File ->

then navigate to CloverX64.efi if it exists anywhere.

 

On the photo you see SetupBrowser from CloverEFI, it means you passed process up to boot file but have no find EFI folder.

How to install Clover? By installer! Click "OK".

Share this post


Link to post
Share on other sites

thanks for attention .CloverX64.efi if it not exists (in file explorer

56652189337505978316.jpg

 

45975910324933894881.jpg

i dont see any file or path for efi file..

i install clover by installer.

how to install clover is correct ?

Share this post


Link to post
Share on other sites

no i use vmware only for efi folder in external hard and install clover in external hard (in hackintosh drive) because my hackintosh not boot when computer restarted or turn on computer for login and install clover.

my computer not recognize my hackintosh boot.

Share this post


Link to post
Share on other sites

no i use vmware only for efi folder in external hard and install clover in external hard (in hackintosh drive) because my hackintosh not boot when computer restarted or turn on computer for login and install clover.

my computer not recognize my hackintosh boot.

I never saw computer "not recognize hackintosh boot". Check your BIOS once again.

Clover Installer uses device such as /dev/disk1s1. But in case of VMWare it will not the case and your installation failed.

You must boot real OSX any possible way and then install clover on real HDD.

 

 

To moderators.

I think these posts must be moved to Clover discussion. (I can't)

Share this post


Link to post
Share on other sites

hello vrondena

yes (sve15117fdb)

this model not support UEFI

i have above problem with clover ( also when i boot my laptop with clover iso , this not recognize my hfs mac partition and recognize windows partition in my internal and external hard)

please guide me

Share this post


Link to post
Share on other sites

as far as my experiences and knowledges, clover and vmware forgotten for the moment would not do more than chameleon-chimera-enoch

the problem is the correct LVDS connector configuration.but I also do not know how to do this, and in this forum who can do it reminds us a link or a guide instead of helping.for as for you. if you dont have problems to format the disk. install in EFI mode, from your usb , create 1 partition (guid). install osx .reboot from usb,install boot on osx (suggest enoch) whit boot camp create partition fat32 (for install win).install all kexts you won't (for me on ML almost all work) and like me  wait ...... for lvcd 

if you need, ask

Share this post


Link to post
Share on other sites

Hey nice tut! I think I'm going to give this a try. I've got the HD6990 myself and I tried something similar using Chameleon and AtiConfig=Gibba (which I read in another thread). But none of my screens were working or I was getting full white screens.

 

Do you think using this exact tutorial (Clover bootloader etc.) will work for me? The HD6990 has 2 GPU's and such (seems a very specific card to me).

Share this post


Link to post
Share on other sites

This was the most useful topic I have found about ATI 7xxx, It is easy to follow all the steps and i finally got my 7850 working :)
Without applying other peoples kexts it is far better, no kernel panics, Clover works like a charm, even patched my DSDT for Audio...

Thank you very much for the time spent to do this!

By the way, is there any discussion/troubleshooting topic concerning the sleep fix, white screen bug?
If so, please point me the topic ;)

Thanks!

Share this post


Link to post
Share on other sites

This was the most useful topic I have found about ATI 7xxx, It is easy to follow all the steps and i finally got my 7850 working :)

Without applying other peoples kexts it is far better, no kernel panics, Clover works like a charm, even patched my DSDT for Audio...

 

Thank you very much for the time spent to do this!

 

By the way, is there any discussion/troubleshooting topic concerning the sleep fix, white screen bug?

If so, please point me the topic ;)

 

Thanks!

White screen bug can be eliminated by:

1. Sleep trick. 

2. Install FBRotate into login items.

3. Use UEFI boot and set BIOS to use UEFI VideoBIOS.

4. Use Mavericks DP5 (? I am not sure).

Sorry that I didn't provide you links. All information is on this forum or on russian forum applelife.ru

Share this post


Link to post
Share on other sites

Hi:

I have C2D 8300, GA P43T ES3G, Ati Radeon HD 4850, 8 GB ddr3.

 

I tried to install Mountain Lion with the Ati 4850 and Clover v2 r2061.

I configured config.plist like the image. The point is that it only recognize 5 MB and the resolution is 1280x1024.

 

dhas.jpg

 

Then, I changed like the image. Now, it recognize 6 MB but the resolution is 1680x1050.

 

qnse.jpg

 

I used chameleon and it worked good.

 

c1be.jpg

 

With the systeminfo, in clover and chameleon the kexts are not the same and in chameleon there are more.

 

jmk9.jpg

 

Can you help me with the correctly configuration of the archive config.plist? 

 

Thanks you.

 
 
           or
 

Share this post


Link to post
Share on other sites

Where is the kext ATIRadeonX2000 when booted by Clover?

There are in S/L/E. Using systeminfo, there are not  ATIRadeonX2000 and ATI4800Controller.

 

And that is why I asked If my config.plist is incorrectly.

 

kfta.jpg
 
 
 
I try to upload my config.plist but I can not. However, you can find the link in my first post.
 
Thanks a lot.
 
PS: I'm going to reinstall Mountain Lion  from scratch so I can check it out and I'll let you the results. Sorry for my bad English.

Share this post


Link to post
Share on other sites

Tnx, but there is too many stuff for so many card that i can find what i need. . .so can someone tell my what i need to to to get acceleration on 10.8.3 whit clover . . .i can enter in 10.8.3 whit clover in 1080p res. but its glichy. . .there is no acceleration. . .

post-968257-0-59287900-1378503061_thumb.jpg

 

 

tnx

Share this post


Link to post
Share on other sites

Tnx, but there is too many stuff for so many card that i can find what i need. . .so can someone tell my what i need to to to get acceleration on 10.8.3 whit clover . . .i can enter in 10.8.3 whit clover in 1080p res. but its glichy. . .there is no acceleration. . .

 

 

 

tnx

What should I say?

Share this post


Link to post
Share on other sites

What should I say?

HE HE. . .I think i found the problem but no solution, the problem is in OpenGL ( AMDRadeonX4000GLDriver ). . .

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By karthiksh1989
      can somebody walkthrough with the mojave installation guide?
      i have a mac high sierra 13.6 version on my macbook pro and want to install mojave on my desktop
      Exact config is Gigabyte gaming wifi 7 motherboard amy ryzen 7 2nd gen 2700X processor Gigabyte G1 8GB grapgic card VEGA 64
      running 2 nvme Samsung 256gb cards and 1 intel 180gb ssd internal and 1tb WD HDD, with 64 GB 3200Mhz Ram
       
      https://wa.me/919611736534 (whatsapp)
    • By Fede1132
      Hi guys i have a problem install macOs Mojave on my PC, I have this configuration:

      CPU: Ryzen 7 2700X;
      GPU1: GTX 970 Strix(For game rendering and 144Hz Monitor);
      GPU2: GTX 750ti Strix(For 2nd monitor rendering to get 100% performances from 1st 144Hz Monitor);
      MotherBoard: MSI x470 GAMING PLUS
      Hard Disk 1 (Windows 10): Samsung EVO M.2;
      Hard Disk 2 (For Storage): RAID (1) between two hard disks;
      Hard Disk 3 (For Mojave): Kingston SSD 120GB;

      I have created my USB with this:
       
      Create Bootable USB Code: sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB -- /Applications/Install\ macOS\ Mojave.app -- nointeract && say Done. Clover Settings: Boot: Verbose; dart=0; nv_disable=0; kext-dev-mode=1; GraphicsEnabler=No; XMPDetection = No. Cpu: C6. Devices: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Inject (Full Enabled); Add ClockID (Full Enabled); FixOwnership (Full Enabled); Gui: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Enabled (Full Enabled); Screen Resolution: 1920x1080; Kernel and Kext Patches: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Apple RTC (Full Enabled); KernelPm (Full Enabled); SMBIOS: iMac(18,3); System Parameters: Inject Kexts = Yes; Inject System ID; Used Kexts: FakeSMC FakePCIID NVIDIA WEB LILU BIOS: VT-d = Disabled; XHCI Hand-Off = Enabled; Legacy USB Support: Enabled; Hard Disk: AHCI Mode; Selection Mode: Legacy + EUFI; Clover Install Log:
      Full Error Log:
       
    • By corbrink
      Hi,
      I have the following system:
      - Gigabyte Z370M-D3H M-ATX
      - Core i7-8700K Coffee Lake
      - Gigabyte Radeon RX 560 4GB
      - Crucial Ballistix 16GB DDR4
      - 960 EVO 1TB NVMe SSD
      - 850 EVO 500GB SSD
      - Crucial 500GB SSD
      - The 2 500GB SSD's run in Raid for data storage.
      - Western Digital 3TB HDD - Time machine
      - EFI here (too large to attach): EFI.zip

      Questions:
      1. I have a dual screen running from Radeon card, 1 on DP and 1 on HDMI. The one screen on DP goes randomly blank from time to time. Any ideas?
      2. I've read that the kexts should preferably be installed in /library/extensions. I would like to know what kexts should remain in the EFI. I read that you should install FakeSMC in both locations (EFI and L/E). If I follow this route must I change something in the config.plist?
      3. USB info in System Information (attached does not seem correct. I've followed the changes suggested but I'm not sure if this is the best it can be.
      4. Are there something in the EFI and config.plist I don't need or doing wrong?

      Feedback will be appreciated.


    • By 1Ale1
      Ciao a tutti, ultimamente ho deciso di mettermi al lavoro e fare un investimento a lungo termine comprando un fisso che ho assemblato pezzo dopo pezzo leggendo numerosi forum per essere bene informato sul miglior hardware che potessi ottenere per un Hackintosh ottimizzando al meglio i costi: ho finito così per comprare:
       
      Hardware:
       
       
      -Motherboard: Gigabyte Z390 Aorus Pro (Rev 1.0)
      -CPU: Intel i7 9700k raffreddato a liquido (CoffeLake)
      -GPU: AMD Radeon RX580 (avendo letto le eccellenti prestazioni a ottimo prezzo per MacOS)
      -RAM: 32GB DDR4 Crucial Ballistix Sport LT (4x8GB 3000MHz)
      -NVMe SSD Samsung 970 Evo 250GB M.2 dedicato solo a MacOS, nel secondo slot della Mobo M.2 avrei poi messo un Western Digital Blue da 250GB con Windows 10 su metà disco e per l'altra metà il Debian che sto utilizzando adesso
       
       
      Poi mi sono messo subito al lavoro per cercare di far partire questo benedetto MacOs su una macchina non ufficiale, ho tovato quindi questa guida su GitHub che era molto simile alla mia configurazione:
       
      https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Dopo aver fatto partire una macchina virtuale per configurare la USB come comunemente viene fatto, scaricando l'applicazione e facendo il "burn/copia dei file" di macOS su pennetta esterna rendendola bootabile solamente da un pc ufficiale mac, sono passato alla configurazione di Clover (l'EFI installer, cartella che allegherò qui sotto, ma prima leggete il problema): Ho messo i driver necessari, mettendo quelli che lui menzionava sotto la sezione "building the usb installer"
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/building-the-usb-installer
       
       
      Install Clover for UEFI booting only
      Install Clover to the ESP
      Under Drivers64UEFI:
      AptioMemoryFix (the new hotness that includes NVRAM fixes, as well as better memory management) (che poi ho dovuto rimuovere, leggi sezione https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md#fixing-kernel-panics-at-rebootshutdown)
      VBoxHfs-64.efi (or HFSPlus.efi if available) - one of these is required for Clover to see and boot HFS+ volumes. If you see the option to enable it in the installer, make sure it's selected - if you don't see it in the installer, verify that one of them exists in the EFI -> CLOVER -> drivers64UEFI folder
      ApfsDriverLoader - (Available in Dids' Clover builds - or here) this allows Clover to see and boot from APFS volumes by loading apfs.efi from ApfsContainer located on block device (if using AptioMemoryFix as well, requires R21 or newer)
       
      applicando piccole modifiche a causa di un errore già riportato da questa persona che ha scritto la guida di GitHub di sostituire AptioMemoryFix-64 (dalla cartella EFI/EFI/CLOVER/driver64UEFI) con OsxAptioFix2Drv-free2000, questa infatti riportava  quanto segue dopo aver detto di aver sostituito AptioMemoryFix-64.efi con OsxaptioFix2Drv-free2000:
       
      "I am told that there are downsides (that I don't fully understand yet) to using OsxAptioFix2Drv-free2000, so do this at your own risk."
       
      Ho configurato poi il config.plist
       
      Come diceva lui, partendo da questo file: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake e applicando le modifiche che sotto ha descritto, del tipo:
       
      Open coffeelake_sample_config.plist with Clover Configurator (right click → Open With → Clover Configurator)   In SMBIOS: - Click the button with an up/down arrow (middle right). Chose iMac18,3. This is important since we'll be connecting our monitor to the RX580. The HDMI port on our motherboard is NOT yet working for Hackintoshes. - Make sure the serial number generated is an iMac (mid-2017) by clicking Model Lookup. - Ensure that Check Coverage reports that the serial is NOT valid. You don't want to use somebody else's serial number. - While you're here, copy your Board Serial Number to your clipboard. You'll need it soon.
      In Rt Variables: Paste your Board Serial Number in the MLB field. Set CsrActiveConfig to 0x0 which enables SIP for extra security. This should work just fine for a Vanilla Hackintosh install and is how genuine Macs ship. In Boot: Change the Custom Flags to: shikigva=40 uia_exclude=HS14 (this disables onboard Bluetooth since we'll be using an external Broadcom Wi-Fi/Bluetooth adapter) In ACPI: Click List of Patches and enable the following: Change GFX0 to IGPU In Devices: Set Inject to 16. Now to enable our headless iGPU, we need to fake the device id. To do so, Click Properties, select PciRoot(0x0)/Pci(0x2,0x0). Then, click the + button to add a property. Add the following: Property Key: device-id Property Value: 923E0000 Value Type: DATA Click the Export Configuration button (bottom left), then Save As config.plist. Copy your newly generated config.plist to /EFI/CLOVER/ on your bootable USB key.  
      Impostazioni BIOS
       
      E avendo settato nel BIOS le impostazioni che questa perona configliava all'inizio della guida,                       (N.B. la mia versione di Bios è l'ultima, F7 https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#support-dl-bios) (a quanto risulta il giorno 7.01.2019)
       
      Load Optimized Default Settings Peripherals → USB Configuration → XHCI Hand-off : Enabled Chipset → Internal Graphics : Enabled (important for Quicklook/Preview) Please note that we will be using our internal GPU in headless mode only and this guide assumes that. This is how an iMac18,3 (what we're basing our build on) behaves. That's it! I literally didn't change anything else and it just worked.
       
      Anche per me ha funzionato. Comunque lui riportava ulteriori settaggi, aggiungendo:
       
      However, these are settings that are generally recommended. Your mileage may vary:
       
      BIOS → Fast Boot : Disabled BIOS → LAN PXE Boot Option ROM : Disabled BIOS → Storage Boot Option Control : UEFI Peripherals → Trusted Computing → Security Device Support : Disable Peripherals → Network Stack Configuration → Network Stack : Disabled Peripherals → USB Configuration → Legacy USB Support : Auto Peripherals → USB Configuration → XHCI Hand-off : Enabled (Extremely important) () Chipset → Vt-d : Disabled (non l'ho messo e parte a volte, quindi penso che se parte non ha una importanza così rilevante) Chipset → Wake on LAN Enable : Disabled (era già così) Chipset → IOAPIC 24-119 Entries : Enabled  
       
      Il sistema è partito e soltanto alcune volte dava il seguente errore:
       
      Error allocating 0x11996pages at 0x000000001d453000 alloc type 2
      Couldn't allocate runtime area.
       
      Credo che sia questo piccolo problema: la NVRAM.
      Non riesco bene a capire dove cercare per sapere con esattezza se è supportato nativamente o meno. Ho cercato di informarmi, voi potreste dirmi se è vero?
      Premendo poi Ctrl+Alt+Canc riavviavo e selezionando da Clover l'NVMe interno partiva senza dare questo errore, per cui il kernel non trova spazio perché la memoria Non Volatile ad accesso Randomico è troppo frammentata, come
       
      Questa guida riportava:
       
      Primo post:
      https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
       
      Post aggiornato nel 2016:
      https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
       
      Mi sono letto tutto e ho capito che lui applicava anche delle modifiche al file: "Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000."
       
      Ho quindi seguito il suo consiglio di mettere OsxAptiofix Emuvariable 64 e Test2-2016.efi (che lui aveva creato) ma il problema sembrava persistere, più raramente
       
      La mia cartella driver64UEFI di ora
       
      Dopo aver trovato una strada senza soluzoni anche lì mi sono rivolto a degli amici, e di questo errore ne ho parlato anche con utenti del gruppo Telegram "Hackintosh Italia" che sono stati e ancora sono molto gentili ad aiutarmi spiegandomi che si tratta di un problema di NVRAM, che nel mio caso, avendo installato questi .efi file nella cartella EFI/EFI/CLOVER/driver64UEFI (che ancora è cosi attualmente, oscillando tra couldnt allocate runtime area (anche dopo aver definitivamente staccato la corrente dopo aver spento il PC per capire se poteva aiutare) e a volta anche nessun errore)
       
       
      -ApfsDriverLoader-64.efi
      -DataHubDxe-64.efi
      -EmuVariableUefi-64.efi
      -FSInject-64.efi
      -HFSPlus-64.efi
      -NTFS-64.efi
      -NvmExpressDxe-64.efi
      -OsxAptioFix2Drv-free2000.efi
      -PartitionDxe-64.efi
      -UsbKbDxe-64.efi
       
      In più ho aggiunto gli RC Scripts (come mi è stato consigliato dai membri del gruppo telegram) sul disco interno in cui mac è installato.
       
      Togliendo quindi qualsiasi test.efi o test2- 2016.efi ed ascoltando chi ne sapeva di più. Ora mi trovo a dover affrontare diverse volte questo errore dovendo riavviare per risolverlo, cosa che mi fa dedurre che Osxaptiofix2 2000 sia un po' instabile nel pulire la NVRAM prima di avviare la macchina/ allo spegnimento di questa.
      Questo problema di couldnt allocate runtime area persiste sebbene prema F12 dalla schermata di Boot di Clover.
       
      Vi chiedo gentilmente una mano, inoltre mi è stato detto che siccome il sistema da:
       
      -"3.6 GHz unknown nella sezione "Processor"
      -non riconosce la RAM con un Vendor ID? (del tipo Ballistix dovrebbe essere?)
       
       
      Serve di rivedere il config.plist che ho creato, rivedere i DSDT e gli efi? sono a posto?, (mi hanno detto che gengik84 fare, ma accolgo volentieri l'aiuto di tutti) ,  vi mando una foto della schermata di "About this Mac" e della EFI in allegato. Quello che farò sicuramente mentre attendo vostre risposte è il downgrade da 10.14.3 Beta a 10.14.2, l'upgrade l'ho fatto pensando che magari avrei aggiustato qualcosa, ma l'errore come lo dava prima lo dà ora, non credo che questo cambi molto le cose in gioco. Comunque è meglio non essere in Beta per aggiustare gli errori.
       
       
      Grazie mille per essere arrivato a leggere fino a questo punto, lo apprezzo molto.
       
       
      Per la cartella EFI: sono 22MB zippati, in allegato non entrano...
       
      https://drive.google.com/open?id=106jXkDB0Id045lzIIzAn9F5MwnzWFv3X
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       



×