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

71–80 of 290 posts

Re: macOS Sonoma Boot Failures

#71

Post by user9163 »

neilalexander wrote: post #3

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

ya - I cant update my m1 macbook air without going into DFU mode and using configurator to “revive” my macbook. Otherwise it just tells me “Failed to personalize the software update”. Made the mistake of going to the Apple Store where they promptly restored my machine deleting all my data - only to encounter the exact same issue when the next update is shipped. This way you cant even show them that their fix did not actually fixed it permanently.

Re: macOS Sonoma Boot Failures

#72

Post by da768 »

Can something be done using VoiceOver boot mode? I've already recovered macs stuck on 0 brightness after an upgrade with that... Can't find the documentation now, but it definitely exists.

Re: macOS Sonoma Boot Failures

#73

Post by JasonSage »

tripdout wrote: post #59
jwells89 wrote: post #43

Earlier quoted context omitted.

The messiness of resolutions during boot always annoyed me on PCs. It was understandable back in the days of BIOS, but ith the advent of UEFI it seems like it should be possible to run EFI config screens and the like at monitor native rez (or at minimum, native aspect ratio) but I’ve never seen this… it’s always 1024x768 or somesuch stretched to fit a 16:9 monitor which looks awful.

My old AM3+ motherboard has an option for full screen boot logo, and it starts in full HD, continuing with systemd boot, all in 1080p. I thought this wasn't really a problem anymore.

This is fine if you have a 1080p monitor. I was impressed when this first happened to me, now on an ultrawide monitor it’s back to being not great.

I do recall my last motherboard had an option for a splash which was centered in a black screen, so you could basically display it at native resolution with no stretching and it would look great and seamless. I wish every motherboard had that splash option now.

Re: macOS Sonoma Boot Failures

#74

Post by codr7 »

mort96 wrote: post #51
tpmx wrote: post #46

Earlier quoted context omitted.

This is depressing. They clearly have they ability ($$$) to do the required amount of manual QA, but don't. Or there was QA and someone decided that your case still wasn't enough to hold up the release. In my mind, when we pay that ridiculous Apple premium on RAM and storage, we pay for excellent quality in SW/HW. They also need to deliver that quality.

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.

Used to be, while Jobs was still around.

These days it's just a bunch of wannabes trying too hard to be him.

Re: macOS Sonoma Boot Failures

#75

Post by shever73 »

racl101 wrote: post #4

I am so terrified of this upgrade that I think I'll wait a whole year. That's not a good thing.

That’s probably wise. I wish I had waited. Since upgrading to Sonoma, I have recurring issues with the system file dialog. Sometimes the dialog will open, but not allow me to save, other times it will just fail to open altogether.

Any time I start a new video project now, I save it instantly because Command+S still works, but if it opens the Save As dialog then it frequently won’t.

Re: macOS Sonoma Boot Failures

#76

Post by mjg59 »

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.

"Fade to black, turn off screen, turn on screen, fade to image" is just slower flicker.

Re: macOS Sonoma Boot Failures

#77

Post by beebeepka »

Wowfunhappy wrote: post #68
beebeepka wrote: post #66

Earlier quoted context omitted.

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.

Aren't CSS animations capped at 60, same as requestAnimationFrame?

I've been advocating (and using) high refresh displays for over two decades and I find your reasoning preposterous. Downgrading to crappy 60 Hz monitor for nothing.

Re: macOS Sonoma Boot Failures

#78

Post by FirmwareBurner »

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?

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.

Re: macOS Sonoma Boot Failures

#79

Post by dgellow »

SpaceManNabs wrote: post #48

This seems like a very unusual bug by Apple standards. Makes me consider upgrading to new macbooks...

At this point it’s kind of common knowledge to wait a while before upgrading macOS to latest major version. I don’t remember a major update that didn’t come with its own set of problems.
Post reply on HN