Hi Geoff and Frankie and other Alsa experts, Thanks Geoff for the suggestions you made (included below). On bootup I don't get any error messages now... no messages of any kind in fact, but the sound card shows up as correctly initialized and modules loaded in /proc/modules, /proc/interrupts and /proc/dma. I think from those /proc entries that all is loaded properly. However I stil can't get any sound to come from the speakers. I'm thinking that the channels are all muted (sys so in the alsa docs) be default. I found tht atthe aumix mixer that I used to use, no longer works withthe newer versions of alsa. The amixer from the alsa utils package doesn't seem to cooperate, or I'm just too dumb to understand something in the man pages. What mixer(s) are you folks using? I'm open for any suggestions at this point. The only sound I got fromthe the speakers is a "click" when rebooting the system. I assume that happens when the alsa driver gets unloaded? Thanks again for all your help and time. --terry You wrote: -=> Hi: -=> -=> Not sure what impact the alsa debian packages would have, since I've never -=> used them. You can use dpkg to check for installed packages. The best -=> command to use in this particular case, in my opinion, is: -=> -=> dpkg --get-selections |grep -i alsa -=> -=> This is a bit of a funny way to do it, but it allows you to be non-specific -=> with package names. -=> -=> I think I've found your problem, however. It is in /etc/modutils/alsa -=> which is read into /etc/modules.conf when you do an update-modules. There -=> are two lines in there that read: -=> -=> alias sound-service-0-3 snd-pcm1-oss -=> alias sound-service-0-12 snd-pcm1-oss -=> -=> You need to remove the 1 from both these lines, ie, so it says -=> snd-pcm-oss. There is also a line a bit further down that says: -=> -=> options snd-card-sbawe snd_index=1 snd_id=CARD_1 snd_port=0x220 snd_mpu_port=0x300 snd_awe_port=-1 snd_irq=5 snd_dma8=1 snd_dma16=5 snd_mic_agc=0 -=> -=> snd_index needs to be 0 not 1. Also, yours has snd_id set to CARD_1 and -=> mine is set to "SB16" (yes, in quotes), but I don't think this will matter -=> at all. -=> -=> So go edit /etc/modutils/alsa to fix these, then run update-modules and -=> that should do the trick. I think. -=> -=> Geoff. -=> -=> -=> -=> -- -=> Geoff Shang <gshang10 at scu.edu.au> -=> ICQ number 43634701 -=> -=> -=> _______________________________________________ -=> Speakup mailing list -=> Speakup at braille.uwo.ca -=> http://speech.braille.uwo.ca/mailman/listinfo/speakup -=> --terry Name: Terry D. Cudney Phone: (905)735-6127 E-mail: terry at wasagacottage.com WWW: www.wasagacottage.com Q: How many members of the U.S.S. Enterprise does it take to change a light bulb? A: Seven. Scotty has to report to Captain Kirk that the light bulb in the Engineering Section is getting dim, at which point Kirk will send Bones to pronounce the bulb dead (although he'll immediately claim that he's a doctor, not an electrician). Scotty, after checking around, realizes that they have no more new light bulbs, and complains that he "canna" see in the dark. Kirk will make an emergency stop at the next uncharted planet, Alpha Regula IV, to procure a light bulb from the natives, who, are friendly, but seem to be hiding something. Kirk, Spock, Bones, Yeoman Rand and two red shirt security officers beam down to the planet, where the two security officers are promply killed by the natives, and the rest of the landing party is captured. As something begins to develop between the Captain and Yeoman Rand, Scotty, back in orbit, is attacked by a Klingon destroyer and must warp out of orbit. Although badly outgunned, he cripples the Klingon and races back to the planet in order to rescue Kirk et. al. who have just saved the natives' from an awful fate and, as a reward, been given all lightbulbs they can carry. The new bulb is then inserted and the Enterprise continues on its five year mission.
