From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: sound driver
Date: Mon, 6 Dec 2004 22:55:34 +0000 (UTC) [thread overview]
Message-ID: <loom.20041206T233307-573@post.gmane.org> (raw)
In-Reply-To: 41B4D42E.5050206@planet.nl
Holly Bostick <motub <at> planet.nl> writes:
> Yes they are---
>
> ALSA:
>
> CONFIG_SND_INTEL8X0:
>
> Say Y here to include support for the integrated AC97 sound
> device on motherboards with Intel/SiS/nVidia/AMD chipsets, or
> ALi chipsets using the M5455 Audio Controller. (There is a
> separate driver for ALi M5451 Audio Controllers.)
> To compile this driver as a module, choose M here: the module
> will be called snd-intel8x0.
Well after digging round the alsa-project.org site, I have to agree with you.
http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=
SiS&card=SiS+740.&chip=SI7012&module=intel8x0
I believe the chip number is SiS 7012 but it could be the 7013. Since it's a
(clevo D470W) portable, there is no mobo book....
Here's what I did for I2C bus
I2C support --->
I2C Hardware Bus support --->
<*> SiS 96x
And for the alsa (in case it matters) stuff:
Multimedia devices --->
Video For Linux --->
and Sound:
Sound --->
<M> Sound card support
Advanced Linux Sound Architecture --->
<M> Advanced Linux Sound Architecture
PCI devices --->
<M> Intel i8x0/MX440, SiS 7012; Ali 5455; NForce Audio; AMD768/8111
So for the
> OSS:
>
> CONFIG_SOUND_TRIDENT:
I think this OSS/trident as nothing on the system is trident stuff is
irrelevant
>
> This is kernel 2.6.10-rc2-bk7, and alsa-driver-1.0.7
>
> So you probably want to dig out your mobo manual and see if you can get
> more information on just what chipset is at work here.
do not get a mobo book with a portable
>
> Maybe you're just using the wrong drivers.
yep, that I was, now I need a little more help to see that I get
the modules loaded correctly.
>
> You might also want to check if you've enabled the I2C bus for your mobo
> chipset-- I'm not quite sure what it is, but if the kernel has gone to
> so much trouble to include some special support for my mobo's particular
> version of it in the kernel, I figure I should enable it . It might
> be important, and might be some dependency of the sound drivers (or
> other similar onboard components).
As mentioned above, I2C looks correct, according to your advice.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2004-12-06 22:56 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 2:34 [gentoo-user] sound driver James
2004-12-05 3:02 ` [gentoo-user] " james
2004-12-05 3:59 ` Glenn Enright
2004-12-05 5:25 ` James
2004-12-05 5:31 ` james
2004-12-05 6:21 ` Glenn Enright
2004-12-05 6:29 ` Glenn Enright
2004-12-06 13:29 ` james
2004-12-06 21:01 ` Glenn Enright
2004-12-06 13:33 ` james
2004-12-05 9:28 ` [gentoo-user] " Christoph Eckert
2004-12-05 16:55 ` Mike Noble
2004-12-05 17:21 ` Dave Erickson
2004-12-05 18:32 ` Christoph Eckert
2004-12-05 19:25 ` Bastian Balthazar Bux
2004-12-05 20:46 ` Christoph Eckert
2004-12-06 3:49 ` Kathy Wills
2004-12-06 3:55 ` Nick Rout
2004-12-06 4:07 ` Kathy Wills
2004-12-06 4:14 ` Nick Rout
2004-12-06 13:03 ` Kathy Wills
2004-12-06 13:13 ` Holly Bostick
2004-12-06 13:31 ` Kathy Wills
2004-12-06 13:53 ` Holly Bostick
2004-12-06 14:15 ` Tero Grundström
2004-12-06 14:30 ` Holly Bostick
2004-12-06 15:02 ` Tero Grundström
2004-12-06 15:58 ` Holly Bostick
2004-12-06 17:21 ` Peter Ruskin
2004-12-06 21:56 ` Holly Bostick
2004-12-06 17:55 ` Christoph Eckert
2004-12-06 14:40 ` [gentoo-user] " james
2004-12-06 14:37 ` James
2004-12-06 15:43 ` Holly Bostick
2004-12-06 17:24 ` James
2004-12-06 17:50 ` Christoph Eckert
2004-12-06 19:23 ` James
2004-12-06 19:37 ` Christoph Eckert
2004-12-06 20:56 ` James
2004-12-06 21:50 ` Holly Bostick
2004-12-06 22:55 ` James [this message]
2004-12-06 23:24 ` Christoph Eckert
2004-12-07 1:19 ` James
2004-12-07 17:46 ` Christoph Eckert
2004-12-07 1:31 ` James
2004-12-07 7:43 ` Dennis Robertson
2004-12-07 15:01 ` james
2004-12-07 17:47 ` Christoph Eckert
2004-12-06 23:20 ` James
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=loom.20041206T233307-573@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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