I have an audio interface Focusrite Scarlett 2i4 which is recognized in ALSA and pulseaudio. When I turn the PC off for the night and turn it back on in the morning, there is no sound output from the interface to the speakers. Pavucontrol and ALSA still see the device and from Pavucontrol I can see that the audio is being played and sent to the unit, but no sound is outputted from the speakers.
I have discovered that I can get the sound back if I boot into windows, unplug the interface, re-plug the device back in and reboot into Linux. Then I get sound until I decide to power off the system again. Rebooting works fine and the audio interface initializes itself properly, the issue only occurs when I turn off the PC.
Weird thing is that if I happen to be in windows, shut the PC down, boot it back up into windows, then the interface also initializes itself correctly and the sound is working fine. So the issue seems to be limited to how Linux handles the initialization of the audio interface after a cold start/power-off. (again, rebooting Linux or between windows and Linux, the audio keeps working, so it only affects Linux cold starts)
Also a minor thingy I have noticed is that whenever the device is initialized when logging in, all the lights on the interface blink for a split second, that’s when I know that I’m getting sound from it. During cold starts it does not happen.
I have tried checking ALSA settings for mutes and configuration - nothing is muted and the device is recognized as needed.
Also tried resetting the alsa-restore.service - I am not sure if that would do anything, but I thought it was worth a shot. When I do restart the service, I see this error in the service logs:
okt 13 11:08:02 Shoemaster alsactl: /usr/bin/alsactl: set_control:1461: Cannot write control '2:0:0:USB Internal Validity:0' : Operation not permitted okt 13 11:08:02 Shoemaster systemd: Starting Save/Restore Sound Card State... okt 13 11:08:02 Shoemaster systemd: Started Save/Restore Sound Card State.
I am not an expert and don’t know much about how ALSA works, but it seems to me that the device is rejecting the initial initialization of the audio passthrough. Or I might be mistaken. Hence I’m here, hoping that the more experienced community members could maybe give a helping hand so I would properly have audio at home. The best that the Focusrite support could offer is to boot into windows as they don’t support Linux.
I have also tried to remove the kernel module for usb-audio and re-probing it - which results in a reboot-simulator for the interface:
sudo rmmod -f snd_usb_audio && sleep 5 && sudo modprobe snd_usb_audio
Unfortunately this did not help either - interface is recognized but no sound is passed through it to the speakers.
As I also noticed that both Blue Yeti and Focusrite use the USB Audio driver, I thought I would test it with the Yeti un-plugged to make sure that the driver is not getting confused - and it is not, results are the same unfortunately.
Also the issue is not directly related to Manjaro - I could re-produce it on Arch so I don’t expect any fixes or similar from the team. Maybe just if someone has any ideas, I would be more than happy to try them out.
Manjaro branch: Testing
System: Host: Shoemaster Kernel: 4.13.5-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Manjaro Linux Machine: Device: desktop Mobo: MSI model: Z97 GAMING 3 (MS-7918) v: 1.0 serial: N/A BIOS: American Megatrends v: V2.3 date: 07/24/2014 CPU: Quad core Intel Core i7-4790K (-HT-MCP-) cache: 8192 KB clock speeds: max: 4400 MHz 1: 3999 MHz 2: 3999 MHz 3: 3999 MHz 4: 3999 MHz 5: 3999 MHz 6: 3999 MHz 7: 3999 MHz 8: 3999 MHz Graphics: Card: NVIDIA GP104 [GeForce GTX 1070] Display Server: N/A driver: nvidia tty size: 100x45 Audio: Card-1 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel Card-2 NVIDIA GP104 High Def. Audio Controller driver: snd_hda_intel Card-3 Blue Microphones Yeti Stereo Microphone driver: USB Audio Card-4 Focusrite-Novation driver: USB Audio Sound: Advanced Linux Sound Architecture v: k4.13.5-1-MANJARO Network: Card: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 44:8a:5b:d2:ab:05 Drives: HDD Total Size: 1378.3GB (25.0% used) ID-1: /dev/sda model: Samsung_SSD_840 size: 128.0GB ID-2: /dev/sdb model: Samsung_SSD_850 size: 500.1GB ID-3: /dev/sdc model: Samsung_SSD_850 size: 250.1GB ID-4: /dev/sdd model: Samsung_SSD_850 size: 500.1GB Partition: ID-1: / size: 113G used: 13G (13%) fs: ext4 dev: /dev/sda2 ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda1 Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 42C Fan Speeds (in rpm): cpu: N/A Info: Processes: 217 Uptime: 1 min Memory: 2511.6/16003.2MB Init: systemd Client: Shell (zsh) inxi: 2.3.40