From: Adam Mazurkiewicz <trzczy@gmail.com>
To: help-guix@gnu.org
Subject: Checking out if an ALSA driver for a sound card is installed
Date: Wed, 19 Jun 2019 13:21:10 +0000 [thread overview]
Message-ID: <CALStFoF0Jie=mk9y9HDeqQgcAvraS-sLCHMj2K8DC79GvjZjxg@mail.gmail.com> (raw)
My Sound Blaster PCI card is not working, so I have watched things
around ALSA drivers.
In fact I cannot state if ALSA is installed:
The M-x guix-default-services for %desktop-services is this:
(...)
agetty gnu/services/base.scm:1104:2
Provide console login using the `agetty' program.
alsa gnu/services/sound.scm:93:2
Configure low-level Linux sound support, ALSA.
avahi gnu/services/avahi.scm:145:4 Run
`avahi-daemon', a host and service discovery daemon that implements
the multicast DNS (mDNS) and DNS service discovery (DNS-SD) protocols.
Additionally, extend the C library's name service switch (NSS) with
support for `.local' host name resolution.
(...)
So ALSA is present in services, but aplay command doesn't work:
bash-4.4# aplay -l
bash: aplay: command not found
bash-4.4# find / -name aplay
/gnu/store/04g77pl6i6b8adj7pr1kbsz0qjar021z-alsa-utils-1.1.8/bin/aplay
find: ‘/run/user/1000/gvfs’: Permission denied
bash-4.4#
The card is visible here:
bash-4.4# lspci -nnk
(...)
01:00.0 Multimedia audio controller [0401]: Creative Labs
EMU10k2/CA0100/CA0102/CA10200 [Sound Blaster Audigy Series]
[1102:0004] (rev 04)
Subsystem: Creative Labs SB0240 Audigy 2 Platinum 6.1 [1102:1002]
01:00.1 Input device controller [0980]: Creative Labs SB Audigy Game
Port [1102:7003] (rev 04)
Subsystem: Creative Labs SB Audigy2 MIDI/Game Port [1102:0060]
Kernel driver in use: Emu10k1_gameport
Kernel modules: emu10k1_gp
01:00.2
(...)
How to check out if ALSA is installed or how to install it?
reply other threads:[~2019-06-19 13:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALStFoF0Jie=mk9y9HDeqQgcAvraS-sLCHMj2K8DC79GvjZjxg@mail.gmail.com' \
--to=trzczy@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.