#asahi · 2021-10-31 15:40
VinDuv(It’s possible to reinstall Big Sur on another partition even after upgrading to Monterey — put it on a USB stick and select the installer in the boot picker)#asahi · 2021-10-31 15:37
VinDuvI don’t think it has been investigated yet… Maybe the driver was removed?#asahi · 2021-10-30 18:45
VinDuvI’m assuming iodev_whoami is simple enough so a timeout can only mean mismatched baudrate #asahi · 2021-10-30 18:39
VinDuv(I also had some issues with chainload timing out but it looks like it’s just because the MMU-less m1n1 is a bit too slow to finish starting…)#asahi · 2021-10-30 18:37
VinDuv(and should not mess with usb-serial)#asahi · 2021-10-30 18:37
VinDuvsven: This seems to work for me: https://github.com/VinDuv/m1n1/blob/baud-adjust-fix/proxyclient/m1n1/proxyutils.py#L461#asahi · 2021-10-30 16:01
VinDuvah, true#asahi · 2021-10-30 16:00
VinDuvIf it raises ProxyCommandError the baudrate is also good I think#asahi · 2021-10-30 15:59
VinDuvYeah but if you’re using the non-usb uart and it returns without raising any exception, it means the baudrate is good#asahi · 2021-10-30 15:57
VinDuvPretty sure it’ll work but I’m still unsure about the whole iodev_whoami thing#asahi · 2021-10-30 15:47
VinDuvIt works but it’s a bit slow since it waits for the default timeout#asahi · 2021-10-30 15:42
VinDuvOn my Mac the proxy.iodev_whoami raises m1n1.proxy.UartTimeout which is not caught#asahi · 2021-10-30 15:39
VinDuvI don’t really understand how that would work since it sends a proxy command before trying to adjust the baud rate?#asahi · 2021-10-30 15:38
VinDuvIn my case it’s the proxy.iodev_whoami() call in bootstrap_port which fails#asahi · 2021-10-30 15:36
VinDuvah you’re right, I’ve missed that part of the code#asahi · 2021-10-30 15:31
VinDuvI don’t remember marcan having problems with it but I guess it’s because his serial adapter has auto baudrate#asahi · 2021-10-30 15:27
VinDuvso if I close the shell and restart it, the proxy will be at 115200 and the target at 1500000 so it doesn’t work#asahi · 2021-10-30 15:26
VinDuvhmm, there’s something else I don’t quite understand: it looks like m1n1’s proxy always opens the serial port at 115200 baud (unless M1N1DEVICE has a specified baudrate) and then switches both ends to 1500000#asahi · 2021-10-30 15:16
VinDuvand probably a bunch of refactoring to remove hardcoded addresses…#asahi · 2021-10-30 15:15
VinDuv:-)#asahi · 2021-10-30 15:06
VinDuvsven: changing the addresses did not seem to fix anything, but I’ve probably messed up something somewhere#asahi · 2021-10-30 12:24
VinDuvlooks like it dies after printing “MMU: SCTLR_EL1: 30100180 -> 30901085”#asahi · 2021-10-30 12:11
VinDuvThe 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)#asahi · 2021-10-30 11:18
VinDuvyeah, chickens.c doesn’t recognize the cpu model so it applies half of the chicken bits I think#asahi · 2021-10-30 10:58
VinDuvok, m1n1 seems to mostly work on the 14" MBP with UART_BASE changed and mmu, pmgr and usb removed :)#asahi · 2021-10-29 20:08
VinDuvwhich is not entirely unexpected tbf#asahi · 2021-10-29 20:08
VinDuvawww, m1n1 doesn’t just work on it#asahi · 2021-10-29 18:42
VinDuvlol, the 14" MBP is actually smaller in every dimension than my old 13" MBP :-)#asahi · 2021-10-18 17:57
VinDuvlol#asahi · 2021-10-18 17:56
VinDuvok that’s a bit deceptive, going from M1 Pro to M1 Max adds 230€ but it forces 32 GB RAM which adds 460€#asahi · 2021-10-18 17:42
VinDuv:D#asahi · 2021-10-18 17:38
VinDuvWhen they brought back the FireWire and the SD card slot on the 2009 MBP I don’t think they mentioned it so clearly, at least#asahi · 2021-10-18 17:36
VinDuvI wonder what happen to the cursor around the notch#asahi · 2021-10-18 17:34
VinDuvit’s split looks like#asahi · 2021-10-17 15:28
VinDuvstd::launder(std::get_money(…))#asahi · 2021-10-17 09:49
VinDuvhonestly I’m impressed that the combination wine + moltenvk + rosetta2 even works at all :)#asahi · 2021-10-06 18:47
VinDuvNot sure if it’s easy to remove the “internal” macOS install without rendering the “external” one unbootable…#asahi · 2021-10-06 18:46
VinDuvbut yes, the M1 needs a pre-boot partition on internal storage to be able to boot from external AIUI#asahi · 2021-10-06 18:46
VinDuvThe safest way would probably be to install macOS on the external device, and at first boot, use the migration assistant to copy the data from the internal storage#asahi · 2021-09-25 08:17
VinDuvMJPEG encoder/decoder ?#asahi · 2021-06-29 19:59
VinDuvjelly: hi! IIRC marcan said on Twitter that GitHub was better (because lower fees)#asahi · 2021-06-19 08:37
VinDuv(The bug is in sym(), it should always return a tuple — https://github.com/AsahiLinux/m1n1/blob/main/proxyclient/m1n1/hv.py#L426 should be return None, None)#asahi · 2021-06-19 08:36
VinDuvIf I’m not mistaken your patch to addr() should not be needed now that you have symbols — if you revert it and hv._reloadme() it you should have a nicer output#asahi · 2021-06-19 08:28
VinDuvdid you reload system.map?#asahi · 2021-06-19 08:14
VinDuvthis is definitely not the right way to do it, but if you set hv.sym_offset = hv.tba.virt_base = hv.macho.vmin = 0 and hv.pac_mask = 0xffff000000000000 I think you should get your symbols…#asahi · 2021-06-19 07:57
VinDuvcan you get the values of hv.sym_offset , hv.tba.virt_base , and hv.macho.vmin ?#asahi · 2021-06-19 07:55
VinDuvdid you get 0xffff8000102fdc3c (four f, one 8) at the top of the stack trace this time?#asahi · 2021-06-19 07:51
VinDuv(not really sure if it’s the right way to do it, but that should give you more correct addresses I think)#asahi · 2021-06-19 07:50
VinDuvamw: just a guess, but try setting hv.pac_mask = 0xffff000000000000#asahi · 2021-06-19 06:00
VinDuvyou should run a picocom on the secondary m1n1 USB device to see the boot logs