Screen darkens after booting in Windows mode

I have an intel mac pro that runs windows xp (sp3) on boot camp.
Every time i boot up in windows mode, once I reach the desktop, the screen darkens. Windows xp, to my knowlege, does not have the capacity to adjust screen brightness, as that is normally done manually with the monitor. When I boot back up in mac mode, the screen is unusually dark, so I go to the display window in the control panel, and find that it has been set to minimum brightness.
This does not happen unless I boot up in windows mode.
I think this is a new phenomenon. Since it's relatively subtle, it may have been going on for a while.
I just installed SP3 a few days ago, after installing the bootcamp 2.1 update.
and before you ask, yes, i have installed the mac drivers in windows.

hmmmm. Interesting. Does seem that the monitor is common. Your description just says macPro. If the 8800 is the OEM card, then yours is a quad 3.0, or current gen 8 core?
Do you also have the external controls on the monitor disabled via the X control panel? Although the old 23 does have both brightness and power controls on the front bezel, I have disabled them in the X control panel. I wonder if re-enabling them and using it for brightness control instead would make a difference on the windows side?
===
On replacing the monitor....
Is the 8800 GT HDCP compliant?
I don't think Apples new FP displays are. I say that b/c if if you do replace the monitor, it may be worth considering a small HD TV, many of which are HDCP compliant, and less expensive than the Apple screen.
That would set you up for an internal blueray player
I've seen a Sony on sale for about 150.
I have an off brand...Insignia, I think, 19" HDTV as the monitor on my Windows box. Surprisingly nice screen, and has an ATSC tuner, too. Think retail on it like 300$ at BBuy (I got it as a giveaway at a local car dealer).
HDMI, composite, and VGA inputs. composite and minijack for audio.

Similar Messages

  • My screen darkens after 1 minute and turns off after 3.  All of a sudden, now, after the screen shuts down, it comes right back on????

    My screen darkens after 1 minute and then turn off after 3 minutes (energy saver).  Now, all of a sudden, after it shuts down it comes right on???

    thank you so much sir... i am very thank ful to u... it was an breath taking moment ... i was almost dead as it didnt work

  • Upper part screen darkens after EFI 1.1 update

    After the EFI 1.1 update I am experiencing some problems with the screen of my iMac core duo 20". In OSX, after my mac turns back on from sleep-mode, after a few seconds the upper part of my screen darkens. It looks like the backlite panel dims slightly on the upper part.
    The strange thing is it doesn't happen when I boot in Windows XP with bootcamp. I thought I was experiencing hardware problems. But this can't be the case because it works fine in XP... Anyone

    Nope, didn't work.
    Strange thing is: I've worked on my machine the whole day without any problem. But... when my iMac goes to sleep and wakes up, the problem appears in a few seconds. The whole screen darkens a few tints, and the upper part of the screen darkens a bit more.
    If anyone knows a way to undo the 1.1 update. I can't find the 1.0 version anywhere on the apple site...

  • Macbook Pro boots to a blue screen. Only boots in safe mode

    Hi, I am a long time reader, first time poster.
    OK so I just go a new Macbook Pro 13' from my school (my school made it mandatory to get a mac this year) and I was installing some of my applications. Then I got the "You need to restart your computer" message. I restarted, and all i got was a blue screen with my pointer. Then after a while it says the same restart message. Also I have tried booting from the Snow Leopard Disk, but I get the same message before the actual SL installer comes up. I have been able to get the Macbook to boot in safe mode and I repaired permissions and the disk, however that does not seem to help. I have also reset the PRAM and that did nothing. I am running out of ideas... how can I fix this?!? Help!

    You should not be having kernel panics on a new Mac. Kernel panic causes is sometimes hardware related. Your computer is still under warranty since it's new. You can either call Apple tech support or try the suggestions mentioned in User Tips: Kernel Panics and this article - http://support.apple.com/kb/HT1392

  • OS hangs at grey startup screen, won't boot into safe mode

    I rebooted my G5 this morning and when it came back up, it hung on the grey screen with the Apple logo and the spinning 'gear' progress bar. I tried rebooting several times, but that didn't help. I tried booting from the install DVD (which it did) and ran disk utility (both verify & repair on the start up drive and on permissions. It claims to have found permission errors and fixed them.) I hunted for answers online and tried to boot into safe mode, which did not work.
    Someone mentioned booting into verbose mode and I saw that the load sequence was choaking on the login.
    What could the problem be and how can I fix it?

    Hi Yosarian,
    Minor permissions repairs are no concern: The good news is that your data is probably OK.
    Three things can be happening: Some of the machines boot settings are corrupted, or the OS files or settings are damaged, or there's a hardware problem.
    Resetting the machines power management chip, called a PMU or SMU, depending on your computer, and the PRAM will resolve machine boot settings problems. Run a google search for your model of Mac plus reset pmu OR smu for instructions. After that, reboot your computer and hold Option-Apple-P-R down as you power on. Hold all 4 keys until you hear the startup chime a second time.
    You can test your hardware with the grey disk that came with it that ays AHT in little letters. Boot from the CD and run the extended test. Be patient: AHT can take a long time to boot and run.
    If you reset your PMU and PRAM and pass a hardware diagnostic but still can't boot normally, in safe mode, or in single-user mode, the problem is system software. Reinstall from your latest installer, checking off Archive and Install and Preserve Users and Settings from the Options screen available at the screen where you choose which disk to install to.
    Good luck,
    John

  • No reboot after booting into safe mode

    For a few years I've just ignored the problem but thought I should take time to mention it now.
    When I boot into Safe Mode (holding down the shift key during boot up) I can always click on restart when the password screen comes up and the computers will restart.
    But if I log in after safe boot and let the system boot up past the login screen THEN try a restart I get hours of beach ball. I've left various computers running over night and it is always the same in the morning, no restart, no beach but lots of beach ball.
    So I do a force shutdown (hold the on/off button for 10 seconds) or a forced restart.
    This has been the case from Leopard OSX10.5 and up including Snow Leopard. And on five different Intel Core 2 Duo Macs including 2GHz & 2.4 GHz iMacs and Macbooks.
    The common theme is that I have migrated my setup through all these Macs so maybe there is some legacy thing in my software.
    Suggestions?

    Well… some improvement.
    Here’s what I did: (note that I did a restart and sometimes safe boot after each and every step.
    1 – use FontNuke (free shareware) to blast away font cache files. It found 8 some dating from 2002.
    2 – use Apple’s Font Book to reconcile duplicate fonts.
    Those two steps fixed my slow down problems with playing movie files in Quicktime and VLC.
    But not Skype video. The biggest CPU load with Skype is with the transmitted picture oddly enough.
    Then for good measure I zapped the PRAM and PMU. No noticeable improvement from doing those. Obliviously repair permissions and verify disk was done long long ago and redone.
    I still have the problem of not being able to reboot from safe mode.
    The Startup folders are clean except for Qmaster which I do not believe is the cause of not being able to reboot out of safe mode.
    Does anyone know of other files/locations that put 3rd party startup items? I remember finding things from Western Digital and Symantic a few years ago in unexpected places. Symantic was especially hard to track down and eliminate.

  • Screen flickers after boot camp 2.1 upgrade

    I have been running boot camp 2.0 and WinXP for a few weeks on my iMac 24" 3.06 Ghz 4 Gb running 10.5.5. I had installed the nvidia 177.98 drivers and they improved gaming performance and work great.
    I installed the boot camp 2.1 upgrade and the video drivers changed back to the boot camp 2.1 drivers. I re-installed the nvidia 177.98 drivers.
    I now have two issues:
    1. the monitor is listed as generic plug and play. Is there a driver for the iMac 24" display?
    2. My room is dark so I use F1 to reduce the screen brightness. The whole screen flickers or flashes continuously. IF i have the brightness up near make the flickers or flashing stops. Anyone sen this or have any thoughts?
    If i can't stop the flickering and flashing, I will eventually delete the WinXP system and re-create it and stick with boot camp 2.0.
    ..Bob

    Before you re-do everything consider other options.
    This is the procedure for uninstalling and installing drivers. A program called driver sweeper is required. To uninstall your old drivers you must boot into safe mode, uninstall your old drivers, use driver sweeper to eliminate any remaining fragments of your driver and then install new driver.
    http://www.guru3d.com/category/driversweeper/
    http://forums.guru3d.com/forumdisplay.php?f=29
    Maybe you need to do 2.1 first? or use later drivers?
    nVIDIA ForceWare X 179.13 for Windows XP/2K 32bit
    http://www.laptopvideo2go.com/drivers/xp/179.13
    In the future, you might want to use something to regularly backup, but for now, WinClone can take a full snapshot image for restore, and runs in OS X. DataBackupPC from Prosoft Engineering (Data Rescue II folks) or similar backup / cloning software (Acronis doesn't support GPT and EFI, so no Mac support).

  • [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.

  • Have to restore OS X.9.1 after booting into Windows 7 on Bootcamp

    I am having an odd problem--whenever I boot into Windows 7 on bootcamp, when I then boot into Mac OS X.9.1, I have to restore the disk from Time Machine. This has never happened before, but now has happened twice in a row. It takes hours for the Restore function to restore everything. Anyone have any idea as to why this is happening. My MacPro dates to 2010. Thanks.

    Windows is a guest on your Mac. If you use Windows tools to change the partition Map, or the size of any partition, all Mac OS X partition information is trashed, and you will need to restore it before proceeding.
    Otherwise, you should be able to hold down Alt/Option key at Startup, and select your Mac OS X Volume to boot from (after several minutes of discovering what Volumes are present).

  • Nokia2630 screen darkens after 15 seconds,is it no...

    Dear All,
    The screen of my newly purchased Nokia 2630 darkens after about 15 seconds, I can see that the cahracters are still there but they are difficult to read.
    This makes it e.g. difficult to read a phone number or some other info. If I want the screen to become bright again I have to push any button which has for result that I come onto another screen or the action associated to that button is done. I tought that I could keep the screen lighting on by setting the sleepmode OFf and the energy saving stand OFF but this doesn't help. there seems to be no menu item available where this screen darkening time can be made longer.
    My questions :
    1)is it normal that the screen goes dark after a short period ?
    2)If yes Can I lengthen the period before the screen goes dark. Setting screensaver time out longer doesn't help.
    3)What's the use of havin a screensaver on e.g. the analog clock if you can't hardly see it because thescreen darkens after 15 seconds.
    Many thanks for helping in advance,
    Rgds
    Solved!
    Go to Solution.

    I asked the same question to Nokia Care and this is the answer I received-
    Thank you for contacting Nokia Care.
    With regard to your issue, I recommend that you reboot your Nokia 2630 by switching it off before removing the back cover and battery. After 10 minutes, replace the battery and back cover, then switch the phone on. This acts as a temporary measure to reset the software of the phone and refresh the device's memory. Check and see if you still have the same issue.
    If the issue persists, I suggest that you take your phone together with your proof of purchase to your nearest Nokia Care Point. This is because we are unable to physically assess the phone to determine its issue. The technicians will assess if a repair is required and take the necessary measures to rectify the issue.

  • No SATA drive after booting into Windows (BootCamp 5.0)

    One of my DVD burners has failed in one of my 2008 Apple Mac Pro's.  I pulled the drive out (it was PATA/IDE) and replaced with a new LG WH14NS40 Blu-Ray Burner.  I had to pull the fan out (temporarily) and run a new 24" SATA cable (with right-angle connector) from one of the two extra SATA ports (on the motherboard) to the new actual SATA drive, and also install a MOLEX to SATA power connector.
    I managed to get the drive installed (and working).  I now at least have a Blu-Ray burner in my 2008 Apple Mac Pro (with OS X 10.8.3 Mountain Lion).
    The problem seems to be with when I boot directly into Windows 8.  When I boot into Windows 8, the two ports on the motherboard are disabled and the latest BootCamp 5.0 drivers don't seem to support the two SATA ports on the motherboard (they seem to be disabled).  So when I boot directly into Windows, my LG WH14NS40 Blu-Ray drive disappears.
    I really wish Apple would have just "done things right" from the very beginning and took the time to write decent BootCamp 5.0 drivers that supported the two SATA ports on the motherboard, so that users who need to replace their old/dying/aging PATA drives could easily replace them with SATA drives and use the two SATA ports on the motherboard.
    Also it would have been nice if Apple would have taken the time to write good BootCamp 5 drivers (for Windows 8) that support booting from the two SATA ports on the 2008 Apple Mac Pro motherboard.
    I've heard of many people that have tried installing RAID Controller Cards (from OWC) in their 2008 Apple Mac Pro to upgrade their four hard drive caddys from SATA II (3Gbps) to SATA III (6Gbps) but unfortunately the RAID Controller Cards don't seem to be bootable and the only option is to install a fifth (bootable) hard drive into the Apple Mac Pro and this is normally done by installing a bootable SSD drive into one of the DVD-drive bays.  Unfortunately if you use a SATA SSD drive (which most SSD's are SATA) and then use one of the two SATA ports on the motherboard to connect it, then you go back to having the problem of not having a boot drive when you boot directly into Windows 8 (since there are no BootCamp 5 drivers for the 2008 Apple Mac Pro that support the two SATA ports on the 2008 Apple Mac Pro motherboard).
    This seems to be a never-ending problem, and we have twelve 2008 Apple Mac Pro's (along with an office full of 2008/2009/2010/2013 Apple Mac Pro's) and we're getting extremely frustrated with Apple's lack of support in BootCamp 5.0 drivers for the 2008 Apple Mac Pro (and the two SATA ports on the mainboard).
    Please fix this problem, and please update the BootCamp 5.0/5.1 drivers (for 2008 Apple Mac Pro users) and please support the two SATA ports on the Apple Mac Pro mainboard, and please make those two SATA ports on the motherboard bootable and usable in both Microsoft Windows 8 and in OS X 10.8.3 Mountain Lion.  Please update the BootCamp 5.0 drivers to support the two onboard SATA ports in Windows 8 (so that my Blu-Ray burner is viewable/usable in Windows 8).

    Just as a follow-up, yes it does seem to be possible to get both SATA ports on a 2008 Apple Mac Pro working (in Windows 8).
    You need to enable AHCI in Windows 8.
    First boot into Windows 8 and then go into the windows registry (regedit) and enable AHCI in your registry.
    You can do this by going to the following registry key:
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci
    Set the "Start"  Value data to "0" (to enable AHCI in Windows).
    After AHCI is enabled in Windows, then reboot your computer and now the SATA drive (connected to the ODD port) should appear in Windows (under devices).
    Now the next step is to update your AHCI drivers (in Windows) to the latest Intel drivers, so that your SATA device will actually work (and work properly).
    The latest Intel RST drivers can be found here:  https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=2306 0&ProductFamily=Software+Products&ProductLine=Chipset+Software&ProductProduct=In tel%C2%AE+Rapid+Storage+Technology+(Intel%C2%AE+RST)&lang=eng
    Download the 64-bit drivers (if you are running 64-bit Windows).
    After you install the latest drivers, and perform a reboot, your SATA drive should now work under windows.
    You can find a long detailed thread about enabling AHCI (in Windows 7) here:  http://forums.macrumors.com/showthread.php?t=760482
    The thread listed above is a bit old/dated (2009?) but it does give detailed step-by-step instructions for those that want to enable AHCI (and get those two onboard SATA ports working in Windows 8 or Windows 7).
    I managed to get everything working in Windows 8, and I was able to enable AHCI in Windows 8, installed the latest AHCI drivers and I'm now able to use my SATA Blu-Ray burner in my 2008 Apple Mac Pro.
    Hope this helps!
    ->  Mark

  • Touchpad cannot connect to PC after booting to USB mode using power and volume-up buttons

    My Touchpad can connect via USB to PC while Web-OS is running OK, but when I reboot the Touchpad into USB mode the PC recognises it as a "Palm" device but cannot load drivers and thereofre it does not appear in "My Computer".
    Post relates to: HP TouchPad (WiFi)
    This question was solved.
    View Solution.

    Are you trying to run the webOS doctor?. Is this the first time, or has it worked before?
    Here's my standard help file for doctoring a touchpad:
    How to Doctor an HP TouchPad (reflash the ROM)
    On your Touchpad be sure to have:
    USB cable.
    The battery is charged to at least 30%.
    Computer:
    Windows 7, Windows XP, Windows Vista
    Available USB port (not a hub or secondary port).
    Java 1.5 or later is installed. If you are not sure about what version of Java you have, or even if Java is installed, go to www.java.com and click the Do I have Java? link to install the latest version of Java.
    210MB of storage space.
    Internet connection.
    Miscellaneous Info:
    The update process will take approximately 15 minutes.
    During this process, your device will not be available for use.
    Downloading webOS Doctor
    Download webOS Doctor on your desktop computer. If you have a webOS profile, get it from http://ws.hpwebos.com/webosdoctor/sorry.htm
    If not, check the webOS Internals page: http://www.webos-internals.org/wiki/Webos_Doctor_Versions
    Get your TouchPad ready to update
    Hold the Power Button for several seconds until a menu appears.
    Tap Shut Down to completely power down your device.
    Running webOS Doctor
    Double-click the file that was downloaded to run webOS Doctor.
    Follow the on screen directions up until you are asked to connect your device.
    Select the language you selected on your device, and click Next.
    Confirm your language choice.
    Click Accept to accept the terms of use.
    Click Next. webOS Doctor checks your system. BE PATIENT! I've seen this part take a few minutes to complete.
    After webOS Doctor finishes checking your system, you will be asked to connect your device.
    Connecting your device and finishing the webOS Doctor update
    Connect your device to your computer using the USB cable. You must connect your device directly to your computer, not through a USB hub or other intermediate device.
    Now the tricky part. Hold the Volume Up button on the device and insert the USB cable. After the large USB symbol appears on screen, let go of the Volume Up button. If you see the HP logo instead of the large USB symbol, you may have let go of the Volume Up button prematurely. If this occurred , wait until your device boots up, shut down your device and then repeat step 2.
    Windows will find your device and may offer to install two different drivers.
    When asked to install drivers of OMAP, select No, not at this time.
    When asked to install drivers for Palm Novacom (bootie), select Yes and let the drivers install. This may take a while. Once the drivers have been installed, the Next button will become available in webOS Doctor.
    Click Next.
    Do not disconnect your device from the computer during the update process.
    When the Reset Complete screen appears, click Done.
    Wait a few minutes for your device to reset.
    You're done!
    WyreNut
    I am a Volunteer here, not employed by HP.
    You too can become an HP Expert! Details HERE!
    If my post has helped you, click the Kudos Thumbs up!
    If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

  • Black Screen - Can't Boot to SAFE Mode or Advanced Options

    have a three month old Inspiron 3847 with Win 8.1 that cant boot past the black screen. It does not go to Advanced Options like it should and the F8 key does not take it to SAFE mode. I do not have a bootable media to install. How can I repair this PC?

    Go to run, type msconfig, hit enter, click on boot when the window opens then check safe and reboot.

  • Mac Won't Boot after Boot Camp Windows Update - Macbook Pro Mid 2010

    Hello All, and thanks in advance for any assistance you can provide.
    I have a Mid 2010 Macbook Pro. Last year I upgraded the RAM, then this year I decided to upgrade the hard drive to an SSD-hybrid. Everything went perfectly smoothly with both upgrades, and I was a happy camper.
    I had also installed Boot Camp with Windows 7 and everything worked perfectly. Then last night, I boot in to Windows 7 and it gives me a 'service pack update'. After installing it, I had to reboot my computer. Rebooted it and it accidently started booting OSX. No problem, I thought. I held down the power button, and booted back in to Windows. The service pack installation continued and it had me restart my computer an obscene amount of times during the installation. This is when I initially thought "this is weird".
    Finally the service pack installs, and I'm able to use Windows 7 again. Then I shut down the machine and tried to boot back into OSX. No dice.
    Here's how the OSX booting process goes:
    First, the Apple logo appears, then what appears to be a progressive loading bar at the bottom. After a few seconds, the loading bar disappears. Then it's just at the Apple booting screen with the spinning wheel/gear and sits there indefinitiely. I let it sit there for over an hour last night and nothing happened.
    Any suggestions? I tried resetting the NVRAM and the SMC.
    Thanks so much,
    dlevv

    It looks like a hard disk problem. Press Command and R keys on boot, open Disk Utility, select Macintosh HD in the sidebar and repair your drive

  • Dark screen remains after waking from sleep mode

    Whilst using Safari Version 3.1.2, Mac OS 10.4.11 on my Powerbook G4 (aluminum, 1.5 ghz), my screen remains dark upon waking from sleep mode. Trying to increase screen brightness is ineffectual for some reason likely related to this problem. My only workaround is to force shutdown and restart. Any ideas about a solution would be greatly appreciated.

    Hi Gary,
    This behavior is not a Safari issue but system related.
    Close all applications an run in utilities> disc repair permissions.
    After you done reboot an see what happens when your Mac gets to sleep mode again. This time don't open any applications to test it. Just leave it showing your desktop.
    Post back with the results ...
    Dimaxum

Maybe you are looking for