Earlier quoted context omitted.
Exact same thing happened to me.
What kind of HW?
same specs as OP
macOS Sonoma Boot Failures
111–120 of 290 posts
Re: macOS Sonoma Boot Failures
#112Today I had to DFU restore my macbook because I wanted to reinstall it, but built-in restore over the web did not work. My base system was 13.2, it downloads all the files for 13.6, it filled bar to 100% and then spewed error. It's obvious that it's some incompatibility between 13.2 base system and 13.6 install. Apple quality is atrocious these days. One would have thought they would test the most basic scenarios bef…
Yeah the Apple bootloader and restore stuff scares the shit out of me. The network access requirement, firmware on SSD and hardware lock are always lurking waiting for the most inconvenient time to go wonky when I hose something. Conversely windows, just got a USB stick in the drawer I can boot off.
As a lifelong Mac user, it just now hit me how inconvenient locked down the restore process is.
Re: macOS Sonoma Boot Failures
#113Re: macOS Sonoma Boot Failures
#114Earlier quoted context omitted.
> they never EVER publicly admit any faults or mistakes with their products Of course they do. They’re just secretive in general, and keep communications edited. Compared to the word salad of modern companies on social media, I find it refreshing. Just fix the problem, issue replacements for those affected and move on quietly.
>Of course they do. Where? Do you have any examples?
> Where? Do you have any examples?
The whole battery gate saga. Touch Bar. The 2013 Mac Pro [1].
[1] https://www.theverge.com/2017/4/4/15175994/apple-mac-pro-fai...
Re: macOS Sonoma Boot Failures
#115On a much more minor note the .0 version of the upgrade also has a big that pops up a contacts window every few minutes and steals keyboard focus.
Re: macOS Sonoma Boot Failures
#116Earlier quoted context omitted.
>Of course they do. Where? Do you have any examples?
> Where? Do you have any examples? The whole battery gate saga. Touch Bar. The 2013 Mac Pro [1]. [1] https://www.theverge.com/2017/4/4/15175994/apple-mac-pro-fai...
Yeah but that only proves my original point that Apple only admits mistakes when the public scandals are so violent it can't possibly deny them anymore as the shit pile broomed under the carped has grown so large it makes even them trip on it, so then they just enter damage control mode and PR recovery but not out of the kindness of their heart but because of media backlash.
But they never have the common sense to release statements like "hey, the latest MacOS update might brick some systems so we're pulling the updated until we can do further testing and patching, if you've been affected by the bug already go to a Apple store and have it fixed for free".
Re: macOS Sonoma Boot Failures
#117Earlier quoted context omitted.
macOS is very good at adaptively reducing refresh rate when nothing is happening on screen, with the panel reportedly supporting the full range of 1-120hz so barring badly engineered apps that are permanently pinned at max refresh, the battery impact of keeping ProMotion on is minimal for most use cases.
Which raises the question even more why the refresh rate matters during early bootup - surely you could just start with an apple logo and a 1 Hz refresh rate, and then up the rate later during boot when it's time to do some animation...
Changing the refresh rate makes the screen go blank for a second or so.
GP of this thread links to a post arguing that Apple is going out of their way to avoid just that during the boot sequence.
Re: macOS Sonoma Boot Failures
#118Earlier quoted context omitted.
Even for text-only I’d prefer native rez if possible to reduce scrolling, label truncation, etc. That said yes, there’s no reason why there shouldn’t be a low rez textual fallback.
Then you'd need scaling and all that. Seems a bit overkill for something people rarely use.
scaling? nah, I'd say to just choose at runtime a sane text size (only to avoid using the same pixel size on a 1024x768 as a 5k screen) and set the number of rows and columns to fit the screen. Even if there isn't enough to fill the screen that's fine.
> Seems a bit overkill for something people rarely use.
Okay, but a lot less so than a full GUI with mouse and thousands of colors, like many motherboards have gone to.
Re: macOS Sonoma Boot Failures
#119Earlier quoted context omitted.
You clearly don't know Apple as a company. Last most big companies, they never EVER publicly admit any faults or mistakes with their products (unless forced to by large scale fiascos) because that would damage their perfect brand image. It's why they have comments disabled on all their social media accounts.
> they never EVER publicly admit any faults or mistakes with their products Of course they do. They’re just secretive in general, and keep communications edited. Compared to the word salad of modern companies on social media, I find it refreshing. Just fix the problem, issue replacements for those affected and move on quietly.
It's not "refreshing" to hide problems.
Re: macOS Sonoma Boot Failures
#120I had this exact thing happen to me when I tried to reset a Mac and wipe it clean. Would not start up and went into this doom loop when booting with the apple logo and a black screen. No amount of key combinations worked. I had to drop into DFU, which is a huge pain to get into to begin with and then use another Mac to recover.