OpenCore General Discussion

[fusion71au]

4 hours ago, MorenoAv said:

Hi guys good afternoon...

Quick question for @eSaF, the entry below in your config.plist is what makes widows boot successfully?

Thanks

 

27 minutes ago, MorenoAv said:

Yep it's not activated... but is the correct way to d it...

 

Hi @MorenoAv,

 

Just a few tid bits on dual booting macOS and Windows with OC...

1.  Since 0.5.9, OC can automatically detect UEFI Windows loader bootmgfw.efi --> no need for Custom Entry

2.  From OC documentation (Configuration.pdf) re OEM Windows activation...

 

"Windows may need to be reactivated. To avoid it consider setting SystemUUID to the original firmware UUID. Be warned, on old firmwares it may be invalid, i.e. not random. In case you still have issues, consider using HWID or KMS38 license or making the use Custom UpdateSMBIOSMode."

 

Personally, I set Kernel/Quirks/CustomSMBIOSGuid to YES and PlatformInfo/UpdateSMBIOSMode to Custom in my OC config.plist  ---> avoids Windows OEM activation problem (Windows keeps its original firmware UUID and macOS keeps its own SystemUUID).

 

PS I moved my reply here since I think it would be off topic in the Big Sur beta thread

[SavageAUS]

4 minutes ago, fusion71au said:

Personally, I set Kernel/Quirks/CustomSMBIOSGuid to YES and PlatformInfo/UpdateSMBIOSMode to Custom in my OC config.plist  ---> avoids Windows OEM activation problem (Windows keeps its original firmware UUID and macOS keeps its own SystemUUID).

So if i read correctly PlatformInfo/UpdateSMBIOSMode is a string set to Create now, if i change that to the string Custom with the other quirk enabled that should avoid everytime i boot into windows with OC the message i get about a microsoft account problem?

[LarryTran016]

10 hours ago, SavageAUS said:

So if i read correctly PlatformInfo/UpdateSMBIOSMode is a string set to Create now, if i change that to the string Custom with the other quirk enabled that should avoid everytime i boot into windows with OC the message i get about a microsoft account problem?

I don't know but I'm using that, UpdateSMBIOSMode: Create, CustomSMBIOSGuid: Yes, Automatic: No but it still work well with both win and mac (My laptop is Ivy Bridge and DELL INSPIRON 3421, those are  relevant for DELL laptop maybe) 

[ghost8282]

14 hours ago, iGPU said:

 

I've already installed BS. I now simply want to boot into Recovery rather than directly into BS.

I understood, what I was saying is that I had the same issue when I forced a shutdown after preboot and my solution was to reinstall without that forced shutdown, so I asked if your installtion completed successfully without forcing shutdowns.

[markl18]

hi I am still stuck on boot failures 

EB|H:LV] Err(0xE) @ GV boot-image-key

02:533 00:062 AAPL: [EB|#WL|6] 0x01 0x01 24 0x0E

02:594 00:061 AAPL: [EB|H:LV] Err(0xE) at GV? boot-image

02:678 00:083 AAPL: [EB|H:LV] Err(0xE) @ SV- boot-signature

02:741 00:063 AAPL: [EB|H:LV] Err(0xE) @ SV- boot-image-key

02:803 00:061 AAPL: [EB|H:LV] Err(0xE) @ SV- boot-image

02:864 00:061 AAPL: [EB|#H:NOT]

02:928 00:063 AAPL: [EB|SB:EN] Err(0xE) @ LocP 24B73556-2197-4702-82A8-3E1337DAFBF2

02:995 00:066 AAPL: [EB|#LIMG:DP] Acpi(PNP0A03,0)/Pci(1D|0)/Usb(0, 0)/Usb(1, 0)/HD(Part2,SigA8820BD4-68DB-4047-B763-250643691A75)

03:056 00:061 AAPL: [EB|#LIMG:FP] \System\Library\CoreServices\boot.efi

03:660 00:603 AAPL: [EB|#LIMG:OPT] ()

03:722 00:061 AAPL: [EB|#RPS] R?0 P?0 S?0

03:784 00:062 AAPL: [EB|OPT:LXF] 'LF (\\System\\Library\\CoreServices\\com.apple.Boot.plist)

03:848 00:063 AAPL: [EB|LD:LF] FIO: 0, DIR: 1, P: \System\Library\CoreServices\com.apple.Boot.plist, DP: 0

03:908 00:060 AAPL: [EB|LD:OFS] Err(0xE) @ OPEN (\\System\\Library\\CoreServices\\com.apple.Boot.plist)

03:969 00:061 AAPL: [EB|OPT:LXF] Err(0xE) @ 'LF

04:054 00:084 AAPL: [EB|OPT:LXF] 'LF (Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist)

04:119 00:065 AAPL: [EB|LD:LF] FIO: 0, DIR: 1, P: Library\Preferences\SystemConfiguration\com.apple.Boot.plist, DP: 0

04:184 00:065 AAPL: [EB:#KF] (root-dmg=file:///BaseSystem/BaseSystem.dmg -no_compat_check cs_enforcement_disable=1 cs_debug=1 amfi_allow_any_signature=1 amfi_get_out_of_my_way=1)

04:246 00:061 AAPL: [EB|#MBA:CL] ()

opencore-2020-07-16-225345.txt

Edited July 16, 2020 by markl18

[SavageAUS]

Ive noticed recently on my laptop if I boot with OC I get the error in the picture but if I use bios to select to windows that device is fine.
Using latest master 0.6.0
I’ll upload config or anything else that may be needed if needed.
Please help, this affects windows performance substantially.

Spoiler

Sent from my iPhone using Tapatalk

[Killuminati91]

Any Idea what this error is related to? Searching through the net gave me basically zero results.

 

ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC.ECRD] (Node ffffff8028109390), AE_NOT_EXIST (20160930/psparse-632)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC.BAT0._STA] (Node placeholder), AE_NOT_EXIST (placeholder)
ACPI Error: Result stack is empty!

 

EFI and Screenshot attached.

EFI 2.0 DEBUG Dortania.zip

Edited July 17, 2020 by Killuminati91

[Matgen84]

3 hours ago, SavageAUS said:

Ive noticed recently on my laptop if I boot with OC I get the error in the picture but if I use bios to select to windows that device is fine.
Using latest master 0.6.0
I’ll upload config or anything else that may be needed if needed.
Please help, this affects windows performance substantially.

  Reveal hidden contents

Sent from my iPhone using Tapatalk

 

@SavageAUS

Just my opinion (I haven't a laptop): have a look to your SSDT-PLUG (and Darwin args), Windows settings in your OC Config! What SMBIOS do you use for this Laptop?

[SavageAUS]

  [mention=1083558]SavageAUS[/mention] 

Just my opinion (I haven't a laptop): have a look to your SSDT-PLUG (and Darwin args), Windows settings in your OC Config! What SMBIOS do you use for this Laptop?

 

 

Here is my EFI folder minus resources and serial numbers.EFI.zip

[Matgen84]

51 minutes ago, SavageAUS said:

Here is my EFI folder minus resources and serial numbers.

Also ioreg in case it helps.

EFI.zip

Shane’s MacBook Pro.zip

 

Unfortunately this exceeds my modest knowledge. Macbook pro 16.1 has the same processor, Coffee Lake. 

[FreeJHack]

5 hours ago, SavageAUS said:

minus ... serial numbers.

Just FYI, the serial & UUID is also included in the IORegistryExplorer file, you may want to delete it from there...

......VMD6N

[Tiem]

Updated to dd6e13c yesterday and woke up to my Watch unable to unlock my Hack. The setting is unchecked and when re-checking it errors out. Console reports the following:

 

 

Signed out on my Mac. Rebooted all my devices. Everything else works, handoff, everything. Just not aWatch unlock. *throws PC out the window

[Tiem]

Ok resetting the aWatch fixed it. *runs outside to pick up the pieces of his PC

[Tiem]

6 hours ago, eSaF said:

Were you abled to put it back together? 

I had to wrestle my ram back from an aggressive squirrel but ya, all good

[Sherlocks]

I have a question for boot entry.

i usually use this option

RequestBootVarRouting true

Scan Policy 0

BlessOverride \EFI\Microsoft\Boot\bootmgfw.efi

 

it shows clean boot picker

1. Windows

2. Macintosh HD

3. Recovery HD

~

 

but i found some issues of UEFI bootloader order in Windows.

i usually control UEFI boot part easily from BOOTICEx64 

but when using this option

RequestBootVarRouting true

Scan Policy 0

in windows, i can't see exact same boot entry in BIOS.

 

so i change options.

RequestBootVarRouting false

Scan Policy 0

BlessOverride \EFI\Microsoft\Boot\bootmgfw.efi

i can get exact same boot entry of BIOS in windows.

but in boot picker. added two EFI entry.

 

i want to remove two EFI and bootmgfw entries.

i tried to change Scan Policy bit. it is no luck.

 

anyone who give me tip?

 

 

[Andrey1970]

18 minutes ago, Sherlocks said:

BlessOverride \EFI\Microsoft\Boot\bootmgfw.efi

It isn't required for Windows, OpenCore knows this way.

RequestBootVarRouting=true - surely need.

[Sherlocks]

10 minutes ago, Andrey1970 said:

It isn't required for Windows, OpenCore knows this way.

RequestBootVarRouting=true - surely need.

 

RequestBootVarRouting=true

i lost boot entry of BIOS in windows.

 

if RequestBootVarRouting=false

 

i get same boot entry of BIOS in windows.

i prefer UEFI boot entry control in windows if needs.

[arsradu]

On 7/15/2020 at 11:29 AM, eSaF said:

I was abled to boot into the Big Sur Recovery Partition without any issues whatsoever after setting 'JumpstartHotPlug' as true, as a matter of fact, I now have 'true' as the default setting going forward.

I must add, no other setting was made to the config.plist to invoke this.

 

Lucky you! It still doesn't work for me (without the apfs.efi driver). As soon as I disable that driver, the error comes back and it just goes back to the boot picker.

 

I suppose you've got both EnableJumpstart and (now) JumpstartHotPlug enabled, right? If so, then I don't know... 

[Gigamaxx]

6 hours ago, eSaF said:

Yes quite right I have both enabled. Just for the heck of it I tested the Recovery Partition and it worked flawless, when I got to the 'Disk Utility' Menu, I completely wiped the Disk and done a clean install (With both cheeks clinched as I didn't know if it would work ) and at the end I was abled to boot into a clean install again.  

Awesome find.

Has anyone been able to figure out killall Finder?   Kext modification possibilities?

[SavageAUS]

Ive noticed recently on my laptop if I boot with OC I get the error in the picture but if I use bios to select to windows that device is fine.
Using latest master 0.6.0
I’ll upload config or anything else that may be needed if needed.
Please help, this affects windows performance substantially.
Spoiler



Sent from my iPhone using Tapatalk

Is there anything in OC I can test to fix this?
Can anyone confirm if this is in fact OC causing this or is it a laptop problem?


Sent from my iPhone using Tapatalk

[Matgen84]

13 minutes ago, SavageAUS said:

Is there anything in OC I can test to fix this?
Can anyone confirm if this is in fact OC causing this or is it a laptop problem?


Sent from my iPhone using Tapatalk

 

Just my stupid opinion: do you try to boot OC ---> Windows, without DSDT

[SavageAUS]

  Just my stupid opinion: do you try to boot OC ---> Windows, without DSDT

 

Not yet but I will soon and I’ll modify this post to reflect the outcome.

 

[mention]Matgen84 [/mention]

One successful boot to windows without errors without DSDT so far. All my DSDT was doing was implementing my keys for brightness anyway as I don’t know how else to do it.

 

Will continue to test as one boot isn’t enough

 

Sent from my iPhone using Tapatalk

[Riley Freeman]

According to the documentation it should be possible to boot an installed copy of Snow Leopard. I've tried here but just after the boot picker I get the message "OCB: LoadImage failed - Unsupported" and i'm kicked back to the bootpicker again. Are there any extra steps needed for Snow Leopard? I couldn't find anything.

[MacNB]

1 hour ago, Riley Freeman said:

According to the documentation it should be possible to boot an installed copy of Snow Leopard. I've tried here but just after the boot picker I get the message "OCB: LoadImage failed - Unsupported" and i'm kicked back to the bootpicker again. Are there any extra steps needed for Snow Leopard? I couldn't find anything.

 

I am testing Legacy issues with @vit9696 and I had the same issue with SL.

He told me to use the OsxFatBinaryDrv.efi driver from Clover to boot FAT binaries.

Now SL boots fine via OC.

 

Eventually FAT binary support will make into OC (low priority) and in the meantime OsxFatBinaryDrv.efi works fine.

[Riley Freeman]

28 minutes ago, MacNB said:

I am testing Legacy issues with @vit9696 and I had the same issue with SL.

He told me to use the OsxFatBinaryDrv.efi driver from Clover to boot FAT binaries.

Now SL boots fine via OC.

 

Eventually FAT binary support will make into OC (low priority) and in the meantime OsxFatBinaryDrv.efi works fine.

 

Thanks. That got me a little further along. I'm getting "OC: Prelink inject prepare error - Unsupported" instead, followed by a "couldn't allocate runtime area" stop shortly after loading the extensions.mkext from the SL volume.

 

I tried dropping in OsxAptioFixDrv.efi from Clover and that got the system to boot a little further but it reboots almost straight away after TSC Deadline Timer.