Personally I went to the nVidia forums to find out more on the drivers, and how too's, as I want my 1400x1050 24 back as the new 7147 drivers take me back to 1280x1024 24 and this is very unacceptable. I want my 1400x1050 24 back.

I have removed the rc.modules from loading the agpart since it does not like my VIA chipset. Then set the NvAgp to 3 to use the AGP only. and it's not letting it.

Yea....

I was camping this weekend. No sweat... The kernel slak-paks make all the appropriate symlinks for you. Not really a need to re-install either. But if you want to, you can ofcourse... I suppose it's best to stick with slak-paks for the time being tho.

Now, if you opt for 2.6.10, then that 2.6.11 driver isn't the one you want. You need the base 2.6 driver and use the first patch (2.6.9 thru 2.6.10).... I think 2.6.11.10 is in Slack testing right now. Just because it's in "testing" doesn't mean there is anything wrong with it... Let me know how it goes. I'm curious...

Well I have to FTP the Testing again if I want to use the Prepackaged, but am happy with the Linux 2.4.30 I instaalled from the -current.

also with my setup, I have had to disable the XWindow Nvidia Driver settings, and leave the xorg settings so I could get my 1400x1050 24, as the nVidia sets it at 1280x1024 24, and I left that over a month ago and have a hard time dealing with anything less than 1400x1050.

I acidentally installed my 2.6.11 nvidia driver on 2.6.10 and it worked... Makes me wonder if it will run on 2.6.8.1 or below... If that's the case, then that's kinda cool. It will be a unified 2.6 nvidia driver then.... Just thought I'd mention it...

I don't know if this will help anyone with NVidia problems, but they've issued an updated build of the unified drivers. 7664 now. Check out:

http://www.nvidia.com/object/unix.html

Most likely not... Now they are pretty much stating your SOL

Hello all,

dear oh dear... I seem to be plagued with problems with Slack10.1 and my laptop. I decided to take a break from working on the display problem so I could start on it with a fresh mind. So much for that.

The same problems. Not just with the nvidia drivers either. I tried installing ndiswrapper to get my wireless card working, and I get the same UID GID errors that I mentioned earlier of (pg. 3 or 4). This was a on a completely clean install of Slack too.

I think I might try Debian again. Or one of the others, FC3 seems to be quite a sucess with other users of this kind of laptop. With any luck something'll work out.

Thanks again for all your help, esp. Jong. Maybe all this is just some difficulty with this particular laptop model.

R

Hmm... Sucks to hear your having so many problems... Their not Slackware related tho. If your having problems with permissions when trying to build kernel modules, then it's a kernel problem.. I don't know if you tried using a newer kernel that came from Slackware or not... I remember before, you were trying to compile your own. Most kernels, if not all, from kernel.org come with uid/guid of 500 or something like that. Doing a "chown -R root.root ." from inside the kernel directory will fix that.

So... What I'm trying to say is.... Don't give up on Slackware... Try using 'official' kernel Slak-paks from a Slackware FTP site if you haven't already. That or chown as stated above and build as root.

Sorry for necroposting, but I've got some pretty good news Just upgraded to the latest nvidia drivers (8774). Someone mentioned that "ConnectedMonitors" has been deprecated for some time, so I changed:
to:
I restarted xorg and TwinView works! The long-standing bug which bugged me for over two years has finally been fixed! Hope this works for all you people who had the same troubles as I did I imagine that the same fix was also applied in the newest release of the legacy drivers.