From Newsgroup: comp.sys.mac.misc

On 2022-02-01, Ant <ant@zimage.comANT> wrote:

In comp.sys.mac.portables Ant <ant@zimage.comant> wrote:

In comp.sys.mac.portables Ant <ant@zimage.comant> wrote:

In comp.sys.mac.system Ant <ant@zimage.comant> wrote:
...

Since it's still a slow weekend, I decided to try resetting MBP's NVRAM >> > > first. So I told its macOS Big Sur v11.6.2 to shut down MBP, but it got >> > > stuck during its shutdown for like a minute with admin account's desktop
background (no icons and menu) for about a minute. Mouse cursor was still
movable. And then, it finally shut down. Weird lag. I booted it up, logged in, and then retried its shutdown. No long lags (only a second).

Anyways, I continued on to reset VRAM from
https://www.macworld.com/article/224955/how-to-reset-a-macs-nvram-pram-and-smc.html's
instructions, I did:

"Intel Macs

To reset your NVRAM, you use exactly the same procedure you once used to reset PRAM.

1. Shut down your Mac.
2. Press the power button, and as soon as you power up the laptop, hold down Command-Option-P-R.
3. Keep holding down those keys for about 20 seconds. Then let go and allow your Mac to continue starting normally..."

Step #3 took a while to start up again after pressing all keys down for >> > > about 20 seconds. I thought I messed up since my four fingers hands,
without thumbs, had a hard time pressing all. And then, about ten seconds later, MBP booted by itself. I hope that's normal.

Also, does "nvram ???-c" trick not work? It shows:
% nvram -c
nvram: Error clearing firmware variable fmm-computer-name: (iokit/common) not permitted
nvram: Error clearing firmware variable fmm-mobileme-token-FMM: (iokit/common) not permitted
nvram: Error clearing firmware variable fmm-mobileme-token-FMM-BridgeHasAccount: (iokit/common) not permitted
I even tried with sudo.

...

FYI. No new incidents so far. I hope it stays that way! :)

MBP was doing well until this morning, and then it wouldn't wake up this
morning after sleeping since late last night. And then, it powered on by
itself when I clicked on its trackpad. After logging in, it restored
previous sessions from the crash. :(

Again, it wouldn't wake up correctly this evening like this morning. It powered on by itself with its Apple logo chime after I clicked on the
old external USB mouse's button. After logging in back into the standard level account, Chrome said to restore previous sessions from the crash. I tried to reproduce it manually, but no luck. Its console's logs are confusing and so long. :( When I logged out and logged into the
admin-level account, then I saw its crash report that popped up for me
to to share to Apple and you guys: http://zimage.com/~ant/temp/MBP2020crashWhenWakingUp.txt.

I particularly like how you are doing everything you can to avoid
contacting Apple while the computer is in this problem state, so as to
avoid actually allowing anyone to diagnose and resolve the issue.
Instead, you fumble around until it's up and running again, so that
nobody on the planet can tell what was actually wrong. Good work, and
may you continue to "struggle" so that you can endlessly complain
without actually allowing anyone to help.

Mission accomplished! ; )
--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR
--- Synchronet 3.19b-Linux NewsLink 1.113