From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sound issue - can't use /dev/dsp
Date: Thu, 30 Oct 2008 13:01:39 -0400 [thread overview]
Message-ID: <e38d12ff0810301001m7d38d00fx8c138c29c26f6512@mail.gmail.com> (raw)
In-Reply-To: <20081030164103.GE18532@edespot.com>
On Thu, Oct 30, 2008 at 12:41 PM, Andrew MacKenzie <amackenz@edespot.com> wrote:
> My MythTV Gentoo box has recently started having issues recording sound.
> The TV tuner re-plays audio through the "mic" interface on my soundcard.
> It has worked for months, but now MythTV can't read anything from /dev/dsp.
>
> Any device that uses ALSA directly seems to work fine (like TVTime which
> plays TV with audio just fine) - only those that rely on /dev/dsp seem to
> have trouble. My simple test shows this:
>
> # cat /dev/dsp > /dev/null
> cat: /dev/dsp: Input/output error
>
> This was run as root. Perms are fine:
>
> crw-rw---- 1 root audio 14, 3 2008-10-03 08:56 /dev/dsp
>
> Myth user is in audio group (always has been).
>
> Has something changed in ALSA that I didn't catch? I don't see anything in
> my logs or dmesg that shows a problem. My /etc/asound.conf is as follows:
> pcm.nforce-hw {
> type hw
> card 0
> }
> pcm.!default {
> type plug
> slave.pcm "nforce"
> }
> pcm.nforce {
> type dmix
> ipc_key 1234
> ipc_perm 0660
> slave {
> pcm "hw:0,0"
> period_time 0
> period_size 1024
> buffer_size 4096
> #rate 44100
> rate 48000
> }
> }
> ctl.nforce-hw {
> type hw
> card 0
> }
>
>
> I have tried without this asound.conf and see the same issue.
Try using alsaconf as root.
--
Andrey Vul
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
next prev parent reply other threads:[~2008-10-30 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 16:41 [gentoo-user] Sound issue - can't use /dev/dsp Andrew MacKenzie
2008-10-30 17:01 ` Andrey Vul [this message]
2008-10-30 20:06 ` Andrew MacKenzie
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=e38d12ff0810301001m7d38d00fx8c138c29c26f6512@mail.gmail.com \
--to=andrey.vul@gmail.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox