Jump to content

Hackintool v3.x.x

headkaze

By headkaze,
in Hackintosh Tools

 Share
1059 posts in this topic

Recommended Posts

miliuco
miliuco
Posted
Posted (edited)

@kaoskinkae

Yes, I see, the file got from Hackintool is missing the EC device, it has only USBX device. I don't know why. SSDT-EC-USBX file included in OpenCore package has both devices.

 

Edited by miliuco
kaoskinkae
kaoskinkae
Posted
Posted
On 1/24/2022 at 2:36 PM, miliuco said:

@kaoskinkae

You can post an issue in the bug tracker, so @headkaze can read it.

It's here

https://github.com/headkaze/Hackintool/issues

You must have an GitHub account and go to New Issue.

Saludos.

perfect public

miliuco
miliuco
Posted
Posted (edited)
3 hours ago, kaoskinkae said:

perfect public

 

I see, waiting for @headkazecomment.

 

I've been checking old versions, e.g. 3.6.0 and 3.4.0, and SSDT-EC-USBX file is always the same, only USBX part, it seems that Hackintool has built the same SSDT since the beginning.

We know that SSDT-EC-USBX is recommended for Skylake desktops and newer and AMD CPUs, SSDT-EC is for Broadwell and older. I don't know why Hackintool builts this so named SSDT-EC-USBX file. But I'm sure Headkaze has a valid explanation for it.

Edited by miliuco
kaoskinkae
kaoskinkae
Posted
Posted
On 1/30/2022 at 1:30 AM, miliuco said:

@kaoskinkae

Your issue has been useful, Headkaze is going to add EC device to this SSDT. Really I haven't noticed this detail, you're more observant than me 🙂

You know that with the yotube channel and facebook and telegran in Spanish I don't stop investigating and giving support

image.png

  • Like 1
  • 2 months later...
joevt
joevt
Posted
Posted
11 minutes ago, 5T33Z0 said:

Is there a reason why there is no "Comet Lake" category in the dropdown menu for the creating Framebuffer patches or is the data just not implemented yet?

I don't think any Macs used Comet Lake.

macOS doesn't have Comet Lake drivers? See Intel Graphics Drivers at:

 https://forums.macrumors.com/threads/intel-graphics-and-5120x1440-testing-in-big-sur.2244174/

 

OpenCore has notes for Comet Lake so I guess it's supposed to work.

 https://dortania.github.io/OpenCore-Install-Guide/config.plist/comet-lake.html#starting-point

 

If you're using Comet Lake in a Hackintosh, what drivers does it say are loaded? 

kextstat | grep -i graphics

Maybe it uses Coffee Lake (CFL)?

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted (edited)

@joevt Thanks for the explanation and the links.

 

As for GREP it spits out these results: 

steezo@iMac ~ % kextstat | grep -i graphics
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
  110   11 0xffffff7f9b13e000 0x2f000    0x2f000    com.apple.iokit.IOGraphicsFamily (585.2) 17732FC2-63ED-3059-B006-A492D276F99C <14 8 6 5 3 1>
  111    5 0xffffff7f99950000 0x4000     0x4000     com.apple.AppleGraphicsDeviceControl (6.3.6) 1151AFDA-B186-34D1-9675-D0901B34BE02 <110 14 8 7 6 5 3 1>
  113    0 0xffffff7f99dcd000 0xc1000    0xc1000    com.apple.driver.AppleIntelCFLGraphicsFramebuffer (16.0.5) 36017EC6-D31F-3F2E-9AD1-0D9E68ECF2E2 <112 111 110 42 14 13 8 7 6 5 3 1>
  124    0 0xffffff7f9a6ad000 0xb9000    0xb9000    com.apple.driver.AppleIntelKBLGraphics (16.0.5) D8AE3E77-5EEA-3DE4-8753-AADD31988F03 <112 110 87 14 8 7 6 5 3 1>
  136    1 0xffffff7f9993c000 0x1000     0x1000     com.apple.driver.AppleGraphicsControl (6.3.6) AEAE3F49-2C66-3BD0-BAA4-90BB45C99CCC <8 6 5 3 1>
  137    0 0xffffff7f99958000 0xa000     0xa000     com.apple.driver.AppleGraphicsDevicePolicy (6.3.6) 9AD8C808-E931-32FF-8826-BA30B5BDB3D1 <136 111 110 14 13 8 7 6 5 3 1>
steezo@iMac ~ %  ioreg -lw0 | grep "AAPL,ig-platform-id"
    | |   | |   "AAPL,ig-platform-id" = <07009b3e>
steezo@iMac ~ %  kextstat | grep Intel | egrep "Graphics|Framebuffer"
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
  113    0 0xffffff7f99dcd000 0xc1000    0xc1000    com.apple.driver.AppleIntelCFLGraphicsFramebuffer (16.0.5) 36017EC6-D31F-3F2E-9AD1-0D9E68ECF2E2 <112 111 110 42 14 13 8 7 6 5 3 1>
  124    0 0xffffff7f9a6ad000 0xb9000    0xb9000    com.apple.driver.AppleIntelKBLGraphics (16.0.5) D8AE3E77-5EEA-3DE4-8753-AADD31988F03 <112 110 87 14 8 7 6 5 3 1>

 

Edited by 5T33Z0
joevt
joevt
Posted
Posted
1 hour ago, 5T33Z0 said:

@joevt Thanks for the explanation and the links.

 

As for GREP it spits out these results: 

steezo@iMac ~ %  kextstat | grep Intel | egrep "Graphics|Framebuffer"
  113    0 0xffffff7f99dcd000 0xc1000    0xc1000    com.apple.driver.AppleIntelCFLGraphicsFramebuffer (16.0.5) 36017EC6-D31F-3F2E-9AD1-0D9E68ECF2E2 <112 111 110 42 14 13 8 7 6 5 3 1>
  124    0 0xffffff7f9a6ad000 0xb9000    0xb9000    com.apple.driver.AppleIntelKBLGraphics (16.0.5) D8AE3E77-5EEA-3DE4-8753-AADD31988F03 <112 110 87 14 8 7 6 5 3 1>

Same as my Mac mini 2018 which is Coffee Lake.

 

55 minutes ago, badbrain said:

That's not right:

iMac20,1: https://everymac.com/ultimate-mac-lookup/?search_keywords=iMac20%2C1

iMac20,2: https://everymac.com/ultimate-mac-lookup/?search_keywords=iMac20%2C2

Thanks. I didn't do an extensive search - I was just going by the list of Intel*Graphics drivers. Now we know that Comet Lake uses Coffee Lake graphics drivers. Coffee Lake graphics drivers uses Kaby Lake graphics drivers for the parts that don't have a Coffee Lake version. The frame buffer part is Coffee Lake and so is the VAME part (whatever that is?). The other parts are Kaby Lake.

 

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted

@joevt Thanks. I was asking because a couple of days ago my GPU died and now I have to use the iGPU in the until the new card arrives. While booting with the Framebuffer patch for the iGPU, I notice some stalling before reaching the desktop. My guess it's due to the framebuffer for my i9 10850K isn't optimal, so I was looking into fine tuning it.

rafale77
rafale77
Posted
Posted

In regards to Comet Lake, using the iMac20,2 SMBIOS, the PCIe section shows this:

 

I am using the headless iGPU framebuffer recommended by WEG: 9BC800003

which can also be found under the Hackingtool patch menu under coffee lake. I am guessing the device name below is purely hackintool cosmetic.

 

Note also some of the CPU devices being reported as a "Xeon" while others are correctly reported as "Comet Lake" by Hackintool... Maybe a database update for Hackintool is needed?

 

image.thumb.png.cdac1d5e996074e62f67d98902cd44f6.png

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted

@rafale77 In my case it's showing the correct CPU description. As far as the Frambuffer is Concerned, hackintool detects the Laptop version of th UHD 630 which irritates me, since it's an i9 CPU.

 

Anyway, the database for the PCI devices is included in the App in the Resources > PCI folder. It's called pci.ids. You can get the latest version of it from The PCI ID repository: https://pci-ids.ucw.cz/

rafale77
rafale77
Posted
Posted
5 minutes ago, 5T33Z0 said:

@rafale77 In my case it's showing the correct CPU description. As far as the Frambuffer is Concerned, hackintool detects the Laptop version of th UHD 630 which irritates me, since it's an i9 CPU.

 

Anyway, the database for the PCI devices is included in the App in the Resources > PCI folder. It's called pci.ids. You can get the latest version of it from The PCI ID repository: https://pci-ids.ucw.cz/

 

Thanks! Just tried installing it but the result is the same. It is odd that your CPU description is correct and not mine. What framebuffer did you inject? That could be the reason why you are getting a Laptop UHD630.

The only Mac with Comet Lake is the iMac20,x which uses its iGPU headlessly. If you are going to use for display you would be better off using a coffee lake framebuffer like 3E9B0007 and patch the connectors. I have tried both on my machine and it works.

 

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted

@rafale77 I am using the one mentioned in the OpenCore Install Guide for Coemt Lake, when using the iGPU for driving a display: AAPL,ig-platform-id 07009B3E. Which, according to Whatevergreen's Intel HD Faq is for a desktop (0x3E9B0007). That's the one you mentioned. My GPU is dead and I am still waiting for a replacement. So in the meantime I have to use the iGPU. I was shocked how bad its performance is in Davinci Resolve when performing the simplest of tasks.

 

I just realized that you can update the pci.ids file from within Hackintool itself (there's a download icon on th the PCI tab), so there's no need to update it manually.

rafale77
rafale77
Posted
Posted

@5T33Z0, Not sure if this is going to help you but... I suspected that the problems had something to do with the device ID being injected in the device properties so I took out that entry and sure enough... problem fixed on the iGPU.

 

I was assuming that the device ID should be a hex transposition of the framebuffer as it had been on my previous hack. It's not the case: Device ID:0x9BC5 for framebuffer 0x9BC800003.

 

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted

@rafale77 The device-id is provided by the CPU. You can find it in the Specs for your CPU on Intel's site. For the 10th Gen Intel Core i9 it's 0x9BC5 and if you change the "endianess" for OpenCore, then it's C59B0000.

I disabled it now and rebooted.  Performance is still the same. I'm going to try different Framebuffers from the list.

kocoman
kocoman
Posted
Posted

 

can this tool dump these variables?

 

Debugger called: </Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-16.0.31/IONDRV/IVB/AppleIntelFramebuffer/AppleIntelController.cpp:14147 Assertion failed: (0 == i) || ((pfbInfo->rangeStolen.physBase - pfbInfoPrev->r

(0 == i) || ((pfbInfo->rangeStolen.physBase - pfbInfoPrev->rangeStolen.physBase) == fFramebufferMemorySize)

 

thx

  • 2 months later...
Allan
Allan
Posted
Posted

@headkaze how are you?

 

I'm using the Lenovo Gamming 3i as my main Hackintoh, and it's screen resolution is 1920x1080, but all the itens is soo terrible small.


And I wanna use Hackintool to add more resolution options, but before that I want to understand the options available at the app, such as:

 

Spoiler

Screen Shot 2022-06-28 at 14.08.25.png

 

  • HiDPI 1, 2 and etc...
  • Non Scaled
  • Auto

Wich I need to use?


I've made some tests, and add the .kext generated by the Hackintool with OpenCore, but after a reboot, the options that I want won't appears.

 

Thank you 😃

Allan
Allan
Posted
Posted
2 hours ago, eSaF said:

Hi Buddy - Are you sure it's not down to old age and bad eye sight? :) - Sorry for the levity pal I couldn't resist, please don't be harsh with me ---and yes I was the class clown at school. :graduated: 

That aside hope you get it sorted.

lol!

 

I was so worried about it, that I've put some glasses hehehe 🤓

But still the same

  • Like 2
  • Haha 1
Allan
Allan
Posted
Posted

Look how it looks, and I hope it helps.

 

I was using the one-key-hidpi script by @xzhih, but I have problems with sleep.

 

1600x900

 

Spoiler

1600x900.png

 

1920x1080

 

 

Spoiler

1920x1080.png

 

 

At Windows I feel more comfortable with 1080p, but at the macOS all the thing is much smaller.

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...