headkaze Posted September 26, 2018 Author Share Posted September 26, 2018 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. Link to comment Share on other sites More sharing options...
onemanOSX Posted September 26, 2018 Share Posted September 26, 2018 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. Link to comment Share on other sites More sharing options...
Mison Posted September 27, 2018 Share Posted September 27, 2018 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 1 Link to comment Share on other sites More sharing options...
headkaze Posted September 27, 2018 Author Share Posted September 27, 2018 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 It's fixed in 1.4.3, thanks! Link to comment Share on other sites More sharing options...
headkaze Posted September 27, 2018 Author Share Posted September 27, 2018 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. Link to comment Share on other sites More sharing options...
Mison Posted September 27, 2018 Share Posted September 27, 2018 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 Link to comment Share on other sites More sharing options...
Mison Posted September 27, 2018 Share Posted September 27, 2018 I exported data to config.plist. It seem that something is wrong. Link to comment Share on other sites More sharing options...
headkaze Posted September 27, 2018 Author Share Posted September 27, 2018 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. Link to comment Share on other sites More sharing options...
Mison Posted September 27, 2018 Share Posted September 27, 2018 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. Link to comment Share on other sites More sharing options...
headkaze Posted September 27, 2018 Author Share Posted September 27, 2018 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 Link to comment Share on other sites More sharing options...
Mison Posted September 27, 2018 Share Posted September 27, 2018 1 hour ago, headkaze said: con1 for 0x591B0000 is default set to HDMI o, you are right. Link to comment Share on other sites More sharing options...
Faradis Posted September 27, 2018 Share Posted September 27, 2018 (edited) @headkaze still the same blank screen on usb tab also What boot flag to use to get the dump of frambuffer?? ioreg.txt CLOVER.zip Edited September 27, 2018 by Faradis Link to comment Share on other sites More sharing options...
headkaze Posted September 28, 2018 Author Share Posted September 28, 2018 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. Link to comment Share on other sites More sharing options...
Faradis Posted September 28, 2018 Share Posted September 28, 2018 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 Link to comment Share on other sites More sharing options...
headkaze Posted September 28, 2018 Author Share Posted September 28, 2018 (edited) 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 September 28, 2018 by headkaze Link to comment Share on other sites More sharing options...
headkaze Posted October 1, 2018 Author Share Posted October 1, 2018 Version 1.4.4 Released - Added ability to inject valid device-id's 1 Link to comment Share on other sites More sharing options...
Mison Posted October 1, 2018 Share Posted October 1, 2018 I hope you can add 9m cursor patch in this app. Link to comment Share on other sites More sharing options...
headkaze Posted October 1, 2018 Author Share Posted October 1, 2018 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). Link to comment Share on other sites More sharing options...
Mison Posted October 1, 2018 Share Posted October 1, 2018 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? Link to comment Share on other sites More sharing options...
headkaze Posted October 1, 2018 Author Share Posted October 1, 2018 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. 1 Link to comment Share on other sites More sharing options...
Mison Posted October 2, 2018 Share Posted October 2, 2018 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. Link to comment Share on other sites More sharing options...
headkaze Posted October 4, 2018 Author Share Posted October 4, 2018 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. 1 1 Link to comment Share on other sites More sharing options...
pteix Posted October 5, 2018 Share Posted October 5, 2018 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!! Link to comment Share on other sites More sharing options...
STLVNUB Posted October 5, 2018 Share Posted October 5, 2018 First off make a signature with your specs then people may be able to help you. Link to comment Share on other sites More sharing options...
headkaze Posted October 6, 2018 Author Share Posted October 6, 2018 Version 1.4.7 Released - Added support for new WEG -igfxfbdump boot flag using File->Import->IOReg Dump menu Link to comment Share on other sites More sharing options...
Recommended Posts