Jump to content
headkaze

Hackintool v3.x.x

882 posts in this topic

Recommended Posts

Hi @headkaze

 

Is it possible to add applebuspower patch automatically when hackintool generate USBPorts Info.plist:

 

kUSBSleepPortCurrentLimit, 2100

kUSBSleepPowerSupply,5100

kUSBWakePortCurrentLimit,2100

kUSBWakePowerSupply,5100

 

Sorry for my bad english 

Thanks :)

Share this post


Link to post
Share on other sites
Advertisement
48 minutes ago, Matgen84 said:

Is it possible to add applebuspower patch automatically when hackintool generate USBPorts Info.plist:

 

kUSBSleepPortCurrentLimit, 2100

kUSBSleepPowerSupply,5100

kUSBWakePortCurrentLimit,2100

kUSBWakePowerSupply,5100

 

Sorry mate but with latest Hackintool, inside the Info.plist we do get these. Here's mine:

<key>kUSBSleepPortCurrentLimit</key>
<integer>2100</integer>
<key>kUSBSleepPowerSupply</key>
<integer>3600</integer>
<key>kUSBWakePortCurrentLimit</key>
<integer>2100</integer>
<key>kUSBWakePowerSupply</key>
<integer>5200</integer>

Not sure what is your question...?

Share this post


Link to post
Share on other sites
Posted (edited)
16 minutes ago, MacKonsti said:

 

Sorry mate but with latest Hackintool, inside the Info.plist we do get these. Here's mine:


<key>kUSBSleepPortCurrentLimit</key>
<integer>2100</integer>
<key>kUSBSleepPowerSupply</key>
<integer>3600</integer>
<key>kUSBWakePortCurrentLimit</key>
<integer>2100</integer>
<key>kUSBWakePowerSupply</key>
<integer>5200</integer>

Not sure what is your question...?

 

You answers to my question :) Great. I try the latest Hackintool: these entries doesn't exist. I don't understand.

 

Why the integer are different between yours and mine values on my Z390 Aorus Master!

Edited by Matgen84

Share this post


Link to post
Share on other sites
Posted (edited)
11 minutes ago, Matgen84 said:

Why the integer are different between yours and mine values on my Z390 Aorus Master!

 

I am not sure Hackintool can "guess" each person's hardware, mate. These values that I show you here, are pretty standard and those are the ones generated by Hackintool.

If you know what you are doing, I guess you can change them, but be careful or you can damage your ports. Hackintool includes the standard values in the Info.plist but I suggest you try as-is.

Edited by MacKonsti

Share this post


Link to post
Share on other sites
7 minutes ago, MacKonsti said:

 

I am not sure Hackintool can "guess" each person's hardware, mate. These values that I show you here, are pretty standard and those are the ones generated by Hackintool.

If you know what you are doing, I guess you can change them, but be careful or you can damage your ports. Hackintool includes the standard values in the Info.plist but I suggest you try as-is.

 

I've generate a new USBPort.kext (Hackintool 3.3.1): these keys and integer is not present?

Share this post


Link to post
Share on other sites
Posted (edited)
17 hours ago, Matgen84 said:

 

I've generate a new USBPort.kext (Hackintool 3.3.1): these keys and integer is not present?

I think Hackintool checks if you have those keys in ACPI and will not write them into USBPorts.kext if you do.

Perhaps you already have these properties in ACPI under USBX or XHC?

Or somewhat different approach: What is your SMBIOS? Maybe those keys are already embedded in /S/L/E/IOUSBHostFamily.kext/C*/P*/AppleUSBHostPlatformProperties.kext/C*/Info.plist

Edited by displhehynehym

Share this post


Link to post
Share on other sites
6 minutes ago, displhehynehym said:

I think Hackintool checks if you have those keys in ACPI and will not write them into USBPorts.kext if you do.

Perhaps you already have these properties in ACPI under USBX or XHC?

Or somewhat different approach: What is your SMBIOS? Maybe those keys are already embedded in /S/L/E/IOUSBHostFamily.kext/C*/P*/AppleUSBHostPlatformProperties.kext/C*/Info.plist

 

My SMBIOS Imac19,1. Yes those keys are already embedded but not with the same values. But the keys ara note embedded in in /S/L/E/IOUSBHostFamily.kext/C*/P*/AppleUSBHostPlatformProperties.kext/C*/Info.plist

Share this post


Link to post
Share on other sites
2 minutes ago, Matgen84 said:

 

My SMBIOS Imac19,1. Yes those keys are already embedded but not with the same values. But the keys ara note embedded in in /S/L/E/IOUSBHostFamily.kext/C*/P*/AppleUSBHostPlatformProperties.kext/C*/Info.plist

OK, now you know why you aren't getting those keys. You must have added USBX or XHC's _DSM with kUSB properties via DSDT patch or SSDT. Delete them and you will get kUSB entires when you export USBPorts.kext.

Check out Hackintool codes to see on what condition these values are assigned their specific numbers.

Share this post


Link to post
Share on other sites
1 hour ago, displhehynehym said:

OK, now you know why you aren't getting those keys. You must have added USBX or XHC's _DSM with kUSB properties via DSDT patch or SSDT. Delete them and you will get kUSB entires when you export USBPorts.kext.

Check out Hackintool codes to see on what condition these values are assigned their specific numbers.

 

Without any kUSB proprieties (SSDT-USBX) or else, Hackintool 3.3.1 do not generate the specific numbers for my SMBIOS Imac19,1 :cry:

Share this post


Link to post
Share on other sites
10 minutes ago, Matgen84 said:

 

Without any kUSB proprieties (SSDT-USBX) or else, Hackintool 3.3.1 do not generate the specific numbers for my SMBIOS Imac19,1 :cry:

Do you mean the numbers are the same for all SMBIOS or they are not generated at all for iMac19,1?

If the second one is your case, I don't know why.

If you are really need to just see Hackintool export USBPorts.kext with kUSB, then ask headkaze if there's anything about iMac19,1. If it's because you want specific values for iMac19,1, look into iMac19,1's IOReg or DSDT found in https://applelife.ru/threads/dampy-originalnyx-makov.2943712/. You should know it's not about what SMBIOS you choose, but about how much current your MOBO safely supports.

Share this post


Link to post
Share on other sites
5 minutes ago, displhehynehym said:

Do you mean the numbers are the same for all SMBIOS or they are not generated at all for iMac19,1?

If the second one is your case, I don't know why.

If you are really need to just see Hackintool export USBPorts.kext with kUSB, then ask headkaze if there's anything about iMac19,1. If it's because you want specific values for iMac19,1, look into iMac19,1's IOReg or DSDT found in https://applelife.ru/threads/dampy-originalnyx-makov.2943712/. You should know it's not about what SMBIOS you choose, but about how much current your MOBO safely supports.

 

The numbers are not generate at all for my Imac19,1. I already ask Headkaze for anything about iMac19?1 in my first post.

Thanks for your help :)

Share this post


Link to post
Share on other sites
6 hours ago, Matgen84 said:

Without any kUSB proprieties (SSDT-USBX) or else, Hackintool 3.3.1 do not generate the specific numbers for my SMBIOS Imac19,1 :cry:

Please try Hackintool 3.3.2.

 

In Catalina the USB power properties were removed from /System/Library/Extensions/IOUSBHostFamily.kext/Contents/Info.plist so I don't know if they're needed or not. So anyway I integrated an earlier version into Hackintool and will also inject default values if there's no similar system to match.

Share this post


Link to post
Share on other sites
Posted (edited)
9 hours ago, headkaze said:

Please try Hackintool 3.3.2.

 

In Catalina the USB power properties were removed from /System/Library/Extensions/IOUSBHostFamily.kext/Contents/Info.plist so I don't know if they're needed or not. So anyway I integrated an earlier version into Hackintool and will also inject default values if there's no similar system to match.

 

Thanks. :)

I try v3.2.2. On Catalina, SMBIOS Imac19,1 keys are not embedded in /S/L/E/IOUSBHostFamily.kext/C*/P*/AppleUSBHostPlatformProperties.kext/C*/Info.plist. There are only for Imac15-Imac17 SMBIOS, lower values.

Edited by Matgen84

Share this post


Link to post
Share on other sites
11 hours ago, Matgen84 said:

 

Thanks. :)

I try v3.2.2. On Catalina, SMBIOS Imac19,1 keys are not embedded in /S/L/E/IOUSBHostFamily.kext/C*/P*/AppleUSBHostPlatformProperties.kext/C*/Info.plist. There are only for Imac15-Imac17 SMBIOS, lower values.

I didn't know about this new location for USB power data in Catalina. Hackintool 3.3.3 has been released.

Share this post


Link to post
Share on other sites
Posted (edited)

Hi @headkaze

 

Few questions: latest release 3.3.6

  • It seems to have double HS ports in USB section
  • what is inject function in USB section
  • No more SSDT UBX generate!
  • USBPort: there is iMac19,1-XHC and iMac19,1-XHC-internal-hub, I don't understand why? I need some explanation to use it. Sorry.

I double check

Edited by Matgen84

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Matgen84 said:

Hi @headkaze

 

Few questions: latest release 3.3.6

  • It seems to have double HS ports in USB section
  • what is inject function in USB section
  • No more SSDT UBX generate!
  • USBPort: there is iMac19,1-XHC and iMac19,1-XHC-internal-hub, I don't understand why? I need some explanation to use it. Sorry.

I double check

The "Inject" button will inject USB ports like USBInjectAll does. It's currently an experimental feature.
 
So here are some quick instructions:
1. Click the Clear button and then the Inject button
2. It should inject the appropriate ports for XHC, EH01 and EH02 if the controllers are present
3. Click the Export button and copy USBPorts.kext to EFI/CLOVER/kexts/Other (or the appropriate place if using OpenCore)
4. Reboot into macOS again and then run Hackintool
5. Remove any unused ports using the usual port discovery procedure
6. Click the Export button and copy it to EFI/CLOVER/kexts/Other
7. Reboot
8. Run Hackintool again and check the ports have "stuck" by clicking Clear then Refresh
 
The downside to using this procedure is you can't use this method booting into macOS the first time so it's probably just easier to use USBInjectAll anyway.
 
It should not be doubling your ports (unless you clicked the Inject button) but it definately should not be generating an "iMac19,1-XHC-internal-hub" entry. Can you post your .ioreg here along with the USBPorts.kext.
Edited by headkaze

Share this post


Link to post
Share on other sites
36 minutes ago, headkaze said:
The "Inject" button will inject USB ports like USBInjectAll does. It's currently an experimental feature.
 
So here are some quick instructions:
1. Click the Clear button and then the Inject button
2. It should inject the appropriate ports for XHC, EH01 and EH02 if the controllers are present
3. Click the Export button and copy USBPorts.kext to EFI/CLOVER/kexts/Other (or the appropriate place if using OpenCore)
4. Reboot into macOS again and then run Hackintool
5. Remove any unused ports using the usual port discovery procedure
6. Click the Export button and copy it to EFI/CLOVER/kexts/Other
7. Reboot
8. Run Hackintool again and check the ports have "stuck" by clicking Clear then Refresh
 
The downside to using this procedure is you can't use this method booting into macOS the first time so it's probably just easier to use USBInjectAll anyway.
 
It should not be doubling your ports (unless you clicked the Inject button) but it definately should not be generating an "iMac19,1-XHC-internal-hub" entry. Can you post your .ioreg here along with the USBPorts.kext.

The problem with using USBInjectAll, it only supports Intel chipsets, not AMD chipsets.

Share this post


Link to post
Share on other sites
2 hours ago, Pavo said:

The problem with using USBInjectAll, it only supports Intel chipsets, not AMD chipsets.

If someone collects the port layouts for the various AMD USB controllers they can be added to USBInjectAll's USBInjectAll-Info.plist.

 

2 hours ago, Alpha22 said:

canceled and refresh remains the same

If I accept a USB port as being valid even if it doesn't have a UsbConnector entry in IORegistry it seems to be showing them even if they were removed as part of port discovery. This is obviously not a good thing so I've added back this check. Please try Hackintool v3.3.6.

Share this post


Link to post
Share on other sites
Posted (edited)
13 hours ago, headkaze said:
The "Inject" button will inject USB ports like USBInjectAll does. It's currently an experimental feature.
 
So here are some quick instructions:
1. Click the Clear button and then the Inject button
2. It should inject the appropriate ports for XHC, EH01 and EH02 if the controllers are present
3. Click the Export button and copy USBPorts.kext to EFI/CLOVER/kexts/Other (or the appropriate place if using OpenCore)
4. Reboot into macOS again and then run Hackintool
5. Remove any unused ports using the usual port discovery procedure
6. Click the Export button and copy it to EFI/CLOVER/kexts/Other
7. Reboot
8. Run Hackintool again and check the ports have "stuck" by clicking Clear then Refresh
 
The downside to using this procedure is you can't use this method booting into macOS the first time so it's probably just easier to use USBInjectAll anyway.
 
It should not be doubling your ports (unless you clicked the Inject button) but it definately should not be generating an "iMac19,1-XHC-internal-hub" entry. Can you post your .ioreg here along with the USBPorts.kext.

 

@headkaze

 

Thanks for your instruction. I follow them but my skills are weak.

 

  • I don't touch any connector type, I remove USR1/USR2, ITE device (Intel Wifi) HIC Intel Bluetooth, some others ports but not everything i wanted (type-C, USB-DAC for example, I've no device at this time)
  • If hackintool could automatically detect the type of connect, it would be great

 

I attach ioregistryexplorer file, screenshot, USBPorts. Thanks for your help.

 

Note: there are no kUSBSleepPowerSupply, kUSBWakePowerSupply in IOReg. No entries in Apple Get Info/USB

 

The detail of my Z390 config is in my signature.

 

 

 

 

 

Capture d’écran, le 2020-04-02 à 09.35.53.png

iMac de matgen84-2.ioreg.zip

USBPorts.kext.zip

Edited by Matgen84

Share this post


Link to post
Share on other sites
Posted (edited)
18 hours ago, headkaze said:

If I accept a USB port as being valid even if it doesn't have a UsbConnector entry in IORegistry it seems to be showing them even if they were removed as part of port discovery. This is obviously not a good thing so I've added back this check. Please try Hackintool v3.3.6.

@headkaze

 

latest version v3.3.6

canceled and refresh

 

Schermata-2020-04-02-alle-08-29-56.png

 

 

If you want to check and tell me if everything is ok

 

iMac di Fabio.zip

USBPorts.kext.zip

Edited by Alpha22

Share this post


Link to post
Share on other sites

 

It is posible to add a tab to check the "drivers" and the version of them both opencore and clover. And if you are misusing the driver64 folder.

 

 

 

Share this post


Link to post
Share on other sites

There seems to be something wrong with the bootloader detection. I'm using the latest OC from source (just compiled it)

 

 

Screenshot 2020-04-19 01.05.17.png

Share this post


Link to post
Share on other sites
On 4/18/2020 at 5:06 PM, Shaneee said:

There seems to be something wrong with the bootloader detection. I'm using the latest OC from source (just compiled it)

I get the version from IODeviceTree:/options/4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version. Has it changed recently?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×