Agreed, it made a slight behavior change, but otherwise still the same problem. I've submitted a bug report to Nouveau about it.

HOWEVER, I noticed something else was changed at this same time: LibELF. Since its the same version, I might dig out the DVD and install the old one again and see if anything happens. I don't see how since this all happens before any drives get mounted, but its the only other thing that was changed. (It doesn't help that, even after reading about it, I'm still not entirely sure what LibELF is used for: is it for messing with objects at run-time, at compile time, or what? And what do you do with those objects?)

I'm running 3.14.5, i.e. latest -current (including libelf updates) and having no issues at all... Also using Alien's multilib, etc... did you maybe forget or not update some of the compat32 packages? Working on -current, you may need to update these yourself using his massconvert32.sh script.

I do however use the nvidia binary drivers as Nouveau is just slightly less useful than a stick in the eye imho. Not sure if that is a difference or not given previous posts in this thread.

From what I can tell from what has been posted elsewhere by others (see post #10, above) and my own experiences, 16-bit ms-windows applications and some 32-bit ms-windows applications will not run with WINE with the 3.14.4 or 3.14.5 kernels. Re-install the 3.10.30 kernel and the same applications run just fine, as they have for all the years prior to the 3.14.4 kernel.

Just found this in the change log for the 3.14.6 kernel:

The 3.14 Kernel and WINE problem finally hit the "press,"

http://news.softpedia.com/news/Linux...s-447273.shtml

The 3.14.12 kernel does not solve the problem/regression. We'll have to wait for the 3.15.x kernel.

@cwizardone and all others who are interested:

Put the following in /etc/rc.d/rc.local:

This suggestion is per a thread in the WineHQ forums. Caveat: This only works in 3.14.6 and above. In short, if you are running the latest kernel on -current, this will fix the problem. It did for me.

That did the trick!
Thank you very much!
:hattip:

You are welcome. Always glad to help whenever I can. :)

Just curious, where did the OP see the original error message? I'm on 3.14.7 (14.1 upgraded, not brave enough for current :D) and I've never seen such a strange message for the nVidia driver.

nvidia 331.67 running great currently... I have an issue with a game in wine that I wrote off as an audio issue. If it turns out to be this well then, uh, holy ****!

Thanks for the insights :)

You can just upgrade the kernel bits (-generic/-huge, (depending on which you use), -modules, -source, -firmware, & -headers) without upgrading anything else. I do that all the time. It won't hurt anything.

EDIT: And, by the way, the audio issue might well be the lack of a program (OpenAL). You can find both versions (x86 & x86_64) at Alien BOB's repository.

Just as an addendum to this thread: kernel 3.16.x does not require this workaround, as WINE will work automatically. If you have this kernel running, you may remove the workaround from /etc/rc.d/rc.local.

The WINE problem has been fixed in the 3.14.16 kernel.
Thanks!

So it is good news that that kernel just landed in Slackware-current.

Eric

This is what I meant, i.e., the regression has been fixed in the latest kernel in -current.
From what I've read it didn't appear that the problem was fixed until the 3.15 kernel, so, perhaps, Mr. Volkerding was kind enough to patch the 3.14.16 kernel?
If so, Many Thanks!
:hattip: