Vyzantion Posted March 19, 2020 Share Posted March 19, 2020 (edited) Yesterday, a few days after installing Clover for the first time in the new way, via the Clover app, not the pkg file, (an update, technically) suddenly, the screen grew black, a circle of death was spinning (with pauses) and the mouse pointer was visible, but frozen. I gave the command from the keyboard for log of, the circle froze. I had to reset the machine and, on boot on verbose mode, it said something about apfs corruption and was, of course, not able to boot. I use the dosdude1 patcher for Catalina, that, among other things, disables SIP. I have reinstalled Catalina and installed in the new way from the beginning. The OS seems fine, but still I am afraid of surprises like the one I had yesterday. I do not know if it related to the Clover changes, both those implemented by Slice and the ones implemented by Vector Sigma . Edited March 19, 2020 by Vyzantion Link to comment Share on other sites More sharing options...
Slice Posted March 20, 2020 Share Posted March 20, 2020 4 hours ago, Vyzantion said: Yesterday, a few days after installing Clover for the first time in the new way, via the Clover app, not the pkg file, (an update, technically) suddenly, the screen grew black, a circle of death was spinning (with pauses) and the mouse pointer was visible, but frozen. I gave the command from the keyboard for log of, the circle froze. I had to reset the machine and, on boot on verbose mode, it said something about apfs corruption and was, of course, not able to boot. I use the dosdude1 patcher for Catalina, that, among other things, disables SIP. I have reinstalled Catalina and installed in the new way from the beginning. The OS seems fine, but still I am afraid of surprises like the one I had yesterday. I do not know if it related to the Clover changes, both those implemented by Slice and the ones implemented by Vector Sigma . I think it appears because of Clover bug revealed 5 hours ago by Pene. 1 Link to comment Share on other sites More sharing options...
lutin Posted March 23, 2020 Share Posted March 23, 2020 Great app!!!!! Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 Just perfect! Excellent work. Thank you so much. Just tested on Catalina with release v1.16beta, fixing all my issues! As I didn't know how to ensure my MB was NVRAM native, thanks to the app, I get the answer! Just a short question: what means grey NVRAM in the list box under Theme? Link to comment Share on other sites More sharing options...
vector sigma Posted March 23, 2020 Author Share Posted March 23, 2020 1 hour ago, Jessy Lou said: Just a short question: what means grey NVRAM in the list box under Theme? You can chose or write the theme name to load for the next boot without editing the config.plist. The theme name is saved in nvram (which is persistent across reboots) and take precedence over the config.plist. This doesn't install a theme (which eventually you can do it by pressing "Manager") but only the theme to load, which must exist. If you ever run the theme Manager, the pull down will have a complete list of the known themes. 1 Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 1 hour ago, vector sigma said: You can chose or write the theme name to load for the next boot without editing the config.plist. The theme name is saved in nvram (which is persistent across reboots) and take precedence over the config.plist. This doesn't install a theme (which eventually you can do it by pressing "Manager") but only the theme to load, which must exist. If you ever run the theme Manager, the pull down will have a complete list of the known themes. Thanks for your clear and complete reply. Nevertheless, it seems I've something wrong in my conf. As the ASUS ROG MAXIMUS XI HERO (no WiFi) has been seen with native NVRAM, when I reboot the NVRAM seems not to have kept the selected theme (which is already present in the EFI folder). I checked thru the tool, and I saw the selected theme has also vanished. I opened the terminal to run the command 'nvram -p' where the Clover.Theme entry has also vanished. I'm using the following drivers at boot time: ApfsDriverLoader.efi AudioDxe.efi FSInject.efi HFSPlus.efi OsxAptioFix2Drv.efi SMCHelper.efi The kexts are these one: AppleALC FakeSMC InelMausi Lilu USBInjectAll WhateverGreen What I did I do wrong? Link to comment Share on other sites More sharing options...
vector sigma Posted March 23, 2020 Author Share Posted March 23, 2020 1 hour ago, Jessy Lou said: OsxAptioFix2Drv.efi Is this the only memory fix driver that works for you? Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 (edited) 7 minutes ago, vector sigma said: Is this the only memory fix driver that works for you? Yes. AptioMemoryFix froze very quickly at boot. I just finished the following test using Clover.app: a). added EmuVariableUefi.efi a). installed CloverDeamonNew b). changed the theme c). rebooted ==> Ok. The new theme has been used for the new GUI (while nothing has been changed in the config.plist). It's clear for me the MB is not 100% NVRAM native. Am I wrong? Edited March 23, 2020 by Jessy Lou Link to comment Share on other sites More sharing options...
vector sigma Posted March 23, 2020 Author Share Posted March 23, 2020 (edited) 18 minutes ago, Jessy Lou said: Am I wrong? Yes and not. EmuVariableUefi.efi is the easy and fastest way. But your motherboard has an nvram chip soldered, so it has nvram support. macOS is made for a mac and your is a PC... macOS needs to know what to do, so try to install this: SSDT-PMC.aml.zip in (EFI/CLOVER/ACPI/patched) delete EmuVariableUefi.efi delete OsxAptioFix2Drv.efi install AptioMemoryFix.efi Uninstall the CloverDeamonNew Of course make this changes to a copy of your EFI folder and boot from USB as the result is not granted. Reboot twice and then set a theme and see if at next reboot it's persistent. Edited March 23, 2020 by vector sigma Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 15 minutes ago, vector sigma said: Yes and not. EmuVariableUefi.efi is the easy and fastest way. But your motherboard has an nvram chip soldered, so it has nvram support. macOS is made for a mac and your is a PC... macOS needs to know what to do, so try to install this: SSDT-PMC.aml.zip in (EFI/CLOVER/ACPI/patched) delete EmuVariableUefi.efi delete OsxAptioFix2Drv.efi install AptioMemoryFix.efi Uninstall the CloverDeamonNew Of course make this changes to a copy of your EFI folder and boot from USB as the result is not granted. Reboot twice and then set a theme and see if at next reboot it's persistent. Of course you already know: IT DOES WORK! What I did: 1). I follow 100% of you recommandations. Did a few boots to tests also writing directly to NVRAM thanks to the 'nvram' command. 2). I uninstalled also CloverDeamonNew and I ran additional boots. May I ask you how you generate the SSDT patch? I'm missing knowledge, but I love to understand each step. 1 Link to comment Share on other sites More sharing options...
vector sigma Posted March 23, 2020 Author Share Posted March 23, 2020 8 minutes ago, Jessy Lou said: May I ask you how you generate the SSDT patch? I'm missing knowledge, but I love to understand each step. I don't even know who found this solution but the patch is assingning a memory region (base address and length) compatible with boot.efi and macOS. 1 Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 7 minutes ago, vector sigma said: I don't even know who found this solution but the patch is assingning a memory region (base address and length) compatible with boot.efi and macOS. Thank you again. I had other weird behaviour regarding the sound, but since this solution, it also works perfect. The only thing I see not working perfect is when I change the volume, there's no sound at boot time. I had a look at the values in NVRAM, despite 20% volume, I have no sound. Maybe it's something not related to Clover.app because the sound is only on the left side while the test sound is on both channels. If you need further information, I'll be glad to run a few tests for you. Link to comment Share on other sites More sharing options...
vector sigma Posted March 23, 2020 Author Share Posted March 23, 2020 3 minutes ago, Jessy Lou said: I had other weird behaviour regarding the sound, but since this solution, it also works perfect. The only thing I see not working perfect is when I change the volume, there's no sound at boot time. I had a look at the values in NVRAM, despite 20% volume, I have no sound. did your theme have a sound.wav file? did you selected the correct output (the one physically connected)? what if you use 100% of volume? Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 1 minute ago, vector sigma said: did your theme have a sound.wav file? did you selected the correct output (the one physically connected)? what if you use 100% of volume? 1). Yes. Using Catalina and HexagonDark with WAV files tested OK (on both channels). 2). Yes. See screen copy below. 3). by default I assume it's at 100% and the sound is Ok (except left side only). When I change the volume, whatever the level is, there's nothing. Is it normal that without the sound driver I'm gaining about 2 sec at boot time? Link to comment Share on other sites More sharing options...
vector sigma Posted March 23, 2020 Author Share Posted March 23, 2020 1 minute ago, Jessy Lou said: Is it normal that without the sound driver I'm gaining about 2 sec at boot time? There is a setting in Clover to load the sound asynchronously (which I can't remembar now) but of course you add another process to existing ones, so yes. 5 minutes ago, Jessy Lou said: 3). by default I assume it's at 100% and the sound is Ok (except left side only). When I change the volume, whatever the level is, there's nothing. Well, don't expect to have a driver as into the OS Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 2 minutes ago, vector sigma said: There is a setting in Clover to load the sound asynchronously (which I can't remembar now) but of course you add another process to existing ones, so yes. I was referring to when the driver AudioDxe is loading before emitting any sound. But as far as Clover.app is always writing the right values concerning the sound in the NVRAM, it's clear the issue can't be from your app. Thanks for taking your time. Link to comment Share on other sites More sharing options...
vector sigma Posted March 23, 2020 Author Share Posted March 23, 2020 Just now, Jessy Lou said: But as far as Clover.app is always writing the right values concerning the sound in the NVRAM, it's clear the issue can't be from your app. Of course Link to comment Share on other sites More sharing options...
Jessy Lou Posted March 23, 2020 Share Posted March 23, 2020 4 minutes ago, vector sigma said: Of course Last thing (for the day): when you uninstall the sound driver, the related sound values in NVRAM remain. Maybe you decided to do so to keep previous values (just in case). Link to comment Share on other sites More sharing options...
exquirentibus Posted March 23, 2020 Share Posted March 23, 2020 (edited) 6 hours ago, vector sigma said: I don't even know who found this solution but the patch is assingning a memory region (base address and length) compatible with boot.efi and macOS. I have a Gigabyte GA-Z207XP-SLI with Kaby Lake i7-7700K. Is the SSDT-PMC.aml something I should add - or is that specific to other motherboards? -- At this link OpenCore Vanilla Guide - Coffee Lake, possibly I found the answer to my question as it seems to only apply to Coffee Lake: SSDT-PMC So true 300 series motherboards(non-Z370) don't declare the FW chip as MMIO in ACPI and so XNU ignores the MMIO region declared by the UEFI memory map. This SSDT brings back NVRAM support and uses the scope PCI0.LPCB, this is the most common scope so a pre-made can be found here: SSDT-PMC.aml Edited March 23, 2020 by exquirentibus Link to comment Share on other sites More sharing options...
lutin Posted March 24, 2020 Share Posted March 24, 2020 In CloverApp I go "update to r5107" but nothings happens. What did I wrong? Link to comment Share on other sites More sharing options...
Matgen84 Posted March 24, 2020 Share Posted March 24, 2020 7 minutes ago, lutin said: In CloverApp I go "update to r5107" but nothings happens. What did I wrong? What do you means! Do you select a disk to install! (sorry for my stupid question). Link to comment Share on other sites More sharing options...
lutin Posted March 24, 2020 Share Posted March 24, 2020 (edited) Merci @Matgen84, question pas trop stupide, elle est relevante... Here is my situation: 1 my mounted disk, the one to upgrade 2 update is downloading 4 then nothing... No new window, no 'installateur de Clover r5107' (3 this might be my problem? I use CarbonCopyCloner to keep a back-up, and as I remember CCC can mix up the UUID from different disks? Can this be root of my trouble?) Edited March 24, 2020 by lutin Link to comment Share on other sites More sharing options...
Matgen84 Posted March 24, 2020 Share Posted March 24, 2020 (edited) 19 minutes ago, lutin said: Merci @Matgen84, question pas trop stupide, elle est relevante... Here is my situation: 1 my mounted disk, the one to upgrade 2 update is downloading (3 this might be my problem? I use CarbonCopyCloner to keep a back-up, and as I remember CCC can mix up the UUID from different disks? Can this be root of my trouble?) 4 then nothing... No new window, no 'installateur de Clover r5107' If I'm not mistaken To update, first don't mount EFI partition at this stage, second Clover cannot be installed without making choices click "Update to r5107" button in the new windows select a disk (the app automount efi partition) select your driver click "Install" That's what I do. Take a look at my previous picture. Edited March 24, 2020 by Matgen84 Link to comment Share on other sites More sharing options...
lutin Posted March 24, 2020 Share Posted March 24, 2020 (edited) Merci @Matgen84, but yes, I guess you are mistaken. My experience is I do not get anything like 'in the new windows select a disk' There is no new window showing up, Clover installer doesn't start tu pige? Comme indiqué sous mon 4 The point of my posting is to flag a bug (?). I do manage to install the update manually, no worries, but maybe @vector sigma would like to know. Edit, for the curiosity: After manually updating to r5107 I do get the option Install 5106 Clicking this item take me to a new window with 'Clover Installer r5106' So this one works fine... Edited March 24, 2020 by lutin 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted March 24, 2020 Share Posted March 24, 2020 10 minutes ago, lutin said: Merci @Matgen84, but yes, I guess you are mistaken. My experience is I do not get anything like 'in the new windows select a disk' There is no new window showing up, Clover installer doesn't start tu pige? Comme indiqué sous mon 4 The point of my posting is to flag a bug (?). I do manage to install the update manually, no worries, but maybe @vector sigma would like to know. Right, I'm mistaken between install and update 1 Link to comment Share on other sites More sharing options...
Recommended Posts