public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hetfield <hetfield666@virgilio.it>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.x ALSA sound is pretty broken
Date: Fri, 18 Jun 2004 17:34:43 +0200	[thread overview]
Message-ID: <1087572882.1936.7.camel@blight.blight> (raw)
In-Reply-To: <s5hn031ndbl.wl@alsa2.suse.de>

Il ven, 2004-06-18 alle 16:35, Takashi Iwai ha scritto:
> At Fri, 18 Jun 2004 16:12:58 +0200,
> Hetfield wrote:
> > 
> > example: "beep"  when i execute beep i hear no sounds, neither from
> > speakers (audio card) 
> > nor from internal pc speaker.
> 
> Did you enable CONFIG_INPUT_PCSPKR?

sorry i can't find it! i searched whole sound system part of menuconfig
without finding nothing similar...

> 
> > in kde environment kconsole doesn't beep too.
> > mplayer seems to have some problem using the alsa output, giving strange messages.
> > (using oss emulation works good, with the only bad sound quality problem)
> 
> Then it's a mlayer specific problem.
> 

i suppose so too. i'll fill an mplayer bug.
however it seems that the problem is with IDE driver, when DMA is
enabled. Can the right team investigate for that?

thanks
> 
> Takashi
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

________________________________________________________________________
Hetfield
www.blight.tk


  reply	other threads:[~2004-06-18 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 14:03 [BUG] 2.6.x ALSA sound is pretty broken Hetfield
2004-06-18 14:12 ` Hetfield
2004-06-18 14:35   ` Takashi Iwai
2004-06-18 15:34     ` Hetfield [this message]
2004-06-21 18:27       ` Takashi Iwai
2004-06-18 15:57   ` Jeff Garzik
2004-06-18 14:20 ` Lenar Lõhmus
2004-06-18 15:23   ` Hetfield
2004-06-18 14:33 ` 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=1087572882.1936.7.camel@blight.blight \
    --to=hetfield666@virgilio.it \
    --cc=linux-kernel@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