2964 Views 3 Replies Latest reply: Nov 24, 2010 1:26 PM by Deborah Terreson
Hmmm. On a reboot, hold down the 'command'+'V' key - this puts the machine into verbose mode, so you see all the BSD loading up and notice if you get any hardware error codes that have something like this: *cpu 0 caller 0x001e00000* blah, blah, blah.. or if you get a kernel panic:(*we are hanging here...*) is usually what it will output.
Hard to say what is going on until you dig a bit deeper..
I would say yes to the verbose mode and go one further and make it permanent. Coming to OSX from running Tiger on an XPF install on a beige G3 system (totally unsupported by Apple), it was ALWAYS a smart move and even in new machines running hardware they're built to, you can't lose. For the times I do have to reboot, it's good to be able to watch the startup, as you catch immediately if there's a problem with anything. It is verbose after all...
To turn the mode on, you open the Terminal, and at the prompt, type in
*sudo nvram boot-args="-v"* and hit enter. It will nag you about using the terminal (if you haven't done so before) and you enter your password, hit enter again and you're good to go. (if you want to turn it off, type in *sudo nvram boot-args=* and hit enter and your password again)