[CUBE] PL upgrade

[James Knight]

Thanks Guy that's useful.

However what we have here is a coma rather than a wake-delay and it occurs
in OS9 as well as X.

The symptom is that the computer will appear to react to the wake-up call -
hard disk will leap into life but the display stays off. The computer itself
is I think still asleep as it does not respond to things like the eject
button or volume keys (which would give feedback other than just via the
display). This happens 100% of the time - not an intermittent issue like
some sleep problems.

For what it's worth I have installed a brand new OS on an erased hard drive
and still have the same issue. In fact I've booted from the OS 9 CD and
still the same - coma every time.

James


-- 
James Knight
Norwich, UK

j.knight at kb-group.co.uk




on 15/1/03 4:34 pm, John Guy at john.guy at btclick.com wrote:

> This may or may not be related, I have had problems in waking up my cube
> numerous times....
> Purely by empirical observation...
> 
> ... if a previous system crash/error has occurred and I have NOT run Norton
> and fixed permissions it can take up to ten mins to wake up, if indeed it
> does wake up.
> Conversely if Norton has been run (disk doctor) and fix permissions the cube
> wakes up within 30 secs max.
> 
> Educated guess, when the cube is attempting to wake from sleep the OS would
> look to access various files to refresh and update the screen, active memory
> and any application and or data changes...if they are "broke" endless loop
> of trying to access unable to access etc...
> 
> Also another thought, the wake up can linked to the user data i.e. enter
> password on wakeup, if the user info is wrongly permissioned or the log file
> or something else prevents access, then maybe that is another avenue to
> explore
> 
> If the disk and or permissions are suspect then either way they would not
> have access to, rights to, and/or the file/data location is corrupt or the
> process the OS is trying to execute is not viable.
> 
> It has to be a fundamentally simple issue that creates a moebius style error
> 
> Just my 2 penith' worth
> 
> John Guy
> 
> Feel free to shoot these thoughts down in flames as long as you have a
> better explanation.
> 
> I.e. Lets fix/identify the problem rather than argue who we should be
> waggling our fingers at...
> 
> JG
>>> 
>>> So here's what we know: some stock Apple machines have sleep problems. Some
>>> PL upgraded machines have sleep problems. Some machines have no problems
>>> with the Apple proc, but as soon as the PL card is installed, problems
>>> occur.  We still don't know why on either count, but it's clear there's
>>> something "off" because it's hard to blame Apple for a problem that only
>>> exists in some machines when a PL card is installed and it's hard to believe
>>> it's a kernel issue, when the problem spans across multiple OS versions.
>>> 
>> 
>> Actually you forgot one scenario: some PL upgraded machines have no
>> sleep problems whatsoever. The problem is, how does one pinpoint the
>> problem when it doesn't manifest itself in every instance? If there
>> was a definitive problem with our cards in terms of hardware, it
>> should occur every time. Yet it does not. That's what makes this such
>> a time consuming, frustrating engineering conundrum.
>> 
>>