sightvorti.blogg.se

1. Remove vbox clover configurator update#
2. Remove vbox clover configurator driver#
3. Remove vbox clover configurator Patch#
4. Remove vbox clover configurator code#

For example my DMI has a value of 100 MHz, however manually overriding it to a value of 99790 kHz produced better clocks. You can choose a more accurate value, if needed. If it is slightly incorrect, clock issues may arise and the system will behave in a strange way.Īn automatic detection was introduced with revision 1060, which relies on the ACPI timer producing much more accurate values than the ones stored in DMI.ĭMI stores this value in MHz, which is not accurate in contrast to a value calculated from CPU frequency. If this value is not correct, the kernel will not start at all. It is passed from the boot loader to the kernel. Very important value for a stable system. Especially if you care about security and privacy of your data.īus speed in kHz. Believe me or not, but it is not something you should rely on. If Hibernation does not work for you… well, RIP.

Remove vbox clover configurator update#

If you have to use HibernationFixup, you may want to update it to 1.2.1, currently only available from source. If you can boot with AppleRTC/FixRTC patches OFF without BIOS settings reset, disable them, they break stuff in macOS OsxAptioFix1/2/3 will NOT work with hibernation on 10.13.6 and newer, and they may be removed from the default Clover installer in the future (time to upgrade).

Remove vbox clover configurator driver#

Config changes (and driver updates) will benefit all the systems (starting from Yosemite if I remember correctly), not just 10.13.6

Remove vbox clover configurator code#

Starting with 10.13.6 a lot of legacy code got (finally) ditched on Apple side, and some changes are necessary to get hibernation to work on hacks. Revision 4450 introduced a new key (Boot → RtcHibernateAware) which improved the situation with hibernation compatibility and reduced the impact of some security issues in this process.

Remove vbox clover configurator Patch#

However, if RtcHibernateAware does not work for you, enabling AppleRTC patch and using HibernationFixup may be a safer workaround. You should DISABLE them if you have no issues with BIOS preferences afterwards or use HibernationFixup. Note, that AppleRTC or FixRTC patches effectively break hibernation by reducing the available RTC memory and avoiding encryption key preservation. While it is extremely recommended to be turned on if you rely on hibernation, it may not work on your hardware (should be fine on Ivy Bridge and newer at least), and is thus optional and disabled by default. This option relies on a poorly documented (or rather undocumented) RTC memory access, and unspecified RTC memory layout, which is implementation-specific.

To workaround this issue a new option enabling RTC memory erase upon waking from hibernation was added:īoot > RtcHibernateAware = YES (BOOLEAN, off by default) More details could be found in this message.

To be used for Hibernation modes 25 & 3 with Lilu.kext and HibernationFixup.kext.Ī data leak issue was identified in the hibernation code, allowing hibernation encryption key to be passed to the system through RTC and preserved till the next hibernation without a subsequent erase. However, the graphics output protocol is not in anyway modified so if the OS draws after it is started then it is after the boot screen is drawn and will overwrite the custom logo, at least for now. The CustomLogo key can also be used under GUI/Custom/Entries in conjunction with BootBgColor for a different screen for every OS. If no option is specified then the boot screen will be drawn only for >= 10.10 Yosemite, so it remains compatible with previous behavior.