Contents 1 Getting ALSA to work 1.1 Make your audio card the default ALSA card 1.2 Disable PC Speaker "audio card" 1.3 Other hardware specific problems 1.4 Fixing sound in KDE (is this now obsolete? 2011/08)' 1.5 Enabling PulseAudio 1.6 Using JACK with PulseAudio 1.6.1 Troubleshooting JACK and PulseAudio

edit Getting ALSA to work

• on a console fire up alsamixer

 alsamixer

• you see plenty of vertical bars?
  • you should be okay

• you see very few vertical bars and the sound card (top-left) is something like "PC Speaker"?
  • hit the 'S' key, you should be able to switch to the "real" audio card (if not your audio card is likely to not being supported yet).
  • when the real audio card is selected you should be viewing the "plenty vertical bars" thing.
    • first thing to do is to disable pc speaker (kernel module "snd-pcsp", see below.

edit Make your audio card the default ALSA card

Sometimes the pc-speaker is the default audio card for ALSA. You can make your real sound card default instead. For example, if your sound card is "hda-intel" then add

  boot.extraModprobeConfig = ''
    options snd slots=snd-hda-intel
  '';

to your /etc/nixos/configuration.nix.

Alternatively you can ...

edit Disable PC Speaker "audio card"

edit /etc/nixos/configuration.nix and add "snd_pcsp" to boot.blacklistedKernelModules option:

 boot.blacklistedKernelModules = [ "snd_pcsp" ];

Now reboot and retry from the beginning (i.e. check that your real card is shown by alsamixer without using the 'S' key).

edit Other hardware specific problems

Some hardware specific problems can be resolved by adjusting the options for the sound module. For example, the microphone may be stuck on an unusably low volume. First you should be sure that you have already checked the settings in alsamixer to make sure nothing is muted, and also any physical buttons on your computer (I have twice overlooked the mute button on laptops!).

You should be able to look up the available options for model in HD-Audio-Models.txt. You can try them out interactively as follows:

1. Close any applications using the sound card
   1. See if any applications are using the sound card

      $ lsof /dev/snd/*

      COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

      pulseaudi 14080 goibhniu 30u CHR 116,7 0t0 5169 /dev/snd/controlC0

      pulseaudi 14080 goibhniu 37u CHR 116,7 0t0 5169 /dev/snd/controlC0

   2. Kill them

      for any process apart from pulseaudio you could just do:

      $ kill -9 14080

      but in the case of pulseaudio you have to prevent it from respawning itself automatically

      $ mkdir -P ~/.pulse && echo "autospawn=no" >> ~/.pulse/client.conf

      you can then stop pulseaudio with:

      $ pulseaudio -k # or kill it by process id

2. Unload the snd-hda-intel module

   rmmod snd-hda-intel

3. Find your model

   grep Codec /proc/asound/card0/codec*

4. Look up the model options for your card
5. Try each one

   modprobe snd-hda-intel model=3stack-6ch

6. Test if this has fixed your problem (tip: aplay and arecord are alsa based command line tools you can use to quickly check)
7. Repeat until you have exhausted all the options or have fixed your problem
8. TIDY UP!

   Don't forget to re-enable pulse autospawning by changing "autospawn=no" to "autospawn=yes" in ~/.pulse/client.conf

Once you have found a setting that works, you can add it to your configuration file:

  boot.extraModprobeConfig = ''
    options snd-hda-intel model=YOUR_MODEL 
  '';

Much of this is taken from https://help.ubuntu.com/community/HdaIntelSoundHowto which also has additional tips.

edit Fixing sound in KDE (is this now obsolete? 2011/08)'

(alsamixer shows my audio card by default, but i get no sound in KDE)

• be sure to explicitly install pkgs.kde44.phonon in /etc/nixos/configuration.nix (environment.kdePackages option) or via nix-env -i

After this step you should be seeing xine and gstreamer backends in the systemsettings / Computer Administration / Multimedia 's Backends tab.

• If you still see Pulseaudio as the only option in the main tab of systemsettings / Computer Administration / Multimedia, do the following:

 $ rm -rf ~/.pulse/*
 $ killall5 -9 pulseaudio

• Log out of kde and re-login

Now you should be able to select your audio card, default hw0,0 etc as your audio device in systemsettings / Computer Administration / Multimedia

Test the audio and enjoy the relaxing KDE's arpeggio.

edit Enabling PulseAudio

In your config file:

hardware.pulseaudio.enable = true

You can check if everything works by using pavucontrol to see the audio streams and to make sure that PulseAudio detects your audio hardware.

You may need to add your users to the audio group:

$usermod -a -G audio myusername

If a user is not a member the audio group only a dummy device will appear in pavucontrol.

The following command should only show that pulseaudio (and nothing else) is using the sound devices, if you see something like "plugin-container" in the COMMAND column then something is definitely not right, perhaps you have a local ~/.asoundrc which overrides the global alsa settings?.

  $ lsof /dev/snd/*
  COMMAND     PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  pulseaudi 14080 goibhniu   30u   CHR  116,7      0t0 5169 /dev/snd/controlC0
  pulseaudi 14080 goibhniu   37u   CHR  116,7      0t0 5169 /dev/snd/controlC0

edit Using JACK with PulseAudio

Jack Audio Connection Kit is used by most of the serious audio applications on Linux. It provides real-time, low latency connections for both audio and MIDI data between applications that implement its API. NixOS uses the dbus version of JACK2 (jackdbus). This can be used together with pulseaudio with a little configuration. The result is that you don't have to manually hunt down applications which are using the sound device and kill them before starting JACK. You can also continue to use non-JACK aware applications (e.g. flash) at the same time as using JACK applications (e.g. Ardour).

1. Enable JACK support

   In your configuration file:

   hardware.pulseaudio.package = pkgs.pulseaudio.override { jackaudioSupport = true; };

2. Ensure that the JACK enabled pulseaudio is being used

   ~/.pulse/client.conf

   daemon-binary=/var/run/current-system/sw/bin/pulseaudio

3. Configure QjackCtl
   1. Enable jackdbus

      Setup -> Settings -> Server Path: jackdbus

      

      Setup -> Misc -> Enable D-Bus interface: check

      

   2. Load the jack modules for pulseaudio after starting jackdbus

      Setup -> Settings -> Options -> Execute script after Startup: check

      pactl load-module module-jack-sink channels=2; pactl load-module module-jack-source channels=2; pacmd set-default-sink jack_out

      Setup -> Settings -> Options -> Execute script on Shutdown: check

      pactl unload-module `pactl list|grep -A 3 jack-source|tail -1|awk '{ print $NF }'`;pactl unload-module `pactl list|grep -A 3 jack-sink|tail -1|awk '{ print $NF }'`

      

You should now be able to start JACK with QjackCtl, you will notice a new playback and capture device in your sound mixer along with your normal devices.

edit Troubleshooting JACK and PulseAudio

$ pactl load-module module-jack-sink channels=2
Failure: Module initalization failed

Check if you have previous settings in ~/.config/jack/conf.xml. Try renaming this file and running the pactl command again.

Otherwise, you may get further info by disabling PulseAudio respawning (see above) and starting it in verbose mode:

$ pulseaudio -vvv

• About us