Contribute
Register

[Release] Hackintool v3.x.x

Sorry mate for some reason I thought Hackingtool created a self-contained usb port injector kext ?, did not realise that it relied on USBInjectAll.kext .... maybe it used to and you've now changed it, or maybe I just imagined it ? ;)

It generates a USBPorts.kext and later I added generation of SSDT-UIAC.aml. It's up to the user which one they want to use. You don't need USBInjectAll.kext with USBPorts.kext once you've created it but apparently you need to leave it installed when using SSDT-UIAC.aml.

As you can see they are almost identical ... so your code generation is good as far as I can tell.

Okay thanks for checking. I'm guessing the "0x00003000" value in the DefinitionBlock doesn't mean anything?
 
It generates a USBPorts.kext and later I added generation of SSDT-UIAC.aml. It's up to the user which one they want to use.


@headkaze,

Ok i see that now ... it generates both and puts them on the desktop.

You don't need USBInjectAll.kext with USBPorts.kext once you've created it but apparently you need to leave it installed when using SSDT-UIAC.aml.


Yes that is correct ....

Okay thanks for checking. I'm guessing the "0x00003000" value in the DefinitionBlock doesn't mean anything?


Nothing important ....

As far as I can tell from my testing the code for defining the ports in SSDT-UIAC.aml generated by Hackingtool looks fine.

Cheers
Jay
 
Hackintool v2.5.2
- Added Host, OS, Kernel and RAM System Info
 
Sorry .. my bad ...
In normal circumstances it wouldn't matter but you do write a lot of documentation around here so I just wanted to clarify :)
 
Hackintool v2.5.3 Released
- Fixed EveryMac.com Visit link
 
In normal circumstances it wouldn't matter but you do write a lot of documentation around here so I just wanted to clarify


@headkaze,

Hummm good call buddy, just checked my guides that detail using Hackintool and there was a few places where I had miss-spelt it as Hackingtool .... not enough sleep .... fixed now.

Cheers
Jay
 
When the KP happens it will display all the info to post here. If your machine resets when a KP occurs you will need to apply patches so it doesn't.
I have finally given up in attempting to solve the instability problem of my Skylake build by myself. During the last 24 hour period the machine KP'ed 6 times whilst unattended and sleeping. here follows a summary:
BSD process name corresponding to current thread.

KP-1 loginwindow
KP-2 launchd
KP-3 mds

KP-4 BluetoothUIServe
KP-6 mds
KP-7 mds

Kindly note that the 6 KP's can be grouped into 2 sets of three. The first KP of the first set occurred on 21-05-2019 at 05.35 followed by 2 others in quick succession because in Energy Saver "Start up automatically after a power failure" is enabled.

The second set of three KP's occurred at 09.00, again followed by 2 others in quick succession.

The first KP of each of the two sets have been attached and can be found in the file Archive.zip
The file Debug-3042.zip contains the problem reporting files as generated by "gen_debug -sysprofile"

The instability first surfaced from around Mojave 10.14.2/3, with nothing that I tried, fixing the issue. I then stumbled across this thread and was hoping by applying the new "connectorless" framebuffer patches, as per this thread, that the problem would be solved, however it was not to be.
I cannot rule out that somehow or other a serious configuration error slipped in which I am unable to discover by myself. The cause may even be some or other imminent hardware failure, however when the machine is in constant use during daytime it remains stable.

Assistance in finally resolving this issue will be highly appreciated.

Greeetings
 

Attachments

  • Archive.zip
    6.9 KB · Views: 175
  • Debug-3042.zip
    2.7 MB · Views: 199
Assistance in finally resolving this issue will be highly appreciated.
This is not really the place to post this. Can you please start a thread?

PS You should probably remove the "Enable TRIM for SSD" patch. I don't think you need that in Mojave.
 
Back
Top