Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted (edited)

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 by 5T33Z0
Anto65
Anto65
Posted
Posted
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

  • Like 1
greythorne
greythorne
Posted
Posted

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. 

F2594569-CAD7-45AC-BC10-A8A2A3605003.jpeg

42633D42-F333-422D-AFDA-97381E073FC2.jpeg

Guest 5T33Z0
Guest 5T33Z0
Posted
Posted (edited)

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 by 5T33Z0
Guest 5T33Z0
Guest 5T33Z0
Posted
Posted
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. 

 

 

SavageAUS
SavageAUS
Posted
Posted
[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
miliuco
Posted
Posted
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
rajkhand
Posted
Posted

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
Stefanalmare
Posted
Posted

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
Anto65
Posted
Posted
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

  • Like 1
Septendre
Septendre
Posted
Posted
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
miliuco
Posted
Posted
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.

Septendre
Septendre
Posted
Posted (edited)
9 minutes ago, miliuco said:

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

I was answering the second part, the one mentioning the motherboard and board name. I know as a fact that the first part is due to the space before efi/ubuntu and since @antuneddu had already kindly answered that part, I offered my knowledge for the second part, cause it happened to me and support assist program from dell was not happy with it, but Ubunt will be just fine.

Edited by Septendre
adding info
miliuco
miliuco
Posted
Posted
2 hours ago, Septendre said:

I was answering the second part, the one mentioning the motherboard and board name. I know as a fact that the first part is due to the space before efi/ubuntu and since @antuneddu had already kindly answered that part, I offered my knowledge for the second part, cause it happened to me and support assist program from dell was not happy with it, but Ubunt will be just fine.

Sorry, my mistake. Then you're right. @rajkhand must set 2 keys in config.plist:

  • Kernel > Quirks > CustomSMBIOSGuid > True (default False)
  • PlatformInfo > UpdateSMBIOSMode > Custom (default Create).

So OpenCore doesn't pass SMBIOS data to other operating systems.

 

  • Like 1
ghost8282
ghost8282
Posted
Posted (edited)

Hi, I just see recent commits in opencore; I saw vit changed in sample.plist AdviseFeatures from false to true with this description:

Quote

Without this bit, it is not possible to install macOS versions with large BaseSystem images, such as macOS 12.

 

Andrey changed it back from true to false.

 

Can anybody give some suggestions?

Is that true that setting AdviseFeatures to false will prevent us to install monterey from BaseSystem?

What's the drawback of setting it to true if not running monterey (let's say big sur), so different than the current default setting in sample.plist?

 

Was that changed again to false because of the change of the last characters from AAAAA= to gAAAA= in FirmwareFeatures and FirmwareFeaturesMask?

Edited by ghost8282
Andrey1970
Andrey1970
Posted
Posted (edited)
8 hours ago, ghost8282 said:

Is that true that setting AdviseFeatures to false will prevent us to install monterey from BaseSystem?

Not truly, because this bit is already included in database for all compatible models.

Edited by Andrey1970
  • Like 1
  • Thanks 2
 Share
Go to topic listing
×
×
  • Create New...