Of so many years of using my Ibook, I had never really used it for very important stuffs. I only use it for some typing, some movies, surfing and all, so no very important data in it. Until recently, as I was doing the layout for my church’s Harvest mag, I decided to use Pages to do it and skip the messy Illustrator. It was the last night as I rush the work, suppose to send it for printing the next day, when I thought I needed a ram upgrade. So without much thinking, I just removed the keyboard and took out the ram, without following Apple’s intructions. Means I didn’t even unplug for 30 min and remove the battery! Foolish…
So removing the ram, I just wanted to check the model number. Then I put it back and it was a pretty simple procedure. Unfortunately, a few minutes upon startup, I suffered a Kernel Panic attack!
I had no idea what it was at first, but knew it has got to do with my wrong ram placement or something. Although the Ibook detected the ram correctly. This screen keep popping out and I restarted the Ibook like more than 5 times! Panic! That’s more me…coz I got all these files in it that I can’t continue editing on the Windows.
The next day, I read some forums and asked around how to settle this problem, only then I found out that it’s called Kernel Panic, which happens on Linux based machines. Hhm. I then downloaded Rember, and open source software used to test the ram, and then run the hardware test found on the Mac CD. Basically the steps are:
1) Recheck that the ram was installed right
2) Run Rember (this takes a long time…..)
3) Boot to your apple disk for your OS X hold the option button down and boot to disk and run your disk utility and repair permissions.
Amazingly after running these tests, the Ibook was healed. What was the problem man?
A couple of days ago, this website wrote that the problem could lie with the Airport and the recent Mac Os X 10.4.10 upgrade. Notably when the prob happen I was online. But after that I ran the tests offline. What’s the connection here? So, I guess I wasn’t alone in having kernel panics over the weekend :P.