[Mdlug] IBM T30/SUSE 10.0 Suspend to RAM Problems (repost word wrapped, sorry)

Jeff Hanson jhansonxi at gmail.com
Mon Nov 20 13:30:11 EST 2006


On 11/20/06, Peter Bart <peter at petertheplumber.net> wrote:
> I did have the program 'configure thinkpad' installed at
> one time. It came with SUSE but I uninstalled it because it used APM and
> I was told it would conflict with the ACPI setings in Yast. Is it
> possible that some mention of APM is still conflicting with ACPI? Should
> I comb through the /etc files for mention of APM? Or should I bag ACPI
> for APM? I don't really want to bag ACPI because I have the latest
> kernel that is supposed to work well with ACPI, it's worked before using
> Gnome, and I perceive it as a step back. However if APM works
> and ........................................
I think in most cases ACPI disables APM.  At least that's what I've
seen in the logs on my systems.  The only time it doesn't happen is if
ACPI is disabled by the kernel because the BIOS is too old.  I'm not
sure about the cutoff date.  On my older systems I have to pass a
"acpi=force" option at boot to enable it.  If your laptop is
partitioned like most installations then it should be relatively safe
to switch distros assuming your home folder is on a separate
partition.  If you have the time, try Ubuntu, Mandriva, or Red Hat and
see if they work better.  The only problem you will encounter is that
the user ID that owns the home files may change and you will have to
chown them to match a new account ID.  This is because different
distros may use different number ranges for user accounts.  Another
option is to compile a new kernel.  The kernel update policies of
distros varies a lot but many stick to one major version and backport
security updates only or significant fixes, not new enhancements.  If
there are fixes in the ACPI modules you may not get them through Suse
updates until the next major release.  You could also try their alpha
or beta versions.



More information about the mdlug mailing list