Jump to content

OpenCore General Discussion


dgsga
8,759 posts in this topic

Recommended Posts

On 7/8/2022 at 8:43 AM, 5T33Z0 said:

A little Python Script for removing sensitive data from your config.plist and resetting some settings to default before sharing your EFI with the world: https://github.com/dreamwhite/OC-Anonymizer

Serious?

Idea and credits: 
black-dragon74
https://github.com/black-dragon74

and update by

hieplpvip
https://github.com/hieplpvip

Respect!

Dreamwhite / Ivan Cafieiro created nothin' just copied or opened PRs with little changes. Rewriting.

  • Like 1
Link to comment
Share on other sites

23 hours ago, ramirezzz said:

Serious?

Idea and credits: 
black-dragon74
https://github.com/black-dragon74

and update by

hieplpvip
https://github.com/hieplpvip

Respect!

Dreamwhite / Ivan Cafieiro created nothin' just copied or opened PRs with little changes. Rewriting.

 

As already explained

 

Here I am, sorry if I haven't replied in the meantime, but was kinda busy. I wanna clarify that in any way I wanna disrespect owners of their project. I heard about black-dragon74 https://github.com/black-dragon74/OSX-Debug project but forgot about it while I was writing the script, under @5T33Z0 suggestion.

Please let me know how should I rewrite the credits section of https://github.com/dreamwhite/OC-Anonymizer/. I'll do the best to fix this stuff.

Sorry again

 

P.S. about PRs with little changes, can you send the links? I can't find them in those links:

- https://github.com/black-dragon74/OSX-Debug/issues?q=author%3Adreamwhite

- https://github.com/hieplpvip/OC-gen-debug

  • Like 2
Link to comment
Share on other sites

1 hour ago, aufuk1 said:

Anyone able to get bluetooth working for Ventura beta 3?

I was using BlueToolFixup.kext and IntelBluetoothFirmware.kext before, currently not working.

Bluetooth is working fine on OSX Ventura ( Intel or BCM94360 ).

As usual, you would need to add specs to your profile if you need further help. 

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

16 minutes ago, Ellybz said:

Bluetooth is working fine on OSX Ventura ( Intel or BCM94360 ).

As usual, you would need to add specs to your profile if you need further help. 

 

I will add features to my signature, thanks.
I don't know exactly which intel wi-fi card is installed in my computer. I can share a screenshot.

 

image.thumb.png.323ed327721b9d56b19f2c4a2fcdb576.png

Link to comment
Share on other sites

Hi, I just bought a wireless/bluetooth mouse combination. It work well in Windows 11 but could not be detected in Monterey and Ventura. All my other devices are working well in Monterey and ventura. What must be the problem? I have only BlutoothFixup.kext in my EFI.

Link to comment
Share on other sites

6 hours ago, aufuk1 said:

 

I will add features to my signature, thanks.
I don't know exactly which intel wi-fi card is installed in my computer. I can share a screenshot.

 

image.thumb.png.323ed327721b9d56b19f2c4a2fcdb576.png

 

If I remember correctly, this is the combo I used with IntelBT & Ventura. It should work with 8265.

BrcmPatchRam3 & BrcmFirmwareData might be optional with the 8265. To be tested.

 

DO NOT USE: BrcmBluetoothInjector.kext.

 

image.thumb.png.5cb8b95ae7f3aa90d44ec6cdd47cda64.png

 

 

Obviously you need to update your kexts.

https://github.com/acidanthera/BrcmPatchRAM

https://github.com/OpenIntelWireless/IntelBluetoothFirmware

 

Don't forget to clean your NVRAM & I would also reset my BT preferences.

Please post your results.

 

Edited by Ellybz
  • Like 4
Link to comment
Share on other sites

Guest ricoc90

So I bought a new microwave, it has a "grill" option but I'm not sure how I can activate it. Any ideas?
I mean, it is off-topic but so are the 7 posts above this one so I figured that this would be the best place to ask

Link to comment
Share on other sites

5 minutes ago, ricoc90 said:

So I bought a new microwave, it has a "grill" option but I'm not sure how I can activate it. Any ideas?
I mean, it is off-topic but so are the 7 posts above this one so I figured that this would be the best place to ask

Good call @ricoc90

Link to comment
Share on other sites

3 hours ago, Ellybz said:

 

If I remember correctly, this is the combo I used with IntelBT & Ventura. It should work with 8265.

BrcmPatchRam3 & BrcmFirmwareData might be optional with the 8265. To be tested.

 

DO NOT USE: BrcmBluetoothInjector.kext.

 

image.thumb.png.5cb8b95ae7f3aa90d44ec6cdd47cda64.png

 

 

Obviously you need to update your kexts.

https://github.com/acidanthera/BrcmPatchRAM

https://github.com/OpenIntelWireless/IntelBluetoothFirmware

 

Don't forget to clean your NVRAM & I would also reset my BT preferences.

Please post your results.

 

 

Unfortunately, the kernel panic at startup when you do it this way.
I think I should open a thread about it, so as not to clutter up the post here.

 

  • Like 1
  • Confused 1
Link to comment
Share on other sites

OpenCore 0.8.3 has added --show-csr option (boolean flag) to be specified as plain text in the Arguments key of the UEFI >> Drivers >> ToogleSIP.efi entry.

If enabled, it shows current hexadecimal value of csr-active-config in the boot entry name.

It doesn't work in OpenCanopy when Misc >> Boot >> PickerAttributes has OC_ATTR_USE_GENERIC_LABEL_IMAGE that provides predefined label images for boot entries without custom entries.

Maybe it is not a very demanded feature but it is an interesting one. 

Spoiler

togglesip0.thumb.jpg.37ba19999d4006aeb26098be197c8da3.jpg

 

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

3 hours ago, Ellybz said:

As an extra note and If I'm not mistaken, this feature doesn't work if your SIP value is 0x0.

I had 0x0 when I grabbed the sample picture. Where have you read this?

  • Like 1
Link to comment
Share on other sites

41 minutes ago, miliuco said:

I had 0x0 when I grabbed the sample picture. Where have you read this?

Never mind... For some reason my ToggleSIPEntry driver was not updated & I was getting that message before entering the GUI.  All good now, I edited my previous post.

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

Hmm, okay. So if I run my machine with a CSR of 6 (i know, odd number but that is what I need for TotalFinder to work) Then I need to put 0x6 in the argument for ToggleSipEntry? Then it can toggle between SIP <on> and my user defined value?

Link to comment
Share on other sites

@pkdesign

I think you must work as before, writing the desired value in NVRAM >> add >> 7C436110-AB2A-4BBB-A880-FE41995C9F82 >> csr-active-config, so you boot always with the selected value.

It's better to have also NVRAM >> Delete >> 7C436110-AB2A-4BBB-A880-FE41995C9F82 >> csr-active-config to load you own value at each boot.

What --show-csr argument does is to show current csrutil value within Toogle SIP label in the picker.

And having ToggleSipEntry.efi driver entry you can enable csrutil at boot if needed sometime, whitout changing csr-active-config.

Edited by miliuco
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

Nice. I hadn’t added the NVRAM >> Delete ... to my config so I went ahead and did that. Looks like it is all working.

 

The only thing I saw was that adding --show-csr put a REM: statement the upper left corner and not in the Toggle SIP label. EDIT: I am still using OC 0.8.2

 

I had ClearNvram.efi in my Tools folder but I disabled that. I guess I can go ahead and just delete it and the config entry.

Edited by pkdesign
Link to comment
Share on other sites

@miliuco is there a specific nightly build date of OC 0.8.3 for which the argument --show-csr  is meant to work?

I am still using nightly 8.3.0 of 11 July 2022 and cannot get it to work as intended.

Guess I need to get a more recent nightly build and try.

 

Greetings Henties

 

Link to comment
Share on other sites

×
×
  • Create New...