[eins]

I have an ibook Model: A1133 g4 1.33 ghz 1.5 gb ram, 40 gb ram and whenever I turn on it on I get a multilanguage kernel panic. I have reinstalled 10.4 however I still get the kernel panic? Any ideas fellas?

[reader50]

Post the panic text here, please. We can usually tell something from the error messages.

[Ω]

Not sure the OP is getting far enough to be able to post the error log.

A few things to try (from easy to more complex):

Unplug everything attached to the iBook
Try booting in safe mode
Try booting in verbose and see if you can determine where it panics
From your install disks run disk utility - cant remember if it has hardware test
Start pulling RAM to see if a bad stick is a culprit.

This is by no means a complete/correct list, but hopefully you can get to point where you can get to the logs so the issue can be isolated.

[eins]

4816/width/350/height/700[/IMG]

I posted a pic of the kernel panic above. the message says: You need to restart your computer. Hold down the power button for several seconds or press the restart button.

Unplug everything attached to the iBook Cannot unplug because battery is not charged.
Try booting in safe mode Yes I find myself in safe mode now what?
From your install disks run disk utility - cant remember if it has hardware test cd drive does not work
Start pulling RAM to see if a bad stick is a culprit. tried pulling ram and still got kernel panic

What now guys?

[eins]

help anyone

[eins]

help anyone

[Ω]

So when you are booting in safe mode are you still getting the kernel panic?

What we are trying to get to is the console logs so you can post something that is more meaningful than the photo above.

[reader50]

If the system is stable in safe mode, then you can reach the panic log at /Library/Logs/panic.log - it will contain the detailed backtrace of the last panic.

If you're not stable in safe mode, boot in verbose mode (command-v during startup), and jot down the text that remains on screen after it panics.

[eins]

I booted in safe mode and found the panic log:

wed dec 31 18:01:06 1969
panic (cpu 0 caller 0x000A8B80): Uncorrectable machine check: pc =
000000000086B508, msr=0000000000149030, dsisr= 42000000, dar=
00000000E009C000
AsyncSrc= 0000000000000000, CoreFIR= 000000000000000
L2FIR=000000000000000000 BusFir=000000000000000

Latest stack backtrace for cpu 0:
Backtrace:
0x00095564 0x00095A7C 0x00026838 0x000A8B80 0X000A7E10
0X000AB880
Proceeding back via exception chain:
Exception state (sv=0x32021C80)
PC=0X0086B508;MSR=0x00149030; DAR=0xE009C000;
DSISR=0x420000000; LR=0x0086B4F8; R1=0x21F4BCC0; XCP=0x000000008
(0x200-Machine check)
Backtrace:
0x0086B4F8 0x0086B1D0 0x0087EBB0 0x002CDC8C 0x002CCB54 0x000A9654
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort3(360.4)@0x841000
dependency:com.apple.iokit.IONetworkingFamily (1.5.0)@0x59e000
dependency:com.apple.iokit.IOPCIFamily(1.6)@0x4520 00
Exception state (sv=0x3BEDB500)
PC=0x0000000000;MSR=0x0000D030;DAR=0x00000000
DSISR=0x00000000; LR=0x0000000000; R1=0x000000000; XCP=0x000000000000
(Unknown)

Kernel version:
Darwin Kernel Version 8.0.0:Sat Mar 26 14:15:22 PST 2005; root:xnu-792.obj-1/RELEASE_PPC

[reader50]

Remove the airport card and try to boot normally.

[Ω]

Originally Posted by eins 

wed dec 31 18:01:06 1969

This line interests me.

Wondering if you need a new PRAM battery.

[eins]

I disabled the airport card and the kernal panics stopped however no I dont have any internet? How can I get internet?

[eins]

help anyone

[reader50]

Use an ethernet cable to your router. In the meantime, I'd use a cloth to clean the airport card contacts. Both on the card, and in the notebook. Either the card has gone bad, or it was experiencing erratic connection. A cleaning just might fix things on the cheap.

[eins]

can this airport problem get fixed with software?

[eins]

help anyone

[Spheric Harlot]

Originally Posted by eins 

can this airport problem get fixed with software?

No. It is a hardware problem.

Have you tried cleaining the contacts, as suggested above?

If that doesn't work, you either buy a new Airport card and hope it was the card and not the socket, or you connect to the internet via Ethernet.