macOS Sonoma Boot Failures

Post by userbinator » Tue, Oct 31, 2023, 10:26 PM UTC

wannacboatmovie wrote: post #54

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.

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.

Post by tomxor » Tue, Oct 31, 2023, 10:28 PM UTC

jwells89 wrote: post #43

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…

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.

Post by londons_explore » Tue, Oct 31, 2023, 10:43 PM UTC

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.

Post by aetherspawn » Tue, Oct 31, 2023, 10:50 PM UTC

mattchamb wrote: post #7

Not sure if related, but my 2020 M1 macbook air bricked a week or so after upgrading to Sonoma. I was suspicious if this was related to the update. Luckily the logic board was replaced for free under warranty laws here, though it put me off switching to iphone which I was a day away from doing.

Post by vondur » Tue, Oct 31, 2023, 10:56 PM UTC

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.