Op donderdag 25 augustus 2005 19:12, schreef Raymond: > Alien wrote: > > anyway, i really need to do the latest tests, i have way too many adb > > failures lately. > > What do you means when you say "adb failures" ? ( any message in system > log ) found one: Aug 22 21:55:45 queen kernel: Vortex: vortex_fifo_setadbctrl fail after that, i have to restart alsa but this is only partly the problem, it's only lately that i see that error when there are problems, before i never saw anything in logs and it still had the same problem there is one thing though, i haven't gotten the error where snd-au8810 has 210 dependencies anymore. if i now have an error with sound, i only have to kill all appl using alsa, and restart alsa (when that dep error was there, i had to reboot to have sound + ps aux crashed the console and lotsa other things, applications using alsa had weird statusses etc...) > > it mostly happens, when watching a movie and gaim starts a little sound. > > > > i've determined that it's not likely to be the max available sounds, but > > more likely to be the weird scheduling of sounds at the same time > > > > i urge you people to chat more using some program that starts little > > sounds so, you have lots of short start and stops at the same time, maybe > > use gaim for ICQ and IRCing, that always gives me plenty of sounds... > > > > PS: i forgot the latest patch i had to try out. > > Don't forget the latest patch "Fixed missing spin_unlock" on CVS . i'll definately try that one sometime later tonight, it seems it might fit the problem > > I'll do one patch to try out, and hope it doesn't require me to reboot > > this machine... > > > > i'm using alsa CVS from some weeks ago, i think > > Although I can play multiple mono sound streams on device 2 on my au8830. > > I don't know why the connection routine of device 2 is disabled only on > au8810 driver. > > If you have any application using device 2 to playback (e.g. 3D demo in > vortexcontrol), wierd things may happen on au8810 since some of the > route and mixer of device 2 playback stream has not been assigned. that's odd ...