Laurent wrote:

> You haven't say your version of alsa... - If it is alsa-0.5x, it's
> perhaps normal because sis7012 was added to the intel driver
> recently... - If you have alsa 0.9.0rc5 or newer, the driver name is
> snd-intel8x0 (just remove the -card-). - Or pehaps your scripts are
> buggy, and you can try modprobe snd-card-intel8x0 or modprobe
> snd-intel8x0
>
> The alsa driber can replace the i810_audio driver. You have just to
> have sound support enabled in your kernel (which often is build as
> soundcore module, automatically loaded by modprobe)

Thanks for the response!

Sorry, I should have included more technical details. I was using the 0.9.0rc5 drivers.

Part of my problem may have been that the Debian packages have the 0.9 drivers but the 0.5.10 version of alsa-utils (including alsaconf, I believe.) I didn't catch that mismatch until last night. Another part was group permissions, and a third was a driver module (the kernel's i810_audo module) that got stuck in the "initializing" state while I was switching back and forth and wouldn't unload properly.

In any case, last night I got things to the point that alsamixer and aplay would run. I was able to adjust the sound levels and unmute the various inputs and outputs, but no matter what I did I couldn't get any sound to come out. So, I finally wound up removing alsa and using what I'd learned from wrestling with it to get the kernel's sound driver working.

So sound is working, though not through alsa. I may take another look at the alsa stuff down the line, depending on what happens with Debian's packages and how closely it becomes integrated with the 2.6 kernel series.

In any case, thanks again for answering my question.

- Jeff



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to