Jump to content
headkaze

Hackintool v2.0.4

441 posts in this topic

Recommended Posts

3 minutes ago, onemanOSX said:

is the app dependant on any injector kexts in order for the usb to show up in the app?

 

The USB patching is not reliant on Lilu or WEG. In some ways it should be a separate app. The first post has a section called "USB Port Patching" which explains what you need (ie. USBInjectAll.kext for "port discovery" and the KextsToPatch for removing port limit). Once you create the USBPorts.kext you can remove them both.

Share this post


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

 

The USB patching is not reliant on Lilu or WEG. In some ways it should be a separate app. The first post has a section called "USB Port Patching" which explains what you need (ie. USBInjectAll.kext for "port discovery" and the KextsToPatch for removing port limit). Once you create the USBPorts.kext you can remove them both.

Was having an offline discussion with erroruser earlier on and your explanation confirms it. Indeed usbinjector kext and kext to patch is a requirement. Thank you.

Share this post


Link to post
Share on other sites

FB-Patcher v1.4.2 have some bug!

1.FB Port Limit function is inoperative!

2.I checked VRAM 2048MB and DP->HDMI,when I unchecked them ,the app not cancel it

 

sorry for my bad English:no:

Share this post


Link to post
Share on other sites
33 minutes ago, Mison said:

FB-Patcher v1.4.2 have some bug!

1.FB Port Limit function is inoperative!

2.I checked VRAM 2048MB and DP->HDMI,when I unchecked them ,the app not cancel it

 

sorry for my bad English:no:

 

It's fixed in 1.4.3, thanks!

Share this post


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

1.FB Port Limit function is inoperative!

I've changed Intel FB-Patcher to just set Connector Index to -1 to disable. I think this is enough to disable but if I'm wrong please let me know.

Share this post


Link to post
Share on other sites
45 minutes ago, headkaze said:

I've changed Intel FB-Patcher to just set Connector Index to -1 to disable. I think this is enough to disable but if I'm wrong please let me know.

I will try it.

I think it should be showed on Connector Info.

More intuitionistic:D

Share this post


Link to post
Share on other sites
54 minutes ago, Mison said:

I think it should be showed on Connector Info.

It does show in Connector Info. Doesn't it?

45 minutes ago, Mison said:

It seem that something is wrong.

What is wrong? Looks okay to me.

Share this post


Link to post
Share on other sites
20 minutes ago, headkaze said:

It does show in Connector Info. Doesn't it?

What is wrong? Looks okay to me.

framebuffer-con1 is missing?

I think con1 connector type shoud be seted to HDMI, but I cannot find this patch in config.plist.

Share this post


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

framebuffer-con1 is missing?

I think con1 connector type shoud be seted to HDMI, but I cannot find this patch in config.plist.

con1 for 0x591B0000 is default set to HDMI

Share this post


Link to post
Share on other sites
On 9/27/2018 at 2:46 AM, Faradis said:

@headkaze

still the same blank screen on usb tab

also What boot flag to use to get the dump of frambuffer??

I think that there must be an exception during the startup of Intel FB-Patcher. Can you show me a screenshot of your System Info and Audio Info tabs? It might give me a clue otherwise I might have to add some logging.

 

The first post explains how to get a dump of your framebuffer or the alternative of using the data built into Intel FB-Patcher. There is also a short guide on setting up USB but as I said I think your issue may be an exception on launch.

Share this post


Link to post
Share on other sites
17 minutes ago, headkaze said:

I think that there must be an exception during the startup of Intel FB-Patcher. Can you show me a screenshot of your System Info and Audio Info tabs? It might give me a clue otherwise I might have to add some logging.

 

The first post explains how to get a dump of your framebuffer or the alternative of using the data built into Intel FB-Patcher. There is also a short guide on setting up USB but as I said I think your issue may be an exception on launch.

here is thing you asked for. if you need more file tell me :)

Screenshot 2018-09-29 at 1.26.40 AM.png

Screenshot 2018-09-29 at 1.28.41 AM.png

Screenshot 2018-09-29 at 1.29.24 AM.png

Share this post


Link to post
Share on other sites
50 minutes ago, Faradis said:

here is thing you asked for. if you need more file tell me :)

Sorry I mean System Info in Intel FB-Patcher (under General tab).

 

EDIT: I've gone over the initialization routine. I may have fixed it? Try downloading again and see if it makes a difference.

Edited by headkaze

Share this post


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

I hope you can add 9m cursor patch in this app.

 

"DVMT pre-alloc 32 MB" advanced setting sets 19 MB Stolen (Framebuffer) and 9 MB FBMem (Cursor).

Share this post


Link to post
Share on other sites
59 minutes ago, headkaze said:

 

"DVMT pre-alloc 32 MB" advanced setting sets 19 MB Stolen (Framebuffer) and 9 MB FBMem (Cursor).

My mean is cursormemorysize, not FBMem.Are they the same thing?

42A67C23-14C9-4267-8249-A413E7144A60.thumb.png.6600eeb0cc025365d55b78cdec98d893.png

AB018574-98CC-49E8-8588-C6A64FF1CF46.thumb.png.8b176bae86d34434bcaa23bdd2f2b5d5.png

Share this post


Link to post
Share on other sites
9 hours ago, Mison said:

My mean is cursormemorysize, not FBMem.Are they the same thing?

 

Okay for Haswell you're right I did not have support for framebuffer-cursormem. Please download Intel FB-Patcher 1.4.5.

Share this post


Link to post
Share on other sites
15 hours ago, headkaze said:

 

Okay for Haswell you're right I did not have support for framebuffer-cursormem. Please download Intel FB-Patcher 1.4.5.

Thank you for your great work.:thumbsup_anim:

Share this post


Link to post
Share on other sites

Intel FB-Patcher 1.4.6 Released
- Fixes. Added Framebuffer->macOS 10.14 (18A389) menu item. Added QE/CI and Metal support detection

 

NOTE: there was a bug in the previous release that could mean the generated patch was not right (Eg. Missing framebuffer-patch-enable entry). Apologies for any problems this may have caused.

Share this post


Link to post
Share on other sites

Someone can help me I'm experiencing problems with the graph in Mojave, I've done everything and I can not leave it enabled, I always have to disable it before the boot to enter the system. Can someone help me please!!

Someone can help me I'm experiencing problems with the graph in Mojave, I've done everything and I can not leave it enabled, I always have to disable it before the boot to enter the system. Can someone help me please!!

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.

×