9 ms·
Asahi Linux goes from Apple Silicon port project to macOS bug hunters
- JohnMakin 3y agoApple Pro M1 16-inch User here. I went to restart my machine (was plugged into a lightning hub with 3 monitors, I don't ever recall messing with refresh rates) and it went to update. At some point in the loading bar, the screen went black and then flashed an apple logo. When I pressed power, I could sometimes get the apple logo to display on boot, then it went dark. To me it looked like it wasn't booting at all but the machine is pretty quiet even when it's on so it was hard to tell what was happening. We went to do the firmware revival process using another mac and it would barely recognize the device depending on what we tried. Eventually we were offered the option to do a full system restore, and after many hours battling this, we decided to just lose the data on the machine. Luckily I keep most major stuff in cloud or in github, but I lost a significant amount of work from the previous 24 hours that ended up delaying a release and causing significant pain. For how much these machines cost, this is completely unacceptable. I know windows machines have their fair share of issues, but in 15 years of working on various windows and mac workstations this is the only time I've lost an entire drive.
- syx 3y agoThis is insane, was there additional software installed by your employer that might have conflicted with the updating process? In my case we have lots of remotely controlled macOS updates that get triggered and supervised by the company I work for.
- ljm 3y agoI wouldn't be surprised if MDM policies caused some funky shit to happen. I couldn't use the migration assistant on one machine because the policy blocked the recovery OS; it just silently failed and booted you back up into your main account.
- striking 3y agoThis is a now well-known bug having to do with multi-monitor setups or changing the refresh rate of the internal panel. MDM policies and other software couldn't write to NVRAM in a way that would cause this issue without the help of a bug in Apple's code.
- avidphantasm 3y agoThis sucks, sorry. Things like this are why I tend to wait until downtime (usually Christmas holiday) to upgrade to the latest macOS each year. This gives time for bugs to be discovered and fixed, and if there is a major problem, I have time to fix it.
- tambourine_man 3y agoAnd, if you can, always wait until X.1 or X.2 at least to upgrade.
- MagerValp 3y agoMe I just yolo the beta on my daily driver right after the wwdc keynote. If there are any issues I prefer to know straight away. Surprisingly I’ve never run into any major issues, only minor glitches.
- sgerenser 3y agoYeah, I always wait until at least X.1. There’s a bunch of people in my company’s Mac users slack group that have been complaining since 14.0 about WiFi/connectivity bugs (often having to reboot to get WiFi to reconnect). It was bad enough for the company to block 14.0 upgrades until 14.1 came out.
- striking 3y agoHi, in case you face these challenges again, put the target system into DFU mode and connect the configuring system using the appropriate USB-C port (only one will work). The DFU key combination is finicky for portable machines: connect a charger (preferably Magsafe so you can watch the power LED) and your configuring system, press and hold power to be sure the system is off (if doing this turned the system on, repeat this step), press left ctrl+option and right shift at the same time as the power button, count ten seconds, let go of everything but power until the device shows up as "DFU" in Configurator (you may be prompted to allow more accessories to connect to your configuring system before it does). If asked to perform a software update before/during reviving, choose "Quit and update" and start the process again. If you upgraded to 13.6 or 12.5 before facing these issues, you may have to enter recoveryOS instead of booting normally and perform a system upgrade to Sonoma. If done correctly (without choosing Restore), you will not lose data. If you can't do these steps yourself or think you will have trouble walking a family member through them, the Apple Store can do a revive for you (be explicit that they are only to revive the machine, not restore or replace). Full details at https://support.apple.com/guide/apple-configurator-mac/revive-or-restore-a-mac-with-apple-silicon-apdd5f3c75ad/mac https://support.apple.com/guide/apple-configurator-mac/reviv...
- ShadowBanThis01 3y agoMy 16" M1 MBP was bricked by the Sonoma update and had to be wiped by Apple. Fortunately, I keep most things on external drives. But it's still an egregious QA failure on Apple's part, as witnessed by the increasing number of reports. And Sonoma appears to be riddled with odd little bugs, manifesting as UI failures. Windows don't come up, or they come up behind others when previously they didn't. For example, disk images, when mounted, open a window as usual but that window appears behind others on the desktop so you're left wondering what happened. I just had keyboard input rejected with "boink" noises in a dialog raised by Safari, over and over. In the end I couldn't log into the site. The "About this Mac" item in the Apple menu did nothing, over and over... and sure enough, I just tried this, and it happened again. But when I started Screenshot to capture it and file a bug, it started working. This is the second day in a row this has happened. It's looking like a shitty Mac OS release.
- baq 3y agoI feel like I live in a parallel universe sometimes when I complain about things randomly breaking or never actually working and they say ‘I’ve been using MacBooks for the past ten years and literally nothing bad happened ever’ and here I am just about to break the one year milestone and I just don’t see the mythical Apple level of quality.
- microtonal 3y agoThe thing is that Apple devices are so widely used, that even if 0.1% of the users encounters an issue, it's still a huge number of people. Added to that, people who run into issues are more likely to complain online than people who don't. So, you don't live in a parallel universe, you're just one of the unlucky 0.1%. And yes, I have been using Macs for 16 years and have never had a catastrophic issue and neither one of my friends of family. The worst problem was kinda self-inflicted, pre-SIP I was once typing something along the lines onf sudo rm -rf /Library and then accidentally pressed enter. Yay for backups.
- threeseed 3y ago> It's looking like a shitty Mac OS release No this happens every Mac OS release for the last 20+ years. Sonoma has literally just been released and we only recently had the first major patch. So there will be bugs both known and unknown. Almost all by definition not fixed. As always if you are doing mission critical work then for any piece of software you should always hold off upgrading until at least a few major patches have been released.
- userbinator 3y agobut the machine is pretty quiet even when it's on so it was hard to tell what was happening. This is why I hate the loss of HDD and other activity lights. It's unfortunately not specific to Apple, but they're a leading offender of this "opaqueness" trend. I admittedly have little Mac experience but it sounds like you weren't able to boot from a USB and copy the files you needed off the drive? That's the usual approach when something like this happens with a PC. I've even done a bit of Hackintoshing and you can certainly boot the macOS installer and use the terminal there. There's currently a gray comment at the bottom of the discussion here lamenting the "smartphonization" of computing, and this is a great example of that. You're expected --- or rather, forced to be --- helpless and treat the machine (or "device") as disposable when something goes wrong, and the same goes for your data; unless you give up some ownership by letting some thirdparty store it for you, that is. (Then again, I own an Android where I can backup and restore the whole eMMC, so it's not a complete characterisation.) Relevant Douglas Adams quote: "The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at and repair."
- callalex 3y agoFor MacOS, iStat Menus, the replacement of the older open source MenuMeters is a hard requirement that should really be built into the OS.
- marci 3y agoIf only they could find a bug/vuln that makes it possible to bypass the "Dead/Corrupted SSD? Dead Machine feature" and make it possible to boot externally, no matter the state of the internal drive.
- nwellinghoff 3y agoWait, so you can't recover data off a drive if you analyze it from another machine? Surely this is only if the drive in encrypted right?
- watermelon0 3y ago> If you have a Mac with Apple silicon or an Apple T2 Security Chip, your data is encrypted automatically. Even if you don't have FileVault (macOS disk encryption) enabled, data on SSD (or NAND chips with Apple silicon) is encrypted, so it's quite unlikely that you would be able to recover anything. Not to mention that SSD/chips are soldered on the motherboard.
- vanchor3 3y agoIf the computer still turns on you can at least get to recovery and use USB-C/Thunderbolt disk sharing.
- samtheprogram 3y agoThis thread is referencing if the SSD fails. If the SSD fails, the computer won't turn on, and even if it could (which we wish were the case, but the T2 chip prevents), you couldn't use get anything off the disk because it's a dead SSD. In the event of an OS crash/issue, or just minor corruption, that might be an option. Related to the original article -- I'm not sure what is meant by DFU mode on a MacBook (only have heard of that on iDevices) so it's unclear to me if you can EFI boot into another OS. Given that it also affects Asahi Linux, sounds like you can't EFI boot into anything, even OS Recovery for Mac Sharing mode.
- unforgivenpasta 3y agoMuch better than the OSnews article that related Asahi[1] to the bug and when called out by marcan they stated that the headline would stay [2]. The article seems to have been deleted[3] at some point since the link from marcan goes to a 404 [1] https://social.treehouse.systems/@marcan/111334488235016591 https://social.treehouse.systems/@marcan/111334488235016591 [2] https://mstdn.social/@osnews/111334720022394898 https://mstdn.social/@osnews/111334720022394898 [3] https://www.osnews.com/story/137678/apples-macos-sonoma-makes-macs-with-asahi-linux-unbootable/ https://www.osnews.com/story/137678/apples-macos-sonoma-make...
- mekster 3y agoOSNews author seems to have something personal against Apple, it reads like a personal blog when it comes to Apple related news with completely biased writing and I stopped reading years ago.
- SllX 3y agoI mean at this point I’m pretty sure it is a personal blog but with an archive of OS-centric news from back when there was more variety in the field. But yeah, quit reading for the same reason. It’s one thing to be biased against a company, I have my biases too, but this was on another level.
- Reason077 3y agoLooks like the OSNews article has been removed now. I just get a 404.
- diffuse_l 3y agoThe author did say he's removing the article for now, and he'll upload a fixed article later [1]. [1] https://mstdn.social/@osnews/111335189028196715 https://mstdn.social/@osnews/111335189028196715
- mise_en_place 3y agoThis is a huge embarrassment for Apple, because a team of unpaid volunteers are superior to the supposed talent you are shelling out multiples of six figures to.
- geodel 3y agoOh yes, multiple six figures have always caught bug every single time at every other place than Apple.
- extrememacaroni 3y agoBricking your own devices with your own update is extremely amateurish and embarrassing. If Apple knew about shame that is.
- saagarjha 3y agoOk, let’s see your processes for shipping an update to a hundred million devices.
- cromka 3y agoThis wasn’t an issue in their rollout process, but in their QA that needs to test orders of magnitude less setups.
- saagarjha 3y agoPresumably they'd need to test more? Because I assume that whatever they tested passed QA and didn't include what Asahi is reporting.
- s3p 3y agoSemantics. Seems to me like OP was talking about the entire project of making and releasing the newest version. QA would most definitely be apart of that.
- 3y ago
- RicoElectrico 3y agoThis is what you get with the creeping smartphonization of general purpose computers. The x86 side doesn't look bright either due to MS slowly forcing TPM. There is a good reason UEFI is stored on a QSPI flash.
- jdiez17 3y agoWhile I hate the gradual death of general purpose computing as much as the next nerd, this bug in particular has nothing to do with it.
- userbinator 3y agoIt does --- if you consider that this doesn't happen on PCs, it only happened to Apple because they believe they own and control the whole software/hardware stack. On a PC, the situation is different. At worst, with bad GPU drivers, you can still fallback to good old 640x480 VGA, or a slightly better generic unaccelerated VESA framebuffer, and be able to troubleshoot from there.
- userbinator 3y agoCare to give a counterargument? I have several decades of experience with PC hardware.
- sounds 3y agoI can't think of one, so this is only a halfhearted attempt (not the GP here)... maybe he's focusing on the mismatched firmware vs. OS version and how that is more closely analogous to a bad BIOS flash? I'm undermining my own counterargument... On a PC, a bad BIOS flash is recoverable. Some have two BIOSes - like on video cards. Some have a recovery mode via a USB stick. And attaching a programmer to the SPI flash is also a viable recovery method... Maybe he doesn't think any of the mac firmware environment is really that different from a general purpose computer? Ok, I don't know what the counterarguments are. ¯\_(ツ)_/¯
- 3y ago
- antoineMoPa 3y ago> We do not understand how Apple managed to release an OS update that, when upgraded to normally, leaves machines unbootable if their display refresh rate is not the default. This seems to have been a major QA oversight by Apple. This sounds like a very weird edge case and it's very easy to say this sort of statement in retrospect, but I wonder what percentage of engineers would think of testing this specific combo beforehand.
- leonheld 3y ago> This sounds like a very weird edge case and it's very easy to say this sort of statement in retrospect As someone who works on embedded devices with a lot of experience with Hardware-in-the-loop testing, this is 100% a QA oversight. The way this feature is implemented screams "test it from boot to reboot". I wouldn't pick too much on a small company doing some basic BSP/application work for some HMI device or something like that, but this is the richest company in the world with major funds/infrastructure to be better than this.
- antoineMoPa 3y ago> The way this feature is implemented screams Do we have info about the implementation somewhere?
- stevenhuang 3y agoYes, we know the setting is persisted by storing the display configuration in nvram.
- phkahler 3y ago>> This sounds like a very weird edge case It's a single setting prior to a standard update. Now I'm not saying they should test every combination of settings, or even every individual setting. I'm more curious how there is any interplay between this setting and the update, and why that has any effect. On the surface it smells like a system design issue to me - like something is going in there on that shouldn't be.
- GTP 3y agoMaybe it's time for Apple to automatically take a snapshot of the system partition before an upgrade? (Does their filesystem support snapshots?)
- sillywalk 3y agoAPFS does support snapshots. Not sure how that would interact with the Signed System Volume thing. https://en.wikipedia.org/wiki/Apple_File_System https://en.wikipedia.org/wiki/Apple_File_System
- duttonw 3y agoother issue is space constraints, if you are at full capicity, you might not be able to afford those extra gb's for said operation.
- callalex 3y agoFor the price they sell their devices at, they could afford to throw in an extra hidden 50GB for a redundant system partition. Instead they choose to bilk customers for over $1/GB above the bare minimum.
- Wowfunhappy 3y agoSee also from yesterday: https://news.ycombinator.com/item?id=38089342 https://news.ycombinator.com/item?id=38089342
- someonehere 3y agoI’ll chime in with something a blogger once wrote. Paraphrasing here: “The current macOS (macos 11 at the time it was written) looks and feels like it was designed by someone who never used macOS and has only used an iPhone.”
- tw1984 3y agoResting & vesting employees in Apple managing this part of the system must be worrying on their next RSU grant amount.