[HOW TO] Get a SoundBlaster Audigy Rx to work in your system!

How to blacklist a sound card in Linux

Sometimes it may happen that you have a sound device that you do not use or then you are one of those people who dislike Pulseaudio and use Alsa instead. Especially with Alsa it gets very useful if you have only the sound device enabled which you actually use. Here are some notes about using Alsa instead of Pulseaudio in Linux.

  1. Start with the minimal installation. When you start with the bare minimum installation (installing only the basic system components during installation) you get the power to decide what comes into the system as it gets tweaked. Remember that in order to use Alsa you should only need the basic system package libasound2.

2. Do not install Gdm or Lightdm. They usually have some Pulseaudio dependencies in them. If you want to use a display manager use Slim instead (see here: Introducing Slim display manager | Techtimejourney) or use startx: (Log in to Linux desktop without a display manager: .xinitrc and startx in action | Techtimejourney). Generally I would recommend towards the usage of startx.

3. Ubuntu users. Currently it seems that Ubuntu has some problems with Pulseaudio and startx combination. If you decide to go with Alsa I certainly recommend remembering this. If you are using Ubuntu I would recommend using the LTS edition since there is less strange bugs that might come to your way while trying to get rid of Pulseaudio.

If you however do not want to remove Pulseaudio and you just want to blacklist a no good sound device then keep on reading as well. The blacklisting is still useful even if you use Pulseaudio. If you are an Alsa user then the following is more or less a must.

Blacklisting a sound device

Type as a root or a sudo inside a terminal:

nano /proc/asound/modules

Note: I prefer to use a text editor here but you can of course list the entries inside the file by just using a program called less or any other you prefer.

The command will open a text file with entries which might look like this:

0 snd_hda_intel

1 snd_ca106

2 snd_usb_audio

What we have here is a list of available sound devices 0 snd_hda_intel being the default one. Also do note that if you have a webcam it will show up on this file (in the above example: 2 snd_usb_audio ). You do not need to worry about the webcam since it does not have speaker qualities which in turn makes sure that it plays nicely with other devices.

In the above example we see two sound devices ca106 and hda_intel. As we want to use ca106 as a default sound provider we will blacklist the hda_intel out of the way. In a terminal as a root or a sudo:

nano /etc/modprobe.d/sound.blacklist.conf

Add the following entry to the file and then save and close it:

blacklist snd_hda_intel

The above entry tells your system to ignore snd_hda_intel module and thus prevent the loading of the Intel sound card which in turn makes the ca106 the default device.

Note: you can by all means choose a different name for you blacklist file than sound.blacklist.conf as long as it is formatted as something.blacklist.conf . When you remove the blacklist file or erase entries from it the system will return to its previous state. Remember to always reboot your computer after the blacklisting or erasing something from the blacklists in order to see the actual results.

Why would you want to use Alsa?

Alsa has (based on my experience) proven to be far less resource hungry than Pulseaudio when it is running. One reason of course is also the fact that Pulseaudio dependencies take a lot more hard drive space than Alsa’s. The previously mentioned might be significant if you are using an older computer and you need caution against resource over usage.

One thing that I have found to be very useful when using Alsa is that with Alsa you can actually get more control out from your sound devices. If you happen to use Skype, for example, you will get a standard device label without any adjustment chances on Skype sound setup when using Pulseaudio. With Alsa you can however adjust your devices, for example, in a way that your speaker system will give you the phone ringing sound when at the same time your headset might be working as a microphone.

This entry was posted in Tips and tricks and tagged blacklist a sound card linux, blacklist sound device linux, blacklist.conf example linux, how to use modprobe.d to blacklist a sound device linux, howto blacklist a sound device on linux, Linux: alsa vs pulseaudio, ubuntu and alsa, use alsa instead of pulseaudio linux, why choose alsa instead of pulseaudio, why choose alsa rather than pulseaudio linux on July 28, 2013.

[Acknowledgements to the link at the top of the paragraph above (I copied the contents of it as far too often useful pages/sites are disappearing at an alarming rate) - which is what I have used to get sound working in Zorin and today in linuxfx 10.06 free edition.]

3 Likes

Just thought an update would be good. Firstly I have tested this in Devuan 3.1.1. I did post somewhere about not getting sound out of all the speakers or a reversal of channels. Had the PC dismembered for a couple of months (by that I mean peripherals, including 5 Channel logitech speaker system). Sound is now coming out of all speakers! I have tested the various audio and multimedia applications and found that Audacious was only coming out of the mini double speaker atop my monitor. So have removed it. The applications that work are:

Alsaplayer
Enqueue in SM Player
MPV Media Player
Quod Libet (ironically rebranded version of Audactious - well same interface)
Parole Media Player
Rhythmbox
SM Player
Videos

Update - just played my latest purchase, LAU - BELIEVER album - sound coming out of all speakers in Videos and Rhythmbox on VM of Zorin 16.2!

Additional information that might prove useful if you are using a surround sound speaker system like myself:

I have the same system. Ironically, I now have this almost working as it should in PCLinuxOS Community Trinity Desktop Big Daddy 2024!

No Pulse Audio apart from Pavucontrol and Pavucontrol-qt, and apulse - but mainly ALSA! (Advanced Linux Sound Architecture).

[UPDATE: Spoke too soon - sound disappeared on my Trinity PCLinuxOS after cleaning CPU and applying fresh Noctua Thermal Paste and still sporadic reboots!

Do a full hardware mechanical checkup:-
Edge connectors clean and firmly pushed home.
Chips in sockets (if any) pushed firmly home.
PSU connections, wiring etc. Anything loose or intermittent connection.
PSU voltages.

Further update. Before I provide additional information, when I test Zorin 17 in live mode it produces sound but wrongly identifies the source as S/PDIF! I have had some issues with PCLinuxOS KDE (running Q4OS instead of Trinity Desktop of PCLinuxOS). Changed to PCIE Slot 1. PCLinuxOS has been pushing out Pipewire updates that did not help my situation, leaving me with sound coming from front centre speaker/s. The solution? Well first make sure you have most of the ALSA packages installed. Then to solve the issue I used Audacious!

Open Audacious and select Output from the Menu Bar, then Audio Settings:

image

Then click on the ALSA Settings (Output plugin default is Pipewire, followed by Pulse Audio - so I selected ALSA), then used these Settings for ALSA:
PCM device:

image

Then select this for Mixer Device:

image

And currently listening to my latest purchase in full surround sound! Yay!:

Favourite track, 2. Restored! No pun intended!