From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Juergen Sawinski <juergen.sawinski@mpimf-heidelberg.mpg.de>
Cc: "linux-kernel@vger" <linux-kernel@vger.kernel.org>
Subject: Re: i810 sound broken...
Date: 05 Aug 2002 22:44:59 +0100 [thread overview]
Message-ID: <1028583899.18156.86.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <1028578861.1894.15.camel@voyager>
On Mon, 2002-08-05 at 21:21, Juergen Sawinski wrote:
> On my Intel D845GBV board (obviously ICH4) none of 2.4 nor alsa works.
> It's a production box, so I hestitate to try 2.5.
2.5 is older audio code than 2.4.19-ac
If your audio isnt working then a good starting point is to grab the
2.4.19-ac1 i810_audio (you can drop those files into 2.4.19 vanilla
fine)
1. Does the mixer work, can you play a CD, control the volume etc ?
If so that means we have an active codec and the AC97 bus is running
2. Do you get regular interrupts doing "yes oink >/dev/audio"
This is a good clue to whether the bus master engine is running. If it
is we should be getting regular interrupts (and if the audio works a
nasty squeak)
3. Does the audio speed test report about 48Khz (expected except on some
Dell laptops)
next prev parent reply other threads:[~2002-08-05 20:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 11:27 Thomas Munck Steenholdt
2002-08-05 12:54 ` Alan Cox
2002-08-05 13:47 ` venom
2002-08-05 15:28 ` Alan Cox
2002-08-05 18:38 ` Thomas Munck Steenholdt
2002-08-06 0:26 ` Jeff Chua
2002-08-07 15:05 ` Doug Ledford
2002-08-07 18:49 ` Juergen Sawinski
2002-08-08 20:47 ` Doug Ledford
2002-08-05 21:38 ` Alexander Hoogerhuis
2002-08-06 14:47 ` Alan Cox
2002-08-06 13:31 ` Alexander Hoogerhuis
2002-08-05 20:21 ` Juergen Sawinski
2002-08-05 21:44 ` Alan Cox [this message]
2002-08-06 7:24 Andris Pavenis
2002-08-08 8:37 Thomas Munck Steenholdt
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=1028583899.18156.86.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=juergen.sawinski@mpimf-heidelberg.mpg.de \
--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
all inboxes | Powered by JetHome®