2021-12-24

<NightRaven[m]> question do i always need to have the second computer to use wifi or can i enable it once and that is it i can have wifi when i reboot
<mps> finished build, now will reboot and see
<mps> hm, not enough just these two, have to enable more codedump and some other. ok will build complete new kernel and reboot

2021-12-23

<mps> ok, though I already rebooted with take2
<Glanzmann> firefox317: I thought so, too. But marcan asked me to: 05:11 <@marcan> before the reboot, when you get the boot picker in the installer, run bputil -g in another terminal
<marcan> before the reboot, when you get the boot picker in the installer, run bputil -g in another terminal

2021-12-22

<rose_> alright, now idevicerestore makes decent progress, but when the mini reboots, idevice waits for it to enter restore mode so it can continue talking over usb, but this doesn't happen and both sides eventually time out. im getting an apple logo and an empty progress bar on the screen, and after a while the mac falls off lsusb and displays a link to
<rose_> after csrutil clear and reboot, csrutil disable gives "failed to create local policy" :(
<rose_> hey, i've just been handed this m1 mini which apparently has u-boot and m1n1 on it and been asked to get macos back. i booted into 1tr and clicked the big "install macos big sur" button but once it finished and rebooted it told me "custom kernel failed to boot". apparently u-boot was installed with this guide:

2021-12-20

<mps> try to reboot first
<NightRaven[m]> The reboot fix one
<NightRaven[m]> And I reboot

2021-12-19

<jannau> I can't reproduce with vf2eac15 but I feel your pain. rebooting m1n1 through long pressing power is annoying
<fionera[m]> I dont boot at all :( I have to reboot m1n1 until it doesnt happen
<fionera[m]> <tpw_rules> "and it works fine in nixos on..." <- I try to build the kernel in nixos itself rn and then keyboard doesnt work anymore. tho the manually build one works. So its probably smth with the config. I didnt try reboot yet, let me see
<Glanzmann> mps: Me, too. I also do not reboot unless I want to try a new kernel. So I had already uptime with 7 days and longer. And currently my mini has 2 days uptime ...
<NightRaven[m]> mps: I found something when you do reboot it work but when you try to shutdown it gets stuck
<tpw_rules> (the watchdog facilitates reboot, it hangs on shutdown for me too)
<steffen[m]> fionera: a watchdog driver is required for reboot. I don't know if that's in the asahi kernel branch yet. https://github.com/AsahiLinux/docs/wiki/HW:WDT

2021-12-18

<sven> afaik on the max/pro there's also a "proper" reboot path using SMC
<j`ey> mps: it only does reboot, poweroff is different
<j`ey> watchdog is what reboots it
<tpw_rules> it reboots fine for me on mac mini with jannau's config
<j`ey> NightRaven[m]: does it actually reboot though?
<NightRaven[m]> Everything I do reboot it shows rhit
<mps> j`ey: so I don't even need to reboot from current linux on target machine?

2021-12-17

<SamAdams[m]> I'm experiencing an issue with m1n1. I'm on Mac OS 12.1 and ran kmutil with m1n1.bin. Does this mean that I just need to install the Linux kernel? I want to install fedora rawhide with the latest 5.16 kernel. When I reboot it keeps on coming up with this message.

2021-12-15

<tpw_rules> my choices are doesn't work at all and works until the machine reboots

2021-12-14

<legarts[m]> So just so I understand we need to use 11.4 as a base for m1n1? I have been playing with developer quickstart and so far I have no feedback on the screen during boot, only 1TR works after rebooting, no SuperSpeed cable to see what's wrong so far

2021-12-12

<landscape15[m]> Glanzmann: I tried but it crashed (it reboots). I try reformatting.

2021-12-11

<Glanzmann> NightRaven[m]: Next step is to do crate a dos fat partition under macos, reboot into linux and put your archlinux on it.
<NightRaven[m]> <Glanzmann> "NightRaven: So you need to do..." <- i will reboot now too see if keyboard works

2021-12-10

<zimsneexh> Yes, this one. Keyboard seemed fine, touchpad did nothing. Rebooted and it seems fine for now, although the touchpad seems somewhat "laggy" compared to rc3_1-keyboard

2021-12-08

<marcan> I basically never rebooted during the SPI thing; once I started wedging the hardware I just started using the PMGR reset bit to reset it on every test run

2021-12-05

<jannau> it should work after reboot with the right timing. in doubt power it off
<zimsneexh> do i do that on reboot?

2021-12-02

<wouter> my point is, the "background image" that eta talks about is easy to add to an "install image", and that image can then just give you instructions to reboot into 1TR and then run the script
<marcan> (and either way you still need to do a reboot into the new 1TR recoveryOS and run step2.sh, regardless of what initial environment you chose)
<wouter> the way I see it is, Debian ships a USB image, which comes with the curl|sh thing that you run from macOS, then you reboot into d-i and get going
<marcan> (I still haven't figured out how to do upgrades, fwiw; I think that would involve another couple reboots and re-provisioning our bootloader, but I need to run some tests)
<marcan> wouter: well, the process involves at least two mandatory reboots, and to make it as user friendly as possible you need to do streaming partial ZIP file fetches from Apple's CDN, firmware cutting and filename munging, manually creating a macOS stub partition with all the Preboot directory structure (which involves parsing and understanding Apple's manifest plists), also you need to race to kill ...
<marcan> ... Apple's boot picker before it reboots because we don't have proper tools to do that programmatically yet, etc

2021-11-22

<_jannau_> reboot was working on the macbook pro, I didn't test the mac mini
<j_ey> yeah reboot should work, it has sven's watchdog driver
<j_ey> reboot should work on that branch
<mps> yes. poweroff and reboot doesn't work for now

2021-11-21

<cth451_desktop> jannau: but the mac address seems unstable and keeps changing across reboots

2021-11-19

<j_ey> RealityVoid: also reboot and swap the two console= things that you have in boot-args
<j_ey> reboot and edit that file
<j_ey> ok well if you reboot and can do: lower() in the hypervisor shell that would be good
<marcan> I guarantee no kernel developer likes doing self-hosted dev and rebooting their machine and dev environment every time, especially not when the alternaive is a 10 second test cycle

2021-11-18

<sven> The unwritable until reboot is because I need to fix the error recovery paths
<boardwalk> Partition was unwritable until reboot, but seems to be fine & was resized.
<radnic> manually rebooting.
<FireFox317> with 20x boots do you mean chainloading 20 times, or rebooting manually?
<marcan> it would be nice to find a way to abort the reboot more reliably...
<mps> marcan: I didn't 'killed' it, just selected asahi and clicked reboot
<marcan> it's not supposed to do that, we do an (ugly) race to kill the boot picker before it reboots, assuming you didn't kill the installer
<marcan> mps: so when you clicked "reboot" the machine actually rebooted?
<Glanzmann> marcan: I had the very same problem. I did only saw the notice for step2.sh after it rebooted, because the boot picker covered it up and rebooted afterwards.
<mps> marcan: I'm not sure that I saw this, maybe I didn't read all text carefully. at the end script told that everything is finished and I rebooted it
<marcan> did that not show up somehow? or did the machine just reboot or shut down?
<radnic> hmm, well, the original .macho is not there after a reboot

2021-11-17

<mps> after upgrade to 12.0.1 axlsh script worked, but when trying to boot from linux disk boot process fails, repeating few times reboot and then goes to macos asking to reinstall it
<kettenis> at least as long as it is required to be able to reboot the machine

2021-11-16

<jannau> I can't reproduce either on the mac mini in ~25 chainload, 15 reboots both through vdmtool and power button

2021-11-08

<bgb> yeah, I just reboot m1n1 every time
<marcan> bgb: remember hotplug doesn't work, you need to reboot after one attempt

2021-11-07

<jannau> charging via magsafe works without touching cd3217, it seems iboot initializes it sufficiently or it is handled by a coprocessor. the led is off during reboot, lights first orange and turns a moment later green with a fully charged battery

2021-11-06

<jannau> not sure if I connected magsafe in macos before rebooting to m1n1 though

2021-11-03

<sven> VinDuv: does macvdmtool itself still work on monterey to reboot the machine btw?

2021-11-02

<jmr2> What works: mkimage on the host, and ext2load usb on the Air. What doesn’t: getting anything else than a synchronous abort exception+reboot after the image content is displayed.

2021-10-30

<sven> like once every 15-20 reboots or so chainload times out a few times before it works
<sven> i also get some timeouts sometimes after a reboot fwiw. but they haven't been very consistent and i haven't been able to figure out why they happen
<VinDuv> The MMU error: https://paste.debian.net/plainh/72286d9b (I also had a SError after but it was caused by the automatic reboot poking the wrong addresses for the WDT; WDT_BASE should be set to 0x2922b0000 in start.S)

2021-10-28

<bgb> yeah, install recent m1n1.macho to mini, then run ./macvdmtool reboot serial on macbook(M1)

2021-10-27

<jix> marcan: btw two things I noticed while running the installer 1) when getting prompted to select the startup disk the message just told me to select the volume... which doesn't do anything, I need to also click on reboot

2021-10-26

<jeffmiw> just after jumping to the kernel it is like it is rebooting in m1n1 and stay there

2021-10-18

<j_ey> nobodynada: the good thing about the hardware uart is that you can reboot the target machine remotely without using the hypervisor
<povik> alyssa: i know, i took reboot from you actually
<alyssa> reboot will be replaced entirely by a wdt driver eventually
<alyssa> reboot, spmi, rtc, and wifi are corellium code
<Serentty[m]> By the way, there’s no filesystem or anything for it to boot off of. That shouldn’t be the issue, right? Like, if that were the issue, I would see Linux try to boot but complain, right? It wouldn’t just reboot without showing anything?

2021-10-17

<Glanzmann> alyssa: I unplugged the eizo S2431W-GY and plugged, EV2780 and have no picture, rebooting now.
<maz> j_ey: ah! that's because you didn't have a TX2 as a desktop. reboot the box, and you immediately know where it is, thanks to the fan basting out a tornado until EFI takes over.

2021-10-16

<alyssa> looks like I only get a single link up / link down interrupt and then I need a reboot :|

2021-10-15

<alyssa> ^ apply that patch, rebuild, reboot, resend dmesg please :)

2021-10-14

<_alice> I think it'd be pretty neat to have a fancy install flow that pre-stages the distribution installer for the next reboot after step2.sh, kinda like how there were Windows GUI installers for Linux back in the day

2021-10-12

<povik> i mean, it reboots while booting
<povik> did it just reboot with little explanation? (that's what happens here)
<rross101> OK making progress thank you. With that kernel image - concatenating and chainloading gets m1n1 rebooting with a 'kernel found' message - but not sure what to do from there. Using linux.py instead I get a decompression error after the 'FDT prepared' stage

2021-10-10

<marcan> macs are the only platform where you can have full freedom to run your own OS *and* the ability to run a locked down DRM system, with a simple reboot

2021-10-09

<povik> first with pmgr_reset commented out, after fresh reboot
<povik> i assume you rebooted

2021-10-06

<Glanzmann> Should I reboot and try to be absolutly sure?

2021-09-29

<Glanzmann> firefox317: In case you missed, reboot your system, go to system preferences and pick the m1n1 parition to boot from, execute step2 and you should be good to go.
<Glanzmann> However the installer is really nice even if we need to reboot inbetween to make m1n1 partition show up.
<marcan> rebooting to get it to show up is obviously a problem we need to fix
<marcan> I mean, rebooting into 1TR
<Glanzmann> But the worst thing is, that you need to reboot, pick it and than go ahead.
<marcan> please experiment to see if you can figure out something to do to make it show up without a reboot
<marcan> yeah, try after a reboot
<marcan> so you can try deleting it, rebooting, then running the installer fresh
<marcan> it did show up after a reboot, right?
<Glanzmann> I rebooted, it works.

2021-09-28

<FireFox317> hmm so somehow the first time I ran the script it did not properly reload the 'Startup Disk' program and thus the Linux partition did not show up. I rebooted the system and now it shows up
<Glanzmann> I reboot and try the hotplugging.
<marcan> Glanzmann: when you pick the boot device, is the installer still running? and once you do, does your computer *shut down* or *reboot*?
<bgb> when I replug the arduino cable, your picocom cmd fails to reboot mac, finally find a solution like this : http://paste.debian.net/1213508/
<bgb> jannu: for the mac reboot thing: seems this is why arduino terminal always works fine, but console cmd may not. https://forum.arduino.cc/t/solved-problem-with-serial-communication-on-leonardo/139614

2021-09-27

<Glanzmann> And the system rebooted or powered off.
<bgb> marcan: btw, I think it's possible to send cmd to arduino(with vdmtool) in python code. I want to write a simple Mac reboot cmd in python, and tried ser = serial.Serial("/dev/ttyACM0", 500000) ser.write(b"5AC8012,0105,80000000\n"), it didn't work. is there any difference from the Ardunio Terminal tool?

2021-09-24

<sven> sometimes the macbook air (running macOS) usb port is dead until i reboot
<sven> okay. rebooting the macbook air fixed the port again *sigh*
<sven> (rebooting will probably fix it, but this whole thing seems to be rather unstable :D)

2021-09-23

<marcan> maz: make sure you chainload *first* after a reboot
<maz> j_ey: yup. fully automated install from scratch (boot from EFI, install everything reboot into the created guest, power-off).

2021-09-20

<povik> works best after fresh reboot

2021-09-18

<j_ey> (or maybe its just easier to reboot)
<j_ey> marcan: is there anything mini specific? python3.9 proxyclient/experiments/cpu_pstate_latencies.py casued my m1 to reboot
<alyssa> (+ corellium reboot + locked DART stuff. actually it's just my tree - DCP)

2021-09-16

<alyssa> maz: just built your branch (+ reboot + DCP patches), everything works as before

2021-09-01

<marcan> he said the system didn't reboot after the startup volume thing was done, which is exactly what the installer does
<marcan> rkjnsn[m]: then his system would've rebooted after the startup volume window closed, *without* having to press enter once again

2021-08-31

<marcan> you can install asahi without any reboots on 11.x from 1TR, but that stopped working with 12.0, it requires at least one reboot into the new paired rOS
<marcan> there's a hideous hack in the installer to race the boot picker and kill it before it can reboot the system for that...
<marcan> that's why I have the installer shutdown instead of reboot, so you can go into recovery and never end up in that messy bootloop
<marcan> pipcet[m]: and your system shut down (not rebooted)?
<pipcet[m]> just rebooted into macos and restored the terminal
<marcan> or rather it's not supposed to reboot

2021-08-30

<sven> what kind of cable do you use? iirc i had a cable where rebooting worked but the serial console didn't because it hadn't connected those lines
<kettenis_> rebooting works, but I don't see any serial output

2021-08-23

<maz> marcan: yup, that's what I thought. the ESR always has the same IMPDEF value 0xbf40100a. it triggers exactly once per VM boot (every time the guest reboots as well).
<j_ey> also m1n1's 017f050fffb8f426eafe65b6a24d71fdc16131f7 reboots my m1 and kills the python side for me

2021-08-19

<alyssa> marcan: But to answer the original question, I'm dailydriver the linked date branch. PCIe + dwc3 device tree + pinctrl + reboot

2021-08-14

<kettenis_> alyssa: using the WDT to reboot works fine in u-boot and openbsd
<pipcet[m]> well, the corellium reboot driver does the same thing as the WDT driver so I'm stumped.
<alyssa> do we know how macOS reboots?
<pipcet[m]> alyssa: can't we use the wdt driver? it handles reboots fine :-)
<alyssa> sven: the corellium reboot driver looks pretty self-contained, might be a good candidate to send off to the LKML almost as-is
<alyssa> corellium's patch doesn't work for me (it reboots)
<alyssa> pipcet[m]: Does shutdown (not reboot) work on pearl?
<alyssa> sven: is there a magic sequence to reboot DCP if it crashes?
<pipcet[m]> i played with that very briefly and macos just rebooted when i crashed the smc
<tophevich[m]> execution, without a reboot."
<tophevich[m]> "Since the hypervisor is built on m1n1, it works together with Python code running on a separate host machine. Effectively, the Python host can “puppeteer” the M1 and its guest OS remotely, and the hypervisor itself is partially written in Python! This allows us to have a very fast test cycle, even updating parts of the hypervisor itself live during guest execution, without a reboot."

2021-08-12

<marcan> interesting, I can SSH into macOS during an upgrade, during the post-reboot 15 minute progress bar thing
<marcan> it would also be nice if we could set the new volume as bootable without a reboot, to avoid having to tell people to force shut down the boot loop
<marcan> eventually, but the steps at the very end (the reboots and running the shell script) are pretty much required

2021-08-06

<pipcet[m]> alyssa: I think the SMC stuff is a mess, frankly, they go digging around in nvmem and the device tree for the poweroff sequence. Reboot is easier, there's apple_wdt_restart here https://github.com/pipcet/linux/blob/543af4a24f5561522e8a52aa6bd6bec692d2e93b/drivers/watchdog/apple_wdt.c#L72. Literally four writel()s :-)

2021-07-30

<pipcet[m]> alyssa: the problem here is a reboot doesn't help us recover from this condition, which I think is a tad worse than anything panfrost might reasonably break :-)

2021-07-29

<MTecknology> lucky bastards... once it starts crashing for me, it doesn't stop crashing. At best, I might get 5 minutes without rebooting back into windows and back into linux to clear whatever with nvidia
<pipcet[m]> sorry about that. I think all you need to play with m1n1 is the .macho, boot into recovery mode, open a terminal, run *util in the right order and with the right parameters, and reboot. you definitely do want to keep macos around on the nvme, though

2021-07-26

<pipcet[m]> (maybe it would be interesting to do a Recovery Mode -> macOS hypervisor trace and compare it with a Recovery Mode -> ANS bringup -> reboot -> macOS one)
<sven> still strange the requires a recovery mode reboot though

2021-07-25

<sven> hrm, i've seen that happen when i try to chainload too early after a reboot. but that's kinda expected i think

2021-07-22

<cth451_desktop> then the system reboots

2021-07-13

<sven> i'm not sure the storage processor can easily be rebooted. there are some suspicious properties in the adt
<marcan> that said, I don't want to reboot DCP
<marcan> and yeah, it's probably cleanest to just reboot it

2021-07-12

<sven> so i've managed to make the mailbox overflow already while trying to make it reboot

2021-07-08

<bgb> typec port(not the DFU one) of my MBP can only charge if I reboot with cable plugged, if unplug and plug again, no charging sign, anyone know why ?

2021-07-05

<marcan> and I have to reboot the thing
<Ariadne> so one thing i've noticed with these M1 macs is, sometimes they won't wake up, and then you have to hold the fingerprint sensor / power button down for 5 seconds and reboot it

2021-06-19

<amw> Woops just crashed my hv ... disassemble_at(0xffff8000102fdc3c, 8) -> it just rebooted...

2021-06-08

<pipcet[m]> I think it's more interesting that you can't reboot the remote processors that you communicate with using the mailbox, so you can't leave the hardware in the state you found it.

2021-06-07

<pitust[m]> and after a reboot nothing changed

2021-06-06

<pipcet[m]> I believe that's correct, yes. Charging is more of an annoyance because you get a spontaneous reboot when the battery's empty.

2021-06-04

<jannau> mac os breaks rebooting via USB PD when it has access to one usb-c port
<marcan> the correct way to support dual-booting without the "hold down the power button" issue is to have whatever boot picker you want to have, but actually clean reboot into the new OS (via nvram var) the same way 1TR does
<Emantor> marcan: reboot is very handy, thanks :-)
<marcan> jannau: btw, have you tried the "turn on on power failure" thing in the macos settings? it might make for a simpler hard reboot by momentarily removing power, instead of having to hold down the power button for a while
<marcan> pushed; `reboot` at the hypervisor console will now do a hard reboot and exit the script
<marcan> actually wait, I don't actually have a proper reboot command do I
<marcan> jannau: with the hv you can reboot by command (or it reboots itself if it crashes, with the wdt)
<jannau> rebooting by command is very convenient compared to pressing the power button

2021-05-31

<MagMell[m]> <marcan "Mag Mell: if you mean m1n1, it s"> It seems that the USB-C cable is not recognized even after reboot, is there a special condition for the USB-C cable?

2021-05-28

<yuyichao> 3) both ttyACM0 and ttyACM1 disappears when the usb cable was disconnected (as expected) and either shows up again when the cable is plugged back in without rebooting m1n1

2021-05-16

<amw> Just for the record it took me three tries to install the latest m1n1, I had to do csrutil clear, reboot, csrutil disable a few times before it took!
<marcan> and are you sure you're not doing something weird like running the hv twice? does this happen from a clean reboot>chainload.py>run_guest.py?

2021-05-09

<arnd> I tried erasing the first install on the external drive and reinstalling to it. The reinstall also worked, but after rebooting, it still fails with "The version of macOS on the selected disk needs to be reinstalled. Use Recovery to ereinstall macOS or select another startup disk."
<marcan> amw: I reboot the thing after each boot, and I would kind of expect RAM to be cleared or shuffled after a reboot
<marcan> well I could stash the image somewhere in RAM that doesn't get touched, but right now I reboot the system after runs anyway to clean up properly so that wouldn't really help

2021-04-10

<marcan> (and reboot takes 7 seconds so whatever)

2021-03-24

<amw> I get a brief Asahi logo flash after the apple and then it reboots (this was an old m1n1 version)

2021-03-21

<amw> Sigh still rebooting from the upgrade...
<amw> Sigh still rebooting from the upgrade...
<amw> sven: Note: I haven't gotten kmutil to complete yet - just rebooting after update now
<amw> sven: Note: I haven't gotten kmutil to complete yet - just rebooting after update now

2021-02-17

<never_released> davidrysk[m]: yeah I don't reboot all the time
<davidrysk[m]> never_released: do you avoid rebooting?

2021-02-12

<Glanzmann> Yes, it works. Rebooting now. I already saw the ash prompt.
<Glanzmann> Perfect. Now it works. This time I typed in 'reboot' instead of using macvdmutil.
<Glanzmann> I try to get the mac mini to boot into m1n1. So the steps are: Build it, boot into 1tr, run the commands and reboot and it should show the asahi linux logo and wait for commands on serial?
<Glanzmann> I think I did something stupid. I installed m1n1.macho but instead of rebooting I ran sithglan@air macvdmtool % sudo ./macvdmtool reboot serial which worked, but now it says custom kernel fialed to boot. And I can't revert from the 1tr so probably I need to reinstall.

2021-02-09

<JTL> On older MacbookPros that use M.2 with a custom connector, there are reports that non Apple brand SSDs (used with chineseium adapter) cause sleep and reboot issues due to presumably power saving not working "properly"
<never_released> I reboot w/ a new kernel to find broken Ethernet
<marcan> I automated the whole reboot-enter 1TR-pull up termina-type command thing when I first brought this up, using a keyboard emulator and the reboot USB-PD command

2021-02-06

<marcan> when you pick something in the boot picker, it sets boot-related nvram variables and reboots

2021-02-04

<marcan> Mary_: make sure you use "reboot serial"

2021-02-02

<marcan> (the regular reboot that is, I wasn't using DFU)
<marcan> just one command chain to reboot, chainload a new m1n1 and/or kernel, etc
<marcan> the remote reboot stuff is super handy for a fast test cycle
<marcan> you can literally hard reboot it if it's in macos

2021-01-24

<Glanzmann> jannau: I tried the corellium kernel on my macbook air (8 core GPU; 16 GB RAM) and it hangs at reboot with the message: Starting linux loader stub.\nLoader complete, relocating kernel...

2021-01-19

<rcombs> since updating the Mach-O image requires rebooting into recovery mode, signing the new file, regenerating boot policy…

2021-01-14

<rwhitby> I've scripted the error-recovery, reboot-normal and reboot-dfu actions. now starting on getting UART output and the I2C buses

2021-01-13

<marcan> (and it reboots fast)
<j`ey> you were looking for a way to reboot without tocuhing it :D
<marcan> the thing reboots endlessly, every minute or half or so
<marcan> but if you don't no worries, plain old fast reboots are the most useful feature and we already have that

2021-01-12

<marcan> I can already reboot via PD, the missing thing is boot into 1TR
<marcan> though strictly speaking that's for early bring-up only, because once I have a working serial loader, I can just never update it on device and just use reboots to test, which is very fast

2021-01-11

<marcan> of course the PD link / serial stuff goes down on reboot
<marcan> I've had my keyboard stop working on macos until a reboot several times now

2021-01-09

<davidrysk[m]> just note that anything you do will get reverted on reboot
<marcan> mine actually failed at some point, but the resize worked, but I had chosen HFS+ and it decided to make it APFS anyway, then I reformatted it as HFS+, then rebooted, 1TR broken
<rwhitby> confirmed - if you boot from an external drive, and then reboot without that drive attached, then you get into a boot loop that eventually results in a Recovery Assistant screen which says you have to reinstall and does not have the option to boot from the internal drive. you have to power cycle into 1TR to see the internal drive again and boot from it.
<rwhitby> davidrysk[m] 4s faster on TBT3 for reboot to same disk
<davidrysk[m]> rwhitby: is it any faster on reboot?
<rwhitby> 32s from reboot to login for TBT3 SSD, roughly same as USBC SSD, so it's not transport or disk speed limited (I know that TBT3 SSD is at least twice as fast as USBC SSD using BlackMagic speed test.

2021-01-08

<marcan> the main purpose of the RPC thing is to allow experimenting from a PC, remotely, without rebooting, and to be robust enough to gracefully recover from simple faults
<Shiz> yay softwareupdate -i -a && reboot seems to work

2021-01-07

<davidrysk[m]> I'm using the M1 as my primary so I wanted to avoid rebooting unnecessarily