Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS Sonoma Boot Failures

github.com

Post reply on HN
Print view View original

61–70 of 290 posts

Re: macOS Sonoma Boot Failures

#61

Post by jamesfmilne »

vbezhenar wrote: post #15

Today 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…

Yes same here. I did install then uninstall Avahi Linux a year or so ago, but now I can't upgrade past 12.6.

I'll need to get an external drive, back everything up, then do a DFU restore on my M1 Max MBP to get it upgraded to Sonoma.

Re: macOS Sonoma Boot Failures

#62

Post by beebeepka »

ddalex wrote: post #60
wmf wrote: post #50

Earlier 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.

Fancy fade in/out effects this early?

Re: macOS Sonoma Boot Failures

#64

Post by Wowfunhappy »

jwells89 wrote: post #45
Wowfunhappy wrote: post #41

Earlier quoted context omitted.

> I wonder why anyone would turn ProMotion off considering that 120Hz massively improves responsiveness. The first reason that comes to mind is battery life. That's probably the most broadly applicable use case. But also, if I was still doing e.g. frontend web development, I would want to confirm that my css animations looked nice at 60 hz. Edit: My first use case is likely wrong, thank you to replies for reminding m…

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.

Oops, thank you, I completely forgot they were doing the adaptive refresh thing!

Re: macOS Sonoma Boot Failures

#65

Post by [deleted] »

krackers wrote: post #57
mort96 wrote: post #51

Earlier quoted context omitted.

Or they did QA but just happened to miss this issue. Most companies would consider "the upgrade sometimes bricks the device" to be a release-stopping bug, I'm betting Apple is among them.

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?

[deleted]

Re: macOS Sonoma Boot Failures

#66

Post by beebeepka »

Wowfunhappy wrote: post #41
NavinF wrote: post #38

Earlier quoted context omitted.

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. The first reason that comes to mind is battery life. That's probably the most broadly applicable use case. But also, if I was still doing e.g. frontend web development, I would want to confirm that my css animations looked nice at 60 hz. Edit: My first use case is likely wrong, thank you to replies for reminding m…

Why would 60 FPS CSS animations look bad on high refresh displays?

Re: macOS Sonoma Boot Failures

#67

Post by zippergz »

NavinF wrote: post #38
krackers wrote: post #5

See 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 turn it off because I can’t tell the difference and if it doesn’t improve anything for me, I might as well not have the system wasting battery and other resources on it.

Re: macOS Sonoma Boot Failures

#68

Post by Wowfunhappy »

beebeepka wrote: post #66
Wowfunhappy wrote: post #41

Earlier quoted context omitted.

> I wonder why anyone would turn ProMotion off considering that 120Hz massively improves responsiveness. The first reason that comes to mind is battery life. That's probably the most broadly applicable use case. But also, if I was still doing e.g. frontend web development, I would want to confirm that my css animations looked nice at 60 hz. Edit: My first use case is likely wrong, thank you to replies for reminding m…

Why would 60 FPS CSS animations look bad on high refresh displays?

Well the CSS transition wouldn't run at 60 fps, it would run at 120 fps, no?

An animation that looks slick at 120 fps might look too fast/slow/complex/whatever on a common 60 hz screen. So if I was still doing this sort of development, I'd prefer to be working on a 60 hz monitor.

Re: macOS Sonoma Boot Failures

#69

Post by fsflover »

coldtea wrote: post #58
fifteen1506 wrote: post #47

Earlier quoted context omitted.

And this is why there will never be a Year of the Linux Desktop -- no-one wants to have to depend on forum posts to fix these kind of issues. /troll

Why the "/troll"? You're 100% right non-ironically: the problem being that on Linux the need to consult forum posts to fix these kind of issues is way more frequent than in macOS.

On Linux it's as rare as on MacOS, if you buy preinstalled.

Re: macOS Sonoma Boot Failures

#70

Post by Wowfunhappy »

fifteen1506 wrote: post #47
miles wrote: post #30

Earlier quoted context omitted.

From comments #736 and #747 attached to the forum post you kindly shared, it sounds like simply disconnecting and reconnecting the I/O board may be sufficient (found those comments linked in #831): https://forums.macrumors.com/threads/macos-big-sur-update-br... https://forums.macrumors.com/threads/macos-big-sur-update-br... https://forums.macrumors.com/threads/macos-big-sur-update-br...

And this is why there will never be a Year of the Linux Desktop -- no-one wants to have to depend on forum posts to fix these kind of issues. /troll

This issue in GP is unrelated to Linux, it happens on single-boot macOS.
Post reply on HN