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

211–220 of 290 posts

Re: macOS Sonoma Boot Failures

#211

Post by _lvbh »

jamesfmilne wrote: post #61
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.

I deleted the MacOS installation on my (older) Mac. Linux works well enough

Re: macOS Sonoma Boot Failures

#212

Post by wizzard0 »

FYI the Asahi Linux installer says “please upgrade that should help” but bumping 13.6 -> Sonoma 14.1 did not help, the SystemRecovery still shows up as 13.5

Or does that mean wait for 14.2?

Re: macOS Sonoma Boot Failures

#213

Post by lvncelot »

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…

It's somewhat endearing that a trillion dollar company goes through something similar as I did - fiddling around with rEFInd, my BIOS splash image, plymouth-git & plymout-sddm, "quiet splash" and god knows what else to get a "smooth" boot experience - not only adding several seconds to the boot process but also having to rescue the system multiple times with a boot stick.

I've come to embrace the flicker and the systemd messages. It's just a boot, it's in the order of seconds in this day and age, I can't even tell you what the initial reason for my obsession was.

Re: macOS Sonoma Boot Failures

#214

Post by fsflover »

coldtea wrote: post #208
kelnos wrote: post #174

Earlier quoted context omitted.

So essentially, the situation you'd have if you'd bought a Mac? If we want to compare apples to apples, then we compare: Mac with macOS updates installed regularly, and only those provided by Apple. Non-Apple apps get dropped in /Applications like they should be. If there's an installer that asks for root access, you might get boned. Linux preinstalled with OS updates installed regularly, and only those provided by t…

> So essentially, the situation you'd have if you'd bought a Mac? No, worse, with more device incompatibilities, manual fiddling, arcane settings, and so on to make things work. > Sure, if you have a Mac and disable SIP (or whatever it's called nowadays) and start mucking around with files in /System or whatever, because you want to install some mod that does something cool, you might have a bad time. Sure, but I'm n…

> with more device incompatibilities, manual fiddling

Did you read what I wrote above? "if you buy preinstalled"

If you install Linux on an ordinary "Windows-certified" computer, you will have problems. If you install an alternative OS on a Macbook, you will have exactly the same problems.

Re: macOS Sonoma Boot Failures

#215

Post by pjmlp »

doublerabbit wrote: post #145
userbinator wrote: post #139

Earlier quoted context omitted.

For those who haven't seen it: https://www.youtube.com/watch?v=XTaNi6uL41s BIOSes of the time were all written in highly-optimised Asm, and I suspect those little "easter eggs" they added were because the programmers knew they had enough space left over to put some more fun stuff in. There was also AMI WinBIOS that provided a GUI, but I remember it being much less featureful than other BIOSes of the time with a TUI a…

A 90's TUI that will forever be more productive than Windows 11.

As someone with experience in Turbo Vision and Clipper, I don't miss them, beyond some nostalgia from simpler times.

Re: macOS Sonoma Boot Failures

#216

Post by bluescrn »

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

Emulation is one case where specific refresh rates are desirable.

Would be nice if I could force my MBP to run at 100Hz for PAL Amiga/C64 emulation - or even better if emulators could/would change the refresh rate at least when running full-screen.

(Actually, since Sonoma, I can manually set it to 50Hz, but there's no fixed refresh rate options above 60Hz, just 'Pro Motion'. Previously, the refresh rate setting seemed missing entirely on my M1 MBP)

Re: macOS Sonoma Boot Failures

#219

Post by bigDinosaur »

cirrus3 wrote: post #153

First I've heard of any issues.. I have done a couple upgrades already with no issue. I'm sure there are some scenarios where it fails, but Sonoma has been out a while with millions of users being prompted constantly to upgrade. Feels like less than a "you're holding it wrong" problem. HN is obv going to bring out the edge cases, but it doesn't seem like the world is on fire with "Sonoma Bricks" by any means.

I use a lot of Apple products but this attitude you're expressing has always annoyed me (because I see it most frequently when it comes to Apple's software and hardware quality). These bugs affect people all the time and are indicative of poor QA. 5 users at a company we provide some software support for (note: we don't control their machines) decided to upgrade their machines and somehow became unbootable just yesterday. Please don't be in denial about Apple's increasingly worse QA. An intern with a checklist could have uncovered these issues.

Re: macOS Sonoma Boot Failures

#220

Post by coldtea »

fsflover wrote: post #214
coldtea wrote: post #208

Earlier quoted context omitted.

> So essentially, the situation you'd have if you'd bought a Mac? No, worse, with more device incompatibilities, manual fiddling, arcane settings, and so on to make things work. > Sure, if you have a Mac and disable SIP (or whatever it's called nowadays) and start mucking around with files in /System or whatever, because you want to install some mod that does something cool, you might have a bad time. Sure, but I'm n…

> with more device incompatibilities, manual fiddling Did you read what I wrote above? " if you buy preinstalled " If you install Linux on an ordinary "Windows-certified" computer, you will have problems. If you install an alternative OS on a Macbook, you will have exactly the same problems.

>Did you read what I wrote above? "if you buy preinstalled"

And did you understand my point? Buying preinstalled isn't a cure-all, only ensures that the bundled hardware drivers are compatible and configured. That's a pretty low bar.

It doesn't cover doing stuff with third party devices (which on the Mac 99% of the time it works every time).

Not to mention even the bundled-hardware doesn't always work even if you buy pre-installed (like the laptop not sleeping properly for example).

Post reply on HN