Contribute
Register

[Release] Hackintool v3.x.x

im using a coffee lake cpu with a 0xE920003 PlatformID but there isn't any Frame-buffer option for it
It's there. Did you scroll down the bottom of the drop down list?
and i was trying to use -igfxdump -igfxfbdump to get my Frame-buffer but nothing
That's okay using the Framebuffer->macOS 10.14 option should be good enough.
 
It's there. Did you scroll down the bottom of the drop down list?

That's okay using the Framebuffer->macOS 10.14 option should be good enough.
i have been using the macOS 10.14 with 0x3E9B007 nut that just boots into a black screen whne i use the id for my system this i what the tool shows me Screen Shot 2019-01-15 at 11.27.47 PM.pngScreen Shot 2019-01-15 at 11.28.05 PM.png
 
i have been using the macOS 10.14 with 0x3E9B007 nut that just boots into a black screen whne i use the id for my system this i what the tool shows me
Well 0x3E920003 would be a terrible choice unless you intend on not using your IGPU. You will notice the little icon with the mans head missing. That icon means it's 'headless' and is only used in special cases so you probably want to use the recommended Platform ID of 0x3E9B0007 or the default 0x3EA50000. Black screen can be caused by different issues but it doesn't necessarily mean you're using a bad Platform ID. It could mean DVMT pre-alloc is set too low in your BIOS or some other mis-configuration in ACPI or in config.plist. From what I understand Mojave and Coffee Lake in general has many compatibility problems as I hear about this "black screen" issue over and over again.
 
Well 0x3E920003 would be a terrible choice unless you intend on not using your IGPU. You will notice the little icon with the mans head missing. That icon means it's 'headless' and is only used in special cases so you probably want to use the recommended Platform ID of 0x3E9B0007 or the default 0x3EA50000. Black screen can be caused by different issues but it doesn't necessarily mean you're using a bad Platform ID. It could mean DVMT pre-alloc is set too low in your BIOS or some other mis-configuration in ACPI or in config.plist. From what I understand Mojave and Coffee Lake in general has many compatibility problems as I hear about this "black screen" issue over and over again.
hmm ok i undrestand didn't know coffeelake would be this much of a problem . i dont have an on option to change DVMT pre-alloc in the uefi but i use framebuffer-stolenmem 00003001 to but and thats when i get the black screen . could the problem be from having too much DVMT pre-alloc ? but if i try to boot without the framebuffer-stolenmem the system kernel panic and reboot .
 
hmm ok i undrestand didn't know coffeelake would be this much of a problem . i dont have an on option to change DVMT pre-alloc in the uefi but i use framebuffer-stolenmem 00003001 to but and thats when i get the black screen . could the problem be from having too much DVMT pre-alloc ? but if i try to boot without the framebuffer-stolenmem the system kernel panic and reboot .
I just can't imagine a modern Coffee Lake PC having DVMT pre-alloc set to 32 MB by default. It's odd you need to set that. Are you using the Patch->Advanced->DVMT pre-alloc 32 MB option? It's not just framebuffer-stolenmem that needs to be set but framebuffer-fbmem also. This option will set them both for you. If your BIOS has it set above 32 MB you shouldn't have any issues.
 
I just can't imagine a modern Coffee Lake PC having DVMT pre-alloc set to 32 MB by default. It's odd you need to set that. Are you using the Patch->Advanced->DVMT pre-alloc 32 MB option? It's not just framebuffer-stolenmem that needs to be set but framebuffer-fbmem also. This option will set them both for you. If your BIOS has it set above 32 MB you shouldn't have any issues.
i am using framebuffer-fbmem also but i think my system system DVMT pre-alloc is set to 128mb im not 100% but thats what came up when i good this system
 
Could you maybe share your config.plist file? I'd be curious to see what SMBIOS you used and whether or not you spoofed your graphics device ID. Plus other stuff...
Here is my config.plist. Normally I use an RX580 and the HD 630 only for quick-sync, but if I get the HD 630 fully working, I sell the RX580.
 

Attachments

  • config18.1.plist.zip
    5.7 KB · Views: 86
I don not know how your tool reads the values, but without changing the pipe values, the tool will show me 18, 18, 18, while the 5912 ID settings are 9, 10, 10. See also the picture.
 

Attachments

  • FBP-KBL_5912.png
    FBP-KBL_5912.png
    82.4 KB · Views: 96
I don not know how your tool reads the values, but without changing the pipe values, the tool will show me 18, 18, 18, while the 5912 ID settings are 9, 10, 10. See also the picture.
try using hackintool-v1-7-4
 
I know i'm off topic but found this thread and I think it may worth a try. I have a couple of Hackintoshes and this forum always been of much help. One of my last projects is an iMac 27' 2011 with an upgraded GPU. It's a 780m with a dell/alienware BIOS. I've been following long threads from macrumors and netkas and none have figured it out yet (we are all waiting for Macvidcards to write a proper rom). The problem with this card, besides not having boot screen, (there is no rom with apple efi available for this card) is that the iMac detects the display as external, with no ability of brightness dimming, keeping it up to 100%.
You guys here have tons more knowledge than me, and was hoping you can tell me if this utility can help me correct the connectors that may be causing this problem. I don't know if this would work with Nvidia cards or it's just working with intel IGPUs.
Thanks in advance.
 
Last edited:
Back
Top