Jump to content
5539 posts in this topic

Recommended Posts

On 1/11/2021 at 6:18 PM, AudioGod said:

Good spot bro,

They are the old config settings that used togo

00000000 - SIP completely enabled
30000000 - Allow unsigned kexts and writing to protected system file locations
67000000 - SIP completely disabled

 

FF0F0000 is correct for sip to be disabled.

it will be defaulting to sip enabled with it set to 67 as it will bypass it.

il correct that one, Thank you bud :thumbsup_anim:

 

Thanks for sharing your new config! But I think you forgot to set the new value for the "car-active-config" didn't you?

22 minutes ago, Blesh said:

 

Thanks for sharing your new config! But I think you forgot to set the new value for the "car-active-config" didn't you?

Haven’t I got it set at 6700000?

2 hours ago, AudioGod said:

HfsPlus is slow to mount USB Devices, OpenHfsPlus is just a repaired and altered version of HfsPlus.

This is also why they flipped over to VBoxHFS for a short while.

Argh, now Andrey1970 says HfsPlus.efi is quicker. What to use?!

 

2 minutes ago, pkdesign said:

Argh, now Andrey1970 says HfsPlus.efi is quicker. What to use?!

 

:hysterical: I give up with them lot. Leave it with the new version for now and let them fight it out between themselves. I’m sure they will have it sorted out by 0.6.7

34 minutes ago, AudioGod said:

Haven’t I got it set at 6700000?

 

It's 6700000 for me! Also my Sleep/Wake-reboot issue appears to fixed! Double Yay! :thumbsup_anim:

Edited by jimborae
Just now, jimborae said:

 

It's 6700000 for me! Also Sleep/Wake appears to fixed! Double Yay! :thumbsup_anim:

Awesome, Could you double check SIP is disabled on your system please?

that’s the old binary I’m using but it’s still meant to work otherwise il update the EFI and correct it....Zzzzzzzzz

1 minute ago, AudioGod said:

Awesome, Could you double check SIP is disabled on your system please?

that’s the old binary I’m using but it’s still meant to work otherwise il update the EFI and correct it....Zzzzzzzzz

Last login: Wed Feb  3 19:33:38 on ttys000

gillbates@iMac-Pro-Intel-2019 ~ % csrutil status

System Integrity Protection status: disabled.

gillbates@iMac-Pro-Intel-2019 ~ % 

  • Thanks 1
Just now, jimborae said:

Last login: Wed Feb  3 19:33:38 on ttys000

gillbates@iMac-Pro-Intel-2019 ~ % csrutil status

System Integrity Protection status: disabled.

gillbates@iMac-Pro-Intel-2019 ~ % 

Perfect, Thank you :) 

Just now, eSaF said:

Yea my sentiments exactly, Iv'e using the new version from when it was introduced without any slow downs or problems.

I noticed my USB storage drives were taking longer to eject using the old HFSPlus so I was happy to flip over. OpenPantiesPlus works just fine so il leave it and just do whatever they do in 0.6.7

i love the way they slyly made it possible to totally bypass OpenCore for other OS a good few revisions ago...lol.

I have it set that way on my X570 build and I much prefer it not messing with windows in any way....sod bootcamp...:hysterical:


If anybody wants to 100% bypass OpenCore for Linux or Windows then just change the following in the Config.plist.

  • Kernel -> Quirks -> CustomSMBIOSGuid -> True
  • PlatformInfo -> UpdateSMBIOSMode -> Custom

 

Personally It’s the one thing I never liked about OC so to be able to do it is lovely jubbly

 

  • Like 1
  • Haha 1
17 minutes ago, letsdrink said:

How to reset NVRAM from OpenCore boot menu?

Hit the Space Bar, then you’ll see the Option to Reset NVRAM. 

Edited by jimborae
  • Thanks 1
59 minutes ago, AudioGod said:

:hysterical: I give up with them lot. Leave it with the new version for now and let them fight it out between themselves. I’m sure they will have it sorted out by 0.6.7

or v1.0!

51 minutes ago, AudioGod said:

I noticed my USB storage drives were taking longer to eject using the old HFSPlus so I was happy to flip over. OpenPantiesPlus works just fine so il leave it and just do whatever they do in 0.6.7

i love the way they slyly made it possible to totally bypass OpenCore for other OS a good few revisions ago...lol.

I have it set that way on my X570 build and I much prefer it not messing with windows in any way....sod bootcamp...:hysterical:


If anybody wants to 100% bypass OpenCore for Linux or Windows then just change the following in the Config.plist.

  • Kernel -> Quirks -> CustomSMBIOSGuid -> True
  • PlatformInfo -> UpdateSMBIOSMode -> Custom

 

Personally It’s the one thing I never liked about OC so to be able to do it is lovely jubbly

 

Wait, what? :worried_anim: So you still get to pick which OS you want to boot into? But OC doesn’t mess with Windows?

I still seem to be having problems getting 0.6.6 up and running, with any version of my own config.plist & driver/.kext updates, or with AG’s very gracious 0.6.6 EFI, following his suggestion to ensure/update boot order in UEFI BIOS or F12, and then reset NVRAM during first OC 0.6.6 boot.

 

I think my trouble (black screens at either graphical OS selection or expanding choices to try to reset NVRAM; see below) has to do with the old OpenCore boot option persisting in UEFI BIOS, whether setting boot order in there or just choosing what OS to boot via F12. If I choose “UEFI OS,” I’m met by a blank screen before I ever see any OC-presented choices of what OS to boot up in. If I select “OpenCore,” I get a similar blank screen. If I have a USB with OC 0.6.5 in its EFI plugged in, I get an OC-presented list of choices of OS to boot into, and can space bar to expand the menu, and reset NVRAM. But when I boot again into what I believe to be OC 0.6.6 & get slightly updated graphical OS choices that seem to confirm this, then go to try to reset NVRAM to make SURE it’s set for a proper 0.6.6 boot… I get a black screen with no expanded choices (and hence no choice to reset NVRAM).

 

I seem to remember sometime in the past, a way when switching between OC & Clover, to clear the “OpenCore” boot entry from UEFI BIOS; not just disable, but remove. I can’t seem to find it now, though. I <i>think</i> this may be my best bet, to flush out the old OC 0.6.5, Bootstrap.efi-requiring “OpenCore” boot entry, and replace it with a well-functioning one for OC 0.6.6. Anybody got insight into what that method was, or whether it’ll help my situation?

 

In the meantime, I’m booting from the USB’s EFI copy of OC 0.6.5, and may restore the main macOS NVME’s copy of OC 0.6.5 to its EFI, until I have a better way to move forward with OC 0.6.6. Thanks, all!

21 minutes ago, juan e. jot said:

I still seem to be having problems getting 0.6.6 up and running, with any version of my own config.plist & driver/.kext updates, or with AG’s very gracious 0.6.6 EFI, following his suggestion to ensure/update boot order in UEFI BIOS or F12, and then reset NVRAM during first OC 0.6.6 boot.

 

I think my trouble (black screens at either graphical OS selection or expanding choices to try to reset NVRAM; see below) has to do with the old OpenCore boot option persisting in UEFI BIOS, whether setting boot order in there or just choosing what OS to boot via F12. If I choose “UEFI OS,” I’m met by a blank screen before I ever see any OC-presented choices of what OS to boot up in. If I select “OpenCore,” I get a similar blank screen. If I have a USB with OC 0.6.5 in its EFI plugged in, I get an OC-presented list of choices of OS to boot into, and can space bar to expand the menu, and reset NVRAM. But when I boot again into what I believe to be OC 0.6.6 & get slightly updated graphical OS choices that seem to confirm this, then go to try to reset NVRAM to make SURE it’s set for a proper 0.6.6 boot… I get a black screen with no expanded choices (and hence no choice to reset NVRAM).

 

I seem to remember sometime in the past, a way when switching between OC & Clover, to clear the “OpenCore” boot entry from UEFI BIOS; not just disable, but remove. I can’t seem to find it now, though. I <i>think</i> this may be my best bet, to flush out the old OC 0.6.5, Bootstrap.efi-requiring “OpenCore” boot entry, and replace it with a well-functioning one for OC 0.6.6. Anybody got insight into what that method was, or whether it’ll help my situation?

 

In the meantime, I’m booting from the USB’s EFI copy of OC 0.6.5, and may restore the main macOS NVME’s copy of OC 0.6.5 to its EFI, until I have a better way to move forward with OC 0.6.6. Thanks, all!

Press F12 at start up and then select your boot drive (not OpenCore bootstrap) reset nvram, go into the bios and set order so only your OS X boot disk is selected (not OpenCore bootstrap) and restart and done.

On the next boot up it will set it correctly, and the bootstrap will be selected and working.

 

If for some reason that’s not enough to clear it then pull your mains cable and remove the bios battery for 5 mins or if you want to be even more extreme then reflash your bios and it will kill all traces but that’s a last resort.

less extreme, disable the boot strap in the config and then do any of the above then set it back to full when done.

All methods should work if not one of them definitely will.

 

Edited by AudioGod
1 hour ago, panosru said:

I wonder if anyone tried the F12l BIOS

 

Nope not tried it, but it's strange that F12K has been removed.  Might give it a whirl & see what happens! :blowup::hyper:

Edited by jimborae
  • Like 1
7 minutes ago, jimborae said:

 

Nope not tried it, but it's strange that F12K has been removed.  Might give it a whirl & see what happens! :blowup::hyper:

Do It, Do It, Do It.....:hysterical:

Go for it dog, you have nothing to loose and just roll back if you don’t like it.

 

P.S They removed F12K because it’s a beta bios, anything with a letter after the number is beta.

  • Haha 1
1 minute ago, AudioGod said:

Do It, Do It, Do It.....:hysterical:

Go for it dog, you have nothing to loose and just roll back if you don’t like it.

 

P.S They removed F12K because it’s a beta bios, anything with a letter after the number is beta.

Flashing now. :bye::hysterical:

  • Like 1

Yep nothing too disasterous report with bios F12l so far. The only issue I might be seeing is the Smart Fan 5 control profiles seem to be a bit fubared, in that I try & disable them for System Pump 5 & 6 board connectors and it doesn't seem to stick & always re-enables them. Need to play a bit more to see if I can work it out.  

 

In my case it's irelevant really anyway as System Fan 6 Pump is only used to monitor the flow rate and not actually control the DC5 water pump's voltage/speed. 

Edited by jimborae
×
×
  • Create New...