Has anyone been able to get the nvidia 180 series drivers to work on slack?

walmartshopper · 12-10-2008, 04:10 PM

I have tried all three of the nvidia 180 series drivers on both 12.1 and current, and could not get them to run. As soon as the KDE splash screen appears, I get an error that says "kdeinit could not start" and then it just stops. I know it's still a beta driver so I don't expect it to work, but I was just curious if any slackers have been able to get it working.

KillerOfGiants · 12-11-2008, 12:29 PM

Take a look at that thread:
http://www.nvnews.net/vbulletin/showthread.php?t=123552
It might be connected, even though the symptoms are different.

walmartshopper · 01-09-2009, 09:59 AM

The same thing still happens with the 180.22 stable release on Slackware 12.2.

tdos20 · 01-09-2009, 10:48 AM

I'm running one of the beta drivers on slackware 12.1, could be a kernel issue - check

Code:

cat /var/log/Xorg.0.log | grep EE

for the errors with the xserver

dugan · 01-09-2009, 11:03 AM

Worked for me with Slackware 12.2 a custom 2.6.28 kernel, and KDE 4

walmartshopper · 01-09-2009, 11:05 AM

Thanks, I'll try 2.6.28

Drakeo · 01-09-2009, 01:03 PM

in run level four type lsmod and see if the module is being loaded. if not modprobe nvidia and if it loads cool if not then there is your source of frustration. but if it does load we have to look into why the nvidia program is not inserting the module. then if it does load and kde does not init thats because kde may need to be tweaked . Not much help but hang in there

drum · 01-09-2009, 04:59 PM

Nvidia driver 180.22 works for me on 12.2 with kde
Cheers
Regards to all

plasmonics · 01-09-2009, 06:46 PM

Quote:

Originally Posted by walmartshopper

I have tried all three of the nvidia 180 series drivers on both 12.1 and current, and could not get them to run. As soon as the KDE splash screen appears, I get an error that says "kdeinit could not start" and then it just stops. I know it's still a beta driver so I don't expect it to work, but I was just curious if any slackers have been able to get it working.

Got 180.22 to work with kernel 2.6.28 and a Geforce 7000M card.

Drakeo · 01-09-2009, 07:50 PM

Quote:

Originally Posted by walmartshopper

I have tried all three of the nvidia 180 series drivers on both 12.1 and current, and could not get them to run. As soon as the KDE splash screen appears, I get an error that says "kdeinit could not start" and then it just stops. I know it's still a beta driver so I don't expect it to work, but I was just curious if any slackers have been able to get it working.

hey walmartshopper you think may be you could tell us if you down loaded nvidia drivers and compiled them then let the program install them . then did a nvidia-xconfig . other wise if you are having problems after an install and can not get your xwindows running as root type xorgsetup.
Other wise if you compiled the program in run level 4 and it built and loaded then it was installed.and did a nvidia-xconfig and then type kdm. if it was the wrong driver then it would have never built. May be

sahko · 01-10-2009, 03:22 AM

180.22 works great for me as well in -current with default kernel

Ilgar · 01-10-2009, 07:10 AM

In my case I have a custom compiled 2.6.27.9 kernel and the 180 series drivers crash KDM. I can use startx or XDM but KDM doesn't work. By the way, this applies to the later 180 versions, the earlier ones caused fan problems on my HP Pavilion but I could log in. I can't try 2.6.28 either because atkbd.c (AT keyboard) gives spurious ACK messages and it hangs. Anyway, the kdm logs are as follows:

The working 177 series log:

Code:

Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan  1 16:28:07 2009
(==) Using config file: "/etc/X11/xorg.conf"
(WW) NVIDIA: No matching Device section for instance (BusID PCI:0:10:3) found
(II) Module "ramdac" already built-in
QImage::convertDepth: Image is a null image
QImage::smoothScale: Image is a null image
FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing.

The broken 180 series log:

Code:

Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 10 14:55:40 2009
(==) Using config file: "/etc/X11/xorg.conf"
(WW) NVIDIA: No matching Device section for instance (BusID PCI:0:10:3) found
(II) Module "ramdac" already built-in
dlsym strcpy error:(null) 
FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing.

walmartshopper · 01-21-2009, 11:54 AM

Quote:

dlsym strcpy error

null)

This is exactly what I'm seeing. I did try 2.6.28 with no luck, and I did compile it runlevel 3. I know the X server is configured correctly because I can run XFCE with no problems. This only happens when starting KDE.

It seems that the people that are not having problems are using the default kernel, and everyone that's having problems is using a custom compiled kernel. I wouldn't mind using the default kernel or a little while, but I would rather figure out which kernel option is causing this. Maybe do a diff between the two configs?

This is the error I get from KDE:
________________________________

There was an error setting up inter-process communications for KDE. The message returned by the system was:

Could not read network connection list.
/home/walmartshopper/.DCOPserver_kyle__0

Please check that the "dcopserver" program is running!
________________________________

And this is what I see in the console:

Code:

startkde: Starting up...
dlsym strcpy error:(null)
startkde: Could not start kdeinit. Check your installation.
Warning: connect() failed: : No such file or directory
dlsym strcpy error:(null)
Could not register with DCOPServer. Aborting.
ERROR: Couldn't attach to DCOP server!
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
startkde: Done.

Ilgar · 01-21-2009, 01:43 PM

It seems it's unable to find a symbol in some library (*.so) file. I'd expect this to be a driver issue rather than a kernel one, but I'm not a true expert on this. I'm now on 2.6.28 and this problems continues. I can't try the stock kernel because it causes random freezes on my system.

walmartshopper · 01-21-2009, 03:13 PM

Got the same results with the stock kernel.