#
…

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:45mpss/ pipework/pipewire 1.0.5/
07:45chadmedmps: interesting, the only fix between 2.1 and 2.0 was for j416...
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 :)
07:46chadmednow just for *checks notes* literally everything else
07:48mpschadmed: yes, but anyway thank you for fix
07:50leiochadmed: he hopes you and/or me can take on the bump and dealing with it all
08:14chadmeddo we have a specific channel for that kind of thing
08:18leionot really, no; could be #gentoo-dev (might need to voice you) or #gentoo-desktop or even #gentoo-arm.
08:18leiomaybe desktop is suitable enough.
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:23leioI think wireplumber would be more about stuff like helvum or whatwasit than easyeffects?
08:24chadmedi believe both helvum and qpwgraph talk to libpipewire directly
08:27chadmedyeah it links against libpipewire
08:29chadmednothing even depends on wireplumber
08:29chadmedwaybar and pipewire are the only things in ::gentoo
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:00mpsanyone could tell how to do this
11:01chadmedenable UCLAMP_TASK in your kernel config
11:01chadmedour wireplumber and pipewire config fragments do the rest
11:01mpschadmed: I enabled it long ago
11:02chadmedoh then youre fine no further action is required
11:03mpsthanks for info, but I hear 'cracks' sometimes especially when there is heavy I/O
11:03chadmedoh you mean actual performance
11:03chadmedwell pegging wireplumber to icestorm isnt gonna fix that, firestorm are the pcores
11:04chadmedheavy i/o is suspect though, the cores should handle it
11:04mpsah, yes, I meant to say firestorm
11:04chadmedwhat source are you listening to and what is "heavy io"
11:04mpsheavy i/o is usually building software
11:05mpskernel, for example
11:05chadmedim building firefox on an m2 air right now and watching 1440p youtube
11:05chadmedand not a single audio underrun
11:06chadmedah ah ah
11:06mpssources are usually video/audio from internet and playing locally with 'mpv'
11:06chadmeddoes alpine list rtkit as a dependency of pipewire/wireplumber
11:06mpslet me check
11:07mpsso I should install it, I guess
11:07chadmedah yeah lol so the uclamp stuff and the rtprio stuff isnt gonna do anything in that case
11:07chadmedwhich is why youre getting underruns
11:07chadmedpipewire and wireplumber assume the presence of rtkit to renice themselves
11:08mpsjust installed it
11:08chadmedprio should be 9 and niceness should be -11 for both pipewire and wireplumber
11:08mpschadmed: nice and thank you very much
11:08chadmedno problem :)
11:10mpsbtw, how the prio and niceness is set on gentoo? Init script?
11:16chadmednope, rtkit
11:17chadmedlike i said the asahi-audio config tells pipewire and wireplumber to set their own prio and niceness via rtkit
11:17chadmedi added the ability to set uclamp to both a while back
11:19mpsaha, so only have to start rtkit and restart pipewire and wireplumber
11:20jannaushould asahi-audio or asahi-meta[+audio] (optionally) depend on rtkit? it doesn't yet as far as I can see
11:21chadmedyeah i was just thinking that
11:21mpsmakes sense
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:40leiobecause it gets rtprio on all threads, not just those that pipewire might want
11:41leiosam_ knows more, he's the limits.d proponent :D
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:42leioI'm not following that part
11:42leiovia limits.d pipewire, and only pipewire, is running at nice level -19 and rtprio
11:43chadmedthat file sets the limits on the user group, and pipewire is not started by a user in the @pipewire group
11:43chadmedit is started as the logged in user
11:43leioin practice I see -11 though
11:43chadmedyes, that's probably rtkit
11:43leioI might have found the wrong limits.d too
11:44chadmedwith rtkit uninstalled pipewire starts with 20 0 just like every other user process
11:44leioelog says to add your user to pipewire group
11:44leioand that's one of the parts I don't like about it
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:44chadmedwhich, again, will just make the scheduler treat all my processes exactly the same
11:45chadmedthereby negating any benefit of bumping the niceness/prio of pipewire
11:45leioI see what you mean.
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:45leiobut I don't know what limits.d is about
11:45chadmedive already wired up direct sched_{get,set} into pipewire and wireplumber
11:45leiomaybe it just allows the process to increase its priority without giving an error when not root
11:46chadmedso maybe we just push to get rtkit yeeted
11:46leioI'm not sure anyone has even asked heftig what's up
11:46chadmedthey have not responded to a single PR or issue in 5 years
11:46chadmedi dont think they're particularly interested in telling us whats up :p
11:46leioI know he's somewhat around in gnome circles
11:47leioor used to be less than 5 years ago
11:47chadmedgithub profile is still very active
11:47leioregarding limits.d stuff, I'm not sure everything will get that priority; it just might be changing the limits
11:47leioallowing a process to lower the niceness value (higher priority) themselves
11:48leiowhich is also a bit iffy, as anything could go and start doing it then, not just pipewire
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:48leiobut not interested in the re-logins to find out :D
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:49chadmedyeah sorry i was confidently wrong :p
11:49chadmedit just sets the limits
11:49chadmedbut thats also really sus as you said
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:50chadmedso i think long-term pipewire and wireplumber should also just stop depending on it
11:51chadmedespecially now that like i said they can both already just sched_{get,set}
11:52leioon GNOME there's a hard dep on rtkit already too
11:52leiohow does the kernel let it? As in, how do those sched_set things work?
11:53chadmedi believe any thread can ask for clamping values
11:53chadmedsched_set will probably return EPERM when trying to renice or set prio
11:54chadmedsched_setattr*
11:54leioGNOME needs to give a higher priority to its input and/or kms thread
11:55leioand apparently pipewire does too
11:55leio(the -11 niceness)
11:56chadmedyeah pipewire needs to so that it's not blocked by some non-interactive thing
11:57chadmednot convinced input or rendering have any particular need to be bumped except on extremely gutless systems but eh
11:59leiothis made a huge difference.
11:59leiochoppy mouse cursor is a very bad experience
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:02leioare you sure? I mean, that's kind of the topic with kwin6 in a way right now :D
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:03leiothat said, I can't spot that thread in my htop right now
12:03chadmed26415 james 20 0 2014816 429072 407712 R 10.6 2.7 11:10.56 kwin_wayland
12:04leiothere's a -21 0 and a 39 19; rest are 20 0
12:04leionot quite sure what the former number means
12:04j`eychadmed: you dont use chadmed as a username?
12:04chadmedno that's cringe
12:05j`eyI dont even know if j`ey is a valid linux username
12:05chadmedmy uncle (a windows user) is still baffled why he cant use his name anywhere in the system
12:05chadmedhis name is constantine but of course goes by a shortened version of that name
12:06j`eyswitch him over to linux!
12:07chadmedim working on it
12:07chadmedgranddad's got an m2 mini running F39 now
12:07chadmedbaby steps
12:07j`eyjealous
12:07j`eyupgrade that bad boy to rawhide
12:07chadmedill bump it to F40 on thusday when im over there
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:10j`eythis is fun, my test is failing inside a VM, non deterministically
12:13chadmedit would be boring if it was deterministic
12:13j`eyI want it to be boring so I can fix it and send my patches out!
12:14j`eyon friday I was like 'finally get round to sending out v4'
12:14j`ey test in a VM again and see a failure D:
12:14chadmedat least you caught it before sending it
12:15j`ey(also I forgot this was #asahi-alt, not -offtopic, woops)
12:15mps(my granddaughter must be happy because her grandfather runs linux exclusively :-) )
12:15chadmedthe utter shame, embarrassment and self-disgust one feels when having to force push like 3 minutes after opening a PR
12:15mpsoh, also her grandmother
12:16j`eychadmed: cant force push to LKML!
12:17chadmedno its even worse there - v4 T16:53:00Z... v5 T16:58:00Z
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
14:36leiodoes it need the subslot bump in pipewire?
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:20jannauyes, was just a race
19:32leiojannau: ok, old kernel just goes "dcp-dp-audio 239b540000.audio-controller: audio TX DMA channel request failed: (efault)" on the echo
19:33jannauwhat do you mean by old kernel? asahi-6.8.8-2 or asahi-6.8.6-4?
19:34leiohaven't spotted a 6.8.8-2 PR ;)
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:41leiobut happy to test if I know what; 6.8.8-2 or 6.8.8-2 + a patch?
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
20:11jannauyes, that's know
20:11leiodmesg shows a SIO failure, but that's the first die one then as per above
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
…