#asahi · 2021-06-19 05:33
VinDuvmight be easier#asahi · 2021-06-19 05:33
VinDuvyes, I was thinking about that, you should be able to run_guest a m1n1 with concatened payloads and the payload will run under HV#asahi · 2021-06-19 05:29
VinDuvM1N1DEVICE=/the/secondary/virtual/usb/port linux.py …#asahi · 2021-06-19 05:27
VinDuvYou should be able to run Linux under the hypervisor though; for this I think you need to run m1n1 under the hypervisor, then start linux.py with the hypervised m1n1#asahi · 2021-06-19 05:24
VinDuvI’m pretty sure the m1n1 USB devices will always disappear if you start Linux directly with linux.py; if Linux itselfs starts emulating a USB serial port it will reappear, but the transition won’t be seamless#asahi · 2021-06-07 19:19
VinDuv(and changes it if fb_improve_logo is called)#asahi · 2021-06-07 19:19
VinDuvm1n1 stores the original logo and restores it during fb_shutdown#asahi · 2021-06-05 09:48
VinDuvnice :)#asahi · 2021-06-05 09:40
VinDuvamw: you can download and apply the patch manually https://github.com/AsahiLinux/m1n1/commit/b135733d733d12907aa0d5af87c770380ae8dc9f.diff -- it’s just a couple of lines in proxyclient/shell.py#asahi · 2021-06-05 08:25
VinDuvamw: You can try https://github.com/AsahiLinux/m1n1/pull/69 , it should allow you to get a shell without chainloading m1n1 first#asahi · 2021-06-05 06:38
VinDuvit’s not a huge problem since chainload.py works but it’s probably not optimal#asahi · 2021-06-05 06:37
VinDuvwhich cahses a P_GET_SIMD_STATE which may not exist on the installed m1n1#asahi · 2021-06-05 06:36
VinDuvwhen it starts up, shell.py fetches methods out of the ProxyUtils instance so you can directly use msr() in the shell instead of u.msr(), but the way it does that makes it fetch the SIMD properties defined here (https://github.com/AsahiLinux/m1n1/blob/main/proxyclient/proxyutils.py#L241)#asahi · 2021-05-29 20:15
VinDuvLinux already has a Bluetooth HID driver for the magic trackpad, so assuming Bluetooth works (?) it should just work; auto-pairing is the responsability of the userland software, not the kernel#asahi · 2021-05-29 20:05
VinDuv by magic trackpad you mean the external one ?#asahi · 2021-05-27 20:18
VinDuvI think I remember a story about some software whose auto-updater replaced itself with a 404 page, and the resulting binary would actually cause bad things when executed#asahi · 2021-05-16 12:34
VinDuvamw: The proxy is supposed to get a reply to the kboot_boot command and receive the “Preparing to run next stage at …” message before m1n1 shuts down USB (and starts Linux), so it’s a bit weird that it doesn’t receive the reply… maybe something isn’t flushed properly#asahi · 2021-05-16 08:54
VinDuvthe “expected 0x00000000” is pretty suspicious… maybe there’s a case where the sender does not correctly put the checksum in the message?#asahi · 2021-05-09 15:23
VinDuvMaybe that does some weird things if you have multiple external installs?#asahi · 2021-05-09 15:23
VinDuvThe page you linked indicates that even if you install macOS on external storage, the macOS kernel will be installed on internal storage (search for “M1 machines cannot boot from external storage.”)#asahi · 2021-05-09 09:06
VinDuvThe builtin zlib module seems to have support for adler32 and crc32 (implemented in C) but I suppose these wouldn’t be compatible with the current checksum you’re using#asahi · 2021-05-08 06:28
VinDuvKVM (or equivalent) virtualizes the CPU but you’d still need to emulate the rest of the M1 hardware#asahi · 2021-01-31 11:19
VinDuvDo you actually have to have macOS installed on the second APFS partition before putting m1n1 on it ?