You are probably right, Roger. I can't check this solution now, but yesterday, I have seen that there is a conflict between the driver 0.5.12* and the 0.9.0* : if I do "/etc/init.d/alsa stop", the system give a wrong version of alsa. I have guessed that the both versions don't use the same directory, but I haven't time enough to check it. Now, I'm sure of it ! That's why I'm going to remove manually the stable drivers. I will tell you the end of the story ! Thanks for your great help. Xavier
En réponse à Roger E Critchlow Jr <[EMAIL PROTECTED]>: > Xavier ALLAMIGEON writes: > > Thanks for your answer. I have tried to use the latest drivers, libs > and > > utils, but I get errors with the utils "function snd_ctl_open failed > for > > default : Sound protocole is not compatible". What is the version of > your > > drivers ? (remember that I have a MDK8.1). > > Thank you > > "Sound protocol is not compatible" is the error generated when an > application compiled with libasound.so.2, from alsa-0.9, tries to talk > to an alsa-0.5 vintage driver. > > This can happen quite easily since the location of the alsa modules > moved and the naming conventions of the modules also changed. The > location change is a problem because the alsa-0.9 driver install > may not clean out the old alsa-0.5 modules. The naming change is a > problem because modules.conf may still be forcing an alsa-0.5 sound > driver to load. > > Look in /lib/modules for your system and see if you can find more than > one directory of alsa sound modules. One place they've installed is > misc/, another is kernel/sound/. They'll be named snd-*.o where ever > they installed. Clean out the older ones. > > Check your /etc/module.conf, if it refers to any snd-card-*, where * > is a hardware name and not a digit, then it's not using the most > recent naming conventions. See the alsa-drivers/INSTALL document. > > -- rec -- > _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
