Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Charles E. Gelm" <gelmce@erinet.com>
To: linux-sound@vger.kernel.org
Subject: Re: Sound under 2.1.125
Date: Wed, 28 Oct 1998 14:47:29 +0000	[thread overview]
Message-ID: <marc-linux-sound-90957541501890@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90956439330548@msgid-missing>

Uh, linux-newbie ?

;-)
Chuck

Alexis DOMJAN wrote:
> 
> On Wed, 28 Oct 1998, Sangohn Christian wrote:
> 
> > I have Kernels 2.0.35smp and 2.1.125 with sound modules for the SB-AWE32.
> > With 2.0.35 there is no problem.
> > But I can't hear anything wtih 2.1.125. Kmix puts out:
> > "There is no mixer support for your system" although "ls -l /dev/mixer"
> > is there:
> > crw-rw-r--   1 root     audio     14,   0 Jul 21 02:45 /dev/mixer
> 
> The mixer device can exist; it doesn't mean that sound is supported.
> To know if sound modules were loaded correctly, then just type
> cat /proc/ioports and look if you see your sound blaster somewhere
> (at 0x220 for example).
> 
> Once you've compiled your sound card support using modules, when booting
> you can type something like: modprobe sound io=0x220 irq=5 dma=1 dma16=5
> then you must also load specific modules. I don't remember the names exactly,
> but for example modprobe opl3 will load opl3 module, just do the same for
> sb, awe32 support; ls /lib/modules/2.1.125/misc to see the sound modules.
> 
> > So how can I fix that?
> 
> Hope it helps you. If I'm wrong, hope that someone will correct me :-)
> 
> Cu!
> Alexis

-- 
Researching GELM

      parent reply	other threads:[~1998-10-28 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-28  6:27 Sound under 2.1.125 Sangohn Christian
1998-10-28  9:21 ` Alexis DOMJAN
1998-10-28 14:47 ` Charles E. Gelm [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=marc-linux-sound-90957541501890@msgid-missing \
    --to=gelmce@erinet.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