#
✕ nick:marcan
#asahi · 2023-08-16 02:50
marcanand there are big hex IDs involved which I doubt are constant
#asahi · 2023-08-16 02:50
marcannicolas17: yes, it's at the very least per-machine-type
#asahi · 2023-08-16 02:45
marcanassuming there's nothing particularly unique about an empty APFS disk image
#asahi · 2023-08-16 02:45
marcanI wonder if I can just do this again and take a disk image of the empty recoveryOS container and publish it, that would make this mess a lot easier to solve for people
#asahi · 2023-08-16 02:42
marcanthanks
#asahi · 2023-08-16 02:40
marcan(for those unaware: where I say "unrecoverable state" I mean without a full wipe. DFU full wipe always works but wipes your data.)
#asahi · 2023-08-16 02:37
marcan*recover
#asahi · 2023-08-16 02:37
marcanbut as long as you have Linux as the default OS and the installer did its job properly with recoveryOS (which it had to, otherwise step2 wouldn't have worked), you can recovery
#asahi · 2023-08-16 02:37
marcanthe reason this state is dangerous is that if there's a problem with your default boot OS/recoveryOS *then* you end up in an unrecoverable state as there's no way to switch OSes without a working recoveryOS
#asahi · 2023-08-16 02:35
marcan(for back to linux just reboot, assuming that's still your default boot OS)
#asahi · 2023-08-16 02:33
marcanthen back to linux and edit the partition type back to what it needs to be (modern fdisk should have it in the list), and set the name too just in case if it went away
#asahi · 2023-08-16 02:32
marcanthen finally `diskutil apfs deleteVolume <old default volume>` (to delete the other volume than Recovery that the eraseVolume created)
#asahi · 2023-08-16 02:32
marcanfor <container device> use the synthesized disk (disk2 or whatever shows up after you format it)
#asahi · 2023-08-16 02:32
marcanyes presumably
#asahi · 2023-08-16 02:32
marcanthen `diskutil list` again to see what you have, `diskutil apfs addVolume <container device> apfs Recovery -role R` to create the Recovery volume
#asahi · 2023-08-16 02:30
marcan`diskutil list` to get the state of things, `diskutil eraseVolume apfs RecoveryOSContainer <partition>` to format the partition properly
#asahi · 2023-08-16 02:29
marcanwhich is what you wiped
#asahi · 2023-08-16 02:29
marcanbecause that forces system recoveryOS fallback
#asahi · 2023-08-16 02:28
marcanwhat happens if you hold the power button for 10s?
#asahi · 2023-08-16 02:28
marcanmake sure you hold it and don't double tap it or anything like that
#asahi · 2023-08-16 02:27
marcanthat should get you into paired recoveryOS for whatever OS is your default boot OS right now
#asahi · 2023-08-16 02:27
marcanyes
#asahi · 2023-08-16 02:27
marcanthat partition is the system/fallback recoveryOS
#asahi · 2023-08-16 02:27
marcanwhy not?
#asahi · 2023-08-16 02:27
marcanit can recover from that state (empty but present and correct recovery container)
#asahi · 2023-08-16 02:27
marcanboot into recoveryOS, format it as APFS, create the Recovery container with the correct role ('R'), delete the default container it created, go back to Linux, fix the partition type GUID which diskutil will have screwed up (and make sure RecoveryOSContainer is still the name just in case), then do a Revive with Apple Configurator
#asahi · 2023-08-16 02:25
marcantook me a while to figure it out
#asahi · 2023-08-16 02:25
marcani509vcb: there's a known fix for borking that partition
#asahi · 2023-08-15 02:18
marcan(the Android driver is a completely different one, so you have to rewrite/reengineer all of the code, but at least you can copy the firmware interface definitions and figure out how it works from that)
#asahi · 2023-08-15 02:17
marcanmost of the functionality is present in various random out-of-tree Android vendor dump kernels, so it isn't really reverse engineering, just porting features from those giant mess source dumps into the proper upstream driver
#asahi · 2023-08-15 02:16
marcanI can take care of new hardware bring-up and basic "stuff is broken" cases, but I can't really spend more of my time adding all the missing features right now :(
#asahi · 2023-08-15 02:15
marcanwe really could use a volunteer to help improve it (seeing as the guy from Broadcom who is supposed to be the maintainer isn't actually doing much)
#asahi · 2023-08-15 02:15
marcanyeah, the broadcom driver is *seriously* behind in modern WiFi features
#asahi · 2023-08-12 06:23
marcanmkurz: done
#asahi · 2023-08-10 11:10
marcan(I might have to worry about it for the CI cluster if it gets busy, but I doubt it :p)
#asahi · 2023-08-10 11:10
marcanmost people probably don't reboot every hour, so I wouldn't worry about that
#asahi · 2023-08-10 11:09
marcanj`ey: as for NVRAM, it's NOR Flash, rated for 100K P/E cycles, split across two NVRAM banks, so assuming you reboot hourly 24/7 and each boot writes to NVRAM once, that'll run out after 22 years
#asahi · 2023-08-10 11:01
marcan(and also when you do anything with m1n1 proxyclient, otherwise after 5 or so reboots you get dumped into recovery)
#asahi · 2023-08-10 11:01
marcanj`ey: the panic counter is in PMC SRAM, not nvram (we clear it on normal successful boots from linux)
#asahi · 2023-08-10 11:00
marcanthough I would normally recommend only restoring part of it, stuff you need and settings you know you want to keep, rather than dumping the whole thing in wholesale, since some apps could be different versions and not like it (rare but possible)
#asahi · 2023-08-10 11:00
marcanit's basically just reinstalling from scratch, with backup+restore of /home
#asahi · 2023-08-10 10:59
marcanhome is not usually a separate partition by default so you can't just keep it anyway, this is the usual process on most machines
#asahi · 2023-08-10 10:59
marcanhandlerug: tar up your home partition onto external media, wipe everything, install again, restore it (and fix any permissions issues etc)
#asahi · 2023-08-09 12:02
marcanit's the new shiny, I would highly recommend it over ALARM :p
#asahi · 2023-08-09 12:02
marcanfedora should work :p
#asahi · 2023-08-09 12:02
marcanthe builds for alx.sh don't support 13.5 yet and that machine requires 13.4+, therefore the intersection of supported firmware versions is empty
#asahi · 2023-08-09 12:01
marcanyeah that's expected
#asahi · 2023-08-09 12:01
marcanon what machine?
#asahi · 2023-08-09 12:00
marcanoh the alx.sh installer?
#asahi · 2023-08-09 12:00
marcanI'll need the installer log (at least the stuff it prints to the console) to see what happened

plus ›