All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Josh Green <josh@resonance.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Intel Azalia problems
Date: Wed, 13 Apr 2005 16:33:28 +0200	[thread overview]
Message-ID: <s5hll7mg30n.wl@alsa2.suse.de> (raw)
In-Reply-To: <1113394027.16526.3.camel@SillyPuddy.localdomain>

Hi Josh,

At Wed, 13 Apr 2005 05:07:07 -0700,
Josh Green wrote:
> 
> Hello, I recently purchased a new laptop which has an Intel Azalia sound
> interface.  I noticed that this is a pretty recent addition to the ALSA
> drivers.  Although it seems to be basically working, I'm having a couple
> problems.
> 
> The first problem has to do with the headphone jack, which on this
> laptop is an SPDIF/output combo jack. I can hear output on the built in
> speakers (after un-muting and turning up the "Front" level), but when I
> plug in headphones I don't hear anything (despite the fact that the
> "Headphone" mixer is turned up and unmuted).

Which HDA codec?  Please attach /proc/asound/card0/codec#*/* file.
(I guess it's CM9880, though..)
Anyway, try the latest CVS version.  Some improvement has been done
since rc2.

> The other problem is with certain applications which use oss.  Quake3
> for example prints the following in the terminal it is started from:
> 
> ------- sound initialization -------
> Could not mmap dma buffer PROT_WRITE|PROT_READ
> trying mmap PROT_WRITE (with associated better compatibility / less
> performance code)
> /dev/dsp: Input/output error
> Could not mmap /dev/dsp
> ------------------------------------

If your codec is CM9880, it supports only 48/96/192kHz while quake
prefers 44.1kHz.  This conflict can't be solved in the OSS mmap mode.

Try to tune via oss proc file as described in
Documentation/OSS-Emulation.txt.


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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-04-13 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 12:07 Intel Azalia problems Josh Green
2005-04-13 14:33 ` Takashi Iwai [this message]
2005-04-15  8:40   ` Josh Green
2005-04-15 12:12   ` Intel Azalia problems (some progress) Josh Green
2005-04-15 12:41     ` Takashi Iwai
2005-04-15 19:49       ` Josh Green
2005-04-19 12:50         ` Takashi Iwai
2005-04-15 22:15       ` Josh Green
2005-04-19 12:11         ` Takashi Iwai
2005-04-19 12:18           ` 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=s5hll7mg30n.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=josh@resonance.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.