I’m using fedora 43 for about a month now and I recently started having issues with my audio setup.
I’m using a Focusrite Scarlett 2i4 (1st Gen.) USB audio interface. I’m making music on fedora and use Reaper as my Digital Audio Workstation, though the problem I’m having is also happening in Ardour. I’ve ruled out the DAW as an issue.
The problem:
Starting my DAW results in the audio signal sounding “metallic” and distorted. It seems like an issue with the sample rate and Linux trying to convert the sample rate to 48kHz in realtime. I couldn’t exactly pin point it, though.
However, the temporary “fix” for me is to roll back the kernel from 6.19.8-200.fc43.x86_64 to version 6.19.6-200.fc43.x86_64 with grubby and then reboot.
It might sound like a kernel regression at first, but if I change the kernel back to 6.19.8 after the first reboot and then reboot again into this current kernel version, everything works just fine. Subsequent reboots also don’t cause any issues from that point on. The issue reappears after a cold start of the computer, though.
Yes, I did look into this. Sadly, this is only relevant for 2nd generation Focusrite Scarletts and newer. My interface is still from the first generation, released in 2012. Since my issue seems to be rather esoteric, I might have to bite the bullet and invest in a new interface.
Just to recap the issue:
The interface worked just fine with kernel 6.19.6.
Kernel update 6.19.7 introduced the issue of the sound getting “metallic” and distorted when I start any DAW (tested with Reaper and Ardour), most likely related to the sample rate
the issue persists with Kernel 6.19.8 and 6.19.9
Rolling back the kernel to 6.19.6 solves the issue - changing the kernel to a newer version, like the current 6.19.9 followed by a reboot doesn’t cause the issue
The issue reappears after powering off the machine completely and turning it back on (cold boot)
Problems with older devices are often inadvertent side effects of changes to Linux. I make a point of trying new Fedora versions during the pre-release test period with my oldest hardware, as linux devs are unlikely to be using older hardware, but the pool of old devices is increasing at a time when linux devs are being hijacked by AI projects. Unless someone with the same hardware can propose a solution, fixes may be a long time coming, if ever.
Nothing’s wrong with the device. It’s a software issue.
Try kernel 6.19.10
Also compare journalctl -b -k outputs for the working and non working kernel after a cold boot and maybe also for a kernel > 6.19.6 after a warm start.
I assume the device will fail again if you unplug it for a few seconds?
Thank you so much for your very helpful reply, Mark. I think you are actually onto something regarding the probable culprits. I already filed a bug report on March, 15th and wrote an e-mail to the author of the commits yesterday.
I got my hands on another audio interface (Arturia MiniFuse 2) just to make sure that this is indeed a device-specific issue - and it is. The Arturia works perfectly fine with the current kernel.
Please do not email the developers directly. This is not recommended, and you might be ignored. File an issue/bug instead.
In this case @gnwiii posted the link to the repository above.
And see, someone already created a bug report two weeks ago.
