#asahi-dev · 2025-12-20 15:07
nickchanOf course this explodes#asahi-dev · 2025-12-20 15:06
nickchanhttps://github.com/AsahiLinux/m1n1/blob/main/proxyclient/m1n1/proxy.py python code: P_MEMALIGN = 0x602, P_FREE = 0x602#asahi-dev · 2025-12-20 15:06
nickchanhttps://github.com/AsahiLinux/m1n1/blob/8e263536bfe664d8d624bc5071279491a73c38ce/src/proxy.h#L99 c code: P_MEMALIGN = 0x602, P_FREE = 0x603#asahi-dev · 2025-12-20 15:06
nickchan... p.free actually calls memalign #asahi-dev · 2025-12-20 15:01
nickchanokay this is even more cursed, if i p.call the free symbol at the last step instead of using p.free then *that* works#asahi-dev · 2025-12-20 14:54
nickchanthe last p.free would cause a data abort#asahi-dev · 2025-12-20 14:54
nickchanfrom m1n1.loadobjs import * lp = LinkedProgram(u) posix_memalign = next(x for x in lp.symbols if x[1] == "posix_memalign")[0] pp = u.malloc(8) p.call(posix_memalign, pp, 0x4000, 0x4000) p.free(p.read64(pp))#asahi-dev · 2025-12-20 14:53
nickchanhowever when I#asahi-dev · 2025-12-20 14:52
nickchanin rust/src/dlmalloc.rs it can be seen that rust uses posix_memalign() to obtain memory#asahi-dev · 2025-12-20 14:52
nickchanokay i don't understand how rust free ever worked#asahi-dev · 2025-12-20 14:17
nickchanokay i don't think freeing memalign ever worked#asahi-dev · 2025-12-20 14:11
nickchanthat causes m1n1 1.0 to crash as well#asahi-dev · 2025-12-20 13:59
nickchansimply calling p.free(p.memalign(0x4000, 0x1000)) crashes on t6000 on upstream m1n1#asahi-dev · 2025-12-20 13:58
nickchanokay so I dug into the mem corruption issue i have with t8015 nvme and appearetly it may not have anything to do with my own code at all?#asahi-dev · 2025-12-20 12:21
oliver_`eDP display without DP-HDMI conversion`#asahi-dev · 2025-12-20 12:21
jannauah#asahi-dev · 2025-12-20 12:20
oliver_according to the comment, it shouldnt be#asahi-dev · 2025-12-20 12:20
jannauI don't remember if main_display might be true for the HDMI port of M1 desktop devices#asahi-dev · 2025-12-20 12:20
oliver_thank you, then i'll adjust it again#asahi-dev · 2025-12-20 12:20
oliver_got it#asahi-dev · 2025-12-20 12:19
jannauyou still have to limit it to 14-/16-inch macbook pros, doesn't matter much anyway#asahi-dev · 2025-12-20 12:19
oliver_so you would really prefer the resolution check#asahi-dev · 2025-12-20 12:18
oliver_ah i see#asahi-dev · 2025-12-20 12:18
jannauthis is going to change soon anyway since I plan to split apple_connector#asahi-dev · 2025-12-20 12:18
oliver_iff main_display is already true for the internal display, that seems cleaner?#asahi-dev · 2025-12-20 12:17
jannauoliver_: I think the resolution of the internal displays is unique enough#asahi-dev · 2025-12-20 12:16
oliver_jannau: regarding your comment on setting the timestamps only for the internal display: i am now checking for dcp->main_display, is valid too? #asahi-dev · 2025-12-19 15:15
fl0_idsven I also am interested in a ticket, I am still waiting to hear from a friend so far#asahi-dev · 2025-12-19 14:00
fl0_idoliver_ it's often possible to get resale tickets, this year there's an official resale site but also through ppl posting to social media etc#asahi-dev · 2025-12-19 11:17
nickchansame build works to chainload on t6000 so it's an issue in my own code paths#asahi-dev · 2025-12-19 10:47
nickchanokay the callsite is in rust_load_image() after a comparison check with 2 and after pt.find_by_partuuid()#asahi-dev · 2025-12-19 10:15
nickchanokay it's an USAGE_ERROR_ACTION in line 4782 of malloc.c#asahi-dev · 2025-12-19 09:41
nickchanget that while trying to chainload after `Searching for partition UUID: ...`#asahi-dev · 2025-12-19 09:41
nickchanif i get dlmalloc: internal error does that mean i have corrupted mem#asahi-dev · 2025-12-19 06:01
oliver_Sven: thank you. Toying with the idea was nice, but my parental leave ends this year and I am going to spend the time with the family #asahi-dev · 2025-12-18 23:36
b074tysm#asahi-dev · 2025-12-18 23:36
b074I just cant believe it#asahi-dev · 2025-12-18 23:35
b074you're right#asahi-dev · 2025-12-18 23:35
b074oh no#asahi-dev · 2025-12-18 23:33
chaos_princessmissing the -s in front of the symbol file#asahi-dev · 2025-12-18 23:33
chaos_princessyour args appear to be wrong, should be sth like `python3 proxyclient/tools/run_guest.py -s kernel.development.t8103.13.5 dev.kc.macho.development.13.5 -- "debug=0x14e serial=3 apcie=0xfffffffe -enable-kprintf-spam wdt=-1 clpc=0"`#asahi-dev · 2025-12-18 23:30
b074This is the full output of run_guest.py https://gist.github.com/thiago4455/4819d99118692e4a015a27b104fedb4d#asahi-dev · 2025-12-18 23:25
b074tracing back the definitions showed that this entry is defined only due to the UNIXTHREAD on the Mach-O file#asahi-dev · 2025-12-18 23:24
b074but on the load_macho function in hv/__init__.py, im getting an error due to a None macho.entry#asahi-dev · 2025-12-18 23:22
chaos_princessshould work then#asahi-dev · 2025-12-18 23:21
b074I do have the kernelcache built, and I'm passing it to the run_gest.py as described in "Starting the development kernel under the m1n1 hypervisor"#asahi-dev · 2025-12-18 23:19
chaos_princessi think you need to build the kernelcache, as described here https://asahilinux.org/docs/sw/m1n1-hypervisor/#getting-the-macos-development-kernel-and-creating-the-kernelcache#asahi-dev · 2025-12-18 23:17
b074but all mach-o files I downloaded does not include it https://gist.github.com/thiago4455/16da2733244309ef070a94df59fbd483#asahi-dev · 2025-12-18 23:17
b074I dont get it. It seems that a UNIXTHREAD command is expected to set the entry point (https://github.com/AsahiLinux/m1n1/blob/main/proxyclient/m1n1/macho.py#L146)#asahi-dev · 2025-12-18 22:30
svenoliver_: I can probably organize a ccc ticket if you want to attend, there’s like 4 or so speakers at the fail0verflow assembly who don’t need the ticket that they bought and I don’t think we sold all of them yet