I have the Nvidia GeForce 7500 LE (and I have Slackware64-current).
I had to compile the kernel with the /boot/config-huge-2.6.33; and had to apply the patch to the Nvidia driver (190.53) before it worked.
edit: and had to blacklist the nouveau also....

I had serious problems with 2.6.33 and the nvidia driver. I couldn't get it to work even with a patched driver. Re-compiling seemed to be the only answer, so I simply used 2.6.32. Everything is fine now with 190.53x. I had heard that there was a serious problem with 195x, so I removed it and went back to the older driver.

I had been using stock kernels for about 3 months, 'cause I was getting lazy I suppose. All was generally ok, or so I thought. With the custom kernel, I see faster responses in boot, with no quirkiness running kde-4.4.1 (from Alien's repo). I am a happy camper except for xconfig still not working. I do have a parallel install of -current that xconfig still works, but i have no idea yet as to why, and I don't yet care enough to try and figure it out.

I don't use dual monitors or cards, Sasha, so I don't have an answer for your problem. Sure wish I did.

There was a reconfigured kernel update for current YESTERDAY that is supposed to let the modules play nicer. I don't know if this will help anyone here or not.

Yeap, that's the kernel that I used. No luck still...

I think that update is for compatibility of the huge kernels with the kernel-modules packages.

For NVIDIA users the official driver works. I configured a twinview last Friday. Worked fine.

Doing this, patching the 190.53 drivers, and installing the 190.53 drivers worked for me on 64-current.

My experience: just patched the 190.53 and blacklisted the nouveau...no kernel recompilation

Or just buy a cheaper ATI videocard... Works fine by default.

This suggestion is from a fanatical NVIDIA user that changed a $250 NVIDIA with a $20 ATI card (BUT WORKING!), for his future peace...

Or you can buy a nice nVidia card that actually has the power to do something and stick with stable Slackware (ie not a bleeding edge kernel) and have none of these issues. nVidia and VirtualBox are always playing catch-up with new kernel versions, and both have *always* provided updated drivers for each new kernel version that breaks the older drivers. If you run a bleeding edge kernel then you should expect breakage.

ATI has better top of the line hardware at the moment than nVidia. nVidia has better drivers for Linux in my opinion, provided you aren't living on the bleeding edge. I just built a new PC with a GTX 260, and I had to do...nothing to get the drivers to work on Slackware64-13.0. I had a previous nVidia integrated graphics card that simply required the proprietary drivers (which were simply installed via the SlackBuild at slackbuilds.org), and I just swapped my hard drives into this computer. No need to play with anything -- nVidia drivers still work for this card, as they should.

I don't see how telling people to just 'buy another graphics card' that is still VERY shaky in the drivers department is helping people who own nVidia cards to use them with the latest kernel...

1 members found this post helpful.

Well, if you want to feel the pleasure to use the default Slackware, with no funny BLOBs, simple: the Slack!

Well, like me, just buy a cheaper and so old ATI card. Slackware is so ATI-enabled today... ;-)

Hooray..after a failed -current upgrade after the *big one* I restored a Clonezilla image from 1/30/10. Doing a full upgrade today the new Nvidia 195.36.15 driver (posted today) compiled with no problem after blacklisting nouveau of course.

After upgrading to the latest batch of updates in -current, including kernel 2.6.33.1, I was able to install 195.36.15 binary driver, and then to run X properly, without any recompilation or any kind of additional hassle - it is only still necessary to blacklist the nouveau kernel module.