2024-04-30
01:00KxCORP589 has quit [Quit: Bye!]
01:01KxCORP589 has joined #asahi-alt
01:14jeisom has quit [Ping timeout: 480 seconds]
01:52pedantic_picto has joined #asahi-alt
03:11Mik_ has quit [Ping timeout: 480 seconds]
05:05KxCORP589 has quit [Quit: Bye!]
05:06KxCORP589 has joined #asahi-alt
05:20zerdox has quit [Ping timeout: 480 seconds]
05:52pthariensflame has joined #asahi-alt
05:53pthariensflame has quit []
07:42opticron has quit [Ping timeout: 480 seconds]
07:44mpsnice work! asahi-audio 2.1, wireplumber 0.5.2, pipework, latest kernel and latest m1n1 works fine on m1pro (j316s) with alpine linux. thanks all for good works
07:46chadmedoh btw sam_ if you're keeping track we're no longer a blocker for wp 0.5 so you can take us off the list :)
08:18leionot really, no; could be #gentoo-dev (might need to voice you) or #gentoo-desktop or even #gentoo-arm.
08:19leioI think mainly it's about knowing what might break, and if some users might need manual migration work, writing a news item for review
08:20chadmedfor a vanilla install the only thing that's gonna break is our oddball USE="sound-server" mechanism
08:20leioyou probably know most what could be affected; I guess users that have done asahi-audio kind of stuff manually on non-asahi (doubtful such exist?) and maybe someone having used some tooling that does something of that sort via a GUI if such exists? I think easyeffects is doing something else
08:20chadmedfor users that are doing weird things they're just gonna have to be on their own and we can write a news item directing them to the porting documentation
08:21chadmedeasyeffects doesnt rely on custom config afaict but when 0.5 first dropped a number of folks popped in to #pipewire to voice their disappointment that their funky little scripts no longer worked so i assume we have more than one person who would break
08:22leioso maybe beyond asahi-audio, there's no concerns beyond those that have done scripts manually, which we'd cover with a news item
08:37chadmedok nvm there are no explicit blockers at the ::gentoo level so i'm going to throw wireplumber 0.5 at ::asahi and see who comes knocking about breakage
09:08chadmed has quit [Quit: Konversation terminated!]
09:13chadmed has joined #asahi-alt
09:16ah- has quit [Read error: Connection reset by peer]
09:17ah- has joined #asahi-alt
10:05chadmed has quit [Quit: Konversation terminated!]
10:05chadmed has joined #asahi-alt
10:07chadmed has quit []
10:07chadmed has joined #asahi-alt
10:52Mik_ has joined #asahi-alt
10:59mpsiirc someone wrote earlier that is possible to lock (pin) wireplumber to icestorm to get better perfomance. I searched backlog but can't find this explanation
11:07chadmedah yeah lol so the uclamp stuff and the rtprio stuff isnt gonna do anything in that case
11:17chadmedlike i said the asahi-audio config tells pipewire and wireplumber to set their own prio and niceness via rtkit
11:20jannaushould asahi-audio or asahi-meta[+audio] (optionally) depend on rtkit? it doesn't yet as far as I can see
11:22chadmedits marked as an optfeature for pipewire/wireplumber, and i think the only reason it's not a hard dep is that its unmaintained
11:33jeisom has joined #asahi-alt
11:40leiochadmed: in gentoo rt is handled via /etc/security/limits.d/25-pw-rlimits.conf - I'm not convinced that's best.
11:42chadmedyeah i mean it kinda defeats the purpose because then the scheduler is just gonna treat all user processes the same
11:42chadmedwhich means pipewire is not any more favoured than anything else and we're right back to where we started
11:43chadmedthat file sets the limits on the user group, and pipewire is not started by a user in the @pipewire group
11:44chadmedif i create the @pipewire group and add myself to it, then _every single process_ i start will be started at the limits.d right
11:45chadmedi think long term if no one is going to step up and maintain rtkit then pipewire should just stop depending on it
11:45leiomaybe it just allows the process to increase its priority without giving an error when not root
11:47leioregarding limits.d stuff, I'm not sure everything will get that priority; it just might be changing the limits
11:48leiobut I'm not convinced everything out of the box will just run at highest priority if you add your user to the group
11:49leioI would just unconditionally depend on rtkit and get rid of this limits.d business, but lack some historical context
11:49leioif fedora and co rely on rtkit for all this, I don't see a need to be special in this regard
11:50chadmedi dont mind to hard dep on rtkit it's just already extremely brittle (couple of issues on the repo re build failures and odd behaviour during suspend etc) and clearly no one is interested in maintaining it
11:57chadmednot convinced input or rendering have any particular need to be bumped except on extremely gutless systems but eh
12:01chadmedsounds like gnome is brute forcing its way around something terriffically broken in its input handling then because neither kwin nor plasmashell boost their prio or niceness and ive not once had my cursor hang or drop a frame
12:02leiobut it makes sense to do, now that it's a very dedicated small thread, the schedulers used to be particularly bad too
12:05chadmedmy uncle (a windows user) is still baffled why he cant use his name anywhere in the system
12:08chadmedi was originally planning to foist gentoo on him but he was already used to fedora after using it for a few years
12:15chadmedthe utter shame, embarrassment and self-disgust one feels when having to force push like 3 minutes after opening a PR
12:42opticron has joined #asahi-alt
12:43zerdox has joined #asahi-alt
12:50opticron has quit [Ping timeout: 480 seconds]
13:06jeisom has quit [Ping timeout: 480 seconds]
13:21john-cabaj has joined #asahi-alt
13:24chadmedsam_, leio: i've pushed media-video/wireplumber-0.5.2:0/0.5, media-video/pipewire-1.0.5-r1:0/0.5 and media-libs/asahi-audio-2.1:0/2.0 to the overlay along with a news item explaining things
13:25chadmedbeen running wireplumber 0.5 locally for weeks now and tested the subslot change and all resolved correctly
13:49alice has quit [Remote host closed the connection]
13:50alice has joined #asahi-alt
14:12pedantic_picto has quit [Quit: Textual IRC Client: www.textualapp.com]
14:12pedantic_picto has joined #asahi-alt
15:51zerdox has quit [Ping timeout: 480 seconds]
16:24iyes has joined #asahi-alt
17:13iyes has quit [Ping timeout: 480 seconds]
17:27opticron has joined #asahi-alt
17:36opticron has quit [Read error: Connection reset by peer]
17:40opticron has joined #asahi-alt
17:50iyes has joined #asahi-alt
18:06iyes has quit [Ping timeout: 480 seconds]
18:10zzywysm has joined #asahi-alt
18:22john-cabaj has quit [Ping timeout: 480 seconds]
18:26pjakobsson has quit [Ping timeout: 480 seconds]
18:26pjakobsson has joined #asahi-alt
18:39iyes has joined #asahi-alt
18:46kloenk has quit [Remote host closed the connection]
18:47kloenk has joined #asahi-alt
18:59Mik_ has quit [Quit: Leaving]
19:00jannauleio: I've pushed a fix for m2 ultra hdmi audio to asahi-wip. not sure if it is indeed a fix or if it is just a race. no need for testing it's verified already
19:01jannauin the case it's a race, `echo 1 > /sys/devices/platform/soc@2200000000/239b540000.audio-controller/probe_snd_card` should reprobe the sound card and fix it. reconnecting the HDMI plug should fix it as well
19:09xal has quit []
19:11xal has joined #asahi-alt
19:32leiojannau: ok, old kernel just goes "dcp-dp-audio 239b540000.audio-controller: audio TX DMA channel request failed: (efault)" on the echo
19:38jannauthere's a tiny difference between those two kernels: https://paste.centos.org/view/f4da6863 - bringing both sio up in m1n1 wasn't a problem on m1 ultra but I haven't tested that on m2 ultra. possible that the current m1n1 code fails to bring up sio1 on m2 ultra
19:39leiook, I don't want to test as much as use it; the audio jack is seeing some heavy switching as-is between headset and external speakers
19:49jannau6.8.8-2 is ok, 6.8.8-2 + https://github.com/AsahiLinux/linux/commit/5a6266a9f5ac64f0474f764dbba88f8f94a69e48 avoids crashing sio on the first die which shouldn't cause problems
20:10leiojannau: works now, thanks. It's wrongly reporting as "Analog Output - Build-in Audio", but I think that was already mentioned earlier
21:25iyes has quit [Ping timeout: 480 seconds]
21:43opticron has quit [Ping timeout: 480 seconds]
21:47iyes has joined #asahi-alt
21:59jeisom has joined #asahi-alt
22:16opticron has joined #asahi-alt
23:19iyes has quit [Ping timeout: 480 seconds]
23:57john-cabaj has joined #asahi-alt