Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/01/2021 in Posts

  1. As always, it is highly recommended to read @vit9696 message. It is the best place to find out what is new and changed in the new version of OpenCore. This step from 0.6.8 to 0.6.9 brings quite a few changes and some of them are very important but they are not as many as in the step from 0.6.7 to 0.6.8. Some of the things that have been improved: AppleEvents and some of its keys compatibility with older systems OpenCanopy and the picker presentation OpenCore password decryption speed, especially on slow systems memory devices on MacPro7,1 SMBIOS.
    12 points
  2. I don't understand why you want to hide warnings. Why would you want to keep problems in your config.plist ??? It's not a lot of work to clean. It's usually because of unknown keys, like "Ignore" in custom entries that never existed that I saw a lot. I called them warnings because Clover will "correct" and "ignore" this problems, but it is still problems. Just take 5 minutes and correct, and you won't need an ignore option. The day you'll immediately realise that your config plist modification doesn't work because of a misspelling, you'll be happy to get warning at C
    11 points
  3. Over the past few days, I've been working on ECEnabler, with u/midi1996's help with testing. ECEnabler is a Lilu plugin which allows macOS to read any size of EC field, meaning that no more ACPI patches are needed to split EC fields up within ACPI. I got tired of trying to make a complicated automated ACPI battery patcher (like SSDTTime), especially when dealing with all different vendors. I eventually had the idea to try patching macOS instead, which turns out to be much easier. Hopefully this saves you guys a little time with not having to go through Rehabman's patching guide L
    9 points
  4. New theme MacSteel available on Github 5 background included Background-1080p.png Background-1366x768.png Background-1024x768.png Background-2560x1440.png Background-1600x900.png Included MacOS Icons from Tiger to macOS Big Sur
    7 points
  5. just updated Z97 & Z490 Hacks to Version 11.4 Beta (20F5055c)
    7 points
  6. You would prefer kernel panics and black screens? Sent from my iPhone using Tapatalk
    7 points
  7. What I'd like to understand is why it is nice to turn it off instead of fixing your config.plist.
    7 points
  8. Update made, all is well...
    6 points
  9. OpenCore 0.6.9 EFI Update (Big Sur 11.4 Ready), 3rd May 2021 (Use With Bios Revision F12K or Newer) The EFIs and DSDTs have now been updated to the my latest versions. Changes made include, Lilu 1.5.3, AppleALC 1.6.0, IntelMausi 1.0.6, VirtualSMC 1.2.3, OpenCore Updated to Revision 0.6.9 (Big Sur 11.4 Ready), OpenCanopy is Enabled as Standard, New OpenCanopy Icons, Mouse now working in OpenCanopy, Plus other minor tweaks and changes to all of the configs, OpenCore EFI Update v0.6.9 - 03/05/202
    6 points
  10. I just wanted to let you know that I updated the prebuilt binary in the download section to version 2.4.2. Have fun! Mieze
    5 points
  11. Hi, guys did it another boring update no issue everything is on the right place
    5 points
  12. The Fast and the Furious. I'm beginning to lose track of all the updates.
    5 points
  13. Slice

    Clover General discussion

    I corrected somehow the Validator and upload it to Releases https://github.com/CloverHackyColor/CloverBootloader/releases/download/5134/CloverConfigPlistValidator.zip iMac2017:Debug sergey$ ./CloverConfigPlistValidator /Users/sergey/Desktop/config.plist Your plist looks so wonderful. Well done! iMac2017:Debug sergey$ It is in other place
    5 points
  14. TheBloke

    OpenCore Discussion

    The reason to apply the _DSM -> XDSM patch is because you have already added SSDTs that are trying to add _DSM sections, and they are conflicting with a _DSM in the same Device(s) in your system DSDT. So yes, there would be an SSDT adding a _DSM for each specific _DSM ACPI patch, but not a new SSDT - the one you were already adding. And if you don't have any SSDTs that include a _DSM and are resulting in an AE_ALREADY_EXISTS error, there's no reason to rename _DSM. Before ACPI -> Base was added to OpenCore, we used to have to rename _DSM to XDSM globally, affecti
    4 points
  15. I’m far from it bud, I’m like a journalist, I know a little about everything and and a whole lot about nothing. I should of been a physicist… LOL
    4 points
  16. it's time to update. All right
    4 points
  17. Another easy smooth update!
    4 points
  18. Another easy update.....I almost think I'm getting spoiled....they all should be like this.....
    4 points
  19. 4 points
  20. SavageAUS

    OpenCore Discussion

    Just wanted to hop in and say great work. I have not used OpenCore for a while now but I jumped back last night, updated my old OC EFI, kexts and AMD patches and voila back in business. Running Big Sur 11.4, OC 6.9.0. Was running Clover on the same system but the newest update ended in black screen. I’m yet to test sleep and shutdown but everything else is working as it should. Sent from my iPhone using Tapatalk
    4 points
  21. pkdesign

    OpenCanopy Icons

    Updated my Hex Icons set to be 0.6.8+ compatible: https://github.com/pkdesign/OpenCanopyIcons
    4 points
  22. Update made, all is well...
    4 points
  23. TheBloke

    OpenCore Discussion

    Ideally, yes, for neatness and peace of mind. Your system booted fine before and it's very likely there was no problem caused by the global rename. But now the ability exists to target it, it's cleanest to do so.
    3 points
  24. A new theme very nice add to Github Black-Blue 5 background included Background1024x768.pngBackground1080p.pngBackground1366x768.pngBackground1600x900.pngBackground2560x1440.png You can find my theme Clover on my signature is also linked to Google Drive
    3 points
  25. chris1111

    Clover General discussion

    Build CloverConfigPlistValidator xcodebuild -project $HOME/src/CloverBootloader/Xcode/CloverConfigPlistValidator/CloverConfigPlistValidator.xcodeproj -alltargets -configuration Release Open $HOME/src/CloverBootloader/Xcode/CloverConfigPlistValidator/build/Release
    3 points
  26. LAbyOne

    Clover General discussion

    yes, but before that i've a stupid question to ask.. about the buildme 1) this is how just integrates CloverConfigPlistValidator (8) 2) or would be better have a Clover Utilities menu (15) ( I added the newparser here just to give the idea...) for future additions? what do you think?
    3 points
  27. Strange! Because I fixed a panic, not a crash. And I had the message when I tried with your DSDT... I've added the panic in the log (it was only screen before) so I can have it. Before, there was an array of devices that has 16 slots even if less than 16 was needed. Empty slots were just initialised to 0. Accessing an empty slots was valid. Now, I store only the valid one. Empty slots doesn't exists, therefore trying to access one of them is invalid and generate a panic (panic is a proper message saying that there was something wrong and the program cannot recover).
    3 points
  28. Fixed. Please use "xcodebuild -target CloverConfigPlistValidator" instead of using the option "-scheme" to compile. Compiling through a scheme doesn't really make sense as schemes are made for running into xcode and don't contains any build settings.
    3 points
  29. I'm currently working on cleaning the validator project. This problem is fixed, soon to be committed. Yes, you pull everything. It's not separate project, they are in the same tree.
    3 points
  30. "I lost time" : I think I understand now. But you have to send at least some logs if you want us to look. Wouldn't it be handy if you create a pull request ?
    3 points
  31. Another smooth update!
    3 points
  32. To compile the validator, use "xcodebuild -target CloverConfigPlistValidator -configuration Release". That way, the name of the scheme doesn't matter... Done.
    3 points
  33. Slice

    Clover General discussion

    Enable/Disable the feature is problematic because it can be written in config.plist which we have to check. Сhicken or egg?
    3 points
  34. Oh, I didn't see that. Sorry, my bad. There was quite a few pages of this forum I missed. I think it should stay on, because we know that we will use the validator, most of the time only after we know there is a problem. Knowing that Clover will notify if there is one is a good thing. Looks like we mainly agree on this. That said, a notification at Clover GUI instead of text messages before the GUI would be nicer... But my days has only 24 hours...
    3 points
  35. I like OC Guy But about OpenCore, in the OpenCore Discussions thread is where the people who really know about OpenCore are. I'm thinking of @vit9696 @Andrey1970 @Download-Fritz @Hervé @Pavo @tonyx86 @joevt @mitch_de yourself @Allan and so many others whose name I can't remember now. I am envious (healthy) of these people because my training and knowledge place me far from them. When I saw that I had to work hard to update each OpenCore version was when I decided to prepare for myself, during the evolution of the beta version, the changes that were taking place, and this is how this s
    3 points
  36. OpenCore 0.6.9 EFI Update (Big Sur 11.4 Ready), 3rd May 2021 (Use With Bios Revision F11L or Newer) The EFIs and DSDTs have now been updated to the my latest versions. Changes made include, Lilu 1.5.3, AppleALC 1.6.0, IntelMausi 1.0.6, VirtualSMC 1.2.3, OpenCore Updated to Revision 0.6.9 (Big Sur 11.4 Ready), OpenCanopy is Enabled as Standard, New OpenCanopy Icons Mouse now working in OpenCanopy Plus other minor tweaks and changes to all of the configs. OpenCore EFI Update v0.6.9 - 03/05/2021 OC 069 1,
    3 points
  37. Matgen84

    Clover General discussion

    I think too. A addition with Debug (in config.plist) for example. but currently anyway, if the config.plist is correct, there are no messages.
    3 points
  38. I think if we have the option to toggle between showing/hiding these messages would be a nice addition so is it possible to have it as an option?
    3 points
  39. Hi @Allan The error will appear until you fix it. Send me your config in PM and I'll try to fix it. When the error is fixed your config will be even "More Wonderful"
    3 points
  40. 1Revenger1

    OpenCore Discussion

    We generally recommend creating the fake EC device. The comment about AppleACPIEC not connecting is meant if you also make SSDT-EC disable the original EC to help prevent panics in some cases. I wouldn't recommend a rename because that's a lot of patching your making OC do without any real purpose other than the satisfy the requirement that some device named EC needs to exist, plus it can break booting Windows.
    3 points
  41. 5T33Z0

    Clover General discussion

    Well, open the config with a plist editor to edit the entries. - AppleXcpmCfgLock is not a Quirk used by Clover. Delete it and enable "KernelPM" under Kernel and Kext Patches instead - Move ProvideConsoleGop to GUI Section - As for the GUI entries: I would delete those, save and open the config with Clover Configurator and select the options you need again which recreates the entries. Or compare your config with the sample-config to see if there are difference in formatting (classes, data types, etc.).
    3 points
  42. @Streets Yes. VALIDATING YOUR CONFIG and FIXING ERRORS: Starting from version r5134, Clover now includes error reporting similar to OpenCore which displays configuration errors before the actual boot menu appears. Do the following to validate your config and fix configuration errors: Download CloverConfigPlistValidator.zip from the Clover Repo: https://github.com/CloverHackyColor/CloverBootloader/releases unpack it Open Terminal Drag CloverConfigPlistValidator into it and hit the right arrow key once, so the file path is no longer highlighted/selected
    3 points
  43. See correspondence here https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?do=findComment&comment=2740755
    3 points
  44. 5T33Z0

    Clover General discussion

    These renames are only necessary in OpenCore. You can disable/delete them and the SSDT-HPET.aml that comes along with them and use the "FixIPIC", "FixRTC", "FixTMR" and "FixHPET" instead. This rename doesn't seem to be necessary. Check System DSDT to see if method _UPC really exists. If not, disable/delete it. Another SSDT that you don't need from OpenCore would be "SSDT-SBUS-MCHC.aml" – use "FixSBUS" and "AddMCHC" instead
    3 points
  45. Hi guys me again here with fresh baked 11,4 Beta everything is still intact No big deal no issue Emulated NVRAM Open Core Bootloader X58 The Beast
    3 points
  46. @kushwavez Did you have an error message on the screen finishing with "A fatal error happened. System halted" ? Try this, with fix airport enabled : CloverX64-2021-05-05-23-30-57-d52803e-dirty-jief.zip You have to add that "change" like you any other. It's a submodule instead of a file, but that the same idea. Probably "git add OpenCorePkg". I have to admit I never did on command line.
    2 points
  47. with RDNA2 support ...
    2 points
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...