#asahi-alt · 2025-04-11 20:38
chaos_princesslooks correct#asahi-alt · 2025-04-11 20:37
floklihttps://paste.linuxlounge.net/AY#asahi-alt · 2025-04-11 20:37
chaos_princesscan you also list /proc/device-tree/soc/aop@24ac00000/#asahi-alt · 2025-04-11 20:34
flokliMacBook Air J413#asahi-alt · 2025-04-11 20:34
chaos_princessand which device is it?#asahi-alt · 2025-04-11 20:34
flokliI guess I can bump to asahi-6.14.1-3#asahi-alt · 2025-04-11 20:32
flokli31a0d9d457fde5974ff105c9ad19171f79959987#asahi-alt · 2025-04-11 20:32
flokliasahi-6.14.1-2#asahi-alt · 2025-04-11 20:30
chaos_princesswhere exactly are you getting the kernel from? (commit hash if possible, otherwise which branch)#asahi-alt · 2025-04-11 20:29
chaos_princessisnt that the wrong driver? apple_aop is the root device, while the one for the mics should be snd_soc_apple_aop_audio#asahi-alt · 2025-04-11 20:27
floklibut tbh I don't understand the logic there#asahi-alt · 2025-04-11 20:25
flokliit's not#asahi-alt · 2025-04-11 20:25
floklihttps://paste.linuxlounge.net/E4#asahi-alt · 2025-04-11 20:25
chaos_princesscan you check if the relevant property is present then?#asahi-alt · 2025-04-11 20:23
floklichadmed: -22 suggests it's running into the if "!audio && of.property_present(c_str!("apple,no-beamforming")) {" branch#asahi-alt · 2025-04-11 09:12
leio(for the earlier case the internal jack was selected and working with headphones)#asahi-alt · 2025-04-11 09:11
leioand now I got the usual problem (also desync) when playing over HDMI audio: https://bpa.st/ZWVA#asahi-alt · 2025-04-11 08:52
leio(not to mention getting it going in 240Hz with some overrides, but I haven't cared for it anymore)#asahi-alt · 2025-04-11 08:51
leiounrelatedly, the EDID stuff doesn't look to be working either?#asahi-alt · 2025-04-11 08:51
leiomacOS I saw it on older monitor firmware, but newer had a related fix claim; I haven't seen it on macOS lately, but I haven't used it for any longer durations since the monitor fw upgrade#asahi-alt · 2025-04-11 08:50
leioI dunno, I didn't touch the menu then, was staring at a terminal window#asahi-alt · 2025-04-11 08:32
jannauis there anything the monitor could report as change? monitor setting changes, integrated kvm, plugging in usb devices headphones or aan ambient light sensor#asahi-alt · 2025-04-11 08:30
jannauleio: '[AFK]Restaring interfaces with reason - Capabilities changed..' sounds like it might be the monitor. I guess you're not using macos would be interesting if it happens there as well#asahi-alt · 2025-04-11 07:55
floklichadmed: I'll be afk for a few hours, but can check later#asahi-alt · 2025-04-11 07:48
chadmedyeah okay so the kernel is shitting the bed for some reason#asahi-alt · 2025-04-11 07:44
flokli[ 9.731516] apple_aop 24ac00000.aop: probe with driver apple_aop failed with error -22#asahi-alt · 2025-04-11 07:44
flokli[ 9.731483] apple_aop 24ac00000.aop: Adding to iommu group 7#asahi-alt · 2025-04-11 07:42
chadmedflokli: can you also grep dmesg for "aop" and see if there are any probing errors#asahi-alt · 2025-04-11 07:40
flokliI'll manually diff the generated file with what's on /boot this evening, just to double check it indeed is what it's supposed to be.#asahi-alt · 2025-04-11 07:30
flokliso I'd assume my /boot/m1n1/boot.bin does contain all dtb files from the current kernel.#asahi-alt · 2025-04-11 07:30
leioany idea why my monitor sometimes loses signal and has to reacquire it? These are the logs from that time: https://bpa.st/UHCQ - should I blame the monitor (or cable?) on that one too or probably not?#asahi-alt · 2025-04-11 07:29
flokliyeah, we do this here: https://github.com/tpwrules/nixos-apple-silicon/blob/8457960249bcfd34c22838e20eaa7d8261428688/apple-silicon-support/modules/boot-m1n1/default.nix#L18#asahi-alt · 2025-04-11 07:27
chadmedthey need to be concatenated into the m1n1 payload though. they cant just exist on the filesystem#asahi-alt · 2025-04-11 07:27
chadmedyeah kernel tree dtbs#asahi-alt · 2025-04-11 07:25
flokliWe have a process populating bootloader things in /boot / the ESP, it could be looped into this. It might already be - Just need to know which dtbs we're talking about.#asahi-alt · 2025-04-11 07:22
flokliasahi-kernel tree?#asahi-alt · 2025-04-11 07:22
flokliwhere do the dtbs come from?#asahi-alt · 2025-04-11 07:22
chadmedyou really really ought to have some update-m1n1 analogue #asahi-alt · 2025-04-11 07:21
chadmedthats the latest, but the dtbs should be updated with every kernel uprev#asahi-alt · 2025-04-11 07:18
floklim1n1 is at 1.4.21, but u-boot is still at rev asahi-v2024.10-1 / version 2024.10-1-asahi#asahi-alt · 2025-04-11 07:17
flokliwe don't have this script, but our u-boot expression definitely seems to be outdated.#asahi-alt · 2025-04-11 07:14
chadmedupdate-m1n1? #asahi-alt · 2025-04-11 07:13
flokliI don't know how to update device trees. They're baked into uboot?#asahi-alt · 2025-04-11 07:10
flokliLinux m2air 6.14.1-asahi #1-NixOS SMP currently#asahi-alt · 2025-04-11 07:10
chadmedwhat kernel version are you on and did you update your device trees#asahi-alt · 2025-04-11 07:10
chadmedlol the mic device isnt even there#asahi-alt · 2025-04-11 07:05
floklichadmed: https://paste.linuxlounge.net/II#asahi-alt · 2025-04-11 07:02
chadmedflokli: can you paste the output of `arecord -l`#asahi-alt · 2025-04-11 06:58
chadmedi dont think it's hardware related. the ucm stuff is all at the alsa-lib or whatever level#asahi-alt · 2025-04-11 06:57
flokliIf you think it's something with the hardware, I might be able to run some patches or dig up some more info.