OpenCore General Discussion

[Matgen84]

7 minutes ago, 5T33Z0 said:

@Matgen84 I tried the SSDT method before and it didn't work for some reason. But maybe I try again

 

@5T33Z0 I used MaLdOn's method at: Here It works for my Z390 config. I followed the Info.plist settings of a working USBMap. And it works.

[Guest 5T33Z0]

@Matgen84 I just opened my existing USBPorts  Kext in Hackintool and exported it again which also created a SSDT-UIAC.aml which is working fine so far. EDIT: now Front USB3 Connectors don't work any more. No I remember why I was using the USBPort.kext again…

Edited August 19, 2021 by 5T33Z0

[hardcorehenry]

@5T33Z0 maybe this one works for you.

Edited August 19, 2021 by hardcorehenry

[Guest 5T33Z0]

If I am emulating a CoffeLake CPU, do I have to change the AAPL,ig-platform-id and and device ID of the framebuffer patch, too so it matches the CPU I am emulating? I think the Framebuffer-Patch (Headless) might be the reason, why the system stalls when I am trying too boot into Mojave.

[Guest 5T33Z0]

Changing the AAPL,ig-platform-id and device-id to what is recommended for Coffeellake did the trick - no more stalling.

 

 

Edited August 20, 2021 by 5T33Z0

[Alex HQuest]

Anyone knows how to cancel OpenCore swap of the Windows and Alt keys?

 

The official Apple key mapping in Boot Camp maps Windows key as Command key, and Alt key as Option key. The official Apple keyboards have the Control, Command and Option keys, whereas PC keyboards have Control, Windows and Alt keys, in this order. On macOS I can remap the Option and Command keys on "SysPrefs > Keyboard > Modifier Keys", but they are too switched on Windows when booted via "SysPrefs > Startup Disk" and it is not that simple to remap these keys over there. If I bypass OpenCore and boot into Windows using the BIOS boot selection feature, these keys are mapped properly as PC keyboard.

 

 

[MacNB]

16 hours ago, Alex HQuest said:

Anyone knows how to cancel OpenCore swap of the Windows and Alt keys?

 

The official Apple key mapping in Boot Camp maps Windows key as Command key, and Alt key as Option key. The official Apple keyboards have the Control, Command and Option keys, whereas PC keyboards have Control, Windows and Alt keys, in this order. On macOS I can remap the Option and Command keys on "SysPrefs > Keyboard > Modifier Keys", but they are too switched on Windows when booted via "SysPrefs > Startup Disk" and it is not that simple to remap these keys over there. If I bypass OpenCore and boot into Windows using the BIOS boot selection feature, these keys are mapped properly as PC keyboard.

 

 

 

I believe not. That's exactly how it works on my real Macs. It's a "feature"

[Guest 5T33Z0]

I just updated 2 machines to OpenCore 073 Commit 09930f3

 

After that, BootPicker GUI no longer worked and both machines didn't boot. So there's either an issue with the built or something drastically changed over night. Seems to be related to OpenRuntime.efi.

Quote

 

OC Validate log:

 

OCS: Couldn't get array serialized at 0 index!
OCS: Couldn't get array serialized at 1 index!
OCS: Couldn't get array serialized at 2 index!
Serialisation returns 3 errors!

Booter->Quirks->ProvideCustomSlide is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers!
CheckBooter returns 1 error!

UEFI->Quirks->RequestBootVarRouting is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers!
CheckUEFI returns 1 error!

 

 

EDIT:

I compared the config against the sample and noticed UEFI > Drivers has a different form now:

 

 

After adding these entries, everything is back to normal.

Edited September 4, 2021 by 5T33Z0

[Anto65]

Yes just tried the system would not boot and no gui like you, after I saw that the driver structure changed
In OcBinaryData-master btrfs_x64.efi and ext4_x64.efi have been introduced. What are they for ? I tried to boot Linux without the misc entry but it doesn't detect it and no ext4 partitions are seen in the finder either 🤔

Edited September 4, 2021 by antuneddu

[Guest 5T33Z0]

@antuneddu From the changelog:

 

Quote

- Add OpenLinuxBoot driver: OC-native Linux autodetect and boot without chaining via GRUB

 

Edited September 4, 2021 by 5T33Z0

[chris1111]

 Also   for me 🧐  

https://github.com/acidanthera/OpenCorePkg/commit/aa1e19bebb20a5ad112fca31b111f8ad69cb8248

 

Roll back here and its work

https://github.com/acidanthera/OpenCorePkg/tree/239c1a533d101c9e46c675a48585dbe548998582

Edited September 6, 2021 by chris1111

[Anto65]

5 hours ago, chris1111 said:

 Also   for me 

https://github.com/acidanthera/OpenCorePkg/commit/aa1e19bebb20a5ad112fca31b111f8ad69cb8248

 

Roll back here and its work

https://github.com/acidanthera/OpenCorePkg/tree/239c1a533d101c9e46c675a48585dbe548998582

Hi, take a look here 🙃

 

https://www.insanelymac.com/forum/topic/348778-problems-with-latest-opencore-073-build/?do=findComment&comment=2765709

 

[Guest 5T33Z0]

@chris1111 @MifJpnAlphaPlus

 

[mhaeuser]

Please always use ocvalidate before posting reports. Don't rely on other junk tools, ocvalidate uses the exact scheme engine from OC + extra sanity-checking, and it is automatically up-to-date with updates.

[Guest 5T33Z0]

11 minutes ago, MifJpnAlphaPlus said:

Thank you for your polite guidance at any time.

This is just my strange impression.

 

% ./ocvalidate /Volumes/EFI/EFI.2109061841/OC/config.plist
OCS: Couldn't get array serialized at 0 index!
OCS: Couldn't get array serialized at 1 index!
OCS: Couldn't get array serialized at 2 index!
OCS: Couldn't get array serialized at 3 index!
OCS: Couldn't get array serialized at 4 index!
Serialisation returns 5 errors!

Booter->Quirks->ProvideCustomSlide is enabled, but OpenRuntime.efi is not loaded at UEFI->Drivers!
CheckBooter returns 1 error!

 

Isn't the above display lacking in sweetness?
It doesn't even have a line number.

 

 Everyone! Isn't it natural for us to seek junk sweetness?

 

thank you.

（It's a silly idea, so please ignore it.）

 

That was my thought as well, when I first saw these results. It takes a bit of detective approch, checking the log from end to beginning for clues: 1st clue: OpenRuntime.efi is not loaded. 2nd clue: it's refering to UEFI > Drivers. 3rd Clue: "Array". Then I just checked the sample for changes in the UEFI > Drivers section and knew what was wrong immediately.

[Matgen84]

14 minutes ago, 5T33Z0 said:

 

That was my thought as well, when I first saw these results. It takes a bit of detective approch, checking the log from end to beginning for clues: 1st clue: OpenRuntime.efi is not loaded. 2nd clue: it's refering to UEFI > Drivers. 3rd Clue: "Array". Then I just checked the sample for changes in the UEFI > Drivers section and knew what was wrong immediately.

 

3 minutes ago, MifJpnAlphaPlus said:

Oh, how I wish I was Sherlock Holmes!

 

I'm a bit of a Holmes too. Because I got used to looking at commits, to see changes in config.plist. And I am also looking at Opencore Changelog.md. Then I also look at the sample.plist for the syntax. I am correcting my config.plist. So ocvalidate says everything is OK. 😜

[Guest 5T33Z0]

The Drivers section was the only part of OpenCore which you didn't really had to care about: throw in your drivers, generate a snapshot, done. Now it's another source for errors. But I hope the change is worth it with the added ability to use additional arguments.  

 

The latest build has a new Quirk, btw: "- Added `ForceOcWriteFlash` UEFI quirk to enable writing OC system variables"

Edited September 6, 2021 by 5T33Z0

[chris1111]

Its work, Boot and GUI ok

Fix

https://github.com/acidanthera/OpenCorePkg/commit/f121677f66e41e6edcda7da9cb69dcb522b532ba

Edited September 6, 2021 by chris1111

[Guest 5T33Z0]

1 hour ago, chris1111 said:

Its work, Boot and GUI ok

Fix

https://github.com/acidanthera/OpenCorePkg/commit/f121677f66e41e6edcda7da9cb69dcb522b532ba

 

Nice. You should use these icons (in black) for "SSD-Minimal" as well. The way it looks now , witht he the Windows and Apple Logo sbelow the SSD Icon makes it look unbalanced and squeezed:

 

Edited September 6, 2021 by 5T33Z0

[mhaeuser]

2 hours ago, MifJpnAlphaPlus said:

It doesn't even have a line number.

The problem is the library was designed without line numbers in mind at the beginning, as despite for debugging this information is useless. While it certainly would be useful for ocvalidate now (which is much younger than OC), this cannot easily be added. Sorry.

[chris1111]

@5T33Z0

 

This is differant Icon, I made like that because if you see the Drive is more Smaller 😁 It was the goal to make them like this

You can use Flavours-B  theme with the  Background-Orig.icns

Edited September 6, 2021 by chris1111

[MacNB]

4 hours ago, Download-Fritz said:

Please always use ocvalidate before posting reports. Don't rely on other junk tools, ocvalidate uses the exact scheme engine from OC + extra sanity-checking, and it is automatically up-to-date with updates.

 

I always use OCVALIDATE and can eventually work out what is wrong/changed.

But...even compared to other "junk tools" it can be improved to be more user friendly as opposed to developer-friendly.

E.g. "OCS: Couldn't get array serialized at 0 index!" does not convey meaningful informative data as to what is wrong. That is, which array ? What does serialized mean ? what' 0 Index ?, etc. In this case, the format of the UEFI drivers section changed but that was not obvious from just the output of OCVALIDATE. Instead one also has to refer to the changelog to get "clues". 

 

Example of the improvement: since config.plist file is essentially a TEXT file (as opposed to binary), it would be useful if OCVALIDATE simply displayed the LINE NUMBER of the offending "OCS: Couldn't get array serialized at 0 index!".

[mhaeuser]

7 minutes ago, MacNB said:

it would be useful if OCVALIDATE simply displayed the LINE NUMBER

I have explained that this is not easily possible. Let me know when instead of CAPS you provide a PULL REQUEST to improve the tool.

[Guest 5T33Z0]

56 minutes ago, chris1111 said:

@5T33Z0

 

This is differant Icon, I made like that because if you see the Drive is more Smaller 😁 It was the goal to make them like this

You can use Flavours-B  theme with the  Background-Orig.icns

I was thinking about something like this (just with perspectively correct icons):

[chris1111]

@5T33Z0

Here you, go let me know

SSD.zip

 

Edited September 6, 2021 by chris1111