ok, so here's a good challenge for all the alsa experts out there. I've been playing around with my alsa configuration for quite a while now, so that I could achieve the holy grail of being able to play more than one sound simultaneously. I've upgraded my drivers, downgraded drivers, tried all sorts of configuration files, and I've finally gotten it to work . . . sort of. When I have no asound.conf, sounds work great, but when I try to boot my computer without it, I don't get anywhere. X will begin and I will get a startup sound, but I won't get the splash screen indicating that Gnome is starting. On the other hand, if I have a certain asound.conf (see below) , I won't get a startup sound, but Gnome will start.
I'm using the alsa drivers from Debian stable, except for libasound2(testing, I believe) and a couple mixers from testing. I also am using a self-compiled kernel, 2.6.14.3 with the included alsa kernel modules. I would downgrade the libasound2 to stable as well, but I've upgraded too many other things that depend on it to easily go back. The following is the asound.conf that lets me boot up:
Code:
oolave.pcm "dmixer"
}
pcm.dmixer {
type dmix
ipc_key 1025
slave {
pcm "hw:0,0"
period_time 0
period_size 1024
buffer_size 4096
periods 128
rate 44100
}
bindings {
0 0
1 1
}
}
This code seems like it would cause an error (especially the '}' with no '{' preceding it), but if I change it at all, Gnome will not load. I've tried deleting the '}', deleting everything before "pcm.dmixer", and deleting everything after the first line, but no matter what, Gnome will not load. I've even tried the sample asound.conf straight from the alsa website with the same result.
Can anyone figure out where my problem may lie, or better yet, how I can fix it?
thanks in advance . . . umichlinux
