Jump to content

OpenCore General Discussion


dgsga
8,887 posts in this topic

Recommended Posts

3 hours ago, iGPU said:

Instead, selecting the "Recovery 10.16" disk repeatedly loops back to menu (but from there, I can successfully boot into BS)

Did your installation complete successfully, without any forced shutdown?

I noticed the same behaviour (loop when trying to access recovery) when I forced a shutdown at Forcing CS_RUNTIME for entitlement : com.apple.rootless.restricted-block-devices

Link to comment
Share on other sites

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.

Edited by eSaF
  • Like 1
Link to comment
Share on other sites

On 7/15/2020 at 7:18 AM, iGPU said:

 

Pavo,

 

I tried booting into BS Recovery with JumpstartHotPlug enabled, but see error: "OCB: LoadImage failed - Unsupported" and OC won't boot into Recovery. Instead, selecting the "Recovery 10.16" disk repeatedly loops back to menu (but from there, I can successfully boot into BS). I'm using OCBuilder compiled v060 (14 July).

 

Also, do you have any comments about my earlier post here?

 

Thanks.

Injector kext (ones without a ExecutablePath) do not show up in kextstat, you need to check IORegistryViewer to see if it loaded, For example AGPMInjector below:

 

 

Spoiler

Screenshot 2020-07-15 08.52.08.png

 

 

Spoiler

Screenshot 2020-07-15 08.52.40.png

 

  • Like 2
Link to comment
Share on other sites

14 hours ago, ghost8282 said:

Did your installation complete successfully, without any forced shutdown?

I noticed the same behaviour (loop when trying to access recovery) when I forced a shutdown at Forcing CS_RUNTIME for entitlement : com.apple.rootless.restricted-block-devices

 

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

Link to comment
Share on other sites

3 hours ago, Sbrillo said:

how to add GUI on OpenCore 6.0 and boot chime?

 

it's OpenCore 0.6.0 -- not yet reached 6.0 :)

 

Read the manual (Configuration.pdf -- hint look for OpenCanopy & AudioSupport).

Then download the Resources folder from https://github.com/acidanthera/OcBinaryData (also mentioned in the manual)

You do not need all the Audio files in the Resources folder if you only want the chime.

 

Link to comment
Share on other sites

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

Captura de ecrã 2020-07-15, às 20.40.47.png

 

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 :)

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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) 

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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 by markl18
Link to comment
Share on other sites

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

d5e06830eefb264fe4bb40d1222c1501.jpg




Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

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

EAE8747A-0BEB-4232-8580-421B300B3DCB.jpeg

Edited by Killuminati91
Link to comment
Share on other sites

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

d5e06830eefb264fe4bb40d1222c1501.jpg




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?

Link to comment
Share on other sites

  [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
Link to comment
Share on other sites

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:

 

1383771709_ScreenShot2020-07-17at12_28_10PM.thumb.png.c57bbe215e05a3be199e4aac3c883a83.png

 

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

  • Haha 1
Link to comment
Share on other sites

6 hours ago, eSaF said:

Were you abled to put it back together? :hysterical:

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

  • Haha 3
Link to comment
Share on other sites

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.

1070159924_2020-07-189_22_38.png.9117fbcb782a18bc6a06a90ab055f704.png

 

i want to remove two EFI and bootmgfw entries.

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

1986870083_2020-07-189_24_28.png.7957c7e612d967d56ca27d8464389a05.png

 

anyone who give me tip?

 

 

  • Sad 1
Link to comment
Share on other sites

×
×
  • Create New...