> > Seems like the kernel never fully recovered from the
> > first sleep. Does
> > switching to a 2.4 kernel, or perhaps another 2.6
> >kernel, improve things?
>
> Yeah, that's what I figured too... switching to 2.4
> does help. What I don't understand though is how or
> why it stopped working. It
Hi Michael,
Thanks for your reply.
> Seems like the kernel never fully recovered from the
> first sleep. Does
> switching to a 2.4 kernel, or perhaps another 2.6
>kernel, improve things?
Yeah, that's what I figured too... switching to 2.4
does help. What I don't understand though is how or
why
just churns away,
> the snooze light never comes on. (Except for the first
> closing after a reboot)
>
> 2) snooze will work once, after the machine has been
> rebooted, every time after "snooze" appears to do
> nothing and "snooze -f" will report: "PMU_IOC
t for the first
closing after a reboot)
2) snooze will work once, after the machine has been
rebooted, every time after "snooze" appears to do
nothing and "snooze -f" will report: "PMU_IOC_SLEEP:
Device or resource busy"
3) "pmud -d" reports before snoozing:
4 matches
Mail list logo
