From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0002116]: no sound in kernel 2.6.16-1-686
Date: Tue, 16 May 2006 23:48:31 +0200 [thread overview]
Message-ID: <59063833f51eeebd4c8ad6bb1989fa82@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2116>
======================================================================
Reported By: mramirez
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 2116
Category: speakertest
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 05-12-2006 01:07 CEST
Last Modified: 05-16-2006 23:48 CEST
======================================================================
Summary: no sound in kernel 2.6.16-1-686
Description:
I have updated my kernel from 2.6.15-1-486 to 2.6.16-1-686, and now the
sound not work.
I run alsaconf, but not solve the problem.
if i boot on kernel 2.6.15-1-486 the sound work. (only in this version)
somebody help me?
======================================================================
----------------------------------------------------------------------
rlrevell - 05-12-06 22:43
----------------------------------------------------------------------
Try raising the PCM and Front volume and make sure all controls are
unmuted.
Don't use kmix, it's terribly buggy. Test with alsamixer.
If it still does not work post the output of "amixer"
----------------------------------------------------------------------
rlrevell - 05-16-06 23:48
----------------------------------------------------------------------
Were you able to get this working?
Issue History
Date Modified Username Field Change
======================================================================
05-12-06 01:07 mramirez New Issue
05-12-06 16:07 tiwai Note Added: 0009777
05-12-06 18:34 mramirez Note Added: 0009785
05-12-06 18:37 tiwai Note Added: 0009787
05-12-06 20:30 mramirez Note Added: 0009790
05-12-06 20:34 tiwai Note Added: 0009791
05-12-06 21:29 mramirez Note Added: 0009792
05-12-06 21:35 mramirez Note Edited: 0009792
05-12-06 22:43 rlrevell Note Added: 0009793
05-16-06 23:48 rlrevell Note Added: 0009842
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-05-16 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 21:48 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 12:30 [ALSA - utils 0002116]: no sound in kernel 2.6.16-1-686 bugtrack
2006-05-12 20:43 bugtrack
2006-05-12 19:29 bugtrack
2006-05-12 18:34 bugtrack
2006-05-12 18:30 bugtrack
2006-05-12 16:37 bugtrack
2006-05-12 16:34 bugtrack
2006-05-12 14:07 bugtrack
2006-05-11 23:07 bugtrack
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=59063833f51eeebd4c8ad6bb1989fa82@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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.