Jump to content


  • Content Count

  • Joined

  • Last visited

About MacKonsti

  • Rank
    InsanelyMac Sage

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Muppet Show

Recent Profile Visitors

5,853 profile views
  1. Hi @Cyberdevs and thanks for maintaining this topic alive. It seems the original developer's site is shut down or not reachable. Can you tell us which version you are using as I see two different "latest" versions going around in file hosting (of old apps) websites, like v1.3.3.2 and v1.3.4.0 so not sure if these are fakes or if the developer pushed one last version before giving it up.... Thanks again! (for example https://www.filehorse.com/download-bootice/ features a different latest version compared to https://www.majorgeeks.com/files/details/bootice_64_bit.html or https://www.softpedia.com/get/System/Boot-Manager-Disk/Bootice.shtml )
  2. MacKonsti


    Thank you VERY much for your work on a Sunday morning, it works straight away with and without my Clover injection! First, I replaced the kext in Clover/Other and booted, while keeping the existing device-properties injected; booted OK sans KP. Then, I removed the device-properties completely, and booted again without issues. Works great for PCI ID 14e4:43a3 and subsystem ID 17aa:075a as ASPM is shown disabled in Hackintool, I also see pci-aspm-default set to 0 in IORegistryExplorer. I will keep testing the beta kext for stability checking. Currently, CPU idle utilisation seems as low as before. I hope this code-fix will make it to the official release! Here is my kernel output since boot time and attaching a screenshot of IORegistry Explorer for renamed device ARPT. Merci, thank you, gracias, Danke, graze, Спасибо, ευχαριστώ. BCM4350.log
  3. MacKonsti


    Salut @Hervé and thank you again in person for your guide. I am not trying to re-invent the wheel, I was merely asking why faking a device compatibility to be used by a third-party kext where we have (as community) control Yes that T77H649.00 variant card of mine does show P/N 00JT494 but as you know, many vendors fake the items and put fake stickers... so we can never be sure. But what you wrote is indeed very helpful that I did not find in your guide: "If your laptop had a BIOS whitelist that did not support the card you use, you'd never be able to get past BIOS POST. Clearly it's not the case so any questioning or discussion about whitelist is irrelevant here." I didn't know about betting beyond the BIOS POST, thanks (and of course no whitelist talk was initiated, I was merely referring to BIOS hacks that allow other Lenovos to access hidden settings). So to cut a long story short, as you saw my Clover device properties injection, I am indeed using your guide and after few reboots, I did confirm that these work great.. And thanks for confirming that the "subsystem id gets changed from 17aa:075a to 106b:075a after the Broadcom kext has loaded. You probably did not realize that vendor ids 17aa=Lenovo and 106b=Apple" as I had noted it down but was curious as to why that changed when checking again in IORegistry Explorer before making my post. Very useful info, merci. Hi @lvs1974 thanks for posting this good news update. Is your commit referring to only pci-aspm-default only or also includes the above card details i.e. PCI ID 14e4:43a3 and subsystem ID 17aa:075a too?
  4. MacKonsti


    Thanks for your reply. Yes I read some stuff about "whitelisting" on Lenovos... not sure what is really happening under the hood, however. My BCM4350 card T77H649.00 variant is supposed to be for Lenovo (shows P/N 00JT494) according to @Hervé post over at OSX Latitude and yes: The BIOS still has an option to enable/disable the card, after replacing it (but I doubt it would get hidden if the card was blacklisted somehow?) but it does control the hardware (confirmed it); Another disk running Windows 10 has the card working fine; Catalina with Clover device properties injection above + AirportBrcmFixup.kext works great (including BTLE via other kexts of course). It's just my surprise that this card blocks booting (in vanilla) and that I need Clover to inject a compatible device for AirportBrcmFixup.kext to work instead having AirportBrcmFixup.kext do this automatically... What we need @fallen00sniper is to find the Lenovo hidden BIOS settings and how to enable them that may possibly provide some further understanding/unlocking but I have not found them for IdeaPad... only for some others
  5. MacKonsti


    Hello everyone, I am hoping to reach a developer of AirportBrcmFixup as I would like to report and confirm an issue facing with a BCM4350 card (supposedly DW1820A). I didn't pay attention to the part number when ordering from a well-known Asian website, and eventually I received the version T77H649.00 variant for my Lenovo. The card is not detected out-of-the-box in Catalina (in AirPortBrcmNIC I think) and it prevents booting the system without tweaking. Now, when booting with the card enabled (in BIOS) and vanilla AirportBrcmFixup.kext in Clover (kexts/Other folder) the system at some points stops loading, just like that. The only way to manage to reach the Catalina 10.15.5 desktop is to inject some device properties in Clover, namely: <key>PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)</key> <dict> <key>AAPL,slot-name</key> <string>WLAN</string> <key>compatible</key> <string>pci14e4,4353</string> <key>device_type</key> <string>AirPort Extreme</string> <key>name</key> <string>AirPort</string> <key>pci-aspm-default</key> <integer>0</integer> <key>model</key> <string>Broadcom BCM4350 Wireless Network Adapter</string> </dict> Any other "compatible" ID such as 14e4:4331 will result to a KP during boot or just freezing. Is it normal to need to inject such device properties for my card, so that AirportBrcmFixup can work? Anyone else having such a BCM4350 / DW1820A that absolutely needs properties like that? The card works well, I am just puzzled that we need to fake to make a third-party kext work My card details are PCI ID 14e4:43a3 and subsystem ID 106b:075a not sure why not 17aa:075a per other threads found :/ Can anyone let me know if we can add these details to the code of AirportBrcmFixup so that some next official release would work with just the vanilla AirportBrcmFixup.kext? Thank you in advance @vit9696 @lvs1974
  6. MacKonsti

    Intel Framebuffer patching using WhateverGreen

    So from your experience, since my computer has no HDAU device natively like other desktops, would making an SSDT that adds to GFX0 (renamed to IGPU via WhateverGreen) such a device under it with name HDAU so that the system detects the sound-output for HDMI? I've seen some SSDT code for laptops adding HDAU right under the graphics device, but not sure if it was for NVIDIA or AMD... perhaps WhateverGreen in combination with AppleALC would make this injected HDAU device active...
  7. MacKonsti

    Intel Framebuffer patching using WhateverGreen

    I am not sure it's changing it completely, mate. Besides, I cannot find any reference to 0xA170... Using FakePCIID.kext and its HDMI Audio injection, I get 2 different audio Codec devices under HDEF now, as posted earlier. Allow me to repeat that the ACPI/firmware has no HDAU or B0D3 device present... IOHDACodecDevice@1F,3,0 --> the original one IOHDACodecDevice@1F,3,2 --> the added one for DP/HDMI output So could it be that FakePCIID+HDMI Audio injection create a new digital audio device? Especially in the absence of a HDAU-B0D3 absence?
  8. This is a thread for Bluetooth mate and using the BrcmPatchRAM kext in Catalina, you refer to a Wi-Fi problem, not the correct discussion here I think.
  9. MacKonsti

    Intel Framebuffer patching using WhateverGreen

    Thank you @headkaze for your reply. I could not replicate the issue first detected with early Mojave versions and early WhateverGreen.kext where the Geekbench graphics score went up to 55000, perhaps later Mojave drivers for IGPU changed (or used the Apple GuC firmware natively, who knows, but igfxfw=2 does not increase performance or score, today). All I can tell you is that if I do not "force" some AAPL,ig-platform-id I get lower GPU scores when using WhateverGreen natively-vanilla, just tested today: On my NUC8i7BEH computer with Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) set as MacMini8,1 in SMBIOS: Scenario 1) Clean Clover configuration, no device properties patching for graphics, using WhateverGreen vanilla; AAPL,ig-platform-id is set as <07 00 9b 3e> that I think belongs to MacMini8,1 but it's not 0x3E9A0000 as my hardware Geekbench IGPU score for OpenCL is 23617 approx. Scenario 2) Clover configuration forcing device property AAPL,ig-platform-id to use either <04 00 a5 3e> 0x3EA50004 (MacBookPro) or 0x3EA50009; Geekbench IGPU score for OpenCL is 38550 approx. A slightly higher score (39352) is obtained when no AAPL,ig-platform-id is injected in Clover device properties (I get only device-id 0x3EA50000) and disabling WhateverGreen via -wegoff I am not sure if these are expected results? As for replacing FakePCIID.kext and the injection of HDMI Audio: My computer has no HDAU or B0D3 device natively. Perhaps this is the reason? Would making an SSDT that adds to GFX0 (renamed to IGPU via WhateverGreen) a device under it with name HDAU and ADDR 0x00 make the system find the sound-output for HDMI? Thank you!
  10. MacKonsti

    Intel Framebuffer patching using WhateverGreen

    Hi @headkaze good to see you active again! Can I please have your comment on my earlier post in this page? Could you understand why I would get a "RAW" power of +80% on Geekbench 4 without using WhateverGreen.kext (namely about 55110 as OpenCL Score) and the moment I include WhateverGreen.kext in /L/E/ on Mojave, the score falls to 38175 approximately? Besides the fix for Safari mentioned in the GitHub notes (embedded video playback) being probably missed, the only other thing I get during boot is a "pink flash" for a brief moment. But can't see why WhateverGreen would provide these Geekbench results -- unless it's a misleading number and not a true one? (kindly refer to my post for IDs etc) Thanks!
  11. Thank you mate, so you are using an independent setting for each option, not a combo thing like framebuffer-con0-alldata OK I see now. That is longer but definitely preferred (easier to debug later!) as we can't reverse-find the settings if you combine them in "alldata". Interesting that you only use <key>AAPL,ig-platform-id</key> and not device-id key as well? How come?
  12. Hi @tonyx86 thanks for your updates, I am following your thread more for your discoveries and less by the fact that I have (actually, not) the same PC. Can I kindly ask you to post a photo/screenshot of Hackintool while you select the different framebuffer options so that we can visualise your choices and learn from it? Would be really appreciated... everyone posts their ready-config for Clover (or OpenCore) but rarely someone posts screenshots during the making Trying to decipher your config.plist and settings by reverse-engineering e.g. <key>framebuffer-con0-alldata</key> or <key>framebuffer-con1-alldata</key> is an impossible task... Thanks, mate.
  13. MacKonsti

    Hackintool v3.x.x

    Hi @headkaze I hope you are well and safe. A small bug accidentally discovered, for your next release: The tooltip text for "Inject Fake IGPU" was probably accidentally copied from "USB Port Limit" code, in PATCH > Patch > Advanced section Many thanks again for your continuing devotion to Hackintosh! Cheers mate. P.S. A question to everyone: if someone enables LSPCON driver (and chipset supports it, of course) do we need still <key> enable-hdmi20 at all? Per definition, LSPCon (Level Shifter and Protocol Converter) driver for native HDMI v2.0 ports (on supported GPUs where HDMI v2.0 is routed to IGPU). I am a total n00b in Framebuffer patching and been studying the different keys added, first... Thanks
  14. Hi @MaLd0n how are you? You will not believe it... After searching for days, eventually I decided to find a way to reset the Keyboard Shortcuts. So according to the solution proposed in this article, I deleted file ~/Library/Preferences/com.apple.symbolichotkeys.plist and rebooted. Guess what... the F11/F12 keys worked with the Notify 0x0405 and 0x0406 values... I am banging my head on the wall ! So free lesson learned, that you can use: If problems with keyboard shortcuts = delete file ~/Library/Preferences/com.apple.symbolichotkeys.plist and reboot! Thank you for your patience and help all this time. I suspect the keyboard shortcuts were never created inside the .plist as I had booted without PNLF etc. originally, that was before using your DSDT... However, in System Preferences > Keyboard > Shortcuts, I still do NOT see "Brightness" anywhere but it works. Please, if you have time, kindly check my PM that regards the overall DSDT patching Obrigado! P.S. By the way, despite your solution to fix trackpad polling works great (as I saw over at Olarila) did you try this alternate solution proposed here, please? https://voodooi2c.github.io/#GPIO Pinning/GPIO Pinning I would be very interested to get your opinion!
  15. Hi everyone, I am trying to contact the developers of the excellent (thank you again) VoodooPS2Controller and VoodooPS2Keyboard found on acidanthera's GitHub: https://github.com/acidanthera/VoodooPS2 with my hack: Lenovo S145-14iWL a 14" laptop with (latest) Catalina Keyboard has F1-F12 keys only (no F13/F14) and is AZERTY layout Clover r5119 with kexts injected via /kext/Other/ only (no /L/E/ as I have no CSR enabled) Using VoodooPS2Controller and VoodooPS2Keyboard plugin, removed others as they don't support my "ELAN0629" HID. MacBook15,4 SMBIOS and I admit not having tested other MacBookPro15,x N.B. I do not get in System Preferences > Keyboard > Shortcuts : No reference in Brightness Control at all (not sure this is indicative?) After my exchange with @MaLd0n my system runs smooth but for the life of me, I cannot enable the F11/F12 keys via Fn that would allow Brightness Control. I have been trying with Rehabman's ioio Terminal tool find out the key-codes for PS2 and ADB, mapping each F1-F12 key with Fn pressed as well: ./ioio -s ApplePS2Keyboard LogScanCodes 1 I was planning to use this guide for PS2 Keyboard mapping, as I thought that the keys sent were wrong. To my surprise, F11/F12 send the normal expected codes but Fn+F11 and Fn+F12 send no codes at all. All other F1-F10 codes, match both PS2 and ADB codes as found in ApplePS2ToADBMap.h Also, I have run Rehabman's ACPIDebug.kext and confirmed that the code when pressing F11/F12 passes through _Q11 and _Q12 Methods of \_SB.PCI0.LPCB.EC0 so I did add the needed Notify (in edited DSDT) but still nothing happens. Tried some Notify (\_SB.PCI0.LPCB.PS2K, 0x????) values found around (like here or here) with the hope to produce some result... Nothing. Is this a kext problem or my hardware, you think? Is it related to MacBookPro15,4 that may impact this? Is this some action or ACPI event that talks directly to the panel and is totally transparent/ignored by macOS ? Can I get please your comment @syscl and @vit9696 as I can't find other developers' nickname, to help please? There is no specific thread URL in the GitHub README.md page of VoodooPS2 to address my issue... Many thanks, I appreciate your feedback. Update: With Notify (^^PS2K, 0x0405) and Notify (^^PS2K, 0x0406) I do get eventually a code when pressing Fn+F11 and Fn+12: F11= default 22:52:30.780256+0200 kernel ApplePS2Keyboard: sending key 57=67 down F12= default 22:52:32.356484+0200 kernel ApplePS2Keyboard: sending key 58=6f down Fn+F11= default 22:52:34.321340+0200 kernel ApplePS2Keyboard: sending key e005=6b down Fn+F12= default 22:52:36.048654+0200 kernel ApplePS2Keyboard: sending key e006=71 down Can you also kindly confirm that the method described here to do PS2 Keyboard Mapping via injection of a proper SSDT and proper Name (RMCF, Package() [...] without ever needing to edit/touch the VoodooPS2Keyboard's Info.plist does produce results? Is this method still valid? Is RMCF taken into consideration? I see that PS2 codes e005 and e006 found in ApplePS2ToADBMap.h map to: BRIGHTNESS_DOWN, // e0 05 dell down BRIGHTNESS_UP, // e0 06 dell up But 0x6b and 0x71 as ADB codes are referenced in: // These ADB codes are for F14/F15 (works in 10.12) #define BRIGHTNESS_DOWN 0x6b #define BRIGHTNESS_UP 0x71 0x6b, // 65 = F14 0x71, // 66 = F15 0x6b, // 46 Scroll Lock 0x71, // e0 4 5* Pause How is the value in Notify (^^PS2K, 0x0405) and Notify (^^PS2K, 0x0406) derived? How is the value 0x0405 ending up as e005=6b for example? What is the definitive value for BRIGHTNESS_DOWN and BRIGHTNESS_UP? Many thanks