Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/07/2020 in all areas

  1. https://www.techpowerup.com/263647/apple-finally-buying-amd-cpus-pointers-to-ryzens-found-in-macos-beta "Since its switch to the x86 machine architecture from PowerPC in the mid-2000s, Apple has been consistent with Intel as its sole supplier of CPUs for its Macbooks, iMac desktops, and Mac Pro workstations. The company's relationship with rival AMD has been limited to sourcing discrete GPUs. If pieces of code from a MacOS beta is anything to go buy, Apple could bite the AMD bullet very soon. References to several AMD processors were found in MacOS 10.15.4 Beta 1. These include the company's "Picasso," "Renoir," and "Van Gogh" APUs."
    3 points
  2. When it comes to dropping MA.EFI your completely wrong bud and 9 it of 10 times your going to need to pull the battery or short the pins to bring it too life. Anybody that does it without doing that and gets away with it will down the line get boot failures but nine out of ten times it just won’t boot at all. this is why I say to do it and I stick to my guns about it. To explain abit more to why without getting all technical about it, MA.EFI and free2000 unlock a section of memory that is reserved and not meant to be used and when you drop the driver again you leave a pile of mess in that reserved area of memory. F11 via clover or a NVRam reset via OC doesn’t clean out the reserved area of memory, there is only two ways to do that properly. 1 is to pull the battery from the mortherboard or 2 is to reflash the bios. Anything else doesn’t clean that area of memory out. I hope that clears up why I am so instant on the process and makes sense to everybody as to why it need to be done.
    3 points
  3. Thanks man Good to be back and you're most welcome. Thanks to you for reporting the new update.
    2 points
  4. Heeey!!!! Welcome back, Cyber! Many thanks for the test, man! Highly appreciated!
    2 points
  5. I confirm that there is no flashing on my end either.
    2 points
  6. Hello Everyone, I have made some progress on making some hotpatch SSDT of DSDT patch used on T460 tluck pack. As OpenCore NDK fork is maturing enough to be a alternative to Clover with GUI boot picker. If anyone interested to Experiment with OpenCore, I think this SSDT hotpatch approach will need to be perfected. So far I have equivalant DSDT patch to SSDTs are (See attachment for dsl source file) 1_led_blink.txt ==> SSDT-PTWK.dsl 1_system_PNOT.txt ==> This patch suppresses PNOT, PPNT, PNTF method call, if found are commonly called from EC/AC adapter related code and often access identifiers that are present in SSDTs generally dropped (CPU SSDTs). I only found one PNTF call on the DSDT and because we don't have to drop any cpu related SSDT, I think we are good to go without it. If anyone have trouble without this patch, it would be great to try to make a hotpatch or binary patch if needed. 2_IGBE_PRW.txt ==> this is achived with config binary patch. 2_system_H8DR.txt ==> SSDT-H8DR.dsl, I have made two alternative verstion of SSDT for this patch, though I am not sure if any one of it work. And this patch might not be required at all because on DSDT I found this code on \_SB._INI method. If ((\_REV >= 0x02)) { \H8DR = 0x01 } and DSDT disassambly Original Table Header: * Signature "DSDT" * Length 0x000127DF (75743) * Revision 0x02 // This says revision is 0x02 so H8DR might automatically be One on newer bios version 2_system_nvst.txt ==> This patch is about enabling lid sleep but I didn't face any problem without it. 3_Fn_Keys.txt ==> SSDT-KBD.dsl 4_battery_fan.txt ==> SSDT-BATT.dsl 5_syscl_PPMCnPMCR.txt ==> This also can be achived with SSDT. As of now for two days I am running my system with these SSDTs and with native unmodified DSDT without any recognizable functional and performace difference, but the acpi log shows tons of errors with these SSDTs. It would be great help if you guys could give a hand to track down these errors and solving them. This work is done by taking as a base and modifying jsassu20's T450s repo. Because these two machines are similar they share lots of things in common and jsassu20 did a fine job making T450 fully hotpatch base. Anyone want to experiment look at his repos for direction. https://github.com/jsassu20/Lenovo-ThinkPad-T450-macOS-Catalina https://github.com/jsassu20/Lenovo-T450-Catalina-OpenCore https://github.com/jsassu20/OpenCore-HotPatching-Guide Regards, Junaed SSDT-HOTPATCH.zip
    2 points
  7. Zenith your 100% correct my path was wrong i dropped my efi into the blank efi folder /Volumes/EFI/EFI/ instead of replacing the one on root of the NVME drive. LOL i guess old dogs can still wet the floors. thanks for your reply.
    2 points
  8. For now you mean. Wait for it!!!!!! clear out your nvram via clover or OC at the very least bud
    2 points
  9. we are working on a fix for all EFIs for the pro thread still and that’s why it’s not been updated yet. Plus I’m a little busy at the moment so bare with me dude and I will come up with a working solution soon. the Z390 Master board has a better bios and less problems with igpu enabled hence why it got updated first. and yes without the MA.EFI life becomes a lot more difficult to keep it stable all the time but what can I do? if you want to continue using the fix then go for it, I can’t say what will happen in the long term but I’m yet to find a genuine case of where free2000 or MA.EFI have caused any harm and I’m always longing to here a story about how it all went sideways because of it but alas this story does not exist because it’s never happened. Make of that what you will buddy.
    2 points
  10. I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop. I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac. Hardware Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings Chipset Intel 7 series, no patches needed Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1 Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0. SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties. USB3.0 works natively if not disabled in DSDT PS2 keyboard and touchpad works with VoodooPS2. WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353 LCD Screen 1366x768 BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions. For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state. WiFi It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver. I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover. As well a patch for channels. I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone. VideoCards In Bios we can set Optimus = Enable/Disable If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia. If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2. But here there is contradiction with WiFi with required Board-ID from MacBookAir. So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge. Set BoardID like iMac13,2 to make Nvidia working. Patch BoardID in Brcm4360 to make WiFi working. Now I have Inject-> ->Intel=YES ->Nvidia=YES and SSDT-3.aml in ACPI\patched folder. This SSDT will switch off Nvidia if Intel card ON. For Intel graphics there is a patch against 8 apples at start. This Nvidia 5200 is Fermi and works in ElCapitan. Brightness No special kexts. The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here #72 DSDT and SSDT This is very long story and finally I have working sleep in both cases Intel or Nvidia. Sensors I use my HWSensors3 with FakeSMC 3.5.2. I got monitoring: CPU temperature GPU temperature GPU main frequency GPU shader frequency Battery state % full, time to charged or time to empty. Battery voltage dinamically. Battery amperage dynamically. I can see it changes on heavy games. HDD temperature. Audio I like VoodooHDA and have no problems with it. The sound is clear, loud, and switchable between internal speaker and headphone. Mic is working. Bluetooth Just tested with BTFirmwareUpdate.kext and it works in 10.11.6. I not needed it so switched off by wireless switch at right side. For 10.13.6 there is other kext BRCMInjector. Keyboard, Touchpad and Touchstick Post #14 I made my fork of the VoodooPS2 driver, take here sources and release version https://github.com/SergeySlice/VoodooPS2-for-ALPS My config, ACPI files and kexts are in attachment. 05.12.2017 EFI.7z EDITED: Better DSDT in the post #6. Sleep working even when AC inserted. EDITED 06.12.2018 Now I have HighSierra and this is my EFI folder. Note, HighSierra is possible only with Intel graphics (Optimus is enabled in BIOS) Welcome to discussion! EFI-E6430.7z BRCMInjector.kext.zip Latest EFI for Mojave here
    1 point
  11. Hi Rocky12, Thanks for all the great help and support which has helped me considerably since El Capitan. I have a Z800 Bios 3.91 2*X5690 Quadro 4000 which I have just rebuilt as Mojave with a very simple setup based on guidance from Sierra. Have attached by Base EFI for anyone who has a Z800 3.91 Bios machine. This setup works but I wondered what would you recommend as the best combination of kexts for Mojave? Thanks. (Also have a Z820 2*E5-2670v2 Mojave using Lilo etc) EFI worked with 3.91.zip
    1 point
  12. It functions in both legacy and UEFI if your firmware supports NVMe drives (you can see the drive in your firmware boot selection). You can also boot in legacy by using another non-NVMe disk to boot clover and using the NVMe driver that comes from EDK2, then you can boot UEFI from the NVMe using clover legacy. How we get into APFS now? I was literally talking about one specific situation for a UEFI boot and everyone is talking about legacy booting like I don't know how it works, lol. I was just saying that the UEFI FAT driver should be able to recognize any variant of FAT, but that some only recognize FAT32 because that is what the ESP is supposed to be formatted. However, because it is so small, most of the time it is actually formatted FAT16 unless you specifically force that it is FAT32. This is a situation that can lead to unrecognized UEFI boot disk. This discussion about FAT turned into a discussion about legacy booting... lmao. The other UEFI problems, no drivers or incorrect paths... haha Yeah, they for sure work in both. You will usually have more trouble with macOS than the booter.... Weird, you should have still booted. Your firmware should have failed and tried the next boot option, unless it just went back to the boot selection menu and you were unsure why? I do way more stupid stuff on a daily basis.... The ESP is always supposed to be FAT32.
    1 point
  13. Thanks man, Yeah I'm ok and I was lurking in the shadows most of the times but wasn't posing much Everything is alright and thanks for asking
    1 point
  14. WOW! I just thought you today. are you ok or not? I didn't see you for a long time and I wonder everything is ok with you. It is good to hear your voice. Welcome back.
    1 point
  15. @arsradu I'm still on 10.14.6 hahaha but I'll update then, when it is out of beta
    1 point
  16. This seems relatively easy to achieve!Like my example, just add an install.icns icon file! switch (Type) { case OcBootWindows: if (StrStr (Name, L"10") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_win10.icns"; } else { FilePath = L"EFI\\OC\\Icons\\os_win.icns"; } break; case OcBootApple: if (Ext == TRUE) { FilePath = L"EFI\\OC\\Icons\\install.icns"; } else if (StrStr (Name, L"Cata") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_cata.icns"; } else if (StrStr (Name, L"Moja") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_moja.icns"; }else { FilePath = L"EFI\\OC\\Icons\\os_mac.icns"; } break; case OcBootAppleRecovery: FilePath = L"EFI\\OC\\Icons\\os_recovery.icns"; break; case OcBootCustom: if (StrStr (Name, L"Free") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_freebsd.icns"; } else if (StrStr (Name, L"Linux") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_linux.icns"; } else if (StrStr (Name, L"Redhat") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_redhat.icns"; } else if (StrStr (Name, L"Ubuntu") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_ubuntu.icns"; } else if (StrStr (Name, L"Fedora") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_fedora.icns"; } else if (StrStr (Name, L"Shell") != NULL) { FilePath = L"EFI\\OC\\Icons\\tool_shell.icns"; } else if (StrStr (Name, L"10") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_win10.icns"; } else { FilePath = L"EFI\\OC\\Icons\\os_custom.icns"; } break; case OcBootSystem: FilePath = L"EFI\\OC\\Icons\\func_resetnvram.icns"; break; case OcBootUnknown: FilePath = L"EFI\\OC\\Icons\\os_unknown.icns"; break; default: FilePath = L"EFI\\OC\\Icons\\os_unknown.icns"; break; }
    1 point
  17. You are not reading the changes on this fork thoroughly, you can use custom entry to override the name from system and can set it be hidden as well. I like to keep it as simple as possible. This GUI picker is only an extra, like bios menu to me, I hardly have to see it, since I can switch Oses using just the Hotkeys. It uses the system fonts, so not changeable.
    1 point
  18. If you're having trouble calculating the slide, one workaround is to copy the `AllocFix.efi` file to `EFI/CLOVER/drivers/UEFI`. You could probably set the `slide` to `0` in that case. It's not the ideal, but it might work until you figure it out the correct slide number. You'll find the `AllocFix.efi` file in the project folder: `DellXPS15-9550-OSX/10.15/CLOVER/drivers/UEFI/other`
    1 point
  19. I got my hand full with other stuffs, these are low priority. I am sure the whole GUI boot picker are wrapped up in that one single file pretty simple enough, if someone want to add something useful, feel free to post and I will not ignore suggestion.
    1 point
  20. It is normal for mis-configured system. Please, if you really need help, at least post your log and config.plist, so others can point you to the right direction, and update your system profile, so people know what system you have. Don't just post some random comment and expect other to help.
    1 point
  21. Yeah man! I think this is it. I think is for real. I could not be happier! This has bothered me since forever!!! And now it looks like it's finally fixed. What OS version are you currently on? You could try the Beta on a separate partition, if you want. But yeah... I cannot believe it! @unixb0y I think you might wanna give it a try, man. This is awesome.
    1 point
  22. How about add below code to the selection list inside OcSimpleBootMenu? You'd need to add one more icon named "os_installer.icns" to the icon folder. (Would this be best under "case OcBootApple:", or under "case OcBootCustom:" ?) (For my own use, I've added extra code in this same section to better distinguish OS on NVMe vs SATA drives as the SATA drives contain my backup copies; one just has to be careful in how one names the actual drives, like "CaBkUp" or "MoBkUp" in accordance with how the search is implemented.) } else if (StrStr (Name, L"Installer") != NULL) { FilePath = L"EFI\\OC\\Icons\\os_installer.icns";
    1 point
  23. 1 point
  24. @lostSoul86 - sorry about that, i will repackage with both kexts.
    1 point
  25. - Make full service for macOS kexts easily. - Latest Kext Utility v2.6.6 for mac OS 10.5-10.13 macOS "Sierra" Super Speed Edition FULL version with KU_config.plist © cVad 2008-2016 Improved version utility from russian MAC community. Description: Super speed repair permissions for all system folders: /System/Library/Extensions and /Library/Extensions; Starts a update (rebuild) system caches: NEW! Starts a update (rebuild) system kernelcache_* for OS X with Extensions.mkext standart cache file (OS X 10.6): Install multiple kext files simultaneously; Kext Utility.app/Contents/Resources/KU_config.plist for ON|OFF some KU functions; KU can automatically add/remove boot args: "-v" for verbose boot, "kext-dev-mode=1" for load unsigned kexts in MAC OS X "Yosemite" and "rootless=0" for perform any repair permissions operation in com.apple.Boot.plist and Unbelievable! in NVRam ; Patch msdosfs.kext Info.plist for add OSBundleRequired="Console". That provides access to an EFI partition in single user mode (disabled for 10.10 and up); Update a records about the unsigned installed kexts in the AppleKextExcludeList.kext (disabled for 10.10 and up); Pack kext files to mkext cache file; UnPack mkext cache files. Note: The latest KU uses highly modified high-speed method of repair kexts. To all kexts granted the same rights (a little more liberal, than it is necessary). This saves a lot of time and nervous when installing and configuring the MAC OS X. On the system performance, is not affected. After installing and configuring the system, if there is free time, run "Disk Utility", and repair the kexts, according to their native permissions. Default config: Troubleshooting: Some thoughts on the repairing of the kexts permissions: Enjoy ... Feel free to click "like" cvad Kext_Utility.app.v2.6.4.zip Kext_Utility.app.v2.6.4.zip.md5.txt Kext_Utility.app.v2.6.5.zip Kext_Utility.app.v2.6.5.zip.md5.txt Kext_Utility.app.v2.6.6.zip Kext_Utility.app.v2.6.6.zip.md5.txt
    1 point
×
×
  • Create New...