On Saturday 10 April 2004 08:28 am, et wrote: > hmmm, cause what I read,,,/etc/modprobe.conf is for a 2.4 kernel... > and /etc/modprobe.preload is the config for the 2.6 kernel > modules (2.4) == modprobe.preload (2.6) modules.conf (2.4) == modprobe.conf (2.6)
Be careful in 10.0, because to accomodate both kernels, it is set up to keep modules.conf and modprobe.conf in sync. This is done by a script called generate-modprobe.conf which generates a modprobe.conf from your modules.conf. This could cause problems if you hack your modprobe.conf to get something working without changing the modules.conf too. The next time something runs that triggers the script you changes will get overwritten. So, if you need to change something like a sound driver in modprobe.conf, change it in modules.conf also. > but I bet the problem is more along the lines of aRts -vs- alsa -vs- OSS. > have you set a timeout for aRts? alsa is a set of kernel module drivers for sound that replaces the deprecated OSS. aRTs is a sound server and will use whichever driver is active. If the problem is with arts, you will most likely experience it with both the alsa or oss drivers. -- /g
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
