From: Andrew Benton <b3nt@ukonline.co.uk>
To: linux-kernel@vger.kernel.org
Subject: ALSA problems with 2.6.18-rc3
Date: Tue, 08 Aug 2006 21:28:21 +0100 [thread overview]
Message-ID: <44D8F3E5.5020508@ukonline.co.uk> (raw)
Hello World,
I use the optical digital output from my computer and normally it works
well. However, with a 2.6.18-rc* kernel I have to use alsamixer to get
any output from it. I tweak the levels till it's working and use alsactl
store to save it. Normally, when I reboot it's enough to have a
bootscript run alsactl restore and it should work, but as I said, with
a 2.6.18-rc* kernel it doesn't. Every time I have to use alsamixer to
change the <IEC958 P> setting to A/D Conv and then back to AC-Link again
to get the diode to come on and start sending a signal to the amplifier.
And the problems don't stop there. At first it sounds fine but after a
few minutes it starts to develop a harsh, tinny, metallic, distorted
quality and it becomes unlistenable.
According to alsamixer v1.0.11, the card is an Intel ICH5 and the chip
is an Analog Devices AD1981B
Andy
next reply other threads:[~2006-08-08 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 20:28 Andrew Benton [this message]
2006-08-08 21:50 ` Lee Revell
2006-08-09 16:30 ` Andrew Benton
2006-08-09 16:35 ` Lee Revell
2006-08-09 16:51 ` [Alsa-devel] " Liam Girdwood
2006-08-09 18:17 ` Gene Heskett
2006-08-09 20:41 ` Lee Revell
2006-08-09 20:51 ` Gene Heskett
2006-08-09 20:57 ` Lee Revell
2006-08-09 21:22 ` Alistair John Strachan
2006-08-09 21:34 ` Lee Revell
2006-08-09 22:07 ` Alistair John Strachan
2006-08-09 22:11 ` Lee Revell
2006-08-09 22:28 ` Alistair John Strachan
2006-08-09 22:49 ` Lee Revell
2006-08-10 8:47 ` Takashi Iwai
2006-08-10 1:47 ` Gene Heskett
2006-08-10 13:13 ` [Alsa-devel] " Takashi Iwai
2006-08-09 10:58 ` 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=44D8F3E5.5020508@ukonline.co.uk \
--to=b3nt@ukonline.co.uk \
--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
Powered by JetHome