Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

Advertisement
1 hour ago, Sherlocks said:

froze up -> processing -> reboot okay?
i know vit9696 nvram clear has bootorder remove. i think he want all nvram value initialized. i will add that avoid to remove boot option.

나의 LG-F800S 의 Tapatalk에서 보냄
 

Thanks, deleting the boot menu will break other OS installations. May prevent booting at all on some systems.

Share this post


Link to post
Share on other sites
Thanks, deleting the boot menu will break other OS installations. May prevent booting at all on some systems.
try latest version r4717. cleannvram.efi has deleting the boot menu option. i added that disabled this option. i tested again. there is no problem.

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
1 minute ago, Sherlocks said:

".. cleannvram.efi has deleting the boot menu option."

 

Sorry, I've removed this *.efi before (on last r4716 test) and it still changed bootloader orders.

OK, I'll try again with r4717.

Share this post


Link to post
Share on other sites
7 minutes ago, Badruzeus said:

 

Sorry, I've removed this *.efi before (on last r4716 test) and it still changed bootloader orders.

OK, I'll try again with r4717.

 

you can't see BootOrder nnvram in macos. cleannvram.efi remove BootOrder nvram value and other from filter that has Boot####.

it affects our clover boot option entry in BIOS. 

 

after press f11, my nvram result(aptiomemoryfix, vitrualsmc). it's very clean status.

Last login: Sat Oct 20 21:15:07 on ttys000
SherloccBookPro:~ sherlocks$ nvram -p
fmm-computer-name	Sherlocks%ec%9d%98 MacBook%c2%a0Pro
security-mode	none
bluetoothActiveControllerInfo	z%e0%89%04%00%00%00%000%14%ac%d1%b8%e2%a4%d0
EFILoginHiDPI	%00%00%00%00
specialbootdevice	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00%00H%06%00%00%00%00%00%00(*%08%00%00%00%00%8f%0a5%8c%c6P%e6C%ad%a6^%16p%d2e%d9%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ba%afc~%ff%1e%a9M%b0%d2$%86%1e%e2HD%7f%ff%04%00
SystemAudioVolume	#
SystemAudioVolumeDB	%d9
csr-active-config	w%00%00%00
backlight-level	i%05
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
SherloccBookPro:~ sherlocks$ 

 

Edited by Sherlocks

Share this post


Link to post
Share on other sites
3 minutes ago, Sherlocks said:

 

you can't see BootOrder nnvram in macos. cleannvram.efi remove BootOrder nvram value and other from filter that has Boot####.

it affects our clover boot option entry in BIOS. 

OK, not a big issue for me since I have "Boot entry" options on my Aptio BIOS (firmware) and could be re-ordered easily.

Share this post


Link to post
Share on other sites
1 hour ago, Sherlocks said:

froze up -> processing -> reboot okay?
i know vit9696 nvram clear has bootorder remove. i think he want all nvram value initialized. i will add that avoid to remove boot option.

나의 LG-F800S 의 Tapatalk에서 보냄
 

Was a hard freeze up, had to hold power button.

Updating to 4717 now

AptioMemory, VirtualSMC.

Edited by SavageAUS

Share this post


Link to post
Share on other sites
Just now, Badruzeus said:

OK, not a big issue for me since I have "Boot entry" options on my Aptio BIOS (firmware) and could be re-ordered easily.

 

my peonix bios laptop, i did lost clover boot option(initialized) if BootOrder was removed. only boot windows. so i added boot entry again in bios.

your bios is good. anyways removing the nvram value associated with the boot is not currently the best option.

thanks

Share this post


Link to post
Share on other sites

4717 still hard froze twice when pressing F11. Will boot to 10.14 then reboot and try again.

Edit: Still hard freeze

American Megatrends BIOS Vendor

Aptio Setup Utility.

Boot option no longer removed and order not changed.

Cleared?


MacBook-Pro:~ shane$ nvram -p

fmm-computer-name MacBook Pro

security-mode none

specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%00h%1f%1d%00%00%00%00%08%f8%18%1d%00%00%00%00%e4%dee%86%de%c8%e9K%a2%a6<%fbhi%fbe%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%a1%16|%98%96%cd%13H%9e%15%cd%c2%df6%c4%1d%7f%ff%04%00

EFILoginHiDPI %00%00%00%00

backlight-level %d9%0a

bluetoothActiveControllerInfo %044%d3%13%00%00%00%00 %14t%c6;O%9e%ef

SystemAudioVolume A

csr-active-config g%00%00%00

SystemAudioVolumeDB %f0

flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00

 

Sent from my iPhone using Tapatalk

 

 

Edited by SavageAUS

Share this post


Link to post
Share on other sites
20 minutes ago, Sherlocks said:

my peonix bios laptop, i did lost clover boot option(initialized) if BootOrder was removed. only boot windows. so i added boot entry again in bios.

your bios is good. anyways removing the nvram value associated with the boot is not currently the best option.

thanks

 

Yeah, same as @SavageAUS for r4717.. it cleared NVRAM properly, though Clover freeze immediately when pressing "F11" key. Boot Entries are still there (previous r4716 actually, not only changed bootloader entries order, but removed them #LoL).

Share this post


Link to post
Share on other sites
2 hours ago, Sherlocks said:

@Pavo. i worked NVRAM cleaner and tested all.
its same that CleanNvram.efi of vit9696. try latest clover.

나의 LG-F800S 의 Tapatalk에서 보냄
 

Will do and report back

Share this post


Link to post
Share on other sites

Hard freeze, had to manually power cycle the machine, only using VirutalSMC.kext. Top before and Bottom after.

xhpaD0t.pngZZxJBNK.png

 

Edited by Pavo

Share this post


Link to post
Share on other sites
Hard freeze, had to manually power cycle the machine, only using VirutalSMC.kext. Top before and Bottom after.
xhpaD0t.png&key=fe3af2af16eb0470f2e2d4a58b6627807f7c28a15f62f2320e55193aeffb1358ZZxJBNK.png&key=e2614cc2101ca0bde15555785706edcadb0612bb4178633b5931a326977ca3d4
 
okay did you try cleanvram.efi?

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
Just now, Sherlocks said:

okay did you try cleanvram.efi?

나의 LG-F800S 의 Tapatalk에서 보냄
 

I have not, will try now

Share this post


Link to post
Share on other sites
1 hour ago, Sherlocks said:

try latest version r4717. cleannvram.efi has deleting the boot menu option. i added that disabled this option. i tested again. there is no problem.

나의 LG-F800S 의 Tapatalk에서 보냄
 

Tested with r4717 Apple NVRAM was cleared, the boot variables were not. Thanks!

nvram.zip

Share this post


Link to post
Share on other sites
Tested with r4717 Apple NVRAM was cleared, the boot variables were not. Thanks!nvram.zip

 

great. we can't see nvram boot order variables in macos. it's normal.your system shown good result. thanks for report.

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

 

 

Share this post


Link to post
Share on other sites
Just now, Sherlocks said:

great. we can't see boot variables in macos. it's normal.
your system shown good result.

나의 LG-F800S 의 Tapatalk에서 보냄
 

clearnvram.efi also freezes machine with a required manual power cycle. result are the same in nvram -p

Share this post


Link to post
Share on other sites
clearnvram.efi also freezes machine with a required manual power cycle. result are the same in nvram -p
okay. seems logic is not univeral for all bios.
i will check it tommorow. and i will upload test file here.

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
14 hours ago, SavageAUS said:

4717 still hard froze twice when pressing F11. Will boot to 10.14 then reboot and try again.

Edit: Still hard freeze

American Megatrends BIOS Vendor

Aptio Setup Utility.

Boot option no longer removed and order not changed.

Cleared?

 


MacBook-Pro:~ shane$ nvram -p

fmm-computer-name MacBook Pro

security-mode none

specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%00h%1f%1d%00%00%00%00%08%f8%18%1d%00%00%00%00%e4%dee%86%de%c8%e9K%a2%a6<%fbhi%fbe%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%a1%16|%98%96%cd%13H%9e%15%cd%c2%df6%c4%1d%7f%ff%04%00

EFILoginHiDPI %00%00%00%00

backlight-level %d9%0a

bluetoothActiveControllerInfo %044%d3%13%00%00%00%00 %14t%c6;O%9e%ef

SystemAudioVolume A

csr-active-config g%00%00%00

SystemAudioVolumeDB %f0

flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00

 

 

Sent from my iPhone using Tapatalk

 

 

 

your nvram was clean.

 

13 hours ago, Pavo said:

clearnvram.efi also freezes machine with a required manual power cycle. result are the same in nvram -p

 

 

try this test file for freeze problem.

 

little freeze happen when removing nvram values. but after freezing, your system have to reboot. if hold on freezing option long time, it's problem.

test.zip

Share this post


Link to post
Share on other sites
 
 
try this test file for freeze problem.
 
little freeze happen when removing nvram values. but after freezing, your system have to reboot. if hold on freezing option long time, it's problem.
test.zip

Test files still hard freeze for me.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
3 hours ago, Sherlocks said:
 

try this

test1.zip

Hard freeze again.

Is there anything I can provide to help?

 

4717 Works fine clearing nvram with F11 at clover GUI on my skylake hack.

Edited by SavageAUS

Share this post


Link to post
Share on other sites

It does not say which disk the EFI partition belongs to anywhere.

 

It does say EFI on Install or EFI on High Sierra HD in Mount EFI section

 

723880003_ScreenShot2018-10-20at17_42_46.png.0d9d96a3e3e71a20e87de34e72a1caf2.png

 

But it does not say what drive does the EFI partition belongs to nor which which drive does the config.plist belongs

 

not in acquired configurations list

 

1363065281_ScreenShot2018-10-20at17_42_54.png.9dc845649de53145af61757fe51e6f1e.png

 

and not in the file path on status bar

 

1407601151_ScreenShot2018-10-21at09_35_43.png.a1fd0233675640b465354ef960f0f901.png

 

It is not possible to tell which drive the EFI belongs to neither in Finder nor Desktop

 

1354428479_ScreenShot2018-10-21at09_43_27.png.41a151f779aaa1403023092b19d86a61.png

 

Not through the Get Info 

 

2084551382_ScreenShot2018-10-21at09_43_41.png.7ad5c13dba5ad26baee30616213087cd.png

 

I have created empty folders on each EFI partition with names which tell which is which. 

 

It is not right. It should be visible in Clover too. You should be able to tell which config.plist you are editing.

 

1928594351_ScreenShot2018-10-21at09_53_47.png.8cf54075da1e7a3707259aa220519e5d.png

 

At least make the disk volume folder name e.g. EFI on Install instead of EFI 3...

Edited by kurbads

Share this post


Link to post
Share on other sites
23 minutes ago, kurbads said:

It does not say which disk the EFI partition belongs to anywhere.

 

It does say EFI on Install or EFI on High Sierra HD in Mount EFI section

 

 


723880003_ScreenShot2018-10-20at17_42_46.png.0d9d96a3e3e71a20e87de34e72a1caf2.png

 

But it does not say what drive does the EFI partition belongs to nor which which drive does the config.plist belongs

 

not in acquired configurations list

 

1363065281_ScreenShot2018-10-20at17_42_54.png.9dc845649de53145af61757fe51e6f1e.png

 

and not in the file path on status bar

 

1407601151_ScreenShot2018-10-21at09_35_43.png.a1fd0233675640b465354ef960f0f901.png

 

It is not possible to tell which drive the EFI belongs to neither in Finder nor Desktop

 

1354428479_ScreenShot2018-10-21at09_43_27.png.41a151f779aaa1403023092b19d86a61.png

 

Not through the Get Info 

 

2084551382_ScreenShot2018-10-21at09_43_41.png.7ad5c13dba5ad26baee30616213087cd.png

 

I have created empty folders on each EFI partition with names which tell which is which. 

 

It is not right. It should be visible in Clover too. You should be able to tell which config.plist you are editing.

 

1928594351_ScreenShot2018-10-21at09_53_47.png.8cf54075da1e7a3707259aa220519e5d.png
 

 

At least make the disk volume folder name e.g. EFI on Install instead of EFI 3...

 

Sorry, I don't get what's your point. How did you get lots of EFI Partitions?

Anyway, I usually use only 1 EFI (with Clover Bootloader inside) on a mach with Multibooting. On my case, I created GPT partition map for another Disks with gParted (or similar 3rd party apps) so it didn't create new EFI. But if you're referring to Clover Configurator.app, this question should be addressed to @mackie100.

Edited by Badruzeus

Share this post


Link to post
Share on other sites
5 minutes ago, Badruzeus said:

 

Sorry, I don't get what's your point. How did you get lots of EFI Partitions?

Anyway, I usually use only 1 EFI on a mach with Multibooting. On my case, I create GPT partition map for another Disks with gParted (or similar 3rd party apps) so it didn't create new EFI. But if you're referring to Clover Configurator.app, this question should be addressed to @mackie100.

I am sorry that you do not understand how because you only use one disk in your computer.

 

I however use several. And I can potentially have an EFI partition on USB drive.

 

It is completely clear that there can be and in my case there are several HDDs and several EFIs from the first screen in my post. 

 

Did you look at my question before answering it?

Edited by kurbads

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Klaidonis
      I am making a minimal Clover build for the fastest boot possible with the boot6 file in legacy mode.
      While looking at the preboot.log, I noticed that there is a line without explanation (at 0:892). Apparently, whatever it is, the execution time of it is close to 2 seconds, more than 55% of the total logged boot time in the current configuration. This does not change whether I use USB 2 or USB 3 port.
       
      Is there a way to eliminate or speed up the above? Also, is there anything else you can suggest to improve the performance based on the below log file? Which moment in the boot process corresponds to the start time in preboot.log?  
      The last thing I would like to understand is the delay/timeout after the boot6 file has loaded, and the number 6 disappears from the screen. For about 2 seconds or slightly less, I can press any key, and then it will enter the BIOS-like interface from the boot6 file. Without further knowledge, it seems like those 2 seconds are just delay time, and only after that is CLOVERX64.efi actually started, which, I presume, is approximately when the preboot.log timer starts. So, if the aforementioned is correct, can I get rid of this delay as well? Note that I am using the boot1f32 file to chain-load boot6, which does not include the initial 2-second wait period for a keypress.
       
      === preboot.log ===
      0:100 0:100 MemLog inited, TSC freq: 2394459554 0:100 0:000 CPU was calibrated with ACPI PM Timer 0:100 0:000 LegacyRegion2: Chipset/proc: 0x0A048086 0:100 0:000 Next Generation Core processors (PAM 0x80-0x86) 0:100 0:000 Test PAM1=(0x41=90, 0x5a=90, 0x81=11, 0x91=00) at chipset 0A048086 0:100 0:000 , Install = Success 0:112 0:012 BiosVideoDriverBindingStart! 0:112 0:000 BiosVideoCheckForVbe 0:112 0:000 EdidOverride not found 0:121 0:009 Edid1+ 0:121 0:000 found Detail Timing 1920x1080 0:121 0:000 timing string after 0xFE:AUO 0:121 0:000 timing string after 0xFE:B156HAN01.2 0:122 0:000 0 1280x1024 attr=9B - ok, edid- 0:122 0:000 1 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=1 0:122 0:000 2 640x480 attr=9B - ok, edid-, 640x480, working 0:122 0:000 3 800x600 attr=9B - ok, edid-, 800x600, working 0:123 0:000 4 1920x1080 attr=9B - ok, edid+, working, highest, pref=4 0:123 0:000 BV new mode: 4 1920x1080 0:398 0:275 SetMode pref 4 (4) = Success 0:892 0:493 VGA Pci.Hdr.Command=6 - not enabled 2:623 1:731 2:623 0:000 Now is 21.02.2020, 13:03:21 (GMT) 2:623 0:000 Starting Clover revision: 5103 (master, commit 3f3b85da0) on CLOVER EFI 2:623 0:000 Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -t GCC53 | -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/sergey/src/CloverHackyColor/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: 10.14.6] 2:623 0:000 SelfDevicePath=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) @940C9698 2:623 0:000 SelfDirPath = \EFI\CLOVER 2:623 0:000 SimpleTextEx Status=Success 2:623 0:000 === [ Get Smbios ] ======================================== 2:623 0:000 Type 16 Index = 0 2:623 0:000 Total Memory Slots Count = 2 2:623 0:000 Type 17 Index = 0 2:623 0:000 SmbiosTable.Type17->Speed = 1600MHz 2:623 0:000 SmbiosTable.Type17->Size = 4096MB 2:623 0:000 SmbiosTable.Type17->Bank/Device = BANK 0 DIMM0 2:623 0:000 SmbiosTable.Type17->Vendor = Hynix 2:623 0:000 SmbiosTable.Type17->SerialNumber = 00000000 2:623 0:000 SmbiosTable.Type17->PartNumber = HMT451S6MFR6A-PB 2:623 0:000 Type 17 Index = 1 2:623 0:000 SmbiosTable.Type17->Speed = 1600MHz 2:623 0:000 SmbiosTable.Type17->Size = 8192MB 2:623 0:000 SmbiosTable.Type17->Bank/Device = BANK 2 DIMM1 2:623 0:000 SmbiosTable.Type17->Vendor = Kingston 2:623 0:000 SmbiosTable.Type17->SerialNumber = 5A060A8A 2:623 0:000 SmbiosTable.Type17->PartNumber = KHX1600C9S3L/8G 2:623 0:000 Boot status=0 2:623 0:000 Running on: 'Aspire V5-573G' with board 'Dazzle_HW' 2:623 0:000 === [ GetCPUProperties ] ================================== 2:623 0:000 CPU Vendor = 756E6547 Model=40651 2:623 0:000 The CPU supported SSE4.1 2:623 0:000 BrandString = Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz 2:623 0:000 The CPU supported turbo 2:623 0:000 MSR 0x35 20004 2:623 0:000 MSR 0xE2 before patch 1E008405 2:623 0:000 MSR 0xE2 is locked, PM patches will be turned on 2:623 0:000 MSR 0xCE 0008083D_F3011800 2:623 0:000 corrected FLEX_RATIO = 0 2:623 0:000 MSR 0x1B0 00000000 2:623 0:000 FSBFrequency = 71 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz 2:623 0:000 MaxDiv/MinDiv: 24.0/8 2:623 0:000 Turbo: 27/27/27/30 2:623 0:000 Features: 0xBFEBFBFF 2:623 0:000 Threads: 4 2:623 0:000 Cores: 2 2:623 0:000 FSB: 100 MHz 2:623 0:000 CPU: 1700 MHz 2:623 0:000 TSC: 1700 MHz 2:623 0:000 PIS: 100 MHz 2:623 0:000 ExternalClock: 25 MHz 2:623 0:000 === [ GetDevices ] ======================================== 2:623 0:000 GOP found at: PcieRoot(0x0)/Pci(0x2,0x0)/AcpiAdr(0x80010100) 2:623 0:000 PCI (00|00:00.00) : 8086 0A04 class=060000 2:623 0:000 PCI (00|00:02.00) : 8086 0A16 class=030000 2:623 0:000 - GOP: Provided by device 2:623 0:000 - GFX: Model=Intel HD Graphics 4400 (Intel) 2:623 0:000 PCI (00|00:03.00) : 8086 0A0C class=040300 2:623 0:000 PCI (00|00:14.00) : 8086 9C31 class=0C0330 2:623 0:000 PCI (00|00:16.00) : 8086 9C3A class=078000 2:623 0:000 PCI (00|00:1B.00) : 8086 9C20 class=040300 2:623 0:000 PCI (00|00:1C.00) : 8086 9C10 class=060400 2:623 0:000 PCI (00|00:1C.02) : 8086 9C14 class=060400 2:623 0:000 PCI (00|04:00.00) : 168C 0034 class=028000 2:623 0:000 - WIFI: Vendor=Atheros 2:623 0:000 PCI (00|00:1C.03) : 8086 9C16 class=060400 2:623 0:000 PCI (00|05:00.00) : 10EC 5287 class=FF0000 2:623 0:000 PCI (00|05:00.01) : 10EC 8168 class=020000 2:623 0:000 - LAN: 0 Vendor=Realtek 2:623 0:000 PCI (00|00:1C.04) : 8086 9C18 class=060400 2:624 0:000 PCI (00|01:00.00) : 10DE 0FE4 class=030200 2:624 0:000 PCI (00|00:1D.00) : 8086 9C26 class=0C0320 2:624 0:000 PCI (00|00:1F.00) : 8086 9C43 class=060100 2:624 0:000 PCI (00|00:1F.02) : 8086 9C03 class=010601 2:624 0:000 PCI (00|00:1F.03) : 8086 9C22 class=0C0500 2:624 0:000 === [ GetDefaultSettings ] ================================ 2:624 0:000 Clover load options size = 0 bytes 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G--00-00-00-00-00-00. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Aspire V5-573G-1700. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Dazzle_HW. Dir not exists 2:624 0:000 CheckOEMPathExists tried EFI\CLOVER\OEM\Dazzle_HW-1700. Dir not exists 2:624 0:000 set OEMPath by default: EFI\CLOVER 2:637 0:012 EFI\CLOVER\config.plist loaded: Success 2:637 0:000 === [ GetListOfThemes ] =================================== 2:637 0:000 === [ Found config plists ] =============================== 2:637 0:000 - config.plist 2:637 0:000 === [ GetEarlyUserSettings ] ============================== 2:637 0:000 timeout set to 0 2:637 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0) 2:637 0:000 Default theme: embedded 2:637 0:000 === [ LoadDrivers ] ======================================= 2:637 0:000 === [ InitScreen ] ======================================== 2:637 0:000 Console modes reported: 4, available modes: 2:637 0:000 - [01]: 80x25 2:637 0:000 - [02]: 80x50 2:637 0:000 - [03]: 100x31 2:637 0:000 - [04]: 240x56 (current mode) 2:637 0:000 SetScreenResolution: 1920x1080 - already set 2:637 0:000 SetScreenResolution: 1920x1080 - already set 2:637 0:000 reinit: self device path=PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) 2:637 0:000 === [ GetMacAddress ] ===================================== 2:637 0:000 === [ ScanSPD ] =========================================== 2:637 0:000 Scanning SMBus [8086:9C22], mmio: 0xB3619004, ioport: 0x5040, hostc: 0x1 2:656 0:018 Slot: 2 Type 24 8192MB 1600MHz Vendor=Kingston PartNo=KHX1600C9S3L8G SerialNo=050A0006000A080A 2:657 0:000 === [ GetAcpiTablesList ] ================================= 2:657 0:000 Get Acpi Tables List from RSDT: 2:657 0:000 - [00]: FACP ACRPRDCT len=268 2:657 0:000 - [01]: UEFI ACRPRDCT len=566 2:657 0:000 - [02]: FPDT ACRPRDCT len=68 2:657 0:000 - [03]: ASF! ACRPRDCT len=165 2:657 0:000 - [04]: HPET ACRPRDCT len=56 2:657 0:000 - [05]: APIC ACRPRDCT len=140 2:657 0:000 - [06]: MCFG ACRPRDCT len=60 2:657 0:000 - [07]: BOOT ACRPRDCT len=40 2:657 0:000 - [08]: LPIT ACRPRDCT len=148 2:657 0:000 - [09]: ASPT ACRPRDCT len=52 2:657 0:000 - [10]: DBGP ACRPRDCT len=52 2:657 0:000 - [11]: SSDT ACRPRDCT len=1337 2:657 0:000 - [12]: SSDT ACRPRDCT len=2776 2:657 0:000 - [13]: SSDT ACRPRDCT len=12013 2:657 0:000 - [14]: SSDT ACRPRDCT len=11433 2:657 0:000 - [15]: SSDT ACRPRDCT len=2230 2:657 0:000 Calibrated TSC Frequency = 2394459554 = 2394MHz 2:657 0:000 === [ GetUserSettings ] =================================== 2:657 0:000 === [ Found DSDT tables ] ================================= 2:657 0:000 === [ ScanVolumes ] ======================================= 2:657 0:000 Found 8 volumes with blockIO 2:657 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0) 2:659 0:001 Result of bootcode detection: bootable Linux (grub,linux) 2:659 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0) 2:660 0:001 Result of bootcode detection: bootable unknown (legacy) 2:660 0:000 - [02]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,8017BD66-1E24-4B31-8E09-BC49BECD6CC4,0x800,0x21330000) 2:661 0:001 Result of bootcode detection: bootable Windows (vista,win) 2:661 0:000 - [03]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,82F3B738-65E9-458E-B2F1-BB55D4F00885,0x21331000,0x3D0800) 2:663 0:001 - [04]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,E701DCD8-E3C5-4BFA-B61B-BFF4D80153FD,0x21701800,0x18C4F000) 2:664 0:001 - [05]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(4,GPT,4DB1239A-A9D7-4045-A162-7EF1B3A5913B,0x3A350C21,0x3A3B616E) 2:665 0:001 Result of bootcode detection: bootable Windows (vista,win) 2:665 0:000 - [06]: Volume: PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0) 2:677 0:011 Result of bootcode detection: bootable unknown (legacy) 2:677 0:000 USB volume 2:677 0:000 USB volume 2:677 0:000 - [07]: Volume: PcieRoot(0x0)\Pci(0x1D,0x0)\USB(0x0,0x0)\USB(0x4,0x0)\HD(1,MBR,0x04944021,0x3F,0x3BC1042) 2:688 0:011 Result of bootcode detection: bootable unknown (legacy) 2:688 0:000 USB volume 2:688 0:000 USB volume 2:688 0:000 This is SelfVolume !! 2:688 0:000 PutNvramPlistToRtVars: nvram.plist not found 2:689 0:000 No AudioIoProtocols, status=Not Found 2:689 0:000 === [ InitTheme ] ========================================= 2:689 0:000 use daylight theme 2:689 0:000 using embedded theme 2:689 0:000 got embedded sound 2:689 0:000 Channels: 2 Sample rate: 8000 Hz Bits: 16 2:689 0:000 output to channel 0 with volume 70, len=25600 2:689 0:000 sound channels=2 bits=16 freq=8000 2:689 0:000 sound converted to 48kHz 2:689 0:000 not found AudioIo to play 2:689 0:000 sound play end with status=Not Found 2:690 0:001 Using embedded font: Success 2:691 0:000 theme inited 2:691 0:000 Chosen embedded theme 2:691 0:000 after NVRAM boot-args= 2:691 0:000 === [ Dump SMC keys from NVRAM ] ========================== 2:691 0:000 no AppleSMC protocol 2:691 0:000 Entry scan disabled 2:691 0:000 === [ AddCustomTool ] ===================================== 2:692 0:000 === [ GetEfiBootDeviceFromNvram ] ========================= 2:692 0:000 Default boot entry not found 2:692 0:000 DefaultIndex=-1 and MainMenu.EntryCount=4 2:973 0:281 GUI ready  
    • By Jancey
      I used this command: diskutil info disk0s2 | grep -i "Partition UUID" | rev | cut -d' ' -f 1 | rev

      But I accidentally removed the wrong disk and now my main windows drive is not appearing in the bootloader. I can't figure out how to get it back. I tried resetting my windows drive, but I kept getting an error. I also reset my mac and reinstalled Catalina.
    • By gengstapo
      @Hervé
       
      Im having similar issue with my HS setup, dell latitute 3480, i5-7200U
      Once the hdmi plugged in, the laptop display went blank, only could see the external tv
      But, when i put my laptop to sleep & wake up again, both screen got display (hdmi still connected)
      Even the hdmi could be plugged off & in (after sleep), the laptop display is fine
       
      What could be the culprit?
      Dell’s MacBook Pro IORegistry.zip
      config.plist.zip
    • By TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
×