#
#asahi-dev · 2025-12-12 18:03
oliverand how does the linux kernel handle this then? it just talks 13.5 and the dcp is reverse compatible?
#asahi-dev · 2025-12-12 18:02
oliveri see
#asahi-dev · 2025-12-12 17:58
chaos_princessdcp changes between versions, and tracer does 12.3(?) or 13.5 specifically
#asahi-dev · 2025-12-12 17:58
chaos_princessyes
#asahi-dev · 2025-12-12 17:52
oliveri am running macos 15.7 right now. is that too new?
#asahi-dev · 2025-12-12 17:49
oliverwith all kind of sizes for all kind of messages
#asahi-dev · 2025-12-12 17:49
oliver` messages.
#asahi-dev · 2025-12-12 17:49
oliverwhen running the parse_log script i also get a lot of `Expected 0x6f0 bytes, got 0x730 bytes (in)
#asahi-dev · 2025-12-12 16:52
oliverThanks
#asahi-dev · 2025-12-12 16:52
jannaupossible an issue from the aop tracer. I might have fixed that only locally. I'll check for unmerged DCP trace change later today
#asahi-dev · 2025-12-12 16:50
oliverin DCPTracer
#asahi-dev · 2025-12-12 16:49
oliverokay, after disabling some of the endpoints, i could now boot the system
#asahi-dev · 2025-12-12 16:34
oliverEverything that inherits from EPICEp in trace_dcp.py seems to have this issue
#asahi-dev · 2025-12-12 14:31
oliver`
#asahi-dev · 2025-12-12 14:31
oliversetting the environment variable did not help. i was trying to trace the dcp with the internal display on my m1 pro. i set `dcp_name = "dcp"` in trace_dcp.py and also changed line 34 to `"/arm-io/dart-disp0"`. Using dcp0 seems not to be part of the device tree: `"Child node 'dcp0' not found"
#asahi-dev · 2025-12-12 13:27
jannauwhich device are you tracing?
#asahi-dev · 2025-12-12 13:26
jannauotherwise I'll take a look what dcp tracing change I have locally
#asahi-dev · 2025-12-12 13:26
jannauthat might just required for parse_log though. we should change the default
#asahi-dev · 2025-12-12 13:25
jannauoliver: try exporting AGX_FWVER=V13_5
#asahi-dev · 2025-12-12 13:12
oliverfull exception: https://pastebin.com/diBqHN2m
#asahi-dev · 2025-12-12 13:11
olivercan that be some kind of firmware/tooling missmatch?
#asahi-dev · 2025-12-12 13:11
oliverparsing expected 2 but parsed 0
#asahi-dev · 2025-12-12 13:10
oliverconstruct.core.ConstError: Error in path (parsing) -> version
#asahi-dev · 2025-12-12 13:10
oliverThank you. After replacing dcp0 with dcp and disp with disp0, it actually did print some back end forth. it then crashes with:
#asahi-dev · 2025-12-12 11:07
jannauit has at the bottom a a commented line to write the log for parse_log.py
#asahi-dev · 2025-12-12 11:06
jannauoliver: see proxyclient/hv/trace_dcp.py you use that with `./tools/run_guest.py -m hv/trace_dcp.py ...`
#asahi-dev · 2025-12-12 11:02
oliveri am now able to boot a macos kernel under the hypervisor. how would i now run a tracer, say trace dcp calls? i ran `trace_device("arm-io/dcp")` followed by `cont`. that gives me this log: https://pastebin.com/0KkJ5SjE is that everything? how would i get a file i could put int othe dcp parse_log command?
#asahi-dev · 2025-12-11 12:32
oliveri'll try to go with the second macos install. Need to check if i still have enough space on the drive. linux got most of it
#asahi-dev · 2025-12-11 12:32
oliverno i am not specificly targeting that version, i just wanted to get m1n1 and tracing working for now.
#asahi-dev · 2025-12-11 12:31
chadmedtheres some oddness with newer versions
#asahi-dev · 2025-12-11 12:31
chadmedbut if youre trying to target 13.5 specifically yeah this wont work and youll need a second macos
#asahi-dev · 2025-12-11 12:31
oliverokay
#asahi-dev · 2025-12-11 12:30
chadmedno, it will just wait for a proxy connection
#asahi-dev · 2025-12-11 12:30
chaos_princessunlikely the main install is 13.5
#asahi-dev · 2025-12-11 12:30
oliverit will then automatically boot to macos if no usb device/proxy is connected?
#asahi-dev · 2025-12-11 12:30
chadmedreverting back to the vanilla macos kernel is as simple as running bputil -f from 1TR
#asahi-dev · 2025-12-11 12:29
chadmedif youre not particularly fussed about the data on your "main" macos install you can just install m1n1 as the boot kernel on that volume
#asahi-dev · 2025-12-11 12:14
oliveryea that makes sense. john_travolta.gif
#asahi-dev · 2025-12-11 12:12
chaos_princessright now it is trying to load macos rootfs from the asahi volume, going "where is everything?" and panicking
#asahi-dev · 2025-12-11 12:11
oliverah, okay, got it. thank you
#asahi-dev · 2025-12-11 12:08
chaos_princessif you want to use m1n1 as a hypervisor, you need to install a full separate copy of macos, and then replace it's kernel with m1n1
#asahi-dev · 2025-12-11 12:08
chaos_princessactually, > "and m1n1 came with that" - you are doing it wrong.
#asahi-dev · 2025-12-11 12:07
chaos_princesswhen you did kmutil configure-boot, what did you specify as the -v parameter
#asahi-dev · 2025-12-11 11:58
oliverand m1n1 came with that
#asahi-dev · 2025-12-11 11:57
oliverI dont know what that means. I installed asahi linux using the alx.sh script, which is working fine.
#asahi-dev · 2025-12-11 11:52
chadmedoliver: is m1n1 installed on top of the blessed macos root contianer?
#asahi-dev · 2025-12-11 11:51
oliverI see that I did not need to specify the root volume of the macos install in this command, can I assume that the kernelcache knows what to boot?
#asahi-dev · 2025-12-11 11:51
oliverThe docs tell me to debug using a second picocom command like `picocom -b 115200 /dev/m1n1-sec` but that did not output anything.
#asahi-dev · 2025-12-11 11:51
oliverm1n1 copied the kernel to the macbook, but after a few seconds I only get the rainbow apple and the following m1n1 logs: https://pastebin.com/2mwayBit
#asahi-dev · 2025-12-11 11:50
oliverHello, i am trying to run a stock macos kernel under m1n1 on a m1 pro with firmware version 13.5. I followed the guides, extracted the kernelcache (there where two for some reason), connected via usb, chainloaded m1n1 and then tried to boot the kernel via `python3 tools/run_guest.py -S ~/k1.macho -- "debug=0x14e serial=3 apcie=0xfffffffe -enable-kprintf-spam wdt=-1 clpc=0"`.

plus ›