- Joined
- May 15, 2013
- Messages
- 56
- Motherboard
- Asus Prime Z490-A
- CPU
- i9-10850K
- Graphics
- RX5600XT
Hackintool > Help > Hackintool Help > USB Patching
[Release] Hackintool v3.x.x
- Thread starter headkaze
- Start date
- Joined
- May 15, 2013
- Messages
- 56
- Motherboard
- Asus Prime Z490-A
- CPU
- i9-10850K
- Graphics
- RX5600XT
Attached is the Hackintool > Logs >Boot log. There is no output in the Lilu tab nor the System > Process : Hackintool tab.
- Joined
- Jul 15, 2017
- Messages
- 170
- Motherboard
- Gigabyte GA-Z270XP-SLI
- CPU
- i7-7700K
- Graphics
- RX 6600 XT
- Mac
- Mobile Phone
I just got 10.14.6 (upgraded from 10.12.6) installed and so far running well on a Kaby Lake i7-7700K with an RX 570. I'm using a USB.aml compiled two years ago specifically for this motherboard.
I used a friend's config.plist as he has the exact same motherboard and processor, but he has an RX 580 instead of my RX 570. I have the iGPU turned on in the BIOS, but am not using any connector from the motherboard, just the RX 570.
My current FB in config.plist is:
If I run Hackintool and generate a patch I get:
Am I safe using this Hackintool generated patch as is? I'm using the release version of WEG and Lilu - a bit unclear if I need to use the debug version or perform more steps to get the correct frame buffer patch?
Massively cool tool!!
I used a friend's config.plist as he has the exact same motherboard and processor, but he has an RX 580 instead of my RX 570. I have the iGPU turned on in the BIOS, but am not using any connector from the motherboard, just the RX 570.
My current FB in config.plist is:
XML:
<key>Properties</key>
<dict>
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
<key>AAPL,ig-platform-id</key>
<data>AwASWQ==</data>
<key>AAPL,slot-name</key>
<string>Internal@0,2,0</string>
<key>device-id</key>
<data>ElkAAA==</data>
<key>device_type</key>
<string>Display controller</string>
<key>framebuffer-patch-enable</key>
<data>AQAAAA==</data>
<key>hda-gfx</key>
<string>onboard-2</string>
<key>model</key>
<string>Intel HD Graphics 630</string>
</dict>
</dict>If I run Hackintool and generate a patch I get:
XML:
<dict>
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
<key>AAPL,ig-platform-id</key>
<data>AwASWQ==</data>
<key>AAPL,slot-name</key>
<string>Internal@0,2,0</string>
<key>device_type</key>
<string>Display controller</string>
<key>framebuffer-fbmem</key>
<data>AACQAA==</data>
<key>framebuffer-patch-enable</key>
<data>AQAAAA==</data>
<key>framebuffer-stolenmem</key>
<data>AAAwAQ==</data>
<key>hda-gfx</key>
<string>onboard-1</string>
<key>model</key>
<string>Intel HD Graphics 630</string>
</dict>
</dict>Am I safe using this Hackintool generated patch as is? I'm using the release version of WEG and Lilu - a bit unclear if I need to use the debug version or perform more steps to get the correct frame buffer patch?
Massively cool tool!!
- Joined
- Mar 20, 2017
- Messages
- 15
- Motherboard
- HP Zhan66 Pro G2-Clover
- CPU
- i5-8265U
- Graphics
- UHD 620(3EA0),1920*1080
Sorry, I originally wanted to ask is the native support whisky lake card without fakeID.
So we can use the HDMI port...
- Joined
- Feb 18, 2019
- Messages
- 358
- Motherboard
- ASUS Z690 Maximus Extreme
- CPU
- i9-12900KF
- Graphics
- 6900XT
- Mac
- Mobile Phone
Thanks for your hard work on Hackintool!
I'm observing the following on my X299/9980XE/Vega56 build (iMacPro).
When running Catalina (consistently seen with all betas; now ß9), clicking on the Export USB button in Hackintool issues an "SSDT-EC Required" window. However, I'm already using this SSDT. EC is unpopulated, as below. So the SSDT-EC is not working. This same SSDT-EC works just fine in Mojave, properly injecting AppleBusPowerController into the EC device.
Catalina:
Mojave:
Oddly, there is an AppleBusPowerController appearing under IOResources in Catalina, as shown below. But it's not being injected into EC. How do we get AppleBusPowerController into the EC device in Catalina?
*****
EDIT: 27 Sept 2019
I was informed on another forum that:
"AppleBusPowerController doesn't need the EC anymore to load starting with Catalina. So whatever you did in the past to get it loading, either by renaming your EC or providing a fake EC device isn't necessary anymore. AppleBusPowerController now attaches to RTC."
So SSDT-EC is no longer needed in Catalina. But perhaps an RTC method is needed: AppleBusPowerController is appearing under IOResources but not RTC.
EDIT:
More information from the other forum now suggests that this is all normal behavior on Catalina: AppleBusPowerController appears under IOResources but not under RTC or EC. So then SSDT-EC is no longer needed under Catalina as I inactivated it for the above examples (and I also had no RTC patches).
I'm observing the following on my X299/9980XE/Vega56 build (iMacPro).
When running Catalina (consistently seen with all betas; now ß9), clicking on the Export USB button in Hackintool issues an "SSDT-EC Required" window. However, I'm already using this SSDT. EC is unpopulated, as below. So the SSDT-EC is not working. This same SSDT-EC works just fine in Mojave, properly injecting AppleBusPowerController into the EC device.
Catalina:
Mojave:
Oddly, there is an AppleBusPowerController appearing under IOResources in Catalina, as shown below. But it's not being injected into EC. How do we get AppleBusPowerController into the EC device in Catalina?
*****
EDIT: 27 Sept 2019
I was informed on another forum that:
"AppleBusPowerController doesn't need the EC anymore to load starting with Catalina. So whatever you did in the past to get it loading, either by renaming your EC or providing a fake EC device isn't necessary anymore. AppleBusPowerController now attaches to RTC."
So SSDT-EC is no longer needed in Catalina. But perhaps an RTC method is needed: AppleBusPowerController is appearing under IOResources but not RTC.
EDIT:
More information from the other forum now suggests that this is all normal behavior on Catalina: AppleBusPowerController appears under IOResources but not under RTC or EC. So then SSDT-EC is no longer needed under Catalina as I inactivated it for the above examples (and I also had no RTC patches).
Last edited:
- Joined
- Jul 15, 2017
- Messages
- 170
- Motherboard
- Gigabyte GA-Z270XP-SLI
- CPU
- i7-7700K
- Graphics
- RX 6600 XT
- Mac
- Mobile Phone
In this post on the previous page, I showed the current FB patch in my working 10.14.6 - and also what I think should actually be the correct FB patch - generated by Hackintool after setting up the parameters for a headless Kaby Lake 18,3.
I used Hackintool to update my config.plist (Very nice feature!!), and created screen shots of the IO Registry Explorer IGPU@2 before and after booting with the changes.
It boots up and I don't notice any changes in behavior, but ... obviously the IO Registry has Really changed a lot.
How can I determine if the changes are correct or beneficial? I've read thru the notes on creating the changes, but ... I haven't seen any mention of how to test the changes?
Here is my Before:
After:
I used Hackintool to update my config.plist (Very nice feature!!), and created screen shots of the IO Registry Explorer IGPU@2 before and after booting with the changes.
It boots up and I don't notice any changes in behavior, but ... obviously the IO Registry has Really changed a lot.
How can I determine if the changes are correct or beneficial? I've read thru the notes on creating the changes, but ... I haven't seen any mention of how to test the changes?
Here is my Before:
After:
- Joined
- Sep 23, 2019
- Messages
- 13
- Motherboard
- Asus Z390-f
- CPU
- i9-9900k
- Graphics
- UHD 630
- Mac
headkaze
Hello
After the changes are made, the system loads with the correct adapter and working accelerations, but the desktop is larger than the physical resolution of the screen. This means that on the screen I only see the central part of the desktop, I don't see the top menu, half of the bottom panel and all the elements larger than usual.
Tell me what can affect the screen so much.
When an adapter is recognized incorrectly (7mb), the resolution corresponds to the screen and I see the full
i9-9900k, asus z390f, uhd 630
I'm attaching screenshots of what I see.
Yes, it actually looks strange, fullhd monitor. I can't understand the reasons for that, windows don't have this problem, so the problem also goes away when I write another the AAPL value, ig-platform-id, but I'm gonna get a wrong definition of the adapter and 7 MB of memory.
By the way, without device-id I get a black screen by hdmi
So I think maybe there's a problem with my configurator, I'll put it on the message, maybe I don't notice anything important.
I pointed out the other smbios, but the result is the same. But I don't understand which framebuffer patch prevents the system from detecting the monitor. I think the reason is some extra patch, because without it the resolution is correct
Which patch can block the EDID definition
of the monitor?
Hello
After the changes are made, the system loads with the correct adapter and working accelerations, but the desktop is larger than the physical resolution of the screen. This means that on the screen I only see the central part of the desktop, I don't see the top menu, half of the bottom panel and all the elements larger than usual.
Tell me what can affect the screen so much.
When an adapter is recognized incorrectly (7mb), the resolution corresponds to the screen and I see the full
i9-9900k, asus z390f, uhd 630
I'm attaching screenshots of what I see.
Yes, it actually looks strange, fullhd monitor. I can't understand the reasons for that, windows don't have this problem, so the problem also goes away when I write another the AAPL value, ig-platform-id, but I'm gonna get a wrong definition of the adapter and 7 MB of memory.
By the way, without device-id I get a black screen by hdmi
So I think maybe there's a problem with my configurator, I'll put it on the message, maybe I don't notice anything important.
I pointed out the other smbios, but the result is the same. But I don't understand which framebuffer patch prevents the system from detecting the monitor. I think the reason is some extra patch, because without it the resolution is correct
Which patch can block the EDID definition
of the monitor?
Attachments
- Joined
- Sep 18, 2010
- Messages
- 638
- Motherboard
- Asus Z87 Maximus Gene VI
- CPU
- i7-4790K
- Graphics
- Vega 64
- Mac
- Mobile Phone
When I was running Mojave, Hackintool was showing 15 USB ports. I have upgraded to Catalina and now the app is showing 27 ports. Is this normal?
- Joined
- Jun 24, 2010
- Messages
- 56
- Motherboard
- ASUS ROG STRIX Z270G GAMING
- CPU
- i7-7700
- Graphics
- HD 630
- Mac
Going through the process of port discovery... when I connect a USB 3.0 device to any USB 3.0 port, it isn't recognized. I've tried 4 different devices. USB 2 devices are recognized in 3.0 ports fine. And 3.0 devices are recognized in 2.0 ports. Anyone have any ideas?
- Joined
- Mar 30, 2013
- Messages
- 217
- Motherboard
- Asus TUF Gaming Z590 Plus WiFi
- CPU
- i9-10900
- Graphics
- RX 5700 XT
- Mac
- Mobile Phone
The AppleAHCIPortHotPlug kext does not work with Catalina anymore. As soon as I install it macOS won't boot anymore. It also did prevent my first tries with upgrading to Catalina. Is it possible for you to make a new kext for that?