00:06 <akaWolf0> but to be honest that time they did pretty worthy integration IRC and Matrix

00:28 <akaWolf0> steev: why aplay doesn't work for you and works for me?

00:29 <steev> i do not know, or care

00:29 <steev> i *never* use aplay

00:29 <steev> it's 2023, not 1998

00:29 <akaWolf0> steev: we have to figure it out since as you can see there is some unstability with the sound

00:30 <akaWolf0> you got me wrong: aplay is for checking, not for every day use

00:30 <steev> you can dig into it, i do not have the time

00:47 <akaWolf0> yeah and when it not worked with default device it also didn't work with aplay -D.

00:48 <akaWolf0> I guess it's related

00:56 <HdkR> aplay usually fails when something else already has access on the hardware

00:56 <akaWolf0> HdkR: yeah, but it wasn't a case

00:59 <HdkR> does pipewire not open the device?

00:59 <HdkR> Because I had to kill pulse for aplay to work

01:01 <akaWolf0> HdkR: it doesn't keep it open while not playing

01:01 <akaWolf0> or open another device

01:02 <akaWolf0> ah, no, it opens hw:0,5 and close when there is no sound

01:05 <HdkR> Interesting

01:15 <akaWolf0> there is pipewire for v4l2 also :)

01:49 <HdkR> One day I'll switch over to pipewire :P

01:51 <HdkR> Pulse's support for zero auth network audio streaming is something I would miss a lot

01:57 <HdkR> (Plus a few other things)

01:58 <akaWolf0> HdkR: but bluetooth support in pipewire much better

01:58 <HdkR> I used to use the aptx pulse plugins so I didn't notice that problem :D

01:59 <HdkR> pipewire doesn't pipe bluetooth latency numbers through still I think?

01:59 <HdkR> So you can't determine what audio profile has the lowest latency and quality ratio

02:01 <HdkR> My current headphones have lowest latency with AAC where aptx is something like double the latency for example. But I could only determine that through pulse rather than pipewire

02:03 <akaWolf0> HdkR: I don't know, I don't use bluetooth stack et all, but I encourage you to try and to share your impression

02:04 <akaWolf0> does pulse can auto switch bluetooth profiles?

02:04 <HdkR> pulse lets you select the profile

02:05 <akaWolf0> but it's handy to autoswitch them when you started a call and ended it

02:05 <HdkR> some pactl command for getting latency and choosing profiles, and also pavucontrol lets you do it

02:05 <HdkR> oh yea, I don't use my headphones for calling at all

02:05 <akaWolf0> HdkR: I guess it's something missing in pulse AFAIK

02:06 <HdkR> SBC/HFP can go die in a fire for all I care :P

02:06 <HdkR> The audio quality destroys me on that

02:07 <HdkR> SBC/HFP/HSP*

02:09 <akaWolf0> yeah, definitely

02:10 <HdkR> Which is why I take calls with my AKG K712 headphones and Blue Yeti mic. So the limiting factor is the call service

02:10 <HdkR> Google Meet still not supporting full-duplex audio!

02:15 <akaWolf0> what about https://telemost.yandex.ru/ ? :)

02:15 <HdkR> Dunno what that is

07:01 <konradybcio> Probably Google meet except yandex

08:04 <jhovold> steev and anyone using my wip branches for the X13s: here's an updated branch based on v6.4-rc3:

08:04 <jhovold> https://github.com/jhovold/linux/commits/wip/sc8280xp-v6.4-rc3

08:04 <jhovold> Changes since the previous 6.3.3 branch include:

08:04 <jhovold> - audio speaker-playback regression fix

08:05 <jhovold> - disable DP PSR support which breaks virtual terminals

08:05 <jhovold> - suppress bogus usb-phy warnings

08:06 <jhovold> steev: srinik fixed the speaker playback regression, even if the best way to fix it is still being hashed out

11:34 <agl7-x13s> clover[m]: Hello Clover! Thank you for the .config! It was successfull now to generate the initrd-6.3.3-ironrobin. At this moment I'am in the Clubhouse. I will go home later and then I will try your kernel!

11:36 <agl7-x13s> Then I will see if the sound works and if I can record with the microphones.

12:19 <srinik> jhovold, steev: fixes are available in https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/log/

12:20 <jhovold> srinik: perfect, equivalent to what you have me yesterday (and that's in my 6.4-rc3 branch)

12:20 <jhovold> gave*

12:21 <srinik> jhovold: exactly same patches, with fix tags

12:24 <jhovold> srinik: except for the wcd938x_sdw one I guess, headphone playback still works without it though

12:25 <srinik> jhovold: i have added some checks in regmap-sdw so did not want to drop this out this invalid setup.

12:25 <jhovold> ok, got it

12:26 <srinik> jhovold: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?id=95856d1f3c223c015780fffb8373a827fc4efd2e

16:10 <agl7-x13s> clover[m]: Your kernel 6.3.3-15-x13s+ starts, but when it tries to mount the root partition the screen is cleared and nothing happens, as if it could not find the partition. BUT the kernel is NOT crashed! If I give Ctrl-ALT-DEL the x13s reboots and I can start another kernel in the grub that works. Can you explain this? Could it be that some kernel parameters are missing or have to be left out? I have the following kernel

16:10 <agl7-x13s> parameters set: ro pd_ignore_unused clk_ignore_unused

16:10 <agl7-x13s> And for the root I have root=UUID=.... specified.

16:10 <agl7-x13s> Everything is also specified at the kernel from steev and there the kernel starts normally.

16:10 <agl7-x13s> The root partition is on a USB-C-SSD that is connected to a USB-C-HUB and the USB-C-HUB itself is connected to the ThinkPad X13s at the USB-C port where the power supply is connected. The power supply is plugged into the USB hub and thus charges the ThinkPad X13s and provides power for the USB-C SSD. When I connect the USB-C SSD directly to the second USB-C port on the ThinkPad X13s, the SSD obviously does not get enough

16:10 <agl7-x13s> power and errors occur. When the USB-C SSD is connected to the USB-C hub, steev's kernel starts normally without errors.

16:10 <clover[m]> im not supporting non arch people sorry. told ya you were on your own

16:12 <agl7-x13s> ok

16:15 <agl7-x13s> I will also install ARCH arm64 on a USB-Stick. That wil be my next project.

16:16 <agl7-x13s> will

16:17 <clover[m]> cool, and if you have any issues there i CAN help you. i made an archiso and put instructions in the README: https://github.com/ironrobin/archiso-x13s

16:17 <agl7-x13s> clover[m]: Thank You!

16:33 <agl7-x13s> <clover[m]> I had already downloaded the ISO yesterday and loaded it on a USB stick and then I started the x13s with the USB stick. The way I see it, I guess I have to pull up everything from scratch from the text console, right?

16:33 <agl7-x13s> Or gives there a install programm?

16:34 <clover[m]> right, fully console based. arch doesnt do installers really unless you are talking about endeavouros or some other custom spin

16:34 <clover[m]> its all on the arch wiki just follow Installation_guide

16:36 <agl7-x13s> ok

16:37 <agl7-x13s> Is there a special Wiki for ARCH arm? When yes have you the URL?

16:43 <clover[m]> i put all of the special instructions in the readme

16:43 <clover[m]> the rest is just like a regular arch install

16:43 <clover[m]> * special instructions/information in

16:49 <agl7-x13s> ok

19:01 <steev> srinik: jhovold: okay, so i do get audio with the johan defconfig, but enabling lpasscc isn't enough with the defconfig, so i'll go through the diffs of the config and try to figure out what we're missing with defconfig

21:45 <clover[m]> godspeed