Jump to content
ErmaC

Clover General discussion

21,098 posts in this topic

Recommended Posts

Guys, I'm still having problems with boot chime :cry:  I can only select AMD HDMI and Intel HDMI without freeze. Whenever I want to change my audio output to ALC1150 (any output), whole GUI freezes and no value is written to NVRAM. Since newer Clover revisions use different way of saving NVRAM value, BootChimeCfg is no longer working also. Tested on 4870, 4871 and 4876. 

Share this post


Link to post
Share on other sites
Advertisement

@arsradu

If you have FakeSMC and other critical kexts in SLE then you sure you can boot after OS update broking kext injection.

Anyway you need FakeSMC and LAN in Clover/kext folder to boot into Recovery.

So the logic is follow: let all kext to be in SLE and so in cache to speedup boot and for some troubles. But keep all kexts also in Other folder to boot into recovery or to OS Installer.

Then "Detect" has a sense to not inject kexts from "Other" if we have them in cache but do this in the case of clean cache (Recovery or Installer).

 

Anyway I see that double injection is not dangerous so we can always set Inject=YES.

10 hours ago, lisai9093 said:

For boot chime, is it possible to add USB speaker support? My desktop use USB speaker as the only output

I don't know how.

10 hours ago, bidero said:

Guys, I'm still having problems with boot chime :cry:  I can only select AMD HDMI and Intel HDMI without freeze. Whenever I want to change my audio output to ALC1150 (any output), whole GUI freezes and no value is written to NVRAM. Since newer Clover revisions use different way of saving NVRAM value, BootChimeCfg is no longer working also. Tested on 4870, 4871 and 4876. 

I have no such issue with my ALC1150.

Share this post


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

@arsradu

If you have FakeSMC and other critical kexts in SLE then you sure you can boot after OS update broking kext injection.

Anyway you need FakeSMC and LAN in Clover/kext folder to boot into Recovery.

So the logic is follow: let all kext to be in SLE and so in cache to speedup boot and for some troubles. But keep all kexts also in Other folder to boot into recovery or to OS Installer.

Then "Detect" has a sense to not inject kexts from "Other" if we have them in cache but do this in the case of clean cache (Recovery or Installer).

 

Anyway I see that double injection is not dangerous so we can always set Inject=YES.

I don't know how.

I have no such issue with my ALC1150.

Hi Slice,

 

can you please separate the boot chime from theme loading, so we can use boot chime while GUI->Fast is set to "true"?

Share this post


Link to post
Share on other sites
On 2/11/2019 at 5:02 PM, arsradu said:

 

To me, this is not efficient. One reason being that you're basically doubling your kexts. :))

 

 

Not sure what kind of error checking is kextcache doing in this case. So I'm not gonna say anything on that. Maybe people with more experience and knowledge can comment on that.

 

 

Are you a kext developer? If not...I don't see the benefit from your point of view.

 

 

True that. But...once again, are you using any of those kexts? Cause...I don't. At least not anymore.

 

 

I'm not sure what was the idea behind this implementation, but I can tell you it served me very well over the years, and not just for installer/recovery. Actually, I've had more issues placing kexts in S/L/E than having them in Clover/kexts/Other. It might be (probably is) a very subjective point of view, but...I don't know. To me, it's a lot easier to drag and drop my kexts into Clover/kext/Other than fiddling with S/L/E's permissions and all that. Call me lazy, but I prefer spending my time actually using my computer, than trying to get it to work. So...I do appreciate the simplicity and the convenience that Clover's implementation brings to this. :) 

 

 

And still, you seem to prefer having two sets of kexts, one updated, one not, instead of having them all in one place, and up to date. How is that gonna bring you less problems? :))

 

 

It might be less native, and "non-Mac", but then again, a lot of the hackintoshing is. And, I personally haven't noticed any difference in day-to-day use between having those kexts in S/L/E rather than having them in Clover/kexts. And I think the benefits of this implementation overweigh the lack of realism.

 

Again, just my opinion. And also, not trying to cause any discussions or so. :)) Just...sharing my opinion on the points you laid out. Simply because I think difference of opinion (done right) can start a very nice and fruitful conversation. And it can lead to progress, on both sides.

 

I can agree on all your point. I'm using some of the kext that don't work in clover folder so i should kextcache my kernel anyway .

After a while you will be used to install kext in /L/E . I don't use any app to do that. Just the terminal and some command line . So i guess it's very subjective but thanks for the discussion

 

Mattia

Share this post


Link to post
Share on other sites

Minor issue related to Clover GUI; having a weird "tool_shell.png" appearance with UEFI, no problem with Legacy (SS: bottom left). Shell is still functional. Strange, it appears normal if booting from USB (UEFI). I use Scan=true on config.plist - GUI #btw

screenshot0.png

Share this post


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

Minor issue related to Clover GUI; having a weird "tool_shell.png" appearance with UEFI, no problem with Legacy (SS: bottom left). Shell is still functional. Strange, it appears normal if booting from USB (UEFI). I use Scan=true on config.plist - GUI #btw

 

It may be a problem of File System of your EFI partition.

UEFI BIOS has quirky FAT32 driver. For this purpose I have Fat-64.efi in the Clover distribution. It works better.

Share this post


Link to post
Share on other sites

Hi there, 

I'm using the recently added Clover feature of playing sound on boot.

I was wondering if there is a problem with my config or I'm missing something, but when I boot with "Time-out=0" the boot Chime plays twice (the second is a little bit cut off).

Booting with "Time-out=1" plays the sound fine (but it's showing GUI).

I add the sound i'm using.

Thank you in advance.

sound.wav

Edited by pepitillo

Share this post


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

Hi there, 

I'm using the recently added Clover feature of playing sound on boot.

I was wondering if there is a problem with my config or I'm missing something, but when I boot with "Time-out=0" the boot Chime plays twice (the second is a little bit cut off).

Booting with "Time-out=1" plays the sound fine (but it's showing GUI).

I add the sound i'm using.

Thank you in advance.

sound.wav

I know this bug.

Share this post


Link to post
Share on other sites

r4877, report.

PlayAsync=TRUE, scan drive with play sound, then enter GUI. and i have a timeout 3, 3 -> 2 -> 1. automatically enter macos. there is no loop sound.

PlayAsync=TRUE, scan drive with play sound, then enter GUI. and i have a timeout 3, 3 -> 2 -> "enter key". enter macos. there is loop sound until boot macos.

 

thanks in advance

Edited by Sherlocks

Share this post


Link to post
Share on other sites
On 2/13/2019 at 1:12 AM, bidero said:

Guys, I'm still having problems with boot chime :cry:  I can only select AMD HDMI and Intel HDMI without freeze. Whenever I want to change my audio output to ALC1150 (any output), whole GUI freezes and no value is written to NVRAM. Since newer Clover revisions use different way of saving NVRAM value, BootChimeCfg is no longer working also. Tested on 4870, 4871 and 4876. 

I have same problem on my rig. I got ALC1150 too.

Share this post


Link to post
Share on other sites

Hello people.

 

During the last days, I experience a strange behavior with boot sequence, and I'd be grateful if you gurus can help me.

First of all, my system:

Gigabyte Z390 Aorus pro, i9 9900K, Samsung 970 Evo, AMD Vega 64

This system installed fine and worked as expected.

 

*But*, due to some issues with my Windows installation, I had to flash my BIOS to the latest version, and to fiddle around with the system. Then, at some time, when I tried to boot to OSX, although booting started and everything seemed to work fine, just after booting, instead of displaying the login screen, an inner square appears, just like the screenshot. (Actually this was taken when tried to boot in safe mode, when I try to boot regularly, there is either a dark square where this square is, or garbage, or green color). As you can see here, even the mouse pointer is visible (and movable).

 

The strange thing is, if I boot from my USB stick, using the EXACT files, as from my HD EFI partition, the system boots perfectly! So, if I use the stick to load Clover, it properly initializes visuals, if I use the disk to load Clover, it fails.


This drives me mad, and I can't find any logic in this, or how to debug it.

 

Please help!

 

(PS: I hope this is the correct thread!)

 

IMG_20190211_200556.jpg

Share this post


Link to post
Share on other sites

@Teras: Are you using UEFI boot from both the HDD and the USB stick?  If using legacy boot on one of them, you get a completely different UEFI bios, which could explain the difference.  Also, note that when booting legacy Clover, it sometimes picks up CloverX64.efi from a different disk (!) if multiple copies exist - because the search algorithm of boot6/boot7 does not know which disk it was loaded from.

Share this post


Link to post
Share on other sites
12 hours ago, Teras said:

Hello people.

 

During the last days, I experience a strange behavior with boot sequence, and I'd be grateful if you gurus can help me.

First of all, my system:

Gigabyte Z390 Aorus pro, i9 9900K, Samsung 970 Evo, AMD Vega 64

This system installed fine and worked as expected.

 

*But*, due to some issues with my Windows installation, I had to flash my BIOS to the latest version, and to fiddle around with the system. Then, at some time, when I tried to boot to OSX, although booting started and everything seemed to work fine, just after booting, instead of displaying the login screen, an inner square appears, just like the screenshot. (Actually this was taken when tried to boot in safe mode, when I try to boot regularly, there is either a dark square where this square is, or garbage, or green color). As you can see here, even the mouse pointer is visible (and movable).

 

The strange thing is, if I boot from my USB stick, using the EXACT files, as from my HD EFI partition, the system boots perfectly! So, if I use the stick to load Clover, it properly initializes visuals, if I use the disk to load Clover, it fails.


This drives me mad, and I can't find any logic in this, or how to debug it.

 

Please help!

 

(PS: I hope this is the correct thread!)

 

That looks like a piece of the default Mojave wallpaper. So that means you're probably reaching Desktop. Now, I've never seen this issue before. My guess is that something has to be different between your Clover USB drive and your HDD/SSD EFI. Something you might have missed. Either Clover is not the same version, not installed the same way (legacy vs UEFI mode), maybe kexts are not the same versions, drivers are not exactly the same... I don't know. But that would be my opinion on this issue so far.

 

If you want, you can remove sensitive serials from your SMBIOS and upload both the EFI folder on your USB and the one on your SSD/HDD. Also, although I think your BIOS might have already done that after flashing, you can try setting it to Optimised Defaults again and see if that helps. Also, just for testing, you can always put back the old BIOS and see if that changes anything. If not, then it's not the actual BIOS. It's gotta be something else. Personally I'm not sure it's Clover related. Probably not. But as I said, you can upload both so we can take a look.

 

Also, in case you haven't already done that, you can mount both your USB EFI partition and your HDD/SSD EFI partition and copy-paste everything (make sure you're not merging anything in the process) from one place to the other.

 

But before that, let's have a look at the current setup. :) 

Edited by arsradu

Share this post


Link to post
Share on other sites
16 hours ago, Teras said:

Hello people.

 

During the last days, I experience a strange behavior with boot sequence, and I'd be grateful if you gurus can help me.

First of all, my system:

Gigabyte Z390 Aorus pro, i9 9900K, Samsung 970 Evo, AMD Vega 64

This system installed fine and worked as expected.

 

*But*, due to some issues with my Windows installation, I had to flash my BIOS to the latest version, and to fiddle around with the system. Then, at some time, when I tried to boot to OSX, although booting started and everything seemed to work fine, just after booting, instead of displaying the login screen, an inner square appears, just like the screenshot. (Actually this was taken when tried to boot in safe mode, when I try to boot regularly, there is either a dark square where this square is, or garbage, or green color). As you can see here, even the mouse pointer is visible (and movable).

 

The strange thing is, if I boot from my USB stick, using the EXACT files, as from my HD EFI partition, the system boots perfectly! So, if I use the stick to load Clover, it properly initializes visuals, if I use the disk to load Clover, it fails.


This drives me mad, and I can't find any logic in this, or how to debug it.

 

Please help!

 

(PS: I hope this is the correct thread!)

 

IMG_20190211_200556.jpg

 

As @arsradu copy EFI folder from USB stick to EFI Folder on your HDD. Before that, you can recreate EFI partition on your hard disk, maybe corrupted

  1. Boot on USB
  2. go to Terminal
  3. diskutil list

    newfs_msdos -v EFI -F 32 /dev/rdisk0s1 (for example)

More experienced users may have a better solution than me

 

Share this post


Link to post
Share on other sites

You should provide a video of the verbose mode output, or just see if it is printing that output and then going to the desktop. Also I would actually recommend that you just run the clover installer again and then put you config, drivers, and kexts from your usb. You may not have been using UEFI mode to boot from the usb. It's hard to tell really you gave very limited information.

Share this post


Link to post
Share on other sites

@Badruzeus: I think it's a typo.  Remove the offending line

diff a/rEFIt_UEFI/Platform/HdaCodecDump.c b/rEFIt_UEFI/Platform/HdaCodecDump.c
--- a/rEFIt_UEFI/Platform/HdaCodecDump.c
+++ b/rEFIt_UEFI/Platform/HdaCodecDump.c
@@ -404,7 +404,6 @@ EFI_STATUS SaveHdaDumpBin() {
                        }
                }
                
-               CodecAddress;
                Status = HdaIo->GetAddress(HdaIo, &CodecAddress);
                
                CopyMem(HdaCodec.Header, hdcID, 4);

 

Share this post


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

@Badruzeus: I think it's a typo.  Remove the offending line



diff a/rEFIt_UEFI/Platform/HdaCodecDump.c b/rEFIt_UEFI/Platform/HdaCodecDump.c --- a/rEFIt_UEFI/Platform/HdaCodecDump.c +++ b/rEFIt_UEFI/Platform/HdaCodecDump.c @@ -404,7 +404,6 @@ EFI_STATUS SaveHdaDumpBin() { } } - CodecAddress; Status = HdaIo->GetAddress(HdaIo, &CodecAddress); CopyMem(HdaCodec.Header, hdcID, 4);

It works, many thanks. Codec Dump'ed successfully either using "F8" > \efi\clover\misc.

Screenshot 23.png

EFI-r4886.zip

misc_r4886_preboot_CodecDump.zip

Share this post


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

@Badruzeus: I think it's a typo.  Remove the offending line


diff a/rEFIt_UEFI/Platform/HdaCodecDump.c b/rEFIt_UEFI/Platform/HdaCodecDump.c
--- a/rEFIt_UEFI/Platform/HdaCodecDump.c
+++ b/rEFIt_UEFI/Platform/HdaCodecDump.c
@@ -404,7 +404,6 @@ EFI_STATUS SaveHdaDumpBin() {
                        }
                }
                
-               CodecAddress;
                Status = HdaIo->GetAddress(HdaIo, &CodecAddress);
                
                CopyMem(HdaCodec.Header, hdcID, 4);

 

Really!

Before the commit I tested with VS2013 compilation and fix some warnings. This one is not a warning for VS!

Share this post


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

Thanks @Slice for the fix on commit 4887. :) All good now building Clover. Also, implementing that functionality right inside Clover was an awesome idea! Well done!

Credits to headkaze as well as explanations from him.

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 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!
×