More ACPI woes? - Mandriva

This is a discussion on More ACPI woes? - Mandriva ; I had problems recently with screensavers 'freezing' after a few seconds with error messages from ACPI in /var/log/syslog, and sommeone here gave me a workaround for that, for which I'm grateful. But I'm beginning to think that there's a more ...

+ Reply to Thread
Results 1 to 13 of 13

Thread: More ACPI woes?

  1. More ACPI woes?


    I had problems recently with screensavers 'freezing' after a few seconds
    with error messages from ACPI in /var/log/syslog, and sommeone here gave
    me a workaround for that, for which I'm grateful. But I'm beginning to
    think that there's a more fundamental problem somewhere.

    I have discovered now that if I right-click the Kpowersave applet in the
    bottom right taskbar, and then select 'Suspend to Disk', I get the
    following two messages in a console:

    swsusp: Marking nosave pages: 000000000009f000 - 0000000000100000
    swsusp: Basic memory bitmaps created

    and the machine then freezes, requiring a power-off.

    If I select 'Suspend to RAM', it seems to suspend correctly, but on
    resume the display is corrupted, and requires a restart.

    Anything I can do to diagnose this further? If it helps I'm running the
    2.6.24.5-laptop-2mnb kernel...

  2. Re: More ACPI woes?

    On Sun, 03 Aug 2008 13:48:04 -0400, Keith wrote:

    > I have discovered now that if I right-click the Kpowersave applet in the
    > bottom right taskbar, and then select 'Suspend to Disk', I get the
    > following two messages in a console:
    > swsusp: Marking nosave pages: 000000000009f000 - 0000000000100000
    > swsusp: Basic memory bitmaps created
    > and the machine then freezes, requiring a power-off.


    If you take a look at https://qa.mandriva.com/show_bug.cgi?id=38300
    the standard questions will be what make/model, and what version of
    the bios are you using.

    Also, how much ram do you have, and what is the size of the swap?

    Be very careful, if you decide to update the bois. A failure during the
    bios burn can make the computer unbootable, until the bios chip is replaced.

    > If I select 'Suspend to RAM', it seems to suspend correctly, but on
    > resume the display is corrupted, and requires a restart.


    As per https://qa.mandriva.com/show_bug.cgi?id=39616 try pressing alt+ctrl+f1,
    then alt+ctrl+f7, to see if that will work around the display problem.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  3. Re: More ACPI woes?

    David W. Hodgins wrote:
    > On Sun, 03 Aug 2008 13:48:04 -0400, Keith wrote:
    >
    >> I have discovered now that if I right-click the Kpowersave applet in the
    >> bottom right taskbar, and then select 'Suspend to Disk', I get the
    >> following two messages in a console:
    >> swsusp: Marking nosave pages: 000000000009f000 - 0000000000100000
    >> swsusp: Basic memory bitmaps created
    >> and the machine then freezes, requiring a power-off.

    >
    > If you take a look at https://qa.mandriva.com/show_bug.cgi?id=38300
    > the standard questions will be what make/model, and what version of
    > the bios are you using.
    >
    > Also, how much ram do you have, and what is the size of the swap?


    The machine is an Advent 9617 (a re-badged Uniwill L75II8, apparently).
    The BIOS version is 1.00DIX, and there appears to be no later version.

    RAM is 2Gb, and swap partition is 4088511 blocks according to
    fdisk -l

    That size is the default as selected on install.

    >> If I select 'Suspend to RAM', it seems to suspend correctly, but on
    >> resume the display is corrupted, and requires a restart.

    >
    > As per https://qa.mandriva.com/show_bug.cgi?id=39616 try pressing alt+ctrl+f1,
    > then alt+ctrl+f7, to see if that will work around the display problem.


    Yay! That does in fact do the trick there. I'd really like to get the
    Suspend to Disk working as well though...

  4. Re: More ACPI woes?

    Keith wrote:
    > David W. Hodgins wrote:
    >> On Sun, 03 Aug 2008 13:48:04 -0400, Keith wrote:
    >>
    >>> I have discovered now that if I right-click the Kpowersave applet in the
    >>> bottom right taskbar, and then select 'Suspend to Disk', I get the
    >>> following two messages in a console:
    >>> swsusp: Marking nosave pages: 000000000009f000 - 0000000000100000
    >>> swsusp: Basic memory bitmaps created
    >>> and the machine then freezes, requiring a power-off.

    >>
    >> If you take a look at https://qa.mandriva.com/show_bug.cgi?id=38300
    >> the standard questions will be what make/model, and what version of
    >> the bios are you using.
    >>
    >> Also, how much ram do you have, and what is the size of the swap?

    >
    > The machine is an Advent 9617 (a re-badged Uniwill L75II8, apparently).
    > The BIOS version is 1.00DIX, and there appears to be no later version.
    >
    > RAM is 2Gb, and swap partition is 4088511 blocks according to
    > fdisk -l
    >
    > That size is the default as selected on install.
    >
    >>> If I select 'Suspend to RAM', it seems to suspend correctly, but on
    >>> resume the display is corrupted, and requires a restart.

    >>
    >> As per https://qa.mandriva.com/show_bug.cgi?id=39616 try pressing
    >> alt+ctrl+f1,
    >> then alt+ctrl+f7, to see if that will work around the display problem.

    >
    > Yay! That does in fact do the trick there. I'd really like to get the
    > Suspend to Disk working as well though...


    Oh, and looking at the Suspend to RAM bug report you mentioned more
    closely, I'm using KDE, whereas the bug-poster was complaining about
    GNOME. Don't know if this is relevant.

  5. Re: More ACPI woes?

    On Mon, 04 Aug 2008 07:59:56 -0400, Keith wrote:

    > Oh, and looking at the Suspend to RAM bug report you mentioned more
    > closely, I'm using KDE, whereas the bug-poster was complaining about
    > GNOME. Don't know if this is relevant.


    Shouldn't matter. I think you should file a bug report, include an
    attachment with the output from dmidecode.

    I would try installing apmd, and booting with the kernel paramater
    noacpi, to see if the laptop suspend/resume will work with apm.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  6. Re: More ACPI woes?

    David W. Hodgins wrote:
    > On Mon, 04 Aug 2008 07:59:56 -0400, Keith wrote:
    >
    >> Oh, and looking at the Suspend to RAM bug report you mentioned more
    >> closely, I'm using KDE, whereas the bug-poster was complaining about
    >> GNOME. Don't know if this is relevant.

    >
    > Shouldn't matter. I think you should file a bug report, include an
    > attachment with the output from dmidecode.


    OK, I've done that.

    > I would try installing apmd, and booting with the kernel paramater
    > noacpi, to see if the laptop suspend/resume will work with apm.


    Now this is interesting. apmd is already installed, but not running.
    It won't allow me to start it through MCC, although there are no error
    messages in the logs. So I tried starting it manually using

    apmd -v7 (which switches on DEBUG-level output)

    and I get:
    No APM support in kernel

    WTF is going on here?! As I think I said before I'm running the
    2.6.24.5-laptop-2mnb kernel.

  7. Re: More ACPI woes?

    On Thu, 07 Aug 2008 11:19:56 -0400, Keith wrote:

    > Now this is interesting. apmd is already installed, but not running.
    > apmd -v7 (which switches on DEBUG-level output)
    > and I get:
    > No APM support in kernel
    > WTF is going on here?! As I think I said before I'm running the
    > 2.6.24.5-laptop-2mnb kernel.


    The following command shows whether or not apm is compiled into the kernel.
    The output below is for 2.6.24.5-desktop-2mnb ...
    $ grep -i apm /boot/config
    CONFIG_APM=y
    # CONFIG_APM_IGNORE_USER_SUSPEND is not set
    # CONFIG_APM_DO_ENABLE is not set
    CONFIG_APM_CPU_IDLE=y
    # CONFIG_APM_DISPLAY_BLANK is not set
    # CONFIG_APM_ALLOW_INTS is not set
    # CONFIG_APM_REAL_MODE_POWER_OFF is not set

    It's might be that, having acpi enabled, is blocking the apmd. Try booting
    with the noacpi option, and then starting apmd.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  8. Re: More ACPI woes?

    David W. Hodgins wrote:
    >
    > The following command shows whether or not apm is compiled into the kernel.
    > The output below is for 2.6.24.5-desktop-2mnb ...
    > $ grep -i apm /boot/config
    > CONFIG_APM=y
    > # CONFIG_APM_IGNORE_USER_SUSPEND is not set
    > # CONFIG_APM_DO_ENABLE is not set
    > CONFIG_APM_CPU_IDLE=y
    > # CONFIG_APM_DISPLAY_BLANK is not set
    > # CONFIG_APM_ALLOW_INTS is not set
    > # CONFIG_APM_REAL_MODE_POWER_OFF is not set


    I get the same results from this kernel.

    > It's might be that, having acpi enabled, is blocking the apmd. Try booting
    > with the noacpi option, and then starting apmd.


    I tried appending 'noacpi', which hung on boot, then I tried 'acpi=off',
    which booted, but gives identical results on the 'Suspend to Disk' as
    before, apmd still won't start from MCC, and 'apmd -v7' still says "No
    APM support in kernel".

    Puzzled, I am.

  9. Re: More ACPI woes?

    On Friday 08 August 2008 11:36, someone identifying as *Keith* wrote
    in /alt.os.linux.mandriva:/

    > David W. Hodgins wrote:
    >>
    >> The following command shows whether or not apm is compiled into the
    >> kernel. The output below is for 2.6.24.5-desktop-2mnb ...
    >> $ grep -i apm /boot/config
    >> CONFIG_APM=y
    >> # CONFIG_APM_IGNORE_USER_SUSPEND is not set
    >> # CONFIG_APM_DO_ENABLE is not set
    >> CONFIG_APM_CPU_IDLE=y
    >> # CONFIG_APM_DISPLAY_BLANK is not set
    >> # CONFIG_APM_ALLOW_INTS is not set
    >> # CONFIG_APM_REAL_MODE_POWER_OFF is not set

    >
    > I get the same results from this kernel.
    >
    >> It's might be that, having acpi enabled, is blocking the apmd. Try
    >> booting with the noacpi option, and then starting apmd.

    >
    > I tried appending 'noacpi', [...


    As far as I know, that's not a valid kernel parameter.

    > ...] which hung on boot, [...


    That is odd, because the kernel is supposed to discard invalid parameters.

    > ...] then I tried 'acpi=off', which booted, but gives identical results on
    > the 'Suspend to Disk' as before, apmd still won't start from MCC, and
    > 'apmd -v7' still says "No APM support in kernel".


    Looking back at your original post, I suspect that it's simply a bug in the
    suspend to swap functionality of that particular kernel. It could have
    been a bug in that particular kernel version, or it could have been
    introduced by Mandriva's patches.

    As for APM, I'm not so sure modern systems still support it, even if it is
    built into the kernel. Error messages may sometimes be unclear as to the
    exact nature of the failure, which in this case might turn out that /apmd/
    says that there is no APM support in the kernel even if there is, but that
    the real cause is that the hardware doesn't support it, and that therefore
    the kernel can't implement it even if it has the support built-in.

    Another possibility - looking at what Dave pasted from his kernel config -
    is that you need to enable more of the APM kernel options, although that
    would surprise me, unless of course it's a bug in the kernel configurator.

    > Puzzled, I am.


    Help, I hope it does.

    --
    *Aragorn*
    (registered GNU/Linux user #223157)

  10. Re: More ACPI woes?

    On Fri, 08 Aug 2008 05:36:11 -0400, Keith wrote:

    > I tried appending 'noacpi', which hung on boot, then I tried 'acpi=off',
    > which booted, but gives identical results on the 'Suspend to Disk' as
    > before, apmd still won't start from MCC, and 'apmd -v7' still says "No
    > APM support in kernel".


    Looks like "CONFIG_APM_DO_ENABLE is not set" stops apm. Try booting
    with "acpi=off apm=on". After it's booted, check to see if /proc/apm
    exists. If it doesn't another kernel, or possibly a custom kernel
    will have to be tried. If it does, try starting apmd, and the suspend
    to disk.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  11. Re: More ACPI woes?

    David W. Hodgins wrote:
    > On Fri, 08 Aug 2008 05:36:11 -0400, Keith wrote:
    >
    >> I tried appending 'noacpi', which hung on boot, then I tried 'acpi=off',
    >> which booted, but gives identical results on the 'Suspend to Disk' as
    >> before, apmd still won't start from MCC, and 'apmd -v7' still says "No
    >> APM support in kernel".

    >
    > Looks like "CONFIG_APM_DO_ENABLE is not set" stops apm. Try booting
    > with "acpi=off apm=on". After it's booted, check to see if /proc/apm
    > exists. If it doesn't another kernel, or possibly a custom kernel
    > will have to be tried. If it does, try starting apmd, and the suspend
    > to disk.


    OK, tried that. The apmd daemon still won't start, and the message is
    still "No APM support in kernel". I'll have a hunt around for a
    different kernel - if anyone has any suggestions about which to try I'd
    be grateful.

  12. Re: More ACPI woes?

    Keith wrote:
    > OK, tried that. The apmd daemon still won't start, and the message is
    > still "No APM support in kernel". I'll have a hunt around for a
    > different kernel - if anyone has any suggestions about which to try I'd
    > be grateful.


    Just for grins, I took a look at the config files for the current
    stock and tmb 64-bit Mandriva kernels, vmlinuz-2.6.24.5-desktop-2mnb
    and vmlinuz-2.6.25.11-tmb-desktop-2mdv. Neither had any setting
    for APM, whatsoever.

    The header files for each (in the *devel* package) contain settings
    for APM devices, so my guess is that the full source code likewise
    would have the APM code but that it simply is not being enabled for
    the kernels provided in compiled form.

    It looks like it is time to download full source and roll your own,
    or change to a non-Mandriva kernel. Recommendations of some to the
    contrary, I find the Mandriva patches do good things for my Mandriva
    system and the Linux plain vanilla kernels do not play nicely. I
    would recommend getting full source from Manddriva, editing the
    config file (essential -- as the README will tell you) and compiling.

    Each of the methods for editing the config file has a different set
    of help files. I have found it useful to use all three methods and
    look at the help files for each choice each time. This is time-
    consuming, but the compiled kernels were more likely to boot and
    work.

    Cheers!

    jim b.

    --
    UNIX is not user unfriendly; it merely
    expects users to be computer-friendly.

  13. Re: More ACPI woes?

    On Sat, 09 Aug 2008 08:15:23 -0400, Keith wrote:

    > OK, tried that. The apmd daemon still won't start, and the message is
    > still "No APM support in kernel". I'll have a hunt around for a
    > different kernel - if anyone has any suggestions about which to try I'd
    > be grateful.


    Because I'm using dialup, I don't want to download the various kernel options
    available, to see if any of them support apm. I normally use a custom compiled
    kernel, and will experiment with what changes are needed to get apm working, and
    (If I get it working), will then post detailed instructions on how to try this yourself. As I don't have a laptop, I won't be able to test past the checking to
    see if /proc/apm exists.

    I expect you'll be stuck with suspend to disk not working, until the kernel
    developers fix acpi, for your type of laptop.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

+ Reply to Thread