#
#asahi-dev · 2026-06-02 19:18
Psil0Cybin[m]plus you MAY by accident remove the Mac bootloader which is cool as long as you do not plan to go back to Macintosh
#asahi-dev · 2026-06-02 19:18
Psil0Cybin[m]VMS you can take with on extrnal hard drive and run anywhere without carrying the laptop
#asahi-dev · 2026-06-02 19:17
Psil0Cybin[m]like u want ur mac into a linux box, i would start with a mac on VM, very little ---> security issues unless you are pushing your security chances to the limit
#asahi-dev · 2026-06-02 19:17
Psil0Cybin[m]io did this and than switched back to mac, and was missing keyboard functions like lights and sound
#asahi-dev · 2026-06-02 19:17
Psil0Cybin[m]oh princess oh princess, you are using this for Mac? Why no virtual machine?
#asahi-dev · 2026-06-02 19:06
jannaushould be /usr/share/alsa/ucm2/conf.d/macaudio
#asahi-dev · 2026-06-02 19:06
jannau`equery f alsa-ucm-conf-asahi`
#asahi-dev · 2026-06-02 18:59
chaos_princessshortly after login. where does said ucm profile live?
#asahi-dev · 2026-06-02 18:57
jannauwhen does this happen? on use? Message sounds familar. Did you adjust the ucm to cover M3 devices as well? "or UCM profile" might be true
#asahi-dev · 2026-06-02 18:50
chaos_princesshttps://github.com/WhatAmISupposedToPutHere/linux/commit/e101a747a83ae1356509852f37adeb15af6b7685
#asahi-dev · 2026-06-02 18:50
chaos_princesstrying to get audio output to work, getting this error in dmesg "Secondary: ASoC: no backend DAIs enabled for Secondary, possibly missing ALSA mixer-based routing or UCM profile" and no audio output. (input seems to be working, the volume meters do bounce.) Any ideas on what i might be doing wrong?
#asahi-dev · 2026-06-02 18:02
svenit'll try but the hw will refuse
#asahi-dev · 2026-06-02 18:02
svenit just won't enter that p-state
#asahi-dev · 2026-06-02 17:13
yukaI guess it's a _target_ p-state
#asahi-dev · 2026-06-02 17:11
yukaI heard about those p-states which can only be reached if some other cores are in deep wfi. Does Linux somehow know about this for scheduling, or will it still attempt to use the highest p-state even in an all-core workload, and what will happen then?
#asahi-dev · 2026-06-02 17:00
jannaudidn't dump_pmgr output it on m1/m2?
#asahi-dev · 2026-06-02 16:55
chaos_princessdoes anyone know where the frequency for nco_clkref comes from?
#asahi-dev · 2026-06-02 16:54
chaos_princessand send all other secondaries into wfi
#asahi-dev · 2026-06-02 16:53
chaos_princesswould make sense to do that
#asahi-dev · 2026-06-02 16:53
yukaso I should measure the e-core cluster from p-core, and the p-core cluster from e-core
#asahi-dev · 2026-06-02 16:53
yukaHmm, right
#asahi-dev · 2026-06-02 16:53
chaos_princessin wfi
#asahi-dev · 2026-06-02 16:53
yukathe other cores shut down completely?
#asahi-dev · 2026-06-02 16:53
chaos_princessmeasure from ecore
#asahi-dev · 2026-06-02 16:52
yukathe only core how?
#asahi-dev · 2026-06-02 16:52
chaos_princess(per cluster)
#asahi-dev · 2026-06-02 16:52
chaos_princessi wonder if they will behave saner if that is the only core
#asahi-dev · 2026-06-02 16:51
chaos_princessoh, not getting the 20 is my fault, i noticed them going down and assumed that is the end of the table
#asahi-dev · 2026-06-02 16:51
yukaodd indeed that the frequency goes down again
#asahi-dev · 2026-06-02 16:50
yukajannau: no, the e-core pstates match with powermetrics output
#asahi-dev · 2026-06-02 16:48
yukahttps://yuyu.yuka.dev/public/t6034-powermetrics.txt
#asahi-dev · 2026-06-02 16:47
jannau20 probably needs the other cpu cores in idle but 17 and 18 look wrong
#asahi-dev · 2026-06-02 16:46
jannau... 15:3624MHz 16:3708MHz 17:3705MHz 18:3704MHz 19:3960MHz 20:3959MHz
#asahi-dev · 2026-06-02 16:46
jannauthe 20 p-states on everest behave a little strange in the upper range:
#asahi-dev · 2026-06-02 16:45
jannauare you missing e-core pstates? t6030 has 8 up to 2748 MHz
#asahi-dev · 2026-06-02 16:43
yukaThen it is already in the right place
#asahi-dev · 2026-06-02 16:42
yukathe header says t0631-base is for t603[124] but not t6030
#asahi-dev · 2026-06-02 16:42
yukaAh no
#asahi-dev · 2026-06-02 16:41
yukaSo this table needs to go in t6031.dtsi instead of t6031-base.dtsi, correct?
#asahi-dev · 2026-06-02 16:40
yukachaos_princess measured similar things on t6031 using cpu_pstate_latencies.py
#asahi-dev · 2026-06-02 16:39
yukaT6034 powermetrics match my table (except of higher p-states missing in my table)
#asahi-dev · 2026-06-02 16:30
jannauyeah: "current CPU frequency: 10.44 GHz"!
#asahi-dev · 2026-06-02 16:22
jannauI want "opp-mhz", annoyinmg to keep track of 6 trailing zeros
#asahi-dev · 2026-06-02 16:18
jannaudoes the t6031 table matches powermetrics? both t8122 and t6030 are different then. both have 700 - 800 MHz p-states for everest and sawtooth (I guess the non working op_01 p-state)
#asahi-dev · 2026-06-02 16:15
yukaCrazy that this thing can go even faster, it already feels super fast
#asahi-dev · 2026-06-02 16:14
yukaAhh okay then I need to re-do the table
#asahi-dev · 2026-06-02 16:01
jannau20 distinct p-states according to powermetrics
#asahi-dev · 2026-06-02 16:00
jannauno, even base M3 has 4056 MHz as highest p-state
#asahi-dev · 2026-06-02 15:57
yuka(maybe on purpose, so that I focus on the other things I should be doing ;))
#asahi-dev · 2026-06-02 15:57
yukadon't have a second device or central scrutinizer with me rn

plus ›