PDA

View Full Version : What a week!




Zeke D
Sep 1, 2012, 12:35 PM
Most of you know I have a barely alive PowerMac G5. Well it died completely this week. Poop happens right? It sucks but another regular on these forums is sending me a replacement because he is awesome. I figure, it will eventually get here, so I drag out my 1GHZ eMac until the G5 gets here. Guess what? The power button on my eMac has failed! I tried hooking up a G3 keyboard with a power button to see if that old power on the unit, but it doesn't seem to do anything. What a poopy week! Any suggestions on getting the keyboard to power on the eMac? Feel like commiserating?



Intell
Sep 1, 2012, 12:42 PM
Apple got in trouble with those keyboards because they had live power over them when the machine was off. They only turn on the G3 iMacs as well. If you're brave, you can take off your eMac's shell and wire an external power button. The switch is just two wires that are connect to power on the machine.

Zeke D
Sep 1, 2012, 12:46 PM
Apple got in trouble with those keyboards because they had live power over them when the machine was off. They only turn on the G3 iMacs as well. If you're brave, you can take off your eMac's shell and wire an external power button. The switch is just two wires that are connect to power on the machine.

Yeah, I could do that, but it will look ghetto! I just wish my powermac G4s were better than 733mhz. FCE4 drags on those.

Intell
Sep 1, 2012, 12:49 PM
You could always get real fancy and wire up a capacitive sensor like on the Cube.

Zeke D
Sep 1, 2012, 12:54 PM
The Adventure continues:

Interval Since Last Panic Report: 2830077 sec
Panics Since Last Report: 1
Anonymous UUID: 79354846-E520-4037-994E-A9AFF1D64F01

Sat Sep 1 10:49:14 2012


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000000C PC=0x000000000080D38C
Latest crash info for cpu 0:
Exception state (sv=0x60c1c000)
PC=0x0080D38C; MSR=0x00009030; DAR=0x0000000C; DSISR=0x40000000; LR=0x00805EB0; R1=0x6083E920; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x708492C9
backtrace terminated - unaligned frame address: 0xBE48B911

Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon9700(5.4.8)@0x7ef000->0x84bfff
dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0x7d7000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x644000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x7b1000
Proceeding back via exception chain:
Exception state (sv=0x60c1c000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x60c1e280)
PC=0x92711078; MSR=0x0200D030; DAR=0x087A301C; DSISR=0x0A000000; LR=0x92717FA0; R1=0xF0215270; XCP=0x00000030 (0xC00 - System call)

BSD process name corresponding to current thread: Unknown

Mac OS version:
9L31a

Intell
Sep 1, 2012, 12:57 PM
Bad capacitors. A kernel panic pointing to the GPU usually is caused by bad capacitors.

Zeke D
Sep 1, 2012, 01:06 PM
Bad capacitors. A kernel panic pointing to the GPU usually is caused by bad capacitors.

Hmmm, I'll have to check it out. I need it tomorrow, so I don't dare turn it off until after.

Intell
Sep 1, 2012, 01:07 PM
If it is the capacitors, it could panic at anytime without warning or cause.

Zeke D
Sep 1, 2012, 01:09 PM
If it is the capacitors, it could panic at anytime without warning or cause.

Hopefully it will happen while the lady is here to edit video.

Intell
Sep 1, 2012, 01:12 PM
I seem to remember one of my eMacs with bad capacitors panicking more when the screen saver was running. Seemed that the more screen activity stressed it to the panicking point.

Zeke D
Sep 1, 2012, 01:16 PM
I seem to remember one of my eMacs with bad capacitors panicking more when the screen saver was running. Seemed that the more screen activity stressed it to the panicking point.

I blame politicians... No wait, lawyers!

I applied for an IT position with the town. It was nice filling out an application and not hiding my education. Anyway if that job happens, I will finally be able to afford some gear.

Intell
Sep 1, 2012, 01:21 PM
I think the trouble with the bad capacitors was tracked down to corporate espionage. It effected many manufactures that used capacitors from that maker of the capacitors who used them from about 1999-2005.

Zeke D
Sep 1, 2012, 01:24 PM
I think the trouble with the bad capacitors was tracked down to corporate espionage. It effected many manufactures that used capacitors from that maker of the capacitors who used them from about 1999-2005.

I'm pretty sure the batch from '99 is all right, only the post Y2K ones you have to worry about.

Davy.Shalom
Sep 1, 2012, 02:16 PM
Bad capacitors. A kernel panic pointing to the GPU usually is caused by bad capacitors.

Yeah open it up to check if the capacitors are bulging and/or leaking.