OpenCore General Discussion

[Anto65]

24 minutes ago, MacWill said:

I'm using Opencore 0.7.5 and I've tried all the ways but it looks like the path is wrong or it needs some argument to locate the Ubuntu boot.

Since the linuxboot driver was introduced it went fine with scapolicy 0, but I prefer not to use it and start Linux (Garuda) and use its grub through custom entries and scan policy 2687747 after finding the path via shell .. .maybe that is wrong?

 

[Stefanalmare]

8 hours ago, Stefanalmare said:

About the new OpenCore feature "gpubar" on Aorus Master Z390, Rx 6800 XT.
1. Resize bar enable on bios + ResizeAppleGpuBars 10 all OK - from picker: Mac OS, ubuntu and windows (resize bar enable on Radeon Software) are booting OK
2. Resize bar enable on bios + ResizeAppleGpuBars 11 - Mac OS stuck on PCI configuration
3. Resize bar enable on bios + ResizeGpuBars 10 - from picker: Mac OS, ubuntu boot OK, windows no display and error 43 if I remember well
Questions:
1. OC can be made to use for example 1,5 value on ResizeAppleGpuBars (1,5G resize bar)? For trying values below 2G.
2. On older firmwares, without resize bar option in bios, this feature is relevant?

If I enable resize bar on bios, I kill sleep on hack with AMD framebuffer error. 

[MacNB]

20 hours ago, miliuco said:

It's a workaround, but it works. As part of the install process, IPG updates Preboot volume (setup window shows info when installation is ending) and it does what we aren't able to do: new volume name is written into  .disk_label / .disk_label_2x  / .disk_label.contentDetails, so OpenCore can read the right name at next boot.

Fist time I read about it was in the other forum, a post of Aug 26, 2020 from joostiphone titled [Solved] OpenCore boot menu. I know it's not an elegant solution but...

 

 

Thanks.

Still bizarre that IPG does that.

 

What's wrong with mounting the preboot volume and manually writing the  .disk_label / .disk_label_2x  / .disk_label.contentDetails to the folder where the boot.efi file resides?

The  .disk_label / .disk_label_2x can be created with OpenCore's utilities

 

[miliuco]

1 hour ago, MacNB said:

What's wrong with mounting the preboot volume and manually writing the  .disk_label / .disk_label_2x  / .disk_label.contentDetails to the folder where the boot.efi file resides?

The  .disk_label / .disk_label_2x can be created with OpenCore's utilities

Yes, disklabel utility is for that task but in my case it doesn't work fine and I'm not able to get those 2 files next to BOOTx64.efi.

[deeveedee]

@MacNB I'd like to be able to follow your advice.  I tried the steps I outlined here which created the .disk_label and .disk_label_2x files in /Volumes/EFI/EFI/BOOT:

 

/Volumes/EFI/EFI/BOOT

Spoiler

 

I haven't yet followed the steps to create .disk_label.contentDetails.  Does creation of .disk_label.contentDetails require disabling SIP, or is there another way that's as easy as using disklabel?

 

EDIT: Note that I had naively tried creating .contentDetails and .disk_label.contentDetails (in /Volumes/EFI/EFI/BOOT) where each file contained the desired volume name in clear text, but that didn't work for me.

Edited October 12, 2021 by tonyx86

[Stefanalmare]

14 hours ago, Stefanalmare said:

If I enable resize bar on bios, I kill sleep on hack with AMD framebuffer error. 

After more testing, doesn't matter what value I put in ResizeGpuBars, windows boot but with graphic card error 43 and no display. On the other hand, 8 (256MB) on ResizeAppleGpuBars give boot without problems on Windows, Ubuntu and Hack, also no problems with sleep/wake.

Just FYI.

[MacNB]

2 hours ago, tonyx86 said:

@MacNB I'd like to be able to follow your advice.  I tried the steps I outlined here which created the .disk_label and .disk_label_2x files in /Volumes/EFI/EFI/BOOT:

 

/Volumes/EFI/EFI/BOOT

  Hide contents

 

I haven't yet followed the steps to create .disk_label.contentDetails.  Does creation of .disk_label.contentDetails require disabling SIP, or is there another way that's as easy as using disklabel?

 

Sorry to ask, but why are you trying to label the EFI volume ?

The EFI volume is for example where the booter resides such as OpenCore's BOOTx64.efi or Windows, or Linux Grub. Normally OC Bootpicker will not display itself in the boot picker list.

 

Using OC's disklabel utility is easy:

disklabel  -e "OSX HD" .disk_label .disk_label_2x

This will create two hidden files .disk_label & .disk_label_2x  in your current working directory.

You can also create the text file .disk_label.contentDetails using a simple echo command:

echo "OSX HD" > .disk_label.contentDetails

You can list hidden files using :

ls -ial

You then copy (using sudo prefix) the three hidden files to your Preboot volume where boot.efi file resides.

On Big Sur, that file resides in:

/System/Volumes/Preboot/<UUID>/System/Library/CoreServices

where <UUID> is unique folder name on your system.

 

When you reboot, you will see a disk named OSX HD in the OC Boot Picker.

 

Edited October 12, 2021 by MacNB
typo

[deeveedee]

@MacNB For the reason that's probably obvious: I have no idea what I'm doing

[MacNB]

3 hours ago, tonyx86 said:

@MacNB For the reason that's probably obvious: I have no idea what I'm doing

🤣 no worries. 

 

Try it.

 

BTW, those two  .disk_label & .disk_label_2x files are special bitmap render files used by Apple boot picker and of course OpenCanopy to render onto the screen.

I have not found a graphical tool to display them but did find a terminal command to display the content in textual form to get an idea what is in the label files.

Go to where your .disk_label & .disk_label_2x are located then copy and paste this :

 

dump_label () { local contents=$(xxd -p -c99999 $1); echo ${contents:10} | perl -pe "s/(..)/\1 /g;s/00/../g;s/ //g;s/(.{$((0x${contents:2:4}*2))})/\1\n/g" ; }
dump_label .disk_label
dump_label .disk_label_2x

It will print out the contents on the screen. Make your terminal window large to see it properly.

 

I cannot take credit for that clever little script. That goes to a user joevt at MacRumors Forums.

Source of dump_label here on GitHub. 

Edited October 12, 2021 by MacNB
added source of dump_label

[deeveedee]

@miliuco and @MacNB - Your instructions were excellent.  In my case, I didn't need to create any files.  I simply needed to edit the existing .disk_label.contentDetails files in each /System/Volumes/Preboot/<UUID>/System/Library/CoreServices directory.

 

@miliuco I did need to mount /System/Volumes/Preboot.

 

After performing the edits, I fully enabled SIP to return my system to its previous baseline.

 

Thank you for your patience and help!

Edited October 12, 2021 by tonyx86

[miliuco]

@tonyx86

 

[deeveedee]

@eSaF Then apparently I have been in your employ for a long time.  I'll PM you with an address to send my paychecks.

[miliuco]

@Stefanalmare

I see you are working with the new gpubar OpenCore feature so I allow myself to ask you.

Correct me if I'm wrong.  The new  feature only can be used if we have AMD 6000 series (as you do) + motherboard BIOS with rbar option + CPU rbar capable.

Do you know if Intel capable CPUs includes only 10th and 11th gen or Coffee Lake R (9th) also?

It seems to be interesting only for modern games, right?

And about the new quirks, does ResizeAppleGpuBars affects only to macOS and ResizeGpuBars to other OSes? Is it so?

Thanks.

 

[Stefanalmare]

1 hour ago, miliuco said:

@Stefanalmare

I see you are working with the new gpubar OpenCore feature so I allow myself to ask you.

Correct me if I'm wrong.  The new  feature only can be used if we have AMD 6000 series (as you do) + motherboard BIOS with rbar option + CPU rbar capable.

Do you know if Intel capable CPUs includes only 10th and 11th gen or Coffee Lake R (9th) also?

It seems to be interesting only for modern games, right?

And about the new quirks, does ResizeAppleGpuBars affects only to macOS and ResizeGpuBars to other OSes? Is it so?

Thanks.

 

I have i9 9900k, Aorus Master Z390 and bar size working in windows (I'll test it also in ubuntu). So, 9th also work. AMD 6000 and Nvidia 3000 are bar size capable. Yep modern games, each day more. "And about the new quirks, does ResizeAppleGpuBars affects only to macOS and ResizeGpuBars to other OSes? Is it so?", after 2 days experience: yes!

[miliuco]

2 minutes ago, Stefanalmare said:

I have i9 9900k, Aorus Master Z390 and bar size working in windows (I'll test it also in ubuntu). So, 9th also work. AMD 6000 and Nvidia 3000 are bar size capable. Yep modern games, each day more. "And about the new quirks, does ResizeAppleGpuBars affects only to macOS and ResizeGpuBars to other OSes? Is it so?", after 2 days experience: yes!

Thank you!!! Something new to learn. 

[miliuco]

@tonyx86

Although your problem is solved, look at what I’ve found on the OpenCore configuration pdf:

 

How do I customise boot entries?

OpenCore follows standard Apple Bless model and extracts the entry name from .contentDetails and .disk_label.contentDetails files in the booter directory if present. These files contain an ASCII string with an entry title, which may then be customised by the user.

[Stefanalmare]

For those with ivy bridge on Monterey who want to enable XCPM. Found at: https://github.com/5T33Z0/OC-Little-Translated

Working in laptop and desktop.

README.md XCPM_IvyBridge.plist

[miliuco]

23 minutes ago, Stefanalmare said:

For those with ivy bridge on Monterey who want to enable XCPM. Found at: https://github.com/5T33Z0/OC-Little-Translated

Working in laptop and desktop...

Good work by @5T33Z0

[Guest 5T33Z0]

I havent tested it in Monerey. All I know that XCPM on an IvyBridge laptop runs really bad. You lose like a third of the performance.

[miliuco]

4 minutes ago, 5T33Z0 said:

I havent tested it in Monterey. All I know that XCPM on an IvyBridge laptop runs really bad. You lose like a third of the performance.

 

But the translation work is there and it's what matters.

[Stefanalmare]

7 minutes ago, 5T33Z0 said:

I havent tested it in Monerey. All I know that XCPM on an IvyBridge laptop runs really bad. You lose like a third of the performance.

Geekbench 4, 5 the same like before with just ssdtPRGen, but better temps and I suppose battery management.

[maly70]

Hi, I am trying to boot from OC 0.7.4 and installing Monterey beta9, every time I load it from OC boot menu I get apple icons and then back to OC boot menu, I have Z490 gigabyte with intel 10th generation and Nvidia gt710
I have been like that for 2 weeks now(couldn't install beta8). Thanks in advance 

[joevt]

7 hours ago, MacNB said:

🤣 no worries. 

 

Try it.

 

BTW, those two  .disk_label & .disk_label_2x files are special bitmap render files used by Apple boot picker and of course OpenCanopy to render onto the screen.

I have not found a graphical tool to display them but did find a terminal command to display the content in textual form to get an idea what is in the label files.

Go to where your .disk_label & .disk_label_2x are located then copy and paste this :

 

dump_label () { local contents=$(xxd -p -c99999 $1); echo ${contents:10} | perl -pe "s/(..)/\1 /g;s/00/../g;s/ //g;s/(.{$((0x${contents:2:4}*2))})/\1\n/g" ; }
dump_label .disk_label
dump_label .disk_label_2x

It will print out the contents on the screen. Make your terminal window large to see it properly.

 

I cannot take credit for that clever little script. That goes to a user joevt at MacRumors Forums.

Source of dump_label here on GitHub. 

I added a command, convert_label, that can convert a disk_label file to a tiff file.

https://gist.github.com/joevt/6d7a0ede45106345a39bdfa0ac10ffd6

 

[MacNB]

8 hours ago, joevt said:

I added a command, convert_label, that can convert a disk_label file to a tiff file.

https://gist.github.com/joevt/6d7a0ede45106345a39bdfa0ac10ffd6

 

 

Great job 👍

 

Did not work for me though.

 
macnb@DG-MacBook-Pro DiskUtil % source diskutil.sh
macnb@DG-MacBook-Pro DiskUtil % convert_label .disk_label my_test_label.tiff
tr: Illegal byte sequence
macnb@DG-MacBook-Pro DiskUtil %                          

It created my_test_label.tiff file but it's just black background.

Source label attached.

Destination tiff attached.

 

.disk_label my_test_label.tiff

Edited October 13, 2021 by MacNB
update

[miliuco]

@joevt Thanks for the dump label script, it works great, and thanks to @MacNB for show it to me. By the way, I like the ASCII representation of the disk label got from the script.

 

About convert_label, I get the same error "tr: Illegal byte sequence".