Jump to content
8755 posts in this topic

Recommended Posts

38 minutes ago, Humanate said:

 

I have an i5 9400f so no onboard graphics to disable

 

So I did some experimenting, boot chime was enabled although I wasn't hearing it as I use a USB DAC, removed boot chime, much quicker now from BIOS OEM screen to Boot picker, excellent

 

I also removed all but essential kexts. Also improved boot time. Interestingly, I removed RadeonBoost.kext and ran Basemark GPU Benchmark - my score was 3677 with RadeonBoost and 4185 without, strange

 

One more question then that's it from me for today you'll be pleased to hear! The renaming thing you helped me with works perfectly but I'm now thinking I'll be better, if it's possible, to hide the duplicate Windows 10 drive (my backup clone). Reason is my wife mainly uses Windows for her work, if she clicks on the Win 10 clone it will just cause problems, so if I can hide it in Boot Picker that would be even better. Possible do you know?

 

Really appreciate your help

 

Hey! Oh, sorry about that. I thought all i5 CPUs come with integrated graphics. Well, one more thing I learned today. :)) 

 

I never heard of that RadeonBoost.kext and it looks like we're using the exact same GPU. Well, now I know what to avoid. :))

 

About hiding that specific drive....I feel like it might be possible... But I don't know how. And never done it before with OC. I mean, you can adjust ScanPolicy to exclude NTFS from scanning. But that means you won't be seeing either of the two drives anymore in boot picker. So that's not quite the expected result.

9 minutes ago, Tiem said:

A single line in Terminal:


echo "NAME" > /Volumes/EFI/EFI/Boot/.contentDetails

Change NAME to whatever you want. In this case "Windows 10 Pro"

 

Oh cool! I didn't know that. That is very useful. Thank you! :) 

Edited by arsradu
updated path

Updating to the latest Catalina beta 5 I got this:

OCUI: Entry kind 16 unsupported for IconOCB: ShowMenu failed - Unsupported
Halting on critical error

Restarted the install process and it completed the second time no issues. Using OC 0.5.9 build e7989ef

 

  • Confused 1
1 hour ago, Humanate said:

 

I have an i5 9400f so no onboard graphics to disable

 

So I did some experimenting, boot chime was enabled although I wasn't hearing it as I use a USB DAC, removed boot chime, much quicker now from BIOS OEM screen to Boot picker, excellent

 

I also removed all but essential kexts. Also improved boot time. Interestingly, I removed RadeonBoost.kext and ran Basemark GPU Benchmark - my score was 3677 with RadeonBoost and 4185 without, strange

 

One more question then that's it from me for today you'll be pleased to hear! The renaming thing you helped me with works perfectly but I'm now thinking I'll be better, if it's possible, to hide the duplicate Windows 10 drive (my backup clone). Reason is my wife mainly uses Windows for her work, if she clicks on the Win 10 clone it will just cause problems, so if I can hide it in Boot Picker that would be even better. Possible do you know?

 

Really appreciate your help

 

Fixed mine as well by removing the AudioDxe entry in my UEFI/Driver. Now boot picker shows instantly, well, 1 sec delay.

 

Is your Windows backup on a separate drive from your main Windows? Because if not, then I don't see it as a backup. Just doesn't make sense.

But if it is on a separate drive then one way to hide it is to disable it in your BIOS. Unless again, if you access it frequently.

Edited by insanefrancis
  • Like 1
On 4/30/2020 at 1:19 PM, droples said:

I slightly corrected your config. Using it, I booted onto Asus N53sv, OS x10.13.6,OC-0.5.8. Try it ....Archive.zip

THANK YOU!!!!

I can't stress this enough: Thank you!

 

But I now have one problem. I don't have keyboard of trackpad working. I see VoodooPS2Controller is loaded but it does nothing. The same kext works fine on Clover, but not on OpenCore. What could it be?

 

I have keyboard and trackpad working on OpenCore menu (I can use the cursor and the keyboard keys to move between entries) but not on the High Sierra installer or the actual partition I have.

 

EDIT: I had to explicitly declare the VoodooPS2 plugins in my config.plist now everything works fine. Thank you again!

Edited by el_charlie
4 hours ago, punjabigator said:

Fred, I have an OptiPlex 7040 (HD530, GT730) and unable to boot using the most recent open core. The clover it booting well. Would you mind sharing your config? Thanks

IMG_5295.jpg

 

 

Hi,

 

Here is attached config.plist I use with 7050, juste remove specific data injection for my Nvidia video and empty data in Generic plateforminfo.

I'm using a little tweak DSDT, maybe you should remove all what I drop in ACPI.

 

config.plist.zip

 

Fred 

9 hours ago, Download-Fritz said:

 

@MacNB HideSelf now works by detecting the OC boot file and discarding that entry, it does no longer refer to the source paritition specifically.

 

Thanks @Download-Fritz for the clarification.

OpenCanopy still displayed an EFI disk icon:IMG_1779.thumb.jpg.38b87d901893be6a1db3ca855e7e4c7f.jpg

 

But I figured out which drive that EFI was.

It was the EFI partition on the Mojave-SSD drive above that contains Clover :rolleyes:

 

Anyway to hide that (apart from deleting Clover) ?

 

4 hours ago, insanefrancis said:

 

Fixed mine as well by removing the AudioDxe entry in my UEFI/Driver. Now boot picker shows instantly, well, 1 sec delay.

 

 

Yes the culprit is AudioDxe.efi.

 

I just checked the debug log and there's nearly 5 seconds overall delay cause by AudioDxe.

Here's a snippet of the log:

 

.
.
00:359 00:005 HdaCodecProbeFuncGroup(): probing widgets
00:745 00:385 HdaCodecProbeFuncGroup(): probing widget connections
.
.
00:778 00:000  Widget @ 0xC (type 0x0)
01:784 01:005 HdaCodecInstallProtocols(): start
.
.
01:978 00:005 HdaCodecProbeFuncGroup(): probing widgets
04:310 02:332 HdaCodecProbeFuncGroup(): probing widget connections
.
.
04:366 00:000  Widget @ 0x6 (type 0x0)
05:372 01:005 HdaCodecInstallProtocols(): start
.
.

 

  • Like 2
5 hours ago, insanefrancis said:

 

Fixed mine as well by removing the AudioDxe entry in my UEFI/Driver. Now boot picker shows instantly, well, 1 sec delay.

 

Is your Windows backup on a separate drive from your main Windows? Because if not, then I don't see it as a backup. Just doesn't make sense.

But if it is on a separate drive then one way to hide it is to disable it in your BIOS. Unless again, if you access it frequently.

 

Nice to see that boot picker quicker eh? Kudos to @arsradu who suggested this as possible cause. BTW It's not a Windows Backup technically, it's an exact clone on separate SSD (how I tend to back up) which is why OC boot picker sees it

Edited by Humanate
  • Like 2
14 hours ago, AudioGod said:

Is there any Ryzen 3000 OpenCore users on this thread by any chance that can share there thoughts on there build without being a AMD troll about it?

 

What would you like to know? We have simple power management now, but there is still some app (abode) issues, and sleep works or it doesn't. If you want to run Catalina on Ryzen you have to use OC, the latest patches are not for Clover, but OC developers are not going to support it, they are trying to make a PC as close to a Mac as possible with their boot loader and that doesn't include AMD since no Mac uses AMD. (understandable).

On 5/23/2020 at 1:44 AM, koder said:

I need help make patch for making sleep/awake works. I post full info and they locked. It's hard to find someone who has experience with ACPI spec.

what am i going to do without RehabMan?

 

This is the problem everything here

https://github.com/acidanthera/bugtracker/issues/931

Help

4 hours ago, koder said:

I need help make patch for making sleep/awake works. I post full info and they locked. It's hard to find someone who has experience with ACPI spec.

what am i going to do without RehabMan?

 

This is the problem everything here

https://github.com/acidanthera/bugtracker/issues/931

 

Sleep/wake issues are usually caused, in my experience, by misconfigured iGPU. Also, if you don't necessarily need a custom DSDT, I would recommend not using one and only working with SSDTs (the ones mentioned on the Dortania OpenCore page). Looks like you're using the HD4600 (same as mine, by the way), which should be pretty easy to configure using Lilu + WEG + config -> Device Properties (AAPL,ig-platform-id). More info on that here.

 

Also, if I may suggest, try not to spam the forum. If people don't reply, more often than not, they don't know how to fix your issue. Or expect a bit more details. Also, please add your hardware information to your signature. That helps a lot.

Edited by arsradu
If I wanted to switch from clover to oc on my desktop would a fresh install be best or just clear nvram is enough?
 
 
Sent from my iPhone using Tapatalk

I think clearing nvram is enough but I keep getting stuck on
[EB|#LOG:EXITBS:START] or something alike.
I have unlocked my msr to see if that helps but still no joy.
Any suggestions?
I’ll upload config after.


Sent from my iPhone using Tapatalk
If I wanted to switch from clover to oc on my desktop would a fresh install be best or just clear nvram is enough?
 
 
Sent from my iPhone using Tapatalk

I think clearing nvram is enough but I keep getting stuck on
[EB|#LOG:EXITBS:START] or something alike.
I have unlocked my msr to see if that helps but still no joy.
Any suggestions?
I’ll upload config after.


Sent from my iPhone using Tapatalk
28 minutes ago, SavageAUS said:


I think clearing nvram is enough but I keep getting stuck on
[EB|#LOG:EXITBS:START] or something alike.
I have unlocked my msr to see if that helps but still no joy.
Any suggestions?
I’ll upload config after.


Sent from my iPhone using Tapatalk
I think clearing nvram is enough but I keep getting stuck on
[EB|#LOG:EXITBS:START] or something alike.
I have unlocked my msr to see if that helps but still no joy.
Any suggestions?
I’ll upload config after.


Sent from my iPhone using Tapatalk

 

Take a look Here for this troubleshooting.

10 hours ago, Download-Fritz said:

If categorical filtering by ScanPolicy does not work for you, no... it's bootable, so it's shown as bootable :)

 

Thanks. 

Actually, I made a mistake. That EFI drive displayed was not Clover but ANOTHER OpenCore on the Catalina-HD drive.

Let me explain.

I have seen a worrying problem with OC (which I will explain in another thread) so I removed Clover from my Mojave-SSD and installed OC.

So now I have OC on the the Catalina-HD ESP AND OC on the Mojave-SSD.

Then I switched the BIOS default boot priority from Catalina-HD ESP to Mojave-SSD ESP.

That screenshot above is what happens when I boot.

 

So OpenCanopy is displaying second OC EFI.

Of course it Halts with Critical Error when I try to boot that EFI (since OC Image has already started).

 

If I select either Catalina-HD or Mojave-SSD they both boot fine.

 

I know we should not have more than one OC instance but how should OC scan policy handle more that one instance of OC ESP ?

8 hours ago, eSaF said:

I also have a disk containing Mojave plus one with Catalina and the other with Windows, I have no problem using OC to boot Mojave. Have you tried temporarily removing the Clover EFI folder and try booting Mojave with OC which would get rid of the extra EFI partition? Worked for me.

 

Thanks eSaF. Actually I don't have a problem booting any of the four displayed OS's (even when Clover was on the Mojave drive).

The question was about the displayed EFI drive icon (now that HideSelf setting is removed).

That displayed icon is for a second OC on another drive (see my explanation above to Download_Fritz).

@MacNB, currently OpenCore has no ways to hide discovered entries on request. We do not see a valid reason to, since in our eyes these are valid bootable entries. Even if you boot a second OpenCore copy, it should no longer cause boot failure (unless the second copy is very old) but return to the UI with no issues.

 

With or without HideSelf (i.e. regardless of the OpenCore version — 0.5.8 or 0.5.9) you will always see all OpenCore versions installed but the one you booted from. There was no change here in 0.5.9, and I do not believe we will change it in the future mainly due to performance reasons of doing extra I/O.

 

Finally, if you believe that seeing EFI Boot is not intuitive in regards to your second OpenCore copy, you could always provide a custom .disk_label and/or .VolumeIcon.icns to make it clear. If desired, as an alternative you can also remove the other installation entirely.

3 hours ago, Matgen84 said:
 

Take a look Here for this troubleshooting.

Yeah I checked there, that’s why I unlocked my msr but I’ll check again and upload my config when I get a chance.

 

Attached config

 

Sent from my iPhone using Tapatalk

config.plist

Edited by SavageAUS
Added config.plist
4 hours ago, MacNB said:

I know we should not have more than one OC instance but how should OC scan policy handle more that one instance of OC ESP ?

Which version of OC is the secondary instance? If it's older than the 0.5.9 revision that dropped HideSelf (remember BOOTx64 and OC must always be in sync here), it will be shown no matter what. Once you upgrade that instance to the latest version, it should disappear too.

 

EDIT: Turns out I remembered incorrectly and only the boot partition is "filtered" for OC booters, looks like you're out of luck.

Edited by Download-Fritz
1 hour ago, SavageAUS said:

Yeah I checked there, that’s why I unlocked my msr but I’ll check again and upload my config when I get a chance.

 

Attached config

 

Sent from my iPhone using Tapatalk

config.plist

 

What do you mean by unlock your msr (config.plist or BIOS)?

 

Your config.plist:

<key>AppleCpuPmCfgLock</key>
<false/>
<key>AppleXcpmCfgLock</key>
<true/>

 

 

Dortania guide:  needed when CFG-Lock can't be disabled in BIOS

<key>AppleCpuPmCfgLock</key>
<true/>
<key>AppleXcpmCfgLock</key>
<true/>

 

 
What do you mean by unlock your msr (config.plist or BIOS)?
 
Your config.plist:
AppleCpuPmCfgLockAppleXcpmCfgLock

 
 
Dortania guide:  needed when CFG-Lock can't be disabled in BIOS

AppleCpuPmCfgLockAppleXcpmCfgLock

 


Yeah CFG lock. I used modified grub shell to change the var to unlocked.
I also uploaded config.plist to check for errors.


Sent from my iPhone using Tapatalk
 
What do you mean by unlock your msr (config.plist or BIOS)?
 
Your config.plist:
AppleCpuPmCfgLockAppleXcpmCfgLock

 
 
Dortania guide:  needed when CFG-Lock can't be disabled in BIOS

AppleCpuPmCfgLockAppleXcpmCfgLock

 


Yeah CFG lock. I used modified grub shell to change the var to unlocked.
I also uploaded config.plist to check for errors.


Sent from my iPhone using Tapatalk
  • Sad 1
3 hours ago, vit9696 said:

@MacNB, currently OpenCore has no ways to hide discovered entries on request. We do not see a valid reason to, since in our eyes these are valid bootable entries. Even if you boot a second OpenCore copy, it should no longer cause boot failure (unless the second copy is very old) but return to the UI with no issues.

 

With or without HideSelf (i.e. regardless of the OpenCore version — 0.5.8 or 0.5.9) you will always see all OpenCore versions installed but the one you booted from. There was no change here in 0.5.9, and I do not believe we will change it in the future mainly due to performance reasons of doing extra I/O.

 

Finally, if you believe that seeing EFI Boot is not intuitive in regards to your second OpenCore copy, you could always provide a custom .disk_label and/or .VolumeIcon.icns to make it clear. If desired, as an alternative you can also remove the other installation entirely.

 

 

2 hours ago, Download-Fritz said:

Which version of OC is the secondary instance? If it's older than the 0.5.9 revision that dropped HideSelf (remember BOOTx64 and OC must always be in sync here), it will be shown no matter what. Once you upgrade that instance to the latest version, it should disappear too.

 

EDIT: Turns out I remembered incorrectly and only the boot partition is "filtered" for OC booters, looks like you're out of luck.

 

Guys, thanks for the clear explanation.

I agree there's no valid reason to hide discovered entries on request as it's a very unusual situation in general use (specially multiple instances of OC).

I had an older version of OC on the Catalina-HD vs. current version (compiled last last night) on Mojave-SSD.

 

Just for testing, I've copied that latest OC build to Catalina-HD EFI and put .contentsDetails with name = OC-NVMe in the Boot folder.

I put a .contentsDetails file with the name = OC-P120 on the Mojave-SSD EFI Boot folder.

So now both EFI's are the same.

 

If I boot Mojave-SSD EFI via BIOS F12 (on the P120 drive), I see this in OpenCanopy:

IMG_1784.thumb.jpg.8259b3c1b21861aef1e73c9f43d7dbb3.jpg

 

If I boot Catalina-HD EFI (on the NMVe drive), I see:

 

IMG_1785.thumb.jpg.3ff42089831b55fcbcb2895582feaeb5.jpg

 

Now if I select either OC-NMVe or OC-P120, it no longer crashes and gets me back into OpenCanopy.

Actually, it's kind of handy to have a secondary OC EFI has a backup while testing bleeding edge versions :)

So all cool. Keep up the great work.

 

Now to my next discovery/problemo....:dev:

  • Like 2

OpenCore Debug logs corrupting EFI partition ?

 

So recently in the last couple of days my boot times are slowed down even after removing AudioDxe.efi.

The Apple logo appears and the loading bar starts (slower than before) and around half way it's starts to stutter and halts for a couple of seconds  and screen goes black and the loading bar continues and boots normal.

I think ~ 8-10 seconds have been added.

 

Anyway, leaving that problem to one side for the moment, I discovered potentially another.

In order to track down that issue, I first ran diskutil verifydisk command and discovered another problem.

The OpenCore EFI partition is getting corrupted:

 

macnb@My-iMac OpenCore % diskutil verifydisk disk1
Started partition map verification on disk1
Checking prerequisites
Checking the partition list
Checking the partition map size
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Problems were found with the partition map which might prevent booting
Error: -69766: The partition map needs to be repaired because there's a problem with the EFI system partition's file system
Underlying error: 8

macnb@My-iMac OpenCore % 

 

I most have been boot with Debug Builds with Debug->Target=0x43 which creates OC log files on every boot.

Over the past few weeks, I must have restarted 100's of times (with logs created on each restart).

I normally delete the older log files as they start taking space. 

 

next I ran fsck command:

macnb@My-iMac OpenCore % sudo fsck_msdos /dev/disk1s1
Password:
** /dev/rdisk1s1
** Phase 1 - Preparing FAT
** Phase 2 - Checking Directories
Invalid long filename entry for /opencore-2020-05-23-170943.txt
Remove? [yn] n
** Phase 3 - Checking for Orphan Clusters
Found orphan cluster(s)
Fix? [yn] n
Found 8 orphaned clusters
1436 files, 57752 KiB free (115505 clusters)
** Phase 1 - Preparing FAT
** Phase 2 - Checking Directories
Invalid long filename entry for /opencore-2020-05-23-170943.txt
Remove? [yn] n
** Phase 3 - Checking for Orphan Clusters
Found orphan cluster(s)
Fix? [yn] n
Found 8 orphaned clusters
Free space in FSInfo block (115505) not correct (231010)
Fix? [yn] n
1436 files, 115505 KiB free (231010 clusters)
** Phase 1 - Preparing FAT
** Phase 2 - Checking Directories
Invalid long filename entry for /opencore-2020-05-23-170943.txt
Remove? [yn] n
** Phase 3 - Checking for Orphan Clusters
Found orphan cluster(s)
Fix? [yn] n
Found 8 orphaned clusters
Free space in FSInfo block (115505) not correct (346515)
Fix? [yn] n
1436 files, 173257 KiB free (346515 clusters)
macnb@My-iMac OpenCore %

Lots of orphaned clusters and also see:

Invalid long filename entry for /opencore-2020-05-23-170943.txt

 

I backed up the EFI folder onto the my Home folder.

I fixed the EFI partition by running diskutil repairdisk disk1 and luckily nothing was lost.

 

So I installed OC onto one of the other drives in my system and booting off that fine.

After a few days (lots of restarts and OC log files), that drive's EFI partition was also corrupted with similar errors.

 

I have now turned OFF debug (Target=0) and have not seen any corruptions.

 

Both drives are new (one NVMe and the other SSD).

 

Anyone else seen this ? or verified their Disks recently after logging OC ?

 

×
×
  • Create New...