From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.5.6x Sound frustration
Date: Fri, 25 Apr 2003 17:43:50 -0400 [thread overview]
Message-ID: <3EA9AC16.4070903@coyotegulch.com> (raw)
The 2.5.66 kernel loads the ALSA sound drivers for my Intel i8x0
on-board sound, but no sound files make any... well, *sound.*
Note that, other than sound, the machine is performing flawlessly.
I've enabled the ALSA drivers, with (and for one etst, without) OSS
emulation, integrated into the kernel (no modules).
I hear a pop while the OS is loading; the log states:
Apr 25 17:06:18 Tycho kernel: intel8x0: clocking to 41158
Apr 25 17:06:18 Tycho kernel: ALSA device list:
Apr 25 17:06:18 Tycho kernel: #0: Intel 82801BA-ICH2 at 0xe800, irq 17
Yes, I'm using the latest ALSA tools.
Yes, I've used a mixer (several, actually) to make sure nothing is muted
and that all volumes are maximized.
Yes, I have the speakers turned on, plugged in, and connected to the
proper connector on the motherboard (an Intel D850EMV2). I've even tried
different speakers, jacks, and cables. The speakers work fine when
attached to a Wintel system, BTW.
I've tried running several different "sound" apps, along with directly
sending sounds to various devices -- and my reward is silence.
This is the first Linux system on which I've wanted the sound working...
I'm willing to admit I may be doing something stupid -- please be gentle! ;)
..Scott
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
next reply other threads:[~2003-04-25 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 21:43 Scott Robert Ladd [this message]
2003-04-26 3:46 ` 2.5.6x Sound frustration David van Hoose
2003-04-28 14:00 ` Takashi Iwai
2003-04-28 15:33 ` Scott Robert Ladd
2003-04-28 15:42 ` Scott Robert Ladd
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=3EA9AC16.4070903@coyotegulch.com \
--to=coyote@coyotegulch.com \
--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