[Release] Hackintool v3.x.x

[rajuchacharuk]

Disabling the EHCI controller(s) is done with BIOS options, if provided.

disabling from BIOS would affect anything in Windows?

 

[hackmefrancis]

Spare me on my ignorance

I already have a working USB-SSDT using @RehabMan 's guide (thank you). I'd like to think that this *new method from @headkaze would now be the better way to handle these USB limitation or there's really no difference at all?

Are there any advantages of this method as opposed to using an SSDT?

Thank you.

 

[RehabMan]

disabling from BIOS would affect anything in Windows?

Yes, of course it would. If you disable EHCI in BIOS, then even Windows will use xHCI only.

 

[RehabMan]

Spare me on my ignorance

I already have a working USB-SSDT using @RehabMan 's guide (thank you). I'd like to think that this *new method from @headkaze would now be the better way to handle these USB limitation or there's really no difference at all?

Are there any advantages of this method as opposed to using an SSDT?

Thank you.

No difference really. Both methods inject a "ports" dictionary.

There are some advantages to the SSDT + USBInjectAll method:
- the SSDT created is not specific to a certain SMBIOS
- you can use uia_exclude to exclude specific ports from injection

For example, I use uia_exclude to exclude injection of the port attached to my touchscreen on my u430. So, people following my guide for it have a working touchscreen, but I'm able to disable it with a simple change to my local config.plist.

The uia_exclude feature also comes in handy when troubleshooting, as you can disable a certain built-in device to see if it is causing a problem, all without editing anything but kernel flags.

 

[zzmadd]

I have an issue with a Gigabyte B360N WiFi Motherboard and iGPU acceleration in Mojave.
My Gigabyte Z370N WiFi was super easy to get iGPU working:
Device/Properties: PciRoot(0x0)/Pci(0x2,0x0) -> AAPL,ig-platform-id: 07009B3E
Inject Intel checked under Graphics (didn't test without)
AND NOTHING ELSE!

BUT
2 - Gigabyte B360N WiFi is a mess. I'm unable to get iGPU acceleration working
I believe it has to be used Device/Properties and NOT ig-platform-id
I believe it has to be used PciRoot(0x0)/Pci(0x2,0x0) -> AAPL,ig-platform-id: 07009B3E
But such is not enough. With such you get the monitor going into stand by mode after Apple logo.
So some frame buffer, connectors patch need to be applied.
I tried appliying some patches suing FBPatcher but I get the same black screen.
This motherboard to work needed 3 KextToPatch entries in High Sierra to modify the frame buffer.

As side note if I use:
Inject Intel: yes - ig-platform-id: 59120000 the OS Loads, but I get No Acceleration and 31MB Video Memory

Anybody can help please? Ridiculous motherboards!

 

[headkaze]

This motherboard to work needed 3 KextToPatch entries in High Sierra to modify the frame buffer.

Try using the new Patch->Import KextsToPatch menu to import your 3 patches.

 

[zzmadd]

I tried but the exported config.plist showed the same problem.
After Apple logo monitor goes into stand by mode.
In High Sierra there are 3 KextToPatch to add:
AppleIntelKBLGraphicsFramebuffer Find 01050900 00040000 87010000 Replace 02021200 00080000 87010000
AppleIntelKBLGraphicsFramebuffer Find 02040A00 00040000 87010000 Replace 03041200 00080000 87010000
AppleIntelKBLGraphicsFramebuffer Find 03060A00 00040000 87010000 Replace 01011200 00080000 87010000

I've attached the tested config.plist so you/someone can maybe make a bit more sense of the patches I tried.
Thanks for your help.

 

[RehabMan]

I tried but the exported config.plist showed the same problem.
After Apple logo monitor goes into stand by mode.
In High Sierra there are 3 KextToPatch to add:
AppleIntelKBLGraphicsFramebuffer Find 01050900 00040000 87010000 Replace 02021200 00080000 87010000
AppleIntelKBLGraphicsFramebuffer Find 02040A00 00040000 87010000 Replace 03041200 00080000 87010000
AppleIntelKBLGraphicsFramebuffer Find 03060A00 00040000 87010000 Replace 01011200 00080000 87010000

I've attached the tested config.plist so you/someone can maybe make a bit more sense of the patches I tried.
Thanks for your help.

Those patches are for KBL, but your Devices/Properties is injecting a CFL ig-platform-id.

 

[zzmadd]

Those patches are for KBL, but your Devices/Properties is injecting a CFL ig-platform-id.

Thanks for the reply!

I understand the patches are for KBL and we're no longer spoofing such platform.
Thing is what on a Z370 leads to a perfectly working and easy iGPU implementation on a B360 leads to a stand by monitor, as it used to happen in HSierra btw.
Do you have any suggestion in how I could find a way to make this board gen work?
I also tried using FBPatcher to change number of ports to 2, patch connectors, independently from those KBL patches, but I'm kind of moving blind, attempting, without a wholistic understanding of the software implementation.

Thanks for your help.

 

[headkaze]

Version 1.4.4 Released
- Added ability to inject valid device-id's