Jump to content
ErmaC

Clover General discussion

21,091 posts in this topic

Recommended Posts

Advertisement

About my GT 520 HDMI "HdaCodec#0 (NVIDIA (Unknown))" is it because 0x10DE001C already taken by GT610?

Can a same Device ID used by 2 different Audio models? Thanks.

Edited by Badruzeus

Share this post


Link to post
Share on other sites

Hi

 

Commit r4887: my question may be stupid: audiodxe must be installed to press F8 and get  HdacodecDump in misc folder? Right.

 

Thanks

 

Sorry for my bad english

Share this post


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

Commit r4887: my question may be stupid: audiodxe must be installed to press F8 and get  HdacodecDump in misc folder? Right.

No, it does not require any additional files.. Yes you require AudioDxe-64.efi installed in CLOVER/drivers64UEFI.

 

Note that there is some sort of bug with the filename creation. Hopefully it can be fixed soon.

Edited by headkaze

Share this post


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

No, it does not require any additional files.

 

Note that there is some sort of bug with the filename creation. Hopefully it can be fixed soon.

 

Thanks for your reply. Actually, I don't use audiodxe, there is no HdacodecDump file when I press F8 on my system.

Share this post


Link to post
Share on other sites

Has anyone been able to use clover to boot into Windows USB installer? On the selection screen, I can see the "Windows EFI" partition. Selecting this then displays "Press any key to continue booting from CD/DVD". Pressing any key just gives me a blank screen. If I boot into the Windows EFI directly instead of Clover, the installation process is normal.

 

Both Clover and Windows are UEFI boot.

 

The reason why I'm doing this is that I'm trying to install Windows to an NVMe card (connected to a PCIe slot) that's installed in a PC that doesn't support NVMe natively. I'm trying to use Clover as a frontend. I've also used Clover as a frontend to OSX that's installed on an NVMe card on a PC that also has no support for NVMe natively.

 

Thanks

Edited by mrjayviper

Share this post


Link to post
Share on other sites
4 hours ago, mrjayviper said:

Has anyone been able to use clover to boot into Windows USB installer? On the selection screen, I can see the "Windows EFI" partition. Selecting this then displays "Press any key to continue booting from CD/DVD". Pressing any key just gives me a blank screen. If I boot into the Windows EFI directly instead of Clover, the installation process is normal.

 

Both Clover and Windows are UEFI boot.

 

The reason why I'm doing this is that I'm trying to install Windows to an NVMe card (connected to a PCIe slot) that's installed in a PC that doesn't support NVMe natively. I'm trying to use Clover as a frontend. I've also used Clover as a frontend to OSX that's installed on an NVMe card on a PC that also has no support for NVMe natively.

 

Thanks

 

Do you try to boot directly into Windows USB Installer? and boot into Clover after Windows installation completed!

Share this post


Link to post
Share on other sites

Hi guys,

 

Any idea what's up with this? Worked fine yesterday when building 4888. But now, I get this. And of course, no drivers for AptioMemoryFix and AppleUiSupport in the installer. I'm curious why unknown version though. I doubt this is somehow Clover related, since it worked yesterday, with revision 4888. And although now we're at 4889, I don't think the changes in HdaCodecDump.c would cause third party drivers to be skipped. Still, I'm wondering what could cause this.

 

1638646456_Screenshot2019-02-28at11_41_54.png.8850a4bc349a82bd828633f8430cb95e.png

Edited by arsradu

Share this post


Link to post
Share on other sites
37 minutes ago, arsradu said:

Hi guys,

 

Any idea what's up with this? Worked fine yesterday when building 4888. But now, I get this. And of course, no drivers for AptioMemoryFix and AppleUiSupport in the installer. I'm curious why unknown version though. I doubt this is somehow Clover related, since it worked yesterday, with revision 4888. And although now we're at 4889, I don't think the changes in HdaCodecDump.c would cause third party drivers to be skipped. Still, I'm wondering what could cause this.



1638646456_Screenshot2019-02-28at11_41_54.png.8850a4bc349a82bd828633f8430cb95e.png

 

No issue here, I'm using UDK and build with ./ebuild.sh -fr or --ext-co -fr, both worked fine.

Spoiler

Last login: Thu Feb 28 17:14:53 on ttys000
MacBook-Pro:~ badruzeus$ cd ~/udk/UDK2018/
MacBook-Pro:UDK2018 badruzeus$ svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover
U    Clover/rEFIt_UEFI/Platform/HdaCodecDump.c
Checked out revision 4889.
MacBook-Pro:UDK2018 badruzeus$ cd Clover
MacBook-Pro:Clover badruzeus$ ./ebuild.sh -fr
TOOLCHAIN_DIR: /Users/badruzeus/udk/UDK2018/Clover/../../opt/local
MTOC_PREFIX: /usr/local/bin/
NASM_PREFIX: /opt/local/bin/
NASM_VER: 2.14.02
Initializing workspace
Loading previous configuration from /Users/badruzeus/udk/UDK2018/Conf/BuildEnv.sh
WORKSPACE: /Users/badruzeus/udk/UDK2018
EDK_TOOLS_PATH: /Users/badruzeus/udk/UDK2018/BaseTools
CONF_PATH: /Users/badruzeus/udk/UDK2018/Conf

Running edk2 build for CloverX64 using the command:
build  -D USE_LOW_EBDA -D HAVE_LEGACY_EMURUNTIMEDXE -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 5 

Build environment: Darwin-15.6.0-x86_64-i386-64bit
Build start time: 17:16:55, Feb.28 2019

WORKSPACE        = /Users/badruzeus/udk/UDK2018
ECP_SOURCE       = /Users/badruzeus/udk/UDK2018/EdkCompatibilityPkg
EDK_SOURCE       = /Users/badruzeus/udk/UDK2018/EdkCompatibilityPkg
EFI_SOURCE       = /Users/badruzeus/udk/UDK2018/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/badruzeus/udk/UDK2018/BaseTools
CONF_PATH        = /Users/badruzeus/udk/UDK2018/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = /Users/badruzeus/udk/UDK2018/Clover/Clover.dsc
Flash Image Definition   = /Users/badruzeus/udk/UDK2018/Clover/Clover.fdf

Processing meta-data ................ done!
...
(Cencored)
...
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/AppleImageCodec/AppleImageCodec.inf [X64]
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/AppleUITheme/AppleUITheme.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/HashServiceFix/HashServiceFix.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/AppleKeyAggregator/AppleKeyAggregator.inf [X64]
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/AppleKeyFeeder/AppleKeyFeeder.inf [X64]
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/DumpUefiCalls/DumpUefiCalls.inf [X64]
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/OsxFatBinaryDrv/OsxFatBinaryDrv.inf [X64]
Building ... /Users/badruzeus/udk/UDK2018/Clover/Protocols/EmuVariableUefi/EmuVariableRuntimeDxe.inf [X64]
make: Nothing to be done for `tbuild'.
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/Drivers/AudioDxe/AudioDxe.inf [X64]
Building ... /Users/badruzeus/udk/UDK2018/Clover/bdmesg_efi/bdmesg.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/ShellPkg/Application/Shell/Shell.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/rEFIt_UEFI/refit.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/OsxAptioFixDrv/OsxAptioFixDrv.inf [X64]
make: Nothing to be done for `tbuild'.
Building ... /Users/badruzeus/udk/UDK2018/Clover/OsxAptioFixDrv/OsxAptioFix3Drv.inf [X64]
[CC] EfiLoader
[CC] OsxAptioFix3Drv
[CC] BdsEntry
[CC] OsxAptioFixDrv
[CC] main
[SLINK] EfiLoader
[SLINK] OsxAptioFixDrv
[SLINK] OsxAptioFix3Drv
[SLINK] BdsDxe
[DLINK1] EfiLoader
[DLINK1] OsxAptioFix3Drv
[DLINK1] OsxAptioFixDrv
[DLINK1] BdsDxe
[MTOC] OsxAptioFix3Drv
[MTOC] OsxAptioFixDrv
[MTOC] EfiLoader
[MTOC] BdsDxe
[GENFW] EfiLoader
[GENFW] OsxAptioFixDrv
Building ... /Users/badruzeus/udk/UDK2018/Clover/OsxLowMemFixDrv/OsxLowMemFixDrv.inf [X64]
[GENFW] OsxAptioFix3Drv
[GENFW] BdsDxe
[CC] menu
[CC] OsxLowMemFixDrv
[SLINK] OsxLowMemFixDrv
[DLINK1] OsxLowMemFixDrv
[MTOC] OsxLowMemFixDrv
[GENFW] OsxLowMemFixDrv
[CC] HdaCodecDump
[SLINK] CLOVER
[DLINK1] CLOVER
[MTOC] CLOVER
[GENFW] CLOVER

Generating DUETEFIMAINFVX64 FV
###
GUID cross reference file can be found at /Users/badruzeus/udk/UDK2018/Build/Clover/RELEASE_XCODE8/FV/Guid.xref

FV Space Information
DUETEFIMAINFVX64 [42%Full] 2752512 total, 1181720 used, 1570792 free

- Done -
Build end time: 17:17:37, Feb.28 2019
Build total time: 00:00:42

Compressing DUETEFIMainFv.FV ...
Encoding
Compressing DxeCore.efi ...
Encoding
Compressing DxeIpl.efi ...
Encoding
Generate Loader Image ...
Created /Users/badruzeus/udk/UDK2018/Build/Clover/RELEASE_XCODE8/FV/Efildr64
warning: boot file bigger than low-ebda permits, switching to --std-ebda
943+0 records in
943+0 records out
482816 bytes transferred in 0.008226 secs (58694484 bytes/sec)
Copy CloverEFI:
  -> boot6
Changing byte at 0xa9 of boot6 to show 6 as init message:
1+0 records in
1+0 records out
1 bytes transferred in 0.000029 secs (34664 bytes/sec)
  -> BOOTX64.efi
  -> CLOVERX64.efi
Copy Mandatory drivers:
  -> FSInject-64.efi
  -> XhciDxe-64.efi
  -> SMCHelper-64.efi
  -> AudioDxe-64.efi
  -> AppleImageCodec-64.efi
  -> AppleKeyAggregator-64.efi
  -> AppleUITheme-64.efi
  -> FirmwareVolume-64.efi
  -> FSInject-64.efi
  -> DataHubDxe-64.efi
  -> SMCHelper-64.efi
  -> AudioDxe-64.efi
  -> AppleImageCodec-64.efi
  -> AppleUITheme-64.efi
  -> AppleKeyAggregator-64.efi
  -> FirmwareVolume-64.efi
  -> VBoxHfs-64.efi
  -> GrubEXFAT-64.efi
  -> GrubISO9660-64.efi
  -> GrubNTFS-64.efi
  -> GrubUDF-64.efi
  -> AptioMemoryFix-64.efi
  -> AptioInputFix-64.efi
  -> AppleUISupport-64.efi
  -> ApfsDriverLoader-64.efi
  -> ApfsDriverLoader-64.efi
  -> AppleImageLoader-64.efi
  -> AppleImageLoader-64.efi
  -> CsmVideoDxe-64.efi
  -> EnglishDxe-64.efi
  -> EmuVariableUefi-64.efi
  -> Fat-64.efi
  -> NvmExpressDxe-64.efi
  -> OsxAptioFix3Drv-64.efi
  -> OsxAptioFixDrv-64.efi
  -> OsxFatBinaryDrv-64.efi
  -> OsxLowMemFixDrv-64.efi
  -> PartitionDxe-64.efi
  -> Ps2MouseDxe-64.efi
  -> UsbKbDxe-64.efi
  -> UsbMouseDxe-64.efi
  -> VBoxExt2-64.efi
  -> VBoxExt4-64.efi
  -> VBoxIso9600-64.efi
  -> AppleKeyFeeder-64.efi
  -> HashServiceFix-64.efi
Copy Applications:
  -> bdmesg.efi
  -> Shell64U.efi
Done!

Generating BootSectors
make: Nothing to be done for `all'.
Done! 

 

 

Share this post


Link to post
Share on other sites
22 minutes ago, Slice said:

It seems external server cancel to provide the files. So why I prefer to keep all sources in one repo.

 

I agree. At least if it fails, it fails for all. But, having some sources compile perfectly fine, while others are not, simply because they're not hosted in the same place...yeah, that can be problematic sometimes. Especially when there are important files that need to be compiled with those sources.

Share this post


Link to post
Share on other sites
Can anyone tell me what appleimageloader.kext is for ? Is it only for filevault ?

  For as far as I know AppleUiSupport is for FileVault. AppleImageLoader is something else.

 

According to the developer's description, it's a:

 

 

Secure AppleEfiFat binary driver with implementation of AppleLoadImage protocol with EfiBinary signature verification.

It provides secure loading of Apple EFI binary files into memory by pre-authenticating its signature.

  Also, it's been removed from AppleSupportPkg starting with version 2.0.5 until it gets Secure Boot compatibility.

 

1374496643_Screenshot2019-03-04at23_42_11.thumb.png.56928a5ecf3150a0272bfc5ba92b27b0.png

 

More info here.

 

 

Edited by arsradu

Share this post


Link to post
Share on other sites

Hi guys,

 

Whoever thought of making an EFI backup on the target disk was an absolute genius! That was a brilliant idea.

 

Now, I'm thinking of the following scenario:

Let's say you updated to the latest version of Clover and...for some reason, you can't boot anymore. And you don't have a USB drive with another version of Clover.

You still have access to the Clover UI, but you don't have access to the drivers folder for example (maybe that would be another useful feature), assuming you know that's where the issue resides. But regardless, you know you have a working backup on your target disk. So you can attempt to restore one of the previous versions.

 

Unfortunately...there is no easy way to do that. Or maybe there is and I'm making a total fool of myself writing this. :)) I mean, I guess you could boot in single-user mode and try to copy the content of your backup folder over the current one. Now, one thing I don't know...is whether or not, when you do this, it replaces everything...or adds to the current content. Cause that might cause more issues than it solves... Also, I don't know how many people know how to do this from command line in the first place.

 

So, the idea here is: would it be possible to have a feature to restore a backup of Clover (from the target partition) using the Clover UI itself (assuming you can boot into the UI of course)?

 

I mean, I'm thinking something like this:

  1. scan the target disk for available backups
  2. display the results
  3. let the user choose the one he thinks might be the most reliable one
  4. load that one and replace the current installation with that new/old one.

 

It's just an idea, but also an open discussion. And I would love to know your opinion on it. :) 

 

Alternatively...can we maybe just allow the user to select a backup to boot only that specific time? He can fix his current EFI installation once he gets back into the OS, I guess. Something similar to what we have right now for loading a backup config (another really useful feature). Only in this case, we're not loading only the config from EFI/Clover/Config, but loading the entire folder from EFI-Backups.

 

Maybe I'm missing something here and this idea won't work. Or at least in its current form. Nonetheless, I'd love to know your opinion.

 

Thanks guys!

 

Aaand keep up the good work. :)

Edited by arsradu

Share this post


Link to post
Share on other sites

Nah, you are mistaking the backup as an option to restore a broken or misconfigured installation without another boot mechanism. If you break booting clover you can only fix it by booting something else. There is no where else to really save backups, the ESP doesn't make sense because it may not have a reasonable amount of space for doing so. So, there are two options, and you always need a usb, either keep a working copy of clover (with the EFI shell) on a usb to use the EFI shell to restore or modify, or always test first on a usb. Also you can use a different operating system. Like I often mess up some code and clover will segfault or something, so I just boot directly into windows or linux from the firmware and fix it.

Share this post


Link to post
Share on other sites
4 minutes ago, apianti said:

Nah, you are mistaking the backup as an option to restore a broken or misconfigured installation without another boot mechanism. If you break booting clover you can only fix it by booting something else. There is no where else to really save backups, the ESP doesn't make sense because it may not have a reasonable amount of space for doing so. So, there are two options, and you always need a usb, either keep a working copy of clover (with the EFI shell) on a usb to use the EFI shell to restore or modify, or always test first on a usb. Also you can use a different operating system. Like I often mess up some code and clover will segfault or something, so I just boot directly into windows or linux from the firmware and fix it.

Thanks God, my AMI Aptio has `Launch EFI Shell from FS` option. Anyway, how to boot into *.iso that is placed on specific volume (if it' s possible)?

Share this post


Link to post
Share on other sites

I used to do this a few years back:

 

Install clover on both EFI & macOS partition. so if i break one, i have another one. macOS partition is booting as legacy in case UEFI breaks.

But, thats just me :D

 

 

 

Edited by ellaosx

Share this post


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

Hi guys,

 

Whoever thought of making an EFI backup on the target disk was an absolute genius! That was a brilliant idea.

 

Now, I'm thinking of the following scenario:

Let's say you updated to the latest version of Clover and...for some reason, you can't boot anymore. And you don't have a USB drive with another version of Clover.

You still have access to the Clover UI, but you don't have access to the drivers folder for example (maybe that would be another useful feature), assuming you know that's where the issue resides. But regardless, you know you have a working backup on your target disk. So you can attempt to restore one of the previous versions.

 

Unfortunately...there is no easy way to do that. Or maybe there is and I'm making a total fool of myself writing this. :)) I mean, I guess you could boot in single-user mode and try to copy the content of your backup folder over the current one. Now, one thing I don't know...is whether or not, when you do this, it replaces everything...or adds to the current content. Cause that might cause more issues than it solves... Also, I don't know how many people know how to do this from command line in the first place.

 

So, the idea here is: would it be possible to have a feature to restore a backup of Clover (from the target partition) using the Clover UI itself (assuming you can boot into the UI of course)?

 

I mean, I'm thinking something like this:

  1. scan the target disk for available backups
  2. display the results
  3. let the user choose the one he thinks might be the most reliable one
  4. load that one and replace the current installation with that new/old one.

 

It's just an idea, but also an open discussion. And I would love to know your opinion on it. :) 

 

Alternatively...can we maybe just allow the user to select a backup to boot only that specific time? He can fix his current EFI installation once he gets back into the OS, I guess. Something similar to what we have right now for loading a backup config (another really useful feature). Only in this case, we're not loading only the config from EFI/Clover/Config, but loading the entire folder from EFI-Backups.

 

Maybe I'm missing something here and this idea won't work. Or at least in its current form. Nonetheless, I'd love to know your opinion.

 

Thanks guys!

 

Aaand keep up the good work. :)


Just boot to windows, mount EFI partition and modify the EFI/CLOVER files

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

  • 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 MaLd0n
      ---TUTORIAL---
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Original Post--
      https://www.olarila.com/topic/6531-olarila-hackbeast-z390-designare-thunderbolt-full-dsdt-patches-clover-opencore/
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://www.olarila.com/topic/6364-mojave-catalina-on-mobos-series-100200300-with-opencore-bootloader/
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
×