I assume that it can not find my nvidia drivers somehow. Minecraft works perfectly, so it seems to be just wine or steam that is making a fuss about it. Can someone give me some direction? I would sure love to play CS:GO on my gentoo I get the same output on both 1.4.1 and 1.5.6 of wine.

From my searching on google I have seen others fix very similar issues by installing a 32-bit driver. I thought that a 64 bit version would use a 32bit sub process within it when detecting a 32bit application, but I guess not. Also, I don't see a use flag for it either in the x11-drivers/nvidia-drivers-295.71 ebuid.

did you install emul-linux-x86-opengl? That is what provides 32-bit OpenGL.

And di you install Wine with 32-bit and/or 64-bit support flags?

I run 64-bit Gentoo, with Nvidia drivers, using 32-bit version of Wine (use flag) and emul-linux-x86-opengl and have no issues with steam (other than no font, but that is a wine issue with dwrite implementation being incomplete).

I would try a newer version of wine (1.5.9 and lower don't have the font issue, but launching newer wine with the -no-dwrite option fixes the font issue).

and this is my wine use flags are similar to yours, just no win64 (because I am lazy). I got opencl and gnutls now (didn't before, no effect on steam).

I have been running steam on wine for several versions of wine, currently on version 1.5.10. Version 1.5.11 crashes Skyrim for me.

I am running nvidia drivers version 304.43.

Oh, is your nvidia-drivers showing that the multilib flag is enabled? I just realized that it is what creates 32-bit libraries and not emul-linux-x86-opengl. I think. I am just too tired to think straigh. Sorry.[/code]

Because that is probably just misleading. I had that exact same error a few days ago, yet even while getting that error I could still start steam in WINE and even play CS:GO.
However, there is a solution for it, you just need to get "winbind". To do that you would have to emerge wine with the USE flag "samba" and emerge the package "samba" with the use flag "winbind".

This stopped the error for me, but it didn't appear to change anything at all. The frame rate actaully seemed lower when I had this built so I reemerged wine without it, the error came back but performance improved.

So hopefully this information at least helps you narrow down the problem. It seems to me that you are only having 1 real issue:

Because that is probably just misleading. I had that exact same error a few days ago, yet even while getting that error I could still start steam in WINE and even play CS:GO.
However, there is a solution for it, you just need to get "winbind". To do that you would have to emerge wine with the USE flag "samba" and emerge the package "samba" with the use flag "winbind".

I gave this a go. Here's the output after it and launching steam. It appears to be the same output, even with all the opengl errors.
http://pastebin.com/rVfL9BKG

Quote:

from a quick google search it seems maybe the game is trying to load a 32bit library and you only have a 64bit version.

Yeah, I've noticed that too before I posted here on this issue. However, It looks as though my nvidia drivers are fine and I have the opengl 32 bit libraries installed as I worked with Mistwolf to verify. Perhaps steam is looking for another 32 bit library then what I suspect. The plugin error you quoted above looks suspicious enough.

Quote:

Oh, is your nvidia-drivers showing that the multilib flag is enabled? I just realized that it is what creates 32-bit libraries and not emul-linux-x86-opengl. I think.

I get this output with the command, emerge -pv nvidia-drivers
[ebuild R ] x11-drivers/nvidia-drivers-295.71 USE="acpi (multilib) tools" 0 kB
It appears I do.

I would try a newer version of wine, but any version above 1.5.6 gives me the same blocks which I am a bit concerned about and don't really know how to deal with them. For example, when I run the command, emerge -pv =wine-1.5.7

After fooling around with this for a day or so, it seems a bit of a mess (well, that is because I don't know enough of the library matters, no doubt). A lot of time was wasted yesterday wondering why alsaequal was not working, at all! Today I noticed I had been trying with a .asoundrx instead of a .asoundrc... oopsies! In any case, it seemed a bit similar to an issue I had with libxcb. I had forgotten about the emul-linux packages, and thus, was very confused as to why a certain patch did not take effect if I built it with Portage, but it did if I built it manually 'outside' of Portage. Wine was using the libraries from app-emulation/emul-linux-x86-xlibs, or so I was told.

In any case, I tried building the media-plugins/caps-plugins (which is where your 64-bit caps.so should come from) manually, and while I was unsuccessful to tell Wine to use the build directory as I did with libxcb (LD_LIBRARY_PATH=path), I simply replaced the 64-bit caps.so temporarily with the 32-bit version I had compiled.
Wine did not complain about it any longer, but I would be unable to really test it since now I of course had mixed 32-bit libraries with 64-bit ones, which you shouldn't do, so the alsaequal would not work (or rather, I could not verify if it works or not, because the .alsaequal.bin would be the wrong length. I did, however, have audio in CS:GÖ nevertheless. ^^;

Of course all other audio applications would be broken now, heh!

Now, it's quite easy to tell Portage to build 32-bit code, but it is not as easy (to me at the time of writing) to solve the file collisions that become of it. You see, there already are 32-bit versions of files such as caps.so and libasound_module_pcm_equal.so that come from the package app-emulation/emul-linux-x86-soundlibs, similarly to libxcb.so, and right now, I don't have ideas on how to make alsaequal play nicely with them.

I was hoping that I could solve this issue for you, but I think I would have to mess around with the ebuild a lot more while not even being sure that it would be the right way of going at it at all. Right now I have no more time to spare for this particular adventure. Apologies. Perhaps I managed to at least make some sense and not be completely wrong about it. I did, however, manage to learn a thing or few myself, so it wasn't a complete loss! So I thank you.

Thank you!

You might want to report a bug at bugs.gentoo.org if nothing more comes up here.
Good luck~_________________Kind Regards,
~ The Noob Unlimited ~