(Redirected from User:Lruzicka/QA:Testcase ALSA backend)
This test case tests that ALSA works as a sound backend and that various frontends can be used to communicate with it.
- This test case should be performed on bare-metal machines. To be able to test with virtual machines, consider a USB device pass-through. Leave a note in the comments if you have performed this test using the VM with the USB Passthrough strategy.
- The computer must be equipped with a sound device.
- Install a desktop version of Fedora 35 (or later).
- Make sure the
alsa-utilspackage is installed.
- Connect your speakers (headphones) to your computer’s sound device.
- Use an audio file in wav format. If you do not have one you can download a suitable audio file. Some default files can be also found in the
- Perform the following steps as a regular user.
How to test
List the sound devices known to ALSA.
$ aplay -l
or (for more details)
$ aplay -L
Identify the ones that represent the logical (
pipewire) or a physical device (
Play the audio file (wav) over the default device.
$ aplay -D sysdefault <audiofile.wav>
Play the audio file (wav) over a selected ALSA device. Make sure that you do not have another audio application running in the background, because the command would end up in error due to the device being blocked by another application.
$ aplay -D hw:X <audiofile.wav>
Play the audio file (wav) over the pipewire device.
$ aplay -D pipewire <audiofile.wav>
Play the audio file (wav) over the physical device. The Step 3 limitation applies here, too.
$ aplay -D sysdefault:CARD=USB <audiofile.wav>
Repeat the above step for all physical devices.
alsamixerand try setting the volume for a physical device use while playing some audio.
aplay -Llists physical and logical devices on the system.
- Audio can be played over different endpoints using the
- Volume levels can be adjusted for physical devices using
The device identifier might differ on your machine.
- This is valid for devices that support software volume adjusting. USB cards often use dedicated hardware knobs to do it and they cannot be controlled programmatically.