Hello,
What you've got here is your Mac is trying to load what's called a "kernel extension". In this case, it's ACPI, which is a power management driver. Either the permissions are corrupted, or the file itself is.
What I would suggest at this point is to insert the OS X disk; holding down the 'C' key while booting. Proceed with installation, and under "Install type" choose "Archive+Install". This will preserve your data and settings, but will archive all the system files into a compressed folder.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
ya but i dont have cd..os...its broken,,,:surprised
Your installation disk is broken too, eh? You'll just have to buy a new copy of Tiger then.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
- What kind of Mac are you using? Is it Intel-based, or is it one of the older PowerPC-based Macs?
- When did this start happening?
- Are you holding down the 'C' key the whole time your Mac is booting? What happens if you hold down the Option key?
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
>This happened right after I ran an auto recommended "MacBook Pro SMC Firmware Update"
What happened, exactly? When you run the firmware installer, it doesn't actually update, it simply places the files into a special EFI partition, which are installed when the Mac is rebooted. Did this ACPI error start occurring immediately after you ran the firmware installer, or did you actually see the computer installing the firmware during the boot process? Did it complete successfully?
To be truthful, it sounds like your system is hosed. Firmware is a beautiful thing because it can be updated (unlike a PC BIOS), but on the other hand if you mess it up, there's no way of restoring it. That's why Apple warns never to reboot or switch off a Mac while it's installing firmware updates, and to have it plugged into a reliable power source (rather than battery).
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
One more thing you can try. Is your iMac by any chance Intel-based? If so, you can use Carbon Copy Cloner to copy the contents of your iMac's hard drive to your MacBook Pro. It won't do anything if the firmware's fried, but if it isn't, it should work. If your iMac isn't Intel-based, then try to find a Mac that is.
And replying to the PM that you sent earlier, no, if the firmware is messed up, there's not much you can do about it. It's essentially a feedback loop: the firmware needs itself in order to update.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
Glad to hear that it's working, and yes, I would definitely agree that your firmware is fine. For some reason, your Mac wasn't booting off the DVD -- my initial suspicion. Why that is remains a mystery, as holding down the 'C' key should have been sufficient. Regardless, congratulations on getting it working and booted.
>So, i plan to just get a REAL install DVD and start fresh.
Yes, an upgrade disc isn't enough. You need the DVD that came with your MacBook Pro (and it's worth noting that it's not possible to buy a real install DVD from Apple; they only sell upgrade DVDs).
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
Hello,
It's actually possible to delete files from your hard drive using the OS X installation disk. However, you must use some Unix shell commands to accomplish this. After you've booted off the installation disk, from the Utilities menu, choose Terminal. I can give you a brief tutorial on how to delete files using Unix commands:
- When working at the shell, always hit 'return' or 'enter' to execute the command that you've typed. To start with, run the following command:
cd "/Volumes"
This command changes the current directory to /Volumes.
- Now, list the contents of this directory:
ls
- Most likely it will list the name of your hard drive. Enter this directory by typing the following:
cd "Macintosh HD"
Or whatever name your hard drive is.
- Now list the contents of your hard drive:
ls
At this point, you should see the pattern. cd to a directory, and ls the contents. To go back (up) one directory use this command:
cd ..
- With me so far? Now, go to a directory that contains files or folders you want to delete. To delete a file, do the following:
rm "essay.txt"
That command would delete a file named essay.txt .
- Deleting an entire directory is similar:
rm -r "my directory"
That would delete a directory named my directory and all its contents.
- When you're done, quit the Terminal, and you can continue installing OS X.
I hope that made sense. If you're confused, or have problems with the instructions, please ask, and I will do my best to further clarify them.
John A
Vampirical Lurker
7,633 posts since Apr 2006
Reputation Points: 2,233
Solved Threads: 340
Skill Endorsements: 7
I have th same problem
Won't boot up after aPple logo screen. Monitor just says no signal
Troubleshoot
- ram
- CPU
- replaced mother board
- graphics card
- did system hardware test ( everything works )
- put hard drive in slot 1,2,3 and 4 . No change
- acpi error trying to boot in safe mode
- single user more works ( hard drive one, seems to be working fine)
- cant load from disk ( with hard drive in and out)
- Can't load from external drive ( kernal panic screen comes up)
- put new hard dive in and tried to install os ( no change )
- basically did everything but power supply.
Is it a os or hardware ? Stress!!!!!
What do yu think I should do?
I'm running Mac pro tower.
Have you tried loading your system in target disk mode at boot and seeing if you can access it using firewire connection as an external HD. At least this way you could look for corrupted files in your init.
Check your RAM riser cards for blown capacitors, that could effect all ECC-ram modules and cause a kernel panic. From my experience I have had more kp's from bad ram or a ram missmatch than for any other reason.
http://osxbook.com/book/bonus/ancient/whatismacosx/arch_startup.html
dioioib
Junior Poster in Training
61 posts since Feb 2011
Reputation Points: 14
Solved Threads: 2
Skill Endorsements: 0