From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001134]: alsa 1.0.9rc4 + intel 82801FB/.../ = No sound (Benq 52-101)
Date: Wed, 1 Jun 2005 16:58:32 +0200 [thread overview]
Message-ID: <2d625eb4db542fc5230e7d7c87cdf29a@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1134>
======================================================================
Reported By: liangalei
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 1134
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution: Fedora Core 3
Kernel Version: 2.6.11-1.14
======================================================================
Date Submitted: 05-28-2005 08:49 CEST
Last Modified: 06-01-2005 16:58 CEST
======================================================================
Summary: alsa 1.0.9rc4 + intel 82801FB/.../ = No sound (Benq
52-101)
Description:
My notebook is Benq 52-101, update FC3 to kernel 2.6.11-1.14_FC3
alsamixer report: Card=intel ICH6, chip=Conexant id 3 (Question, Conexant
just support modem's AC-97 or else provide whole sound ? )
alsaconf: can find "Intel Corp 82801FB/.../ ICH6 family AC'97 Audio", and
will contine to "Have a lot fun".
I have ever, update linux kernel from 2.6.9 to 2.6.11(yum update, no
recompiling), and alsa driver from 0.9.0/1.0.8/1.0.9rc3/4.
Recomipling ALsa driver/lib/oss/tools/util.., with drive, ever try
----- ./configure --with-cards=azx (error: no this card)
----- ./configure ; make; make install (no error report), not run
./snddevices
No sound ! So much days, so much test..... (if i915GM chipset + Conexant
chip...(see below lspci), will be powered by alsa-1.0.9rc4 ? --- if still
not, I will just wait for new alsa-driver.)
thanks
======================================================================
----------------------------------------------------------------------
liangalei - 05-30-05 03:29
----------------------------------------------------------------------
hinted by https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1078
I have a look at my /proc/asound, it looks like following, ----- Is it
strange? I see many "off" ---- but I cannot turn-ONs them, by either
alsamixer or aumix, because in alsamixer jack-bars, them can not be seen
!
[lal@lal ~]$ cat /proc/asound/card0/codec97#0/ac97#0-0
0-0/0: Conexant id 31
Revision : 0x00
Compat. Class : 0x00
Subsys. Vendor ID: 0x0000
Subsys. ID : 0x0000
Capabilities :
DAC resolution : 18-bit
ADC resolution : 18-bit
3D enhancement : No 3D Stereo Enhancement
Current setup
Mic gain : +20dB [+20dB]
POP path : pre 3D
Sim. stereo : off
3D enhancement : off
Loudness : off
Mono output : MIX
Mic select : Mic1
ADC/DAC loopback : off
Extended ID : codec=0 rev=2 AMAP LDAC SDAC CDAC DSA=0 SPDIF
Extended status : PRL SPCV LDAC SDAC CDAC SPDIF=10/11
SPDIF Control : Consumer PCM Category=0x2 Generation=1 Rate=48kHz
Extended modem ID: codec=0 LIN1
Modem status : PRA(GPIO) PRB(res) PRC(ADC1) PRD(DAC1) PRE(ADC2)
PRF(DAC2) PRG(HADC) PRH(HDAC)
Line1 rate : 48000Hz
[lal@lal ~]$
----------------------------------------------------------------------
tiwai - 06-01-05 16:58
----------------------------------------------------------------------
I suspect it's not a Conexant codec. The driver seems to fail detection of
the codec.
This kind of problems is often related with ACPI. Try to tune the ACPI
boot setting.
Issue History
Date Modified Username Field Change
======================================================================
05-28-05 08:49 liangalei New Issue
05-28-05 08:49 liangalei Distribution => Fedora Core 3
05-28-05 08:49 liangalei Kernel Version => 2.6.11-1.14
05-28-05 09:17 liangalei Note Added: 0004759
05-28-05 09:18 liangalei Issue Monitored: liangalei
05-30-05 03:29 liangalei Note Added: 0004795
06-01-05 16:58 tiwai Note Added: 0004863
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next reply other threads:[~2005-06-01 14:58 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 14:58 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 8:48 [ALSA - driver 0001134]: alsa 1.0.9rc4 + intel 82801FB/.../ = No sound (Benq 52-101) bugtrack
2006-06-30 2:06 bugtrack
2006-06-28 17:28 bugtrack
2006-06-28 17:15 bugtrack
2006-06-28 17:11 bugtrack
2006-06-28 16:47 bugtrack
2006-06-28 15:33 bugtrack
2006-06-28 14:41 bugtrack
2006-06-28 14:34 bugtrack
2006-06-28 14:03 bugtrack
2006-06-28 12:14 bugtrack
2006-06-14 3:19 bugtrack
2006-06-08 7:39 bugtrack
2006-06-07 22:14 bugtrack
2006-06-07 20:32 bugtrack
2006-06-07 20:24 bugtrack
2006-06-07 18:49 bugtrack
2006-06-07 18:47 bugtrack
2006-06-07 18:46 bugtrack
2006-06-07 8:49 bugtrack
2006-06-02 23:51 bugtrack
2006-06-02 19:34 bugtrack
2006-06-02 17:40 bugtrack
2006-06-02 17:29 bugtrack
2006-06-02 15:54 bugtrack
2006-06-02 15:37 bugtrack
2006-05-25 21:03 bugtrack
2006-05-19 6:07 bugtrack
2006-05-18 11:37 bugtrack
2006-05-18 10:45 bugtrack
2006-05-15 13:25 bugtrack
2006-05-15 12:57 bugtrack
2006-05-15 12:49 bugtrack
2006-05-15 12:15 bugtrack
2006-05-12 6:13 bugtrack
2006-05-11 16:25 bugtrack
2006-05-11 6:45 bugtrack
2006-05-11 6:42 bugtrack
2006-05-11 6:15 bugtrack
2006-05-10 16:34 bugtrack
2006-05-10 16:20 bugtrack
2006-05-10 16:03 bugtrack
2006-05-10 15:41 bugtrack
2006-05-10 15:25 bugtrack
2006-05-10 15:22 bugtrack
2006-05-10 15:19 bugtrack
2006-05-10 15:10 bugtrack
2006-05-10 13:58 bugtrack
2006-05-09 20:07 bugtrack
2006-05-09 18:34 bugtrack
2006-05-09 18:29 bugtrack
2006-05-09 18:28 bugtrack
2006-05-09 18:19 bugtrack
2006-05-09 18:17 bugtrack
2006-05-09 18:16 bugtrack
2006-05-09 17:50 bugtrack
2006-05-09 17:42 bugtrack
2006-05-09 17:39 bugtrack
2006-05-09 17:30 bugtrack
2006-05-09 17:28 bugtrack
2006-05-09 17:27 bugtrack
2006-05-09 17:21 bugtrack
2006-05-09 17:12 bugtrack
2006-05-09 17:11 bugtrack
2006-05-09 16:44 bugtrack
2006-05-09 16:33 bugtrack
2006-05-09 16:00 bugtrack
2006-05-09 15:57 bugtrack
2006-05-09 15:52 bugtrack
2006-05-09 15:49 bugtrack
2006-05-09 15:32 bugtrack
2006-05-09 15:29 bugtrack
2006-05-09 15:16 bugtrack
2006-05-09 14:40 bugtrack
2006-05-09 12:36 bugtrack
2006-04-18 7:35 bugtrack
2006-04-13 12:00 bugtrack
2006-04-12 14:21 bugtrack
2006-04-09 1:23 bugtrack
2006-04-07 11:05 bugtrack
2006-03-30 13:47 bugtrack
2006-03-25 9:51 bugtrack
2006-03-21 1:38 bugtrack
2006-03-17 11:35 bugtrack
2006-03-17 11:07 bugtrack
2006-03-17 3:10 bugtrack
2006-03-16 18:34 bugtrack
2006-03-16 14:04 bugtrack
2006-03-15 22:48 bugtrack
2006-03-15 11:18 bugtrack
2006-03-15 11:13 bugtrack
2006-03-15 10:53 bugtrack
2006-03-15 10:40 bugtrack
2006-03-15 5:39 bugtrack
2006-03-15 4:34 bugtrack
2006-03-03 7:29 bugtrack
2006-02-18 7:13 bugtrack
2006-02-18 1:05 bugtrack
2006-02-17 21:22 bugtrack
2005-11-29 5:03 bugtrack
2005-08-28 13:28 bugtrack
2005-06-24 1:18 bugtrack
2005-06-23 10:42 bugtrack
2005-06-02 8:42 bugtrack
2005-06-01 15:04 bugtrack
2005-05-30 1:29 bugtrack
2005-05-28 7:17 bugtrack
2005-05-28 6:49 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=2d625eb4db542fc5230e7d7c87cdf29a@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.