OpenCore General Discussion

[vit9696]

@arsradu, stuff like that is often caused by APFS. With time it may need maintenance across the reboots like snapshot cleaning, trim, and so on. You can always inspect the verbose log for more details.

[KvL]

Hi! Is there a guide for compiling OpenCore under Linux environment? Like Debian/Ubuntu?

I'm trying hard but I feel I'm missing something different every time. I'd love to test "nightly" builds.

Thanks!

K.

[arsradu]

28 minutes ago, vit9696 said:

@arsradu, stuff like that is often caused by APFS. With time it may need maintenance across the reboots like snapshot cleaning, trim, and so on. You can always inspect the verbose log for more details.

 

I see... Thanks for the info!  

 

I just tested verbose mode, and surprisingly enough (at least for me), it seems to hang to something Ethernet related. Or at least that's what it looks like. Please, see the attached photo. That's the last thing it prints out before switching to second stage with graphics and all that.

[AudioGod]

1 hour ago, arsradu said:

I agree. Partition order seems off. Also, your EFI is named "NO NAME" instead of EFI. And it's smaller than usual. Should be around 200MB, yours is around 100MB.

 

For comparison, this is what my BootCamp Windows drive looks like (you can ignore the Backup partition I made).

 

 

@arsradu My Windows disk on my hack has the same strange order so I just had to double checked this for myself on a non macOS system and windows partitions the disk with the EFI at 100mb and after the Recovery Partition as standard and doesn't give the EFI partition a name.

 

@vit9696 Would this be connected to why my disk order is always changing via MountEFI with every restart? Sometimes my macOS drive is the lead drive out of the 4 I have in there and then on the next reboot its listed somewhere else in the disk order,

Edited May 20, 2020 by AudioGod

[arsradu]

7 minutes ago, AudioGod said:

 

@arsradu My Windows disk on my hack has the same strange order so I just had to double checked this for myself on a non macOS system and windows partitions the disk with the EFI at 100mb and after the Recovery Partition as standard and doesn't give the EFI partition a name.

 

@vit9696 Would this be connected to why my macOS boot time slows down over time without me doing anything and also why my disk order is always changing via MountEFI with every restart? Sometimes my macOS drive is the lead drive out of the 4 I have in there and then on the next reboot its listed somewhere else in the disk order,

 

The partitioning, in my case, was done by BootCamp Assistant itself. So, the EFI is created by MacOS, not Windows. Could be that Windows only creates a 100MB partition.

 

Also, I did notice the second thing, as well. I didn't pay much attention to it. But I don't think it's related to OC. In fact, I used to have this issue a lot more often with Clover than OpenCore. But, as I said, I didn't pay much attention to it. My boot drive is usually the first one in the list.

I think it might have something to do with your NVRAM and the default boot disk you have set up. I could be wrong though. So, please, ignore my comment if that's inaccurate.

Edited May 20, 2020 by arsradu

[AudioGod]

Just now, arsradu said:

 

The partitioning, in my case, was done by BootCamp Assistant itself. So, the EFI is done by MacOS, not Windows. Could be that Windows only creates a 100MB partition.

 

Also, I did notice the second thing, as well. I didn't pay much attention to it. But I don't think it's related to OC. In fact, I used to have this issue a lot more often with Clover than OpenCore. But, as I said, I didn't pay much attention to it. My boot drive is usually the first one in the list.

I think it might have something to do with your NVRAM and the default boot disk you have set up. I could be wrong though. So, please, ignore my comment if that's inaccurate.

 

Yeah its always been there with me too tbh,

I always put it down to macOS but its always bugged me as to why it happens.

I never thought it was OC or any other boot loader related. When you have OCD like I do it can send you a little loopy but mind you I'm little loopy full stop..  

[insanefrancis]

1 hour ago, arsradu said:

I agree. Partition order seems off. Also, your EFI is named "NO NAME" instead of EFI. And it's smaller than usual. Should be around 200MB, yours is around 100MB.

 

For comparison, this is what my BootCamp Windows drive looks like (you can ignore the Backup partition I made).

 

 

I just checked 3 modern desktop computers and it has the same partition scheme, 1=Recovery, 2=EFI, 3=Data. I also asked some friends and also the same as what I have.

 

Edited May 20, 2020 by insanefrancis

[arsradu]

7 minutes ago, eSaF said:

For the love of all things good and hackable, can some kind person please look through my EFI Folder and tell me what I am missing causing a previous Boot-Chime working in OC 0.5.8 not to work in OC 0.5.9 - Cold boot, hot boot, different permutations you name I done it. I went to bed at 3.00 am this morning mumbling to my self with the wife threatening to send me to the spare bedroom. I am not desperate to have it's just the thought that something so simple (well I thought it was) is doing my head in. I don't usually ask for help, I tend to quietly just to figure things out, nothing to with pride just scared of looking and sounding stupid  but as the saying goes ...'A Faint Heart Never ....... etc, etc. Ok enough of the mindless rambling  please save my sanity, my marriage (rambling again!!!) and my Hack, take a look at the folder please (personal data removed) Thanks.

EFI.zip

 

Try this. Your OC and AudioDxe look fine... I replaced them with my own, just to have some consistency.

The only thing that caught my eye as possibly causing issues is your Timeout. So I set it to 5s (default). Maybe the chime needs a bit of time to shine...sort of speak? :)) 

 

Also, is AudioOut = 1 correct? I mean, it should be, since it works with 0.5.8 with the same config. I set mine to 2. Not sure if that's 100% correct. But that seems to work. :))

[Matgen84]

2 minutes ago, insanefrancis said:

 

I just checked 3 modern desktop computers and it has the same partition scheme, 1=Recovery, 2=EFI, 3=Data. I also asked some friends and also the same as what I have.

 

 

Since 1909, this is the default partioning for Windows 10. 

[arsradu]

1 minute ago, Matgen84 said:

 

Since 1909, this is the default partioning for Windows 10. 

 

1909?! That was a long time ago. Windows 10 wasn't even around at that time. :)) Windows itself wasn't around. Bill Gates wasn't around either!

 

Bad dorky joke..? Ok... Sorry...  

[Matgen84]

33 minutes ago, arsradu said:

 

1909?! That was a long time ago. Windows 10 wasn't even around at that time. :)) Windows itself wasn't around. Bill Gates wasn't around either!

 

Bad dorky joke..? Ok... Sorry...  

 

The future major update: Windows 2004  A little bit funny too.

[arsradu]

9 minutes ago, Matgen84 said:

 

The future major update: Windows 2004  A little bit funny too.

That is funny! :))

 

On a more serious note, in my Windows Bootcamp installation journey, Windows (not sure which version it is, but it was freshly downloaded from Microsoft, so I'm guessing probably at least the 1909 version) didn't create any Recovery partition. I guess it just used the EFI already present.

 

The issue here...might be that MacOS probably still expects EFI to be the first partition... So, even if for Windows, the order might not be relevant, I think it still is for MacOS.

[markl18]

6 hours ago, arsradu said:

 

Are you booting off of an USB drive? What's your system hardware configuration? Can you add some details to your signature so we know what we're talking about.

 

If you're on a newer system, try to see if you have a driver called XhciDxe.efi in your Drivers folder and remove it. You don't need it for newer systems. I think this is for Ivy Bridge.

It 10 years old haswell yoga 2 pro hd4400 4510u It is opencore 0.5.9

Edited May 20, 2020 by markl18

[arsradu]

It 10 years old haswell yoga 2 pro hd4400 4510u

Yeah... I’m not an expert on laptops. But since it’s a Haswell CPU i think you can safely remove that driver.

[arsradu]

@vit9696 I think I might have found the issue for hanging on boot...

 

Initially I thought it's something related to the network kext. So I removed that. => Slow boot.

Then I removed all the kexts except for Lilu, VirtualSMC and WEG. => Slow boot.

 

Then I noticed it started to hang on gIOScreenLockState 3, which I don't know exactly what it is, but I remember it was something related to graphics.

 

 

So I thought: ok...maybe my iGPU is really slow, and it's dragging everything down. Or maybe WEG is waiting before it can move on.

I'm using ig-platform-id 0300220D (default). So...with framebuffer. If I use headless (04001204), it might be faster, but then I'll have other issues, as you probably remember.

 

Aaanyway, so that made me try to test my theory. So I set BIOS to PEG (it was already), but disabled multi-monitor support. Result: fast boot. :)) A LOT faster (it was down to a max 2 seconds from 17 seconds). So yeah...looks like that's the reason.

 

I don't know if there's anything that can be improved here... I wish there was, but then again, I know it's an old computer with old integrated graphics. So...I don't expect any miracles. But I'm just saying, IF there's anything that can be done on WEG side for example, to improve this (or if there's something else I can try), I would really appreciate it!  

Edited May 20, 2020 by arsradu

[MacNB]

Just built 0.5.9

Clear NVRAM

 

With the removal of RequestBootVarFallback setting and replaced with DeduplicateBootOrder setting, I can no longer set Windows as startup drive from System Preferences. It see's the Windows drive:

 

 

I soon as I click restart, I get:

 

If I select my Mojave drive, that boots Mojave fine.

Once in Mojave, I can select Windows as Startup and restarts the PC, OC now boots my Catalina partition instead of Windows  ! 

 

ScanPolicy is set to 0x000F0103

BootProtect = none

 

Anyone else seen this ?

 

UPDATE:

Workaround:

I had to disable the Misc->Entries ->0 (my custom Windows Entry).

Added the Misc->BlessOverride->0-> \EFI\Microsoft\Boot\bootmgfw.efi

 

Now OC 0.5.9 boots Windows from System Preferences Startup Disk.

 

I say this is a workaround since it's not what I wanted to happen.

I wanted a custom entry so that I can label the drive name that's display on boot picker.

Edited May 20, 2020 by MacNB
UPDATE

[arsradu]

15 minutes ago, MacNB said:

Just built 0.5.9

Clear NVRAM

 

With the removal of RequestBootVarFallback setting and replaced with DeduplicateBootOrder setting, I can no longer set Windows as startup drive from System Preferences. It see's the Windows drive:

 

 

I soon as I click restart, I get:

 

If I select my Mojave drive, that boots Mojave fine.

Once in Mojave, I can select Windows as Startup and restarts the PC, OC now boots my Calalina partition instead of Windows  ! 

 

ScanPolicy is set to 0x000F0103

BootProtect = none

 

Anyone else seen this ?

 

Uhm....no. BUT I also made those changes in config and I've got no issues booting into Windows, or selecting Bootcamp Windows from Startup Disk on the Mac. From Catalina. So...I'm not sure that has anything to do with it.

 

My ScanPolicy is also set to 983299 (or 0x000F0103) and BootProtect = none. As for the Mojave issue...I'm thinking probably something specific to Mojave... Is your Catalina partition the first one? Cause I'm thinking it probably can't really boot into Windows (even if you can select Windows as Startup Disk), so it defaults to something else. But that's just my theory.

Edited May 20, 2020 by arsradu

[AudioGod]

23 minutes ago, MacNB said:

Just built 0.5.9

Clear NVRAM

 

With the removal of RequestBootVarFallback setting and replaced with DeduplicateBootOrder setting, I can no longer set Windows as startup drive from System Preferences. It see's the Windows drive:

 

 

I soon as I click restart, I get:

 

If I select my Mojave drive, that boots Mojave fine.

Once in Mojave, I can select Windows as Startup and restarts the PC, OC now boots my Catalina partition instead of Windows  ! 

 

ScanPolicy is set to 0x000F0103

BootProtect = none

 

Anyone else seen this ?

Did you try setting AdviseWindows to Yes?

 

@arsradu this is what happens when the recovery drive is the first partition on windows instead of the EFI but setting AdviseWindows=Yes sorts it out.

Edited May 20, 2020 by AudioGod

[arsradu]

6 minutes ago, AudioGod said:

Did you try setting AdviseWindows to Yes?

 

@arsradu this is what happens when the recovery drive is the first partition on windows instead of the EFI but setting AdviseWindows=Yes sorts it out.

 

Oh. I didn't know that. I mean, I knew it's because of the Recovery partition, since we've just discussed this earlier. But I didn't know that AdviseWindows fixes it. My Windows takes no advises from anyone. :))

[AudioGod]

Just now, arsradu said:

 

Oh. I didn't know that. I mean, I knew it's because of the Recovery partition, since we've just discussed this earlier. But I didn't know that AdviseWindows fixes it. My Windows takes no advises from anyone. :))

Stupid Windows.... 

I feel to wipe out my partitions now and rebuild it the bootcamp way so my mind is at ease and drive looks correct cos it’s annoying me now... 

@arsradu I blame you!  (Jokes)

[arsradu]

27 minutes ago, AudioGod said:

Stupid Windows.... 

I feel to wipe out my partitions now and rebuild it the bootcamp way so my mind is at ease and drive looks correct cos it’s annoying me now... 

@arsradu I blame you!  (Jokes)

 

I know how that is. My OCD wouldn't let me sleep either if something wasn't right. :))

 

I spent two days trying to figure out what the heck is wrong with BCA and why it won't let me format the freaking USB drive!! Turns out it tries to format it as GUID + ExFAT. And to make things more fun, it also throws an error in the process.

 

So you can't create the USB drive using BCA itself on MacOS. Or at least I couldn't. But as I said a few posts before, this was my first time using BCA, so...I'm sure there are plenty of things to learn!  

And if you want to add the Support Software to the same USB, the drive needs to be MBR + FAT32 otherwise it will throw another wonderful error.

Like...WHY?! So..first you format it as GUID + ExFAT (which fails) in order to "make the USB drive for Windows". But then in order to add the Support Software to it, you want to format it AGAIN (which will obviously also erase the whole thing) as MBR + FAT32?! Are you freaking kidding me?!!

 

So the way to do it is simple (if you already know how to do it):

1. format the Windows USB drive as MBR + FAT32 (Legacy Mode) and add Windows to it using UnetBootin on the Mac, or in Windows directly, with Rufus. Ideally you should try avoiding using Windows to make Windows... I mean, at least that's what I tried to do.

2. add support software with BCA (careful on the SMBIOS). This time it will work, since the drive is already formatted as expected. And it won't delete your Windows information, cause that would be bad.

3. select the hard drive you want to put Windows on and let it format it as it pleases (select how much storage you want to allocate to Windows and how much to MacOS, in case you want to make a split Windows + MacOS, like I did).

4. reboot and boot off of the USB drive. From here on out you're all Windows. Typical Windows installation. With the exact same errors and quirks as a regular one.

 

Two things to remember:

1. if you have multiple drives connected at the same time, you need to use either iMac14,2 or MacPro6,1 SMBIOS which should allow you to enter BCA in the first place.

2. if you don't have multiple drives connected, you can also use iMacPro1,1 or something else and I think it will put its files on your hard drive (not USB). I could be wrong here, but the first thing it will ask you to do if you use one of these SMBIOSes, is to disconnect any USB drive. So...I'm assuming it's not gonna use them.

 

In fact, I heard this is actually the "new method" and the old method (with making the USB installer, adding support software to it and only after that, partition the drive) is for older machines. Again, could be wrong. Just sharing my experience in case it helps anyone.

Edited May 20, 2020 by arsradu

[MacNB]

1 hour ago, arsradu said:

 

Uhm....no. BUT I also made those changes in config and I've got no issues booting into Windows, or selecting Bootcamp Windows from Startup Disk on the Mac. From Catalina. So...I'm not sure that has anything to do with it.

 

My ScanPolicy is also set to 983299 (or 0x000F0103) and BootProtect = none. As for the Mojave issue...I'm thinking probably something specific to Mojave... Is your Catalina partition the first one? Cause I'm thinking it probably can't really boot into Windows (even if you can select Windows as Startup Disk), so it defaults to something else. But that's just my theory.

 

Catalina is on separate NVMe drive and yes it's on the first partition.

Mojave is on separate SSD drive and it's the only partition.

Widows is on yet another SSD and it's effectively the first partition followed by High Sierra.

 

I think you are right in that OC can't really boot Windows and seems to default to the NVMe drive (with Catalina).

 

I love the OC documentation, but the description of the new DeduplicateBootOrder is not super clear to me.

 

1 hour ago, AudioGod said:

Did you try setting AdviseWindows to Yes?

 

@arsradu this is what happens when the recovery drive is the first partition on windows instead of the EFI but setting AdviseWindows=Yes sorts it out.

 

Thanks for the tip.

I had AdviseWindows = NO in 0.5.8 it worked fine.

But I tried setting AdviseWindows = Yes in the current 0.5.9 and it made no difference.

 

I can boot Windows but only via boot picker - not via Startup Disk selection.

 

Something in 0.5.9 has changed for me.

Need to go back to 0.5.8 and try again.

 

UPDATE: reverting back to 0.5.8 and all is working - switching between macOS and Windows via Startup disk and Windows Bootcamp control panel. Hmmmm

 

 

Edited May 20, 2020 by MacNB

[Andrey1970]

14 minutes ago, arsradu said:

 

I know how that is. My OCD wouldn't let me sleep either if something wasn't right. :))

 

I spent two days trying to figure out what the heck is wrong with BCA and why it won't let me format the freaking USB drive!! Turns out it tries to format it as GUID + ExFAT. And to make things more fun, it also throws an error in the process.

 

So you can't create the USB drive using BCA itself on MacOS. Or at least I couldn't. But as I said a few posts before, this was my first time using BCA, so...I'm sure there are plenty of things to learn!  

And if you want to add the Support Software to the same USB, the drive needs to be MBR + FAT32 otherwise it will throw another wonderful error.

Like...WHY?! So..first you format it as GUID + ExFAT (which fails) in order to "make the USB drive for Windows". But then in order to add the Support Software to it, you want to format it AGAIN (which will obviously also erase the whole thing) as MBR + FAT32?! Are you freaking kidding me?!!

 

So the way to do it is simple (if you already know how to do it):

1. format the Windows boot drive as MBR + FAT32 (Legacy Mode) and add Windows to it using UnetBootin on the Mac, or in Windows directly, with Rufus. Ideally you should try avoiding using Windows to make Windows... I mean, at least that's what I tried to do.

2. add support software with BCA (careful on the SMBIOS). This time it will work, since the drive is already formatted as expected. And it won't delete your Windows information, cause that would be bad.

3. select the hard drive you want to put Windows on and let it format it as it pleases (select how much storage you want to allocate to Windows and how much to MacOS, in case you want to make a split Windows + MacOS, like I did).

4. reboot and boot off of the USB drive.

 

Two things to remember:

1. if you have multiple drives connected at the same time, you need to use either iMac14,2 or MacPro6,1 SMBIOS which should allow you to enter BCA in the first place.

2. if you don't have multiple drives connected, you can also use iMacPro1,1 or something else and I think it will put its files on your hard drive (not USB). I could be wrong here, but the first thing it will ask you to do if you use one of these SMBIOSes, is to disconnect any USB drive. So...I'm assuming it's not gonna use them.

 

In fact, I heard this is actually the "new method" and the old method (with making the USB installer, adding support software to it and only after that, partition the drive) is for older machines. Again, could be wrong. Just sharing my experience in case it helps anyone.

 

 

 

https://github.com/acidanthera/OcBinaryData/tree/master/Drivers

[arsradu]

35 minutes ago, Andrey1970 said:

 

 

 

https://github.com/acidanthera/OcBinaryData/tree/master/Drivers

I see... So that's why it failed.  It makes sense. Alright, so that was my bad.

 

It still doesn't explain why the hell does it want to reformat the same drive as MBR + FAT32 after that! :)) I mean, assuming it doesn't show any errors and it succeeds adding Windows to that USB drive, it still doesn't make any sense to format it again on the second step, to add Support Software to it. But maybe I missed something.

 

 So...I'll try again. But this time with the ExFAT (does that stand for Extra FAT? Cause I don't know why would you want that, especially with staying at home and all that.). :)) Joking, of course.

 

Update:

 

Alright. So, with the ExFatDxe driver in place, and correctly added to config (which for some reason I always forget to do, resulting in all kinds of issues :))), looks like I can now format the drive as ExFat, from Disk Utility. It still fails though, from BCA. Could be a bug. Could be something else. No idea. The drive is actually formatted, for as far as I can see. It just doesn't move any further at that step... It just starts formatting, (formatting looks ok, if that's indeed the correct format for making a bootable Windows USB drive, which...I don't know, could be), throws this error and then stops.

 

For as far as I could see, even real Mac users are getting this. So...as I said, could be a bug.

 

Edited May 20, 2020 by arsradu

[MacNB]

Forgot to add, with 0.5.9, I am seeing these "Invalid file system policy (400/F0103)" in the OC log:

07:078 00:003 OCB: Invalid file system policy (400/F0103) for BBBACE98
07:080 00:001 OCB: Adding fs BBBACE98 (E:0|L:1|P:Security Violation) - PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,36-39-28-51-29-A7-79-64)/HD(1,GPT,48FD2EC1-C3AE-4458-B959-BDBEED7D2ABE,0x28,0x64000)
07:082 00:002 OCB: Invalid file system policy (400/F0103) for BB983B18
07:084 00:001 OCB: Adding fs BB983B18 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,B23BFB37-1721-48BA-823F-76152B5DC630,0x28,0x64000)
07:086 00:002 OCB: Invalid file system policy (400/F0103) for BB95DB18
07:088 00:001 OCB: Adding fs BB95DB18 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,A4CE4F1A-43C6-492D-BB16-2DD6EABCE4EF,0x28,0x64000)
07:090 00:001 OCPI: Located cached partition entries
07:091 00:001 OCB: Invalid file system policy (200/F0103) for BB94DA98
07:093 00:001 OCB: Adding fs BB94DA98 (E:0|L:0|P:Security Violation) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(7,GPT,8B191946-A4A6-4CDF-8D18-F0E28B417C68,0x574107A8,0x135F20)