#asahi-dev · 2026-02-21 21:10
fl0_iddo you have the right port? is your cable the right one?#asahi-dev · 2026-02-21 20:43
fl0_id(my changes are not online anywhere yet)#asahi-dev · 2026-02-21 20:43
fl0_idbtw, i modified https://github.com/Dil4rd/dpp/tree/main/apfs (MIT) to work with no_std + alloc. maybe interesting for m1n1. seems to work, but needs more testing. reading only so far and muti volume support is just added#asahi-dev · 2026-02-21 12:40
fl0_id:)#asahi-dev · 2026-02-21 12:36
fl0_idor that, but that's not as fun#asahi-dev · 2026-02-21 12:34
fl0_idnow I imagine one engineer having the sole job of testing different monitors for quirks#asahi-dev · 2026-02-20 22:14
fl0_idsiirko[m] it is not using. the DT. but afaik the memory layout gets output during m1n1 boot log#asahi-dev · 2026-02-20 22:12
fl0_id(afaik)#asahi-dev · 2026-02-20 22:11
fl0_idsiirko[m] you maybe can get the right values from DT or m1n1 boot log#asahi-dev · 2026-02-20 22:11
fl0_idabrender that seems surprisingly civil and constructive #asahi-dev · 2026-02-20 21:25
fl0_idno I'm not, but if you read about it being added, then it was added to that upstream, not asahi#asahi-dev · 2026-02-20 21:22
fl0_idso upstream "official" linux now also has cpuidle for apple silicon#asahi-dev · 2026-02-20 21:21
fl0_idand it is slowly changing#asahi-dev · 2026-02-20 15:04
fl0_idin some cases for specific devices, if the older compatible still works, it would still work. but if it only checks the machine, yes. you could just try adding t8122#asahi-dev · 2026-02-20 13:55
fl0_idmaybe someone else can weigh in, haven't used uboot much. so it hangs after loading kernel, but before you can give it commands?#asahi-dev · 2026-02-20 13:35
fl0_idah. yeah not sure about u-boot. did you install that manually or via (modified) installer?#asahi-dev · 2026-02-20 13:29
fl0_idsiirko[m] what do you mean by other way round?#asahi-dev · 2026-02-18 17:32
fl0_idyeah that's the most tested I think#asahi-dev · 2026-02-18 17:17
fl0_idthere is no complete guide though on getting a full system. the feasability of that depends not only on your skill and frustration tolerance, but also on which m3 you have.#asahi-dev · 2026-02-18 17:16
fl0_idyou should be able to follow the m1n1 user guide, yes. for experimenting, you will also need a second machine to control m1n1, a good usb c cable and remember to connect the usb-c cable before starting the mac#asahi-dev · 2026-02-18 17:15
fl0_idsiirko[m] you don't really need that gist, that is only for running macos in the hypervisor#asahi-dev · 2026-02-15 00:20
fl0_idand just wanted to know if it's possible to tell programmatically#asahi-dev · 2026-02-15 00:18
fl0_idi just did that as an extra check when lookig at the format. I'm not saying it should be like that in the final asahi installer with fixed urls#asahi-dev · 2026-02-15 00:15
fl0_idnicolas17 the urls are from https://theapplewiki.com/wiki/OTA_Updates/Mac/14.8.3#asahi-dev · 2026-02-14 20:42
fl0_idbtw, I wrote a hacky script to check if an OTA is a full update or delta, and to extract from full OTA. Looks correct but haven't tested any of those files yet. If you think this could be part of the installer, I can have a look how to integrate it. (it uses the existing code that is already there)#asahi-dev · 2026-02-14 16:37
fl0_idthx#asahi-dev · 2026-02-14 16:13
fl0_idfirmware files should be able to be loaded from initramfs, right? or do I need to get nvme working before loading them?#asahi-dev · 2026-02-13 21:30
fl0_idchaos_princess there. is something in installer to check OTA. but not sure how functional#asahi-dev · 2026-02-13 21:12
fl0_id(only found 14.6.1 ipsw for extracting with the installler...)#asahi-dev · 2026-02-13 21:12
fl0_idintegralpilot thx. where did you get the ipsw from? can I extract it from a running system?#asahi-dev · 2026-02-13 13:12
fl0_idintegralpilot for t8122, did you use firmware files from 14.8.3 or 14.6?#asahi-dev · 2026-02-12 15:26
fl0_idok#asahi-dev · 2026-02-12 15:26
fl0_id(cannot check logs right now)#asahi-dev · 2026-02-12 15:25
fl0_idchaos_princess I meant linux is booting, I saw some messages re rtkit but didn't manually start anything, also b/c keyboard is not working. I assumed if it's detected it would just work (tm)#asahi-dev · 2026-02-12 15:17
fl0_idchaos_princess I think I turned on all the pmgr bits. I didn't know that mtp needs firmware, so will check that#asahi-dev · 2026-02-12 15:11
fl0_iddoes someone know what apart from aic has to be working for mtp / dockchannel to work for hid etc? it is booting but keyboard doesn't work yet and not sure why. (made a bit hard by somehow HV being broken the last few boots)#asahi-dev · 2026-02-11 15:48
fl0_idif you inject stuff there, I assume the idea is that you then can trace from there#asahi-dev · 2026-02-11 15:47
fl0_idvmapple is a special xnu kernel for virtualized macos on macos. it runs in a different mode#asahi-dev · 2026-02-11 14:05
fl0_idnoopwafel oh, all the best, get well soon!#asahi-dev · 2026-02-09 08:10
fl0_idat least one could prob also be called pmgr_gpu#asahi-dev · 2026-02-09 08:03
fl0_idbtw, for pmgr, how should these be named? on m3 max I see 4 pmgrs. though at least one gave my a sync error so far. On t602x multidie they are name north/south/east, should I just go with that?#asahi-dev · 2026-02-05 15:05
fl0_idkloenk sure :)#asahi-dev · 2026-02-05 14:23
fl0_idkloenk you might be able to klick edit in github, and then it forks for you automatically. but not sure if that's better for you...#asahi-dev · 2026-02-05 14:12
fl0_idkloenk for the asahi / asahi-wip tree you can use github, there is no ML. For the upstream tree, it goes throuhg the relevant MLs like normal. You can also first wait for feedback here or on a WIP PR on gh#asahi-dev · 2026-02-03 15:07
fl0_idalso good to know it's not just me...#asahi-dev · 2026-02-03 15:07
fl0_idmildsunrise yeah same...#asahi-dev · 2026-02-03 14:51
fl0_idmildsunrise did you have any insight into why cpufreq is not working?#asahi-dev · 2026-02-03 12:20
fl0_idjannau ok no hurry#asahi-dev · 2026-02-03 12:16
fl0_idhttps://github.com/step21/linux-asahi/commit/67e5cec167f41c6a07a635f9bc6a0ee5fe6c9f74#asahi-dev · 2026-02-03 12:16
fl0_idjannau is it possible that some of the items here for m2 and m3 are wrong? specifically m3 max is listed apple j414c, which is incorrect. (it's j514)