OpenCore General Discussion

[Pavo]

On 9/18/2021 at 12:26 PM, ghost8282 said:

emu

It seems a bug in libvirt or qemu (I suspect libvirt).

Not working: qemu 6.1, libvirt 7.6.0/7.7.0

working (same vm configuration, same oc): qemu 5.1, libvirt 6.5.0

 

I opened an issue in libvirt gitlab, hopefully someone will be able to sort it out.

 

So nothing to do with oc, sorry.

Never had any installation/updating issues using KVM+Qemu even OTA updates have worked fine in all versions of Monterey. Currently on Libvirt 7.3.0 and Qemu 6.0.0 on Unraid 6.10.0-rc1.

[FredWst]

On 9/20/2021 at 2:26 PM, tonyx86 said:

@FredWst If I understood you correctly, you're wondering why your rig boots without AppleCpuPmConfigLock=True and/or AppleXcpmCfgLock=True even though your MSR 0xE2 is locked and you are unable to unlock it in BIOS.  I experience the same behavior with my rig.  Further, when I was using CLOVER, I was unable to boot without CLOVER's KernelPM fix enabled, so the behavior is different with OC than with CLOVER.  Others who have used my posted OC EFIs have indicated that if they don't set AppleXcpmCfgLock=True, their rig freezes under heavy CPU load even though it boots fine.  

If you're looking for a suggestion, I would recommend that you set AppleXcpmCfgLock=True if you can't unlock MSR 0xE2.

 

@tonyx86

I've no issue during heavy load or after many hour of use, even wake up after many days.  (without patch)

I read your post before posting, I activate xclm patch ... but not sure it is correctly working. wait and see if it's better or not.

 

14:567 00:033 OCAK: Read kernel version 21.1.0 (210100)
14:579 00:012 OCAK: Replacing _xcpm_core_scope_msrs data 226 76
14:586 00:006 OCAK: Replacing _xcpm_core_scope_msrs data 226 406416
14:592 00:006 OCAK: Replacing _xcpm_core_scope_msrs data 226 16384
14:599 00:006 OCAK: Not matching _xcpm_core_scope_msrs data 46 422876
14:610 00:011 OCAK: 64-bit XcpmCfgLockRel replace count - 2

 

Fred

[ghost8282]

On 9/20/2021 at 4:24 PM, Pavo said:

Never had any installation/updating issues using KVM+Qemu even OTA updates have worked fine in all versions of Monterey. Currently on Libvirt 7.3.0 and Qemu 6.0.0 on Unraid 6.10.0-rc1.

It's ovmf not qemu, nor libvirt.

Latest working version is 202011 (stable). I suggest to not update OVMF_CODE and VARS.

Unraid uses old versions of ovmf.

Thanks to this I was able to track the culprit to ovmf.

[Septendre]

On 9/12/2021 at 7:55 PM, 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

 

 

 

 

 

 

I finally got openlinuxboot working on my rig, after a lot of fiddling, reading and testing. 

With Misc:Security:ScanPolicy set to 16129, UEFI:APFS:EnableJumpstart= true, and UEFI:Drivers:OpenLinuxBoot.efi + Flags=0x0000018F, everything works, and linux boot real quick (without using grub) !

So I moved my USB test EFI to the computer boot disk, and got rid of Clover (after long years of faithful service). 

The only annoying thing left is since Ubuntu doesn't manage the external screen resolution of 2560 x 1440  (it stops at 1080p) when I come back to OSX I have to power off, wait and then power on the external screen so that Catalina have the framebuffer activated with the 2560 x 1440 resolution. Otherwise both screens flick on and off trying to adjust, the internal one showing the desktop (on and off), and the external remaining black. I wonder if there is a NVRAM UUID addressing that ... more reading to do. When I come back from windows 10 everything is fine, probably since Windows manage the screen resolution that I use in OSX.

 

By the way Antuneddu where is your icon set from? They look real nice.

Edited September 21, 2021 by Septendre

[Anto65]

Well, welcome aboard ... you're okay with Linux too 👍
The icons come from myself, every now and then it takes my fancy and I create some sets 🙂  (Backgrounds are resized to your 2560x1440 resolution)

 

 

https://drive.google.com/file/d/1yiuk4G2fnbGIAngP0LhWjhqNPYAXGVeA/view?usp=sharing

 

[Guest 5T33Z0]

Been trying to work out how to calculate the new 12 bit csr-active-config. But I don't know if the hex value for bit 8 is correct. Could someone check this: https://docs.google.com/spreadsheets/d/1f6bGPFUahIp4NvqDRRmyZ3Gkm929Qim2u2h6qcntAOQ/edit#gid=1747705456

Edited September 21, 2021 by 5T33Z0

[Guest 5T33Z0]

@antuneddu Great Flavors. Can you tell me hwo I can rezise the wallpapers inside the background.icns files? Do I need a tool for that? Thanks.

[Anto65]

On 9/21/2021 at 12:53 PM, 5T33Z0 said:

@antuneddu Great Flavors. Can you tell me hwo I can rezise the wallpapers inside the background.icns files? Do I need a tool for that? Thanks.

Vielen Dank 😊 

export the .icns in .png via Preview Images on the osx , after you drag it into the app of our dear chris1111 https://github.com/chris1111/Background-Resizer (accepts only png , jpg) 
new pngs will be created with various resolutions, choose your ideal one and convert it back to .icns with
https://github.com/chris1111/OpenCanopy-Generator

[Septendre]

@antuneddu Thanks a lot for sharing your theme ! Have a great day !👍

[Guest 5T33Z0]

Getting there… need to figure out the formulas for converting back from DEC to HEX and then swapping the pairs etc:

 

[Guest 5T33Z0]

@MifJpnAlphaPlus It say "HEX SWAPPED" in the last line…

 

Anyway, I noticed there's a tool called BitmaskDecode which basicall can do ALL the calculations one needs for OpenCore.

 

 

 

[greythorne]

Updated to Opencore 0.7.3, however the Bluetooth is lost. Apparently even the USB devices when plugged in do not show up but in the system hardware it is shown. 
 

also noticed when I use USB to test out opencore, it boots very slowly. 
 

any idea what could be wrong with my setup? 
 

please see attached. 

[Guest 5T33Z0]

Okay, done wit OpenCoreCalcs. Uploaded it to google docs:https://docs.google.com/spreadsheets/d/1_JiTL-VNNvS8-cFclZ7AZ2Tqd_a5_ZHlVWXBcGQ1iGw/edit?usp=sharing (You can download but not edit it online.)

 

It Included:csr-active-config, ScanPolicy, PickerAttributs, ExposeSensitive Data.

 

Also available here: https://github.com/5T33Z0/OC-Little-Translated/tree/main/10. Calculators

 

Thanks to @Hervé for the research on the CSR bitmask!

Edited September 21, 2021 by 5T33Z0

[Guest 5T33Z0]

On 9/21/2021 at 8:19 PM, Hervé said:

A few adjustments to be made in my opinion:

1. "size of bitmask" -> just "bitmask" (the actual size of the CsrActiveConfig value ranging from 8 to 12 bits since inception)
2. "storage" (???) -> "Hex value"
3. "hex swapped"-> incorrect term which does not mean much, it should be "byte reverse(d) order"
4. you should have just used power of 2 for the hex and dec. values of each flag
5. you should have provided a facility to set/unset the bit and calculate the car-active-config value accordingly
6. unspecified entries for the Hex values resulting in null decimal values -> may be somehow confusing for people...
7. decimal values shown for csr-active-config -> not really useful...
8. selected/specified csr-active-config hex values -> no rationale provided, needs explanation and reasoning

 

 

1.: "Size" = number or bits used to encode the the csr.active-config for the listed macOS versions: from 8 to 12 bits

2 and 5:  "Storage" = It's a just storage for Hex values, nothing more. It says so in the Description. It's a workaround since you can't create Switches in Numbers (afaik)

3. Ok.

4. Ok.

7.  I think it is quite educating to know the full calculation path

8. These are examples.

 

At the end of the day, everybody has to decide which flags to use. All I can do is provide some visual illustration to help people to understand the principle behind calculating  csr-active-config. 

 

 

[Guest 5T33Z0]

Done with the OC Troubleshooting Workflow. Added to OpenCore Update Guide as well:

[SavageAUS]

Is there a setting I need to change for my smbios info to work? I have the generic section filled in correctly but shows up as pictured.


Sent from my iPhone using Tapatalk

[Anto65]

have you tried with
https://github.com/corpnewt/GenSMBIOS 

[eSaF]

@SavageAUS - Hi I suspect there is mismatch data in your SmBIOS/Mac Model hence the screwed output name, have a look at what @antuneddu suggested.

[SavageAUS]

[mention=1083558]SavageAUS[/mention] - Hi I suspect there is mismatch data in your SmBIOS/Mac Model hence the screwed output name, have a look at what [mention=1390874]antuneddu[/mention] suggested.

Was working previously but I updated OpenCore version and now it’s as pictured. No change to smbios / generic has been made. I’ll check older config files to confirm.


Sent from my iPhone using Tapatalk

[miliuco]

1 hour ago, SavageAUS said:

Was working previously but I updated OpenCore version and now it’s as pictured. No change to smbios / generic has been made. I’ll check older config files to confirm.

It's not reading SMBIOS data or config.plist is incomplete. Recheck or upload here the file.

[rajkhand]

My EFI works perfectly but both ocvalidate and OCAuxollaryTools give me error for illegal character in Path variable. This line is at Misc->Enteries->0

 

PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,03-1D-00-BF-49-A7-79-64)/HD(1,GPT,13D0BB3F-6C1B-4801-84EC-A0FBFBD2C315,0x800,0x100000) /\EFI\ubuntu\grubx64.efi

 

What is wrong?

 

Also when I boot in Ubuntu with OpenCore (0.7.3) my motherboard is recognised as a Mac 19,1 and board name is Acidanthera etc. But if I choose to Boot to Ubuntu drive from BIOS it shows all correct values.

1. Will this affect working in UBUNTU?

2. Any way to avoid this?

[Stefanalmare]

Starting with the last 2 OC builds, I saw a big improvement in boot time (machine's - ivy bridge laptop, desktop, haswell laptop, coffee lake desktop). Also in coffee lake, Ubuntu started to boot with no issue with ScanPolicy 0 and ext4_x64.efi, OpenLinuxBoot.efi.

[Anto65]

1 hour ago, rajkhand said:

My EFI works perfectly but both ocvalidate and OCAuxollaryTools give me error for illegal character in Path variable. This line is at Misc->Enteries->0

 

PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,03-1D-00-BF-49-A7-79-64)/HD(1,GPT,13D0BB3F-6C1B-4801-84EC-A0FBFBD2C315,0x800,0x100000) /\EFI\ubuntu\grubx64.efi

 

What is wrong?

 

Also when I boot in Ubuntu with OpenCore (0.7.3) my motherboard is recognised as a Mac 19,1 and board name is Acidanthera etc. But if I choose to Boot to Ubuntu drive from BIOS it shows all correct values.

1. Will this affect working in UBUNTU?

2. Any way to avoid this?

...100000) /\EFI\ubuntu\grubx64.efi

 

this ok

...100000)/\EFI\ubuntu\grubx64.efi

[Septendre]

On 9/23/2021 at 8:49 AM, rajkhand said:

My EFI works perfectly but both ocvalidate and OCAuxollaryTools give me error for illegal character in Path variable. This line is at Misc->Enteries->0

 

PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,03-1D-00-BF-49-A7-79-64)/HD(1,GPT,13D0BB3F-6C1B-4801-84EC-A0FBFBD2C315,0x800,0x100000) /\EFI\ubuntu\grubx64.efi

 

What is wrong?

 

Also when I boot in Ubuntu with OpenCore (0.7.3) my motherboard is recognised as a Mac 19,1 and board name is Acidanthera etc. But if I choose to Boot to Ubuntu drive from BIOS it shows all correct values.

1. Will this affect working in UBUNTU?

2. Any way to avoid this?

I quite sure it won't affect Ubuntu, but this is caused by PlatformInfo: UpdateSMBIOSMode ... you probably have selected Create or Overwrite. You have to remember that OpenCore passes all its arguments to every Operating systems it boots, not only OSX as was the case with Clover.

[miliuco]

18 minutes ago, Septendre said:

I quite sure it won't affect Ubuntu, but this is caused by PlatformInfo: UpdateSMBIOSMode ... you probably have selected Create or Overwrite. You have to remember that OpenCore passes all its arguments to every Operating systems it boots, not only OSX as was the case with Clover.

No, see @antuneddu post, it's the extra space at the end of the PCI path.