Firewire Drive Causes Crash at Startup, Safe Boot OK

I have a LaCie External Drive that all of a sudden decided to start causing OSX to crash at startup. While connected booting normally brings up the "need to restart" screen, booting in Single User causes a Kernel Panic, Safe Boot is ok, Booting from Install Disk is ok, but as soon as I connect the drive it's "you need to restart..."
So far i have tried the following;
Zapped the PRAM, repaired permissions normally while disconnected, repaired permissions in Safe Boot while connected, and repaired permissions from Install CD while connected.
My question is of course, what can be causing this problem and how do I fix?
I have sifted through previous discussions but was unable to find an answer, so I apologize if this is a duplicate. Also, if anyone knows of a better category to list this I would appreciate input. Thanks!

DOH!
Like everything else in life, the simplest solution is best. after remembering that the drive is both USB and FW i dug up my cables and tried the USB connection and...all better. So yes, I guess this would prove that the FW port is to blame.
Thanks for the help!

Similar Messages

Firewire driver causes crash on wake up

Every time I wake up my Mac Pro I get a crash report, that Leopard quit. The culprit I have found out is the Apple driver for my Saffire audio device which uses the apple firewire. My only choice is never to let my mac sleep, which I find unacceptable.
Does anyone have an idea about a fix or wether apple has plans to update their firewire drivers?

If anyone did have an idea when an update was forthcoming, the Terms of Use of this forum, and their non-disclosure agreement would forbid them from saying.
I would say this, contact the manufactuers of Saffire Audio, and inform them their firmware needs to be updated for Energy Saver compatibility. Not all peripheral vendors know the Energy Saver standards that Apple uses.
In the meantime, you can use a Screen Saver instead of Energy Saver of a picture filling the screen with black, or download the freeware Mac Brightness. I can't find the link right now as Versiontracker appears to be down from where I'm at.

Sleeping firewire drive causes system crash

I have a 320 GB external firewire seagate drive connected to my Dual Ghz Quicksilver G4. At least twice a day, when I try to access that drive, I experience a system crash, what I believe to be a kernal panic. I get a message telling me I need to shut my computer down and restart it. I am thinking this is not so good for my computer.
So, either the hard drive is the problem or it's the third party firewire card i have installed in one of my PCI slots. But here's the thing, other drives are connected to that card.
Would keeping the Seagate drive awake stop this from happening? It goes to sleep all the time. Have others experienced problems with the seagate drives? Should I stop using it?

Hi, Aaron. Welcome to the Discussions.
If you are seeing this message, that indicates a kernel panic.
There could be a problem with the FireWire drive or the card. If disconnecting the drive for a few days results in no additional panics, then it is the drive. For that, I'd contact Seagate. If not, the card becomes suspect. An examination of the panic log might prove helpful.
You can also try running Step 1 of the process specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ against the Seagate FireWire drive.
Checking the FireWire cables, trying different cables or ports, checking that the card is installed correctly, checking that you assembled the Seagate drive and enclosure correctly (sounds like you built the FW drive) are some other troubleshooting steps to consider. The FireWire enclosure itself may be defective.
See also my "Resolving Kernel Panics" FAQ. This FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics, including tips like those above.
My FAQ is a roadmap: start at the beginning and work through to the end, following the instruction in the order specified, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein.
You maybe unable to prevent the FireWire drive from sleeping. Secondary hard drives (second internal, as well as external drives) may not respect the "Put the hard drive(s) to sleep when possible" option if de-selected. I discuss this particular issue in my "Spinning Beach Ball Of Death (SBBOD)" FAQ, specifically in the section entitled "SBBOD spins for 30-35 seconds. You may hear your hard drives spinning up."
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Question mark folder at startup, safe boot not working

Last night my iMac froze up, Force Quit didn't work, and I used the Power button to shut it off. When trying to restart, it was getting stuck at the grey Apple.
I tried unplugging the peripherals and restarting; zapping the PRAM and restarting; safe boot and restarting. Safe boot did it.
I then ended up going through those steps a few more times as my iMac starting freezing up again. One of those times I changed all my applications in the dock that were set to launch at login to not do so, wondering if that was somehow causing a problem. I also took a folder of recent items I'd created, mostly a LOT of PDFs of newspaper articles, burned it to a DVD and deleted the folder to free up more memory if that was part of the problem (I'm running out). I then restarted from the Apple menu and it shut down through safe boot and then restarted without safe boot and did so just fine. I ran Disk Utility and very few if any permissions needed repairing. And it was operating OK for a bit and then froze up again.
Now I'm getting the question mark folder at startup and safe boot isn't working. What should I be trying next? Lion Recovery with Command-R? I'm relatively new to Lion, but it had been working OK for me for a while now.
What other things should I try? Would Target Disk mode possibly work from the MacBook I'm using now, which doesn't have Lion installed?

The question mark folder usually means that the
firmware could either not find a valid operating
system to boot, or, it could not find a hard disk
with an operating system on it.
Have you tried booting to Lion Recovery? If
you can, then go into Disk Utility and do a
Repair Disk on your OSX volume. If the
OSX volume is not showing up, you may need
to do a reformat and re-install.
Since it is a 24" iMac (from your description) it was
a pre-Lion Mac. If you still have the original install
disks, try booting with it and use Disk Utility from it
to see if the hard drive is working.
Try this first before making a road trip.

LaCie 500GB External Firewire 800 causes crash every time its plugged in???

My LaCie 500GB Firewire External hard drive causes the computer to freeze every time I plug it in.
I just switched back to Mac from Win XP, where the LaCie was used for almost a year without a single problem. Supposedly, since it is formatted for XP use, it can simply be plugged in to my G5 (dual 2.3, 4BG RAM) and work just fine.
I've upgraded to 10.4.4 and still have issues. I've read this is a 'kernal panic' issue, etc.
What is the solution? I can't even plug it in and reformat it - as soon as it's plugged in the Mac collapses; the screen goes 'grey tinted' and an error message appears telling me to hold down the restart button and restart the computer. If I leave the drive plugged in, as soon as I've signed in on the restart, it crashes/freezes/collapses again, same error (i.e. it's circular).
There seems to be no solution. Any help MUCH appreciated!
Thanks,
Sarge

Welcome to Apple Discussions!
First find out if this is a Firewire 800 or 400 problem. Try connecting a Firewire 400 cable to the drive if it supports it. If it only has Firewire 800 ports, you may want to get a Firewire 400 drive to experiment to see if that's all the problem is.
After a forced reboot, it is also always wise to repair the directory if you are backed up:
http://docs.info.apple.com/article.html?artnum=106214
If it detects issues on your source drive that it can't repair, and you are backed up, then I would use Alsoft Disk Warrior.
If it detects no issues, then the problem probably resides in either the cable or the drive you are connecting to. Try a little process of elimination.

Firewire drives cause kernel panic on PPC, not Intel

I'm trying to get three firewire drives to work on a PowerMac G5. Before updating to 10.4.8, they worked individually, but not chained together. Now, if you connect any one of them, the system has a kernel panic. They would cause the panic on the earlier version of 10.4 when chained together. Everything works perfectly on a MacBook and a MacBook Pro, both running 10.4.8.
Below are the notes I took on the three drives as I was troubleshooting. All three are from Maxtor.
Drive 1:
300GB
EDA EB300G0160101
Has a filesystem, but Disk Utility claims there is no partition. It mounts on an Intel Mac, but causes a kernel panic on a G5.
Filesystem is Mac OS Standard
G5 System will panic while booting if the drive is connected and turned on.
G5 panics when trying to mount drive.
Drive 2:
200GB
EDA Ay200A0260101
Has a Mac OS Extended filesystem
G5 System will panic while booting if the drive is connected and turned on.
G5 Panics when trying to mount drive.
Drive 3:
300GB
EDA BA300D0080101
Has a Mac OS Extended (Journaled) filesystem.
G5 System will panic while booting if the drive is connected and turned on.
G5 panics when trying to mount drive.
Because of the change when 10.4.8 was installed, I suspect this is a driver problem. It could also be a controller problem that just happened to get worse when the update was done.
I ran the Apple Service Diagnostic on this machine and was unable to find anything wrong since I replaced both CPUs.
Any ideas?
PowerMac G5 dual 1.8 Mac OS X (10.4.8)

If the drives were formatted on the Intel Mac then they will have a GUID partition map installed on the drive. PPC Macs will not understand the GUID partition scheme which may be the root cause of your problem. If you want to use the drives on both platforms they need to be re-partitioned using the APM partition scheme.
Also, you should not use Mac OS Standard. You should use Mac OS Extended (Journaled.)

Copy from xServe RAID to firewire drive is crashing my OS...

Fellow mac users,
I am a relatively new OS X system admin and I am having a hard time copying files from my xServe RAID to a firewire drive to do an intermittent backup. When I try to copy the files over it crashes the OS without fail. I was wondering if anyone has ever heard or seen of this before? It's rather discouraging when all I'm trying to do is get a quick backup of the RAID which is only 300 gb in size currently.
Our hardware is very good, we have a dual 2.3 G5 model with 3 gb of RAM so I know the hardware can handle a simple finder copy. The only idea I have is to do a "ditto" in the terminal. I thought I'd ask for input from the resident apple sages before trying that. Does anyone have any suggestions or ideas for me?
Thanks for any help,
Thomas
xServe Dual G5 Mac OS X (10.4.5)

Be sure you have the external drive connected when you boot from the installer disc. Use the OS X Installer One disc that came with your MacBook. After you boot from the installer and select your language select Disk Utility from the Utilities menu.
After DU loads select the drive entry (mfgr.'s ID and drive size) for the external drive from the left side list. Click on the Partition tab in the DU main window. Click on the Options button, select the GUID partition scheme and click on the OK button. Set the Format drop down menu to Mac OS Extended (Journaled) and the number of partitions from the Partition drop down menu to one (1). Click on the Partition button. Wait for the volume to mount on the Desktop.
Quit DU and return to the installer. Proceed with the OS X installation. When you get to the part where you select a destination click on the icon for the external hard drive.

Grey screen on startup - safe boot works

Hi. I have a Mac Pro (2008) that starts up with the apple logo and the spiining wheel. Then the screen goes blank. I have tried everything at:
http://support.apple.com/kb/TS2570?viewlocale=en_US&locale=en_US
Interestingly it does work in safe boot mode (but lots of the functionality isn't there).
Disk utility doesn't find any problems. Hardware check from the original disks is very slow but says the hardware is working.
I even got a new disk and put a clean install of Mountain Lion, and got the same behaviour.
I think I'd like to try various options of what is disabled by safe mode, to find the culprit, but I can't seem to find what that may be.
Thanks,
David

I did something better; I erased the disk and did a clean install of Mountain Lion. (I had previously bought a new disk becuase I though that it might be a disk failure). But I still get the same problem. In fact I got the problem during the install. But I could finish the install doing safe boot. Again, I can do a safe boot, but not a standard one. And this occurs before the login.
The hardware check from the original disk says that there are no problems with the hardware.
I will now try a clean install of Snow Leopard and see whether that works.
I'm guessing that it is a hardware problem, because Mountain Lion has worked fine for a few months. But I've no hints as to what it may be.
Thanks again,
David

Second Firewire drive causes first to be disconnected

Having transferred a load of stuff off the main HD onto an external Firewire drive, I decided it would be prudent to have a backup schedule for the new drive as well as the main one. However, whenever I connect and power up a second Firewire drive, the first is disconnected and I get the message that it's a bad idea to disconnect drives without unmounting them first. I ended up having to connect the backup drive via the powered USB hub and watch a very slow backup take place.
If you can't run two drives off an iMac, what's the point of having two Firewire ports...? (The external drives are both powered by "bricks" so I'm surprised there's a problem.)
Is my Mac a lemon? (Cos with all the problems I've been having I'm beginning to think so!)
Would an external (powered) Firewire hub be a good idea in this case?

Have you tried daisy-chaining them? That is, plugging one drive into the other, then into the computer? In any case, a fire wirehub wouldn't be a bad idea.

IdeaCenter - USB thumb drives cause crash/shutdown

Firstly , I have this desktop
IdeaCentre B540 - 25681JU
Every now and then when I insert a thumb drive in to the USB the fan will kick in on full force for about 2 seconds and then the computer will shut down. Ever since I bought the machine new.
It's not limited to a single thumb drive, it has occurred with both a Kingston and Patriot brand.
When ever I have lined the drive up and inserted it quickly and as straight as possible nothing has happened; it generally seems to occur when I am more casual about inserting it with less concentration.
It has probably happened about 10-12 times in 6 months- which doesn't sounds like a lot, but its not right all the same and it would be more if I were more lax about it.
Any ideas? Or others with the same problem?
Damien

hi damien5000,
Welcome to the Lenovo Forums
Can you try to:
1. Boot the PC into the BIOS by continuously tapping F1 on startup
2. When you're in, try to insert the flashdrive
If the unit shuts down while inserting it in carefully, there's a big possibility that something is shorted inside (probably the I/O board) that's causing the PC to shut down and you need to contact lenovo for service.
If the unit doesn't shutdown, try to boot into safe mode and try to insert and access the flashdrive. If everything's ok, perform a clean boot, restart the computer in normal mode and observe the PC.
Let me know your findings
Cheers
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

External USB & Firewire drives causing system to stall

Hi there,
I have zapped the PRAM and reset the system controller.
I have two external hard drives, one USB and one Firewire, connected directly to the computer. I run into the frequent problem where either (or both) of the hard drives are keeping the computer from switching users, although they do seem to allow the computer to fully boot. However, if I try to change users, it will not allow me to get to the login screen without shutting the hard drive off. We also run into problems where the hard drives stall the system... just causes the whole computer to lock up. Any ideas?
Thanks!

With a brand new iMac, make use of the free 90 day Apple support. In the US (800) APL-CARE (800-275-2273)

Optical drive causes crash every time

I installed a DVD burner (NEC DVD_RW ND-3540A) in place of my DVD-RAM drive. The new drive is set as a master. The drive works fine, except if I dont eject a disc immediately after burning, the entire bus goes down. I am not able to shutdown, restart or anything. The only way to fix the issue is to manually restart with he reset button. Any suggestions would be appreciated.

Welcome to Apple Discussions!
First find out if this is a Firewire 800 or 400 problem. Try connecting a Firewire 400 cable to the drive if it supports it. If it only has Firewire 800 ports, you may want to get a Firewire 400 drive to experiment to see if that's all the problem is.
After a forced reboot, it is also always wise to repair the directory if you are backed up:
http://docs.info.apple.com/article.html?artnum=106214
If it detects issues on your source drive that it can't repair, and you are backed up, then I would use Alsoft Disk Warrior.
If it detects no issues, then the problem probably resides in either the cable or the drive you are connecting to. Try a little process of elimination.

Satellite C660-23M - driver causing crash when program starts

I have loaded a CAD program on my new 64bit laptop, the program will start then stops and windows closes it. In the crash reports the modules ntddll.dll and aticfx.dll both seem involved. Could there be some conflict, can I update a driver somehow?
I have seen a report on a gaming website that the aticfx.dll isa the problen on the c660 range.
Please help or the machine goes back to the shop.
PS I have tried running in compatibility mode and disabling antivirus but the problem is unchanged
Regards Ian

Hi
I think the CAD application is not fully compatible with the preinstalled graphic card driver.
The ntddll.dll files is part of the windows system and aticfx.dll file seems to be a part of the graphic card driver and therefore I think that you would need to use another graphic card driver.
The notebook seems to support an Intel HM55 HD graphic card. Try to update the driver using the newest version from the Intel page.

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

Upgrade to 8.0.1 with TDM causes crash on startup of app

I just upgraded to 8.0.1, and Logic will not open. I get through most of the start up, and then get a "quit unexpectedly" error. (Don't you love these informative error messages?)
I have tried:
1)Installing ProApps updates. ProApp2007 2 had not been installed prior to installing 8.0.1. This is contrary to Apples instructions, but I just did what Software Update told me to do.
2)Re-installing 8.0.1, from a download rather than software update-just get "there is nothing to install" message
3)Re-installing from the cd-this strangely, leaves me at 8.0.1. Why?
4)Repairing permissions
5)Swearing alot, to try and intimidate my computer.
Any thoughts?
-Evan Benjamin

Because of what you said in #2 and #3, I don't think you've been successful in doing a reinstall. There's no way you would be a 01 if you truly reinstalled from the disk.
First I'd create a new user and try to start Logic. If it starts, then there is nothing wrong with the program. Go back to your account and delete all preference files. If you have Logic set to open a specific project or autoload, and that file is corrupt, that could crash logic too. Delete whatever file you have set to open with Logic.
If you want to reinstall, I'd use a program like AppZapper to make sure you have all the preference files and all the receipt packages deleted. Do a spotlight search to make sure you get everything. You could leave the Apple Loop content and be OK, but I'd delete all of the programs you installed with Logic Studio, and their associated preference and receipt files. Then reinstall from the disk. You should be at 8.0.0. Then do the upgrade from software update.
Re #3. Intimidation never works. You're machine will rebel. It needs reassurance and kind words. Try telling it how great it is and how you're there for it in its time of need. Whisper sweet nothings and give it a gentle massage.
Good Luck!

Firewire Drive Causes Crash at Startup, Safe Boot OK

Similar Messages

Maybe you are looking for