#
✕ nick:nnym
#asahi-re · 2025-10-06 00:38
nnymIt cleared my kernelcaches so I copied the last one from my other computer over, installed it, and rebooted; and now m1n1 behaves as before.
#asahi-re · 2025-10-06 00:30
nnymI ran `bputil -nkcas` and `csrutil disable` again and now `/dev/disk3s2` is automatically mounted at `/Volumes/Preboot`.
#asahi-re · 2025-10-06 00:24
nnymI think that I've tested all of them now and they all ran for less than a second but I know that m1n1 was running for longer—around a minute perhaps—apparently calling `print_regs` over and over until it stopped for a while, the screen became blurry, and the computer rebooted.
#asahi-re · 2025-10-05 23:59
nnymI've gone through almost all of my kernelcaches—including the first—and every one of those that was built without `BRINGUP` exits almost immediately. I think that something changed outside my m1n1 and I think that it started after I ran m1n1 with `BRINGUP`. Is there a connection?
#asahi-re · 2025-10-05 23:13
nnymI was editing a script in Vim and recoveryOS crashed. Is this normal?
#asahi-re · 2025-10-05 22:56
nnymThanks.
#asahi-re · 2025-10-05 22:56
nnymOh yeah. They're all there.
#asahi-re · 2025-10-05 22:53
nnymOh that's what you mean. `/System/Volumes/Preboot` is a tmpfs which is not `/dev/disk3s2` ("Preboot"). Let me see.
#asahi-re · 2025-10-05 22:43
nnymThe UUIDs match my volume groups but there's only the official kernel in each.
#asahi-re · 2025-10-05 22:41
nnym/System/Volumes/Preboot/54B91C04-0D42-448A-806D-E2251A3F1DF6/boot/FC163BEB29178A53F9CC278EFA5992045C407B8A203446FF6CCA5B4F57D3A6D19070A1D84CF967EAEE8FC737B4034FB6/System/Library/Caches/com.apple.kernelcaches/kernelcache
#asahi-re · 2025-10-05 22:41
nnym/System/Volumes/Preboot/EF3C096E-D78F-49E3-AD0F-26A11FF83EE6/boot/FC163BEB29178A53F9CC278EFA5992045C407B8A203446FF6CCA5B4F57D3A6D19070A1D84CF967EAEE8FC737B4034FB6/System/Library/Caches/com.apple.kernelcaches/kernelcache
#asahi-re · 2025-10-05 22:41
nnymOnly `kernelcache`. I powered off and booted recoveryOS but I still see only `kernelcache`.
#asahi-re · 2025-10-05 22:36
nnymI ran `kmutil configure-boot` with the XNU kernelcache and then m1n1 again and now I'm in recoveryOS but the directories in `/System/Volumes/Preboot` don't match my volume groups anymore. Also, I ran `find / -name 'kernelcache*'` (or `kernelcache.*`) earlier and it didn't find my kernelcache. I'll take a look here before rebooting.
#asahi-re · 2025-10-05 22:24
nnymYeah.
#asahi-re · 2025-10-05 22:22
nnymAlso, I wanted to look at the current kernelcache in recoveryOS but there seems to be only the official XNU kernelcache. (There's only the single directory whose name is the hash of some `apticket.der` in `/System/Volumes/Preboot/<long hash>/boot/<the hash>`.)
#asahi-re · 2025-10-05 22:21
nnymI see. Perhaps I misremembered.
#asahi-re · 2025-10-05 22:09
nnymconfigure-boot -c m1n1.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/test` and it still runs for less than a second.
#asahi-re · 2025-10-05 22:09
nnymI had an m1n1 that ran for around a minute or 2 before rebooting on my T6041, made some changes (defined `BRINGUP`), reverted them, and built it again and now it lasts less than a second. I purged `build/` before rebuilding to be sure but its SHA-256 hash changed after I did that while the source code was the same; so I copied it again, verified its hash, and ran `kmutil
#asahi-re · 2025-10-05 21:05
nnymI ran `du -h build/m1n1.bin` a little earlier and saw that it was around 70K; now it's over 900K. Is that possible or am I misremembering?
#asahi-re · 2025-10-05 17:33
nnymThat would disable more than just the broken code though. And with a Macbook, would you use a USB-C to RS-232 cable in that case?
#asahi-re · 2025-10-05 17:14
nnymWhy would you do it in the latter case? Does it make debugging easier somehow?
#asahi-re · 2025-10-05 16:20
nnymDefining `BRINGUP` in m1n1 seems to only disable things and causes only the white apple to show while booting. If I can otherwise see the Asahi logo and a log, is defining it useless?