Hi, just a update. I found out that i needed to delete the prelinkedkernel and with that action on the Terminal and the wrong rm-rf code it wiped all 4 hdd's plus the Sierra SSD empty.
I better go with High sierra as new install. Is the process the same as with Sierra, (Clover, EFI, Multibeast for High Sierra, etc.??) Can i use the EFI you have provided for Sierra?
Yes the process is the same if you use the Tonymacx86 tools.
The CLOVER folder you were using with Sierra should work the same with High Sierra (HS), with the following caveats.
You will need to add ApfsDriverLoader-64.efi to your /CLOVER/drivers64UEFI folder. Assuming you are using the same old version of Clover you were using before.
If you use a newer version of Clover, post r5000, then you need to add ApfsDriverLoader.efi to your /CLOVER/drivers/UEFI folder.
The two APFS drivers are attached below.
Other than that it should work just fine.
Your IGPU will face the same issues it did with Sierra, you need to fix the IGPU for full acceleration to work once you have HS installed.
The options you applied for getting the two Radeon HD 6800 dGPU's will remain the same for HS.
High Sierra will look to change the format of the SSD from HFS+ to APFS, if that is your main macOS drive and where you plan to install High Sierra.
I beleive there is a trick to prevent this format change, but I'm not sure if the trick is necessary. I have been using the APFS format since it was released in the HS Beta and not encountered any issues using it.
You might want to look at creating a Clone of your working High Sierra drive, once you have it installed. Especially before you install any security updates for HS.
I use Carbon Copy Cloner for this task. It is simple, straightforward and not too expensive at around £30 (UK). I use a spare laptop hard drive for the clone, which I can then use to boot the system and reinstall/clone back the OS and all my apps etc. in one action. Not needing to go through the whole macOS installation wizard and issues that can arise when reinstalling the OS.
Got High Sierra running. Now fine Tuning. one Problem: As soon i plug a HDD on HS boot up fine and runs for about 2-3 min and then puff, reboot..... I got a 14TB WD Gold HDD and i can't Format or Initialize the HD. As soon it's connected and boot up....HS reboot and Bios is set on IDE. What can be the Problem?
Have 256gb SSD as Os disk. The 14tb Hd shows up in the AHCI list while booting. Now i face a problem even when only the Os Drive is connected. HS runs 2 minutes, then reboot and bios set on IDE. As soon i click on a icon or try to open Disk Utility, same thing........
The Manual for GA-Z68XP-UD5 says that a SATA3 Drive has to be on the black SATA0 and SATA1 connected. On theSATA0 i have the Os SSD connected. Found out the 14TB Drive is broken. Arrived DOA, just purchased the drive.
Page 27 of the manual for your motherboard explains the difference between the upper pair of SATA ports and the four lower SATA ports. Basically the lower four ports run at half the speed.
Logically you want your OS drive(s) attached to the two SATA 3 ports.
The Data drive(s) can be attached to one or more of the SATA 2 ports, as speed will not be as important for the data drive(s).
Details from the manual regarding the SATA ports:
Intel Z68 Chipset:
2 x SATA 6Gb/s connectors (SATA3_0, SATA3_1) supporting up to 2 SATA
4 x SATA 3Gb/s connectors (SATA2_2~SATA2_5) supporting up to 4 SATA
If you need/want more SATA 3 ports, I would suggest adding a PCIe SATA card such as one of these, Syba SI-PEX40064 SATA III 4 Port PCI-e x1 Controller Card. They cost around £26 in the UK, provide four addtional SATA 3 ports, which use the Marvell 88SE9215 chipset. This card works just fine in macOS. I have successfully used a number of these cards in older Hacks I have built.
If the Marvell 88SE9215 chipset doesn't show in 'About this Mac' it is only a cosmetic issue. The card will still work. If you want to fix this cosmetic issue, just install AHCI_3rdParty_SATA.kext to your /Library/Extensions folder and the card will be identified correctly in About this Mac > System Reports > SATA/SATA Express.
Here is a shortened version of what you would need to do:
Extract your ACPI files with Clover, by pressing F4 when you are on the Clover boot screen. This will save the ACPI files, including your DSDT to the /EFI/CLOVER/ACPI/origin folder on the EFI partition of your hard drive, if that is what you are using to boot the system. Otherwise it will be in the same folder on your USB drive.
Disassemble your DSDT and SSDT's, using Terminal and the following commands:
cd "to the directory where you placed a copy of your SSDT/DSDT", I normally use a folder named 'Original' for where I save copies of these files.
After cd'ing to the Original folder, Enter the following Terminal command:
iasl -da -dl DSDT.aml SSDT*.aml
This will create disassembled copies of the DSDT and SSDT's in the 'Original' folder, these new files will have the .dsl file type in place of the .aml file type.
Move the DSDT.dsl and SSDT'*.dsl files to another folder, I normally use one called 'Disassembled'.
Now you can open the DSDT.dsl in MaciASL and patch it, The resources you need are all linked in Rehabman's guide, at the bottom of the first post.
If you have gone to this much trouble you probably want to do more than just apply the ShutdownFix to the DSDT.
Your system sounds like it also needs these the "6-Series USB" patch.
Once you have applied the patches, checked that the DSDT.dsl Compiles without any errors. I ususally Close the patch window and check that the DSDT is compiling after applying each patch, that way I can see if a specific patch is causing issues and errors to occur.
Once you have applied all the necessary patches, the DSDT Compiles without errors, you can save it as an ACPI Machine Language Binary, i.e. DSDT.asl.
This patched DSDT.asl should then be copied to your /EFI/CLOVER/ACPI/patched folder so it is used in place of the one normally loaded by your system.
Probably not what you want to hear but that is normally the way with any Hackintosh issues.
Hi Ed, got High Sierra re-installed works stable till WiFi. I can't connect to the Internet. It says
there is a problem with a Country Code? Other have trouble in Mojave with this, but High sierra??? Worked before in Sierra out of the Box with a TP-Link WDN4800.
The Atheros kext that your TP-Link wifi card used in High Sierra has been removed in Mojave & Catalina. You need to add these two kexts to your /Library/Extensions folder for the WiFI to work;
The ATH9KInjector.kext being an injector requires Lilu.kext to be installed in the same location. So if you have Luli.kext in your /CLOVER/kexts/Other folder I would recommend you remove it and install it in your /Library/Extensions. Do the same for any other third-party kexts, except FakeSMC.kext, which can remain in the /CLOVER/kexts/Other folder.