[Release] Hackintool v3.x.x

[patrickfogle]

This looks to be an outstanding and useful tool! Unfortunately, when I enter in the options that I need and I click "Generate Patch" FBPatcher crashes. Can anybody give me an idea why? (A screenshot of the options I am choosing before I click "Generate Patch" is below). Thank you.

 

[patrickfogle]

This looks to be an outstanding and useful tool! Unfortunately, when I enter in the options that I need and I click "Generate Patch" FBPatcher crashes. Can anybody give me an idea why? (A screenshot of the options I am choosing before I click "Generate Patch" is below). Thank you.

View attachment 359551

@headkaze, I have narrows it down to the fact that it crashes anytime I check the "Devices/Properties" option and click "Generate Patch." Any idea why it is crashing?

 

[headkaze]

How come the red highlight for an external display doesn't seem to work in the recent FB Patcher versions?

If the port index is -1 then the connector is considered disabled. So you probably have Patch->Advanced->FB Port Limit enabled or something.

@headkaze, I have narrows it down to the fact that it crashes anytime I check the "Devices/Properties" option and click "Generate Patch." Any idea why it is crashing?

Is there any way you can get a crash log? Maybe in ~/Library/Logs/DiagnosticReports/

 

[headkaze]

Clearly, an HDMI connector on Pipe 8 is not supported. Note, Console showed IA-32 errors at the time or two I saw the crash happen.
If interested, I can test Pipes 3, 9, 10 and 11.

That would be helpful. If we can figure out why it's crashing we may be able to understand the pipe value better.

 

[patrickfogle]

Is there any way you can get a crash log? Maybe in ~/Library/Logs/DiagnosticReports/

I found the correct location for the logs I think. But I do not see any FBPatcher logs. Any ideas?

 

[patrickfogle]

I found the correct location for the logs I think. But I do not see any FBPatcher logs. Any ideas?

@headkaze sorry about the funny edits.

 

[patrickfogle]

I found the correct location for the logs I think. But I do not see any FBPatcher logs. Any ideas?

@headkaze

FBPatcher has crashed on 3 separate systems (3 different downloads). Seems strange. I cannot find any crashlogs. Ideas?

 

[jaymonkey]

Hi Headkaze,

Really good to see how this little App is developing ... really great work.

I've just been testing the latest version on my desktop system to get a few screen grabs to update my guide :-

https://www.tonymacx86.com/threads/an-idiots-guide-to-lilu-and-its-plug-ins.260063/

Since the introduction of the audio page (Speaker Icon) where a user can select a supported Layout FB-Patcher no longer detects or reports the codec and current layout-id value.

I have the latest version of Lilu, whatEverGreen and AppleALC installed, which it detects ok:



But nothing reported on the Audio page :-



AppleALC is loading and working fine as seen by looking at the HDEF device :-



I have no problem at all with Audio every thing working fine using layout 1 as defined by Device Properties :-

<key>Devices</key>
    <dict>
        <key>Audio</key>
        <dict>
            <key>AFGLowPowerState</key>
            <true/>
            <key>Inject</key>
            <string>No</string>
            <key>ResetHDA</key>
            <true/>
        </dict>
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                BAASBA==
                </data>
            </dict>
        </dict>
    </dict>

Note: To keep the code snippet small I removed none audio related entries.

The above code Device Property code was generated by a earlier version of FB-Patcher before you introduced the dedicated audio page with the layout drop down menu.

The Codec is a ALC1150 ... PID/VID is 10EC,0900 :-



Like I said I don't have any system related issues, just reporting that the latest version of FB-Patcher is not detecting/displaying the audio codec information .....

Let me know if you need any more info to debug the issue.

Cheers
Jay

 

[headkaze]

@patrickfogle can you run Console and filter Process name by FBPatcher. See if there is any error coming up there.

@jaymonkey please download FB-Patcher again and do the above before launching. I've added some init log output.

 

[patrickfogle]

@patrickfogle can you run Console and filter Process name by FBPatcher. See if there is any error coming up there.

@headkaze

I’ll do it and let you know. Thanks