Hi,

I'll cut to the chase:

G4, dual 1 gHz, OSX 10.4.7, 2 internal IDE drives, 1 firewire, 1.25g RAM.

Automatic sleep used to be OK, though it was never 100%. Even after 
upgrading it still worked for a while, however intermittently. Now it's 
just stopped. Screen goes blank, machine doesn't go into sleep at all 
anymore.

Pardon the attitude, but...what? We're at 10.4.7 now. Is this thing out 
of beta yet?

<<<<< The One True Robb >>>>>>  

In article <robbscott-85CD2E.01072504082006@comcast.dca.giganews.com>,
 Robb Scott <robbscott@comcast.net> wrote:

> Hi,
> 
> I'll cut to the chase:
> 
> G4, dual 1 gHz, OSX 10.4.7, 2 internal IDE drives, 1 firewire, 1.25g RAM.
> 
> Automatic sleep used to be OK, though it was never 100%. Even after 
> upgrading it still worked for a while, however intermittently. Now it's 
> just stopped. Screen goes blank, machine doesn't go into sleep at all 
> anymore.
> 
> Pardon the attitude, but...what? We're at 10.4.7 now. Is this thing out 
> of beta yet?

Must be, because my wife's almost identical machine (more memory) sleeps 
fine and always has. Sounds like yours has been having some degree of 
trouble for a long time. What PCI cards and USB devices do you have 
installed? Any 3rd-party kernel extensions? What have you tried so far 
in terms of troubleshooting?

-- 
What I write is what I mean. I request that anyone who decides to respond
please refrain from "disagreeing" with something I didn't write in the first
place.

In article <uce-E0FAB6.04584104082006@comcast.dca.giganews.com>,
 Gregory Weston <uce@splook.com> wrote:

> In article <robbscott-85CD2E.01072504082006@comcast.dca.giganews.com>,
>  Robb Scott <robbscott@comcast.net> wrote:
> 
> > Hi,
> > 
> > I'll cut to the chase:
> > 
> > G4, dual 1 gHz, OSX 10.4.7, 2 internal IDE drives, 1 firewire, 1.25g RAM.
> > 
> > Automatic sleep used to be OK, though it was never 100%. Even after 
> > upgrading it still worked for a while, however intermittently. Now it's 
> > just stopped. Screen goes blank, machine doesn't go into sleep at all 
> > anymore.
> > 
> > Pardon the attitude, but...what? We're at 10.4.7 now. Is this thing out 
> > of beta yet?
> 
> Must be, because my wife's almost identical machine (more memory) sleeps 
> fine and always has. Sounds like yours has been having some degree of 
> trouble for a long time. What PCI cards and USB devices do you have 
> installed? Any 3rd-party kernel extensions? What have you tried so far 
> in terms of troubleshooting?

Sleep has been problematic for me since 10.2x OS X . Peripherals USB & 
SCSI  perhaps FireWire etc do seem to be involved in big ways with sleep 
problems. 

I have a PCI USB 2.0 card that if ANYTHING is connected & powered to it 
also kills sleep producing that blank screen fans running FORCE SHUT 
DOWN only way out as it won't wake.

You might at least try or look at NMS Sleep Assist. That seemed to work 
for me a while back (10.4.3???). I am currently on 10.4.7 but usually 
just manually SLEEP my G4s anymore.

Morenuf
-- 
morenuf@nobodyhome.com.invalid

In article <uce-E0FAB6.04584104082006@comcast.dca.giganews.com>,
 Gregory Weston <uce@splook.com> wrote:

> Must be, because my wife's almost identical machine (more memory) sleeps 
> fine and always has. Sounds like yours has been having some degree of 
> trouble for a long time.

Yeah, on & off. In the past, trashing the Energy Saver prefs and 
re-setting fixed things for a time.

> What PCI cards and USB devices do you have installed?

USB: Epson printer, Midiman Midisport (Midi interface), keyboard & 
mouse. PCI, not a thing

The Midisport is a new addition, but I'm seeing the problem even when 
it's powered down. I'll unplug it, and might try un-installing its 
driver.

> Any 3rd-party kernel extensions?

Umm, err, stammer...not sure exactly what one of those might be.

>  What have you tried so far 
> in terms of troubleshooting?

I've disabled Compost*, and powered down the external FW drive. Tried 
variations on the Energy Saver settings. The OS is newly installed; my 
main disk went down recently and I'm just getting back up after 
restoration.

It's morning now, and I'm much calmer than when I first fired off that 
message. Thanks for the focus - I'll try a few things, and report back 
after the weekend.

Oh, and thanks again for Compost, one of the most elegant pieces of 
software ever written.


          <<<<< The One True Robb >>>>>>  

* The FW drive has almost 80,000 files in the trash, and Compost has 
been munching on those for a few days, so that was my first thought.

In article <robbscott-0987EE.10210604082006@comcast.dca.giganews.com>,
 Robb Scott <robbscott@comcast.net> wrote:

> > Any 3rd-party kernel extensions?
> 
> Umm, err, stammer...not sure exactly what one of those might be.

If you run System Profiler (from /Applications/Utilities) and click on 
Extensions within the Software group in the Contents list you'll 
eventually be presented with a list of all sorts of little extra 
software components that make your system work the way it does (barring, 
you know, hardware quirks and other anomalies). Most of them come from 
Apple as part of the stock OS install, but I'd imagine a fair percentage 
of people also have 3rd-party ones floating around and some of them, if 
they're not up-to-date or have a bit of sloppiness to the code, could 
theoretically cause local problems such as you're seeing. Unfortunately, 
there's no way to see the vendor for the extensions, so quickly 
filtering out the stock ones isn't easy. But on the machines I have 
access to the list isn't terribly long and about half of them have names 
that start with "Apple." Most if not all of the ones that start "IO" are 
also stock.

> > What have you tried so far  in terms of troubleshooting?
> 
> I've disabled Compost*, and powered down the external FW drive. Tried 
> variations on the Energy Saver settings. The OS is newly installed; my 
> main disk went down recently and I'm just getting back up after 
> restoration.

Hmm. Unless some of what you do in setup has become so automatic that 
you installed some 3rd-party drivers without even thinking about it that 
does tend to rule out a software cause.


> * The FW drive has almost 80,000 files in the trash, and Compost has 
> been munching on those for a few days, so that was my first thought.

Not an unreasonable guess, although it _shouldn't_ be the cause. Part of 
the goal in Compost is that it should be subject to you and your 
machine, not the other way 'round.

-- 
What I write is what I mean. I request that anyone who decides to respond
please refrain from "disagreeing" with something I didn't write in the first
place.

In article <uce-842A55.07225305082006@comcast.dca.giganews.com>,
 Gregory Weston <uce@splook.com> wrote:

> In article <robbscott-0987EE.10210604082006@comcast.dca.giganews.com>,
>  Robb Scott <robbscott@comcast.net> wrote:
> 
> > > Any 3rd-party kernel extensions?
> > 
> > Umm, err, stammer...not sure exactly what one of those might be.
> 
> If you run System Profiler (from /Applications/Utilities) and click on 
> Extensions within the Software group in the Contents list you'll 
> eventually be presented with a list of all sorts of little extra 
> software components that make your system work the way it does (barring, 
> you know, hardware quirks and other anomalies).

Well, damn, lookee dat. Hadn't noticed. 

Wonder if there's something like the old OS9 Extensions Manager for 
these. Gotta check VTracker...

Thanks again!

       <<<<< The One True Robb >>>>>>