OpenCore General Discussion

[Septendre]

1 hour ago, Stefanalmare said:

Same in my coffee lake rig. No avail to make openlinux work.

I have progressed ... 

I changed misc:security:scanpolicy to 5377,

 

 

In UEFI:APFS I unchecked EnableJumpstart, and now I can have ext4_x64 and openlinuxboot both enabled; I added and entry under Misc:Entries for Ubuntu, and I still need to fine tune it to have a working ubuntu.

 

 

But there is progress.   

 

Note: I'm using screen capture from OCAuxilliaryTools just to show where to find these. 

IT'S NOT THE TOOL I USE TO EDIT CONFIG.PLIST, FOR THAT PURPOSE I USE PROPERTREE, as OcAux have caused me some configuration problems in passing arguments to my graphic card that I took almost a full day to find out!

[Anto65]

I think your tool is out of date, masks are missing in the ScanPolicy ( OC_SCAN_ALLOW_FS_LINUX_DATA and  OC_SCAN_ALLOW_FS_XBOOTLDR )

However I tried again for further confirmation
With ScanPolicy = 2703107 and also with ScanPolicy = 0   ( of course with Linux drivers enabled and without Entries in Misc    you don t need to add nothing in Misc > Entries if use the driver ext4_x64 and openlinuxboot )   

 

 all systems are detected and started fine , but Windows and Linux are placed in pole position

 

With ScanPolicy 2687747  without any driver , but with the Entries for Windows and Linux declared in Misc

                

 

At boot it is like this, which is what I prefer ... to have osx in pole position

 

 

 

 

 

 

Edited September 13, 2021 by antuneddu

[ad911]

On 9/10/2021 at 7:27 PM, 5T33Z0 said:

I have a quesion about the use of PlatformInfo > Generic > ProcessorType.

 

In my Notebook (running as MacBookPro10,1) I have an Intel I7 3630QM. According to this List, it is a Type Core i7 Type 4.and has the value 0x0704 as listed here

 

So if I wanted to change the field ProcessorType from "0" (Auto) to 0x0704, do I have to bit swap it to 0407 or what do I just enter 0704?

 

I think it should be byte swap 0407

 

you may check the result in the boot log

ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p

something like this in the log

00:105 00:000 OCCPU: Detected Apple Processor Type: 07 -> 0704 

 

ioreg -rxn "CPU0@0"

| "cpu-type" = <0407>

[Septendre]

3 hours ago, antuneddu said:

I think your tool is out of date, masks are missing in the ScanPolicy ( OC_SCAN_ALLOW_FS_LINUX_DATA and  OC_SCAN_ALLOW_FS_XBOOTLDR )

However I tried again for further confirmation
With ScanPolicy = 2703107 and also with ScanPolicy = 0   ( of course with Linux drivers enabled and without Entries in Misc    you don t need to add nothing in Misc > Entries if use the driver ext4_x64 and openlinuxboot )   

 

 all systems are detected and started fine , but Windows and Linux are placed in pole position

 

With ScanPolicy 2687747  without any driver , but with the Entries for Windows and Linux declared in Misc

                

 

At boot it is like this, which is what I prefer ... to have osx in pole position

 

 

 

 

 

 

However I'm unable to achieve your result with the same settings ... either with 0 or 2703107 my linux doesn't show up. 

 

The setting that prevented OpenCore to even boot with the linux drivers enabled is UEFI:ConnectDrivers, if set to true, OpenCore doesn't boot with the linux drivers when both are enabled (ext4_64 + openlinuxboot).

 

Fun Fact: since I'm working with a usb stick, as long as there is a folder with the name EFI on the stick, the UEFI booter of the firmware will list it as a selectable choice. It doesn't have to be hidden (and later revealed with mount EFI to work on the config.plist)

 

I'm still fiddling with entries to point to my linux partition, as I would like to be able to start linux without using grub.

[Guest 5T33Z0]

@Septendre @antuneddu There's also an online generator for OpenCore ScanPolicy wtth descriptions for each bit and some templates: https://oc-scanpolicy.vercel.app/

Edited September 13, 2021 by 5T33Z0

[Guest 5T33Z0]

4 hours ago, ad911 said:

 

I think it should be byte swap 0407

 

you may check the result in the boot log

 

ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p

something like this in the log

 

00:105 00:000 OCCPU: Detected Apple Processor Type: 07 -> 0704 

 

ioreg -rxn "CPU0@0"

 

| "cpu-type" = <0407>

 

 

Thanks for your explanation. I entered ioreg -rxn "CPU0@0" in terminal and CPU type is

 

 |   "cpu-type" = <0407>

 

So byte swapped it is indeed!

 

[Anto65]

40 minutes ago, 5T33Z0 said:

@Septendre @antuneddu There's also an online generator for OpenCore ScanPolicy wtth descriptions for each bit and some templates: https://oc-scanpolicy.vercel.app/

Yes thanks, I know it but as you can see it has not yet been updated with the new bits, I help myself with the one integrated in OCC and in any case I solved with Linux

[Guest 5T33Z0]

3 hours ago, antuneddu said:

Yes thanks, I know it but as you can see it has not yet been updated with the new bits, I help myself with the one integrated in OCC and in any case I solved with Linux

 

Ahh, new bit because of linux support?

 

The latest Version of Kext Updater now has a ScanPolicy Calc as well and I think it has the added bits:

 

 

https://www.sl-soft.de/kext-updater/

[Anto65]

Dankeschön 🙂  nice ,  the one integrated in OCC is enough ... they both do the same thing 😉

[Guest 5T33Z0]

9 hours ago, ad911 said:

 

I think it should be byte swap 0407

 

you may check the result in the boot log

 

ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p

something like this in the log

 

00:105 00:000 OCCPU: Detected Apple Processor Type: 07 -> 0704 

 

ioreg -rxn "CPU0@0"

 

| "cpu-type" = <0407>

 

 

I just realized that this "cpu-type" field is not useable for (at least not in this form) PlatforInfo > Generic > ProcessorType. Because neither 0704 nor 0407 lead to the correct result when running the ioreg -rxn "CPU0@0" command. Plus the Processor field in "About this Mac" only shows the Frequency. I think something else has to entered, but I don't know what (apart from 0 for auto-detect).

[Stefanalmare]

18 hours ago, Septendre said:

I have progressed ... 

I changed misc:security:scanpolicy to 5377,

 

 

In UEFI:APFS I unchecked EnableJumpstart, and now I can have ext4_x64 and openlinuxboot both enabled; I added and entry under Misc:Entries for Ubuntu, and I still need to fine tune it to have a working ubuntu.

 

 

But there is progress.   

 

Note: I'm using screen capture from OCAuxilliaryTools just to show where to find these. 

IT'S NOT THE TOOL I USE TO EDIT CONFIG.PLIST, FOR THAT PURPOSE I USE PROPERTREE, as OcAux have caused me some configuration problems in passing arguments to my graphic card that I took almost a full day to find out!

I tried this just for testing. The easiest thing for me it was to use EasyUEFI in Windows, boot it up from OpenCore. And I have Mac, Windows, Ubuntu fully functional from picker. The only inconvenient is the name of Ubuntu=EFI and the generic icon.

[deeveedee]

12 hours ago, 5T33Z0 said:

 

I just realized that this "cpu-type" field is not useable for (at least not in this form) PlatforInfo > Generic > ProcessorType. Because neither 0704 nor 0407 lead to the correct result when running the ioreg -rxn "CPU0@0" command. Plus the Processor field in "About this Mac" only shows the Frequency. I think something else has to entered, but I don't know what (apart from 0 for auto-detect).

Not sure if you're still struggling with this.  I'm not experienced with changing ProcessorType, but you've made me curious.  This thread suggests that entering the ProcessorType explicitly as 0x0704 should work.

 

List of ProcessorTypes.

Edited September 14, 2021 by tonyx86

[chris1111]

On 9/6/2021 at 11:36 AM, 5T33Z0 said:

Thanks for the Icons! This is how it looks now. I don't know why the ResetNVRAM Icon is not applied, but it's okay.

 

 

 

My freind seting up config like this 

<key>Tools</key>
		<array>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Auxiliary</key>
				<false/>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Flavour</key>
				<string>OpenShell:UEFIShell:Shell</string>
				<key>Name</key>
				<string>OpenShell</string>
				<key>Path</key>
				<string>OpenShell.efi</string>
				<key>RealPath</key>
				<false/>
				<key>TextMode</key>
				<false/>
			</dict>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Auxiliary</key>
				<false/>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Flavour</key>
				<string>ResetNVRAM:NVRAMTool</string>
				<key>Name</key>
				<string>Reset NVRAM</string>
				<key>Path</key>
				<string>CleanNvram.efi</string>
				<key>RealPath</key>
				<false/>
				<key>TextMode</key>
				<false/>
			</dict>
		</array>
	</dict>

 

[ad911]

14 hours ago, 5T33Z0 said:

 

I just realized that this "cpu-type" field is not useable for (at least not in this form) PlatforInfo > Generic > ProcessorType. Because neither 0704 nor 0407 lead to the correct result when running the ioreg -rxn "CPU0@0" command. Plus the Processor field in "About this Mac" only shows the Frequency. I think something else has to entered, but I don't know what (apart from 0 for auto-detect).

did you enabled the PlatformInfo Automatic option

 

Automatic

Type: plist boolean
Failsafe: false
Description: Generate PlatformInfo based on the Generic section instead of using values from DataHub, NVRAM, and SMBIOS sections.
Enabling this option is useful when Generic section is flexible enough:
• When enabled SMBIOS, DataHub, and PlatformNVRAM data is unused.
• When disabled Generic section is unused.

[Guest 5T33Z0]

5 hours ago, tonyx86 said:

Not sure if you're still struggling with this.  I'm not experienced with changing ProcessorType, but you've made me curious.  This thread suggests that entering the ProcessorType explicitly as 0x0704 should work.

 

List of ProcessorTypes.

 

Thanks. As of now, "ProcessorType" is defined as "Number". But if the value has to be in the form of 0x0704 explicitly, then the type has to be set to "Data", right?

 

EDIT: I've figured it out. The values for the CPUs are in hex and have to converted to a decimal number. So 0x0704 (HEX) = 1031 in Dec and nd THEN you can use the number for `ProcessorType`. Now it works. Wouldn't hurt to mention this in the documentation.

Edited September 14, 2021 by 5T33Z0

[ghost8282]

29 minutes ago, 5T33Z0 said:

As of now, "ProcessorType" is defined as "Number"

Worked for me defined as integer (integer is also defined in sample.plist, so let's go with it!).

From the table in the link I used 0A01 (hex), so:

			<key>ProcessorType</key>
			<integer>2561</integer>

 

Edited September 14, 2021 by ghost8282

[ghost8282]

25 minutes ago, 5T33Z0 said:

But if the value has to be in the form of 0x0704 explicitly, then the type has to be set to "Data", right?

I don't have a single hex value in my config.plist

As far as I know, data is base64.

 

By "explicitly" I think he meant to manually specify the processor type value in the Generic section with automatic set to false.

 

Edit:

I remember ProcessorType was added to the Generic section (in addition to the SMBIOS section), so automatic can be true if ProcessorType is set there

Edited September 14, 2021 by ghost8282

[Guest 5T33Z0]

@ghost8282 You're right, I forgot to save the config, after changing the value so it still was set to "0", so my assumption was wrong, because converting from hex to dec resulted in the wrong cpu. So what do I add now? 0704 as integer? I am confused.

[ghost8282]

1 hour ago, 5T33Z0 said:

Wouldn't hurt to mention this in the documentation

There's no need in my opinion, one can understand the type by looking at "integer" (also specified in Configuration.pdf --> Type: plist integer).

Again, no hex value is specified in the sample.plist.

30 minutes ago, 5T33Z0 said:

So what do I add now? 0704 as integer?

No, integer means decimal, so convert your hex value to decimal as you wrote in your edited message.

 

			<key>ProcessorType</key>
			<integer>1796</integer>

0x0704 is not 1031 but 1796

Edited September 14, 2021 by ghost8282

[Guest 5T33Z0]

4 minutes ago, ghost8282 said:

There's no need in my opinion, one can understand the type by looking at "integer".

Again, no hex value is specified in the sample.plist.

No, integer means decimal, so convert your hex value to decimal as you wrote in your edited message.

 

			<key>ProcessorType</key>
			<integer>1796</integer>

0x0704 is not 1031 but 1796

 

LOL, you're right, I converted 0x0407 🤣

[ghost8282]

Reviving this:

I'm still unable to update the os without a forced shutdown..

Happened right now with the ota delta update to big sur 11.6.

 

Steps:

1. Downloaded the delta ota update from system software update

2. After finishing the download the system asks to reboot <-- It doesn't reboot, monitor shutdown, virsh is reporting my vm is still in execution <-- Waited for 15 min, I had to force the shutdown (virsh destroy BigSur) and manually start again the vm (virsh start BigSur)

3. Update continues with no problem, reboot (OK)

4. Update continues with no problem, reboot (OK)

 

In general I don't have any issue with shutdown/reboot from within the os.

Any idea on what's going on? @vit9696 do you know what can I check to see what is preventing the os to reboot?

[Guest 5T33Z0]

Okay, so to conclude the `ProcessorType" episode:

• Fnd your CPU model from this List  (section "Apple Processor Type Information - Processor Types")
• convert it from hex to decimal.
• Paste it in PlatformInfo > Generic > ProcessorType
• Save, Reboot, check "About this Mac" to see if it is correct
• Be happy!

Edited September 14, 2021 by 5T33Z0

[Guest 5T33Z0]

Somehow the command

 

ioreg -rxn "CPU0@0"

 

does not work on my desktop which uses an i9 10850K. Is it because it's defined as "PR00" instead of CPU?

[ghost8282]

5 minutes ago, 5T33Z0 said:

ioreg -rxn "CPU0@0"

 

does not work on my desktop which uses an i9 10850K. Is it because it's defined as "PR00" instead of CPU?

-n specifies the name, if CPU0@0 doesn't exist nothing will be shown in output

[Guest 5T33Z0]

Okay, thanks. Will check later what the name is.

 

BTW, I created an issue for the Online ScanPolicy Generator and the guy fixed it already: https://oc-scanpolicy.vercel.app/