[Release] Hackintool v3.x.x

[headkaze]

My system's native igpu is 0x3e91. In selecting a platform, I follow "What ig-platform-id should I use for my system? You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one".
The exact match, 0x3e91 is headless, so any guidance in selecting the platform that makes best sense?

I wouldn't recommend a headless frame. I would try 0x3E9B0000 (Mobile) or 0x3E9B0007 (Desktop) and if you have a problem then spoof the Device Id as shown in the screenshot.

 

[jaymonkey]

I was considering adding it but it's kinda obvious when the connector data is empty.

@headkaze,

Fair enough ....

PS 0x3E920003 / 0X3E910003 are two for Coffee Lake (no need to spoof Kaby Lake)

Thanks for pointing these two headless ID's out ... i'll add them to my guide ..

Cheers
Jay

 

[stiligFox]

Hey all, silly noob question, but can I use the IntelFB tool to determine all of the USB ports on my hack? Does it essentially do the same thing this guide does?

https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/

Or are they separate and I need to do the custom SSDT anyway?

This guide is super intimidating for me and if this tool does the same thing, I can handle the rest of the instructions.

Thanks!

 

[headkaze]

Hey all, silly noob question, but can I use the IntelFB tool to determine all of the USB ports on my hack? Does it essentially do the same thing this guide does?

https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/

Or are they separate and I need to do the custom SSDT anyway?

This guide is super intimidating for me and if this tool does the same thing, I can handle the rest of the instructions.

EDIT: First post has been updated.

 

[emveepee]

If you're interested in testing this new feature feel free and let me know how you go.

I recently update to 10.14.1 and my existing USBPorts.kext file continued to work. If there is something that you would like tested let me know and I would be happy to help.

Also I note in the start up that FB Patcher outputs

2018-11-01 17:51:11.122 FBPatcher[731:7966] Metal Device Name: Intel(R) KBL Unknown

It is not a KBL machine.

On a side note my video connectors did not work properly after the 10.14.1 upgrade using a CFL UHD 630. Before I had to use BusId 1 and 2 to get HDMI working on connections 0 and 1. Now BusId 2 stopped working and both have to use Busid 1 with different ports. The problem with this is both displays now show as the same monitor to macOS and too iogeg Upgrading to WEG 1.2.4 didn't help. I doubt this this a FB Patcher problem but would be interested in any suggestions on how to fix this.

Martin

 

[headkaze]

I recently update to 10.14.1 and my existing USBPorts.kext file continued to work. If there is something that you would like tested let me know and I would be happy to help.

If you've already created a USBPorts.kext you should not need to create a new one.

Also I note in the start up that FB Patcher outputs

2018-11-01 17:51:11.122 FBPatcher[731:7966] Metal Device Name: Intel(R) KBL Unknown

It is not a KBL machine.

That's just what Metal reports back. I'm not sure why though?

On a side note my video connectors did not work properly after the 10.14.1 upgrade using a CFL UHD 630. Before I had to use BusId 1 and 2 to get HDMI working on connections 0 and 1. Now BusId 2 stopped working and both have to use Busid 1 with different ports. The problem with this is both displays now show as the same monitor to macOS and too iogeg Upgrading to WEG 1.2.4 didn't help. I doubt this this a FB Patcher problem but would be interested in any suggestions on how to fix this.

Sorry I don't understand enough about what the BusId value means to be able to help you. It seems odd that you would need to change it after an upgrade. It just means that the value is possibly not tied to hardware.

 

[emveepee]

If you've already created a USBPorts.kext you should not need to create a new one.

I was thinking if you needed help testing 1.5.8 I can disable my working file to see if it works with your new process. Knowing I have a fallback is good.

Martin

 

[dbdb]

I wouldn't recommend a headless frame. I would try 0x3E9B0000 (Mobile) or 0x3E9B0007 (Desktop) and if you have a problem then spoof the Device Id as shown in the screenshot.
View attachment 361800

FB Patcher features QE/CI and Metal support detection. Both show "no" for my iGPU. Can you please explain a little about how this detection is done? Also, the FB Patcher CPU detection doesn't know the G5600 is 8th gen, it reports "IntelGen: ???"
Thank you

 

[headkaze]

I was thinking if you needed help testing 1.5.8 I can disable my working file to see if it works with your new process. Knowing I have a fallback is good.

Yes, that would be helpful, thanks. I've updated the instructions in the first post.

 

[headkaze]

FB Patcher features QE/CI and Metal support detection. Both show "no" for my iGPU. Can you please explain a little about how this detection is done? Also, the FB Patcher CPU detection doesn't know the G5600 is 8th gen, it reports "IntelGen: ???"
Thank you

For QE/CI detection I use CGDisplayUsesOpenGLAcceleration(). For Metal if MTLCreateSystemDefaultDevice() fails then it's not supported. IntelGen is detected based on the framebuffer kext loaded. So if you do not have one loaded then it means you have no graphics acceleration.