Matej Cepl wrote:
> Tried just out of the box configuration of hibernate from Debian/testing
> and got this error with uswsusp:
And I may as well send my /etc/uswsusp.conf
# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
#early writeout = y
compute checksum = y
resume device = /dev
Matej Cepl wrote:
> suspend: Could not stat the resume device file
>
> Which is kind of weird because there is /dev/snapshot (I hope, that's the
> device file the error message is talking about -- the error message could
> use some love concerning clarificatioin):
Sorry, that was apparently broke
Jason Lunz wrote:
> Come to think of it, I wonder how many of the "in-kernel swsusp doesn't
> work but suspend2 does" reports this is responsible for.
Hmm, I won't argue against in-kernel swsusp that much (two years after
suspend2 and it finally seems to begin to work ;-)), but uswsusp broke my
co
Matej Cepl wrote:
> Do people usually use hibernate script or they run s2* directly? And BTW,
> could somebody point me to the working configuration of /etc/acpi (for
> Debian if it matters) for all power button, closing lid, etc.?
Tried just out of the box configuration of hibernate from Debian/t
[EMAIL PROTECTED] said:
> (aside from your fierce opposition to the competition, is there any rational
> reason why I should not have suspend2 in my kernel?)
On more than one occasion, the suspend2 patches have broken both
in-kernel swsusp and uswsusp on my laptop.
Come to think of it, I wonder h
[EMAIL PROTECTED] said:
> Would that kill keyboard leds?
the opposite, actually. After about 30 seconds or so hung, my capslock
LED would start blinking on and off
Jason
-
Take Surveys. Earn Cash. Influence the Future of IT
Pavel Machek wrote:
> Probably kernel hardlocks during resume. Go to *vanilla* 2.6.18-rc3
> (no suspend2 patch, please), and try suspending it by echo 3 >
(aside from your fierce opposition to the competition, is there any rational
reason why I should not have suspend2 in my kernel?)
Sorry, I for
Hi!
> Sorry to bug you both individually, but Mr. Joseph Fannin suggested I send
> this to both of you -- it may not fall under your "jurisdiction," so to
> speak, as this concerns ACPI suspend-to-ram, not swsusp. Anyway, thanks
> for taking a look!
This would be very much on-topic on suspend.sf
Hi!
> > Probably kernel hardlocks during resume. Go to *vanilla* 2.6.18-rc3
> > (no suspend2 patch, please), and try suspending it by echo 3 >
> > /proc/acpi/sleep (from init=/bin/bash boot, minimum config, no fb).
>
> I guess it's an IDE-related problem similar to the one which Jason Lunz's
> pa
[EMAIL PROTECTED] said:
> I guess it's an IDE-related problem similar to the one which Jason Lunz's
> patch fixed, or a (P)SATA-related one.
If it's like what I saw, most of the time the hang will keep the hard
drive LED on solid. But not always.
Jason
--
On Friday 04 August 2006 22:49, Pavel Machek wrote:
> On Thu 2006-08-03 17:09:37, Matej Cepl wrote:
> > Pavel Machek wrote:
> > > Yes. Try again on minimal system, see if it is just video that is
> > > broken or if machine is hung up, and report.
> >
> > Apparently everything is broken. I tried "b
On Thu 2006-08-03 17:09:37, Matej Cepl wrote:
> Pavel Machek wrote:
> > Yes. Try again on minimal system, see if it is just video that is
> > broken or if machine is hung up, and report.
>
> Apparently everything is broken. I tried "brutal mode" (see
> attached /boot/grub/menu.lst a /boot/config-`
On Fri 2006-08-04 07:49:04, Dmitri Hrapof wrote:
> Hello!
>
> I just installed Debian on my iMac. My question is: what is current
> state of sleep/suspend support for PowerPC Macs in general and iMacs
> specifically? My kernel is 2.6.15-1-powerpc. Do I need to upgrade? Any
> special patches? What
Hello!
I just installed Debian on my iMac. My question is: what is current
state of sleep/suspend support for PowerPC Macs in general and iMacs
specifically? My kernel is 2.6.15-1-powerpc. Do I need to upgrade? Any
special patches? What programs/daemons do I need?
Thanks in advance,
Dmitri
14 matches
Mail list logo
