#
#asahi-dev · 2026-09-30 08:35
yukaon t8132
#asahi-dev · 2026-09-30 08:35
yuka*I had
#asahi-dev · 2026-09-30 08:35
yukabut yeah, I iboot crashes on 27.x no matter what
#asahi-dev · 2026-09-30 08:34
yukacheck if your m1n1 binary is padded to multiples of 4K/16K/64K
#asahi-dev · 2026-09-30 08:28
svenalso tested sptm on 27.x beta on my old m1 so presumably that will work on m4 pro as well
#asahi-dev · 2026-09-30 08:28
svenI did hv bringing with 26.7 on m4 pro so that should work
#asahi-dev · 2026-09-30 07:57
devdragoi also just had a duh-doy moment bc i just remembered i recently upgraded my main macOS install to 27.0... it was doing the boot loop before when i was on 26.x, but i assume my system firmware being on 27.x-era firmware will probably be bad for debugging regardless, is that correct
#asahi-dev · 2026-09-30 07:55
devdragojust tried again with NO_DISPLAY and BRINGUP enabled (neither of which i had before), still bootlooping, probably <4 seconds between the apple icon displaying and the screen going black again
#asahi-dev · 2026-09-30 07:08
yukaif you want to revert the original thing and let me make a new PR later that's also fine
#asahi-dev · 2026-09-30 07:08
yuka(not tested, I'm busy with all systems go today)
#asahi-dev · 2026-09-30 07:08
yukahttps://github.com/AsahiLinux/m1n1/pull/689 for the inverted wfi bootargs condition
#asahi-dev · 2026-09-30 07:07
svenm4 pro works for me, I have NO_DISPALY in config.h but it should work even without that
#asahi-dev · 2026-09-30 07:03
devdragoatm? Or is this a known / previously encountered error?
#asahi-dev · 2026-09-30 07:03
devdragoHello, on my M4 Pro MBP (T6040, J616sAP) I'm having trouble booting into m1n1 in proxy mode. I installed manually using `kmutil configure-boot` which I assume is the only way right now, m1n1 was built from the most recent commit, and I've double checked that I'm installing from 1TR on the correct volume; however it just bootloops. Is there an alternative boot flow for T604x SOCs
#asahi-dev · 2026-09-30 06:11
yukasorry, I am once again reminded I should always test the code before pushing some "small fixes" because then this happens
#asahi-dev · 2026-09-30 06:10
yukaArgh
#asahi-dev · 2026-09-30 06:08
nickchanit would add boot args if sysregs are *NOT* locked
#asahi-dev · 2026-09-30 06:08
nickchanhttps://github.com/AsahiLinux/m1n1/commit/3a69c73f59332b7b617835fd9a1c49dc89edcfd2 excuse me isn't this backwards
#asahi-dev · 2026-09-29 18:45
yukaI see, let's hope that works ^^
#asahi-dev · 2026-09-29 18:45
flokliyuka: I should get remote hands in 2-3 days
#asahi-dev · 2026-09-29 18:44
yukaAlso since flokli's setup is currently down, I don't have a machine to continue working on / testing those device trees. Maybe I should get an M4 Pro or M4 Max. Any particular device we would like to test on but nobody has it yet?
#asahi-dev · 2026-09-29 18:43
svennice, gonna try tomorrow then
#asahi-dev · 2026-09-29 18:43
yukait's just not complete (enough) / some pmgr stuff is commented out
#asahi-dev · 2026-09-29 18:43
yukasven there's a device tree: https://cyberchaos.dev/yuka/linux/-/commit/4d4732812bae3bf93bc5aa79c3dda557fd4426d0
#asahi-dev · 2026-09-29 18:02
svenwhile the CTRR are just 0x8000000000000001
#asahi-dev · 2026-09-29 18:02
sventhat's how i e.g. have to init one of them to make sptm happy
#asahi-dev · 2026-09-29 18:02
svensptm_cpus[i].shadow[HV_SPTM_ACC_CTXR_A_CTL_EL2] = 0xc000000000aa019a;
#asahi-dev · 2026-09-29 18:02
sveni don't know, i just know their names but the control register is more complicated
#asahi-dev · 2026-09-29 18:01
chaos_princessis ctxr a thing that disallows execution outside of specified regions?
#asahi-dev · 2026-09-29 18:01
sventhey have the same values on m4 pro so it should work
#asahi-dev · 2026-09-29 18:00
svencan you try using the _EL1 variant and see if that still works?
#asahi-dev · 2026-09-29 17:59
svenyuka: can't test linux boot yet because i don't have device trees for M4 but I found the names for the weird CTRR registers in SPTM and I think also their _EL1 variant https://github.com/AsahiLinux/m1n1/pull/688/changes
#asahi-dev · 2026-09-28 21:31
myriaMain thing that I need to check if it works for now is if `perf stat -e r011:u sleep 5` runs sucessfully and returns a non-zero count
#asahi-dev · 2026-09-28 21:29
myriaUhh, yeah
#asahi-dev · 2026-09-28 21:29
chaos_princessyou should probably tell people how to test that
#asahi-dev · 2026-09-28 21:29
myriaDevice trees aren't there, but they should be similar to the M3 device trees, just with different compatibles
#asahi-dev · 2026-09-28 21:28
myriaHey, would someone on an M4+ be able to test https://github.com/sempiternal-aurora/linux/pull/1 ?
#asahi-dev · 2026-09-28 15:37
svenfeels like i'm hitting even more weird timing edge cases than before on this m4 pro compared to my old m1
#asahi-dev · 2026-09-28 15:35
svenin other cursed news, i occasionally see hv rendezvous failures now. wasn't that smp issue bad enough? :(
#asahi-dev · 2026-09-28 11:15
jannaudt-binding, driver and dts chnages to fix this properly. dts changes alone "fix" it since the power-domains are enabled on boot
#asahi-dev · 2026-09-28 10:09
mazah!
#asahi-dev · 2026-09-28 09:55
jannauworks when aic on the second die is not turned off
#asahi-dev · 2026-09-28 09:50
jannaueven with pd_ignore_unused
#asahi-dev · 2026-09-28 09:49
jannaulooks power-state related. something in pmgr1_die1 breaks it
#asahi-dev · 2026-09-28 09:25
mazone possibility is that enabling the second soc routes interrupts over there, but that we're missing something that allows the interrupt to be observed on that second soc.
#asahi-dev · 2026-09-28 09:21
jannaustarts working with an empty second soc node
#asahi-dev · 2026-09-28 09:20
jannauI don't see how that would suddenly break late during boot
#asahi-dev · 2026-09-28 09:12
mazmaybe not on a per-CPU basis, but on a die basis?
#asahi-dev · 2026-09-28 09:11
mazhave they restored some form of affinity management, AIC1-style?
#asahi-dev · 2026-09-28 09:02
jannautimer FIQs are still delivered

plus ›