From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001274]: alc655: low volume
Date: Sun, 24 Jul 2005 22:19:01 +0200 [thread overview]
Message-ID: <62e8c0b5e55000fef4262f4f390a3a69@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1274>
======================================================================
Reported By: vitja
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1274
Category: PCI - atiixp
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution:
Kernel Version:
======================================================================
Date Submitted: 07-22-2005 10:46 CEST
Last Modified: 07-24-2005 22:19 CEST
======================================================================
Summary: alc655: low volume
Description:
I have ATI IXP400 sound in my notebook. codec is realtek's alc655. The
problem is I couldn't hear anything from internal speaker. When I plug
earphones in I hear very-very low music signal, so driver actually works
but. By the way under xp with realtek's drivers thats all right.. Is there
a way to see dump of ac97's registers under xp? May be XP driver uses some
proprietary features of alc655?
======================================================================
----------------------------------------------------------------------
vitja - 07-24-05 22:19
----------------------------------------------------------------------
temporarily solution:
I hop this will help
cat > /proc/asound/IXP/codec97#0/ac97#0-0+regs <<EOF
00 0000
02 0a0a
04 0000
06 8000
08 0000
0a 0000
0c 8008
0e 8008
10 8808
12 8808
14 0000
16 8808
18 8808
1a 0000
1c 8000
1e 0000
20 0400
22 0000
24 0000
26 000f
28 09c4
2a 05f0
2c bb80
2e bb80
30 bb80
32 bb80
34 0000
36 8080
38 8080
3a 2000
3c 0000
3e 0000
40 0000
42 0000
44 0000
46 0000
48 0000
4a 0000
4c 0000
4e 0000
50 0000
52 0000
54 0000
56 0000
58 0000
5a 0000
5c 0000
5e 0000
60 0000
62 0000
64 0808
66 0808
68 0aea
6a 0040
6c 0000
6e 0025
70 81e0
72 22e8
74 8000
76 0000
78 0007
7a 2090
7c 414c
7e 4760
EOF
Issue History
Date Modified Username Field Change
======================================================================
07-22-05 10:46 vitja New Issue
07-22-05 20:32 vitja File Added: codec
07-24-05 22:19 vitja Note Added: 0005560
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-07-24 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 20:19 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-08 18:18 [ALSA - driver 0001274]: alc655: low volume bugtrack
2006-01-06 19:59 bugtrack
2006-01-05 13:46 bugtrack
2006-01-04 16:02 bugtrack
2006-01-04 11:47 bugtrack
2006-01-04 11:24 bugtrack
2005-07-30 7:11 bugtrack
2005-07-29 16:01 bugtrack
2005-07-22 8:46 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=62e8c0b5e55000fef4262f4f390a3a69@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox