Re: Bug#267600: Is CONFIG_SOFTWARE_SUSPEND enough?
Am Dienstag, den 22.11.2005, 11:58 +0100 schrieb Maximilian Attems:
> [ please open new bug reports for newer issues ]
> aboves bug report was about enabling swsusp.
Umm, actually it was 'Please consider including "suspend to disk"
option' and that could mean anything from please enable
CONFIG_SOFTWARE_SUSPEND to please make it work, but hey, sorry anyway.
> On Tue, Nov 22, 2005 at 11:39:13AM +0100, Thomas Maier wrote:
> >
> > I happily discovered that CONFIG_SOFTWARE_SUSPEND is enabled in my
> > 2.6.14-2-686 kernel (version 2.6.14-3) and tried to suspend to disk.
> > Unfortunately it refused to suspend and after googling for a while it
> > seems to me that the problem is that the IDE drivers are still compiled
> > as modules. See LKML, thread
> >
> > http://marc.theaimsgroup.com/?t=110789542400001&r=1&w=2
> >
> > However, it is quite old. So am I able to suspend to disk with the
> > Debian kernel image somehow or would I have to recompile with the IDE
> > stuff builtin?
>
> looks like.
> suse has a swsusp patch for modular ide, will try to dig it up.
Great. Thanks for the very quick reply. Would that patch be included
in the standard linux-image package so I would not need to recompile?
And would that need support from yaird to trigger a resume? Or at least
not mount the file system before a resume is triggered? I googled for a
while and found
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329319
and it seems to me this might be relevant, although it is about
suspend2.
Sorry for being so clueless, Thomas.
Reply to: