Always Booting In Verbose Mode

Recently I did some work on my two MacBooks. Simply enough, I removed the hard drive from each MB and switched it with the other so that each machine now had the other's hard drive (reasons are unnecessary). It worked perfectly, or so I thought. The only bug that has come up repeatedly is that my MBP, which has the HD from the older BlackBook, is always starting up in verbose mode.
What would cause this? I never altered the "sudo nvram boot-args= " command in terminal, though I guess it could be possible for something else to have altered it when the hard drives were switched.

Hi there,
Now we are getting some fun, don't we? that's really odd.
The blank screen before the verbose mode is normal, usually after the blank we get the apple splash screen.
I also found a bug at my startup as I was making some tests trying to find your ways out of this bug.
In fact I found some log features that I should not have in my system since it was set before I format and zero out my hard disc two times in the last two weeks.
I could not proceed with my testings by now but I will. Also I found something yesterday that you could read about if you have any interest about the boot process at http://osxbook.com/book/bonus/ancient/whatismacosx/arch_startup.html
Good luck, hope I come back soon with some light.

Similar Messages

  • Boot using verbose mode

    When booting with verbose mode (cmd v) it all scrolls by faster than I can absorb it. Ok, I'm slow. Does this get saved to a log file somewhere that I can look at with a more leasurely pace???
    hyram

    Everything should be in /var/log/system.log

  • Turned on fileVault AND firmware password, can't boot into verbose mode?

    Just out of curiousity, I turned on fileVault AND firmware password on my retina macbook pro,
    and when I boot up holding command-v, instead of getting the firmware password screen, I get the filevault password screen.
    Is this normal and expected behaviour?

    The firmware password disables that shortcut; verbose mode can still be used by using the Terminal to change the NVRAM boot arguments, which requires an administrator password.
    (100118)

  • Vista boots in Verbose Mode

    I just installed Vista and everytime it boots the command line displays verbose mode, meaning it's telling me almost everything it's doing during startup.
    How do I turn this off on a MacBook Pro?
    Normally on a regular PC with BIOS, I am able to press the F# hotkey during startup to set my boot preferences. Not sure how to do this on an Intel Mac.
    Any ideas?
    Also, I'm not sure if this is the right forum to post this, so I am posting this in "Installation..." as well

    Thanks, John.
    The only login item was iTunes Helper. I disabled it. (what does it do anyway? that's for another forum)
    While in System Preferences I also enabled ftp login and file sharing (I think I had left that off before).
    I rebooted and got the familiar blue screen on the external screen, nothing on the built-in screen.
    I logged in from my MBP usin ssh and got connected. I also was able to look at the disk and directories from the finder.
    In terminal, with "top" I noted that there was a stuck process. If I knew Unix I could have determined what that process was but I don't. WaitingForLoginWindow came up at some point when I also used "ps".
    Eventually I decided to try connecting with Chicken of the VNC, and this time I connected. Except, all I got was a black screen. Nothing I did would change it from a black screen.
    What I forgot to mention earlier is that this iBook at first appears to start from a bootable CD (like TechTools or Diskwarrior or a system disc) but then just gets stuck at some point.
    This all seems like a hardware error to me.
    Message was edited by: Simon Frech
    Message was edited by: Simon Frech

  • Booting in verbose mode after installing Mountain Lion

    I installed Mountain Lion on 3 machines. On my iMac I now boot after a cold start in verbose mode. What do I do to stop that? Thanks.

    Sorry, that I have no answer, but may be it helps psychologically to know that you are not alone. I have the same problem and maybe worse because the boot process holds at a certain point in single user mode and a root prompt. I have to enter "exit" to make it continue and startup properly. It looks like I have the same HW as you.

  • ML boots into verbose mode - why?

    And how can I prevent this happening. 
    I'm running -
    Processor  2.66 GHz Intel Core 2 Duo
    Memory  8 GB 1333 MHz DDR3
    Graphics  NVIDIA GeForce 9400 256 MB
    Software  OS X 10.8 (12A269)
    I use a wireless keyboard and mouse - can that have anything to do with it?
    There must be a solution form Apple.  Please, what is it?

    A further update. I se a wireless keyboard and mouse. If these are switched on during the boot process then I get the verbose screen. Solution was to turn them on afrer booting up. Weird.

  • TS2570 iMac won't boot, GSOD with Flashing Question Mark, safe/verbose mode not possible

    I have an iMac 24", just over 2 years old running OS X v10.5 (Leopard). Mighty Mouse and bluetooth keyboard, no peripherals.
    It slowed enormously over the last few weeks and has now ceased to boot.
    On switching on I hear the chime (blank grey screen initially), the grey screen hangs for approx 30sec before the flashing folder/?mark icon appears.
    There is no further progress.
    Boot key combination results:
    Can reset NVRAM (Option-Command-P-R)
    Cannot boot to safe mode
    Cannot boot to startup manager
    Cannot boot to verbose mode
    Cannot boot from target media (DVD etc)
    Cannot boot to AHT mode
    Cannot boot to single user mode
    I have followed the steps here http://support.apple.com/kb/TS2570
    Disconnect, test peripheral devices and network cables - done - de-powered and rebooted. No difference.
    Perform a Safe Boot- this does not work.  I am familiar with the boot combinations and timings. The safe boot leads to the same flashing folder/?mark icon. I have also tried verbose, single user, AHT and startup manager with the same result.
    Reset the NVRAM / PRAM - done - this worked and kicks the system into an auto-reboot after 3-5 seconds. This also demonstrates the Keyboard is fine. The subsequent boot fails at the same point via normal, safe or verbose boot instructions.
    Start from your Mac OS X Install disc; use Disk Utility – I never received an OSX install disk.  I have the original box with receipts etc, the only disk present is an unsealed version of iLife (yeah thanks Apple).  Where would I get one?
    Check your cables and power source – done - all fine.
    Remove third-party RAM and internal hardware – not applicable.
    Perform an Archive and Install installation of Mac OS X – how would I do this when I cannot boot the device?
    Perform an Erase and Install installation of Mac OS X as a last resort – how would I do this when I cannot boot the device?
    To me the problem looks like a HDD failure.  I had windows (dual boot) professionally installed when I bought the iMac and since the Windows boot option is also not visible (startup manager itself does not work) I suspect the system can’t find bootable media because the HDD isn’t spinning.
    An OS corruption would generally affect one or the other but presumably not both Operating Systems simultaneously.
    It's hard to be certain, but I’m sure it used to make more noise.
    I had a look into opening it up and troubleshooting the physical components but it’s hard to know where to start.  There are no obvious ways in and I’m not a professional so decided to post a question here rather than hack it open.
    I'd be grateful if you could suggest next steps here, or is it time to go dig a hole in the garden?  I certainly expected more than 2yrs life from a £1200 unit.
    Many Thanks,
    Ryan

    Thanks for the response,
    I bought the iMac new, 17th Jan 2010, all receipts intact but no extended warrenty. I declined the Applecare Plan for two reasons.
    (1) The sales rep seemed very confident in the product build. In fact the main justification of the price tag was the quality of the device. I'd also never had an apple device malfunction at that stage.
    (2) The incumbent EU regulations are quite fair in so much as legislation dictates electrical goods should be manufactured to function for a 'reasonable' lifetime. I would be morally uncomfortable paying for rights I theoretically already have.
    I triple checked on the OS X disks you mentioned but no joy. Unusual as it may be, the box has not been used and it's contents reflect the day of purchase. 
    I'm happy to order the OS X v10.5 DVD and attempt a boot to the disk utility, I don't mind risking a few bucks on a potential fix.  I'll need to figure out where to order the disk, the call centre is closed ATM so watch this space.
    What I'd really be interested in is; (a) is there a known diagnostic routine to determine the HDD functionality and (b) it is possible to replace/upgrade the HDD?  This for me is where the iMac loses ground against a conventional PC in terms of motherboard/component access. It's far superior from an asthaetics perspective while things are running smoothly and the OS is great but the first sign of a hardware malfunction and there seems little or no scope to self-medicate the device.
    The disk has around 40-60 GB free space.
    I don't have a second Mac, nor any friends or family with a Mac to 'borrow' for the disk utility test you mentioned. I'll hunt around this afternoon/week but my instinct tells me finding a locally accessable Mac running 3 yr old OS X might not be possible. Again, watch this space, I'll post any further developments. 
    In the meantime any further assistance or answers to the above questions on determining HDD status would be much appreciated. No progress has yet been made on the original issue of failing to boot.
    Many Thanks
    Ryan

  • Normal Startup Messages (System.log; Intel Verbose Mode)?

    Over this past weekend, I wanted to test the backup I had for my 24" iMac. I had always used Apple's Backup program that comes with .Mac when I had my PowerBook, and never tested it. This was bad, because it didn't work when I actually needed it.
    I also suspected there might be something slightly wrong with my iMac, so equipped with about 4 hours and my install DVDs i went to work.
    The only thing I've done so far is get all the Apple updates and setup my iChat account. I changed to boot in verbose mode, and found that the eery messages that scared me prior to doing my reinstallation of OS X (I zeroed the drive, then did a full install) were still there.
    Here is my entire System.log:
    Jan 30 09:22:35 mike-barcas-computer sudo: Mike : TTY=ttyp1 ; PWD=/Users/Mike ; USER=root ; COMMAND=/usr/sbin/nvram boot-args=-v
    Jan 30 09:22:48 mike-barcas-computer shutdown: reboot by Mike:
    Jan 30 09:22:48 mike-barcas-computer SystemStarter[279]: authentication service (287) did not complete successfully
    Jan 30 09:22:48 mike-barcas-computer kernel[0]: (295: ps)tfp: failed on 0:
    Jan 30 09:22:48 mike-barcas-computer kernel[0]: (295: ps)tfp: failed on 0:
    Jan 30 09:22:48 mike-barcas-computer kernel[0]: (295: ps)tfp: failed on 0:
    Jan 30 09:22:49 mike-barcas-computer kernel[0]: (322: ps)tfp: failed on 0:
    Jan 30 09:22:49 mike-barcas-computer SystemStarter[279]: The following StartupItems failed to properly start:
    Jan 30 09:22:49 mike-barcas-computer kernel[0]: (322: ps)tfp: failed on 0:
    Jan 30 09:22:49 mike-barcas-computer SystemStarter[279]: /System/Library/StartupItems/AuthServer
    Jan 30 09:22:49 mike-barcas-computer kernel[0]: (323: ps)tfp: failed on 0:
    Jan 30 09:22:49 mike-barcas-computer SystemStarter[279]: - execution of Startup script failed
    Jan 30 09:23:08 localhost kernel[0]: hi mem tramps at 0xffe00000
    Jan 30 09:23:08 localhost kernel[0]: PAE enabled
    Jan 30 09:23:08 localhost kernel[0]: 64 bit mode enabled
    Jan 30 09:23:08 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Jan 30 09:23:08 localhost kernel[0]: vmpagebootstrap: 512343 free pages
    Jan 30 09:23:08 localhost kernel[0]: migtable_maxdispl = 71
    Jan 30 09:23:08 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
    Jan 30 09:23:08 localhost kernel[0]: 80 prelinked modules
    Jan 30 09:23:08 localhost kernel[0]: ACPI CA 20060421
    Jan 30 09:23:08 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
    Jan 30 09:23:08 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
    Jan 30 09:23:08 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
    Jan 30 09:23:08 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Jan 30 09:23:08 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Jan 30 09:23:08 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
    Jan 30 09:23:08 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
    Jan 30 09:23:08 localhost kernel[0]: Started CPU 01
    Jan 30 09:23:08 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
    Jan 30 09:23:08 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
    Jan 30 09:23:08 localhost kernel[0]: Security auditing service present
    Jan 30 09:23:08 localhost kernel[0]: BSM auditing present
    Jan 30 09:23:08 localhost kernel[0]: disabled
    Jan 30 09:23:08 localhost kernel[0]: rooting via boot-uuid from /chosen: 771A8047-7B26-48DC-ABB6-89E46168EE40
    Jan 30 09:23:08 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Jan 30 09:23:08 localhost kernel[0]: USB caused wake event (EHCI)
    Jan 30 09:23:08 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 0017f2fffe6db760; max speed s800.
    Jan 30 09:23:08 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT2 @2/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/ST3500641AS Q Media/IOGUIDPartitionScheme/AppleHFS_Untitled2@2
    Jan 30 09:23:08 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
    Jan 30 09:23:08 localhost kernel[0]: CSRHIDTransitionDriver::probe: -v
    Jan 30 09:23:08 localhost kernel[0]: CSRHIDTransitionDriver::start before command
    Jan 30 09:23:08 localhost kernel[0]: CSRHIDTransitionDriver::stop
    Jan 30 09:23:08 localhost kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
    Jan 30 09:23:08 localhost kernel[0]: Jettisoning kernel linker.
    Jan 30 09:23:08 localhost kernel[0]: Resetting IOCatalogue.
    Jan 30 09:23:08 localhost kernel[0]: GFX0: family specific matching fails
    Jan 30 09:23:08 localhost kernel[0]: Matching service count = 1
    Jan 30 09:23:08 localhost kernel[0]: Matching service count = 2
    Jan 30 09:23:08 localhost kernel[0]: Matching service count = 2
    Jan 30 09:23:08 localhost kernel[0]: Matching service count = 2
    Jan 30 09:23:08 localhost kernel[0]: Matching service count = 2
    Jan 30 09:23:08 localhost kernel[0]: Matching service count = 2
    Jan 30 09:23:08 localhost kernel[0]: NVDANV40HAL loaded and registered.
    Jan 30 09:23:08 localhost kernel[0]: GFX0: family specific matching fails
    Jan 30 09:23:08 localhost kernel[0]: wl0: Broadcom BCM4328 802.11 Wireless Controller
    Jan 30 09:23:08 localhost kernel[0]: 4.80.76.0Previous Shutdown Cause: 3
    Jan 30 09:23:08 localhost memberd[38]: memberd starting up
    Jan 30 09:23:08 localhost mDNSResponder-108.2 (Aug 25 2006 14: 50:48)[31]: starting
    Jan 30 09:23:10 localhost lookupd[44]: lookupd (version 369.6) starting - Tue Jan 30 09:23:10 2007
    Jan 30 09:23:13 localhost diskarbitrationd[37]: disk0s2 hfs 8AAF2196-1366-34AB-B7BC-3D96F131E9AD Macintosh HD /
    Jan 30 09:23:13 localhost DirectoryService[43]: Launched version 2.1 (v353.5)
    Jan 30 09:23:13 localhost kernel[0]: yukonosx: Ethernet address 00:16:cb:9e:39:58
    Jan 30 09:23:13 localhost kernel[0]: AirPort_Brcm43xx: Ethernet address 00:17:f2:99:63:9d
    Jan 30 09:23:13 localhost lookupd[56]: lookupd (version 369.6) starting - Tue Jan 30 09:23:13 2007
    Jan 30 09:23:14 mike-barcas-computer configd[35]: setting hostname to "mike-barcas-computer.local"
    Jan 30 09:23:14 mike-barcas-computer kernel[0]: Registering For 802.11 Events
    Jan 30 09:23:14 mike-barcas-computer /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
    Jan 30 09:23:14 mike-barcas-computer kernel[0]: [HCIController][setupHardware] AFH Is Supported
    Jan 30 09:23:16 mike-barcas-computer mDNSResponder: Adding browse domain local.
    Jan 30 09:23:16 mike-barcas-computer loginwindow[50]: Login Window Started Security Agent
    Jan 30 09:23:17 mike-barcas-computer kernel[0]: SetCryptoKey T: len 16, idx 0
    Jan 30 09:23:17 mike-barcas-computer kernel[0]: SetCryptoKey R: len 16, idx 1
    Jan 30 09:23:17 mike-barcas-computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Currently connected to network Ferrari
    Jan 30 09:23:20 mike-barcas-computer configd[35]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
    Jan 30 09:23:20 mike-barcas-computer configd[35]: posting notification com.apple.system.config.network_change
    Jan 30 09:23:20 mike-barcas-computer lookupd[88]: lookupd (version 369.6) starting - Tue Jan 30 09:23:20 2007
    Jan 30 09:23:20 mike-barcas-computer ntpdate[126]: no servers can be used, exiting
    Jan 30 09:23:21 mike-barcas-computer configd[35]: target=enable-network: disabled
    The lines that concern me are the ones bolded at the top of System.log
    The other thing that is a bit unnerving to me is that when I have it set to boot in verbose mode, and then restart the computer, I get a screen that looks out of place. It is a box with a dark background in the center of the screen with text in there, and then it quickly switches to full screen verbose mode. The first line of full screen verbose mode (which is what I'm used to since I always used verbose mode on my PowerBook) is this one:
    Jan 30 09:23:08 localhost kernel[0]: hi mem tramps at 0xffe00000
    In the centered text, it mentions something about "loading drivers" followed by many lines of periods. It is only up for about 5 seconds, and then switches to full screen verbose mode. Is that centered window for verbose mode new to intel Macs? I never recall seeing it on my PowerBook.
    When i googled around for the "hi mem tramps" message, i found it might be linked to bad ram. I used memtest and did 3 passes to check the ram, and it found no errors.
    Are these messages in System.log normal?
    Thanks!

    Hi, Mike.
    First, please don't use the "scatter gun" or "post everywhere" approach. I see you've also post the same question here. I appreciate your urgent desire for help, but it would be very annoying to anyone answering questions here to spend time researching your question in one post, only to find it already answered in another place where it was also posted. The "scatter gun" approach is a good way to get all your future posts ignored.
    According to what I read in the second post of this topic on another forum, I suspect you may have a Startup Item that's causing the highlighted messages to be written to system.log. Perhaps some PowerPC code you may have migrated over to your Intel-based Mac if you used the Setup / Migration Assistant to move to the new Mac from a pervious Mac.
    There have been numerous posts about the tfp: failed on 0 message, which can be seen in this search of the Discussions. However, I suspect the explanation I've cited above fits your situation.
    If an errant Startup Item is the cause, my "Troubleshooting Startup and Login Items" FAQ can help you pin that down if such an item is causing the problem.
    As to hi mem tramps…, that may be normal. If you read this item and click on the link for dmesg you'll see a typical output someone else posted as, I suspect, an example of "normal."
    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.

  • 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

  • 10.4.9 Server Starts in Verbose Mode

    When I restart my G4 Server, it looks like it is starting like normal, shows the blue startup screen and says Mac Server is starting up, but when the bar reaches the end, it briefly goes to an all blue screen and then moves to a black screen with white text(verbose mode I think).
    After searching the forums, I tried forcing the mac os x startup by holding command and x during startup, but nothing changes. I have also tried entering:
    sudo nvram boot-args=""
    to boot up normally, but still no change. I have tried repairing the disk in disk utility, booting from an external hard drive, but still boots in verbose mode.
    Any help would be great.
    1.6GHz G5 iMac   Mac OS X (10.4.10)  

    Hi Dan-Cherokee:
    What happens if you boot from the installer disk?
    In the meantime try resetting the PRAM (ParameterRAM). Restart the server and hold down the command, alt, P and R keys at the same time. You should hear the start-up chime, keep them depressed until you hear the chime again, keep them depressed for a further start-up chime, now release the keys and immediately hold down the shift key. You will have to keep this depressed for some time as you are now booting in safe mode/boot. Eventually you will see the log in window with Safe Mode/Boot (in red) displayed, release the shift key and log in as normal, wait a few seconds and click on the trash icon, you should see a folder that has a long number for its name or possibly be called recovered items, delete this folder and reboot as normal. Safe Mode does a thorough check of your drive and directory as well as flushing system caches (this is what gets dumped into the trash).
    Hope this helps – Tony

  • Mac OS X v10.7 Lion always boot into safe boot after upgrade?

    I have recently upgraded my OS from snow leopard to lion and the upgrade process was smooth and no problems encountered.
    I am also running boot camp with windows XP installed in the same iMac.
    After the upgrade, my iMac almost always boot into safe mode whenever I switch it on and I need to restart it again and it will then return to its normal mode.
    I wonder anyone encounter the same problem and if so, please give me a hand to solve it.
    Thank you very much!

    Same problem here with my 2011 21" iMac that I purchased in mid July.
    I have a wireless keyboard, trackpad and mouse. When I power everything off and turn off the power strip then later turn on the computer it boots into Safe Mode.
    Also, the Wi-Fi (formerly Airport) icon in the menubar is just the empty outline and clicking on it gives me the message "Wi-Fi: No hardware installed". Rebooting fixes this.
    I spent an hour on the phone with an Applecare manager who had me run Disk Utility repair after booting into the recovery partition. Disk Utility found some disk errors, which I thought was strange for a new computer, and repaired them.
    The problem still exists though.

  • Delete folders in verbose mode?

    Hi. My laptop won't boot properly because the disk is full.  I can boot in verbose mode to type commands.  What is the command to delete the main Movies folder?  Or main Downloads folder?

    Actually it's Single User mode, it's  Verbose when it's booting and you can see it but have no control.
    What you want to do your better off doing this. Single User mode is dangerous and can have unexpected issues from human error. Also you can keep the files.
    Create a data recovery/undelete external boot drive

  • 10.6 Verbose mode stops at ACPI_SMC_PlatformPlugin::start....

    Macbook not booting and stalls at spinning gear.
    Tried many things but ended up booting into verbose mode and it stops at
    ACPI_SMC_PlatformPlugin::start - watiForService(resourceMattching(AppleIntelCPUPowerManagement) timed out.
    Previously in the boot, it says it failed to load that kext because the link failed.
    - Tried repairing permissions
    - Netbooting into AST and running MRI. No errors. Reset SMC and NVRAM. No change.
    - Swapped RAM
    - Made image and restored to a new hard drive. Same problems.
    - Booted different computer from the harddrive. Still get spinning gear.
    - Swapped hard drive for a working one from another laptop and it booted fine.
    Any thoughts before I wipe the HD it and start from scratch?

    Dont wipe the hard drive!
    Just had this problem on a macbook pro 2011 at my work (computer repair business).  The problem occurred after switching out the hard drive and hard drive cable.  Tried booting an Apple Hardware Test, by install disk, or by bootable USB OSx.  Each time the verbose popped up before completing boot and ended at a failure of the load of the driver regarding cpu power management. 
    Ultimately, the problem was a corruption of the firmware, which is embedded in flash-based rom chips on the logic board.  The Apple website has the firmware for your model available and it should boot from the disk without trouble. 
    Incidentally, all attempts to boot failed except when booting to the OSx Lion full install from USB.  This alone seemed to bypass the corruption.  Regardless, the firmware restore should do it. 
    So don't wipe your drive.

  • How to permanently boot up in verbose mode?

    Hi,
    I want to always boot up OS X Mavericks (10.9.2) in verbose mode (debug mode) as I pressed Cmd+V everytime.
    I remember an old command which I used on Snow Leopard for doing this:
    « sudo nvram boot-args="-v" »
    but I don't know if it's still valid on Mavericks!!
    The command « nvram -p » works and doesn't show any "-v" verbalization in the "boot-args" section, so I'm currently thinking my command is still valid (it does still show other commands, though).
    But I need your help, Apple experts! Can you confirm this?
    Thanks in advance,
    Tyrexionibus
    Message was edited by: Tyrexionibus

    Restart the computer. At the chime press and hold down the SHIFT key until you see the spinning gear below the Apple Logo. You should also see a progress bar appear. Booting into Safe Mode takes much longer than a normal startup.

  • ALWAYS BOOTS UP IN SAFE MODE

    MY MAC ALWAYS BOOTS UP IN SAFE MODE. I REPLACED THE KEYBOARD DUE TO A JAMMED SHIFT KEY WHICH WAS CAUSING IT TI DO THE SAME THING, BUT ITS DOIN IT AGAIN. CAN SOMEONE HELP PLEASE?

    ACTUALLY IT BOOTS THE RIGHT WAY IF I LEAVE THE KEYBOARD OFF UNTIL THE SIGN IN SCREEN COMES UP. AND YES IT IS A WIRELESS. IF I TURN THE KEYBOARD ON BEFORE I TURN THE COMPUTER ON IT WILL BOOT IN SAFE MODE. IS THERE ANYTHING ELSE THAT I CAN TRY, OR SHOULD I JUST SAY FORGET IT, AND WAIT UNTIL THE SIGN IN SCREEN COMES UP BEFORE I CUT IT ON?

Maybe you are looking for