#
…

2026-11-09

01:08chadmed has quit [Remote host closed the connection]
01:08chadmed has joined #asahi-alt
01:10chadmed has quit [Read error: Connection reset by peer]
01:10chadmed has joined #asahi-alt
01:10chadmed has quit [Read error: Connection reset by peer]
01:11chadmed has joined #asahi-alt
03:05tobhe_ has joined #asahi-alt
03:12tobhe has quit [Ping timeout: 480 seconds]
03:57nicolo has joined #asahi-alt
03:57nicolosiduck[m]: indeed, Void should work well after you build a fresh iso
03:58nicoloone thing to consider is that it currently cross-compiles to aarch64{,-musl}
03:58nicoloso certain software, like sagemath, is not available in binary from repo
03:59nicolo has quit []
06:45bit_runner80 has joined #asahi-alt
07:08Calandracas_ has joined #asahi-alt
07:14Calandracas__ has joined #asahi-alt
07:14Calandracas has quit [Ping timeout: 480 seconds]
07:19Calandracas_ has quit [Ping timeout: 480 seconds]
07:32Calandracas_ has joined #asahi-alt
07:32bit_runner80 has quit [Read error: Connection reset by peer]
07:38Calandracas__ has quit [Ping timeout: 480 seconds]
07:56marcusr has quit [Remote host closed the connection]
07:59marcusr has joined #asahi-alt
08:33elara_ has joined #asahi-alt
08:34elara has quit [Ping timeout: 480 seconds]
08:34elara_ is now known as elara
08:37chadmed has quit [Remote host closed the connection]
08:37chadmed has joined #asahi-alt
08:40chadmed has quit []
08:40chadmed has joined #asahi-alt
08:55elara has quit [Ping timeout: 480 seconds]
10:34elara has joined #asahi-alt
11:41mpsi have problem with boot from usb. u-boot detect usb storage and start boot loader, kernel boots but cannot detect usb at all and enters emergency console. even then unplug usb and plug it again kernel doesn't detect it
11:42mpsall usb drivers related to storage are built in kernel, not as modules
11:44mpsalso boot from nvme with usb storage plugged in have to unplug and plug in usb storage to be seen and work
11:45siduck[m]nicolo: coool
11:47mpscould be CONFIG_USB_OTG=y problem
12:01cy8aerIt must be set or it must not be set?
12:04mpsit is set in my case
12:04mpsbut right now i set it to =n but this didn't help
12:09cy8aerOk thanks
12:10cy8aerNever had it set by the way
12:10mpsonly what i see is 'macsmc 23e400000.smc RTKit: syslog message: aceElec.cpp:1163: Elec: Elec Cause 0x0' kmesg
12:11mps0x0 also sometimes is 0x8000 ot 0x20000
12:11cy8aerKernel 7.1 up? That needs: CONFIG_USB4_APPLE_SOC=m, CONFIG_USB4=y minimum.
12:11cy8aerThey swapped to thunderbold usb4 there!
12:12mpsi have these
12:12chaos_princessdo you have any "waiting for power state" or something like that in dmesg?
12:14mps'pending due to $numbers.isp'
12:14flokliAny more kernel config options / modules needed when bumping from 7.2 and 7.3?
12:14mpspart of kmesg
12:15chaos_princessdoes it spam dmesg on unplug/replug?
12:15mpsalso i2s, cio and mux in place of cio
12:16chaos_princessthose are bad
12:16chaos_princessyou need apple_cio and apple_cio_reset built-in
12:21mpsfound only in Kconfigs RESET_APPLE_CIO
12:23chaos_princessis usb4_apple_soc built-in?
12:25mpsRESET_APPLE_CIO=y solved issue
12:26mpschaos_princess: as usual, many many thanks
12:27mpsyou helped me many times
12:27cy8aerOh, sorry the other parameter of 7.x. It was set automatically and therefor I do not mention it.
12:28mpsofc, all others from asahi team
12:28mpscy8aer: it was =m in my case
12:29cy8aeryes it was set y on my system
13:17cy8aer has quit [Remote host closed the connection]
13:23cy8aer has joined #asahi-alt
13:25elisaadodid anything audio related change between 7.2.15 and 7.3.3? the speakers of my j316s sound noticbly more highs-emphasized now but it might be my ears being weird? idk
13:27JamesCalligeros[m]The kernel has no bearing on the dsp so no
13:40LarstiQdid something change about your ears? ;)
13:40picnoir has quit [Quit: WeeChat 4.10.2]
13:41picnoir has joined #asahi-alt
13:46mpselisaado: on my j316s i don't hear any noticeable change (though my ears not good as were 5-10 years ago)
13:57elisaadoyeah I think my ears changed xD
14:01elisaadohm no something is up, I am getting audio stutters with the following in my kernel logs
14:01elisaadois speakersafetyd supposed to do that xD
14:01jannauis speakersafetyd restarting?
14:02elisaadopanic-ing
14:03elisaadoso out of the 5 panics, 1x left tweeter, 1x right woofer 1, 1x left woofer, 1x right tweeter, 1x right woofer 2
14:04elisaadoand some wireplumber logs surrounding it, I'll send a screenshot from my journal of the first crash
14:08elisaadoah that's why the highs are so pronounced, > [speakersafetyd] Speaker group 1 gain limited to -0.19 dBFS
14:09jannauI can reproduce issues at higher (not near 100% though) volumes
14:09elisaadoI am at 40% volume (on my j316s)
14:10elisaadoI will stick to 7.2.15-2 for now unless I can help with some tests or probes?
14:15jannauI have no issues at 50% but the point where issues start certainly depends on the audio signal
14:16MichaelLong has joined #asahi-alt
14:17elisaadoif it helps, at the time I was listening to the drum & bass song 18% by Particle :P
14:19Michae|Long has quit [Ping timeout: 480 seconds]
14:22jannauhuh, I thought I switched to the upstream macaudio but did not
14:31elisaadoI muted my audio and switched to using my phone for now, but still seeing speakersafetyd crashes (with nothing playing!)
14:49chadmed has quit [Quit: Konversation terminated!]
14:50chadmed has joined #asahi-alt
15:16Yushi has quit [Remote host closed the connection]
15:17Yushi has joined #asahi-alt
15:45Yushi has quit [Remote host closed the connection]
15:46Yushi has joined #asahi-alt
15:51Yushi has quit [Remote host closed the connection]
15:52Yushi has joined #asahi-alt
15:54chadmed has quit [Read error: Connection reset by peer]
15:54chadmed has joined #asahi-alt
16:03chadmed has quit [Ping timeout: 480 seconds]
16:32jannauelisaado: I can't reproduce with fedora on the same device (j314c) booted via HV vs self-compiled kernel gentoo. Fedora lags a little on speakersafetyd / asahi-audio but nothing looks like it could explain this
16:33elisaadointeresting, I'm on NixOS which packages the latest asahi-audio
16:34jannauasahi-audio is the least likely source of the issue
16:34elisaadoit's on 4.1, latest Asahi Audio is 5.0
16:35elisaadoI could try to upgrade it, see if that helps
16:35elisaadobut it also seems related to wireplumber
16:35jannaufedora is on 4.1 as well
16:36elisaadoI'm on wireplumber 0.5.19
17:02jannaufedora system is still on pipewire 1.6.9 / wireplumber 0.5.18, updating now
17:04elisaado(lib)pipewire is on 1.6.11 here
17:08jannauno issues after upgrading
17:09elisaadospeakersafetyd 3.0.0 ?
17:10elisaadolatest in fedora's repos is 2.0.1-1
17:16elisaadoif thats also not it then it has to be a kernel thing :/
17:35jannauback on gentoo with kernel 7.3.3 and it hasn't reproduced yet at 95% volume
17:42jannaunot sure what triggers it
18:03rivendell has quit [Remote host closed the connection]
18:04rivendell has joined #asahi-alt
18:07sckova[m] has joined #asahi-alt
18:07rivendell has quit [Remote host closed the connection]
18:07rivendell has joined #asahi-alt
18:08elisaadothat's cursed
18:08elisaadoI can try a reboot
18:09jannaureproduce now with a different symptom, speakersafetyd panicked with "Gain reduction exceeded threshold", audio wasn't even load
18:11jannauthe issue is that speakersafetyd either gets bogus ivsense data or it processes it in strange way
18:20elisaadosame here at high (75%) volume, Gain reduction exceeded threshold
18:21elisaadobut it feels like even without speakersafetyd limiting the gain my music sounds /different/
18:24elisaadoand now after a wireplumb restart and the last speakersafetyd crash I can't reproduce it anymore....
18:25elisaadoah, https://www.szynalski.com/tone-generator/ <-- at 113 Hz at mid to high volume can reprodue it quite well
18:46travltux[m] has joined #asahi-alt
18:47travltux[m] has left #asahi-alt [#asahi-alt]
18:48rivendell has quit [Remote host closed the connection]
18:50rivendell has joined #asahi-alt
19:00bgb has quit [Remote host closed the connection]
19:00bgb has joined #asahi-alt
19:28vimproved has quit [Remote host closed the connection]
19:30vimproved has joined #asahi-alt
19:41cy8aer has quit [Remote host closed the connection]
19:48bgb has quit [Remote host closed the connection]
19:52cy8aer has joined #asahi-alt
19:54bgb has joined #asahi-alt
22:17myriaelisaado, jannau
22:19jannaumyria: I picked that patch up but it is the wrong speaker amp. tas2770 is only use on devices with base m1
22:20jannauI was thinking if we might need the same for tas2764
22:20myriaquite possibly, JamesCalligeros[m] thoughts?
22:21jannaubut it seems to have that already
22:34bgb has quit [Remote host closed the connection]
22:38bgb has joined #asahi-alt
22:49JamesCalligeros[m]yeah 2764 already has this
22:49JamesCalligeros[m]i will investigate at home this evening
22:52JamesCalligeros[m]thats gonna be a looong emerge -auvDN @world...
23:03jannauit's unfortunately not reproducible just by playing the same audio
23:03JamesCalligeros[m]i havent changed anything recently that would affect the sound on that machine...
23:04JamesCalligeros[m]and we didnt pull in the on-list version of macaudio
23:07jannaudiff between 7.2.14-1 and 7.3.3-1 is very small. the most suspicious thing I saw was that REG_SYNCGEN_MCLK_SEL gets now BIT(1) or-ed instead of writing 7
23:08JamesCalligeros[m]I’ll look into it. There was a reason for that but I can’t remember what
23:08JamesCalligeros[m]Wouldve helped if there were proper commit messages from the authors but alas
23:09jannauyou changed it after Joshua asked about "6 + 1" in https://lore.kernel.org/all/sCELYiNQSvCxqjQFP0uhkQ@gmail.com/
23:10JamesCalligeros[m]I dont know where 6+1 came from is the problem
23:13jannauI mostly noticed it because `BIT(ffs(port_mask))` looks wrong. ffs() returns 1 + 0-based index of the first set bit (or 0 for ffs(0))
…