Toshiba A500 Power Management

OK - I got the wireless working, now I need to move on to the next problem: Power Management doesn’t work on my Toshiba A500.

When I pick “Suspend to RAM”, my Internet connection gets stopped (which probably should happen), but then only the screen gets locked, it does not actually go to Suspend.

Where do I start troubleshooting? I’m assuming that Power Management is handled through a kernel driver…? Are these drivers updateable and accessible as, for example, network drivers?

Proprietary (graphics and network) drivers are often the cause of this type of problem. I suggest you have a read of these to start with

Suspend to RAM - openSUSE

Pm-utils - openSUSE

This is worth a try as an initial step

s2ram -f

BTW, which desktop environment are you using?

Well, that was a lot of fun (not really) - I tried all suggested permutations of “s2ram” and the various switches and none of them bring the laptop back to life (the screen remains off).

Since this is a brand-new laptop, my guess is I need some kind of driver? What are my next steps?

BTW, which desktop environment are you using?

It was in my tagline: KDE 4.3.5

Well, that was a lot of fun (not really) - I tried all suggested permutations of “s2ram” and the various switches and none of them bring the laptop back to life (the screen remains off).

From this, I’m assuming your machine ‘suspended’ ok, but did not resume properly? In your original post, you mentioned

When I pick “Suspend to RAM”, my Internet connection gets stopped (which probably should happen), but then only the screen gets locked, it does not actually go to Suspend.

I would have a look at the suspend logs that get generated

/var/log/pm-suspend.log

It might also be worth checking your power management config via KDE’s system settings.

Yes, I should have been more clear - I followed the instructions on the Wiki page: I started with the init=/bin/bash command into a “bare-bones” startup and then issued the various permutations of “s2ram”.

Every time, the laptop went into suspend, but when I turned it back on, the screen did not resume.

Any thoughts? I logged a bug report on Bugzilla (“mobile” component) with my laptop info and results. Are there any drivers I can try?

Any thoughts? I logged a bug report on Bugzilla (“mobile” component) with my laptop info and results. Are there any drivers I can try?

No, its probably a driver causing this. Quite often, it is the network or proprietary graphics card driver that can cause problems like this. Posting your suspend log might yield clues…

Weird - /var/log/pm-suspend.log does not contain any information from all my attempts yesterday - only from the time I tried to suspend from KDE. Here is that log:


2010-05-02 23:52:42.105984955 -0600: running 'suspend'/'suspend'/'' hooks.
===== 2010-05-02 23:52:42.154660536 running hook: /usr/lib/pm-utils/sleep.d/00clear =====
===== 2010-05-02 23:52:42.237825784 running hook: /usr/lib/pm-utils/sleep.d/01logging =====
suspend initiated: Sun May  2 23:52:42 MDT 2010

Linux finrod 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux
kernel command line: 'root=/dev/disk/by-id/ata-ST9500420ASG_5VJ2XRWC-part1 resume=/dev/disk/by-id/ata-ST9500420ASG_5VJ2XRWC-part4 splash=silent quiet vga=0x314'
Module                  Size  Used by
nfs                   405152  0 
lockd                  95636  1 nfs
fscache                52048  1 nfs
nfs_acl                 4072  1 nfs
auth_rpcgss            56928  1 nfs
sunrpc                267144  5 nfs,lockd,nfs_acl,auth_rpcgss
cryptd                 10832  0 
crypto_wq               2064  1 cryptd
aes_x86_64              9576  3 
cryptomgr             109904  0 
aead                   10792  1 cryptomgr
pcompress               3560  1 cryptomgr
crypto_blkcipher       18028  2 cryptd,cryptomgr
crypto_hash            17416  2 cryptd,cryptomgr
aes_generic            29128  1 aes_x86_64
crypto_algapi          25904  8 cryptd,aes_x86_64,cryptomgr,aead,pcompress,crypto_blkcipher,crypto_hash,aes_generic
af_packet              28680  4 
ip6t_LOG                7980  6 
xt_tcpudp               4104  2 
xt_pkttype              2248  3 
ipt_LOG                 7660  6 
xt_limit                4076  12 
snd_pcm_oss            60032  0 
snd_mixer_oss          22728  1 snd_pcm_oss
snd_seq                78560  0 
snd_seq_device         10460  1 snd_seq
edd                    13232  0 
vboxnetadp              8448  0 
vboxnetflt             19184  0 
vboxdrv              1811500  2 vboxnetadp,vboxnetflt
cpufreq_conservative    10360  0 
cpufreq_userspace       4364  0 
cpufreq_powersave       2152  0 
acpi_cpufreq           11544  0 
ip6t_REJECT             6856  3 
nf_conntrack_ipv6      26632  4 
ip6table_raw            3720  1 
xt_NOTRACK              2248  4 
ipt_REJECT              4136  3 
xt_state                2920  8 
iptable_raw             3560  1 
iptable_filter          4520  1 
ip6table_mangle         5000  0 
nf_conntrack_netbios_ns     3400  0 
nf_conntrack_ipv4      14232  4 
nf_conntrack          101952  5 nf_conntrack_ipv6,xt_NOTRACK,xt_state,nf_conntrack_netbios_ns,nf_conntrack_ipv4
nf_defrag_ipv4          2856  1 nf_conntrack_ipv4
ip_tables              24536  2 iptable_raw,iptable_filter
ip6table_filter         4552  1 
ip6_tables             26072  4 ip6t_LOG,ip6table_raw,ip6table_mangle,ip6table_filter
x_tables               30768  11 ip6t_LOG,xt_tcpudp,xt_pkttype,ipt_LOG,xt_limit,ip6t_REJECT,xt_NOTRACK,ipt_REJECT,xt_state,ip_tables,ip6_tables
fuse                   87984  1 
loop                   22292  0 
dm_mod                101544  0 
snd_hda_codec_realtek   318124  1 
snd_hda_intel          37280  2 
snd_hda_codec         111112  2 snd_hda_codec_realtek,snd_hda_intel
uvcvideo               74484  0 
snd_hwdep              11216  1 snd_hda_codec
videodev               46848  1 uvcvideo
snd_pcm               117808  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
jmb38x_ms              17964  0 
snd_timer              32152  2 snd_seq,snd_pcm
v4l1_compat            19020  2 uvcvideo,videodev
sdhci_pci              11048  0 
sr_mod                 20964  0 
v4l2_compat_ioctl32    12776  1 videodev
snd                    97608  14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
sdhci                  27628  1 sdhci_pci
cdrom                  48232  1 sr_mod
memstick               16784  1 jmb38x_ms
mmc_core               83616  1 sdhci
pcspkr                  3720  0 
r8192se_pci           549320  0 
sg                     40128  0 
r8169                  46412  0 
ac                      6416  0 
i2c_i801               15624  0 
battery                15824  0 
joydev                 14400  0 
rfkill                 28176  0 
video                  29156  0 
button                  8360  0 
snd_page_alloc         12600  2 snd_hda_intel,snd_pcm
intel_agp              37584  0 
ext4                  426040  2 
jbd2                  115712  1 ext4
crc16                   2504  1 ext4
fan                     6352  0 
processor              56932  1 acpi_cpufreq
thermal                25160  0 
thermal_sys            21888  4 video,fan,processor,thermal

             total       used       free     shared    buffers     cached
Mem:       3916264     823604    3092660          0      34208     432760
-/+ buffers/cache:     356636    3559628
Swap:      8385920          0    8385920

===== 2010-05-02 23:52:42.263838640 running hook: /usr/lib/pm-utils/sleep.d/02rtcwake =====
rtcwake alarm not enabled in /etc/pm/config.d/rtcwake.config, doing nothing...
===== 2010-05-02 23:52:42.272676806 running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== 2010-05-02 23:52:42.279394036 running hook: /usr/lib/pm-utils/sleep.d/06autofs =====
===== 2010-05-02 23:52:42.362577367 running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
===== 2010-05-02 23:52:42.591475459 running hook: /usr/lib/pm-utils/sleep.d/30s2disk-check =====
===== 2010-05-02 23:52:42.613530483 running hook: /usr/lib/pm-utils/sleep.d/45pcmcia =====
ejecting PCMCIA cards...
===== 2010-05-02 23:52:42.650872971 running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== 2010-05-02 23:52:42.678915418 running hook: /usr/lib/pm-utils/sleep.d/80acpi-fan =====
===== 2010-05-02 23:52:42.683191925 running hook: /usr/lib/pm-utils/sleep.d/80videobios =====
===== 2010-05-02 23:52:42.716508655 running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== 2010-05-02 23:52:42.757306601 running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== 2010-05-02 23:52:42.773715933 running hook: /usr/lib/pm-utils/sleep.d/99Zgrub =====
===== 2010-05-02 23:52:42.778441958 running hook: /usr/lib/pm-utils/sleep.d/99info =====
2010-05-02 23:52:42.782360964: done running suspend/suspend hooks.
INFO: going to suspend. In case of problems with the selected suspend options,
INFO: please read /usr/share/doc/packages/pm-utils/README.smart-suspend-to-RAM
INFO: no quirks found, using info passed by HAL.
INFO: S2RAM_OPTS from HAL quirks: ''.
+ /usr/sbin/s2ram
Machine is unknown.
This machine can be identified by:
    sys_vendor   = "TOSHIBA"
    sys_product  = "Satellite A500"
    sys_version  = "PSAR9C-01V002"
    bios_version = "1.50"
See http://en.opensuse.org/S2ram for details.

If you report a problem, please include the complete output above.
If you report success, please make sure you tested it from both X and
the text console and preferably without proprietary drivers.
+ RET=127
+ set +x
2010-05-02 23:52:43.050429319 -0600: running 'suspend'/'resume'/'reverse' hooks.
===== 2010-05-02 23:52:43.071972136 running hook: /usr/lib/pm-utils/sleep.d/99info =====
===== 2010-05-02 23:52:43.075261408 running hook: /usr/lib/pm-utils/sleep.d/99Zgrub =====
===== 2010-05-02 23:52:43.079372189 running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== 2010-05-02 23:52:43.082405025 running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== 2010-05-02 23:52:43.106045387 running hook: /usr/lib/pm-utils/sleep.d/80videobios =====
===== 2010-05-02 23:52:43.112844700 running hook: /usr/lib/pm-utils/sleep.d/80acpi-fan =====
===== 2010-05-02 23:52:43.119825483 running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== 2010-05-02 23:52:43.133690949 running hook: /usr/lib/pm-utils/sleep.d/45pcmcia =====
inserting PCMCIA cards...
===== 2010-05-02 23:52:43.140353730 running hook: /usr/lib/pm-utils/sleep.d/30s2disk-check =====
===== 2010-05-02 23:52:43.144069074 running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
method return sender=:1.10 -> dest=:1.98 reply_serial=2
===== 2010-05-02 23:52:43.296860300 running hook: /usr/lib/pm-utils/sleep.d/06autofs =====
===== 2010-05-02 23:52:43.306994129 running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== 2010-05-02 23:52:43.312723905 running hook: /usr/lib/pm-utils/sleep.d/02rtcwake =====
===== 2010-05-02 23:52:43.320646908 running hook: /usr/lib/pm-utils/sleep.d/01logging =====
===== 2010-05-02 23:52:43.327465703 running hook: /usr/lib/pm-utils/sleep.d/00clear =====
2010-05-02 23:52:43.339207254: done running suspend/resume hooks.


Nothing obvious there. I think it maybe worth experimenting with some acpi kernel boot parameters listed here

SDB:Kernel Parameters for ACPI/APIC - openSUSE

A link to HCL database concerning Toshiba models

HCL/Laptops/Toshiba - openSUSE

but unfortunately yours is not listed. It may still have some useful info.

Folks,

I just realized that after installing the NVIDIA driver (closed source), my power management started to work as desired!

Thanks for the update. Graphics drivers are often the culprit as I mentioned a few posts ago, although its good to see that the proprietary nvidia driver works ok here :slight_smile:

I’ve added the A500 to the Laptop HCL wiki - it gave me an error initially when I tried to save, so hopefully it’s in there still.

I also was having problems with suspend and hibernate on my Toshiba laptop(different model though).

Anyway searching the Yast software manager found a program called fnfx that adds support for function key combinations on toshiba laptops.

On my laptop it totally fixed power management.
Might be worth trying if you haven’t done so already.

There is a new kernel available that supports the Toshiba laptops with buggy Bios problem.

To get opensuse installed you need to boot up the installation with acpi=off

I have been running a custom patched kernel, and it worked well.

I decided to try the kernel with the patch built in, and everything is working flawlessly.

Add the repository below (it is an rc release buyer beware)

Once the repository is added go into software management, in the drop down menu, repositories, select the new repository, and click the switch to repository option.

Install the kernel, and edit the /boot/grub/menu.lst file replace acpi=off with acpi=copy_dsdt

Reboot and enjoy your fully functional system

Index of /repositories/Kernel:/v2.6.35/openSUSE_Factory

If you want to avoid the possibility of the kernel being updated in the future and possibly breaking things, lock the installed kernel files in Yast so that it can’t be replaced.

If you want to run nvidia drivers you will need to blacklist the nouveau driver.

kdesu kwrite /etc/modprobe.d/50-blacklist.conf

At the bottom of the file add

blacklist nouveau

Download the nvidia driver from nvidias website and install as you normally would.

If you do not blacklist nouveau you will not be able to install the nvidia driver. ( the nvidia repo will not work)

The latest I found on the news site is that the upcoming release 11.3 sports the .34 kernel. Is this true? Or is .35 part of 11.3?

No 11.3 does not use the 2.6.35 kernel