Kernel Panics????

[mattpen]

Whenever i try to boot into 6c75 i get a kernel panic during startup, any suggestions?

[AlphaTech]

Just for S&G's, have you run fsck -y?? What system are you trying to run 10.2 on??? Have you made any hardware changes lately??? More info is needed in order for us to give any additional assistance... :p :D

[mattpen]

it's an older iMac i tried running fscl -y and it said that everything appeared to be ok. When i install 10.2 which option should i use (archive, erase ...etc.)?

[AlphaTech]

How about wait for the official release??? You didn't say if you made any hardware changes recently... How much memory is inside that older iMac (which iMac is it?). You may not meet the system requirements to run 10.2.


BTW, it's fsck -y ;) did you boot from the command+s?? or run it from within OS X? Do the boot version...

[mattpen]

sorrry i meant fsck -y, and no i haven't made any changes to hardware. I had to boot into single user because i was getting a kernel panic every time the computer started, meaning right after the smiley mac. It has 160mb of ram.

[firewire2001]

Originally posted by mattpen
sorrry i meant fsck -y, and no i haven't made any changes to hardware. I had to boot into single user because i was getting a kernel panic every time the computer started, meaning right after the smiley mac. It has 160mb of ram.

a while back a lot of ppl were having trouble with os X and odd amounts of memory... 160 mbs of memory is definately an odd amount (the most normal increments are: 128,256,512...)...

that could be yer problem right there..

[mattpen]

well it worked in the jaguar developer build

[AlphaTech]

It could be that old 32MB chip you have... what brand is the 128??? [firewire2001, what do you get when you add 128+32??? :p]

Do you get the same issue under 10.1.x?? I'd say you have a hardware issue there, most likely the memory is the culprit, since the fsck -y came back clean.

Try holding down the apple+option+o+f on boot and then type in 'reset-all' when you get the prompt screen (booting into open firmware).

You still haven't told us which iMac this is... Speed, color, tray or slot loading... come on Bubba...

BTW, there is no such animal as a 'mb' memory chip... they are ALL 'MB'. :rolleyes:

[mattpen]

it's an older 333mhz, tray loading, blueberry

[AlphaTech]

Try installing it without the 32MB memory... check and see what brand the 128MB is as well. If it is a Microtek, you need to get good memory... those chips are sub-par/standard. I'd also suggest cranking the memory to at least 512MB before going forward... with 384MB the bare-bones minimum.

Did you reset the open firmware yet???

[mattpen]

i tried that resetting of the firmware with no luck, any other ideas? i'm really starting to get used to that new kernel panic screen

[AlphaTech]

Check the memory...

How does it run with 10.1.x???

[mattpen]

it's fine in 10.1.5

[AlphaTech]

Then I would say just wait for the full/official release to come out. IF your 333MHz iMac is on the list of supported hardware then, and meets the memory requirements, you can call Apple about it. Until then, just chill with 10.1.5.

Oh, and I really would upgrade the memory in that old dog...

At work, we are getting ready for OS X, by adding 256MB to ALL iMac's. Just about all of them are now at 320MB or more (a few are at 288MB, but not all that many).

[mattpen]

well thanks for the help i better get started on reinstalling 10.1

[mongolikescandy]

Did you resolve your panics?

I'm being battered by five or so a day, on a 1G dual G4 w/ 1.5 GB.

10.2.6; an HP 6110 all-in-one USB hooked to a small USB hub, then to the 'puter. A microtek scanner plugged to the keyboard USB jack.

All worked just hunky until July 19, when all hell broke loose. Reseller had to replace hard drive, the CPU module twice, the logic board twice, the fan. Actually, the tale of what they swapped out changes with every call. But I've tested superdrive, memory sticks, cards, all to no effect.

Operating theory at the moment is USB is the culprit.....

mongo