The 337.19 (beta) installs without error, but WINE does not work.

The 331.67 driver repeatedly issued this error,


during installation, but was bootable. WINE also does not work
with this driver.

The 331.49 and 325.15 versions of the driver would not build. Period.

The 304.121 driver installed without error, but WINE would not work.

Following up:
WINE has worked with previous kernels and Nvidia drivers and as recently as a few hours ago with the 3.10.30 kernel and the 325.15 Nvidia driver.
Now, with the 3.14.4 kernel and the Nvidia 337.19 driver this error is reported when trying to start WINE,

is your system working otherwise?

the last error message says nothing about nvidia or even graphics.

shouldn't you post to http://forum.winehq.org/ ?

Seems to be a known issue with kernels >= 3.14.3 : https://lkml.org/lkml/2014/5/7/145
I'll try to run Wine at home tonight and see what happens.

Eric

@ondoho,
Yes, other than that, the system is working fine.

@Alien Bob,
It appears to have something to do with 16-bit vs 32-bit. There are two versions of the same program on the CD. In one directory, labeled, win, there is the 16-bit version and in the directory labeled, win32 is, of course, the 32-bit version. The 16-bit will not run. The 32-bit version will run off of the CD, but since the setup program is 16-bit I cannot install the program to the hard disk.

Edit in: Just read the post at the link in your message above. Apparently this problem is also effecting some 32-bit win programs.
Just another day in paradise.

Edit in: Apparently wine-pipelight is also affected.

Just re-installed the 3.10.30 kernel and the Nvidia 325.15 driver and things have returned to what passes for normal around here.

We'll try again with the next kernel "upgrade."

I tried the SilverLight test page http://bubblemark.com/silverlight2.html and watched a bit of television in the Widevine plugin, both are still working just fine with the 3.14.4 kernel in am running on this slackware64-current box.

Eric

By disabling the plug-ins and un-installing pipelight and then re-installing and re-enabling, I was able to get them to work with the 3.14.4 kernel.

I hope "they" fix the WINE problems as suggested by Mr. Torvalds.

cwizardone, if you are the C. Wizard who is posting on my blog, you seem to have an installation which has been mangled (or just customized) so much that nothing works as advertised any longer. In this wine case too, I did not experience these issues you describe, and they have nothing to do with KDE4 even!


Eric

Some 32-bit ms-windows applications will work in WINE with the 3.14.4 kernel, but 16-bit ms-windows apps will not.

As pointed out via the link in your message, #4, above,


As it is a kernel problem, you are correct, KDE has nothing to do with it.

And, just for the record, this installation, from scratch, is almost brand new. The only thing added are your multilib files, java files, wine-pipelight, etc. In fact, everything added after the new complete installation were from either -current or your repositories.

I was referring to your "Edit in: Apparently wine-pipelight is also affected". But if only 16-bit Windows applications are affected, that will not influence the pipelight plugins, at least that is my observation.
In your fresh installation, do you retain your original homedirectory or do you start your user account from scratch (i.e. no old data in .kde , .local , .config and all those other dot directories)?

I was not trying to mock you. In all honesty, I am trying to wrap my head around the completely opposite user experience you describe, compared to my own observations and those of some of my friends. I just can not understand what it is that messes up your computer.

Eric

Mr. Joachim, as quoted in post #10, seems to think some 32-bit apps are also affected.

"From scratch" means a freshly formated partition.

I run 32 bit -current. When I started to read the forums regarding the new kernel and Nvidia/Wine I got nervous. I use wine primarily to run some old games from the past I still occasionally enjoy, the original Unreal series. When I got to the bottom of this thread it seemed I might be safe! Did slackpkg upgrade-all
and reinstalled Nvidia 331.67. Wine working flawlessly for me. Whew...!

I can't speak for anyone else, but this isn't just Wine or other user programs: Since upgrading this afternoon from 3.14.3 to 3.14.4, Nouveau is no longer working for me. There seems to be some race condition in its initial load during boot where it fires up the framebuffer: in 5 boots on my Acer Aspire laptop since the upgrade, I've got twice with no backlight, twice with backlight but nothing being displayed, and only once with a normal boot and display where I was able to start X and XFCE. Looking at the X server logs I could see nothing special; I didn't think to look in the kernel logs at the time, and now I can't (the normal boot was the third).

The way I see it, the only way out after seeing all the problems everyone else is having is, if I can, blacklist Nouveau from LILO before boot and then use Slackpkg to roll it back to 3.14.3.

Also, FWIW, this is a big "I told you so!" for me as I was afraid of something like this when all the open drivers insisted on KMS at boot--until now, it was just annoying, but now I don't have a working machine.

Update: aaaand...the system is borked. Tried to compile 3.14.4, obviously I screwed something up big time as it panicked before it even got to mounting anything. Sigh...compiling a kernel wasn't this hard in years past...

Oh, and I did reset Slackpkg's "delall" variable to off in slackpkg.conf...helpful for the future, not so much right now.

Sorry to report the 3.14.5 kernel does not fix the previously mentioned WINE problem. Back to 3.10.30.