From: Miles Lane <miles@amazon.com>
To: linux-sound@vger.kernel.org
Subject: Problem with cs4232.o
Date: Sun, 24 Jan 1999 23:44:14 +0000 [thread overview]
Message-ID: <marc-linux-sound-91722163016425@msgid-missing> (raw)
Hi,
I have a Crystal Audio CS4232 sound card in my Quantex H-1331 laptop.
I have built my own kernel using 2.2.0-pre7ac and the rest of the
OS is installed from the RPMs on rawhide.redhat.com. I also have
Gnome installed from the 0.99.2 files.
The problem is that when I start up X, if I try to use the sound card
a get a popping sound from the speakers and STDERR shows a messages
stating that the program couldn't access /dev/dsp. If I then run
"rmmod cs4232 ; probemod cs4232", the sound card works fine.
This leads me to think that my soundcard driver settings are fine.
However, I don't know why the driver needs to be unloaded and reloaded
before the driver can be accessed successfully. Perhaps it's a side
effect of loading Gnome, but I don't think so.
Let me know if you have suggestions.
Thanks!
Miles
next reply other threads:[~1999-01-24 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-24 23:44 Miles Lane [this message]
1999-01-25 1:13 ` Problem with cs4232.o Alan Cox
1999-01-26 3:06 ` Miles Lane
1999-01-31 8:52 ` Miles Lane
1999-01-31 17:38 ` Bill Nottingham
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=marc-linux-sound-91722163016425@msgid-missing \
--to=miles@amazon.com \
--cc=linux-sound@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