- Dec 13, 2010
- Z390 PHANTOM GAMIG-ITX/ac
- UHD 630
- Mobile Phone
Excellent guide, helps us newbies to enter a little better this utility
On my HM67 mainboard the IRQ Fix (FixTMR, FixRTC, FixIPIC & FixHPET) is still needed for AppleALC to work.AppleALC
[...] you should remove [...] DSDT Edits ...
Not setting this option results in US by default.AirportBrcmFixup
If necessary, you can over-ride the default MacOS WiFi local and explicitly set the country code for your WiFi device using the boot argument brcmfx-country=XX, this is sometimes necessary to get 5Ghz WiFi working at full speed with your router.
I can confirm this for for my DW1550 (Broadcom BCM94352HMB). In addition, after disabling ACPI->DSDT->Fixes->FixAirport and Devices->FakeID->WIFI the card is now marked as built-in.
Faced a few problems when download big files. They were useless due to corrupted files. Re-enabling ACPI->DSDT->Fixes->FixAirport fixed the problem. Therefore, the fix seems to be still needed.
Your question has been answered below your other post ....hey everyone, im super noob in hackintosh my goal is : to enable intel quicksync/igpu (for fcpx offcourse)
i already put patch from FBpatcher in my config.plist ( see attachment ), but i think is not correctly place.
and my patch from FBpatcher didnt show any device id ( attachment )
i really hope someone can help me, and sorry for my bad english
I have finally got this reply from @scj312 in the other "universe" concerning the validity of the shikigva=xx bootflag.@Henties,
You could try asking the WEG Devs for confirmation on the WEG official support thread :-
Would be interesting to know what they say so i can update the guide if necessary.
The boot flags are still listed in the "Manual" sub folder on WhatEverGreen's Git-Hub page, however these are essentially the old readme.md files from each of the merged plug-in's. As I previously mentioned in the case of shikigva I believe thats it's enabled by default if applicable to the IGPU as there is no real reason not use it, I suspect that the boot flag is still left in there just incase a user needs to over-ride the defaults, I suspect the same is true for the other merged plug-in's in that commonly used options are enabled as default hence the reason WhatEverGreen works so well with minimal configuration on many systems.The fact that the old shikigva boot flags are not listed, although seemingly still usable' makes me view the "merged" Whatevergreen.kext with suspicion. It still seems only to be a half baked egg. I am not presently using the shikigva=xx flag and have so far not been able to detect anything untoward"
Thanks for your explanation, now this all makes more sense to me.I suspect the same is true for the other merged plug-in's in that commonly used options are enabled as default hence the reason WhatEverGreen works so well with minimal configuration on many systems.