OVERKILL
$100 Site Donor 2021
@bunnspecial can likely relate this this.
So, after going down the rabbit hole on OpenCore, I of course was pulled back into the enthusiast community, something I'd been out of when I was just comfortable with my Mac the way it was.
I had an odd video issue that a post on MacRumours gave me a lightbulb moment for a workaround, which I then posted there. Basically, with a Kepler architecture GPU, if you have both HDMI and DisplayPort screens connected, you'll only have video on HDMI. However, if you boot with just DisplayPort, it will work fine. Ergo, I just disconnected my HDMI screen as a troubleshooting step and then reconnected it once the OS had booted and it showed up with both displays perfectly. Weird quirk.
This got me reading through threads there.
Another odd issue developed: AirPlay would stop working when the screen locked. On most Mac desktops the default is for the screen to go to sleep, then, after a period, it locks. The music would continue to play when the screen went to sleep, but would stop and then do little "blips" of music once the lock had kicked in. Wake it up and log back in, problem stops and music plays normally. I'll be playing around with that a bit, going to try disabling screen lock as a troubleshooting measure. I've already disabled it going to sleep, as when it tries to do that, it seems to cause several applications to crash and I have to reboot before being able to launch any of them again, or at least that's my theory as to what seems to be causing it to crap out when I wake it up in the AM.
So, after posting about that one, I saw a firmware thread. I had installed Mojave the instant it was available and was subsequently on bootROM 138.0.0.0.0. Despite being on the latest version of Mojave, subsequent updates didn't update the bootROM. Interesting.
So, that was my adventure for today. Download High Sierra. Install another SSD. Install High Sierra, download Mojave 10.14.6 full installer, run it, it prompts for firmware update, do the update. Check that computer is now on 144.0.0.0.0? Golden! Shutdown, swap back to my Big Sur SSD.
Apparently, there was a relatively long list of fixes that were implemented between the version I was running and this most recent. Odd that Apple didn't push it out as part of the cumulative updates, but then, it's Apple, so...
We'll see how the adventure continues!
I find it quite amusing that there are so many people out there that are continuing to use these now 12 year old (and in some cases older, if they have a 4,1) computers as their daily machines. They have an incredible following.
So, after going down the rabbit hole on OpenCore, I of course was pulled back into the enthusiast community, something I'd been out of when I was just comfortable with my Mac the way it was.
I had an odd video issue that a post on MacRumours gave me a lightbulb moment for a workaround, which I then posted there. Basically, with a Kepler architecture GPU, if you have both HDMI and DisplayPort screens connected, you'll only have video on HDMI. However, if you boot with just DisplayPort, it will work fine. Ergo, I just disconnected my HDMI screen as a troubleshooting step and then reconnected it once the OS had booted and it showed up with both displays perfectly. Weird quirk.
This got me reading through threads there.
Another odd issue developed: AirPlay would stop working when the screen locked. On most Mac desktops the default is for the screen to go to sleep, then, after a period, it locks. The music would continue to play when the screen went to sleep, but would stop and then do little "blips" of music once the lock had kicked in. Wake it up and log back in, problem stops and music plays normally. I'll be playing around with that a bit, going to try disabling screen lock as a troubleshooting measure. I've already disabled it going to sleep, as when it tries to do that, it seems to cause several applications to crash and I have to reboot before being able to launch any of them again, or at least that's my theory as to what seems to be causing it to crap out when I wake it up in the AM.
So, after posting about that one, I saw a firmware thread. I had installed Mojave the instant it was available and was subsequently on bootROM 138.0.0.0.0. Despite being on the latest version of Mojave, subsequent updates didn't update the bootROM. Interesting.
So, that was my adventure for today. Download High Sierra. Install another SSD. Install High Sierra, download Mojave 10.14.6 full installer, run it, it prompts for firmware update, do the update. Check that computer is now on 144.0.0.0.0? Golden! Shutdown, swap back to my Big Sur SSD.
Apparently, there was a relatively long list of fixes that were implemented between the version I was running and this most recent. Odd that Apple didn't push it out as part of the cumulative updates, but then, it's Apple, so...
We'll see how the adventure continues!
I find it quite amusing that there are so many people out there that are continuing to use these now 12 year old (and in some cases older, if they have a 4,1) computers as their daily machines. They have an incredible following.