#asahi-dev · 2026-07-02 07:03
Sobek[m]integralpilot: FYI see https://social.treehouse.systems/@AsahiLinux/116813000429256653 there are now suitable kernels.#asahi-dev · 2026-07-02 06:52
Sobek[m](I just don’t have the right to close the issue on GH, but I’ll drop the line)#asahi-dev · 2026-07-02 06:50
chaos_princessSobek[m]: 517#asahi-dev · 2026-07-02 06:46
Sobek[m]integralpilot: What I thought, happy I had guessed right.#asahi-dev · 2026-07-02 06:41
Sobek[m]Yaaay, so that issue is basically a duplicate bug. Do we have a Asahi-radar number to close the issue as duplicate of asahi-radar:xyz ? 😈#asahi-dev · 2026-07-02 06:40
integralpilotyou can either: 1. stop macsmc-power from loading, 2. apply the patch & rebuild kernel, 3. DFU revive to get rid of the newer SMC firmware#asahi-dev · 2026-07-02 06:39
integralpilotyes, the bootloop is a result of the battery firmware change#asahi-dev · 2026-07-02 06:39
Sobek[m](I really want to turn anyone who installs macOS beta and surprises pikatchu when it doesn’t work into a newt(on). Obviously they didn’t give exact versions)#asahi-dev · 2026-07-02 06:39
Sobek[m]Checking a thing, boot loop on Asahi after updating macOS 27 beta is a known issue due to the battery firmware change ? Or that would result in different symptoms ?#asahi-dev · 2026-07-02 04:15
integralpilotit did work, thanks!#asahi-dev · 2026-07-02 04:04
integralpilotyes, it does go to iboot recovery. thank you so much for that, should save me a lot of time vs reviving, will try now #asahi-dev · 2026-07-02 03:47
NickChan[m]in which case... (full message at <https://matrix.org/oftc/media/v1/media/download/AZGUH4kLBBXK0oIZaUyA8vBs7vJqQ-Vl6bLN9tEN12KJGIjtMfPLaf8ghlfhSD1skp65PlIw_pqU3TIKvtNhHExCefaQnBdwAG1hdHJpeC5vcmcvWGNwbVhESG9FcUxCanJrSFhYTHZJZWlT>)#asahi-dev · 2026-07-02 03:46
NickChan[m]auto-boot false should send to iboot recovery shouldn't it#asahi-dev · 2026-07-02 03:45
integralpilotah thank you, good to know for when it finishes reviving!#asahi-dev · 2026-07-02 03:44
jannaustarting with macos 15 system firmware#asahi-dev · 2026-07-02 03:43
jannauit's BootPreference=%00 on apple silicon#asahi-dev · 2026-07-02 03:43
jannauintegralpilot: it'x https://support.apple.com/en-us/120622#asahi-dev · 2026-07-02 03:40
integralpilot"Downloading Mac software update - 60MB of 19.77 GB - 2 hours remaining" :(#asahi-dev · 2026-07-02 03:32
integralpilotin my case i saw that there was one var auto-boot=TRUE and was like "well it annoys me when it turns on automatically when i open the lid, i'll change it to FALSE" and now i get DFU. its reviving and should be fine, but lesson learned i guess#asahi-dev · 2026-07-02 03:29
JamesCalligeros[m]yeah be careful with nvram. a lot of the documented nvram vars are intel only and will send you to dfu if you apply them to apple silicon #asahi-dev · 2026-07-02 03:28
integralpiloti was messing around with random NVRAM vars so now i have to DFU revive LOL #asahi-dev · 2026-07-02 01:20
StanfordAppliedCyber[m]i didn't try just accessing a bunch of other pages to try to flush the fabric that way, i suppose i should try that#asahi-dev · 2026-07-02 01:20
StanfordAppliedCyber[m]also, i did try the dumb thing of just adding a sleep to the retype endpoint and that didn't solve the problem, unsurprisingly#asahi-dev · 2026-07-02 01:08
StanfordAppliedCyber[m]or use breakpoints on the allocator and for specifically this call return some address, i suppose that also works#asahi-dev · 2026-07-02 00:59
StanfordAppliedCyber[m]this has obvious risk though, and i'd like to see if anyone else has any better ideas before doing this#asahi-dev · 2026-07-02 00:56
StanfordAppliedCyber[m]i did have one idea: figure out how xnu allocates pages and specifically where it gets the entropy, patch the entropy to some fixed value so that page allocation becomes deterministic, then in the sptm emulator make sure that page is always mapped NC forever#asahi-dev · 2026-07-02 00:18
StanfordAppliedCyber[m]specifically the m3 just lacks the entire codepath that the a18 pro sptm binary has#asahi-dev · 2026-07-02 00:02
StanfordAppliedCyber[m]i havent fully looked into how m3 sptm works, but i'm not optimistic we can just copy the m3 sptm method#asahi-dev · 2026-07-02 00:00
StanfordAppliedCyber[m]also, i did look at the m3 sptm, and the answewr is that this endpoint just looks very different, the sysreg solution i thought worked earlier does in fact not work (i read the asm wrong)#asahi-dev · 2026-07-01 23:58
StanfordAppliedCyber[m]also, the instruction meaning is speculative, we can't run it because it doesn't exist on m3 and the locked gxf isue on m4#asahi-dev · 2026-07-01 23:56
StanfordAppliedCyber[m]for linux this isn't a problem because we'll just map the page nc to start and never change it, but i'm not quite sure how to hanle it here. the page changes every time so it's not like i can just add some hack that says "always mark X page as nc"#asahi-dev · 2026-07-01 23:55
StanfordAppliedCyber[m]so it sticks around, and nondeterministically the soc fabric sees it and panics#asahi-dev · 2026-07-01 23:55
StanfordAppliedCyber[m]but the error tells us there's some unexpected attributes. my hypothesis on what's going wrong is that some RW page was remapped to PAGE_TABLE_ALT, but there was some stale tag that's never flushed. this would normally be flushed by the custom gxf op, but we just can't do that#asahi-dev · 2026-07-01 23:54
StanfordAppliedCyber[m]importantly, after the panic, if we dump the mappings for the faulting page, it's already marked NC (correctly)#asahi-dev · 2026-07-01 23:53
StanfordAppliedCyber[m]PAGE_TABLE_ALT is the type for iommu owned page tables#asahi-dev · 2026-07-01 23:53
StanfordAppliedCyber[m]this is nondeterministic, tit doesn't happen every time#asahi-dev · 2026-07-01 23:52
StanfordAppliedCyber[m]well on about 50% of boots, we hit some error: UNEXP_RT_HIT_DIR from the command ncrdincri coming from the pmgr#asahi-dev · 2026-07-01 23:51
StanfordAppliedCyber[m]obviously we can't run this on m4#asahi-dev · 2026-07-01 23:51
StanfordAppliedCyber[m]basically, when SPTM retypes a page to type PAGE_TABLE_ALT, it runs the custom gxf instruction i mentioned earlier, which very likely does some cache maintainence stuff#asahi-dev · 2026-07-01 23:50
StanfordAppliedCyber[m]i need some advice on how to handle an error involving the custom gxf intructions m4+ sptm added#asahi-dev · 2026-07-01 20:25
jmcknice#asahi-dev · 2026-07-01 20:25
chaos_princesscongrats#asahi-dev · 2026-07-01 20:25
Tachyonray[m]Got the stage 1 installed on the M3#asahi-dev · 2026-07-01 20:24
Tachyonray[m]uploaded an image: (2158KiB) < https://matrix.org/oftc/media/v1/media/download/AfBJeqOcCZSvn_YAEBWq1CaVOjtKdSHUpLafjBbug8BpH5IUU3-2dUsY3tkA6FUOA_rvI99Ps6B25im3mcgdg3ZCefZ3PqGAAG1hdHJpeC5vcmcvSFRlalZMY2N3ZUV6RmJTeWRPT2tzTnlB >#asahi-dev · 2026-07-01 19:54
mischa85got linux running on all 16 cores on t6041 under HV. need to trap WFI/WFIT in HV for it to not bork out. keyboard also works nicely.#asahi-dev · 2026-07-01 19:24
jannauhas the ADT a misleading speaker config, is my understanding of how to map ADT to DT wrong or is our audio DT broken (14/16-inch MBP): https://github.com/AsahiLinux/m1n1/pull/612 ?#asahi-dev · 2026-07-01 13:29
integralpilot*going to bed now#asahi-dev · 2026-07-01 13:29
integralpilotgood to bed now hopefully by tomorrow should be able to write here from my patched upstream kernel, but we'll see#asahi-dev · 2026-07-01 13:28
integralpilotwifi upstreaming is going well#asahi-dev · 2026-07-01 10:06
enverbalalic+1 great blogpost, learned some new stuff!