Originally posted by joe:
...
My take on the deep sleep problem:
1 - my original 500Mhz Apple cpu didn't have it.
2 - my "unsupported" dual 500 Sonnet cpu didn't have it when I hacked in my Cube.
3 - but my 1GHz PL goes into a coma if I even try.
I miss sleep mode but am happy with my 1Ghz PL upgrade otherwise. It's a helluva lot faster than my previous dual 500 for most things (actually - my 1GHz PL is faster at everything I own except Quake3). I can still set the hard drive and display to sleep. Of course I hope PL can get sleep mode working. But I'd prefer a beefier VRM and dualie upgrades first 
.......joe
The "Powerlogix sleep bug" seems to affect only the single 1GHZ and single
1.2 GHZ. The machine is frozen the second the disc spins up. No reaction
what so ever, keyboard is not functioning etc. Hard reboot is only solution
to this.
True, other CPU configurations and stock apple CPU's may experience almost
similar problems from time to time, but often of a slightly different
character/syptoms (the screen does not wake, but otherwise the machine
functions), and it is not a consequent failure explicitly linked to the
type of CPU.
Check out xlr8yourmac's database. As far as I could see, all 1 and 1.2 GHZ
PWL CPU's suffered from the sleep bug. 800's and dualies don't.
As I have said before, from a logical point of view, this should quite
clearly indicate that there is something wrong with the PWL upgrades. Of
course, PWL can always claim that their CPU's would work if Apple adapted
OSX to accomodate their special "PWL's sleep bug", but I believe that a
company that sell upgrades should rather meet the specifications and
requirements of the host system rather than the other way around.
I find it intrigueing that they claim the problem is with Apple while they
at the same time (allegedly) have said that they have spent $ 20K trying to
figure out what's wrong without solving the problem. Clearly, the problem
is tied to their upgrades, they don't know whats causing it, which in turn
leads to the conclusion that there is no valid basis for their claim that
this is a fault of the OSX. BTW, OS 9 shows a similar error for most people
with PWL CPU's mentioned.
As the case stands, PWL has disappointed me with their lack of will to
claim responsiblity or at least provide an explanation as to why this
happens almost without exceptions with their upgrades while not with
sonnets etc. (Sonnet btw. has allegedly claimed that they knew about this
potential problem and solved it before release of their product).
Sophus (I really, really miss sleep...)
I wonder what the hold up is for those new VRMs? I'd love to have a dualie Cube again!
Top
