lkml.org 
[lkml]   [1998]   [Feb]   [2]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
SubjectHibernate != Standby
FromJohn Goerzen <>
Date02 Feb 1998 14:56:14 -0600
Stephen.Rothwell@canb.auug.org.au writes:

> but Linux is running in protected mode where access to this value
> as a segment descriptor is illegal.  The BIOS is buggy!

I flashed the BIOS with IBM's latest image and the oops went away.
However, suspend (hibernate) still doesn't work!

Now, both suspend and standby give a standby.  I cannot get a suspend, 
either by pressing the suspend key combination or using the apm -s
command.  Neither one will do a hibernate, only a standby.

Any ideas on this one now?

Thanks,
John

> 
> > My laptop is an IBM Thinkpad 310ED (I believe this model was
> > introduced last fall. It is a P133 MMX).  I am getting protection
> > faults at 0040.  Is it possible to make the Linux kernel use a
> > different location for whatever it is trying to store at 0040?  Would
> > one of the exclude kernel parameters that I seem to recall hearing
> > about at one time fix this, and if so, what exactly should I exclude?
> > (How much RAM, etc.)
> 
> See above - it is not that simple.
> 
> > I am suspecting that this problem is why I cannot suspend or hibernate 
> > my laptop under Linux.  It will do either of those fine under bare DOS 
> > (no config.sys, autoexec.bat, etc) or Windows.
> 
> DOS runs in real mode.
> 
> > Further, it seems that apm_bios.c in even 2.1.82 was last updated in
> > 1996 -- and there may well be more laptops appearing since then that
> > may need special support.  Is anybody still working on the APM driver?
> > It seems somewhat out of date.
> 
> OK, there is not much work going on with the APM driver for various
> reasons - the biggy being that APM is now defunct :-(  There is a new
> API for doing power management that I know nothing about (yet).  Also
> there have not been any major revisions of teh APM BIOS specifiation anyway.
> 
> I think the only solution is to complain to IBM and get it fixed.
> There may already be an updated BIOS available (I don't know).
> 
> Cheers,
> Stephen
> --
> Stephen Rothwell                    Stephen.Rothwell@canb.auug.org.au
> 

-- 
John Goerzen
Southwind Internet Access, Inc,
Business e-mail: jgoerzen@southwind.net

Personal e-mail: jgoerzen@complete.org
Wichita State University e-mail: jgoerzen@cs.twsu.edu
Developer, Debian GNU/Linux    <http://www.debian.org>

\
 
 \ /
  Last update: 2005-03-22 12:41    [from the cache]
©2003-2008