Search results

I'd like to note that since Big Sur release, battery issues been poppin in troves everywhere, on a real hardware too. I had to replace mine. And I'm absolutely certain that during update something was done to it which borked it.

It behaves really oddly, only charges fully/stops charging when it's suspended or powered down. And after being powered down for some time it'll always show 86% charged, why that effin arbitrary number? There are 14 pages of similar battery issues due to BS upgrade at Apple's forum. I hope that...

Their 'power reset' just means powering down completely, because those laptops go into standby instead. I’ve already done more than that because I've physically detached the battery and cleared cmos Also, in current state it 'power resets' itself just by disconnecting the charger, before it...

40 times at least

Ok. I'm ordering a new battery then, should arrive next week. Also, it literally happened during the update, the laptop was on a fully charged battery and shut itself down during, which is extremely suspicious to me [possibly bizarre coincidence]

This is slightly reassuring, is there any way to definitely check that it wasn't applied? Battery health before the update was marked as good in both Linux and macOS [Catalina] There also threads popping up from the owners of original MacBooks with batteries suddenly failing after the update...

I have my config.plist set to MacBook 8,1 as that's what's recommended for Broadwell and during BigSur install it flashed firmware for said MacBook which can be found in APPLE's EFI folder and is attached below. Now the laptop can only be used on AC, when disconnected it instantly powers off...

Looks like it flashed firmware for MacBook 8,1, that's what I've had set in my config.plist as that's what is recommended for Broadwell. Found it in APPLE's EFI folder I mean, how the hell? Why it's even possible?

Reinstalled it via OpenCore and booted successfully via it, fixed some of my issues too, like broken Safari. So it looks like Clover totally botched the job. Marked as Solved

Yeah, OpenCore seems to think that it's an Update/Installer partition. It's the same one that I'm booting via clover, I think [the UUID corresponds to the 'data' one in APFS containers], I can see only two in both. I went straight from last Catalina to Big Sur 11.1 [from within it via clover]...

Ah, so that would explain my issues, was that ever resolved?

Managed to take a better photo but I'm out of ideas tbh

I tried debug version of OC with all debugging enabled and it's stuff related to OC, not kernel boot. It's increddibly slow too

Well, that wasn't very helpful, still stuck around that place, tried FakeSMC too, it's also extremely tedious to capture

Found the ramrod thing, let's see where it leads me

As you wish, I wanted to narrow it down nad make it clearer. I'm yet to enable debug and log but in meantime captured some screenshots. One below is second before reboot, it all looks very weird to me [ also, I've seen that ramrod thing mentioned somewhere.. ] Rest is stuff from the whole...

You're right it wasn't clear. I’ve captured some stuff but’ll post it in bootloaders subforum as it seems better suited.

I really appreciate that you're trying to help, but you're confused. The topic is about OpenCore, not Clover [or Clover/OC hybrid] and OpenCore has the driver that you've attached. The screenshot is no longer valid because as I've mentioned one comment below it, it goes further with DSDT, SSDT...

Managed to disconnect the battery, snaping my sdcard in half in the process. Got cmos reset as a bonus which scared the hell out of my as it enabled secured boot. It changed nothing in the end, looks like my lappy is perma-semi-****ed :) Seems like a proper ending after almost two decades of...

Erm, my Clover boot is fine, it's the OpenCore one that doesn't work What's the point of that HFS+ driver anyway? I'm using APFS.