Well, I got fed up with 5.0 so I just downgraded to 4.5 and sound works just fine again. 5.0 just does not work at all with sound in Linux. I tried it on my other 2 boxes and those had the same problem. One is a FC3 box, the other is Debian. All of them had 4.5 with working sound. I upgraded them all to 5, they lost sound of coarse. Tried the artsdsp, esdsp, vmwarearts and vmwareesd and none of them worked at all. I dont think 5.0 was a step up in progress for VMWare. Seems to me that they've gone backwards. I'm just going to stick with 4.5 until someone can actually confirm that they have sound working in 5 and can explain how to get it running.
Richard Fish wrote: >I can only speak to artsd, which if you have configured to use ALSA, >will not use /dev/dsp at all. /dev/dsp is the (obsolete) OSS API, so an >application using ALSA will not use it at all. esd should be similar. > >FYI, the wrappers work by overloading the file operation functions such >as open(), read(), write(), close(), etc. When the replacement function >in the wrapper sees an attempt to open "/dev/dsp", it instead opens the >appropriate sound library/server. So it doesn't matter whether you have >/dev/dsp or not if you are using a wrapper. > >The current artsdsp and esddsp will not work (at least on a 32-bit >system) with VMWare, because VMWare is a large-file aware application >and thus uses open64(), read64(), write64(), etc.. That is why you need >vmwaredsp. > >You may want to turn on debugging in vmwaredsp: > >1. Change "#define VMDSP_DEBUG (0)" to "#define VMDSP_DEBUG (1)" in >vmdsp.c, and rebuild/re-install vmwaredsp. >2. Modify the startup script vmwarearts (or vmwareesd) to add >"VMDSP_DEBUG=1" to the command line. > >When you run VMWare after these steps it should create a /tmp/vmdsp.log >file with some info about what the wrapper is doing. > >-Richard > > > -- [email protected] mailing list
