All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Frans Ketelaars <ketelaars@wanadoo.nl>,
	alsa-user@lists.sourceforge.net,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-user] External input doesn't work
Date: Mon, 20 Dec 2004 19:21:50 +0100	[thread overview]
Message-ID: <s5hk6rcvni9.wl@alsa2.suse.de> (raw)
In-Reply-To: <1103360054.16168.9.camel@krustophenia.net>

At Sat, 18 Dec 2004 03:54:14 -0500,
Lee Revell wrote:
> 
> On Sat, 2004-12-18 at 09:32 +0100, Frans Ketelaars wrote:
> > The i810_audio module is an OSS module and interferes with ALSA.
> 
> This keeps coming up over and over.  Isn't there some way we can at
> least print an obvious warning if someone tries to load the OSS and ALSA
> module for the same device?

I guess this isn't the culprit.  On 2.6 kernels, the modules can stay
even if the probe fails because of PCI hotplug.  So, i810_audio can't
obscure snd-intel8x0 driver.   (Yes, there was a bug in i810_audio,
ignoring the error from request_* functions, but it was fixed
meanwhile.)

My wild guess is a mixer configuration problem as usual.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-20 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200412180017.39649.ham.weebers@hccnet.nl>
     [not found] ` <200412180932.11234.ketelaars@wanadoo.nl>
2004-12-18  8:54   ` External input doesn't work Lee Revell
2004-12-20 18:21     ` Takashi Iwai [this message]
2004-12-20 21:27       ` [Alsa-user] " Rick B
2004-12-21 10:40         ` Takashi Iwai

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=s5hk6rcvni9.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=ketelaars@wanadoo.nl \
    --cc=rlrevell@joe-job.com \
    /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.