[ltp] Redhat 9.0 on A22p

[Richard Neill]

Tim,

Thanks for that. Your apmd file is identical to mine (although I did try 
uncommenting the #HDPARM_AT_* bits.)
Given that I've had problems with resume, I'd advise you to make sure 
you at least always save your work before doing apm -s !
As far as I can tell, Fn-F4 and apm -s are equivalent. So, I'd love to 
know what the secret is! One other thing - can you do a hdparm -v 
/dev/hda to let me know what your hdd is set to?

I have:

# hdparm -v /dev/hda

/dev/hda:
  multcount    = 16 (on)
  IO_support   =  0 (default 16-bit)
  unmaskirq    =  0 (off)
  using_dma    =  1 (on)
  keepsettings =  0 (off)
  readonly     =  0 (off)
  readahead    =  8 (on)
  geometry     = 4134/240/63, sectors = 62506080, start = 0

(I didn't do anything to the defaults).

Best wishes

Richard



Tim Turkington wrote:
>>Dear Tim,
>>
>>You say you have suspend working. I'd be curious to know what you did. I 
>>also have an A22p, and in various Mandrakes (8.0 -> 9.0), I've never had 
>>it work reliably. I find that apm -s or Fn-F4 works most of the time, 
>>but about 1 time in 10, it fails to resume - it seems as though the hard 
>>disc doesn't spin back up - and I have to reset the machine.
>>
>>Do you have this problem? If not, can you send me a  copy of your 
>>/etc/sysconfig/apmd
>>or are you somehow using ACPI ?
>>
>>Thanks a lot
>>
>>Best wishes
>>
>>Richard
> 
> 
> Dear Richard,
> 
> "I" didn't do anything.  It just worked after the installation. So all those
> people who developed the relevant software and got it working did all the
> important work!  Below are the contents of /etc/sysconfig/apmd.
> 
> It won't suspend with the wireless PC card inserted, but there may be some
> good reason for it to be that way.
> 
> It also worked after installing RH7.2.  I almost exclusively use
> <fn>-<f4> and <fn>-<f12> to trigger the suspend and hibernate.
> 
> Note:  I have not yet even done this 10 times with RH9.0, so I don't
> have the statistical sample to know exactly how reliable it is.
> There were a couple of times when I couldn't get the system
> to wake up when I was running RH7.2, but I think both times
> could be attributed to closing the top (which triggers the
> suspend) too soon after starting suspend or hibernate manually.
> 
> Tim
> 
> contents of /etc/sysconfig/apmd:
> (warning: some lines wrapped when I pasted.)
> --------------------------------------------
> 
> APMSCRIPTS=/etc/sysconfig/apm-scripts
> 
> # make an entry in the logfiles whenever the percentage of
> # battery power changes below the value specified here
> LOGPERCENTCHANGE=10
> 
> # warn on specified remainig battery percentage, use negative values
> # to disable this feature
> WARNPERCENT=5
> 
> # use -W to warn all users in a critical power state
> ADDPARAMS="-W"
> 
> # if you have problems with your X display after returning from suspend mode
> # give CHANGEVT the number of the virtual terminal your X-Server runs on
> #CHANGEVT="7"
> 
> # If you set this to yes, the clock will be synced with the hardware clock
> # when the computer returns from suspend mode.
> CLOCK_SYNC="yes"
> 
> # Some broken BIOSes, like those found in early Gericom 3xC notebooks,
> # won't wake up harddisks from suspend to disk unless they're set to PIO mode
> # and 16-bit.
> # Don't activate the following two lines unless you're getting
> # "hda: lost interrupt" after returning from a suspend to disk.
> #HDPARM_AT_SUSPEND="-q -X0 -q -c0 -q -d0 -q -u0 -q -S0"
> #HDPARM_AT_RESUME="-q -X66 -q -c1 -q -d1 -q -u1 -q -S30"
> 
> # the error-beep of your terminal might be set to the default values after a
> # resume so set TERMINALBEEP to "yes" to restore the values in
> # /etc/sysconfig/keyboard
> TERMINALBEEP="no"
> 
> # if your sound sometimes doesn't work after a resume set RESTORESOUND to
> "yes";
> # this will kill all sound applications, remove and start the $SOUNDMODULES
> # again, and, if you also set $RESTORESOUNDPROGS to "yes", restart the
> # sound applications as the correct user and on the correct display
> RESTORESOUND="no"
> RESTORESOUNDPROGS="no"
> SOUNDMODULES="sb uart401 sound soundcore maestro cs4281"
> 
> # some services might need restarting after a suspend/resume cycle - for
> # example, named will shut down if all network interfaces go down.
> # Any valid service (as in "ls /etc/init.d/") can be listed, and will be
> # restarted if it was running at suspend time.
> RESTORESERVICES="named"
> 
> # I got frequent problems mainly with scsi-pcmcia-cards on the cardbus. Use
> # PCMCIARESTART="yes" to stop the whole pcmcia-subsystem on a suspend and
> # to start it again after a resume. This can slow down your suspend and resume
> # process. Use PCMCIAWAIT to wait with the suspend until the pccard is removed
> # from the system.
> # Some BIOSes are too buggy to handle cardctl suspend and cardctl resume
> # properly, in these cases cardctl eject and cardctl insert can be used instead.
> # However, this actually ejects the card on hardware supporting it, so if
> # the BIOS isn't buggy, it shouldn't be used. Set PCMCIABIOSBUG to yes if
> # you are experiencing problems with PCMCIA cards after a resume.
> # Since buggy BIOSes seem to be far more common than hardware that can eject
> # PCMCIA cards (and it doesn't make a difference on systems that don't have
> # either), it is enabled by default.
> PCMCIARESTART="no"
> PCMCIABIOSBUG="yes"
> PCMCIAWAIT="no"
> 
> # Set ANACRON_ON_BATTERY to yes if you want to run anacron after a resume even
> # if you're on battery power.
> ANACRON_ON_BATTERY="no"
> 
> # Set LOCK_X to yes if you want to lock all your X displays at suspend
> LOCK_X="no"
> 
> # If NET_RESTART is set to yes, the network will be shut down at suspend and
> # restarted at resume.
> # This is especially useful if you're using DHCP, but usually won't hurt.
> NET_RESTART="yes"
> 
> # If NETFS_RESTART is set to yes, NFS filesystems will be unmounted at
> # suspend, and remounted at resume (if possible).
> NETFS_RESTART="yes"
> 
> # If you wish to stop any services when going to battery power (and restart
> them
>  when
> # going to line power), list them in POWER_SERVICES.
> # Any service started using the init scripts can be listed (the APM script
> runs
> # "/sbin/service ... stop" for each of the services).
> # If you want to stop/restart any services that are not started by the init
> syst
> em,
> # use an apmcontinue script.
> #POWER_SERVICES="atd crond"
> 
> # If you wish to stop any services when running short of battery power (and
> rest
> art them when
> # going to line power), list them in LOWPOWER_SERVICES.
> # Any service started using the init scripts can be listed (the APM script
> runs
> # "/sbin/service ... stop" for each of the services).
> # If you want to stop/restart any services that are not started by the init
> syst
> em,
> # use an apmcontinue script.
> LOWPOWER_SERVICES="atd crond"
> 
> # Some broken BIOSes (e.g. the ones found in Toshiba Satellite Pro 4600
> # Notebooks) need some time to settle down before really entering suspend
> # mode.
> #
> # If your BIOS is broken, uncomment the line below, and possibly change the
> # value (e.g. "5s = Wait 5 seconds before allowing to suspend").
> #DELAYSUSPEND="3s"
> 
> # If your machine supports using cpufreq to change its speed, you can enable
> # this to support changing the cpu frequence to performance or powersave
> # based on whether or not you are currently on AC power or battery power
> #CPUFREQ="no"
> 
>