#
#asahi-dev · 2026-01-17 09:47
noopwafelso none of this helps and also I hit exactly the same failure 10 times in a row
#asahi-dev · 2026-01-17 09:23
svenyup :D
#asahi-dev · 2026-01-17 09:22
noopwafeloh this is a genius idea
#asahi-dev · 2026-01-17 09:22
svenlol
#asahi-dev · 2026-01-17 09:22
nickchanin regards to speculation there's always the giga hack fix which is to enable TSO
#asahi-dev · 2026-01-17 09:22
noopwafelmy hope is that continuing down the path of 'working out what everything in the proxy code is actually meant to do' will help.. but probably good to push changes first
#asahi-dev · 2026-01-17 09:20
noopwafelnickchan: good news, reverting does not fix. I'm not sure it's locking, the boot failures are not _that_ random, although maybe this is just wishful thinking :)
#asahi-dev · 2026-01-17 09:14
jannaunoopwafel: I think nvme should work with 14.x. the breaking isssue is 15.x
#asahi-dev · 2026-01-17 09:13
noopwafelah cool. I just want to boot to somewhere I can make friends with gpu, so that sounds super hopeful..
#asahi-dev · 2026-01-17 09:11
svennvme probably just needs someone with the hv to run run_guest.py with -m trace_nvme.py (maybe set verbose=3 in there) and see what changed
#asahi-dev · 2026-01-17 09:10
svennoopwafel: afaik there are issues with nvme, integralpilot has managed to boot a linux kernel to userspace but other people ran into issues so far
#asahi-dev · 2026-01-17 09:05
nickchaneven though i think the logic there is sound
#asahi-dev · 2026-01-17 09:03
nickchantry reverting the lock changes in src/utils.c
#asahi-dev · 2026-01-17 09:03
nickchanhttps://github.com/AsahiLinux/m1n1/commit/869d2ae35c31e14935a63492070699aa359df717#diff-3e04e056edbdc0f772b0ffd1c93cef1187209f37276d40d2a281d9b989398a73L14
#asahi-dev · 2026-01-17 09:03
nickchanas much as i don't like to say this but
#asahi-dev · 2026-01-17 09:01
noopwafelwhat is the status on the linux side? I have not tried booting a kernel yet. nvme?
#asahi-dev · 2026-01-17 08:59
svenit’s gonna suck if this some long standing locking or whatever issue that we only hit now because m3 speculates even harder than m1/2 or something equally cursed 🙈
#asahi-dev · 2026-01-17 08:55
nickchanneeds the bigger chips obviously
#asahi-dev · 2026-01-17 08:55
nickchanmaybe check if it works with 1 core per cluster
#asahi-dev · 2026-01-17 08:54
noopwafelintegralpilot: this is all on top of your notes (for the bringup) of course, thank you a lot for writing/sharing..
#asahi-dev · 2026-01-17 08:52
integralpilotthank you!
#asahi-dev · 2026-01-17 08:52
svennice, will take another look either this afternoon or tomorrow probably
#asahi-dev · 2026-01-17 08:51
integralpilothttps://github.com/IntegralPilot/linux/pull/1
#asahi-dev · 2026-01-17 08:51
integralpilotjust pushed new MTP/dockchanel stuff after applying sven's feedback and making some changes. thanks again for making the branch jannau, i think the PR UI is much easier for this!
#asahi-dev · 2026-01-17 08:45
svenso you’re booting with two cores and that works but any more and it’s unstable again? Weird
#asahi-dev · 2026-01-17 08:09
LarstiQnoopwafel, Shiz: very nice work!
#asahi-dev · 2026-01-17 05:36
chadmedyo dawg i heard you like unstable interfaces so we put an unstable interface inside your unstable interface
#asahi-dev · 2026-01-17 05:35
JamesCalligeros[m]They do like moving stupid crap around for some reason, like epic endpoints for dcp methods
#asahi-dev · 2026-01-17 05:35
JamesCalligeros[m]Yeah, the core stuff doesnt really change much architecturally
#asahi-dev · 2026-01-17 05:34
NickChan[m]So a bunch of things changed
#asahi-dev · 2026-01-17 05:34
NickChan[m]But mac is the moment they have to make big chips
#asahi-dev · 2026-01-17 05:34
NickChan[m]the things mostly don't change assumption is still true
#asahi-dev · 2026-01-17 05:33
JamesCalligeros[m]So yes, some incorrect assumptions were made early on
#asahi-dev · 2026-01-17 05:33
JamesCalligeros[m]Yeah like lmfao in the faq under “wont apple just change everything?” the counter example i gave was AIC, which they immediately changed and then changed again
#asahi-dev · 2026-01-17 05:20
Shiz(no shade of course, you can never foresee the entire future)
#asahi-dev · 2026-01-17 05:19
Shizdirectly or indirectly
#asahi-dev · 2026-01-17 05:19
Shizat least half of it seems to come down to "whoops the m3 has a very different memory/mmio map and maybe m1n1 was making a few assumptions related to how m1/m2 were mapping"
#asahi-dev · 2026-01-17 05:19
integralpilot:D
#asahi-dev · 2026-01-17 05:16
Shizmessy but at least a good base for further research :D
#asahi-dev · 2026-01-17 05:16
Shizit seems `self.add_tracer(zone, "CPU_START", TraceMode.RESERVED)` is also messed up, needs to be commented-out
#asahi-dev · 2026-01-17 05:16
integralpilotoh interesting, great work on finding all those! :)
#asahi-dev · 2026-01-17 05:16
Shizomitting any of those seems to make it return to unstable boot, so there's def still work to be done :p (mostly the last one)
#asahi-dev · 2026-01-17 05:16
Shiz3) booting with only one P-core and only one E-core enabled
#asahi-dev · 2026-01-17 05:15
Shiz2) adding some MSRs and marking some more memory as reserved using the memory-map ADT node
#asahi-dev · 2026-01-17 05:15
Shiz1) the PMGR power-gating hacks were definitely poking addresses they shouldn't be (and entirely differently mapped on M3+)
#asahi-dev · 2026-01-17 05:14
ShizI think it was a combination of three things:
#asahi-dev · 2026-01-17 05:12
integralpilothow'd you solve the memory corruption, i was quite confused & stuck about it. was it something with limiting to just one core, i thought i remember something about secondary CPU startup being correlated but not sure.
#asahi-dev · 2026-01-17 05:12
Shizmuch thanks to your earlier efforts too :)
#asahi-dev · 2026-01-17 05:12
integralpilotShiz: omg yay that's so exicting, great work!
#asahi-dev · 2026-01-17 05:11
integralpilotfl0_id: given you had config issues before, can you confirm that CONFIG_APPLE_AIC is set to y in your .config?

plus ›