Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/11/2019 in all areas

  1. All ok now with all! All working! All perfect! all with "only" my "little" 5,1ghz i5 9600k on Catalina 19A526h b5 i7/i9 not needed ...I'm photographer and video maker not really need it...only ram and m.2
    2 points
  2. GLASGOOD'S MOJAVE HACKINTOSH GUIDE For latest EFI for macOS Catalina and discussions, visit @AudioGod's ==> Aorus Pro Z390 Patched DSDT mini guide GIGABYTE AORUS PRO Z390 CREDITS & THANKS @MaLd0n His help with EFI configuration and DSDT CLOVER TEAM Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, rehabman, Download-Fritz, Zenit432, cecekpawon Et al APPLEALC Acidanthera, vit9696 VOODOOHDA autumnrain, slice2009, zenith432 ESP PRO MOUNTER @Micky1979 HACKINTOOL @headkaze CLOVER CONFIGURATOR Mackie100 THEME ENGINE Alex Zielenski INSANELYMAC OLARILA Hackintool Tutorial daliansky Hackintosh Vanilla Desktop Guide /r/Hackintosh - corpnewt MONITORCONTROL JoniVR & theOneyouseek ------------------------------------------------------------------------------------------------------------------------------------------------------------ UPDATES ------------------------------------------------------------------------------------------------------------------------------------------------------------ PART LIST • Intel I7 8700 • Gigabyte Z390 AORUS PRO • Gigabyte AORUS RADEON RX 580 8GB ( connected to monitor with DisplayPort ) • Corsair Vengeance LPX 16GB ( 2 x 8GB ) 2666MHz – CMK16GX4M2A2666C16 In this build, both memory modules are installed in memory slots DDR4_A1 and DDR4_B1 • Corsair RM650x 80 Plus Gold Power Supply Unit • Corsair H100i V2 AIO Hydro/Water RGB LED CPU Cooler • Samsung EVO 500GB SSD (2.5) macOS Mojave • Samsung EVO 250 GB SSD (2.5) Windows 10 Pro • NZXT H500 Mid Tower ATX Case • 1st RECOMMENDED WIFI CARD → ABWB BCM943602CS 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) OR • 2nd RECOMMENDED WIFI CARD → WIFI and Bluetooth with BCM94331CD with PCI-e adapter (but will require AirportBrcmFixup.kext for AirDrop.. ) WORKING • Sound • Ethernet Port • WiFi • SSD Trim • USB 3.0 & 2.0 • AirDrop • iCloud • Hardware Acceleration AMD RX 580 / AMD Vega • iMessages • Facetime • Handoff • Netflix on Safari browser • Continuity PREAMBLE - BEFORE YOU START Here detailed, is all the steps towards building a successful and stable Aorus Pro Z390 Hackintosh, if you are a first time Hackintosher, this guide will have you quickly up and running with the Aorus Pro Z390 Hackintosh. To rule out potential problems from the go, only have the disc that you plan to install macOS Mojave connected to the Aorus Pro, disconnect any other Windows / Linux or data drives, external drives from your Aorus Pro. Windows / Linux and data drives can be connected after successful installation of macOS Mojave If you have more than 16 GB of memory, then install macOS Mojave with just 16GB or RAM installed, you can later add any additional memory. Install memory modules in slots DDR4_A1 and DDR4_B1. This build has a recommended Wi-Fi combo PCI-e card installed in slot PCIEX1_3 with its 9 pin USB cable attached to motherboard header F_USB2. ( ensure WiFi card is seated properly in PCIe slot and cable is firmly attached to WiFi card and motherboard header F_USB2 ) If using the Corsair H100i v2 AIO cooler with USB cable connected to motherboard header F_USB1, you will need to enable hot-patch ( explained in guide ) in config.plist for working sleep, wake from sleep will only work by pressing Power Button. Install macOS Mojave on its own physical drive, so do not try and install macOS Mojave onto a free partition on a disc that contains Windows. Remove any Thunderbolt cards, Thunderbolt card can be reinserted after installation. Double check your BIOS settings are the same as this guide. Following are unsupported / problematic • Intel Optane ( if you have this, remove it before installation of macOS Mojave ) • Samsung EVO Plus drives ( ensure you update Plus drive to latest firmware to avoid problems ) • XFX Radeon RX 580 • NVIDIA GTX / RTX not supported in macOS Mojave Q - WILL THIS GUIDE WORK WITH MY NON AORUS Z390 PRO MOTHERBOARD ? A - Possibly, though you may have to create your own USBPorts fix. Q - I notice you have the Aorus Pro Z390 version, will this guide work with Aorus Pro Z390 WiFi version ? A - Possibly, but onboard Intel / Intel CNVi WIFII /Bluetooth will not work with macOS and you will have to disable HS14 for Bluetooth to function properly. Q - Can I use my AMD Vega Card ? A - Yes, AMD Vega card's will work with this guide, but If you plan to use a Sapphire Pulse Vega 56 then please read @AudioGod ==>post regarding the Sapphire Pulse 56. PART 1 - DOWNLOAD • Update BIOS to version F10 • CLOVER • Aorus Pro Z390 EFI.zip • Aorus PRo Z390 EFI - THE OC VERSION.zip <== OC VERSION • ESP MOUNTER PRO v1.9 • macOS MOJAVE • CLOVER CONFIGURATOR • Hackintool OPTIONAL DOWNLOADS • Native Display Brightness with MonitorControl • ThemeEngine • Assets.car // Not really needed but IF no sound on Wake from Sleep then use SSDT-ALC1220 and CodecCommander • ( Resolves Audio Sound on Wake, place in Clover / ACPI / Patched ) • ( Resolves Audio Sound on Wake, place in Clover / Kexts / Other ) PART 2 - BIOS SETTINGS (Version F10 ) Here is a list of the BIOS settings that I use ( Screenshots in spoiler below ) • Enter BIOS → Press F12 → Enter Setup • Save & Exit → Load Optimized Defaults • BIOS → Windows 8/10 Features → Other OS • BIOS → CSM Support → Enabled ( Optionally, can be enabled after macOS is installed, your choice ) • Peripherals → Initial Display Output → PCIe 1 Slot • Peripherals → Trusted Computing → Security Device Support → Disable • Peripherals → Intel(R)Bios Guard → Intel BIOS Guard Support → Disable • Peripherals → USB Configuration → Legacy USB Support → Enabled • Peripherals → USB Configuration → XHCI Hand-off → Enabled • Peripherals → Network Stack Configuration → Network Stack → Disabled • Peripherals → SATA And RST Configuration → SATA Mode Selection → AHCI • Chipset → Vt-d → Enabled ( can be enabled or disabled, your choice!) • Chipset → Internal Graphics → Disabled • Chipset → Audio Controller → Enabled • Chipset → Above 4G Decoding → Disabled • Power → Platform Power Management → Disabled ( Optionally, can be enabled after macOS is installed ) • Power → CEC 2019 Ready → Disabled • Power → ErP → Disabled (can be enabled or disabled, your choice !) • Power → RC6 (Render Standby) → Disabled • MIT → Advanced Memory Settings → Extreme Memory Profile (X.M.P) → Disabled ( Optionally, can be enabled after macOS is installed, your choice ) // IF USING CORSAIR H100i V2 AIO CPU WATER COOLER • MIT → Smart Fan 5 Settings → CPU Fan Control mode → PWM • Save & Exit → Save & Exit Setup SCREEN DUMP SPOILERS PART 3 – CREATE A MOJAVE USB FLASH INSTALLER Prepare USB Installer for Mojave ( Video below ) • Insert USB drive • Launch /Applications/Utilities/Disk Utility • Disk Utility → View → Show All Devices • On Left-hand panel → External →(Identify your USB device in left hand panel) • Click and highlight your USB device in the left-hand panel. • Click erase button. • Name: USB • Format: Mac OS Extended (Journaled ) • Scheme: GUID Partition Map • Click Erase button. • Place the downloaded MacOS Mojave app into Applications folder. • Open Terminal copy and paste: sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --nointeraction && say Mojave Drive Created • Enter PART 4 – INSTALL CLOVER ON THE MOJAVE USB INSTALLER Make Mojave USB flash drive installer bootable.( Video below ) • Launch Clover application, double click. • Click Continue → Continue → Continue • Click Change Install Location button. • Click Install macOSMojave USB installer → Continue • Click Customise button • Choose: Clover for UEFI booting only Install Clover in the ESP Themes UEFI Drivers • Click Install button • Installation Complete! Video: PART 5 – CUSTOMIZE MOJAVE USB INSTALLER FOR AORUS Z390 PRO Replace Clover EFI folder with PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip Aorus Pro Z390 EFI.zip ( Video below ) • Install ESP Mounter Pro v1.9 • Using ESP Mounter Pro, Mount ESP on disk2s1 ( Your disk name may be different ) • Open mounted EFI partition found on desktop • Copy all the contents from Aorus 390 Pro EFI folder • Replace USB EFI folder with all the contents inside the Aorus 390 Pro EFI folder. PART 6 – INSTALL MAC OS MOJAVE ON INTERNAL DRIVE INSTALL NOTE ENSURE BIOS: Above 4G Decoding is set to Disabled if Above 4G decoding is set to enabled then macOS Mojave install will freeze at 2 mins remaining and will not shut down properly!!!! Please be patient during install, so when install gets to 2 or 3 mins remaining then it may take extra time. Be ready to boot from UEFI USB installer by pressing F12 when install initiates restarts. • INSERT USB INSTALLER INTO THE USB 2.0 PORT Here is a walkthrough of the full process using the macOS Mojave USB Installer on the Aorus Z390 Pro. • Power on PC and press F12• Choose bootable USB drive from boot menu. • Install macOS Mojave to internal solid state or hard drive. When system returns to the Clover boot menu choose: • Boot macOS Install from Macintosh At next restart, press F12 and boot from external UEFI USB device and choose: • Boot macOS Install from Macintosh Proceed with macOS Mojave install macOS Mojave is now installed, but it can only boot at this moment thanks to FakeSMC and Clover on the Mojave USB flash drive installer. PART 7 – MAKE AORUS Z390 PRO INTERNAL DRIVE BOOTABLE Make internal drive bootable ( Video below ) So far, the Aorus Pro can only boot the internal system drive with the aid of the Mojave USB Installer. To boot from the internal system drive without the installer: Download and install Clover with RC Scripts on target volume. Copy the EFI folder from inside Aorus Pro Z390 EFI.zip folder and paste it inside the the System Drive EFI partition. • Remove USB Mojave installer and shut down and restart. Aorus Hackintosh should now be able to boot to macOS Mojave, Done, well almost ! PART 8 – ENABLE IMESSAGES & FACETIME // UPDATE 21st MAY 2019 Possibly Clover Configurator now automatically populates correct values for working iMessages when you select an SMBIOS. After selecting SMBIOS, example iMac19,1 for Aorus Pro with RX580 ( image above ) then go to Apple and ensure you have the "serial number is not valid " message. Done! If you still have problems connecting to iMessage, test and ensure that AirDrop is working, then follow instructions inside spoiler. PART 9 – ENABLE TRIM for Solid State Flash Drives Open Terminal and enter the following command: sudo trimforce enable PART 10 – FRAMEBUFFERS FOR RADEON AMD RX580, VEGA CARD's DEFAULT USB FIX – USB PORTS CONFIGURATION If you have USBC on Computer Chassis / Case, then SS01 and SS02 is mapped to that USB C port ------------ GUIDE FINISHED YOU SHOULD NOW HAVE WORKING AORUS Z390 PRO HACKINTOSH WITH SSDT USB FIX ------------ OPTIONAL: Set Wi-Fi Country Code OPTIONAL: System Information - PCI External USB Storage: Fix "disk did not eject properly" message upon wake from sleep OPTIONAL: Native Display Brightness - with MonitorControl OPTIONAL: Dual Boot macOS Mojave & Windows 10 OPTIONAL: Replace the default "About This Mac" Apple Logo with RED AORUS APPLE OPTIONAL USB PORTS FIX – Create your own SSDT or USBPorts.kext FRAMEBUFFER PATCHING – For working Intel UHD 630 Graphics, working HDMI Port, working HDMI Audio on Aorus Z390 Pro NOT REQUIRED AS GUIDE IS USING SMBIOS FOR IMAC PRO 1,1 FINAL CUT PRO – Configuration for AMD RX5xx NOT REQUIRED AS GUIDE IS USING SMBIOS FOR IMAC PRO 1,1 AORUS PRO Z390 WIFI version with Intel CNVi – Disable Bluetooth on HS14 Resolve bluetooth issue reported by @eSaF CLOVER – Updating / Upgrade Clover boot loader (If hack is stable, don't update unless you have problems) SLEEP – Sleep and Automatic Sleep SLEEP – Resolving Instant Wake ( Corsair H100i v2 AIO ) WIFI – Clover Hotpatch PXSX to ARPT RECOMMENDED READING – Excellent Hackintosh Vanilla guide created by CorpNewt with in depth tutorial on Clover. https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake EFI NON DSDT SMBIOS iMac Pro 1,1 Clover v2.5k r5018 Aorus Pro Z390 EFI - RX580.zip OR Aorus Pro Z390 EFI - Vega-56.zip EFI FOR SMBIOS iMac 19,1 for use with GPU & IGPU enabled in BIOS PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip POST-INSTALL Aorus Pro Z390 EFI - RX580.zip ( Has OsxAptioFix2Drv-free2000.efi ==> recommended reading before use ) EFI FOR INTEL UHD 630 SMBIOS iMAC 18,1 Aorus Pro Z390 EFI - Intel UHD630.zip( Has OsxAptioFix2Drv-free2000.efi ==> recommended reading before use )
    1 point
  3. Version 2.0

    29,949 downloads

    Please read me: Ever since macOS Mojave came out (I mean the first DP) Apple removed the support for Atheros based WiFi Adapters from the IO80211Family.kext, so to fix it we need to add the AirPortAtheros40.kext to the Extensions manually. After each clean install the AirPortAtheros40.kext needs to be installed and after clean installing Mojave DPs after few times I decides to create this app to save some time. How to use it: This application will install the missing AirPortAtheros40.kext into /System/Library/Extensions and after the installation is done and once you reboot your computer the Atheros based WiFi adapters will be enabled. The installation is the first step of the process and it is fast but the next steps which are repairing the permission on /System/Library/Extensions and rebuilding the system caches might take a while so please wait until you were asked to reboot your computer. I'm using a TP-Link WDN4800 with an Atheros chipset and it works on other similar hardware. If this app helped you please consider donating; any amount is appreciated.
    1 point
  4. Hi, this Topic is dedicated to translate the HWMonitorSMC2.app included in the HWSensor-3 project by Slice. Please don't post bugs or anything else is not related to translations, instead use the dedicated thread here. Here the files to be translated to fully make appear everything in you language: en.zip (to be used as base for new translations) de.zip fi.zip it.zip ko.zip pt-BR.zip pt-PT.zip ru.zip tr.zip zh-Hans.zip Info.strings translate the popover that appear when you right click in any sensor: actually contains only one line to translate the button "copy to clip board": Localizable.strings translate name of sensors, title of the groups and the units of measurement: Preferences.strings translate the Preference window: License.strings translate the License window ("License", "Accept", "Close" HOW TO: "Frequency" = "Frequency"; left part is the base string and you always must to translate the strings at right only: "Frequency" = "Frequenza"; (string at left is used to match the string used in the source code and if you change it ... english will be displayed, no matter what) Pay attention to quotes " and each line must be terminated using ; WARNING: Since I use Xcode to develop the application, .strings files already open with it. Please avoid to use funcy methods to open those files since invisible characters may be placed and you will ask why your translated strings will not show up. You can use Text Edit.app but please avoid to use it in RTF format but instead use it with "plain text" format only. Credits Italian and English by @vector sigma Russian by @Andrey1970 Simplified Chinese by @jinbingmao Turkish by @nomadturk Finnish by @Amble Korean by @Sherlocks German by @Mork vom Ork
    1 point
  5. this how to add in the PCI devices you can add in what you need
    1 point
  6. @vit9696 Thanks for all the suggestions and help into the issues we discussed. You were correct !, For now TgtBridge function may not be needed as thanks to @ben9923 solution after analysing my DSDT, we dropped the old way of patching the TPD0 device with a better and simpler solution thanks to the template/idea of your SSDT-AWAC.dsl on ACPI Samples. Previously i had to patch TPD0 _CRS to XCRS and TPD0 _DSM to XDSM and add the patched code into a SSDT which we required the TgtBridge to specify which "device" CRS and DSM method to rename. Now we removed all Renames needed for Touchpad from config.plist and simply use this SSDT based on your SSDT-AWAC.dsl template: // Touchpad fix for Lenovo V330-15IKB DefinitionBlock ("", "SSDT", 2, "V330", "_TPD0", 0) { External (SDM0, IntObj) Scope (_SB) { Method (_INI, 0, NotSerialized) // _INI: Initialize { If (_OSI ("Darwin")) { SDM0 = Zero } } } } And TouchPad now works like charm. About the InfoPlistPatch to disable AppleI2C kext from loading, i first solved the problem by blocking the kext from loading with OpenCore config.plist/Kernel/Block and by listing com.apple.driver.AppleIntelLpssI2C However after @ben9923 told that he found the solution to load VoodooI2C without disabling the AppleIntelI2C kext with your help by just adding: <key>OSBundleRequired</key> <string>Root</string> Into VoodooI2C.kext, Plugins and Satellite kexts, VoodooI2C kexts work excellent on OpenCore. Thanks a lot to all of you. Now my Lenovo V330-15IKB works perfect. Laptops should not be a problem anymore and can use Open Core as default Bootloader. I will soon start working on the project i mentioned on the Sep. Release schedule on Bugtracker which i think should make it easier for everyone else to have laptop templates for each generation. Sincerely, Sniki
    1 point
  7. Chris, may i draw your attention to the following disclaimer from the OpenCore git page WARNING: This release is a developer preview, i.e. it targets experienced engineers and developers. Configuration and feature set are under works, i.e. refinements are expected to happen .....
    1 point
  8. I maybe have misunderstood your point, but, hackintosh is not a brand, just a choice anyone make for its own purpose hence the unavoidable need to understand what they are doing, its something you take on yourself first, then using places like insanelymac you can find help to solve issues, but the base is you have to learn first Sure Clover simplified the installation providing an installer.... but if you then have to modify your config or any other file you will mount your EFI and make the changes... its only a bootloader nothing similar to what dosdude1 did So i can't really see what would make this one so uncomfortable to set up. then again I maybe have misunderstood your point... The real problem in my opinion is that there are also many people now too *miseducated to be able to give real contribution, quoting what you said " people want things to be easier and faster", well people must understand also that sometimes things are different and require a different spirit. PS *miseducated = people who just want to find the supper ready, and can't even make a sandwich by themselves
    1 point
  9. 1 point
  10. I must’ve been asleep. You are quite right. Capslock doesn’t freeze keyboard but doesn’t affect the case of letter typed Still I can’t remember the last time I used Capslock
    1 point
  11. Is this a notebook? If yes you have to rename it in order to not brake battery statistics. If it is desktop you must disable it an add new EC device.
    1 point
  12. @matgeoMaybe ssdt does not load did you add it on the config/ACPI? remove this from your ssdt External (_SB_.PCI0.LPCB.ECDV, DeviceObj) // (from opcode) Scope (\_SB.PCI0.LPCB.ECDV) { Method (_STA, 0, NotSerialized) // _STA: Status { If (_OSI ("Darwin")) { Return (Zero) } Else { Return (0x0F) } } } Because in laptop you lose battery
    1 point
  13. Version 3.0 very good grazie
    1 point
  14. I can confirm that fully working AMD kernel patches are not anymore since Aptiomemoryfix is embedded in OC - stuck at End randomseed. What am I missing? EDIT : FIXED WITH NEW DOCUMENTATION. Below still valid. Also, the first patch [0]: <dict> <key>Comment</key> <string>algrey - commpage_populate -remove rdmsr</string> <key>Count</key> <integer>0</integer> <key>Enabled</key> <true/> <key>Find</key> <data> uaABAAAPMg== </data> <key>Identifier</key> <string>kernel</string> <key>Limit</key> <integer>0</integer> <key>Mask</key> <data> </data> <key>MatchKernel</key> <string></string> <key>Replace</key> <data> Dx+AAAAAAA== </data> <key>ReplaceMask</key> <data> </data> <key>Skip</key> <integer>0</integer> </dict> this patch which is universal across any XNU version (10.13.6 and above) is replaced 15 times, but if you open the kernel in a decompiler your clearly see that B9A00100000F32 is found once. So I don't know what is patched 15 times to be honest. @vit9696 maybe you could help me with that ? 21:208 00:064 OCC: Configuring behaviour 0 21:462 00:254 Trying XNU hook on System\Library\PrelinkedKernels\prelinkedkernel 21:627 00:165 Kext reservation size 7860224 22:522 00:895 Result of XNU hook on System\Library\PrelinkedKernels\prelinkedkernel is Success 22:590 00:067 OC: Read kernel version 18.2.0 22:761 00:171 ReplaceCount - 15 22:793 00:031 OC: Kernel patcher result 0 for kernel - Success 22:965 00:172 ReplaceCount - 1 22:998 00:032 OC: Kernel patcher result 1 for kernel - Success 23:175 00:177 ReplaceCount - 1 23:206 00:031 OC: Kernel patcher result 2 for kernel - Success 23:380 00:173 ReplaceCount - 1 23:409 00:029 OC: Kernel patcher result 3 for kernel - Success 23:579 00:169 ReplaceCount - 1 23:609 00:030 OC: Kernel patcher result 4 for kernel - Success 23:778 00:169 ReplaceCount - 1 23:809 00:031 OC: Kernel patcher result 5 for kernel - Success 23:982 00:172 ReplaceCount - 1 24:015 00:032 OC: Kernel patcher result 6 for kernel - Success 24:186 00:171 ReplaceCount - 1 24:217 00:031 OC: Kernel patcher result 7 for kernel - Success 24:451 00:233 ReplaceCount - 1 24:481 00:030 OC: Kernel patcher result 8 for kernel - Success 24:653 00:172 ReplaceCount - 2 24:684 00:031 OC: Kernel patcher result 9 for kernel - Success 24:857 00:173 ReplaceCount - 1 24:889 00:031 OC: Kernel patcher result 10 for kernel - Success 25:063 00:173 ReplaceCount - 1 25:093 00:030 OC: Kernel patcher result 11 for kernel - Success 25:131 00:038 ReplaceCount - 3 25:164 00:033 OC: Kernel patcher result 12 for kernel - Success 25:339 00:174 ReplaceCount - 1 25:372 00:033 OC: Kernel patcher result 13 for kernel - Success 25:546 00:173 ReplaceCount - 1 25:576 00:030 OC: Kernel patcher result 14 for kernel - Success 25:748 00:172 ReplaceCount - 1 25:781 00:033 OC: Kernel patcher result 15 for kernel - Success 25:964 00:183 ReplaceCount - 1 26:005 00:041 OC: Kernel patcher result 16 for kernel - Success 26:065 00:059 ReplaceCount - 1 26:097 00:032 Patch success com.apple.iokit.IOUSBHostFamily 26:139 00:042 ReplaceCount - 1 26:173 00:033 Patch success com.apple.driver.usb.AppleUSBXHCI 26:228 00:055 OC: Prelink injection Lilu.kext - Success 26:278 00:050 OC: Prelink injection FakeSMC.kext - Success 26:323 00:045 OC: Prelink injection WhateverGreen.kext - Success 26:367 00:044 OC: Prelink injection AppleALC.kext - Success 26:404 00:037 OC: Prelink injection NullCPUPowerManagement.kext - Success 26:451 00:046 OC: Prelink injection RealtekRTL8111.kext - Success 26:514 00:062 Prelinked status - Success
    1 point
  15. set like so then a log will be place on the ESP along side of the efi folder any idea how to remove as i see it just before the picker
    1 point
  16. After cleaning up my folders, I couldn’t get BT working so I tried BrcmBluetoothInjector (in S/L/E) and it's working fine now.
    1 point
  17. AptioFix repo is no longer available since is include in OC. The only possibility is to add directly the file to Clover (before it make PKG). I do that and it works in Build_Clover.command script.
    1 point
  18. no, I use BrcmFirmwareRepo.kext. Follow the README, choose one of BrcmFirmwareRepo and BrcmFirmwareData, right? Update: I'm confused now, I try to use BrcmFirmwareData.kext in E/C/K/O and BT works! I try to cold start twice and it still woks! Amazing! I tried BrcmFirmwareRepo many days ago, but the difference is kexts put in different dictionary. I follow the README to put kext in correct dictionary or only use BrcmBluetoothInjector without other kexts, BT didn't work or be not stable. Anyway, I put BrcmFirmwareData, BrcmBluetoothInjector and BrcmPatchRAM2 the three kexts in E/C/K/O and BT works now. It looks like that I can't believe the README.
    1 point
  19. as an example https://github.com/acidanthera/AptioFixPkg#verifymsre2 But for accessing variables, I use RU.efi http://ruexe.blogspot.com PS. in pdf showed how to do it.iDisplay Audio Disconnect.zip
    1 point
  20. here you go BrcmBluetoothInjector.kext.zip
    1 point
  21. KGP, Pavo, and all experiencing "missing" cores. Check smcread -s, you will find the temperature for all your cores properly listed. See the key names here: https://github.com/acidanthera/VirtualSMC/blob/master/Docs/SMCKeys.txt#L847 If it is not the case, well, I can explore it with you, but this is unlikely. Tt was well tested, and VSMC supports up to 36 cores (Apple max, due to alphabet limitations). Relevant FAQ entries explaining why some software is broken (nobody reads docs, I get it): https://github.com/acidanthera/VirtualSMC/blob/master/Docs/FAQ.md#why-does-sensor-x-not-show-the-information-in-y https://github.com/acidanthera/VirtualSMC/blob/master/Docs/SensorInfo.md#recommendations In short, iStat Menus provides a custom profile (FauxMac) when it detects FakeSMC, which creates and uses SMC keys not existent on a real mac: https://github.com/acidanthera/VirtualSMC/blob/master/Docs/iStat.txt#L1953 This is not the case for VirtualSMC, and VirtualSMC will not invent its own keys but only use the ones found on a real mac. iStat Menus thinks that a hack running vsmc is a real mac, and for this reason the corresponding profiles of each mac model are used (each profile is listed in the document above). Different mac models have different sensor list and different limitations (e.g. core count). That means, iStat Menus will not *try* to read more SMC keys than it expects to find in a corresponding mac model. This behaviour is nothing but a bug of iStat Menus, as even on a real mac the CPU can be upgraded with more cores, and depending on the firmware/software more keys could appear (especially on T2). One could also use VirtualSMC to provide more keys on a real mac. If you find it uncomfortable, you should consider writing your own monitoring software or bugreporting iStat Menus author suggesting to: — remove the "count" limitations — allow custom sensor profile creation This is the most reasonable decision. Also, while it may surprise you, but the values CPUSensors report are actually wrong on systems with multiple CPUs, and I strongly doubt the core values are correct everywhere as well (due to wrong topology/ht analysis) Hope it helps and answers all the questions. Really, docs are your friend, it is no fun to write things twice.
    1 point
×
×
  • Create New...