OK, I have yet again recompiled my kernel (2.4.17). This time, instead of building the oss solo1 module into the kernel, I opted to make it a module and also build alsa. Done and done. Now, when I bootup alsa starts, it is clearly running, starts without complaint. The soundcard is also identified. I look at the kcontrol information window on my soundcard and it has (paraphrased to the important stuff):
Sound driver 3.8.1a-980706 (ALSA 0.5.11 emulation mode) Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: ESS Solo1 rev0 irq5 Audio devices: NOT ENABLED IN CONFIG Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG And, OF COURSE, there is no sound. Sound. Is. Broken. Just like it was when I installed the default Mandrake 2.4.8 kernel with 8.1. Just like it was when I installed the update kernel 2.4.8. Just like it is now with 2.4.17. If I build the oss module for solo1 into the kernel, sound works but artsd crashes periodically with "CPU overload" messages. If I run "amixer" I get the brilliant message: The ALSA sound driver was not detected in this system. WRONG! The driver IS installed/running. Look here: [root@d152-159 etc]# /etc/init.d/alsa start ALSA driver (version 0.5.11) is already running. CLEARLY the driver is installed/running on the system. I also see the "NOT ENABLED IN CONFIG" statements above. What does that mean? It certainly IS enabled in the kernel config if THAT is what it is referring to. I cannot run alsamixer because it complains about "no mixer found" (I did run snddevices so all the /dev devices do exist). I. Want. Sound. How do I do it? What is the deal here? All the links/howtos referring to an ess solo and alsa are pathetically dated or no longer available (the module that once was called "snd-esssolo1" no longer exists as such and is "snd-1938" instead). Finally, my /var/log/messages file contains: Feb 5 16:37:55 d152-159 modprobe: modprobe: Can't locate module sound-slot-1 Feb 5 16:37:55 d152-159 modprobe: modprobe: Can't locate module sound-service-1-0 Feb 5 16:37:57 d152-159 modprobe: modprobe: Can't locate module sound-service-0-3 Feb 5 16:37:58 d152-159 last message repeated 2 times Feb 5 16:38:41 d152-159 modprobe: modprobe: Can't locate module sound-slot-1 Feb 5 16:38:41 d152-159 modprobe: modprobe: Can't locate module sound-service-1-0 Feb 5 16:38:41 d152-159 modprobe: modprobe: Can't locate module sound-slot-1 Feb 5 16:38:41 d152-159 modprobe: modprobe: Can't locate module sound-service-1-0 Feb 5 16:39:08 d152-159 modprobe: modprobe: Can't locate module sound-service-0-6 What is THIS? None of these are listed in modules.conf so I am not sure why it is looking for tem anyway. I have gone back and added entries addressing them but it does nothing, plus I shouldn't have to fill modules.conf with nonsense entries just to shutup these false error messages. Anyone have wisdom to impart? Anyone anywhere have a solo1 card actually functioning with a modern kernel and alsa? praedor
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
