Picker parameter

[scsimaya]

Hi, I have a problem, I have two Big Sur installations with two distinct 6.4 opencores. I would like to have the different default boot on the two opencores, but I can't. What I make default on one disk also defaults to the other. I think it is because the instruction is saved in NVRAM.
Can't save a picker parameter that selects a menu option in the config.plist?
Excuse my english.

 

[scsimaya]

Hi, can anyone help me?

 

[dfritchie]

Once you are in the picker, you have already booted the OC EFI. The only way is to have separate EFI's, one on each disk and pick the disk in the BIOS. Even then you may have to clean NVRAM between boots as each OC config.plist saves to the NVRAM things like the default bootdisk.

 

[scsimaya]

Once you are in the picker, you have already booted the OC EFI. The only way is to have separate EFI's, one on each disk and pick the disk in the BIOS. Even then you may have to clean NVRAM between boots as each OC config.plist saves to the NVRAM things like the default bootdisk.

Hi, thanks for the answer, the two opencores are already in two separate EFIs, in fact I can have different configurations by booting from one or the other, but the default boot system is shared. my idea was to write a boot instruction in the nvram section of opencore, but i don't know which parameter to use.

 

[dfritchie]

Well, since it uses apple's startup disk preference pane to set the default boot disk which writes a variable to NVRAM, I don't think there is a parameter in OC. I know you can use control-enter in the picker to also write the variable to NVRAM. I don't know of a way to do it in config.plist.

 

[jpz4085]

I can have different configurations by booting from one or the other, but the default boot system is shared.

You may want to see if it's possible to consolidate your separate OpenCore configurations into a single installation and use the Startup Disk setting. Consult the documentation both online and included in the distribution to see what config.plist settings could help with attempting this.

my idea was to write a boot instruction in the nvram section of opencore, but i don't know which parameter to use.

If going this route maybe you could try examining the contents of NVRAM from the terminal or macOS logs and look for the efi-boot-device entries. Then create the proper entries in the config.plist for each OpenCore installation. Make sure the correct volume is selected in Startup Disk before doing this and be certain to backup your system before changing anything. See what works for you.

 

[scsimaya]

You may want to see if it's possible to consolidate your separate OpenCore configurations into a single installation and use the Startup Disk setting. Consult the documentation both online and included in the distribution to see what config.plist settings could help with attempting this.

If going this route maybe you could try examining the contents of NVRAM from the terminal or macOS logs and look for the efi-boot-device entries. Then create the proper entries in the config.plist for each OpenCore installation. Make sure the correct volume is selected in Startup Disk before doing this and be certain to backup your system before changing anything. See what works for you.

Hi, I tried this menu entry without success:

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x0,0xFFFF,0x0)/HD(5,GPT,9D155C45-C491-4C2C-BE7E-676FBF4B773B,0x3D268AB8,0x266AC430)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,3AA865CD6D5EED318ECA9FA437FDF235)/\System\Library\CoreServices\boot.efi

Opencore only manages EFI boot entries.

 

[jpz4085]

Hi, I tried this menu entry without success:

Not a menu entry. If attempting the second option in my previous reply you'll need to create an "add" entry in the config.plist NVRAM section (under the macOS GUID) comparable to the one made by Startup Disk. You'll need to look at the "efi-boot-device" and probably "efi-boot-device-data" values present in NVRAM when you set the proper boot volume. The nvram command could be used to examine these values in terminal and try to duplicate them in the config.plist. They should probably also be included in the "delete" section to prevent them from remaining when booting the other disk.

Opencore only manages EFI boot entries.

Correct. Such as the ones made by Startup Disk, Windows, Linux, boot management tools or the firmware itself. Since you have two OpenCore installations they will need to either use the same boot entries or replace them when starting.

 

[scsimaya]

Not a menu entry. If attempting the second option in my previous reply you'll need to create an "add" entry in the config.plist NVRAM section (under the macOS GUID) comparable to the one made by Startup Disk. You'll need to look at the "efi-boot-device" and probably "efi-boot-device-data" values present in NVRAM when you set the proper boot volume. The nvram command could be used to examine these values in terminal and try to duplicate them in the config.plist. They should probably also be included in the "delete" section to prevent them from remaining when booting the other disk.

Correct. Such as the ones made by Startup Disk, Windows, Linux, boot management tools or the firmware itself. Since you have two OpenCore installations they will need to either use the same boot entries or replace them when starting.

Hi, I set up the Startup Disk, and then I read the NVRAM, this is the result for the two parameters:

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>056D898B-DC27-4BC9-A8DA-28355D514236</string></dict></dict><key>BLLastBSDName</key><string>disk5s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\CD65A83A-5E6D-31ED-8ECA-9FA437FDF235\System\Library\CoreServices\boot.efi</string></dict></array>

efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%00%00%00%00%00%00%04%01*%00%05%00%00%00%b8%8a&=%00%00%00%000%c4j&%00%00%00%00E\%15%9d%91%c4,L%be~go%bfKw;%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%8b%89m%05'%dc%c9K%a8%da(5]QB6%04%04%9a%00\%00C%00D%006%005%00A%008%003%00A%00-%005%00E%006%00D%00-%003%001%00E%00D%00-%008%00E%00C%00A%00-%009%00F%00A%004%003%007%00F%00D%00F%002%003%005%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00

I tried to insert them via the config.plist but failed
Could you put them in a generic config.plist so that I can see the right way?

 

[Feartech]

Hi, I set up the Startup Disk, and then I read the NVRAM, this is the result for the two parameters:

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>056D898B-DC27-4BC9-A8DA-28355D514236</string></dict></dict><key>BLLastBSDName</key><string>disk5s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\CD65A83A-5E6D-31ED-8ECA-9FA437FDF235\System\Library\CoreServices\boot.efi</string></dict></array>

efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%00%00%00%00%00%00%04%01*%00%05%00%00%00%b8%8a&=%00%00%00%000%c4j&%00%00%00%00E\%15%9d%91%c4,L%be~go%bfKw;%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%8b%89m%05'%dc%c9K%a8%da(5]QB6%04%04%9a%00\%00C%00D%006%005%00A%008%003%00A%00-%005%00E%006%00D%00-%003%001%00E%00D%00-%008%00E%00C%00A%00-%009%00F%00A%004%003%007%00F%00D%00F%002%003%005%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00

I tried to insert them via the config.plist but failed
Could you put them in a generic config.plist so that I can see the right way?

please use default font colour