Jump to content

OpenCore General Discussion


dgsga
8,888 posts in this topic

Recommended Posts

To The OpenCore Legacy Devs

Can You Possibly make it so the the install creater

Making  uses NOT the WHOLE Disk But Any Partitions you want to use 

PLEASE

Link to comment
Share on other sites

On 6/14/2023 at 9:27 AM, SavageAUS said:

Not sure if anyone has said this recently but I just want to give a huge shoutout to the OC / Dortania devs who have made Sonoma and all previous versions possible on our non Apple non locked down hardware. If memory serves me the biggest hurdle I’ve seen was with big sur at first? But the upgrades after that have been smooth even Ventura to Sonoma (excluding brcm wifi). So once again a huge thanks from me. Keep up the good work.
Anyone got a donation link?


Sent from my iPhone using Tapatalk

 

Thank you for the kind words!

 

Acidanthera does not take any donations, but Dortania (specifically the OpenCore Legacy Patcher team) does. We take donations in hardware (ie. Macs, graphics cards, SSDs, etc.) For those, you can get in touch with me. We also recently opened up a donation page on Open Collective, for which the link is here. The funds will be used for buying hardware.

 

1 hour ago, STLVNUB said:

To The OpenCore Legacy Devs

Can You Possibly make it so the the install creater

Making  uses NOT the WHOLE Disk But Any Partitions you want to use 

PLEASE

 

OCLP's installer creator is mostly just a wrapper around createinstallmedia with some OCLP specific stuff done afterwards. You should just run createinstallmedia manually if hackintoshing or doing any non-standard stuff

  • Like 5
Link to comment
Share on other sites

5 hours ago, dhinakg said:

OCLP's installer creator is mostly just a wrapper around createinstallmedia with some OCLP specific stuff done afterwards. You should just run createinstallmedia manually if hackintoshing or doing any non-standard stuff

The Piont Being That It SHOULD Know If It's One Disk/USB OR Several Partitions On A Disk/USB

It's Called Putting Smarts Into The Program

Link to comment
Share on other sites

On 6/14/2023 at 3:18 PM, STLVNUB said:

Thank You Kind Sir, Will Let You Know How It goes,

Every Version I've Tried Results in a Panic:(

I Haven;t Tried It Yet, My Main Rig Is Out Of Action, Doesn't Power Up

Using My MacBook Pro Instead.

Link to comment
Share on other sites

I want to boot Garuda Linux, OC 0.9.2 doesn't show the entry for it. I have already included bstrfsx64.efi  and OpenLinuxBoot.efi drivers and enabled in config.plist file.

I even tried the bless overide but no entry shown.

My Garuda drive is btrsfs formated with zstd compression, is it because of the compression it is not recognized?

What is the solution?

  • Sad 1
Link to comment
Share on other sites

52 minutes ago, rajkhand said:

I want to boot Garuda Linux, OC 0.9.2 doesn't show the entry for it. I have already included bstrfsx64.efi  and OpenLinuxBoot.efi drivers and enabled in config.plist file.

I even tried the bless overide but no entry shown.

My Garuda drive is btrsfs formated with zstd compression, is it because of the compression it is not recognized?

What is the solution?

Try ext4_x64.efi.

Link to comment
Share on other sites

I think I have a m1 or m2 MacBook at work with a dead screen that I can possibly pull some information from just need to know what is needed for wifi and where to supply the information.
It is a customers machine that has not been collected so it is password protected and I do not know the password.
If I can still pull an ioreg or something helpful for Broadcom wifi please let me know.
Perhaps I can get something via target disk mode? Or even format the drive to reinstall.


Sent from my iPhone using Tapatalk

  • Like 1
Link to comment
Share on other sites

15 hours ago, Stefanalmare said:

Try ext4_x64.efi.

How it will help? my drive is formatted with BTRFS filesystem with ZSTD compression and NOT ext4.

I tried that also but it didn't show the entry.

 

Any Solution to boot from OC?

  • Like 1
Link to comment
Share on other sites

6 hours ago, rajkhand said:

How it will help? my drive is formatted with BTRFS filesystem with ZSTD compression and NOT ext4.

I tried that also but it didn't show the entry.

 

Any Solution to boot from OC?

 

If you have windows installed, download EasyUEFI. Boot windows from OpenCore and make a new entry of your linux in EasyUEFI. I don't know how Garuda works, but I suppose it have a boot folder in EFI. If you do like that, next time you are in OpenCore picker, you will see the linux icon. 

Link to comment
Share on other sites

On 6/19/2023 at 12:17 PM, AslashA said:

How to rename this particular device PEG0.PEGP to PEG0.SSD0 in opencore?

1760527153_Screenshot2023-06-19at22_21_19.thumb.png.e9ace2f5fb67ab86978b8ab3d6589581.png

 

You could disable the PEGP device then create a new SSD0 device. I would not recommend using an ACPI patch to rename, considering how common the PEGP device name likely is.
Does the device really need to be renamed though? I'd avoid it if you can.

Edited by 1Revenger1
  • Like 3
Link to comment
Share on other sites

On 6/18/2023 at 5:58 PM, Stefanalmare said:

 

If you have windows installed, download EasyUEFI. Boot windows from OpenCore and make a new entry of your linux in EasyUEFI. I don't know how Garuda works, but I suppose it have a boot folder in EFI. If you do like that, next time you are in OpenCore picker, you will see the linux icon. 

I have no windows. On one nvme I have Hackintosh and another I have installed Garuda linux which is an ARCH base distribution. It has an EFI partion with BOOT and Garuda directories. BOOT contains BOOTx64.efi And Garuda has grubx64.efi.

If from opencore picker after pressing space bar I select uefishell. In this I can cd to either of these directories and start by either running BOOTx64.efi ot grubx64.efi.

How to add an entry in opencore so the picker shows it?

Link to comment
Share on other sites

Ok I have tried to troubleshoot this mostly on my own but now I need help.

My OpenCore version is not detected by any 3rd party apps (About This Hack, Hackintool, Etc)

I have reset my NVRAM, I have formatted my EFI partition. This has been going on for a long time with this machine.

This is only happening on my AMD rig, my Intel laptops are all fine.

I know this is only a trivial matter but it is bugging me that nothing can see which OpenCore version I am using.

Spoiler

Screenshot 2023-06-23 at 9.13.42 pm.png

Screenshot 2023-06-23 at 9.13.52 pm.png

Screenshot 2023-06-23 at 9.16.16 pm.png

Screenshot 2023-06-23 at 9.16.08 pm.png

Screenshot 2023-06-23 at 9.16.01 pm.png

Screenshot 2023-06-23 at 9.15.53 pm.png

 

EFI.zip

Edited by SavageAUS
  • Sad 1
Link to comment
Share on other sites

1 hour ago, SavageAUS said:

Ok I have tried to troubleshoot this mostly on my own but now I need help.

My OpenCore version is not detected by any 3rd party apps (About This Hack, Hackintool, Etc)

I have reset my NVRAM, I have formatted my EFI partition. This has been going on for a long time with this machine.

This is only happening on my AMD rig, my Intel laptops are all fine.

I know this is only a trivial matter but it is bugging me that nothing can see which OpenCore version I am using.

  Reveal hidden contents

Screenshot 2023-06-23 at 9.13.42 pm.png

Screenshot 2023-06-23 at 9.13.52 pm.png

Screenshot 2023-06-23 at 9.16.16 pm.png

Screenshot 2023-06-23 at 9.16.08 pm.png

Screenshot 2023-06-23 at 9.16.01 pm.png

Screenshot 2023-06-23 at 9.15.53 pm.png

 

EFI.zip 6.91 MB · 0 downloads

 

Looks like a nightly build to me.  Happens to me with nightlies as well as you can see:

 

148884832_Bildschirmfoto2023-06-23um15_36_24.png.edc67a5ec7753e29f31f4af8148d379d.png

 

Same result when using Terminal

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version	UNK-000-0000-00-00

 

Edited by cankiulascmnfye
Link to comment
Share on other sites

@SavageAUS @cankiulascmnfye

 

Check the ExposeSensitiveData setting in the config.plist. It can be set to 2. I believe.

 

According the OC Manual:

7. ExposeSensitiveData
Type: plist integer
Failsafe: 0x6
Description: Sensitive data exposure bitmask (sum) to operating system.
• 0x01 — Expose the printable booter path as an UEFI variable.
• 0x02 — Expose the OpenCore version as an UEFI variable.
• 0x04 — Expose the OpenCore version in the OpenCore picker menu title. 
• 0x08 — Expose OEM information as a set of UEFI variables.

Edited by Matgen84
  • Like 7
  • Thanks 1
Link to comment
Share on other sites

20 hours ago, Matgen84 said:

@SavageAUS @cankiulascmnfye

 

Check the ExposeSensitiveData setting in the config.plist. It can be set to 2. I believe.

 

According the OC Manual:

7. ExposeSensitiveData
Type: plist integer
Failsafe: 0x6
Description: Sensitive data exposure bitmask (sum) to operating system.
• 0x01 — Expose the printable booter path as an UEFI variable.
• 0x02 — Expose the OpenCore version as an UEFI variable.
• 0x04 — Expose the OpenCore version in the OpenCore picker menu title. 
• 0x08 — Expose OEM information as a set of UEFI variables.

Thank you very much.

All is good with my OCD now lol.

 

Such a simple setting, mine was set on 8, now is set to 6.

Spoiler

1417141710_Screenshot2023-06-24at8_26_45pm.png.61ad0b2f9cfb1add37bdcd03f478b54c.png

 

  • Like 1
Link to comment
Share on other sites

So, OC 0.9.4 now has what is called InstanceIdentifier to " target .contentVisibility to specific instances". This sounds like that you can use different instances? of OpenCore now (located in different folders?).

 

So I checked the Documentation:

 

"InstanceIdentifier: […]The current use of this value is to optionally target .contentVisibility files to specific instances of OpenCore, as explained in the Boot Algorithm section."

 

Okay, so let's look into .contentVisibility: "The .contentVisibility file, when present, may optionally target only specific instances of OpenCore. Its contents are [{Instance-List}:](Disabled|Auxiliary). If a colon (:) is present, the preceding Instance-List it is a comma separated list of InstanceIdentifier values (example: OCA,OCB:Disabled). When this list is present, the specified visibility is only applied if the InstanceIdentifier of the current instance of OpenCore is present in the list. When the list is not present, the specified visibility is applied for all instances of OpenCore.

 

Note 1 : For any instance of OpenCore with no InstanceIdentifier value, the specified visibility from a .contentVisibility file with an Instance-List will never be applied. "

 

ICould  somebody show an example of how this is actually implemented? The explanations sound confusing.

  • Like 2
Link to comment
Share on other sites

@cankiulascmnfye I haven't used CLOVER for quite a while, but I remember CLOVER having folders for each macOS version.  I think I always used the "Other" folder which applied to all versions of macOS.  I'm probably forgetting a lot, but if what you say is true, it sounds like an old CLOVER capability that's being resurrected in OC.

  • Like 1
Link to comment
Share on other sites

I have a problem with OC 0.9.3 on a Hackintosh with MSI B250 Mortal motherboard (is kabylake Intel CPU i5-7600).

 

All USB ports are proven to work, they are displayed as Connect in the Hackintosh Tool and in the system properties for USB.

 

However, I don't see any external icons for the USB drives on the desktop or in Disk Utility.

It is only the case in Sonoma Beta1 and Beta2.

 

OC 0.9.3 runs fine with Ventura and Monterey etc.

 

What is causing external drives not showing up in Sonoma macOS? is it because of the OC 0.9.3?

 

Thanks for help on this.

 

My problem has been solved.

 

I have read in other forums that it works with an Intel Blutooth Fix.kext (disable this) then the external drives are displayed.

 

I only installed the BCM94360CD WLAN+BT combo card. Ok WLAN doesn't work under Sonoma anymore anyway, so I deleted all the Brcm kextes.

 

Simply deactivating the BlueToolFixup.kext brought about the success that my 2nd NvME in a PCIe controller and also all USB drives

are visible as external drives in the desktop and disk utility and I also have read+write access to them.

 

I was now able to deactivate all Brcm kextes under OC 0.9.3 and still WLAN and BT still work perfectly under Ventura.

 

So it what is probably simplified a lot under OC 0.9.3 compared to OC 0.8.8.

Edited by AlfredoM
  • Like 2
Link to comment
Share on other sites

1 hour ago, deeveedee said:

@cankiulascmnfye I haven't used CLOVER for quite a while, but I remember CLOVER having folders for each macOS version.  I think I always used the "Other" folder which applied to all versions of macOS.  I'm probably forgetting a lot, but if what you say is true, it sounds like an old CLOVER capability that's being resurrected in OC.

 

These folders in Clover are only relevant for loading kexts based on the macOS version. OpenCore's Min/Max Kernel settings are a much better solution in this regard this since this method doesn't produce kext duplicates.

 

But Clover supports loading different configs from the boot menu. And since the latest commit it now also supports multiple SMBIOS (with an auto-switcher) for different versions of macOS (including FakeCPUID) which allows using the same EFI and config for different versions of macOS which require a different SMBIOS and FakeCPUID which is required when trying to run old OSes with latest hardware.

 

For OpenCore it seems you need a duplicate of the whole OC folder, rename it, configure it differently then do the .contentVisibility thing, I guess.

Link to comment
Share on other sites

×
×
  • Create New...