#asahi-dev · 2026-05-20 15:48
arrynnow everything works#asahi-dev · 2026-05-20 15:47
arrynI completely forgot to align everything to 16K#asahi-dev · 2026-05-20 15:47
arrynugh page alignment was my issue all along....#asahi-dev · 2026-05-19 23:05
arrynToday I gave it another try and I have no idea what I've done differently... But now I can finally boot m1n1#asahi-dev · 2026-05-12 20:00
arrynAll my binary contains is dummy VBAR at 0x0-0x7FF and code from 0x800 which is basically just a b . I tried this because I also couldn't get m1n1 to run at all#asahi-dev · 2026-05-12 20:00
arrynyuka: I am not trying to set up m1n1 but my own binary. But m1n1 does have the same issue for me#asahi-dev · 2026-05-12 16:31
arrynmachO*#asahi-dev · 2026-05-12 16:31
arrynThe only thing that I can think of that I haven't tried yet is to create a mach and see if that changes anything#asahi-dev · 2026-05-12 16:28
arrynOut of despair I even randomly tried bti jc and such but that changes nothing. After the boot chime it reboots. I also tried 26.5 BETA just in case it changes something. But I have not tested the release of it yet#asahi-dev · 2026-05-12 16:27
arrynconfigure-boot -c myobj.o --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/macOS2/ The object is exactly what I expct an have verified with a hexdump and objdump. It seems to mimic what m1n1 is doing, if I remember right. Am I missing a step here?#asahi-dev · 2026-05-12 16:26
arrynAfter a lot of testing I was unable to get a custom payload running on M5... I installed a 2nd macOS partition, booted into it's 1TR by selecting it as startup disk, shutting down and keeping the power button pressed until the menu appears, then I selected options. Then I opened a terminal updated the local policiy with bputil -nckas and installed my kernel with kmutil#asahi-dev · 2026-05-07 12:07
arrynMhhh yeah as it seems this is for memory de-/allocations#asahi-dev · 2026-05-07 11:12
arrynOh I see... #asahi-dev · 2026-05-07 11:11
arrynShouldn't be PAC though because b . does not touch memory, right? I'm not really familiar with those features#asahi-dev · 2026-05-07 11:09
arrynand hardware since armv8.5 has BTI as mandatory#asahi-dev · 2026-05-07 11:08
arrynHmm could it be that I cannot get anything to boot because of BTI or PAC? I just read this: "Within a guarded memory region, when PSTATE.BTYPE != 0b00, all instructions will generate a Branch Target Exception, other than BRK, BTI, HLT, PACIASP, and PACIBSP, which might not. See the individual instructions for more information."#asahi-dev · 2026-05-06 11:37
arrynyeah seems different from my issue#asahi-dev · 2026-05-06 11:35
arrynflokli: whats your issue with it exactly? yesterday I tried booting with 26.4.1 on M5 pro and I can't get it to work either. I even tried my own payload that is only vbar and an endless loop and it just keeps rebooting after the chime and then lava lands me in recovery after a few times#asahi-dev · 2026-05-05 15:44
arrynis it time to conclude that apple broke something again? if the chime finishes and the macOS kernel boots, that means the firmware on my partition is fine too, right?#asahi-dev · 2026-05-05 15:43
arrynfor objdump of try the m1n1 elf I get LLVM ERROR: Invalid data was encountered while parsing the file. bur hexdump of m1n1 shows the vector table at 0 and start at 0x800#asahi-dev · 2026-05-05 15:39
arrynexception vectors at the start, b . instruction at 0x800#asahi-dev · 2026-05-05 15:38
arrynyup its what I expect#asahi-dev · 2026-05-05 15:35
arrynwill do. it should be, I used the same toolchain and program I developed on M1, just put a loop at the start to see if I can get it to rum#asahi-dev · 2026-05-05 15:33
arrynmy kmutil command is the one from the wiki: kmutil configure-boot -c myobj.o --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/macOS2/#asahi-dev · 2026-05-05 15:29
arrynstart vector table is at offset 0 in the binary?#asahi-dev · 2026-05-05 15:27
arrynyup. 0x800 in the binary and I put 2048. that should match if I'm not stupid#asahi-dev · 2026-05-05 15:25
arryneven though I specified the offset for the start function. ill try to put jumps into my exception vectors#asahi-dev · 2026-05-05 15:24
arrynthe chime plays through. maybe it's jumping somewhere it shouldnt#asahi-dev · 2026-05-05 15:24
arrynnow it works. boot loops after the chimr and only plays it once#asahi-dev · 2026-05-05 15:23
arrynmhhh for some reason I don't hear the boot chime. is it a global setting or per partition?#asahi-dev · 2026-05-05 15:21
arrynwhy am I always running into this bug... back with m4 too and I ended up here#asahi-dev · 2026-05-05 15:20
arrynit is M5 pro...#asahi-dev · 2026-05-05 15:19
arrynyeah, I don't even get that far#asahi-dev · 2026-05-05 15:17
arrynI've got the chime off, let me retest#asahi-dev · 2026-05-05 15:17
arrynthe machine I have is a T6050 and I installed a 2nd macOS partition to keep my original one intact#asahi-dev · 2026-05-05 15:16
arrynnot at hand but I've got an M1 Pro that I can access this evening#asahi-dev · 2026-05-05 15:15
arrynmy boot object is literally just vector table + _start with loop at 0x800. #asahi-dev · 2026-05-05 15:14
arrynstill seems to bootloop#asahi-dev · 2026-05-05 15:07
arrynyeah its 26.4.1 #asahi-dev · 2026-05-05 15:07
arrynbputil -a ?#asahi-dev · 2026-05-05 15:06
arrynlet me check#asahi-dev · 2026-05-05 15:06
arryn26.4.1 if I remember right#asahi-dev · 2026-05-05 15:06
arrynmy partition is a vanilla macOS partition unmodified#asahi-dev · 2026-05-05 15:05
arrynwhen installing a raw kernel boot object. is there more to be done than just using kmutil to install it? on M5 pro, I can't even get a payload to run that just does b . it just boot loops#asahi-dev · 2026-02-06 11:09
arrynThe first time I put my own code on it I was messing with a usb stick and uboot commands because I couldn't figure out how to load a raw binary over m1n1 hhh#asahi-dev · 2026-02-06 11:08
arrynAlso learning how to use the m1n1 tooling is also a little complex for people coming in the first time. But I have to say once you figure it out it's a very convenient experience#asahi-dev · 2026-02-06 11:07
arrynAnd since QEMU is often very lenient with mistakes my understanding is a little loose in my opinion #asahi-dev · 2026-02-06 11:06
arrynnoopwafel: yeah something like that. So far my experience with drivers is very limited and mostly things that QEMU emulates#asahi-dev · 2026-02-06 11:05
arrynmaz: That's true BUT! it (often) requires the knowledge of how these kinds of devices work on a deeper level to begin with. That's the knowledge I'd like to gain here#asahi-dev · 2026-02-06 10:59
arrynalso because reading linux driver code is not really easy for me haha