Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

Advertisement

Hi Clover developer's team

 

With latest commit r4665, I've some big problem with my usb keyboard connected to usb keyboard port (Asus p8z77-v Pro):

 

  • In Clover GUI, Shell issues: delayed entry, no seizure at all, delayed with movement arrow

 

I use mandatory drivers, aptiomemory, aptioinput, applepkg drivers too

 

Please, any solutions

Thanks

 

EDIT: if I delete AppleKeyFeeder.efi, all works fine again

Edited by Matgen84

Share this post


Link to post
Share on other sites
6 hours ago, Matgen84 said:
  • In Clover GUI, Shell issues: delayed entry, no seizure at all, delayed with movement arrow

EDIT: if I delete AppleKeyFeeder.efi, all works fine again

Yes, I also got "Slow Motion Fx" on Clover GUI using this efi driver, it still has no "Description" yet on package, so.. simply, this is not suitable for our mach, I think.

Share this post


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

Yes, I also got "Slow Motion Fx" on Clover GUI using this efi driver, it still has no "Description" yet on package, so.. simply, this is not suitable for our mach, I think.

 

After some research, I find some explanations in Jief_MacHack topic: to use AppleKeyFeeder.efi, we have to remove usb and ps2 drivers like AptioInput in my case (if I understand well cause my english is bad).  

So, everything works well on Clover GUI, Shell...

 

Jief_MacHack Topic

 

 

Share this post


Link to post
Share on other sites

Clover InfoPlistPatch not work

If I edit GeForce kext work fine.

How can fix this issue.Thank you.

Comment               GK100 to GF100 
Find                  474B3130 30
InfoPlistPatch         Yes
Name                  com.apple.GeForce
Replace               47463130 30

 

Edited by nmano

Share this post


Link to post
Share on other sites

Hi @Slice

 

Lastest commit r4667 without AppleEvent.efi: I've got blackscreen at boot without clover GUI. Rollback to r4665: all works fine.

 

Where is my mistake?

 

Any ideas, please.

Share this post


Link to post
Share on other sites
32 minutes ago, Matgen84 said:

Lastest commit r4667 without AppleEvent.efi: I've got blackscreen at boot without clover GUI. Rollback to r4665: all works fine.

 

Currently, no issue here with r4667:

Spoiler

0:100  0:000  Now is 8.9.2018,  1:6:26 (GMT)
0:100  0:000  Starting Clover revision: 4667 on American Megatrends EFI
0:100  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/badruzeus/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.11.6 | XCODE: 8.2.1]
.....
0:956  0:000  === [ LoadDrivers ] =======================================
0:964  0:007  Loading ApfsDriverLoader-64.efi  status=Success
0:970  0:006   - driver needs connecting
0:970  0:000  Loading AptioMemoryFix-64.efi  status=Success
0:971  0:000  Loading CsmVideoDxe-64.efi  status=Success
0:972  0:000   - driver needs connecting
0:972  0:000  Loading DataHubDxe-64.efi  status=Success
0:975  0:003  Loading EnglishDxe-64.efi  status=Success
0:976  0:000  Loading FSInject-64.efi  status=Success
0:977  0:000  Loading VBoxHfs-64.efi  status=Success
0:978  0:000   - driver needs connecting
0:978  0:000  3 drivers needs connecting ...
0:978  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:978  0:000  APFS driver loaded
0:978  0:000  Video driver loaded: disconnect Success
.....
12:175  0:000  === [ StartLoader ] =======================================
12:175  0:000  Finally: ExternalClock=25MHz BusSpeed=99774kHz CPUFreq=2195MHz PIS: hw.busfrequency=100000000Hz
12:175  0:000  Loading boot.efi  status=Success
12:356  0:181  GetOSVersion: 10.11.6 (15G22010)
12:356  0:000  CSR_CFG: CSR_ALLOW_UNTRUSTED_KEXTS | CSR_ALLOW_UNRESTRICTED_FS | CSR_ALLOW_TASK_FOR_PID | CSR_ALLOW_UNRESTRICTED_DTRACE | CSR_ALLOW_UNRESTRICTED_NVRAM

 

 

Share this post


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

 

Currently, no issue here with r4667:

 

 

Maybe the new applekeyaggregator is the reason? It is useful for FirefaultV2, but I do not use firefault. What do you think of that Below r4665 bdmesg result and r4667 screenshot.

Capture d’écran 2018-09-08 à 08.56.40.png

Edited by Matgen84

Share this post


Link to post
Share on other sites
2 minutes ago, Matgen84 said:

Maybe the new applekeyaggregator is the reason? It is useful for FirefaultV2, but I do not use firefault. What do you think of that Below r4665 bdmesg result and r4667 screenshot.

I don't use any FV related *.efi driver.. but only these on my /EFI/CLOVER/drivers64UEFI:

ApfsDriverLoader-64.efi
AptioMemoryFix-64.efi
CsmVideoDxe-64.efi
DataHubDxe-64.efi
EnglishDxe-64.efi
FSInject-64.efi
VBoxHfs-64.efi

 

Share this post


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

 


ApfsDriverLoader-64.efi
AptioMemoryFix-64.efi
CsmVideoDxe-64.efi
DataHubDxe-64.efi
EnglishDxe-64.efi
FSInject-64.efi
VBoxHfs-64.efi

 

What is EnglishDxe-64 for?

Edited by ellaosx

Share this post


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

I don't use any FV related *.efi driver.. but only these on my /EFI/CLOVER/drivers64UEFI:


ApfsDriverLoader-64.efi
AptioMemoryFix-64.efi
CsmVideoDxe-64.efi
DataHubDxe-64.efi
EnglishDxe-64.efi
FSInject-64.efi
VBoxHfs-64.efi

 

 

Thanks. I try again without any FV related *.efi driver on my system

 

EDIT: all works fine now with r4667

Edited by Matgen84

Share this post


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

Lastest commit r4667 without AppleEvent.efi: I've got blackscreen at boot without clover GUI. Rollback to r4665: all works fine.

 

Where is my mistake?

 

Any ideas, please.

 

I also had boot hang with r4667 UEFI driver AppleKeyAggregator-64.efi on my NUC6i5SYH.  Actually was able to reach Clover main menu but hang occurs after selecting the macOS entry.

 

Still boots fine if I use CLOVERX64.efi/BOOTX64.efi r4667 with UEFI drivers from r4664.

Share this post


Link to post
Share on other sites

With the latest clover I cannot boot any OS. As soon as I press anything on the clover boot screen it freezes. I have tried reverting back to older versions via copy paste within windows but that isn’t working.


Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
5 hours ago, Matgen84 said:

Hi @Slice

 

Lastest commit r4667 without AppleEvent.efi: I've got blackscreen at boot without clover GUI. Rollback to r4665: all works fine.

 

Where is my mistake?

 

Any ideas, please.

FV2Apfs_OSX_10.13.6_Clover4667 - I don't have problem.clover4667.thumb.jpg.f91336c6b45deb404d07b773bf940f21.jpg

Share this post


Link to post
Share on other sites

Same situation here - updated a working 4666 version to 4667 and now pc boots, Clover starts then black screen. Latest versions of Lilu, whatevergreen, etc installed. Boot from backup, reinstall 4666 and all works again.

 

crash

 

 

Share this post


Link to post
Share on other sites
On 9/6/2018 at 8:26 PM, nmano said:

Clover InfoPlistPatch not work

If I edit GeForce kext work fine.

How can fix this issue.Thank you.


Comment               GK100 to GF100 
Find                  474B3130 30
InfoPlistPatch         Yes
Name                  com.apple.GeForce
Replace               47463130 30

 

How if adding MatchOS?

Share this post


Link to post
Share on other sites
Same situation here - updated a working 4666 version to 4667 and now pc boots, Clover starts then black screen. Latest versions of Lilu, whatevergreen, etc installed. Boot from backup, reinstall 4666 and all works again.

 

crash

 

 

Yeah I had to revert back to 4665 (didn’t have 4666) and it’s all good again. I don’t think it’s a clover thing as I replaced the bootx64 and cloverx64 from earlier versions and it would still freeze up so I think it’s a driver64uefi problem with what ever was updated from 4665 > 4667. One of the main ones I think if I remember correctly was AptioMemoryFix that had a few updates.

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
55 minutes ago, SavageAUS said:

Yeah I had to revert back to 4665 (didn’t have 4666) and it’s all good again. I don’t think it’s a clover thing as I replaced the bootx64 and cloverx64 from earlier versions and it would still freeze up so I think it’s a driver64uefi problem with what ever was updated from 4665 > 4667. One of the main ones I think if I remember correctly was AptioMemoryFix that had a few updates.

 

 

Sent from my iPhone using Tapatalk

 

On previous post, I indicate that I've a issue commit r4667 (description: move AppleEvent into AppleKeyAggregator driver) on my system. In commit r4665, the two driver are separated: no issue on my rig.

Share this post


Link to post
Share on other sites

Thanks for the signal. Indeed it was logical to remove AppleEvent protocol support from Clover, as it is not "core" functionality and is supposed to be provided by FV2 drivers.

I guess Apple changed something and it is now unfortunately required even for a normal boot. I reverted some of the changes to make Clover install dummy AppleEvent if no other implementation is present.

Let me know whether it works.

AppleEventFallback.zip

Share this post


Link to post
Share on other sites

 

52 minutes ago, vit9696 said:

Thanks for the signal. Indeed it was logical to remove AppleEvent protocol support from Clover, as it is not "core" functionality and is supposed to be provided by FV2 drivers.

I guess Apple changed something and it is now unfortunately required even for a normal boot. I reverted some of the changes to make Clover install dummy AppleEvent if no other implementation is present.

Let me know whether it works.

AppleEventFallback.zip

 

Lastest commit r4667 without AppleEvent.efi, but with AppleKeyaggregator.efi: I've got blackscreen at boot instead of clover GUI

 

I test new Clover.efi with AppleKeyaggregator.efi: I got Clover GUI at boot

 

Thanks

 

Sorry for my bad english and little test. Others can do better tests than me

Share this post


Link to post
Share on other sites
8 hours ago, vit9696 said:

Thanks for the signal. Indeed it was logical to remove AppleEvent protocol support from Clover, as it is not "core" functionality and is supposed to be provided by FV2 drivers.

I guess Apple changed something and it is now unfortunately required even for a normal boot. I reverted some of the changes to make Clover install dummy AppleEvent if no other implementation is present.

Let me know whether it works.

AppleEventFallback.zip

 

Unfortunately, boot still hangs with problematic FV drivers, even if I use CLOVERX64.efi/BOOTX64.efi from the above post (UEFI booting into my non FV macOS volumes (10.13.6 hfs and 10.14beta10 apfs) on my NUC6i5SYH).

 

2 problematic r4667 drivers:  

AppleKeyFeeder-64.efi ---> freeze/unresponsive Clover Main Menu GUI

AppleKeyAggregator-64.efi ---> boot hang after launching macOS as shown below...

 

 

Spoiler

IMG_2622.thumb.JPG.37c23d84c737279ee7c567701ad7f9cb.JPG

 

 

Deleting both drivers from /EFI/CLOVER/drivers64UEFI ---> I can boot again normally with CLOVERX64.efi r4667.

 

I vote for Clover package installer not selecting these problematic FV drivers by default...

Share this post


Link to post
Share on other sites
 
Unfortunately, boot still hangs with problematic FV drivers, even if I use CLOVERX64.efi/BOOTX64.efi from the above post (UEFI booting into my non FV macOS volumes (10.13.6 hfs and 10.14beta10 apfs) on my NUC6i5SYH).
 
2 problematic r4667 drivers:  
AppleKeyFeeder-64.efi ---> freeze/unresponsive Clover Main Menu GUI
AppleKeyAggregator-64.efi ---> boot hang after launching macOS as shown below...
 
 
Spoiler IMG_2622.thumb.JPG.37c23d84c737279ee7c567701ad7f9cb.JPG
 
 
Deleting both drivers from /EFI/CLOVER/drivers64UEFI ---> I can boot again normally with CLOVERX64.efi r4667.
 
I vote for Clover package installer not selecting these problematic FV drivers by default...


Agreed. Clover should only select what was previously selected. And not make default drivers that are not required for boot and those with FileVault know they use it and to select the drivers which will stay selected on further installs.

Share this post


Link to post
Share on other sites

Clover Rename Devices can't sort manually.

 

Such as i want to patch OSID first then patch _OSI later but when i sort then in right way when i save the config.plist it still sort by A-Z and _XXX to the last so i want a features to sort Rename Devices manually to avoid some problem.

 

Thanks.

Edited by gujiangjiang

Share this post


Link to post
Share on other sites
18 hours ago, vit9696 said:

Thanks for the signal. Indeed it was logical to remove AppleEvent protocol support from Clover, as it is not "core" functionality and is supposed to be provided by FV2 drivers.

I guess Apple changed something and it is now unfortunately required even for a normal boot. I reverted some of the changes to make Clover install dummy AppleEvent if no other implementation is present.

Let me know whether it works.

AppleEventFallback.zip

Should this be renamed CLOVERX64.efi to overwrite the old one?

Share this post


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

Clover Rename Devices can't sort manually.

 

Such as i want to patch OSID first then patch _OSI later but when i sort then in right way when i save the config.plist it still sort by A-Z and _XXX to the last so i want a features to sort Rename Devices manually to avoid some problem.

 

Thanks.

Clover uses order of patches exactly as they written in config.plist.

But some program you used may change the order in their way. Don't use Clover configurator I take no responsibility how it can change config.plist.

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
×