2026-06-09
00:02voidah has quit [Ping timeout: 480 seconds]
00:11voidah has joined #asahi-dev
00:17hardy94 has quit [Remote host closed the connection]
00:19voidah has quit [Ping timeout: 480 seconds]
00:21voidah has joined #asahi-dev
00:24michaelros4444559 has quit [Ping timeout: 480 seconds]
00:25gargantu1 has quit [Ping timeout: 480 seconds]
00:30voidah has quit [Ping timeout: 480 seconds]
00:36michaelros4444559 has joined #asahi-dev
00:37voidah has joined #asahi-dev
00:41StanfordAppliedCyber[m]i just ended up disabling trusted accessory, it's not like we'll ever support those anyways
00:42StanfordAppliedCyber[m]bad news: more SEP issues, idk if i can just ignore these
00:43gargantua has joined #asahi-dev
00:46voidah has quit [Ping timeout: 480 seconds]
00:48StanfordAppliedCyber[m]AppleSEP:WARNING: timeout/error waiting for reply to lo: 0x170600. endpoint is enabled
00:53voidah has joined #asahi-dev
01:02voidah has quit [Ping timeout: 480 seconds]
01:05StanfordAppliedCyber[m]@ chaos princess it does appear that my problem is related to gigalocker
01:05StanfordAppliedCyber[m]xart and xarm can all send and receive messages which is strange
01:10voidah has joined #asahi-dev
01:18voidah has quit [Ping timeout: 480 seconds]
01:22voidah has joined #asahi-dev
01:31voidah has quit [Ping timeout: 480 seconds]
01:31pb17 has quit [Remote host closed the connection]
01:31pb17 has joined #asahi-dev
01:41voidah has joined #asahi-dev
01:49voidah has quit [Ping timeout: 480 seconds]
01:54voidah has joined #asahi-dev
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-dev
02:03voidah has quit [Ping timeout: 480 seconds]
02:11voidah has joined #asahi-dev
02:20voidah has quit [Ping timeout: 480 seconds]
02:23voidah has joined #asahi-dev
02:42tobhe has joined #asahi-dev
02:48tobhe_ has quit [Ping timeout: 480 seconds]
02:56renoo has quit [Remote host closed the connection]
03:02voidah has quit [Ping timeout: 480 seconds]
03:04nela has quit [Quit: Ping timeout (120 seconds)]
03:05nela has joined #asahi-dev
03:08gargantua has quit [Ping timeout: 480 seconds]
03:11voidah has joined #asahi-dev
03:20voidah has quit [Ping timeout: 480 seconds]
03:28voidah has joined #asahi-dev
03:28StanfordAppliedCyber[m]well, i just tossed the xart device tree node from the ADT and those problems magically went away
03:35StanfordAppliedCyber[m]it's possible apple has massively reduced the capabilities of the SEP in raw boot mode
03:35StanfordAppliedCyber[m]it's not advertising the media key i need to decrypt user data
03:36StanfordAppliedCyber[m]i may have to dump this from a running macos installation
03:36StanfordAppliedCyber[m]like, run a real macho payload in that container, custom kext, dump the key, profit
03:36voidah has quit [Ping timeout: 480 seconds]
03:36StanfordAppliedCyber[m]specifically it never publishes sep-endpoint,sks
03:43nora_ has joined #asahi-dev
03:44voidah has joined #asahi-dev
03:45nora has quit [Ping timeout: 480 seconds]
03:52marvin24 has joined #asahi-dev
04:02asahi has joined #asahi-dev
04:03asahi has quit [Remote host closed the connection]
04:07sventhere’s some side channel between NVMe and Sep and the key the main SoC sees changes each boot
04:08StanfordAppliedCyber[m]possibly? i thought about that, it's definitely possible
04:08StanfordAppliedCyber[m]this is the user data key, the thing that encrypts /Users
04:09StanfordAppliedCyber[m]well, xart (the endpoint) responds, it's stac that's having issues
04:10StanfordAppliedCyber[m]i have a script that successfully decrypted some files on some other volume on the local machine so i'll see if it works
04:11StanfordAppliedCyber[m]if it doesn't then it's time to bash my head against a wall hoping SEP works
04:19voidah has quit [Ping timeout: 480 seconds]
04:26voidah has joined #asahi-dev
04:29eluks has quit [Remote host closed the connection]
04:30eluks has joined #asahi-dev
04:35voidah has quit [Ping timeout: 480 seconds]
04:42voidah has joined #asahi-dev
04:42StanfordAppliedCyber[m]ah yes this does appear to be a problem, it takes the real aes key, encrypts it with some ephmeral key generated from TRNG, then xnu just takes the encrypted key and passes it to ANS
04:43StanfordAppliedCyber[m]well i suppose i get to get xart working then
04:43StanfordAppliedCyber[m]but xart does work?
04:43StanfordAppliedCyber[m]okay this is very fun
04:44StanfordAppliedCyber[m]this does make me feel slightly better though, because it likely means it's something I'M doing wrong as opposed to this just being impossible in raw boot mode
04:51voidah has quit [Ping timeout: 480 seconds]
04:58StanfordAppliedCyber[m]this was never an issue with previous hypervisors?
04:58voidah has joined #asahi-dev
05:02StanfordAppliedCyber[m]chaos_princess: what do we know about gigalocker? like, what sets it up and how does sep talk to it?
05:02StanfordAppliedCyber[m]i'm running out of ideas on what we could possibly be breaking that's causing sep xart to be unhappy
05:03StanfordAppliedCyber[m]dart-txm is totally silent, the firmware is definitely loaded
05:03StanfordAppliedCyber[m]also, when is it configured in regular macos boot? is it before or after decryption of user data (and thus the publishing of the sks service)?
05:06StanfordAppliedCyber[m]ack, i'm really hoping this is just something i'm doing wrong because if it's not then we have problems
05:06elvishjerricco0 has joined #asahi-dev
05:06StanfordAppliedCyber[m]i suppose that in itself is a finding-- "m1n1 hypervisor will never work on raw boot mode", but that would be a sad discovery
05:07StanfordAppliedCyber[m]then again we'd never get a clear Y/N, it'd just be "the sep black box won't work with us and we dont know why"
05:07voidah has quit [Ping timeout: 480 seconds]
05:08renoo has joined #asahi-dev
05:12elvishjerricco has quit [Ping timeout: 480 seconds]
05:12elvishjerricco0 is now known as elvishjerricco
05:14voidah has joined #asahi-dev
05:23voidah has quit [Ping timeout: 480 seconds]
05:30voidah has joined #asahi-dev
05:34StanfordAppliedCyber[m]okay it's definitely not gigalocker
05:35StanfordAppliedCyber[m]none of the gigalocker endpoints are touched before we panic
05:39voidah has quit [Ping timeout: 480 seconds]
05:48voidah has joined #asahi-dev
05:50StanfordAppliedCyber[m]yeah im really not sure how to debug this-- i just don't get a reply to the stac command
05:56voidah has quit [Ping timeout: 480 seconds]
05:58voidah has joined #asahi-dev
06:06voidah has quit [Ping timeout: 480 seconds]
06:08StanfordAppliedCyber[m]i can verify that the txm-dart secure channel is both totally fine and not used for this cmd, that the SEP has successfully written to the OOL pages for different cmds in the same endpoint, and that the sep firmware is definitely alive
06:15NickChan[m]Did you run txm?
06:15StanfordAppliedCyber[m]the only "obvious" thing is that a bunch of TXM is currently stubbed out to either return success or not supported
06:15StanfordAppliedCyber[m]wow we had the same thought at the same time
06:15StanfordAppliedCyber[m]i'll see if i can rule txm out next
06:15voidah has joined #asahi-dev
06:18NickChan[m]txm shouldn't be overly hard to virtualize the main issue is m1n1 hypervisor can only host a single guest
06:18StanfordAppliedCyber[m]txm is currently the most BS emulator endpoint by far, dart/sart/nvme/uat are all pretty legit, xnu_bootstrap i had to slave over but i'm very confident works
06:18StanfordAppliedCyber[m]that's not a terrible idea, if i run out of ideas i'll look into it
06:19NickChan[m]well, I say virtualize, but what I mean is run an unprivileged application since txm runs in GL0; still has context switch issue though
06:21StanfordAppliedCyber[m]yeah i'm familiar
06:21StanfordAppliedCyber[m]but it does some weird stuff involving svc being turned into an hvc effectively by some weird mechanism
06:21StanfordAppliedCyber[m]i'd probably just run the whole thing in el1 and patch svc --> hvc
06:22StanfordAppliedCyber[m]as a bonus all the shared mappings are really easy because we know exactly what they are by the emulator
06:22NickChan[m]svc turned into hvc is VHE
06:22StanfordAppliedCyber[m]i thought there was some apple custom wrinkle to it, not just standard vhe
06:23StanfordAppliedCyber[m]idk, tbh i havent' really looked at the txm firmware, i've mostly just looked at the xnu source and gone "how can i make this take the right code path"
06:23nickchan-https://developer.arm.com/documentation/ddi0601/2026-03/AArch64-Registers/HCR-EL2--Hypervisor-Configuration-Register
06:24nickchan- has quit [Quit: ZNC 1.9.1+deb2+b3 - https://znc.in]
06:24nickchan has joined #asahi-dev
06:24voidah has quit [Ping timeout: 480 seconds]
06:30StanfordAppliedCyber[m]oh for fucks sake i may just be a fucking idiot
06:30StanfordAppliedCyber[m]i set a bunch of stuff wrong in txm along with a lot of it being stubbed out
06:31svenputting it into el1 seems painful when you can just put it into gl0 and leave el1 state alone
06:32StanfordAppliedCyber[m]well it literally does run in the userspace level of the GLs
06:32StanfordAppliedCyber[m]at the same time it is literally just xnu code they copy pasted into the sptm firmware
06:33voidah has joined #asahi-dev
06:34nickchanthe txm image is also unified so I expect it to not directly access any hardware or coprocessor
06:39StanfordAppliedCyber[m]it doesn't have any direct access to hardware or coprocesor
06:41StanfordAppliedCyber[m]OH, FOR, FUCKS, SAKE
06:41StanfordAppliedCyber[m]problem solved
06:41StanfordAppliedCyber[m]shot msyelf in the foot
06:42voidah has quit [Ping timeout: 480 seconds]
06:43StanfordAppliedCyber[m]well i can officially see sks now
06:44mattia013 has quit [Remote host closed the connection]
06:44StanfordAppliedCyber[m]a previous diagnostic turned off was turning off com.apple.driver.AppleMobileApNonce and i left it on by accident
06:44StanfordAppliedCyber[m]like i left the diagnostic on
06:45StanfordAppliedCyber[m]turned that off, oh wow we see sks
06:45StanfordAppliedCyber[m]facepalm
06:45StanfordAppliedCyber[m]well, i'll tell myself we all have air head moments
06:45StanfordAppliedCyber[m]good news: 51 processes running, some panic that i think i have the solution for
06:46StanfordAppliedCyber[m]yeah i'm not nearly as worried about this next one, it's some ipi delivery thing i think
06:46StanfordAppliedCyber[m]i can fix that
06:46StanfordAppliedCyber[m]nah, that panics pmgr
06:46StanfordAppliedCyber[m]i tried that when I was debugging smp on 26.4.1
06:48mattia013 has joined #asahi-dev
06:50voidah has joined #asahi-dev
06:50pjv has joined #asahi-dev
06:58voidah has quit [Ping timeout: 480 seconds]
06:59voidah has joined #asahi-dev
07:05violette- has quit [Remote host closed the connection]
07:05pb17 has quit [Ping timeout: 480 seconds]
07:07voidah has quit [Ping timeout: 480 seconds]
07:08pb17 has joined #asahi-dev
07:15voidah has joined #asahi-dev
07:28pjv has quit [Quit: pjv]
07:36voidah has quit [Ping timeout: 480 seconds]
07:44voidah has joined #asahi-dev
07:48freetolga has quit [Quit: Connection closed for inactivity]
07:52voidah has quit [Ping timeout: 480 seconds]
08:00voidah has joined #asahi-dev
08:08voidah has quit [Ping timeout: 480 seconds]
08:16voidah has joined #asahi-dev
08:21flokliStanfordAppliedCyber[m]: "debugging smp on 26.4.1"... How's the error behavior for you with that?
08:22StanfordAppliedCyber[m]i updated to 26.5 and it fixed all my problems
08:22StanfordAppliedCyber[m]no clue what the issue on 26.4.1 was but i'm 99% sure it was some iboot thing
08:22StanfordAppliedCyber[m]i had people send me their known good m1n1 binaries which i just directly flashed and didn't work
08:22StanfordAppliedCyber[m]i tried replaying literally every mmio access xnu made in the same order and it didn't work
08:22StanfordAppliedCyber[m]i tried every live probe you can think of and the cores would just not drop out of reset
08:23StanfordAppliedCyber[m]update to 26.5 --> wow smp works all of a sudden
08:24StanfordAppliedCyber[m]these machines work in mysterious ways
08:25voidah has quit [Ping timeout: 480 seconds]
08:33chaos_princessi think the "mysterious ways" is "apple fixing their bugs"
08:34voidah has joined #asahi-dev
08:41r0ni has quit [Ping timeout: 480 seconds]
08:43picnoir has quit [Quit: WeeChat 4.9.0]
08:43voidah has quit [Ping timeout: 480 seconds]
08:43picnoir has joined #asahi-dev
08:45chaos_princesspmuch
08:48flokliStanfordAppliedCyber[m]: ok, I am on still on 26.4. Guess I'll spend some time upgrading and re-installing m1n1 into that.
08:52voidah has joined #asahi-dev
08:58jannauflokli: this is possibly an a18 pro only issue (apparently affecting only a subset of devices)
09:00voidah has quit [Ping timeout: 480 seconds]
09:01voidah has joined #asahi-dev
09:04flokliJ773s, with a minimal device tree I get all the way into a a linux initrd, with some m1n1 changes I get the cores initialized, but when not passing cpus=1 i get two 'Unable to handle kernel write to read-only memory at virtual address ffff8000039f8000', and then oops.
09:05asahi has joined #asahi-dev
09:09voidah has quit [Ping timeout: 480 seconds]
09:18voidah has joined #asahi-dev
09:31voidah has quit [Ping timeout: 480 seconds]
09:40voidah has joined #asahi-dev
09:47pb17 has quit [Remote host closed the connection]
09:47pb17 has joined #asahi-dev
09:48voidah has quit [Ping timeout: 480 seconds]
09:54asahi has quit [Quit: asahi]
09:56voidah has joined #asahi-dev
10:00birate17 has joined #asahi-dev
10:15voidah has quit [Ping timeout: 480 seconds]
10:24voidah has joined #asahi-dev
10:32voidah has quit [Ping timeout: 480 seconds]
10:41voidah has joined #asahi-dev
10:50voidah has quit [Ping timeout: 480 seconds]
10:58voidah has joined #asahi-dev
11:01pb17 has quit [Ping timeout: 480 seconds]
11:06pb17 has joined #asahi-dev
11:11voidah has quit [Ping timeout: 480 seconds]
11:12birate17 has quit [Quit: leaving]
11:16birate17 has joined #asahi-dev
11:19voidah has joined #asahi-dev
11:21birate17 has quit []
11:48ScottJones[m] has joined #asahi-dev
11:51ScottJones[m]Did some PMP validation on an M2 Max (MacBook Pro 14", t6021/j414c) running ALARM 6.19.14.asahi2. Enabling APPLE_USE_PMP shows no measurable s2idle suspend effect — 2.64 W (off) vs 2.62 W (on) across two ~8 h continuous-suspend windows, measured at exact suspend boundaries on battery. Consistent with the 7.0 notes describing it as an idle win. Is a null suspend result expected on the Max tier? Happy to measure display-off idle next
11:51ScottJones[m]if that's useful. Full method + numbers: https://gist.github.com/scottjones/c74bd1ac3fca183997c563b57ca7e59d
11:53msimonelli has quit [Read error: Connection reset by peer]
12:02asahi has joined #asahi-dev
12:02asahi has quit []
12:02asahi has joined #asahi-dev
12:18chaos_princesscd into kernel folder, run `make rustavailable`
12:22apalos- is now known as apalos
12:29asahi1 has joined #asahi-dev
12:35asahi has quit [Ping timeout: 480 seconds]
12:35voidah has quit [Ping timeout: 480 seconds]
12:36asahi has joined #asahi-dev
12:42asahi1 has quit [Ping timeout: 480 seconds]
12:42renoo has quit [Ping timeout: 480 seconds]
12:43voidah has joined #asahi-dev
12:44asahi has quit [Quit: asahi]
12:51voidah has quit [Ping timeout: 480 seconds]
12:59voidah has joined #asahi-dev
13:01asahi has joined #asahi-dev
13:08voidah has quit [Ping timeout: 480 seconds]
13:16voidah has joined #asahi-dev
13:24voidah has quit [Ping timeout: 480 seconds]
13:34voidah has joined #asahi-dev
13:42voidah has quit [Ping timeout: 480 seconds]
13:49Calandracas_ has joined #asahi-dev
13:51voidah has joined #asahi-dev
13:55Calandracas has quit [Ping timeout: 480 seconds]
13:59voidah has quit [Ping timeout: 480 seconds]
14:08voidah has joined #asahi-dev
14:16voidah has quit [Ping timeout: 480 seconds]
14:20Yushi_ has joined #asahi-dev
14:22voidah has joined #asahi-dev
14:23Yushi has quit [Ping timeout: 480 seconds]
14:24Yushi_ is now known as Yushi
14:30Yushi_ has joined #asahi-dev
14:30voidah has quit [Ping timeout: 480 seconds]
14:31Yushi_ has quit [Remote host closed the connection]
14:32Yushi has quit [Ping timeout: 480 seconds]
14:32Yushi has joined #asahi-dev
14:38r0ni has joined #asahi-dev
14:38voidah has joined #asahi-dev
14:47voidah has quit [Ping timeout: 480 seconds]
14:55voidah has joined #asahi-dev
15:04voidah has quit [Ping timeout: 480 seconds]
15:09voidah has joined #asahi-dev
15:19picnoir has quit [Ping timeout: 480 seconds]
15:21nela has quit [Ping timeout: 480 seconds]
15:22renoo has joined #asahi-dev
15:25nela has joined #asahi-dev
15:33asahi has quit [Quit: asahi]
15:41chadmed has quit [Quit: Konversation terminated!]
15:41chadmed has joined #asahi-dev
15:43chadmed has quit [Read error: Connection reset by peer]
15:43chadmed has joined #asahi-dev
15:49michaelros4444559 has quit [Read error: Connection reset by peer]
15:49michaelros4444559 has joined #asahi-dev
16:01michaelros4444559 has quit [Ping timeout: 480 seconds]
16:23violette has joined #asahi-dev
16:27picnoir has joined #asahi-dev
16:38Ardu0us_Morning all. I'm running Fedora 44 on kernel 6.19 on an M1 Max. Running 'dnf repoquery' shows 7.0.11 is out there, but not the official Asahi release. Did I miss something? Is Asahi Fedora Remix 44 indeed not yet on kernel 7? Is there a release timeline if so?
16:43Tachyonray[m]i’m on 7.0.11. but i’m not on fedora
16:44Ardu0us_I know I could download and compile it, but would rather be on the official Asahi Fedora Remix release for compatibility and all that.
16:46Tachyonray[m]i’d expect the asahi repo’s to package 7.0.11 as well
16:47Tachyonray[m]or is stable always based on the lts kernel release?
16:57Ardu0us_I'm unsure Tachyonray[m]. Judging by the release cadence found here, I'd guess 7.x is coming relatively soon. https://copr.fedorainfracloud.org/coprs/g/asahi/kernel/builds/
16:58Tachyonray[m]you’ll probably skip over 7.0
17:02Ardu0us_Yeah probably at this point. 7.1 is slated to be released mid to late June, and 7.2 in late August.
17:41voidah has quit [Ping timeout: 480 seconds]
17:49voidah has joined #asahi-dev
17:58voidah has quit [Ping timeout: 480 seconds]
18:06voidah has joined #asahi-dev
18:14voidah has quit [Ping timeout: 480 seconds]
18:18PurpleDrink[m] has joined #asahi-dev
18:23voidah has joined #asahi-dev
18:31voidah has quit [Ping timeout: 480 seconds]
18:40voidah has joined #asahi-dev
18:48voidah has quit [Ping timeout: 480 seconds]
18:57voidah has joined #asahi-dev
19:05voidah has quit [Ping timeout: 480 seconds]
19:08voidah has joined #asahi-dev
19:17voidah has quit [Ping timeout: 480 seconds]
19:24voidah has joined #asahi-dev
19:30catred has joined #asahi-dev
19:33catred has quit []
19:45StanfordAppliedCyber[m]flokli: just update to 26.5 on the neo
19:46StanfordAppliedCyber[m]for the m4, well, probably the same tbh because i'm the first one to look at it and i'm using 26.5 --> fair chance the version we use is 26.5
19:50StanfordAppliedCyber[m]sven: loses register state last i checked but i never checked on 26.5
19:50StanfordAppliedCyber[m]sven: let me check that now
19:51StanfordAppliedCyber[m]i know it was not accessible on 26.4.1 but i actually never checked 26.5 because the code i wrote for 26.4.1 just kept working on 26.5
19:51StanfordAppliedCyber[m]ack, i'll check both sometime today and report back on the neo
19:52StanfordAppliedCyber[m]busy rn so cant check immediately
19:53svenwould just be good to file that feedback report thing soon because getting that fixed is probably gonna take a long while again
19:54StanfordAppliedCyber[m]ACK, is the wfi loses register state thing a blocker for specifically asahi linux? ie there's an easy hack, save all registers, restore all registers
19:55svenand since we can’t easily update firmware we don’t want that as a downstream only hack either
19:56StanfordAppliedCyber[m]fair, somehow i blanked on the whole "INSANE FIRMWARE ABI" thing
19:56StanfordAppliedCyber[m]insane, unstable, firmware abi :)
20:01svenand even if that abi was stable we can’t update firmware (or specifically iboot where they have to fix it) from linux. that might even need a trip to 1TR
20:01StanfordAppliedCyber[m]presumably userspace, especially for the gpu drivers, is very stable however right? ie, the actual shader isa and stuff won't change
20:02chaos_princessisa changes roughly every other chip generation
20:02chaos_princessso, m1, m3, m5
20:02StanfordAppliedCyber[m]yeah that's my current understanding, thanks!
20:02chaos_princesswhen using gpus, you don't ship compiled code, instead use some kind of IR. there is an undocumented something called AIR that some macos games ship
20:03StanfordAppliedCyber[m]for a bit of context on me my goal is to upstream the hypervisor, get the machine to a daily driver usable state without the GPU and DCP, then try to add the GPU, then likely head to another project that is not linux related
20:03StanfordAppliedCyber[m]presumably that's the metal IR that gets compiled to the actual shader isa once we know exactly what platform it's running on?
20:04StanfordAppliedCyber[m]i never said i'd upstream anything but the hypervisor
20:06StanfordAppliedCyber[m]we'll see, maybe i'm simply hopelessly naive
20:56hardy94 has joined #asahi-dev
20:57hardy94 has quit [Remote host closed the connection]
21:21flokliStanfordAppliedCyber[m]: this is a boot which oopses on a secondary cpu as it's loosing state presumably: https://paste.linuxlounge.net/OE
21:22StanfordAppliedCyber[m]what firmware version? 26.5?
21:29StanfordAppliedCyber[m]unfortunate
21:29StanfordAppliedCyber[m]whenever i'm back to my mac i'll see if it loses register state
21:35voidah has quit [Ping timeout: 480 seconds]
21:44voidah has joined #asahi-dev
21:52voidah has quit [Ping timeout: 480 seconds]
21:53renoo has quit [Ping timeout: 480 seconds]
21:55amarioguy has quit [Ping timeout: 480 seconds]
22:02voidah has joined #asahi-dev
22:08jsk_ has joined #asahi-dev
22:11jsk has quit [Ping timeout: 480 seconds]
22:12jsk_ is now known as jsk
22:45voidah has quit [Ping timeout: 480 seconds]
22:47revadam has joined #asahi-dev
22:47revadam has quit []
22:49voidah has joined #asahi-dev
23:43voidah has quit [Ping timeout: 480 seconds]
23:51voidah has joined #asahi-dev