[SOLVED] nVidia driver 195.36.08 causes KDE4.4 to crash after logging?

Hi to all Archers
I noticed the new nVidia driver (195.36.08) on pacman's yesterday updates, I didn't update it immediately and preferred to wait until I was available to fiddle with it in case things went wrong. Apparently, that was the case
Here's what happens if I install the new driver:
KDM starts as usual, I login in, I see KDE loading progress and before it finishes, boom it crashes and returns to KDM login once again.
I tried reinstalling KDE, Xorg and read nVidia wiki to see if there is any hints. I tried once again with a new stock xorg.conf, and removed .nvidia-settings-rc and even disabled KDE compositing but all this couldn't help getting KDE up and running.
However, when I reinstall the previous version (190.53) everything is back to normal.
So what I want to know is am I the only one who gets this problem or there're others here having the same issue?
Because the first time I installed the nVidia driver (almost 3 months now) I used their own installer then used Arch packages afterwards, I suspect that perhaps their installer messed things up !?
For now the solution is to stick to the previous version.
I'm using Arch Linux 32bit and my GC is an nVidia 7300GT.
Regards,
Med
Last edited by stuntgp2000 (2010-03-08 00:17:10)

zero-giulio wrote:
I want to install the 190.53 version of nvidia driver, because it's the correct driver version for my video card, according to nvidia site (see http://www.nvidia.com/object/linux_disp … 0.53.html).
Also, in my prevoius arch system I installed that version and everything worked well. I don't want to try the newerr version. It doesn't matter if 190.53 are not the latest driver available. I'm self confident with the 190.53 version.
How can I install them? The problem is that pacman suggest me only the latest version :-(
You'll find them here http://schlunix.org/archlinux/extra/os/ after choose your system architecture.
if you want to know more about downgrading for more than a few packages read this guide http://wiki.archlinux.org/index.php/Dow … g_Packages
Assuming you have a recent nvidia graphic card and using a i686 system you should download these:
http://schlunix.org/archlinux/extra/os/ … pkg.tar.gz
http://schlunix.org/archlinux/extra/os/ … pkg.tar.gz
Good luck,

Similar Messages

Had to start Firefox in safe mode cause it kept crashing after i deleted the file. Now Fire fox Crashes every time I open it and I have to put it in safe mode j

Had to start Firefox in safe mode cause it kept crashing after i deleted the file. Now Fire fox Crashes every time I open it and I have to put it in safe mode just to use it, also it's not syncing with my iPad.

If you use Norton software, try disabling your Norton extensions. As of last week, there were severe compatibility issues with Firefox 24.

[SOLVED] nvidia driver causes blank screen soon after boot

Hi,
I have a NVIDIA 560 and was originally using the nouveau driver, but that gave slow performance when doing anything (eg. resizing windows), so I installed the nvidia driver instead by following the wiki section:
https://wiki.archlinux.org/index.php/NV … au_drivers
by essentially just following the scripts given there. After switching to nvidia, the screen goes blank soon after boot. I get back into the system by using nomodeset in menu.cfg.
My question is how do I even begin to find the problem, eg. what log file(s) should I look in and post?
Thanks
Last edited by mark1977 (2012-08-19 17:38:42)

Yes it's the 560 Ti. Thanks I just installed straight from the repos. I've also installed cuda-sdk and cuda-toolkit. I've compiled the libraries inside /opt/cuda-sdk/CUDALibraries fine.
No I go to compile the sdk examples by running make in /opt/cuda-sdk/C and get the following error:
# make
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/shared'
make[1]: Leaving directory `/opt/cuda-sdk/shared'
make[1]: Entering directory `/opt/cuda-sdk/C/src/newdelete'
make[1]: Leaving directory `/opt/cuda-sdk/C/src/newdelete'
make[1]: Entering directory `/opt/cuda-sdk/C/src/simpleTextureDrv'
/usr/bin/ld: cannot find -lcuda
collect2: error: ld returned 1 exit status
make[1]: *** [../../bin/linux/release/simpleTextureDrv] Error 1
make[1]: Leaving directory `/opt/cuda-sdk/C/src/simpleTextureDrv'
make: *** [src/simpleTextureDrv/Makefile.ph_build] Error 2
The Makefile itself essentially seems to just include the file /opt/cuda-sdk/C/common/common.mk, which is:
# Copyright 1993-2011 NVIDIA Corporation. All rights reserved.
# NVIDIA Corporation and its licensors retain all intellectual property and
# proprietary rights in and to this software and related documentation.
# Any use, reproduction, disclosure, or distribution of this software
# and related documentation without an express license agreement from
# NVIDIA Corporation is strictly prohibited.
# Please refer to the applicable NVIDIA end user license agreement (EULA)
# associated with this source code for terms and conditions that govern
# your use of this NVIDIA software.
# Common build script for CUDA source projects for Linux and Mac platforms
.SUFFIXES : .cu .cu_dbg.o .c_dbg.o .cpp_dbg.o .cu_rel.o .c_rel.o .cpp_rel.o .cubin .ptx
# Add new SM Versions here as devices with new Compute Capability are released
SM_VERSIONS := 10 11 12 13 20 21 30
CUDA_INSTALL_PATH ?= /opt/cuda-toolkit
ifdef cuda-install
CUDA_INSTALL_PATH := $(cuda-install)
endif
# detect OS
OSUPPER = $(shell uname -s 2>/dev/null | tr [:lower:] [:upper:])
OSLOWER = $(shell uname -s 2>/dev/null | tr [:upper:] [:lower:])
# 'linux' is output for Linux system, 'darwin' for OS X
DARWIN = $(strip $(findstring DARWIN, $(OSUPPER)))
ifneq ($(DARWIN),)
SNOWLEOPARD = $(strip $(findstring 10.6, $(shell egrep "<string>10\.6" /System/Library/CoreServices/SystemVersion.plist)))
LION = $(strip $(findstring 10.7, $(shell egrep "<string>10\.7" /System/Library/CoreServices/SystemVersion.plist)))
endif
# detect 32-bit or 64-bit platform
HP_64 = $(shell uname -m | grep 64)
OSARCH= $(shell uname -m)
# Basic directory setup for SDK
# (override directories only if they are not already defined)
SRCDIR ?=
ROOTDIR ?= ..
ROOTBINDIR ?= $(ROOTDIR)/../bin
BINDIR ?= $(ROOTBINDIR)/$(OSLOWER)
ROOTOBJDIR ?= obj
LIBDIR := $(ROOTDIR)/../lib
COMMONDIR := $(ROOTDIR)/../common
SHAREDDIR := $(ROOTDIR)/../../shared/
# Compilers
NVCC := $(CUDA_INSTALL_PATH)/bin/nvcc
CXX := g++ -fPIC
CC := gcc -fPIC
LINK := g++ -fPIC
# Includes
INCLUDES += -I. -I$(CUDA_INSTALL_PATH)/include -I$(COMMONDIR)/inc -I$(SHAREDDIR)/inc
# Warning flags
CXXWARN_FLAGS := \
-W -Wall \
-Wimplicit \
-Wswitch \
-Wformat \
-Wchar-subscripts \
-Wparentheses \
-Wmultichar \
-Wtrigraphs \
-Wpointer-arith \
-Wcast-align \
-Wreturn-type \
-Wno-unused-function \
$(SPACE)
CWARN_FLAGS := $(CXXWARN_FLAGS) \
-Wstrict-prototypes \
-Wmissing-prototypes \
-Wmissing-declarations \
-Wnested-externs \
-Wmain \
# architecture flag for nvcc and gcc compilers build
CUBIN_ARCH_FLAG :=
CXX_ARCH_FLAGS :=
NVCCFLAGS :=
LIB_ARCH := $(OSARCH)
# Determining the necessary Cross-Compilation Flags
# 32-bit OS, but we target 64-bit cross compilation
ifeq ($(x86_64),1)
NVCCFLAGS += -m64
LIB_ARCH = x86_64
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch x86_64
else
CXX_ARCH_FLAGS += -m64
endif
else
# 64-bit OS, and we target 32-bit cross compilation
ifeq ($(i386),1)
NVCCFLAGS += -m32
LIB_ARCH = i386
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch i386
else
CXX_ARCH_FLAGS += -m32
endif
else
ifeq "$(strip $(HP_64))" ""
LIB_ARCH = i386
NVCCFLAGS += -m32
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch i386
else
CXX_ARCH_FLAGS += -m32
endif
else
LIB_ARCH = x86_64
NVCCFLAGS += -m64
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch x86_64
else
CXX_ARCH_FLAGS += -m64
endif
endif
endif
endif
# Compiler-specific flags (by default, we always use sm_10, sm_20, and sm_30), unless we use the SMVERSION template
GENCODE_SM10 := -gencode=arch=compute_10,code=\"sm_10,compute_10\"
GENCODE_SM20 := -gencode=arch=compute_20,code=\"sm_20,compute_20\"
GENCODE_SM30 := -gencode=arch=compute_30,code=\"sm_30,compute_30\"
CXXFLAGS += $(CXXWARN_FLAGS) $(CXX_ARCH_FLAGS)
CFLAGS += $(CWARN_FLAGS) $(CXX_ARCH_FLAGS)
LINKFLAGS += -L/usr/lib
LINK += $(LINKFLAGS) $(CXX_ARCH_FLAGS)
# This option for Mac allows CUDA applications to work without requiring to set DYLD_LIBRARY_PATH
ifneq ($(DARWIN),)
LINK += -Xlinker -rpath $(CUDA_INSTALL_PATH)/lib
endif
# Common flags
COMMONFLAGS += $(INCLUDES) -DUNIX
# If we are enabling GPU based debugging, then we want to use -G, warning that this
# May have a significant impact on GPU device code, since optimizations are turned off
ifeq ($(gpudbg),1)
NVCCFLAGS += -G
dbg = $(gpudbg)
endif
# Debug/release configuration
ifeq ($(dbg),1)
COMMONFLAGS += -g
NVCCFLAGS += -D_DEBUG
CXXFLAGS += -D_DEBUG
CFLAGS += -D_DEBUG
BINSUBDIR := debug
LIBSUFFIX := D
else
COMMONFLAGS += -O2
BINSUBDIR := release
LIBSUFFIX :=
NVCCFLAGS += --compiler-options -fno-strict-aliasing
CXXFLAGS += -fno-strict-aliasing
CFLAGS += -fno-strict-aliasing
endif
# architecture flag for cubin build
CUBIN_ARCH_FLAG :=
# OpenGL is used or not (if it is used, then it is necessary to include GLEW)
ifeq ($(USEGLLIB),1)
ifneq ($(DARWIN),)
OPENGLLIB := -L/System/Library/Frameworks/OpenGL.framework/Libraries
OPENGLLIB += -lGL -lGLU $(COMMONDIR)/lib/$(OSLOWER)/libGLEW.a
else
# this case for linux platforms
OPENGLLIB := -lGL -lGLU -lX11 -lXi -lXmu
# check if x86_64 flag has been set, otherwise, check HP_64 is i386/x86_64
ifeq ($(x86_64),1)
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
else
ifeq ($(i386),)
ifeq "$(strip $(HP_64))" ""
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
endif
endif
endif
# check if i386 flag has been set, otehrwise check HP_64 is i386/x86_64
ifeq ($(i386),1)
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
ifeq ($(x86_64),)
ifeq "$(strip $(HP_64))" ""
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
endif
endif
endif
endif
endif
ifeq ($(USEGLUT),1)
ifneq ($(DARWIN),)
OPENGLLIB += -framework GLUT
else
ifeq ($(x86_64),1)
OPENGLLIB += -lglut -L/usr/lib64
endif
ifeq ($(i386),1)
OPENGLLIB += -lglut -L/usr/lib
endif
ifeq ($(x86_64),)
ifeq ($(i386),)
OPENGLLIB += -lglut
endif
endif
endif
endif
ifeq ($(USEPARAMGL),1)
PARAMGLLIB := -lparamgl_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifeq ($(USERENDERCHECKGL),1)
RENDERCHECKGLLIB := -lrendercheckgl_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifeq ($(USENVCUVID), 1)
ifneq ($(DARWIN),)
NVCUVIDLIB := -L../../common/lib/darwin -lnvcuvid
endif
endif
# Libs
ifneq ($(DARWIN),)
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib $(NVCUVIDLIB)
else
ifeq "$(strip $(HP_64))" ""
ifeq ($(x86_64),1)
LIB := -L$(CUDA_INSTALL_PATH)/lib64 -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
else
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
endif
else
ifeq ($(i386),1)
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
else
LIB := -L$(CUDA_INSTALL_PATH)/lib64 -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
endif
endif
endif
# If dynamically linking to CUDA and CUDART, we exclude the libraries from the LIB
ifeq ($(USECUDADYNLIB),1)
LIB += ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB} -ldl -rdynamic
else
# static linking, we will statically link against CUDA and CUDART
ifeq ($(USEDRVAPI),1)
LIB += -L/usr/lib -lcuda ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB}
else
ifeq ($(emu),1)
LIB += -lcudartemu
else
LIB += -lcudart
endif
LIB += ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB}
endif
endif
ifeq ($(USECUFFT),1)
ifeq ($(emu),1)
LIB += -lcufftemu
else
LIB += -lcufft
endif
endif
ifeq ($(USECUBLAS),1)
ifeq ($(emu),1)
LIB += -lcublasemu
else
LIB += -lcublas
endif
endif
ifeq ($(USECURAND),1)
LIB += -lcurand
endif
ifeq ($(USECUSPARSE),1)
LIB += -lcusparse
endif
# Lib/exe configuration
# Lib/exe configuration
# Lib/exe configuration
ifneq ($(STATIC_LIB),)
TARGETDIR := $(LIBDIR)
TARGET := $(subst .a,_$(LIB_ARCH)$(LIBSUFFIX).a,$(LIBDIR)/$(STATIC_LIB))
LINKLINE = ar rucv $(TARGET) $(OBJS)
else
ifneq ($(OMIT_CUTIL_LIB),1)
LIB += -lcutil_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifneq ($(OMIT_SHRUTIL_LIB),1)
LIB += -lshrutil_$(LIB_ARCH)$(LIBSUFFIX)
endif
# Device emulation configuration
ifeq ($(emu), 1)
NVCCFLAGS += -deviceemu
CUDACCFLAGS +=
BINSUBDIR := emu$(BINSUBDIR)
# consistency, makes developing easier
CXXFLAGS += -D__DEVICE_EMULATION__
CFLAGS += -D__DEVICE_EMULATION__
endif
TARGETDIR := $(BINDIR)/$(BINSUBDIR)
TARGET := $(TARGETDIR)/$(EXECUTABLE)
LINKLINE = $(LINK) -o $(TARGET) $(OBJS) $(LIB)
endif
# check if verbose
ifeq ($(verbose), 1)
VERBOSE :=
else
VERBOSE := @
endif
# Check for input flags and set compiler flags appropriately
ifeq ($(fastmath), 1)
NVCCFLAGS += -use_fast_math
endif
ifeq ($(keep), 1)
NVCCFLAGS += -keep
NVCC_KEEP_CLEAN := *.i* *.cubin *.cu.c *.cudafe* *.fatbin.c *.ptx
endif
ifdef maxregisters
NVCCFLAGS += -maxrregcount $(maxregisters)
endif
ifeq ($(ptxas), 1)
NVCCFLAGS += --ptxas-options=-v
endif
# Add cudacc flags
NVCCFLAGS += $(CUDACCFLAGS)
# Add common flags
NVCCFLAGS += $(COMMONFLAGS)
CXXFLAGS += $(COMMONFLAGS)
CFLAGS += $(COMMONFLAGS)
ifeq ($(nvcc_warn_verbose),1)
NVCCFLAGS += $(addprefix --compiler-options ,$(CXXWARN_FLAGS))
NVCCFLAGS += --compiler-options -fno-strict-aliasing
endif
# Set up object files
OBJDIR := $(ROOTOBJDIR)/$(LIB_ARCH)/$(BINSUBDIR)
OBJS += $(patsubst %.cpp,$(OBJDIR)/%.cpp.o,$(notdir $(CCFILES)))
OBJS += $(patsubst %.c,$(OBJDIR)/%.c.o,$(notdir $(CFILES)))
OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu.o,$(notdir $(CUFILES)))
# Set up cubin output files
CUBINDIR := $(SRCDIR)data
CUBINS += $(patsubst %.cu,$(CUBINDIR)/%.cubin,$(notdir $(CUBINFILES)))
# Set up PTX output files
PTXDIR := $(SRCDIR)data
PTXBINS += $(patsubst %.cu,$(PTXDIR)/%.ptx,$(notdir $(PTXFILES)))
# Rules
$(OBJDIR)/%.c.o : $(SRCDIR)%.c $(C_DEPS)
$(VERBOSE)$(CC) $(CFLAGS) -o $@ -c $<
$(OBJDIR)/%.cpp.o : $(SRCDIR)%.cpp $(C_DEPS)
$(VERBOSE)$(CXX) $(CXXFLAGS) -o $@ -c $<
# Default arch includes gencode for sm_10, sm_20, sm_30, and other archs from GENCODE_ARCH declared in the makefile
$(OBJDIR)/%.cu.o : $(SRCDIR)%.cu $(CU_DEPS)
$(VERBOSE)$(NVCC) $(GENCODE_SM10) $(GENCODE_ARCH) $(GENCODE_SM20) $(GENCODE_SM30) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -c $<
# Default arch includes gencode for sm_10, sm_20, sm_30, and other archs from GENCODE_ARCH declared in the makefile
$(CUBINDIR)/%.cubin : $(SRCDIR)%.cu cubindirectory
$(VERBOSE)$(NVCC) $(GENCODE_SM10) $(GENCODE_ARCH) $(GENCODE_SM20) $(GENCODE_SM30) $(CUBIN_ARCH_FLAG) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -cubin $<
$(PTXDIR)/%.ptx : $(SRCDIR)%.cu ptxdirectory
$(VERBOSE)$(NVCC) $(CUBIN_ARCH_FLAG) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -ptx $<
# The following definition is a template that gets instantiated for each SM
# version (sm_10, sm_13, etc.) stored in SMVERSIONS. It does 2 things:
# 1. It adds to OBJS a .cu_sm_XX.o for each .cu file it finds in CUFILES_sm_XX.
# 2. It generates a rule for building .cu_sm_XX.o files from the corresponding
# .cu file.
# The intended use for this is to allow Makefiles that use common.mk to compile
# files to different Compute Capability targets (aka SM arch version). To do
# so, in the Makefile, list files for each SM arch separately, like so:
# This will be used over the default rule abov
# CUFILES_sm_10 := mycudakernel_sm10.cu app.cu
# CUFILES_sm_12 := anothercudakernel_sm12.cu
define SMVERSION_template
#OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu_$(1).o,$(notdir $(CUFILES_$(1))))
OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu_$(1).o,$(notdir $(CUFILES_sm_$(1))))
$(OBJDIR)/%.cu_$(1).o : $(SRCDIR)%.cu $(CU_DEPS)
# $(VERBOSE)$(NVCC) -o $$@ -c $$< $(NVCCFLAGS) $(1)
$(VERBOSE)$(NVCC) -gencode=arch=compute_$(1),code=\"sm_$(1),compute_$(1)\" $(GENCODE_SM20) $(GENCODE_SM30) -o $$@ -c $$< $(NVCCFLAGS)
endef
# This line invokes the above template for each arch version stored in
# SM_VERSIONS. The call funtion invokes the template, and the eval
# function interprets it as make commands.
$(foreach smver,$(SM_VERSIONS),$(eval $(call SMVERSION_template,$(smver))))
$(TARGET): makedirectories $(OBJS) $(CUBINS) $(PTXBINS) Makefile
$(VERBOSE)$(LINKLINE)
cubindirectory:
$(VERBOSE)mkdir -p $(CUBINDIR)
ptxdirectory:
$(VERBOSE)mkdir -p $(PTXDIR)
makedirectories:
$(VERBOSE)mkdir -p $(LIBDIR)
$(VERBOSE)mkdir -p $(OBJDIR)
$(VERBOSE)mkdir -p $(TARGETDIR)
tidy :
$(VERBOSE)find . | egrep "#" | xargs rm -f
$(VERBOSE)find . | egrep "\~" | xargs rm -f
clean : tidy
$(VERBOSE)rm -f *.stub.c *.gpu *.cu.cpp *.i *.ii
$(VERBOSE)rm -f *.cubin *.ptx *.fatbin.c *.hash
$(VERBOSE)rm -f *.cudafe1.c *.cudafe2.c *.cudafe1.cpp *.cudafe2.cpp
$(VERBOSE)rm -f $(OBJS)
$(VERBOSE)rm -f $(CUBINS)
$(VERBOSE)rm -f $(PTXBINS)
$(VERBOSE)rm -f $(TARGET)
$(VERBOSE)rm -f $(NVCC_KEEP_CLEAN)
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.ppm
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.pgm
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.bin
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.bmp
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.txt
$(VERBOSE)rm -f $(CUBINDIR)/*.cubin $(PTXDIR)/*.ptx
$(VERBOSE)rm -rf $(ROOTOBJDIR)
$(VERBOSE)rm -rf $(LIBDIR)
$(VERBOSE)rm -rf $(OBJDIR)
$(VERBOSE)rm -rf $(TARGETDIR)
clobber : clean
$(VERBOSE)rm -rf $(COMMONDIR)/lib/*.a
$(VERBOSE)rm -rf $(SHAREDDIR)/lib/*.a
$(VERBOSE)rm -rf $(COMMONDIR)/obj
$(VERBOSE)rm -rf $(SHAREDDIR)/obj
The output of echo $LD_LIBRARY_PATH is blank.
I have checked for libcuda and can find it:
# ls /usr/lib | grep libcuda
libcuda.so.1
libcuda.so.304.32
Is there something obvious I need to do to get these to compile?
Thanks again.

Problems with Premiere Elements 8 after updating to Nvidia driver 195.81 or later?

Hello PRE8 users,
If you have an Nvidia-based graphics chipset, and you've updated to Nvidia driver version 195.81 or later and you're still experiencing frequent crashes and freezes in Premiere Elements 8, then we'd like to hear from you in this thread. As mentioned in the announcement at the top of this forum, we believe most of these issues are caused by a problem with an Nvidia driver that was released after PRE8 was developed, and that the issues should be resolved by updating to Nvidia driver version 195.81 or later. Notes from the announcement I mentioned above are copied below for your reference.
Best regards,
Chad
For Nvidia users, there is a driver update that will fix both of the following issues:
Premiere Elements 8 does not restart after closing on Windows
Frequent and inexplicable crashes with Premiere Elements 8
To resolve these issues, you should update your GPU (graphics card) driver to version 195.81 or higher, by following the steps below.
1.      Identify which GPU driver you have by right clicking on the Desktop > Properties > Settings and in the Display field it will be displayed.
2.      Go to http://www.nvidia.com/Download/index.aspx?lang=en-us and download driver for your GPU card. Its size varies from 80 to 120MB depending upon the GPU card model.
3.      After the download is complete, run the driver install Installation. This should take less than 2 minutes.
There are no known issues that the latest driver update will cause.
This is an announcement. There is a separate discussion topic located here.
***If the update steps shown above do not upgrade your system to version 195.81 or higher, then you may need to download the driver directly. Use the link below only if the steps above do not update your driver to 195.81 or higher. The download page for Vista and Windows 7 is located here:
http://www.nvidia.com/object/win7_winvista_32bit_195.81_beta.html
http://www.nvidia.com/object/win7_winvista_64bit_195.81_beta.html

Processor
AMD Athlon(tm) II X4 620 Processor
7.1
4.9
Determined by lowest subscore
Memory (RAM)
4.00 GB
7.1
Graphics
NVIDIA GeForce 9500 GT
4.9
Gaming graphics
2431 MB Total available graphics memory
6.3
Primary hard disk
231GB Free (466GB Total)
5.9
Up here I copied and posted my PC's spec's. Since upgrading to the new driver, my problems increased. I seem to experience more crashes than before. Happens randomly and I can not see a pattern.   (I have noticed dragging clips from one area to another on the time line is no-no)
JPR

Bridge CS4 crashes with last Nvidia driver (195.62)

Sorry for my bad english...
This message because since november I have crashes with Blue Screnn of the Death when I used Bridge CS4, even when no other programs running on my PC.
Or my computer became veru slow when I open Bridge...
Or Error messages saying that Bridge must close because not enough memory (I have 3gO RAM and 512 on my graphic card Nvidia 9500, and not at all used when I have the message....)
I tried many and many things (uninstall and reinstall Photoshop, change preferences of Photoshop, Bridge, change memory in Windows...) and Bridge always crashes after some minutes of use.
I searched in many forums, and saw many people have the same problem, but nobody have the solution.
Yesterday, in the "Event viewer", in "system", I had the message : "the driver nv_disp of the peripherical display \Device\Video0 remained blocked in an infinite curl. It points out a problem with the material or with the driver of the material programming the equipment in the wrong manner"
So I went to a problem with the graphic card.
I found the solution on a forum about Nvidia : "...the problem is that after driver 195.62, sometimes Blue Screen of the Death happens. This crashes happens everytime I close Adobe Bridge, and also in some other occasions too. With the old driver (190.38), dosn't BSOD. Will be great if NVIDIA told it at 195.62 releases, and fix it if possible..."
In fact, I uploaded my GeForce 9500 driver version 6.14.11.7519 to 6.14.11.9562 in november...
I come back to my old driver and have no more problem with Bridge CS4...

Well I have a 9600GT and at the moment I have the v191.07 installed but on checking the Nvidia site today I saw this
This is a WHQL-certified driver for GeForce 6, 7, 8, 9, 100, 200, and 300-series desktop GPUs and ION desktop GPUs.
New in Version 197.45
Recommended for the best performance with the new GPU-accelerated features in Adobe CS5
RESULT...
Well have tried it and it seems to cure the problem. Opened Bridge and Photoshop CS5 several times, went through hundreds of photo albums, trying to make Bridge crash but it just wouldn't... So for now I'd have to say it works great.

[SOLVED] Nvidia Driver T-Shoot - New Install

...Hello.
Just installed Arch on an office box and everything went great until I tried to access the Nvidia driver controls under XFCE4 after loading the nvidia-utils package. The UI tells me that I "do not appear to be using the Nvidia Driver..." I guess I'm still on Nouveau, despite following the path described in the Beginer's Guide. Here are some system details:
uname -a
Linux 3.0-ARCH #1 SMP PREEMPT Wed Aug 17 21:55:57 CEST 2011 x86_64 Intel(R) Xeon(TM) CPU 3.00GHz GenuineIntel GNU/Linux
lspci |grep VGA
07:00.0 VGA compatible controller: nVidia Corporation NV43GL [Quadro FX 550] (rev a2)
less /var/log/Xorg.0.log | grep -i nvidia
[ 686.487] (II) Module glx: vendor="NVIDIA Corporation"
[ 686.487] (II) NVIDIA GLX Module 280.13 Wed Jul 27 17:12:07 PDT 2011
[ 686.488] (==) Matched nvidia as autoconfigured driver 2
[ 686.490] (II) LoadModule: "nvidia"
[ 686.490] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 686.491] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 686.495] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
[ 686.495] (EE) NVIDIA: system's kernel log for additional error messages.
[ 686.496] (II) UnloadModule: "nvidia"
[ 686.496] (II) Unloading nvidia
[ 686.496] (EE) Failed to load module "nvidia" (module-specific error, 0)
[ 686.498] (II) NOUVEAU driver for NVIDIA chipset families :
[ 686.504] (--) NOUVEAU(0): Chipset: "NVIDIA NV43"
[ 686.860] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
...tried generating an xorg.conf via nvidia-xconfig, and this is what it produced:
=================
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 280.13 ([email protected]) Wed Jul 27 17:15:58 PDT 2011
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
==============
...for giggles, tried to modprobe nvidia into the kernel, and got:
FATAL: Module nvidia not found.
...any help would be greatly appreciated. I don't expect to have this much driver difficulty when I install at home next week, and this office machine is really just a practice run. I suspect that the driver issue might be at least partially down to the fact that this is maybe not one of Nvidia's more standard SOHO-market cards. It came in this huge Dell workstation that weighs a ton...owell.
--Thanks
Last edited by purple12 (2011-08-21 06:34:20)

purple12,
Sorry, I don't have access to a system with Nvidia. As a moderator, may I request that you use bbcode code tags around program output. It uses a monospaced font so that columns line up, and includes scroll bars for long passages. Your readers will appreciate you.
This text is in code tags. To see how I did this, you can use the "Quote" link after this post to see the source.
Thanks.

[SOLVED] NVidia driver for Dell XPS1340 (GeForce 9400M G)

Hi.
I don't know which nvidia driver install for my laptop, Dell XPS 1340. Before i had installed nvidia-173xx but now this driver doesn't work with new xorg-server (http://mailman.archlinux.org/pipermail/ … 20001.html).
I've kernel26-pae and i've install nvidia-pae driver, after installation i config with nvidia-xconfig but when i run startx i get this error:
[ 1210.888] (--) Depth 24 pixmap format is 32 bpp
[ 1217.522] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA GPU at PCI:2:0:0. Please
[ 1217.522] (EE) NVIDIA(GPU-1): check your system's kernel log for additional error
[ 1217.522] (EE) NVIDIA(GPU-1): messages and refer to Chapter 8: Common Problems in the
[ 1217.522] (EE) NVIDIA(GPU-1): README for additional information.
[ 1217.522] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!
[ 1217.523]
Backtrace:
[ 1217.523] 0: /usr/bin/X (xorg_backtrace+0x37) [0x80a38e7]
[ 1217.523] 1: /usr/bin/X (0x8048000+0x5faea) [0x80a7aea]
[ 1217.523] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb779540c]
[ 1217.523] 3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb52c3000+0x471698) [0xb5734698]
[ 1217.523] Segmentation fault at address (nil)
[ 1217.523]
Fatal server error:
[ 1217.523] Caught signal 11 (Segmentation fault). Server aborting
[ 1217.523]
[ 1217.523]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 1217.523] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1217.523]
lspci | grep VGA output is:
02:00.0 VGA compatible controller: nVidia Corporation GT218 [GeForce G210M] (rev a2)
03:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9400M G] (rev b1)
xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 270.41.03 ([email protected]) Sat Apr 9 00:26:11 PDT 2011
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
Can anybody help me?
Thanks and best regards.
Last edited by Pilli (2011-04-14 11:48:58)

Hi.
To fix this problem i've to edit the /boot/grub/menu.lst file and add to kernel line vmalloc=192M option.
More information here: http://us.download.nvidia.com/XFree86/L … ssues.html at Kernel virtual address space exhaustion on the X86 platform section.
I hope this can help someone
Thanks.

Video Drivers in Windows 7 64 bit cause Windows to crash after reboot

I have a Mac Mini mid 2011, I installed Windows 7 64 bit through Bootcamp. After the install I install the Mac drivers. I have narrowed it down to the video card drivers are causing Windows to crash on reboot. Are there other drivers I can use? Am I doing something wrong?
Thank you in advance for any help or advice.

I have an imac
I have an magic pad (same thing as the touch pad on a macbook really)
I have an usb mouse I use both in windows and osx
if your trackpad somehow was registered as actived for some reason it would seem as if it was the mouse
had some *** situations both in windows and osx when my cat sit on the magicpad

All VIs containing MathScript cause a fatal crash after upgrading from 8.2 to 8.5... what gives?

So I finally took the plunge and updated to 8.5 from 8.2 and now when I open a project that was previously done (as in ready for release this week ) it causes a hard crash where LabVIEW closes completely. I've looked and can't seem to find any others complaining of this. My only option that works at this point is to have a coworker open all my VIs containing mathscript and delete the function with his 8.2 enviornment. What could be causing this? There has to be some simple answer...somewhere.
Thanks in advance for all the help!
Regards,
Dave

These VIs work fine for me under LV 8.2 and will no longer work under LV 8.5. The first one is a call to our power supplies, the second uses the math formula node to verify that some color and luminance parameters are valid.
In the meantime I am stuck using a coworkers 8.2 development system with TS 3.5 to deploy which works with no issues. When I try on my new system with 8.5 and TS 4.0 it crashes out.
Thanks for any help you can provide.
Regards,
Dave
Attachments:
DMM - IVI Measure.vi ‏52 KB
Verify Color and Brightness.vi ‏174 KB

Flash 11.3 does cause plugincontainer to crash after closing FF

Hi Chris,
After installing flash 11.3.300.257
the new flash sandboxed causes the plugincontainer of firefox to crash.
open yt video, close the tab.
close firefox (or wait until the process plugincontainer.exe + the newer 2 processes flashplugin in task manager disappear).
close firefox.
after closing ff, I go a crash of plugincontaniner.exe.
no problem with flash 11.2
=> flash 11.3 and his new processes (2) in task manager (sandbox) cause the firefox's contanier to crash.
ff13,
vista 32 sp2.
the first crash of plugincontainer in my life!!!
thanks.
ome evento problema:     BEX
Nome applicazione:     plugin-container.exe
Versione applicazione:     13.0.0.4535
Timestamp applicazione:     4fc8de63
Nome modulo con errori:     NPSWF32_11_3_300_257.dll_unloaded
Versione modulo con errori:     0.0.0.0
Timestamp modulo con errori:     4fc821fc
Offset eccezione:     64f99903
Codice eccezione:     c0000005
Dati eccezione:     00000008
Versione SO:     6.0.6002.2.2.0.768.3
ID impostazioni locali:     1040
Informazioni aggiuntive 1:     27dd
Ulteriori informazioni 2:     b76caa7c2627bab0b68e16f682ad848f
Ulteriori informazioni 3:     ff08
Ulteriori informazioni 4:     4fae96fb14b9fa70f5513f6819ad1b00
Message was edited by: schützenkönig
crash log added.

Hi Chris, I am not alone
https://bugbase.adobe.com/index.cfm?event=bug&id=3209832
=>=>   https://bugbase.adobe.com/index.cfm?event=bug&id=3210025
https://bugbase.adobe.com/index.cfm?event=bug&id=3172259
or 1) protectionmode=0
or 2) plugincontainer.exe crashes AFTER closing Firefox (i.e. the container is unable to RE-load the flash plugin for regularly stopping it! therefore: crash).
I warmly hope that a new version of flash 11.3 for FF will be released in a few days...in the meantime I disable the sandbox (> doing so, the container process in taskmanager ***remains active until I close FF***, as in the past > therofore: no crash
thanks.
please let me know if there are good news

[SOLVED] NVIDIA driver conflict after upgrade

First of all, Its nice to be here. I'm a new arch user. So please excuse me if this has been discussed before. I searched the forum , i seem to have this problem https://bbs.archlinux.org/viewtopic.php?id=156666 but the information in the thread did not solve my issue.
When i do an upgrade i get the following message.
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
:: libgl and nvidia-304xx-utils are in conflict. Remove nvidia-304xx-utils? [y/N]
If i say yes
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-nvidia-304xx-utils: requires nvidia-304xx-utils
:: nvidia-304xx: requires nvidia-304xx-utils=304.64
UNAME
[sam@archetype ~]$ uname -a
Linux archetype 3.7.4-1-ARCH #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013 x86_64 GNU/Linux
Also, I'm running an Nvidia 7300LE with nvidia-304xx driver. I'm on a x64 system.
Thanks in advance,
Skotadi
Last edited by skotadi (2013-01-27 08:39:02)

skotadi wrote:I'm sorry glxinfo isn't working for me even after installing mesa package.
You didn't have mesa before?!
For a newbie what was the reason to omit this part of the Beginners Guide:
Install mesa for 3D support:
# pacman -S mesa
Anyway, glxinfo is inside of a package called mesa-demos (it takes 5 seconds to google it).
Did you removed nouveau as I implied earlier?
Am I getting this right: Arch was working for you since october and something broke in recent days? If so you should have blind idea what could be the reason. Did you changed anything recently? It happened after system upgrade? But first things first: remove nouveau completely (and maybe reinstall nvidia to see what pacman will say about it). Better yet read some of many threads about it. Most notably this one And for christ sake don't use --force switch or I won't be trying to help you anymore.
Last edited by masteryod (2013-01-26 17:55:30)

Filters cause CS6 to crash after update

Hello:
I am running Photosop CS6 64 bit on a Windows 7 machine with a quad i& Intel processor and 12 GB RAM.
Everythng ran perfect until I installed the latest updates. I got a message that the update failed, the code brought me to update my Application Manager, which I did. Now the manager tells me that my Photoshop is up to date. BUT wehenever I try to use one of the filters in like the vanishing point, lens correction, liquify, Photoshop stops working and crashes. Also the filter to process images in Camera Raw is not showing (I do not know if this one is included in the update though or is only CC). The rest of the filters like blur, noise etc. work normally.
I figured that my installation somehow became corrupt and try to re-install, but get thatr message that Photoshop CS6 is already installed, (DUH!)
Any suggestions ?
Thank you for your attention.
Andre

Hello:
Indeed, version 13.0.0, so I installed first the update to 13.0.1.1, rebooted and success, filters there again. Then I went to the update to 13.0.1.2, update failed, filters disappeared again. And reverted to 13.0.0 !
Re-applied the 13.0.1 udate, again success. again reappearance of filters, and now shows version 13.0.1, as it should. Now start my updated Application manager, chews a bit on it and then shows me: Photoshop up-to-date ! This notwithstanding the 13.0.1.1 version showing.
Thus, I am afraid I am stuck with uninstalling and then re-installing, which will not be for now as I do not have any problems, the filters are working etc, and, uninstalling and reinstalling is a hassle I will do it in the near future.
Thanks for the help
Andre
EDIT/UPDATE 2013/06/12
A possible cause could be that I have the Russel Brownextension to edit a picutre or layer in ACR. I tried to remove it with the extension manager, who caims it is removed but it shows still up and works perfectly. So, for the moment, I am going to live with it.
Thanks for your help
Andre
Message was edited by: andrehuls on 2013-06-12

GT70 20D BSoD on win 8.1 - Nvidia driver

Hello,
I have several BSod (blue screen of death) under windows 8.1. (around one every days) i try to run driver verifier on ALL the drivers, one by one (it's take me few hours) and finally discover
that it's the driver for nvidia (nvlddmkm.sys exactly) that do all the time the BSoD ! (in driver verifier it's do BSoD few seconds after windows start)
I try everything possible, uninstalling nvidia driver (no more bsod but not perfect solution because compatible vga driver is used in place), using the last nvidia
driver (9.18.13.3182 but it's not work) and even the beta driver (not work either)
What the solution i have now ? is someone really have one GT70 20D and win8.1 with the laster nvidia driver without any BSoD ??
Also my win8.1 is a clean install from iso DVD
thanks by advance

Quote from: loki5100 on 03-January-14, 21:53:52
but i can't go to windows 8 ! the only previous version i can go (supported by our company) it's windows 7 ! but on the website on msi they said we can not update the bios with a windows 7 version when the bios was originally with a windows 8 version :( this can brick the laptop they say ... so what i can do ???
and sorry but when i read here :
http://www.msi.com/product/nb/GT70-2OD.html
it's clearly say it's work with Windows 8.1 !
So i buy it regarding this ! but it's false advertising because it's never work on windows 8.1 !
it's msi that choose to work with nvidia, so it's their responsibility to say that it's not compatible with windows 8.1 !
anyone with the windows 8.1 can try driver verifer on the nvidia driver to see that it's immediately crash after few minutes
First off, calm down. You're being rather irrational.
The BIOS doesn't matter if it's a Windows 7 or a Windows 8 BIOS. It will work with the OS. You can install Windows 7 perfectly fine on a GT70 20D with it having a Windows 8 or 8.1 BIOS. The bios doesn't effect the OS. The reason they state information regarding the OS is that GT70 0NX's can come with both Windows 7 or Windows 8 pre-installed. Those notebooks can only upgrade to the same BIOS that corresponds to the OS originally installed.
That being said, you don't seem to understand what I said. MSI cannot control NVidia's drivers. If the NVidia drivers don't work well with Windows 8.1, that doesn't mean the notebook is incompatible. The notebook runs Windows 8.1 just fine. The problem lies more with NVidia and the drivers provided for Windows 8.1. I've been over this a million times on many different websites, getting mad at MSI over NVidia's drivers is the same as getting mad at Microsoft for printer manufacturer's not putting out updated printer drivers for Windows 8.1. Microsoft can't control what those manufacturer's do. Get mad at them.
As zipper has said, it does work, but look at what he did...he went through many different versions of both the Intel and NVidia drivers. Most likely you will have to do the same. This is not something we can do for you, you're going to have to do it on your own.

Quicktime in vista using with Nvidia driver version 169.25 crashes

I've been searching the web for a long time to solve this problem, it appears that when quicktime 7.4.1 is used in vista when latest nvidia driver was install will cause the directdraw and direct 3D accelerationg to stop working, therefore the video will jitter and the program will crash when it is closed.
At the same time the latest version of iTunes is working perfectly, the podcast (H.264 encoded) still play fine, also cover flow is smooth, which means directdraw and direct 3D is working in itunes.
Many people in different forums have reported the same problem, but no one has a solutions yet, that's why I would like to post it here and hope that apple can solve this problem once and for all.
Thanks.
My graphic card is Nvidia Geforce 8400GS.
The error message is listed below:
问题签名:
问题事件名称: BEX
应用程序名: QuickTimePlayer.exe
应用程序版本: 7.4.1.14
应用程序时间戳: 47a28143
故障模块名称: QuickTimePlayer.exe
故障模块版本: 7.4.1.14
故障模块时间戳: 47a28143
异常偏移量: 0000130d
异常代码: c0000409
异常数据: 00000000
OS 版本: 6.0.6000.2.0.0.256.1
区域设置 ID: 2052
其他信息 1: 4aa1
其他信息 2: ec2d6aa67da3a13df0a04d40fd655031
其他信息 3: 2330
其他信息 4: de6f39a0b9c5e22c575472cc93ca2944

no problem im happy to see another happy custumer

Unable to get the nvidia driver (proprietary) work

Hi,
I can't get the nvidia-driver work on my Lenovo Thinkpad T61 (Quadro NVS 140M).
At the moment I use the free NV-driver (with hal, no xorg.conf). I deinstalled the xfree86-video-nv package and libgl. Afterwards I installed 'nvidia' and created a minimal xorg.conf via nvidia-xconfigure. When I start the X-Server, the screen stays black, no nvidia-logo- nothing :-(
Dunno what goes wrong. Can someone help?
Thanks and Greetings!

howe wrote:
ngoonee wrote:If your x-server keeps crashing, what do you have to lose?
My work
Its a beta nvidia driver, the WORSE it can do is crash your x-server. Which is what you're experiencing anyway. So net effect on your work is probably 0.
Anyway, just consider it if you decide to try again. I know the feeling of just not having enough time to hack around when REAL work awaits.

[SOLVED] nVidia driver 195.36.08 causes KDE4.4 to crash after logging?

Similar Messages

Maybe you are looking for