Jump to content
ErmaC

Clover problems report & features request

790 posts in this topic

Recommended Posts

Clover4384, AptioMemoryFixRC5.

I have no problems so far.

Z170m-Plus,OS X 10.13.DB5,Apfs

 

 

0:100  0:100  MemLog inited, TSC freq: 3504495820
0:104  0:004  CPU was calibrated with RTC
0:107  0:003  
0:108  0:000  Now is 18.1.2018,  7:42:27 (GMT)
0:112  0:004  Starting Clover revision: 4384 on American Megatrends EFI
0:119  0:007  Build with: [Args: -x64 -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -t XCODE5 | -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 9 | OS: 10.13.2 | XCODE: 9.2]
0:141  0:022  SelfDevicePath=PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,98AC6E18-2974-4432-9E76-18772C419C46,0x28,0x64000) @B0CCD9D8
0:155  0:013  SelfDirPath = \EFI\BOOT
0:174  0:018  === [ Get Smbios ] ========================================
.....................
0:328  0:005  Boot status=0
0:331  0:002  Running on: 'System Product Name' with board 'Z170M-PLUS'
0:337  0:006  === [ GetCPUProperties ] ================================== 

 

 

Z77-ds3h,OS X 10.13.2

 

 

0:100  0:100  MemLog inited, TSC freq: 3403351673
0:104  0:004  CPU was calibrated with ACPI PM Timer
0:108  0:004  
0:109  0:000  Now is 18.1.2018,  7:43:24 (GMT)
0:113  0:004  Starting Clover revision: 4384 on American Megatrends EFI
0:120  0:006  Build with: [Args: -x64 -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -t XCODE5 | -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 9 | OS: 10.13.2 | XCODE: 9.2]
0:142  0:021  SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,0863F066-65A6-46F9-B747-72F25E463E02,0x28,0x64000) @C8975E18
0:155  0:013  SelfDirPath = \EFI\BOOT
.............................
0:314  0:005  Boot status=0
0:317  0:002  Running on: 'To be filled by O.E.M.' with board 'Z77-DS3H'
0:323  0:006  === [ GetCPUProperties ] ==================================
0:331  0:007  CPU Vendor = 756E6547 Model=206A7 

 

 

N53SV,OS X 10.9.5

 

 

0:100  0:100  MemLog inited, TSC freq: 1995465558
0:100  0:000  CPU was calibrated with ACPI PM Timer
0:100  0:000  
0:100  0:000  Now is 18.1.2018,  7:36:52 (GMT)
0:100  0:000  Starting Clover revision: 4384 on American Megatrends EFI
0:100  0:000  Build with: [Args: -x64 -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -t XCODE5 | -D USE_BIOS_BLOCKIO -D NO_GRUB_DRIVERS_EMBEDDED -D ENABLE_VBIOS_PATCH_CLOVEREFI -D DEBUG_ON_SERIAL_PORT -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE5 -n 9 | OS: 10.13.2 | XCODE: 9.2]
0:101  0:000  SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,F61211C5-87B9-4CDD-BE33-9DC9BD4A478E,0x28,0x64000) @22FF618
0:101  0:000  SelfDirPath = \EFI\CLOVER
...................
0:106  0:000  Running on: 'N53SV' with board 'N53SV'
0:106  0:000  === [ GetCPUProperties ] ==================================
0:106  0:000  CPU Vendor = 756E6547 Model=206A7
0:107  0:000   The CPU supported SSE4.1
0:107  0:000  BrandString = Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
......................
2:003  0:000  PrepareHibernation:
2:003  0:000      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
2:003  0:000      SleepImage name from pref: ImageVolume = 'OSX10.9.5', ImageName = '\private\var\vm\sleepimage'
2:004  0:000      returning previously calculated offset: B24ECD000
2:004  0:000   SleepImageOffset: B24ECD000
2:004  0:000  02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 | .....A..........
2:004  0:000  02 1F 03 12 0A 00 01 00 FF FF 00 00 04 04 18 00 | ................
2:005  0:000  42 00 32 00 34 00 45 00 43 00 44 00 30 00 30 00 | B.2.4.E.C.D.0.0.
2:005  0:000  30 00 00 00 7F FF 04 00                         | 0.......
2:005  0:000  boot-image before: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\B24ECD000
2:009  0:003  DeleteBootOption: Boot0082
2:012  0:003   Boot0082 deleted
2:012  0:000  DeleteFromBootOrder: 0082
2:012  0:000  BootOrder: 3: Boot0003, Boot0000, Boot0082
2:013  0:001   found at index 2
2:016  0:003  SetVariable: BootOrder = Success
2:017  0:000   IOHibernateRTCVariables found - will be used as boot-switch-vars
2:029  0:012  SetScreenResolution: 800x600 - already set
2:029  0:000  Custom boot is disabled
2:029  0:000  Closing events for wake 

 

 

Share this post


Link to post
Share on other sites
Advertisement

Anybody tried 4384, don't work here, had to revert to 4380

r4384 works just fine here on my legacy mach (sig)  :)

Whole "CloverV2" built with GCC under Ubuntu 17.10: Drive

.....  .....
1:403  0:000  Now is 18.1.2018,  6:12:30 (GMT)
1:403  0:000  Starting Clover revision: 4384 on CLOVER EFI
1:403  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t GCC53 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: Ubuntu 17.10]
.....  ..... 

Thanks.

preboot.log-r4384-gcc.zip

Share this post


Link to post
Share on other sites

Anybody tried 4384, don't work here, had to revert to 4380

Same here with r4384

 

I had to use AptioMemory instead of AptioFix3drv to start my system  :yes:

Share this post


Link to post
Share on other sites

Same here with r4384

 

I had to use AptioMemory instead of AptioFix3drv to start my system :yes:

Same issue here all I got in Verbose was lots of +'s with r4384.

Reverted to r4382 no issue.

 

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Same issue here all I got in Verbose was lots of +'s with r4384.

Reverted to r4382 no issue.

 

 

Sent from my SM-G930F using Tapatalk

Reverted to r4383 no issue too

Share this post


Link to post
Share on other sites

Before 4385, if you had both OsxAptioFixDrv and OsxAptioFix2Drv in drivers64UEFI, it would pick up the one that occurs first in the FAT32 directory iteration.  After 4385 there is a prioritisation, so OsxAptioFix2Drv is picked up first.  I suggest you keep just the one that works for use in drivers64UEFI and move the others to drivers-Off/drivers64UEFI.

 

Had to change OsxAptioFixDrv2 to  OsxAptioFixDrv for 4385  :thumbsup_anim:

Share this post


Link to post
Share on other sites

Hello,

Is possible to Clover recognize nvram plist files created for Chameleon based bootloaders (such as Enoch), since it has one already when emuvariable driver is used? I mean, if it could recognize and handle with these plist files, it would be possible to have only one plist file storing nvram variables visible and acessible to both bootloaders for the same system. This would be nice in a multibootloader installation. Thanks.

Share this post


Link to post
Share on other sites

Hello,

Is possible to Clover recognize nvram plist files created for Chameleon based bootloaders (such as Enoch), since it has one already when emuvariable driver is used? I mean, if it could recognize and handle with these plist files, it would be possible to have only one plist file storing nvram variables visible and acessible to both bootloaders for the same system. This would be nice in a multibootloader installation. Thanks.

Let Chameleon to be "like Clover".

nvram.plist is created by very common command

$ nvram -x -p>nvram.plist

so it will not depend on bootloader.

Share this post


Link to post
Share on other sites

Let Chameleon to be "like Clover".

nvram.plist is created by very common command

$ nvram -x -p>nvram.plist

so it will not depend on bootloader.

Thank you for your reply. This solution works very well for Clover, since it can see the new nvram.plist and so it recognizes nvram variables defined in a Chameleon boot session. I've written a bash script and used a daemon to do this at every boot. In the other direction, I've had to use PlistBuddy to edit a nvram.plist file in the formatting that Chameleon expects, so that it can see nvram variables defined in a Clover session. Now I'm trying to make this also "scriptized". Thanks again.

Share this post


Link to post
Share on other sites

Hola y gracias por el cambio que propuse anteriormente.
Subir para evitar desplazarse y barra desplazamiento.

 

Hello and thank you for the change I proposed earlier.
Go up to avoid scrolling and scrolling.

post-471348-0-42743100-1516724783_thumb.png

Share this post


Link to post
Share on other sites

Hola y gracias por el cambio que propuse anteriormente.

Subir para evitar desplazarse y barra desplazamiento.

 

 

Hello and thank you for the change I proposed earlier.

Go up to avoid scrolling and scrolling.

try to replace the original one with this... and compile/build a new pkg...

 

Prueba con este html remplazando el original y luego vuelve a crear el pkg.

 

--> Conclusion.html.zip

 

ErmaC

Share this post


Link to post
Share on other sites

report lang issue to dev.
i reported this issue before
http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2565871
i traced this issue point. but not sure. I just want to report this point.
https://sourceforge.net/p/cloverefiboot/code/4414/tree/rEFIt_UEFI/Platform/DataHubCpu.c#l213
but surely effect lang after update with osxaptiofixv2+emul+ko set(config).

but if use osxaptiofixv3 or aptiomemoryfix without emul, what i mentioned above presents lang issue(ko+eng)
i checked this is OS X's business. so i checked realmac nvram dump.

realmac has this nvram vals
------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang
------------------------------------------------------------------------------
000000: 65 6e 67 00 |eng.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes
------------------------------------------------------------------------------
000000: 65 6e 67 00 |eng.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 00 |en-US.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 00 |en-US.|



but clover has only

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 00 |en-US.|

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes
------------------------------------------------------------------------------
000000: 65 6e 2d 55 53 3b 6a 61 2d 4a 50 3b 66 72 2d 46 |en-US;ja-JP;fr-F|
000010: 52 3b 6b 6f 2d 4b 52 00 |R;ko-KR.|

------------------------------------------------------------------------------

does it effect lang issue after update?

thanks in advance.

 

EDIT1.

my friend's real MBP11,5 has 

<key>prev-lang:kbd</key>

<data>

a286MjUy

</data>

 

and

------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang
------------------------------------------------------------------------------
000000: 65 6e 67                                         |eng|
 
------------------------------------------------------------------------------
8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes
------------------------------------------------------------------------------
000000: 65 6e 67                                         |eng|
 
there are not PlatformLang/PlatformLangCodes

Share this post


Link to post
Share on other sites

report lang issue to dev.

i reported this issue before

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2565871

i traced this issue point. but not sure. I just want to report this point.

https://sourceforge.net/p/cloverefiboot/code/4414/tree/rEFIt_UEFI/Platform/DataHubCpu.c#l213

but surely effect lang after update with osxaptiofixv2+emul+ko set(config).

 

but if use osxaptiofixv3 or aptiomemoryfix without emul, what i mentioned above presents lang issue(ko+eng)

i checked this is OS X's business. so i checked realmac nvram dump.

 

realmac has this nvram vals

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang

------------------------------------------------------------------------------

000000: 65 6e 67 00 |eng.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes

------------------------------------------------------------------------------

000000: 65 6e 67 00 |eng.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 00 |en-US.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 00 |en-US.|

 

 

 

but clover has only

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLang

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 00 |en-US.|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:PlatformLangCodes

------------------------------------------------------------------------------

000000: 65 6e 2d 55 53 3b 6a 61 2d 4a 50 3b 66 72 2d 46 |en-US;ja-JP;fr-F|

000010: 52 3b 6b 6f 2d 4b 52 00 |R;ko-KR.|

 

------------------------------------------------------------------------------

 

does it effect lang issue after update?

 

thanks in advance.

 

EDIT1.

my friend's real MBP11,5 has 

<key>prev-lang:kbd</key>

<data>

a286MjUy

</data>

 

and

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Lang

------------------------------------------------------------------------------

000000: 65 6e 67                                         |eng|

 

------------------------------------------------------------------------------

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:LangCodes

------------------------------------------------------------------------------

000000: 65 6e 67                                         |eng|

 

 

there are not PlatformLang/PlatformLangCodes

 

Apple uses a modified EFI 1.10 firmware so it probably never updated from previous protocols those variables are deprecated variables in UEFI:

Lang      NV, BS, RT The language code that the system is configured for. This value is deprecated.
LangCodes BS, RT     The language codes that the firmware supports. This value is deprecated.
Lang has been deprecated. If the platform supports this variable, it must map any changes in the Lang variable into PlatformLang in the appropriate format.
[LangCodes] has been deprecated. If the platform supports this variable, it must map any changes in the [LangCodes] variable into [PlatformLangCodes] in the appropriate format.
*I made some corrections to what seem like obvious mistakes in the specification language

PlatformLang and PlatformLangCodes use RFC 4646, where Lang and LangCodes use ISO 639-2. But none the less, we should set them if they are not present.

Share this post


Link to post
Share on other sites

Apple uses a modified EFI 1.10 firmware so it probably never updated from previous protocols those variables are deprecated variables in UEFI:

Lang      NV, BS, RT The language code that the system is configured for. This value is deprecated.LangCodes BS, RT     The language codes that the firmware supports. This value is deprecated.
Lang has been deprecated. If the platform supports this variable, it must map any changes in the Lang variable into PlatformLang in the appropriate format.[LangCodes] has been deprecated. If the platform supports this variable, it must map any changes in the [LangCodes] variable into [PlatformLangCodes] in the appropriate format.*I made some corrections to what seem like obvious mistakes in the specification language
PlatformLang and PlatformLangCodes use RFC 4646, where Lang and LangCodes use ISO 639-2. But none the less, we should set them if they are not present.
Thanks. So how can i test? Just add lang and lang code?

Current, pre-lang:kbd nvram key effects system lang after update. Because aptiofixv2+emu combination is no problem.

 

Does it equal pre-lang:kbd and lang?

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Thanks. So how can i test? Just add lang and lang code?

 

Yeah, just add them. But you have to use ISO 639-2, so they are different language codes. Lang and LangCodes are firmware variables, they are almost surely not supported by almost all UEFI firmware, so you'd have to still set the others still too. This probably means that it might not be able to find some protocols that relied on this language code format because they have been switched to work with RFC4646 and PlatformLang(Codes). Like EFI_UNICODE_COLLATION_PROTOCOL...

 

Current, pre-lang:kbd nvram key effects system lang after update. Because aptiofixv2+emu combination is no problem.

 

Does it equal pre-lang:kbd and lang?

 

No, that is an Apple GUID variable, that should get set by setting a keyboard and language in system preferences (or when you do that during install). Did you remember to apply all the variables from your nvram.plist to your native NVRAM after removing EmuVar?

Share this post


Link to post
Share on other sites

Yeah, just add them. But you have to use ISO 639-2, so they are different language codes. Lang and LangCodes are firmware variables, they are almost surely not supported by almost all UEFI firmware, so you'd have to still set the others still too. This probably means that it might not be able to find some protocols that relied on this language code format because they have been switched to work with RFC4646 and PlatformLang(Codes). Like EFI_UNICODE_COLLATION_PROTOCOL...

 

 

No, that is an Apple GUID variable, that should get set by setting a keyboard and language in system preferences (or when you do that during install). Did you remember to apply all the variables from your nvram.plist to your native NVRAM after removing EmuVar?

Thank you for info. Yes. I checked it with several test times. I removed EmuVar+osaptiofixv2 and rcscript and nvram.plist. then sudo nvram -c. And check nvram -p until update beta. Then put osxaptiofixv3 or aptiomemoryfix in driver64uefi folder, then update beta. Then i found lang issue of reboot windows.

 

So, i just saw difference between emul+fixv2+ko(config) and (fixv3 or memoryfix). Just there is whethe pre-lang:kdb exist. Iike you said before, this key osx business(recorded in code). I didn't understand. It means what. So i compared my nvram dump and realmac from darwindump tool to close to problem.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

I just got the same issue you have after I deleted src folder for second time to see if I got your issue and I did. I did a ping test to both repo's edk and clover and it returned results so that means there is internet access.

 I then manually tried svn up the clover directory and it updated to 4415 so it must be something in the script. maybe the way it checks for the revisions accessing sourcrforge changed.

 I also noticed that because of the issue it did not check for aptiofix updates

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
×