#asahi-dev · 2025-03-10 18:48
alyssa:p#asahi-dev · 2025-03-10 18:38
jannauquite please that apple has chosen my initials for that#asahi-dev · 2025-03-10 18:37
jannaualyssa: the single macos kernel cache for pro/max/ultra contains "mac13j" vs "mac13g"#asahi-dev · 2025-03-10 13:29
alyssaidk what J is#asahi-dev · 2025-03-10 13:28
alyssanicolas17: S/C/D is definitely pro/max/ultra#asahi-dev · 2025-03-10 08:23
sven*fixes#asahi-dev · 2025-03-10 08:23
sven(same applies to everything else: I’ll start picking things that aren’t fixed up after the merge window again)#asahi-dev · 2025-03-10 08:22
svennickchan: as mentioned, I’ll probably pick the cache series up after -rc1. would be nice to get a review before that #asahi-dev · 2025-03-10 07:47
jannaunicolas17: I think H13J is for for t600x and s/c/d are for t6000/t6001/t6002 so both are not wrong#asahi-dev · 2025-03-10 00:15
nicolas17chadmed: I'm not any more confident about the J/C/D codes on theapplewiki though#asahi-dev · 2025-03-10 00:12
chadmedfeel free to raise PRs for whatever you want to archive/document#asahi-dev · 2025-03-10 00:12
chadmednicolas17: probably just hasnt been edited since we figured out what J/C/D are#asahi-dev · 2025-03-09 23:55
nicolas17for example M1 Pro/Max/Ultra are all H13J in asahi's docs but H13S/H13C/H13D in theapplewiki, are those codes used for different purposes by Apple, or is one of these lists just incorrect?#asahi-dev · 2025-03-09 23:55
nicolas17what could be the cause of the discrepancy of "internal names" here? <https://theapplewiki.com/wiki/Codenames#SoCs> <https://asahilinux.org/docs/hw/soc/soc-codenames/>#asahi-dev · 2025-03-09 19:43
sven-rc3 isn't enough, i'll send something for the fixes branch#asahi-dev · 2025-03-09 11:52
svenok, i'll check this evening if -rc3 helps#asahi-dev · 2025-03-09 11:39
arndsven: my tree is based on -rc3, so you can send a patch based on that if that helps, or I can merge it into the fixes branch#asahi-dev · 2025-03-09 11:38
svenarnd: there's one more maintainer update to add neal as reviewer (https://lore.kernel.org/asahi/20250303154012.1417088-1-neal@gompa.dev/) left which (trivially) conflicts with -rc1, what's the easiest way to send that to you? v2 to soc@ with the acks from alyssa and me?#asahi-dev · 2025-03-09 10:55
fl0_idand then just didn't start#asahi-dev · 2025-03-09 10:55
fl0_id(like it complained about the os not being configured with an allowed user, despite having use the official installer etc)#asahi-dev · 2025-03-09 10:54
fl0_id(hiccups probably because I restarted too late I assume)#asahi-dev · 2025-03-09 10:53
fl0_idyeah that's what I wanted to do at first, but somehow the installer had the hiccups. but if you think that's best I can do that for sure#asahi-dev · 2025-03-09 10:52
chaos_princessjust install a second copy of macos and use that to install m1n1#asahi-dev · 2025-03-09 10:52
fl0_idchaos_princess I'm trying to use the installer to get just enough m1n1 to dump adt. at first I thought i would be enough to just modify it and run it like that (and gave it installe-data.json) but seems it like to be fully assembled and uses a different rust toolchain when building it.#asahi-dev · 2025-03-09 10:46
chaos_princessare you trying to set up hypervisor?#asahi-dev · 2025-03-09 10:45
chaos_princesshttps://github.com/AsahiLinux/asahi-scripts/blob/main/update-m1n1#L55#asahi-dev · 2025-03-09 10:45
fl0_idthx. that helps :)#asahi-dev · 2025-03-09 10:44
chaos_princessstage2? you basically just cat m1n1.bin, all dtbs, and gzipped u-boot#asahi-dev · 2025-03-09 10:40
fl0_idthx. do you by chance also know how the stub payload is generated? (like m1n1 + efi)#asahi-dev · 2025-03-09 10:32
chaos_princessipsws can be downloaded from apple and they generally do not delete them https://ipsw.me/Mac15,12#asahi-dev · 2025-03-09 10:19
fl0_idfor experimenting to get the adt I'm using the modified installer. One last hiccup probably - does someone have a link to an ipsw that's compatible with m3? I know someone recently posted a link to their ipsw archive but I think that was without macs#asahi-dev · 2025-03-09 02:13
ece314378925Got it, thanks!#asahi-dev · 2025-03-09 02:09
chadmedece314378925: asahi-wip is closest to release #asahi-dev · 2025-03-09 01:52
ece314378925What branch does Asahi systems run? I'm wanting to poke through code but there are more than 100 branches, and I'm not sure which to use #asahi-dev · 2025-03-08 22:50
fl0_idwould it help to just use diskutil cli to make things look in the target container exactly as described in the docs? (if they are not already)#asahi-dev · 2025-03-08 22:49
fl0_id second macos install but then abandoning that.#asahi-dev · 2025-03-08 22:49
fl0_idpotentially dumb question - if there is a pending update (supposedly) on one container, should it effect another? Like I am getting the warning with a lot of overhead space, but I literally just deleted this volume ... and in diskutil command line, it also only show Preboot, Recovery, VM. Main macos disk however shows apfs snapshot for com.apple.os-update something. (which might be from real update that I skipped or from first planning to install a#asahi-dev · 2025-03-08 22:47
fl0_idok so finally back up is done#asahi-dev · 2025-03-08 19:09
cy8aerthough I don't know why it overdrives harder with a different kernel without any changes in the audio stack 😕#asahi-dev · 2025-03-08 19:01
cy8aerSorry for my panic#asahi-dev · 2025-03-08 19:01
cy8aerI have found the cause: EasyEffects. It is running in background (but with no effects on the speakers). And it overdrives more with 6.13.5-x. I disabled it now and the sound is perfect#asahi-dev · 2025-03-08 15:08
cy8aerOk (should be expected): asahi-6.13.5-4 is still crackling in seconds.#asahi-dev · 2025-03-08 14:44
cy8aereffort#asahi-dev · 2025-03-08 14:44
cy8aerthanks for your efford#asahi-dev · 2025-03-08 10:22
LarstiQcy8aer: I'll try a 6.13 kernel if I have a free block of time#asahi-dev · 2025-03-08 09:02
cy8aer(would have of course)#asahi-dev · 2025-03-08 09:01
cy8aerOk, call me a paranoiac - but now I hear the crackle with 6.12 too but extremely rare. The way LarstiQ describes it. But now it would be interesting what experiences LarstiQ has with 6.13...#asahi-dev · 2025-03-08 06:53
LarstiQit's hard to reproduce because it doesn't happen in the same spot all the time and can take an hour before it happens#asahi-dev · 2025-03-08 06:52
LarstiQcy8aer: I get a crackle like that too on `6.12.4-asahi` on my j314#asahi-dev · 2025-03-07 23:29
cy8aerBut because of the time I will be afk soon.