| | |
kernel panic
![]() |
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.
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.
"Technological progress is like an axe in the hands of a pathological criminal."
All my posts may be freely redistributed under the terms of the MIT license.
All my posts may be freely redistributed under the terms of the MIT license.
•
•
Join Date: Oct 2006
Posts: 21
Reputation:
Solved Threads: 0
•
•
•
•
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.
"Technological progress is like an axe in the hands of a pathological criminal."
All my posts may be freely redistributed under the terms of the MIT license.
All my posts may be freely redistributed under the terms of the MIT license.
•
•
Join Date: Nov 2007
Posts: 4
Reputation:
Solved Threads: 0
Having the same problem...
However, when I attempt to boot from an install disc, the dvd drive spins-up but i can never get to install set-up screen. I just get the dark gray Shut Down message that starts with:
panic(cpu 0 caller 0x0039BC83): unable to find driver for this platform: "ACPI"
Can't seem to ever get past it...
Thanks,
Lee
However, when I attempt to boot from an install disc, the dvd drive spins-up but i can never get to install set-up screen. I just get the dark gray Shut Down message that starts with:
panic(cpu 0 caller 0x0039BC83): unable to find driver for this platform: "ACPI"
Can't seem to ever get past it...
Thanks,
Lee
•
•
Join Date: Nov 2007
Posts: 4
Reputation:
Solved Threads: 0
Okay. I am on an Intel 1.8MHz MacBook Pro with OS x 10.4.6, 512MB RAM, 80GB HD.
I CANNOT get past the "panic(cpu 0 caller 0x0039BC83): unable to find driver for this platform: "ACPI"" error message. Even with honding "C" with a re-install CD inserted and Even when I attempt to log into the Firmware, I get to a point where I can't even type in a command.
Two things:
1. This happened right after I ran an auto recommended "MacBook Pro SMC Firmware Update"
2. I also have an iMac and I mounted the MacBook Pro as a drive and ran the repair disk utility and the hard drive is ALL GOOD.
What next?
Thank you a million in advance.
-Lee
I CANNOT get past the "panic(cpu 0 caller 0x0039BC83): unable to find driver for this platform: "ACPI"" error message. Even with honding "C" with a re-install CD inserted and Even when I attempt to log into the Firmware, I get to a point where I can't even type in a command.
Two things:
1. This happened right after I ran an auto recommended "MacBook Pro SMC Firmware Update"
2. I also have an iMac and I mounted the MacBook Pro as a drive and ran the repair disk utility and the hard drive is ALL GOOD.
What next?
Thank you a million in advance.
-Lee
>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).
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).
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.
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.
![]() |
Similar Threads
- wont start up (OS X)
- Mac OS X on AMD - kernel panic? (OS X)
- How to fix virtual pc 2004 kernal panic when installing linux (Windows Software)
- Post Sleep crashing (OS X)
- Installing Redhat 9.0 (*nix Software)
Other Threads in the OS X Forum
- Previous Thread: hoping someone can please help
- Next Thread: Leopard 10.5.1 issues anyone?
| Thread Tools | Search this Thread |
Tag cloud for OS X






