#asahi · 2025-03-25 23:16
evil_king_8791[ 1.355948] apple_aop 2a6c00000.aop: RTKit: syslog message: P_os_log_support.cpp:60: AOP os log initialized#asahi · 2025-03-25 23:16
evil_king_8791[ 1.355649] apple_aop 2a6c00000.aop: RTKit: syslog message: AOP_oslog_init.cpp:96: Start AOP OSLog init#asahi · 2025-03-25 23:16
evil_king_8791[ 1.353608] apple_aop 2a6c00000.aop: RTKit: Initializing (protocol version 12)#asahi · 2025-03-25 23:16
evil_king_8791[ 1.347747] apple_aop 2a6c00000.aop: AOP probe() target: 0 align: 64#asahi · 2025-03-25 23:16
evil_king_8791[ 1.345158] apple_aop 2a6c00000.aop: AOP probe() data#asahi · 2025-03-25 23:16
evil_king_8791jannau: module loaded, but there is still no capture devices in ALSA. logs: "[ 1.343850] apple_aop 2a6c00000.aop: Adding to iommu group 1#asahi · 2025-03-25 22:55
thasti_similarly, the meters in the plasma audio widget stays pinned at 0 when pavucontrol is open#asahi · 2025-03-25 22:54
thasti_this seems to reproduce: when pavucontrol is open, recording in audacity only gives a repeated short 'loop' of some very quiet samples (not just very quiet audio afaict) - after closing pavucontrol and starting a new recording, the mic works perfectly fine#asahi · 2025-03-25 22:42
chaos_princessyou need to start all endpoints, otherwise it just sits there doing nothing#asahi · 2025-03-25 22:42
evil_king_8791okay#asahi · 2025-03-25 22:42
jannaunot sure if we need the unnamed endpoints#asahi · 2025-03-25 22:41
jannauevil_king_8791: keep it for now since I see an endpoint #0x2d#asahi · 2025-03-25 22:40
evil_king_8791jannau: should i revert the first patch you shared?#asahi · 2025-03-25 22:39
thasti_yet, it appears that it stops working as soon (and for as long) as I open pavucontrol#asahi · 2025-03-25 22:36
evil_king_8791jannau: thx, trying)#asahi · 2025-03-25 22:36
jannauevil_king_8791: please try https://paste.centos.org/view/a7a0e9e0 (M2 Pro/Max only)#asahi · 2025-03-25 22:35
thasti_works fine there now :)#asahi · 2025-03-25 22:34
chaos_princessthere is another issue that you may or may not run into#asahi · 2025-03-25 22:34
chaos_princesscheck audacity first#asahi · 2025-03-25 22:34
chaos_princessheh#asahi · 2025-03-25 22:33
thasti_thanks for the hint#asahi · 2025-03-25 22:33
thasti_uhhh wait, that's embarrassing. i was checking only pavucontrol (since i'm generally using sway) and made sure nothing was muted there .. just logged into plasma and found the mic muted there, now the meters move#asahi · 2025-03-25 22:31
chaos_princessall zero would be strange, but try opening the kde volume control panel, making some noise and look if the meters move#asahi · 2025-03-25 22:29
thasti_i see a MacBook Air J413 Microphone input device, but cannot get any audio from it (all-zero, e.g. when recording with audacity, webrtc etc)#asahi · 2025-03-25 22:29
chaos_princessevil_king_8791: no, that problem seems to be m2pro/max specific, vanilla m2 confirmed works#asahi · 2025-03-25 22:29
chaos_princessdoesn't show up or too quiet#asahi · 2025-03-25 22:29
evil_king_8791thasti_: I suppose that we disscussing the same problem now#asahi · 2025-03-25 22:29
chaos_princessin what way it doesn't#asahi · 2025-03-25 22:28
thasti_jannau: hmm, okay - anything you would recommend to debug why it doesn't?#asahi · 2025-03-25 22:28
Calandracas_Just did a zoom call, and the mic update works great! Thanks guys!#asahi · 2025-03-25 22:27
jannauthasti_: no, mic works on f40 and f41#asahi · 2025-03-25 22:27
evil_king_8791nice :)#asahi · 2025-03-25 22:27
jannauevil_king_8791: no need to, I'll have a patch to try in a few minutes#asahi · 2025-03-25 22:26
evil_king_8791jannau: maybe there is something with what I can help on my machine?#asahi · 2025-03-25 22:21
thasti_hi! got a quick question: should I expect the mic to work on an M2 air (j413) on FAR41 or is the upgrade to 42 beta required for that?#asahi · 2025-03-25 21:56
chaos_princessNo idea what it means but it comes from the device tree#asahi · 2025-03-25 21:46
jannauchaos_princess: patched bootargs differ, EC0p is 0x100_00000000. what is aop-target? it differs between laptops and desktops#asahi · 2025-03-25 21:23
JamesB192fl0_id, thank you.#asahi · 2025-03-25 21:08
chaos_princessdon't bother at this point, it is not the issue we were thinking about#asahi · 2025-03-25 21:07
fl0_idJamesB192 sorry for being a bit short before, this seems like a suitable guide. adjust for newer kernel etc https://discussion.fedoraproject.org/t/trouble-with-installing-a-patched-vanilla-upstream-kernel/105818#asahi · 2025-03-25 21:05
chaos_princessiop power should be harmless then, no?#asahi · 2025-03-25 21:04
jannauaop seems to be already on. macos doesn't use SetIOPPower but gets immediately HELLO on the management EP after toggling run in CPU control#asahi · 2025-03-25 20:57
chaos_princesscould you capture a m1n1 trace on a m2 pro then?#asahi · 2025-03-25 20:56
jannauendpoints init as well and there are some syslog messages#asahi · 2025-03-25 20:54
chaos_princessjust rtkit? or endpoints too?#asahi · 2025-03-25 20:53
jannauaop's rtkit inits on m1 max studio#asahi · 2025-03-25 20:49
chaos_princessdoes macos initialize aop at all on desktops?#asahi · 2025-03-25 20:22
jannauit doesn't power on, nothing happens after SetIOPPower#asahi · 2025-03-25 20:08
evil_king_8791jannau: you think that it can't properly probe hardware?#asahi · 2025-03-25 20:01
jannausame behavior