You are not logged in.
Pages: 1
so, my fiio ka1 is breaking from time to time and I have to reflash the firmware from a windows vm
(basically the indicator led is not on and it shows as "ESS Technology, Inc. ESS USB Audio" in lsusb)
it's like always, if not most of the time, after a system update and reboot...
the device is used solely with the pc
now, before RMAing it, I'd like to find out whether it's a hardware issue or another arch linux monday
tips on what to do? again, I'm not 100% sure about anything I wrote
Last edited by susamogus (2024-03-27 15:04:19)
Offline
First of all, make absolutely sure that Windows fast boot is disabled -- audio cards are often the first victims of failing to do that: https://wiki.archlinux.org/title/Dual_b … ibernation
Other than that compare lsusb,dmesg and aplay between working and not working, what are the differences? Maybe post these outputs for the working and not working conditions. https://wiki.archlinux.org/title/List_o … n_services
Offline
https://paste.sh/7BsX5V10#AfTqjBwby7OvQ1o99XmPwMZw (couldn't figure out aplay but it did show different device names)
I'm not dualbooting
interestingly the flasher tells that the firmware is "ok," but still it won't work without a reflash
either way, now that I've reflashed we probably have to wait a few days before it breaks again
Last edited by susamogus (2024-03-27 15:51:39)
Offline
life update. I switched to debian sid just over a week ago. I update every other day but absolutely no issues with the dac, whereas I'd already have reflashed multiple times on arch
or it was something with my specific setup? idk, it's not my business anymore
Last edited by susamogus (2024-04-09 08:23:11)
Offline
Happening after system update could be the udev retrigger leading to some edge case, sorry could've surmised that, FWIW if you're willing for an experiment, does running
sudo udevadm trigger -c change
recause the issue on debian? Might also be kernel/linux-firmware specific. But if an udevadm trigger would repro this this would be interesting for a current discussion on the usefulness of keeping that setting on system updates.
Offline
it does not cause the issue
Offline
Pages: 1