Jump to content

E6230: Big Sur error "The update cannot be installed on this computer"


ac23

Recommended Posts

  • Administrators

Go back to the installer main screen and open up Disk utility to reformat your target partition HFS+, i.e. Mac OS Extended (Journaled). It can't be a new volume on an existing container, that only supports APFS format, it'll have to be a separate partition. Adjust your disk arrangement as required.

 

Please note that, as stated in my guide, I reverted to Clover on what was an existing Big Sur installation made with OpenCore. I'm not 100% certain that you'll actually manage to complete a fresh Big Sur installation with Clover 5128 or r5129 (latter is also Ok to use and I've actually updated from r5128 to r5129). But give it a try, you'll soon find out. You say this is a fresh installation but you've actually downloaded Big Sur and initiated its installation from Mojave, not from a booted USB installer, haven't you?

  • Like 1
Link to comment
Share on other sites

Ah that makes sense as the guide didn't say to install VboxHFS/HFSPlus and I could't get Clover to see the Installer USB at first.

I'll install with the Opencore EFI then copy the newest Clover EFI over. I stayed with Catalina as the Big Sur Geekbench results did not match it - there were quite a few errors I noticed in the Opencore guide. Opencore does not need a DSDT - it reads it from the firmware for example. I'm hoping if the Geekbench is 1700+ with the new Clover pack then I will stay with Big Sur. I attempted my own Opencore build and go very close with the Geekbench but not compatible to your Clover Catalina/Mojave packs with Clover.

No, this is a clean install. As I already formatted my working Catalina partition ready to install Big Sur - I was without a working version of macOS to check over the clover install.
I keep Mojave on a drive and use it over eSATA for one application that will never been brought over to x64 - it comes in handy in situations like this.

Thanks for the tip, I'll read better next time.

BTW Why are you using Chrome?

Link to comment
Share on other sites

  • Administrators

That statement in Dortania's documentation about OpenCore not needing a DSDT is a little confusing and misleading. Possibly something lost in translation as one may say...

 

All bootloaders universally pull/read ACPI tables from BIOS (i.e. firmware). On paper, no Hackintosh bootloader needs a (patched) DSDT. It's just that over the years, ACPI patching developed greatly and what was done years ago through DSDT patching is nowadays done through dedicated SSDT patches that leave the loaded DSDT table more or less untouched. OpenCore came out at a time where such development had reached maturity, having already been vastly experimented and successfully used with Clover. That's for the story (or history)...

 

Focusing back on the E6230, I detailed the patches implemented back in 2018 to A19's original DSDT in my E6230 BIOS settings thread, so you may indeed rework them out through SSDTs or pre-programmed patches of the bootloader. It wouldn't be too difficult, most of them are well known and documented. The only patch missing in that list for the brightness keys and details are available here, in my E7250 guide or here, in my 7490 guide (same patches applied throughout). Jake Lo has also published SSDT alternatives for this brightness keys patch.

 

I was (and remain) too lazy to jump back into that and revisit, especially as Catalina or Big Sur work perfectly with my patched DSDT (even with OpenCore, Yes siree!). No issues and no worry to have on the matter.

  • Like 1
Link to comment
Share on other sites

Yeah I don't use a DSDT on my main desktop with Opencore, I don't even patch my SDST - I just use the premade ones. A few seconds added to my boot time is minor.

The issue with your Opencore E6230 was that the Geekbench scores fall short. I think the best I got out of it was low 1600s

I just installed with your Opencore pack and then replaced with your Clover pack and...I got a Geekbench score over 1700!!!!!!!


679541135_ScreenShot2021-02-03at12_52_35pm.png.30a38e307fa65087f29b03f6cb353923.png

Thanks again Herve, saved me a headache - I'm too lazy to fully go in on a opencore build myself as this is just my daily internet / YouTube machine.

Interestingly I only went to Big Sur because I've noticed a painful glitch...the latest Catalina update...the security patch from a few days ago...it causes the horrible video glitches. I thought f#ck it, I'll just go with Big Sur instead of getting my old Catalina pre update installer out. I really shouldn't have been so stupid to update or without a cloned backup.

I've noticed the same thing happens with Mojave with the latest update it had (few months ago update). Fortunately I rarely ever go in Mojave and don't use it for the internet so security patches aren't an issue. I've kept it one shy of the latest update to stop the graphics glitches.

No glitches in Big Sur now tho so all good :)

Thanks again.

Link to comment
Share on other sites

  • Administrators

I don't usually use GB5 but I just got about the same results as you: 774 & 1703. I'm not sure there is much to say or conclude about those benchmarks. Here's what I obtained with GB4.4.4:

  • Catalina/Clover: 3705, 7500
  • Big Sur/OpenCore: 3809, 7401
  • Big Sur/Clover: 3821, 7460

 

Strange about those graphics glitches you encounter in Mojave and Catalina. Not seen/experienced those. Did you have the Capri framebuffer memory patch in place? Anyway, water under the bridge if you're happy with Big Sur and it's fully functional with Clover

  • Like 1
Link to comment
Share on other sites

Yeah It is strange. I hadn't changed anything from your packs which were functioning great before the update so I assume the framebuffer memory patches were applied.

Yeah, Catalina is the past - the future is Big Sur on this machine...wow it is a lot smoother :)

Just need to fill in the missing drivers to get Filevault working again then hopefully no more messing for a while - Thanks again.

Link to comment
Share on other sites

I'm using your Clover pack. I'll check with the OC pack later today.

I did notice a slight decrease in GB5 score when using 11,1 compared to switching back 10,2 after the update."

I only did 1 test on each though, not a few tests though and average it.

One glitch I have noticed off and on through out my E6230 experience is a flash every few seconds when going Full Screen in Youtube in Safari.

I've noticed this with Mojave and Catalina but certain revisions/releases of the macOS would not cause the flash and I just stuck with them.

I forgot all about it until I updated, it was the one glitch I fought with for a while.

It's not going to stop me using BS though as overall I find it a more pleasant OS for day to day tasks.
Although tbh I wish I stayed at Catalina at the release before the latest security update as that was rock solid.
I could get back there but I'm too lazy as it would involved finding the exact revision as I'm sure if I used the Catalina install I had maybe 4-6months ago it will update to the latest security update bypassing where I was.

Anyway...BS 11.2 working fine on your Clover pack, thanks again.

edit: no BS is defiantly better for day to day. I like the separation of versions as I use Catalina for my work desktop. Keeps you in a different headspace :)

Link to comment
Share on other sites

×
×
  • Create New...