On Wed, 2004-01-14 at 19:35, Austin Acton wrote: > On Wed, 2004-01-14 at 13:54, Rupert Heesom wrote: > > I don't know much about the difference between the ALSA sound system and > > the OSS sound system. I've tried running XMMS (OSS). It is happy > > playing an MP3 file if I set the output plugin to the OSS driver (not to > > "alternate /dev/dsp"). However when XMMS is playing an audio file, > > there is still NO SOUND from the speakers. > > Don't be insulted... run alsamixergui or gnome-alsa-mixer and make sure > that both main and pcm are unmuted. Please... do it for me.
I have no problem trying that. I have previously looked at the mixer settings. However this time when I tried loading such utils, I had problems! First of all, I didn't have either alsamixergui or gnome-alsa-mixer installed. Only alsamixer installed. I installed the alsamixergui frontend, but I'm having a load problem with alsamixer, an error msg on loading : "alsamixer: function snd_ctl_open failed for default" I looked this msg up on the web, came across a few other suggestions for that situation, such as: http://ccrma-mail.stanford.edu/pipermail/planetccrma/2003-January/000900.html Looking around further, I realise that alsa seems not to be running properly on my system at all! There is no "/proc/asound" either as directory or file. There is a startup daemon script /etc/init.d/alsa. I tried restarting it. All I got was a msg saying that ALSA was not loaded, no reloading msg. The kernel modules I have loaded are: Module Size Used by Tainted: PF emu10k1 62792 0 ac97_codec 12488 0 [emu10k1] sound 70644 0 [emu10k1] soundcore 6276 0 [emu10k1 sound] It occurs to me that the symptoms on this PC seem to point to the soundcard not responding to the drivers (no /proc file settings visible etc). I've just swapped another soundcard in. A lower-end Soundblaster with the Ensoniq chip. Although there's an error msg on bootup when the init scripts are trying to load the wrong driver, at leaste something better is showing up : /proc/es1371. I was surprised that harddrake didn't pick up the change in hardware and reconfigure the system as I expected it would. Alsa mixer software still have the same load problems: [EMAIL PROTECTED] proc]# amixer amixer: Mixer attach default error: No such file or directory [EMAIL PROTECTED] proc]# alsamixer alsamixer: function snd_ctl_open failed for default: No such file or directory [EMAIL PROTECTED] proc]# I see from others using Mandrake 9.1, that they've had to enable Alsa and possibly manually load the sound driver. (http://www.music.columbia.edu/pipermail/linux-audio-user/2003-August/005887.html) Well, I've been trying to enable Alsa but I don't think I'm successful yet! I've tried to establish which rpms packages comprises Alsa within MDK 9.1. What I have seen from the MDK control panel is that there isn't much under the Alsa packages that I haven't installed yet. This is all getting a bit confusing. Less and less seems to be working. I need to start digging myself out of my hole! If I can ensure that my Alsa setup is correct, perhaps those Alsa utils will work? -- Regards Rupert Heesom ================================================================== Looking for world-class toxin free products? -- --> personal care, food supplements, general household --> Largest range of products under one roof =================> www.worldclasswellness.org.uk <================ --> Highlighting <-- www.worldclasswellness.org.uk/furtherinfo.html?tag=drepstein --> Highlighting <-- ================================================================== ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
