Man, I had a rough week last week. Shipped two regressions. Seeing this story, as awful as it must be for the responsible eng, has really made me feel much better. Not schadenfreude. Just commiseration.
macOS Sonoma Boot Failures
201–210 of 290 posts
Re: macOS Sonoma Boot Failures
#202Earlier 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.
Text UIs don’t actually require different resolution and refresh rates. Even Macs can boot into a text mode, but there’s no jarring mode-change flicker when it switches in and out of it!
Besides, there’s nothing to prevent you having a nice graphical boot configuration while still having a text version as a fallback (which is exactly what Intel Macs do)
Re: macOS Sonoma Boot Failures
#203Earlier 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.
[dead]
Re: macOS Sonoma Boot Failures
#204Earlier quoted context omitted.
Text-only BIOS setup was the norm for a long time before the stupidly bloated EFI graphical stuff became common. Even then, there were the better full-featured TUIs: https://upload.wikimedia.org/wikipedia/commons/0/05/Award_BI... https://liveusb.files.wordpress.com/2010/05/awardbios-firstb... And the simplified crap with tabs that often came with prebuilt PCs but later seems to have spread to others too: https://cdn.…
To my horror, I recently had to visit the UEFI firmware setup of a Lenovo tablet.... That was touch enabled.
And it is to be expected to be able to configure a touchscreen device using the touchscreen.
Re: macOS Sonoma Boot Failures
#205there's something fundamentally wrong at apple theses days, macos just doesn't work like it used to
Re: macOS Sonoma Boot Failures
#206Interestingly 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…
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.
But how would they then keep up their profit margins to keep shareholders happy? Their first obligation is to the shareholder, not to the customer.
(I think it is ridiculous that the system works in that way, especially for a company that hasn’t needed investors in over a decade, but it is what it is.)
Re: macOS Sonoma Boot Failures
#207Not 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.
The logic Board failed in my 2020 M1 Air as well. Opened the lid one day, and it wouldn't power on. I have AppleCare on it, otherwise it would have been a $500 repair. About two weeks ago I'm sitting in a hotel room with the air on bed with the lid open. I grab it by the screen to slide it closer to me and the screen shatters from the light pressure of my finger. There are instances of both these things happening to…
My wife is still rocking a 2012 Mac air and uses it regularly. Apart from never rebooting it - WHAT ABUT MY TABS - its a sturdy little fellow.
Shame to hear the build quality in the latest is so poor.
Re: macOS Sonoma Boot Failures
#208Earlier quoted context omitted.
As long as you don't do anything with it on your own.
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 not talking about that. With Linux you often have a bad time trying to make basic, but not distro configured, functionality to work.
Re: macOS Sonoma Boot Failures
#209Earlier quoted context omitted.
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.
By the standard of "do you ever need to consult forum posts to solve a problem", sure, Linux is worse than macOS. By the standard of "do you ever need to consult forum posts to fix hardware that has apparently been bricked by a software update", macOS seems to be considerably worse. At least, that's my experience. I've never had hardware damaged by Linux, which I've run almost exclusively. On the other hand the one A…
> macOS seems to be considerably worse
Most users will just take their machine in to the Apple Store when this kind of thing happens, rather than try to fix it themselves.
Re: macOS Sonoma Boot Failures
#210Today 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…
Yeah the Apple bootloader and restore stuff scares the shit out of me. The network access requirement, firmware on SSD and hardware lock are always lurking waiting for the most inconvenient time to go wonky when I hose something. Conversely windows, just got a USB stick in the drawer I can boot off.
> Conversely windows, just got a USB stick in the drawer I can boot off.
Linux as well. Will probably work better than windows on older hardware