#asahi-dev · 2026-03-02 00:11
abrenderyuka: Thanks for that PR! I've left 2 comments on it based on my testing#asahi-dev · 2026-03-01 22:48
abrendernnym_ - yep, I was able to make it work by ignoring cpu.cluster_type == "P" - I'm looking into the exception causing that (unless you or someone else already knows why the performance core are unhappy)#asahi-dev · 2026-03-01 21:01
abrenderand 'Sawtooth' in those columns?#asahi-dev · 2026-03-01 21:01
abrenderThe "cpus" section of the ADT on j713 M4, t8132 shows me this: https://gist.github.com/abrender/0eba6c67bb10cf19c56ac47534791dbf . I notice that the E cores have "compatible= [ .. sawtooth ..]" and P cores have "compatible = [ ..everest .. ]". Is that enough verification for me to send a PR to update the P-Core and E-Core columns at https://asahilinux.org/docs/hw/soc/soc-codenames/ with 'Everest' #asahi-dev · 2026-03-01 18:44
abrenderIt's got 26.3 on one MacOS install, and 26.0.1 on another MacOS install. When I try to chainload anything in m1n1 (even the same m1n1 raw binary that boots) it crashes (checking on that)#asahi-dev · 2026-03-01 18:40
abrenderIn case it's useful for anyone, I have a J713 - Macbook Air 13 inch M4 - I don't care about anything on it, it doesn't bother me if I have to wipe or dfu it. I've got it booted into m1n1. If anyone needs anything run on it or from it, please feel free to ask#asahi-dev · 2026-02-20 21:37
abrenderFor anyone interested in the context of the past discussions: https://lore.kernel.org/lkml/5f741a4f-f37d-079b-d464-59045ebef1ce@marcan.st/t/#u#asahi-dev · 2026-02-20 21:26
abrenderRight, drama about architecture-specfic drivers #asahi-dev · 2026-02-20 21:25
abrenderfl0_id - are you sure? I don't see apple silicon here: https://github.com/torvalds/linux/tree/master/drivers/cpuidle - maybe it's somewhere else?#asahi-dev · 2026-02-20 21:23
abrenderThanks for pointing out that the commit I linked to was a rebase. I should have looked closer.#asahi-dev · 2026-02-20 21:22
abrenderI said "yeah" because I thought you were referring to the official kernel released by Asahi rather than me custom compiling a kernel from a branch in the repo. Thank you very much for clarifying#asahi-dev · 2026-02-20 21:22
abrenderokay, gotcha. thanks.#asahi-dev · 2026-02-20 21:21
abrenderI thought it was impossible to run linux on Apple Silicon using the upstream linus kernel without all of the asahi patches? #asahi-dev · 2026-02-20 21:19
abrender@chaos_princess: can you help me to understand what you mean by upstream kernel? Sorry for the ignorance - just trying to learn the lingo#asahi-dev · 2026-02-20 21:14
abrenderIt looked to me like cpuidle wasn't added until Dec 2025: https://github.com/AsahiLinux/linux/commit/4c135ef5c4c15479593b86a6da1b7abf87ffa6e7#asahi-dev · 2026-02-20 21:14
abrenderoh sorry then maybe I misunderstood by upstream? It's just regular Asahi Fedora and I ran the `dnf upgrade` command#asahi-dev · 2026-02-20 21:13
abrenderYeah - 6.18.10-402.asahi.fc42.aarch64#asahi-dev · 2026-02-20 21:13
abrender(I basically put the laptop into suspend, then closed the lid, and opened it a few hours later and checked the loss of battery %)#asahi-dev · 2026-02-20 21:12
abrenderQuick data point: M2 Macbook Air 14 inch (J413) - in January I tested and it lost 1.5% battery per hour on suspend. Now that the cpuidle driver was added in 6.18 I measured a 33% reduction in battery use - 1% per hour instead. I notice there was no mention of cpuidle in the progress reports - maybe it slipped through, or maybe it wasn't expected to make any difference?#asahi-dev · 2026-02-19 03:24
abrendergreat, thanks @JamesCalligeros!#asahi-dev · 2026-02-19 03:16
abrenderI'm wondering if that's problematic, or if "the platforms" here refers to the OS, not the hardware and so it's okay to use x18 because it's Linux and not MacOS? To be clear, I haven't observed any issues, I'm just looking and trying to understand the code :) Thanks!#asahi-dev · 2026-02-19 03:15
abrender(https://developer.apple.com/documentation/xcode/writing-arm64-code-for-apple-platforms#Respect-the-purpose-of-specific-CPU-registers).#asahi-dev · 2026-02-19 03:15
abrenderI'm looking at the cpuidle-apple driver and I notice that it is storing/restoring x18 (https://github.com/AsahiLinux/linux/blob/79a307df1e18f144610742ac9ee60080c3983875/drivers/cpuidle/cpuidle-apple.c#L31). I also notice that apple "The platforms reserve register x18. Don't use this register." #asahi-dev · 2026-02-09 05:27
abrenderYeah, that seems problematic :/ I'll try with ipsw file and dfu#asahi-dev · 2026-02-09 05:20
abrenderAh good to know, thank you oliver!#asahi-dev · 2026-02-09 04:50
abrenderTarget is Mac14,2 J413#asahi-dev · 2026-02-09 04:48
abrenderI saw a comment from marcan saying that there are specfic target versions - and 13.5 was the target version 2 years ago. I'm not sure what the current target version is - or if that's still a thing? https://www.reddit.com/r/AsahiLinux/comments/18lbdco/comment/kdzsfyy/#asahi-dev · 2026-02-09 04:47
abrenderLink to output from run_guests.py: https://gist.github.com/abrender/52d7e042f9feac189824d4e132f93e3c#asahi-dev · 2026-02-09 04:47
abrenderelse. The docs say that I can use `picocom -b 115200 /dev/m1n1-sec` but I don't see any serial output from MacOS. I've tried using the stock kernel and KDK. I also saw drama around AppleSerialShim and tried a version that excluded that too - no luck :/ Does anyone have any thoughts on why I can't see the macos serial output on /dev/m1n1-sec ? Thanks!#asahi-dev · 2026-02-09 04:47
abrenderHi All - I'm following the instructions here to boot MacOS (25C56 aka MacOS 26.2 Tahoe) on the m1n1 hypervisor. My host machine is an Ubuntu box. I see both /dev/m1n1 and /dev/m1n1-sec. I am able to enter proxy mode and play around. However, when I try to use `run_guest.py` to boot MacOS it goes through all the steps to start the HV, I see the rainbow Apple logo on the target device, but nothing #asahi-dev · 2026-01-11 21:03
abrenderokay, thanks @svenpeters and @chaos_princess. So it sounds like if I were to dig further into all of the above I wouldn't be stepping on anyones toes? You're not aware of anyone that would come back to me saying "oh, we already have it working and are just productionizing it, you've just wasted your time", right? :)#asahi-dev · 2026-01-11 20:11
abrenderHi Folks - I am considering spending time working to improve the power management during sleep on my M2 Macbook Air. Before I start down that rabbit hole, I was wondering if there is anyone who has already started to tackle that, so that i don't step on their toes? Thanks in advance!