#asahi-re · 2026-01-14 21:31
nnymIn the first paste, I included all 3 for each of the official kernelcache and a custom Mach-O boot object; in the second, I included the same files for m1n1.bin but the fuOS file appears first because I wrote a script for it and forgot to preserve the order.#asahi-re · 2026-01-14 21:24
nnymMach-O. Here is the one for `m1n1.bin`. https://paste.sr.ht/~nnym/8ea8407ab281b7a9ef020ecb50d0c938c1e5b9fa#asahi-re · 2026-01-14 21:16
nnymhttps://paste.sr.ht/~nnym/fe87296528d089c6e1d05f5cde4f5744789b5198#asahi-re · 2026-01-14 20:58
nnymI thought so. Where is it?#asahi-re · 2026-01-14 20:57
nnym`bputil -d`?#asahi-re · 2026-01-14 20:55
nnymWhen given the default kernelcache, `kmutil configure-boot` produces a new kernelcache that seems to have all of the signs of a fuOS kernelcache. It boots successfully on a T6041.#asahi-re · 2026-01-14 18:12
nnym`otool` does not accept the ASN.1-wrapped kernelcache. If you mean the kext collection straight from `kmutil create`, here it is. https://paste.sr.ht/~nnym/91381031a5a701b5253a9310a195c36b83dbef24#asahi-re · 2026-01-14 16:51
nnymhttps://paste.sr.ht/~nnym/bc41ed859ca03652c5147fceb92f1d8bb590d940#asahi-re · 2026-01-14 16:51
nnymhttps://paste.sr.ht/~nnym/49b4051af4a9c66fcae878ca604c1b81312fd82f#asahi-re · 2026-01-14 14:23
nnymI don't know how to check the tags but I see "fuos" after "IM4P" near the beginning when I look at it with a text editor; ditto for the custom kext collection's kernelcache.#asahi-re · 2026-01-14 13:34
nnymThere is no Mach-O header.#asahi-re · 2026-01-14 01:48
nnymHow can I get the tags?#asahi-re · 2026-01-14 01:48
nnymproperties are obfuscated so I don't know what most of them mean but here they are anyway. https://paste.sr.ht/~nnym/bcb5f6ae0b5217cdd66ef7a45f6227345c09a385#asahi-re · 2026-01-14 01:48
nnymI made a kext collection with `kmutil create`, configured it as the boot object, and examined it with `kmutil inspect` with various options but none seems to refer to "tags". With `--show-mach-header`, it shows at the top that both the custom kernelcache and Apple's kernelcache have `flags: 0x0`; with `--show-mach-boot-properties`, it shows different boot properties for each. The#asahi-re · 2026-01-13 01:47
nnymUnless I can use something else?#asahi-re · 2026-01-13 01:47
nnymIf I understand correctly, the conversation above was about checking the tags set by `kmutil configure-boot` for Mach-O boot objects; so in order to do that, I need an m1n1 Mach-O.#asahi-re · 2026-01-13 01:33
nnymAlso, I thought that text sections were supposed to be always executable so why are there 2?#asahi-re · 2026-01-13 01:25
nnym"LC_THREAD.UNKNOWN_ARCHITECTURE.0"; `ipsw macho info build/m1n1.macho` shows several segments including "TEXT" but not "__TEXT". When I renamed "TEXT" to "__TEXT" in `m1n1.ld`, `kmutil` complained next about a missing `__TEXT_EXEC` segment. Is this a new requirement in firmware version 26.0?#asahi-re · 2026-01-13 01:25
nnym`kmutil configure-boot -c m1n1.macho -C -v /Volumes/test` keeps failing and saying "found valid Mach-O binary, deriving Mach-O boot properties...\nFileset Error: Invalid Mach-O boot properties. Fileset Error: Failed to find __TEXT segment" even with a clean build from upstream main. `aarch64-apple-darwin-objdump -x build/m1n1.macho` shows a single section named#asahi-re · 2025-11-24 21:22
nnymAfter redownloading the KDKs and extracting them with ipsw (github.com/blacktop/ipsw), I can find `ps-regs` in each of them.#asahi-re · 2025-11-24 19:38
nnymGood to know.#asahi-re · 2025-11-24 19:36
nnymOh. No. It's probably because I didn't install the 13.0 beta 1 and 13.1 KDKs; I only `7z x`d them on my Linux computer until I got their `Payload`s. I'm guessing that they're compressed then. Size checks out. I did install the other KDKs that I mentioned though. Does upgrading macOS do something to the KDKs?#asahi-re · 2025-11-24 19:24
nnymI ran `rg -a ps-regs` on macOS 13.0 beta 1, 13.1, 15.0, 15.6, and 26.0 KDKs and didn't get any hits so it seems to be unused for a long time. Is it used in an earlier version?#asahi-re · 2025-10-28 21:22
nnymI suspected that something was missing. So it's true after all.#asahi-re · 2025-10-28 21:18
nnymYeah.#asahi-re · 2025-10-28 21:17
nnymYeah but this is a development build and XNU's source code is public.#asahi-re · 2025-10-28 20:49
nnymWell, they do have names but they're like "param_1" and "uVar1".#asahi-re · 2025-10-28 20:47
nnymI have `kernel.development.t6041` from the 25A353 KDK loaded in Ghidra and functions and global variables have names but parameters and local variables don't. Is this how it should be?#asahi-re · 2025-10-17 11:30
nnymYou can tell? It's all the same to me.#asahi-re · 2025-10-17 11:16
nnymInteresting. In case you're still interested, the names are "ATC{0,1}-USB-V", "ATC{0..3}_CIO_USB", "ATC{0..3}_USB_AON", "ATC{0..3}_USB", "ATC{0..3}-USB-DART", "AUSB{0..3}-AONPCIE-V", and "ATC{0..3}_USB_AON_V".#asahi-re · 2025-10-17 11:04
nnymJ616c has 6 groups of 4 similarly named USB pmgr devices but there are only 3 USB ports. The exceptions are "ATC{0,1}-USB-V" which are only 2. What does that mean? Is the MagSafe port the 4th?#asahi-re · 2025-10-16 21:22
nnymI'm seeing some differences between J516c and J616c.#asahi-re · 2025-10-16 21:11
nnymOh. Well, as it turns out, I don't need it for now. I was looking at `/arm-io/pmgr`'s `reg` and it's the same in the IPSW.#asahi-re · 2025-10-16 19:58
nnymJ616cAP#asahi-re · 2025-10-16 19:56
nnymWell, I need an ADT that's similar to my J616 but from a previous generation; J516 would be best.#asahi-re · 2025-10-16 19:36
nnymIs there some place wherefrom I can get a full ADT ripped directly from the boot environment of a different Mac (to compare to mine)?#asahi-re · 2025-10-10 10:58
nnymSounds good. I'll check it out.#asahi-re · 2025-10-10 10:54
nnymI think that there's too much information for me to capture with my phone. What kind of information is missing from the IPSW?#asahi-re · 2025-10-10 09:28
nnymThanks. I want to see the whole devicetree so I'll use the boot argument.#asahi-re · 2025-10-10 07:58
nnymDo I understand correctly that I can get the complete devicetree only from the boot arguments?#asahi-re · 2025-10-07 13:42
nnymOr the other way around. Stacks confuse me.#asahi-re · 2025-10-07 13:01
nnymBut I think that that should be simple because that means that the next frame pointer is bigger instead of being smaller.#asahi-re · 2025-10-07 12:58
nnymDoes preventing a fault require any more than verifying that the frame pointer and the PC point to the right sections before dereferencing them? And if getting stuck otherwise means following a bad frame pointer that causes a cycle, I don't check that.#asahi-re · 2025-10-07 11:53
nnymm1n1 didn't seem to be able to print a stack trace so I added that to `print_regs`. Would it be desirable upstream?#asahi-re · 2025-10-07 08:25
nnymLooks like the value of `_text_size` is actually the value at the address `. - _text_start` so I have to take its adddress but that just gives me a meaningless virtual address.#asahi-re · 2025-10-07 07:59
nnymI declared `extern size_t _text_size` matching the symbol in `m1n1-raw.ld` and when I printed it I got 0x6162203a43495045 which is bigger than the entire linear address space. `_text_size` is just `. - _text_start` immediately after the text section.#asahi-re · 2025-10-06 07:36
nnymIt works but I had to subtract 4 or pass `-i` to get the right file; no big deal. I can also get the column if I `aarch64-linux-gnu-objdump -dW` but that's more involved. Anywway, this makes things much easier; thanks.#asahi-re · 2025-10-06 07:23
nnymNope.#asahi-re · 2025-10-06 07:22
nnymwithout `--strip-debug` but the resulting flat binary file didn't boot at all so I couldn't print the source location.#asahi-re · 2025-10-06 07:22
nnymI need a good method of finding the piece of source code associated with an instruction. Currently I have 5-second delay after an unhandled exception so I find the IP and then disassemble and search `m1n1-raw.elf` for that address and try to figure out which statement or expression produced it; it takes a while. I also tried `aarch64-linux-gnu-objcopy -O binary build/m1n1.elf`