All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nugent <tony@growzone.com.au>
To: linux-sound@vger.kernel.org
Subject: Re: pci128 line-in help
Date: Thu, 28 Oct 1999 16:14:22 +0000	[thread overview]
Message-ID: <marc-linux-sound-94114189616065@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94098365529736@msgid-missing>

[why all of a sudden are so many of the messages here also going to a
linux audio list in canada?]

On Tue Oct 26 1999 at 17:19, est@hyperreal.org wrote:

> I can't seem to get my pci128 line-in to work.  This is using the
> (es1370) OSS driver distributed with the 2.2.7 kernel.  I've tried all
> the obvious mixer settings as well as all the private ioctl()s the
> driver has, checked my hardware, etc.  Can anyone think of anything I
> might be missing?

You need to configure the sound driver module when you load it.

%   /sbin/modinfo -p es1370
joystick int array (min = 1, max = 5), description "if 1 enables joystick interface (still need separate driver)"
lineout int array (min = 1, max = 5), description "if 1 the LINE input is converted to LINE out"
micbias int array (min = 1, max = 5), description "sets the +5V bias for an electret microphone"

(btw, default 2.2.12-20 kernel/modules from redhat6.1)

Either pass the relevant parameters on the insmod/modprobe command
line if you (re)load it manually, or put them into /etc/conf.modules

Check the /usr/src/linux/Documentation/sound/ directory for more
information about the parameters... there is a file there specifically
for the es1370 chip.

Cheers
Tony

      parent reply	other threads:[~1999-10-28 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27  0:19 pci128 line-in help est
1999-10-27  0:50 ` llornkcor
1999-10-27  2:03 ` David Olofson
1999-10-28 16:14 ` Tony Nugent [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-94114189616065@msgid-missing \
    --to=tony@growzone.com.au \
    --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 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.