You are not logged in.
If you see it physically on the DAC that it receives the signal then the issue is out of linux's control. Check your cables/physical volumes.
Sorry to bother you and this issue. my problem solved. have a shortage of power supply of the usb port.
Offline
Same problem with my walkman.
5.10 works fine, def something with the new kernel, tested in a fresh install.
Kinda new, how can I report the bug?
thx.
Offline
Now that the default card is set, could you post the output again of:
killall pulseaudio speaker-test -c 2
This time I am under 5.11.6-arch1-1. Hope this update can fix my issue. However, my issue is still not fixed.
killall pulseaudio
pulseaudio: no process found
speaker-test -c 2
speaker-test 1.2.4
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 96 to 1048576
Period size range from 32 to 349526
Using max buffer size 1048576
Periods = 4
was set period_size = 262144
was set buffer_size = 1048576
0 - Front Left
1 - Front Right
Time per period = 12.143067
0 - Front Left
1 - Front Right
Time per period = 12.287247
0 - Front Left
1 - Front Right
Offline
If you see it physically on the DAC that it receives the signal then the issue is out of linux's control. Check your cables/physical volumes.
My USB device didn't show it received any signal but KDE Audio component shows dynamic on the sound meter while playing music.
If I have time. I may try to trace diff between kernel 5.10 and 5.11 to find what change leads to my issue.
Offline
V1del wrote:If you see it physically on the DAC that it receives the signal then the issue is out of linux's control. Check your cables/physical volumes.
Sorry to bother you and this issue. my problem solved. have a shortage of power supply of the usb port.
Would you mind show some details of your issue? Like what model of the DAC. How you fix your low voltage issue
Offline
nzfadz wrote:V1del wrote:If you see it physically on the DAC that it receives the signal then the issue is out of linux's control. Check your cables/physical volumes.
Sorry to bother you and this issue. my problem solved. have a shortage of power supply of the usb port.
Would you mind show some details of your issue? Like what model of the DAC. How you fix your low voltage issue
Sorry for not being able to help you. I am not using WALKMAN or any SONY DAC, and I am using a USB hub that can be connected to an external power supply (which forgot to connect at the first time)
Offline
Experiencing the same issue with my Walkman. KDE recognizes the device, the system looks like it is sending audio to it, but there is no sound detected on the device.
Current kernel version is 5.13.5
Kernel version 5.10 woks fine though
Any updates on finding what is causing this issue? perhaps we can submit a bug report somewhere if it's the case
Offline
Compare journal/dmesg/kernel logs between working and not working. Is it "just" the DAC or are other USB devices affected? What's your
lspci
lsusb
output? The 5.10 kernel works fine, 5.13 does not sounds like you have a renesas USB controller which is known to be problematic and might be helped by installing https://aur.archlinux.org/packages/upd72020x-fw/
If you want to be actually active in finding the cause, the best way to do that is a bisection between a known good kernel and a known bad one, but that will require you to do quite a few kernel rebuilds and reboots and tests.
Last edited by V1del (2021-07-30 07:23:15)
Offline
I have already gone down the route of comparing the output of `lsusb -v` on 5.10 and 5.11+, there is absolutely no difference. I can see exactly the same behaviour on three different machines, so this is very unlikely to be related to any particular piece of hardware. As you say, the only option we are left with to find out is to bisect, but I haven't found the motivation to do that yet!
Offline
For the record, I have actually found the motivation to bisect this (in a VM to speed things up). The good news is that I have found the culprit: bf6313a0ff76. The bad news is that it's a pretty big refactoring commit, so nothing easy to revert or tweak here Will try to dig further if I find the time.
Offline
I have now filed a bug on the kernel BugZilla, fingers crossed: https://bugzilla.kernel.org/show_bug.cgi?id=214105
Offline
I am really glad to report that the issue has been identified and there is now a patch to fix it! It has already made it to the sound.git tree: https://git.kernel.org/pub/scm/linux/ke … faceec8911
It should go into 5.15-rc1 (in a couple of weeks), at which point it could be easily backported to the Arch kernel, while waiting for the 5.15 release. In the meantime, it is straightforward to rebuild the linux package with that patch applied (which is what I'm currently using).
Offline
Thanks for the hard work Corax!
Offline
Happy to help Makes me realise I forgot to give a final update: the fix got backported in 5.14.2 (IIRC), which means that the latest Linux package on Arch should just work!
Offline