From: Bob Nielsen <nielsen@oz.net>
To: Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: Looking for soundmodem info
Date: Fri, 28 Jan 2005 21:20:58 -0800 [thread overview]
Message-ID: <20050129052058.GB12792@n7xy.net> (raw)
In-Reply-To: <200501281611.04327.budr@netride.net>
On Fri, Jan 28, 2005 at 04:11:03PM -0600, Bud Rogers wrote:
> On Thursday 27 January 2005 22:22, Jeff Camp wrote:
> > Thanks for the info, Bob. I spent some time scouring the internet
> > this morning looking for soundmodem info. I downloaded
> > soundmodem-0.9-1.i386.rpm and installed it, but now I'm getting the
> > following error message when I try to start it up:
> >
> > [root@n0wjp ax25]# soundmodem -v 9
> > sm[1855]: x86 CPU capability 0383f9ff, MMX enabled
> > sm[1855]: mkiss: ifname sm0 mtu 256 hwaddr N0WJP-15 ipaddr 10.0.0.1
> > netmask 255.255.255.0 broadcast 10.0.0.255
> > sm[1855]: audio: starting "/dev/dsp"
> > sm[1855]: audio: Error, cannot open "/dev/dsp"
> > sm[1855]: cannot start audio
> > [root@n0wjp ax25]#
> >
> >
> > /dev/dsp exists. The sound card is a sound blaster compatible.
> > Anyone have an idea what these error mean? I'm not sure exactly
> > where to start on this one.
>
> Check the permissions on /dev/dsp. On my system they look like this:
>
> budr$ ls -l /dev/dsp
> crw-rw---- 1 root audio 14, 3 Jun 19 2003 /dev/dsp
> budr$
>
> I had to add myself to the audio group in /etc/group before I could
> use /dev/dsp.
>
> HTH es 73,
>
> Bud Rogers <budr@netride.net> KD5SZ
>
Also check that the soundcard driver is either compiled-in or loaded as
a module.
73,
Bob, N7XY
prev parent reply other threads:[~2005-01-29 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 1:03 Looking for soundmodem info Jeff Camp
2005-01-27 1:45 ` Bob Nielsen
2005-01-28 4:22 ` Jeff Camp
2005-01-28 22:11 ` Bud Rogers
2005-01-29 5:20 ` Bob Nielsen [this message]
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=20050129052058.GB12792@n7xy.net \
--to=nielsen@oz.net \
--cc=linux-hams@vger.kernel.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