public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zubaj <pzubaj@gaya.sk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-devel] Re: Brand-new notebook useless with Linux...
Date: Thu, 08 Sep 2005 22:41:54 +0200	[thread overview]
Message-ID: <1126212114.5010.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1126207905.12697.20.camel@mindpipe>

Conexant codec with ID 0x30 - this is AMC97 codec (audio + modem in one
codec) - maybe there is fight between sound and modem driver. On intel
this codec works ok - audio part. Modem part is not working and
snd-intel8x0m have to be in blacklist (otherways audio is not working)
- maybe same problem with ati.

Try to add snd-atiixp-modem to /etc/hotplug/blacklist

Peter Zubaj

On Thu, 2005-09-08 at 15:31 -0400, Lee Revell wrote:
> On Thu, 2005-09-08 at 15:19 -0400, Chuck Ebbert wrote:
> > In-Reply-To: <1125805091.14032.69.camel@mindpipe>
> > 
> > On Sat, 03 Sep 2005 at 23:38:10 -0400, Lee Revell wrote:
> > 
> > > On Sat, 2005-09-03 at 18:58 -0400, Chuck Ebbert wrote:
> > > > I just bought a new notebook.
> > > 
> > > I'd return it if I were you.
> > 
> >  What fun is that?  I have learned that HP/Compaq is hostile to Linux,
> > for one thing, which was interesting (my system is a Compaq Presario
> > V2312US.)
> > 
> >  Can you help me find out why my codec is unknown?  I gave up trying to
> > figure out how to get the codec ID and hacked the source to print it:
> > 
> > 
> > atiixp: codec 0 not available for modem
> > atiixp: no codec available
> > ALSA device list:
> >   #0 ATI IXP rev 2 with 0x43585430 at 0xd0003400, irq 177
> > 
> > 
> > So it's a Conexant codec with ID 0x30 on an atiixp.  OSS has some support
> > for this codec, apparently.
> 
> Wait, that sounds like the modem, not the AC97 audio codec.
> 
> You might be able to get the modem to work with the (proprietary)
> slmodem software modem, or something.  I wouldn't count on it though.
> 
> Does your sound work?
> 
> Lee
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 
> 
> Informacia od NOD32
> Tato sprava bola skontrolovana antivirovym systemom NOD32.
> [ Projekt gaya | www.gaya.sk ]


  reply	other threads:[~2005-09-08 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 19:19 Brand-new notebook useless with Linux Chuck Ebbert
2005-09-08 19:31 ` Lee Revell
2005-09-08 20:41   ` Peter Zubaj [this message]
2005-09-08 19:40 ` Lennart Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2005-09-09 18:09 Chuck Ebbert
2005-09-12  1:42 ` [Alsa-devel] " Lee Revell
2005-09-12 10:42   ` 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=1126212114.5010.6.camel@localhost.localdomain \
    --to=pzubaj@gaya.sk \
    --cc=76306.1226@compuserve.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox