Jump to content
ErmaC

Clover General discussion

21,098 posts in this topic

Recommended Posts

UEFI Shell tip:

 

It is important to be able to type a colon for file management purposes.  The only answer I've found is to use an older Mac wired keyboard.   Wired windows keyboards, wireless keyboards don't work.   The only solution for me was to use the full size wired Apple keyboard.

Edited by meaganmargaret

Share this post


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

UEFI Shell tip:

 

It is important to be able to type a colon for file management purposes.  The only answer I've found is to use an older Mac wired keyboard.   Wired windows keyboards, wireless keyboards don't work.   The only solution for me was to use the full size wired Apple keyboard.

What are you talking about?? I use Wired Windows Keyboard, and i can type "colon" in UEFI Shell

Edited by Andres ZeroCross

Share this post


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

UEFI Shell tip:

 

It is important to be able to type a colon for file management purposes.  The only answer I've found is to use an older Mac wired keyboard.   Wired windows keyboards, wireless keyboards don't work.   The only solution for me was to use the full size wired Apple keyboard.

 

Actually i use usb full apple keyboard and i can't type colon !

Share this post


Link to post
Share on other sites
On 5/4/2019 at 10:37 AM, Andres ZeroCross said:

What are you talking about?? I use Wired Windows Keyboard, and i can type "colon" in UEFI Shell

 

Well, it didn't for me.  It appears there's a bug in the UEFI shell in Clover, and there appears to be a wide variety of methods that work for some and not for others.  In fact, I had to be directly connected (no usb extension cable) via an Apple wired keyboard to a USB 2.0 port (and only USB 2.0) to get my keyboard to type this -> :  in the UEFI shell.

Edited by meaganmargaret

Share this post


Link to post
Share on other sites

I have a wireless usb 3.0 keyboard and have no problem in the shell. Try using one of the other shell variations. It may be a limitation of your firmware or the keyboard as well since the simple text input protocol doesn't have shift/alt/control/etc key support so it relies on the driver. If the driver doesn't properly check whether the shift key is pressed to alter the character that is retrieved from the keyboard then it will just use the character represented by the key scan code. The keyboard may also be to blame by having a different scan code for keys, especially if it is not an ANSI english keyboard.

 

EDIT: You can also try using either the ps2 keyboard driver from edk2, or the usb keyboard driver from clover or unmodified from edk2. Though if you are legacy booting you already have the clover modified one.

Edited by apianti

Share this post


Link to post
Share on other sites

Uhm...guys? Is this intended? Cause it looks like a bug to me... Looks like VBoxHfs-64.uefi is present as both Mandatory and non-mandatory driver.

 

My guess is that it should probably be removed from non-mandatory...?

 

Point is, I can't build Clover anymore due to that error. If there is something I've missed, please, let me know.

 

2115821658_Screenshot2019-05-06at13_19_17.png.1eee70800bcb751fe4e1f301009b3c2a.png

Edited by arsradu

Share this post


Link to post
Share on other sites
On 5/6/2019 at 12:19 PM, arsradu said:

Uhm...guys? Is this intended? Cause it looks like a bug to me... Looks like VBoxHfs-64.uefi is present as both Mandatory and non-mandatory driver.

 

My guess is that it should probably be removed from non-mandatory...?

 

Point is, I can't build Clover anymore due to that error. If there is something I've missed, please, let me know.

 

2115821658_Screenshot2019-05-06at13_19_17.png.1eee70800bcb751fe4e1f301009b3c2a.png

 

 

I don't have this problem with both edk2 and udk2018 script. Which one do you use?

Share this post


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

I don't have this problem with both edk2 and udk2018 script. Which one do you use?

 

Well, the same one I've always used (attached)... And I'm using UDK2018. Not sure what changed and where. Which one are you using? :)) Also, is this with a clean environment?

CloverNew

Edited by arsradu

Share this post


Link to post
Share on other sites

I see no problem

total 43360
drwxr-xr-x  13 sergey  staff      442 May  7 21:28 .
drwxr-xr-x  15 sergey  staff      510 May  7 21:28 ..
drwxr-xr-x   5 sergey  staff      170 May  7 21:28 CloverCD
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 CloverISO-4928
-rw-r--r--   1 sergey  staff  2882689 May  7 21:28 CloverISO-4928.tar.lzma
-rw-r--r--@  1 sergey  staff  9467800 May  7 21:28 Clover_v2.4k_r4928.pkg
-rw-r--r--   1 sergey  staff       68 May  7 21:28 Clover_v2.4k_r4928.pkg.md5
-rw-r--r--   1 sergey  staff  9385613 May  7 21:28 Clover_v2.4k_r4928.zip
drwxr-xr-x   3 sergey  staff      102 May  7 21:26 Resources
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 build
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 i386
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 package
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 utils
done!

 

Share this post


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

I see no problem


total 43360
drwxr-xr-x  13 sergey  staff      442 May  7 21:28 .
drwxr-xr-x  15 sergey  staff      510 May  7 21:28 ..
drwxr-xr-x   5 sergey  staff      170 May  7 21:28 CloverCD
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 CloverISO-4928
-rw-r--r--   1 sergey  staff  2882689 May  7 21:28 CloverISO-4928.tar.lzma
-rw-r--r--@  1 sergey  staff  9467800 May  7 21:28 Clover_v2.4k_r4928.pkg
-rw-r--r--   1 sergey  staff       68 May  7 21:28 Clover_v2.4k_r4928.pkg.md5
-rw-r--r--   1 sergey  staff  9385613 May  7 21:28 Clover_v2.4k_r4928.zip
drwxr-xr-x   3 sergey  staff      102 May  7 21:26 Resources
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 build
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 i386
drwxr-xr-x   3 sergey  staff      102 May  7 21:28 package
drwxr-xr-x   6 sergey  staff      204 May  7 21:27 utils
done!

 

 

Yeah, everything looks fine in your case. 

 

Then it's probably just me... But I can't figure out what am I missing here... It's the same script I've always used. And this is actually the first time I'm encountering this issue...

 

Hmm... which Xcode version are you using? Are you still on High Sierra?

 

I doubt this is an Xcode issue... But then again, we've seen many weird issues in the past that were caused by that. So, I wouldn't be surprised if this is another one of those cases. Right now, I'm on Xcode 10.2.1.

 

If you think it could be Xcode, I can try to get an older version (such as 10.1) and see if that still occurs.

 

Also, I think it might be interesting to see how does it work if I'm trying to force it to build a specific version. Such as 4921 for example. Same environment, of course. Same Xcode. Just a different revision.

 

I'll let you know. :)

Edited by arsradu

Share this post


Link to post
Share on other sites

Fine here

11 minutes ago, arsradu said:

Then it's probably just me... But I can't figure out what am I missing here

Is bash the stock one?

echo $BASH_VERSION

result:

3.2.57(1)-release

 

Edited by vector sigma

Share this post


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

Fine here

Is bash the stock one?


echo $BASH_VERSION

 result:


3.2.57(1)-release

 

 

 

Same here.

 

1945849698_Screenshot2019-05-07at21_51_19.thumb.png.9f7fa4412facbcba853d11ce46e43d6f.png

 

Also, I can build 4291 just fine. I'll try 4293... Maybe there's something in that commit that it doesn't like.

 

One thing I've noticed with build 4291. The name is different.

676635730_Screenshot2019-05-07at21_53_15.thumb.png.91cb48a067c74fcb69f2929a4e6e385a.png

 

Edited by arsradu

Share this post


Link to post
Share on other sites
6 minutes ago, vector sigma said:

Using USE_APPLE_HFSPLUS_DRIVER?

 

Bingo! Indeed, I am using HFSPlus. But...does it check for that before it makes the build? Cause it didn't seem to do that with previous versions. Is this something new?

 

Also, 4923 displays the same error which seems to be caused by the same name... but I'm guessing it's not...caused by that? Since Slice was able to build the latest version with no issues?

 

I'm guessing there's something with commit 4923 that causes this. Maybe only when there's HFSPlus driver... But again, we're not talking about installing the build here. Just...creating it in the first place. If there's a check for that during this step, I wasn't aware of it. Of course, I could be wrong.

Edited by arsradu

Share this post


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

 

Bingo! Indeed, I am using HFSPlus. But...does it check for that before it makes the build? Cause it didn't seem to do that with previous versions. Is this something new?

This must be related to a very old commit, but anyway if you want use that functionality you have to ensure that 

Clover/FileSystems/HFSPlus/X64/HFSPlus.efi

exists :)

EDIT

probably VBoxHfs will be copied anyway and a change will be required, but this is another story.

Share this post


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

This must be related to a very old commit, but anyway if you want use that functionality you have to ensure that 


Clover/FileSystems/HFSPlus/X64/HFSPlus.efi

exists :)

 

Wait. I'm using HFSPlus in the sense that I've got it under Clover/CloverUEFIDrivers on the EFI partition. :)) Not that I'm using it to build Clover. That's what I was trying to say before. I wasn't aware that there's a function that checks what you have in your EFI folder before building Clover. :)) If there isn't, then this is not the case we're talking about.

 

And, as I said, building works perfectly fine with 4921, with the exact same setup.

Share this post


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

 

Wait. I'm using HFSPlus in the sense that I've got it under Clover/CloverUEFIDrivers on the EFI partition. :)) Not that I'm using it to build Clover. That's what I was trying to say before. I wasn't aware that there's a function that checks what you have in your EFI folder before building Clover. :)) If there isn't, then this is not the case we're talking about.

 

And, as I said, building works perfectly fine with 4921, with the exact same setup.

Doesn't check if exist in your ESP in fact, but we're not talking about building Clover?

I mean that if you pass -DUSE_APPLE_HFSPLUS_DRIVER ...it expect to find Clover/FileSystems/HFSPlus/X64/HFSPlus.efi... in the source code directory.. otherwise Vboxhfs will be copied..

Edited by vector sigma

Share this post


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

Doesn't check if exist in your ESP in fact, but we're not talking about building Clover?

 

We are. That's the thing. I don't want it to build Clover with HFSPlus already included. I can add it myself once it's built. I just want it to build it. :)) It doesn't matter what I have in ESP.

 

And looking at commit 4923 I'm guessing some of that might be causing some of the drivers to have a duplicated name...which might cause the error? I don't know. I might be talking stupid here. But...I don't see why it would show that error with build 4923 (which it does indeed looks like it's trying to build two drivers with the same identical name) and not with 4921 (where it builds the VBoxHfs driver without the "-64" part). 

 

1764849128_Screenshot2019-05-07at22_19_26.thumb.png.763ed687ed4aa50106bec36d26f36f60.png

Share this post


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

 

We are. That's the thing. I don't want it to build Clover with HFSPlus already included. I can add it myself once it's built. I just want it to build it. :)) It doesn't matter what I have in ESP.

 

And looking at commit 4923 I'm guessing some of that might be causing some of the drivers to have a duplicated name...which might cause the error? I don't know. I might be talking stupid here. But...I don't see why it would show that error with build 4923 (which it does indeed looks like it's trying to build two drivers with the same identical name) and not with 4921 (where it builds the VBoxHfs driver without the "-64" part). 

 

1764849128_Screenshot2019-05-07at22_19_26.thumb.png.763ed687ed4aa50106bec36d26f36f60.png

Yes can be, but I though you find the culprit by using USE_APPLE_HFSPLUS_DRIVER. You said "Bingo" Lol

 

Share this post


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

Yes can be, but I though you find the culprit by using USE_APPLE_HFSPLUS_DRIVER. You said "Bingo" Lol

 

 

Misunderstanding on my side... And lucky coincidence, I guess...? :))) Cause I actually do have HFSPlus in ESP.

 

Sorry, my bad. :) I hope it's all clear now. At least for this part of the problem. :))

Share this post


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

 

Misunderstanding on my side... And lucky coincidence, I guess...? :))) Cause I actually do have HFSPlus in ESP.

 

Sorry, my bad. :) I hope it's all clear now. At least for this part of the problem. :))

Found the problem, and is not a problem with Clover. Go there: https://github.com/acidanthera/AppleSupportPkg/releases

and download latest release.... it contains VBoxHfs.efi:hysterical::hysterical:

512366948_Schermata2019-05-07alle21_35_34.png.78461de2fe891902f483c40065a4285e.png

Share this post


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

Found the problem, and is not a problem with Clover. Go there: https://github.com/acidanthera/AppleSupportPkg/releases

and download latest release.... it contains VBoxHfs.efi:hysterical::hysterical:

Nooo waaay, Huawei. :))

 

Yeah, that explains it... And because I'm downloading the drivers with "--ext-pre" ...there it is another one. So...there's one from Clover and one from AppleSupportPkg? Uhm...oook... Is that intended? :)) It still doesn't feel quite ok to me.

 

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