At Thu, 29 Nov 2001 14:37:08 -0600, Lindsay Haisley wrote: > > ALSA is an absolute BEAR to install!! > > Is there any comprehensive documentation anywhere discussing the internals > which might be useful to someone trying to solve a problem such as the > follwoing? > > I have a Dell Latitude cPI laptop with 2 hard drives. Both of them have > Debian GNU/Linux unstable on them. The smaller of the two drives is nearly > maxed out and I'm trying to set up the 2nd drive so that it works properly. > > The internal sound card is Crystal cs4236. I found a config for this box > with this card on the Internet and set up my modules config file accordingly > on both drives. /etc/alsa/modutils/0.5 on the old drive is the same as > /etc/alsa/modutils/1.0 on the new drive. All modules load and sound works on > both drives, but only partially on the 2nd drive. > > On the original, smaller hard drive, the kmix and other mixers show a rather > excessive array of controls, the leftmost of which is a master volume. All > sound appears to work (although there are apparently other problems with the > CD so I can't check it explicitly). Notably, signals directed to /dev/dsp > work properly so I can play wav files, mp3 files and such. The tab on kmix > says CS4237B. The CD doesn't work for music, but this may (or may not) be > another matter. > > On the 2nd drive, I get a much smaller set of controls, with no master > volume control. The leftmost control is the Synth control and is mirrored > in the KDE panel single volume control, which is of no use at all. Worse > than this, I get no pcm sound at all, even though apparently signal is being > introduced to the system (aRTS meters show it when I play a wav file). The > microphone works, as does the CD player, so apparently there is _some_ > interface to the card which is working, although this may be only a hardware > interface. The kmix tab says "MIXER00". Maybe this happens because the control names are changed between ALSA 0.5 and 0.9. kmix supports only OSS (well it supports ALSA partly but it's next to useless), and the implementation of OSS mixer emulation has been changed, so it likely happens that not all controls are supported on ALSA 0.9 just because of their names. Well, this should be fixed on cs4236 driver..
My recommendation is: try alsamixer. > Apparently the config of the mixer is expressed via /dev/mixer or some other > inteface independent of KDE since I get the same control selection with > aumix from a vt. ditto. > The old drive has alsa version 0.5.10b, the new drive is using 0.9+0beta7-2. > Is this a difference between drivers? Is there a configuration to change > what's available on the mixer interface in 0.9? Is there something I can do > to get pcm sound to work on the 2nd drive? > > Is there any documentation w. regard to various parameters which can be set > in the modules.conf file which will control the various alsa modules? This has nothing to do with module configuration. Please try to set up via alsamixer. > From a user's perspective, alsa is a very complicated black box, and unless > I want to go digging around in the code there's no way to know what's going > on. I've done as much professional studio work as computer work, so I have > high standards as to how a sound control interface should work, and strong > expectations that it _should_ work :-) It should work as long as you use ALSA native app ;) ciao, Takashi _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
