This is exactly why I lag one major version behind the latest.
Well, this also affects the previous major version, macOS Ventura 13.6
Just don't upgrade to any version ending in 0.
macOS Sonoma Boot Failures
91–100 of 290 posts
Re: macOS Sonoma Boot Failures
#92Earlier quoted context omitted.
EFI config screens should be text mode only, full-stop. So they can easily be used over serial console redirection. Ran into one recently that was high-rez graphical. It needed a USB mouse to change critical settings because the tab order for the onscreen widgets didn't work. Anyone responsible for creating graphical EFI config screens should stop writing software for the good of humanity.
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.
Re: macOS Sonoma Boot Failures
#93Earlier quoted context omitted.
Apple still hasn't put up any official page about the issue though, nor does it appear they've pulled the update. Even if it missed QA, why haven't they made any official comment?
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.
Re: macOS Sonoma Boot Failures
#94Earlier quoted context omitted.
> Aren't CSS animations capped at 60, same as requestAnimationFrame? Did some quick Googling to make sure I wasn't just out of the loop on this, as far as I can tell they are not the same: https://github.com/whatwg/html/issues/5025
Can you point me to the part confirming your claim? If anything, it's confirming mine that they both are stuck at 60 Hz.
The link says:
> As such, on their 120hz devices, requestAnimationFrame is throttled to 60hz, whereas CSS animations run at 120hz.
Please let me know if I am misunderstanding, it has been a few years since I've done this type of work.
Re: macOS Sonoma Boot Failures
#95See also his twitter for some speculation as to how on earth simply changing refresh rate would cause boot corruption: https://social.treehouse.systems/@marcan/111329614147717090 >Why? I can tell you why: because Apple hates display modeset flicker, and switching modes between ProMotion on/off causes a modeset flicker, so of course they made it so that is stored in nvram somewhere and applied when the screen is turne…
Interesting. I wonder why anyone would turn ProMotion off considering that 120Hz massively improves responsiveness. I've only encountered one app that doesn't work with variable refresh rate and that's Genshin on Windows. Even that's probably not an issue with newer monitors that can handle VRR down to 60Hz without my monitor's frame-doubling flicker as it keeps switching been 60Hz and 120Hz
I wonder why anyone would turn ProMotion off considering that 120Hz massively improves responsiveness.
...and I bet that's exactly the attitude Apple had when implementing things, which lead to this mess.
Re: macOS Sonoma Boot Failures
#96Earlier 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.
[deleted]
Re: macOS Sonoma Boot Failures
#97Interestingly I ran into this exact problem with my work MacBook Pro M1 upgrading to Ventura 13.6 and assumed it was a totally isolated incident. I don't have a dual-boot setup either, just a single macOS install. The computer was connected to a Thunderbolt Display during the update which I assume had the same effect of changing the refresh rate to something other-than-ProMotion that the linked article mentions. I ha…
Also what's with the magic trick of entering DFU mode by pressing the buttons at a very specific time for a very specific number of seconds? Felt like singing a song to some fictional Mac OS gods and hoping for the stars to align for the laptop to show up in the second Mac.
Ah, also the port you use for the USB-C cable matters!! Has to be the first from the left? But why?
Anw, I followed a video by Mr. Macintosh and managed to get mine up and running, whew.
Re: macOS Sonoma Boot Failures
#98Earlier 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.
>Of course they do.
Where? Do you have any examples?
Re: macOS Sonoma Boot Failures
#99Had another weird refresh rate bug with 14.1 - external display doesn’t have a HDR option in settings at 120hz anymore - only works with HDR if I change the refresh rate 100hz or lower. Was fine in earlier MacOS
Re: macOS Sonoma Boot Failures
#100Earlier quoted context omitted.
Good UEFI like Surface devices is native resolution so you can have flicker-free boot. My Gigabyte motherboard recently got native resolution with a UEFI update.
I don't understand why modeset causes flicker - fade to black, turn off screen, change resolution, turn on screen, fade to image.
This summer I went into an apple store, and there was this 2019 Intel Mac Pro tower hooked up to the shiny 6k XDR display. I brought up the System Settings, and set the resolution one notch towards "More Space". It faded to black and never came back.