I have updated the machine to bios version 5.90 but it is still not working. 
The laptop is updated to todays factory as well.

I tried Kubuntu 7.04 and that is working without a problem from the default installation.

What is Kubuntu doing differently? Any ideas what I could do to get this working?

This must be an userspace issue. I replaced the Kubuntu 7.05 kernel (2.6.20-16-generic) with openSUSEs 2.6.22-5-default and Kubuntu still does suspend!

I installed s2ram on ubuntu and it seems to work without a problem with that too.

s2ram from Kubuntu says the machine is unknown but using s2ram -f it suspends.

The openSUSE version says the following:
# s2ram -n
Machine matched entry 197:
    sys_vendor   = 'TOSHIBA'
    sys_product  = 'Satellite A100'
    sys_version  = ''
    bios_version = ''
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "TOSHIBA"
    sys_product  = "Satellite A100"
    sys_version  = "PSAA9E-099039GR"
    bios_version = "5.90   "

How can I edit the entry 197?

I have investigated somemore.

Under Kubuntu-userland with kernel and initrd from current openSUSE factory. I can suspend with their /etc/acpi/sleep.sh. s2ram does not work with openSUSE kernel and initrd under Kubuntu either. (But it does work with the Ubuntu kernel. the openSUSE s2ram with the entry and the Kubuntu version without the entry work in fact booth)

So there must be a problem with the openSUSE kernel and s2ram ...

After converting the ubuntu acpi-support package from http://archive.ubuntu.com/ubuntu/pool/main/a/acpi-support/ alien and editing a few lines and and arround 50 reboots I have written the following script, which works reliable on my machine:

#!/bin/bash
CONSOLE=`fgconsole`
chvt 12

for x in /sys/class/graphics/*; do
    if [ -f $x/state ]; then
        echo -n 1 >$x/state;
    fi
done

echo -n mem >/sys/power/state

vbetool post

for x in /sys/class/graphics/*; do
    if [ -f $x/state ]; then
        echo -n 0 >$x/state;
    fi
done

chvt $CONSOLE

After working through the openSUSE pm-utils scripts I came up with the following, which works for me.

# cat /etc/pm/sleep.d/99video
#!/bin/bash
# This makes my Toshiba A100 resume. The code comes from the Ubuntu
# acpi-support package.
# Felix Möller <felix@derklecks.de>
case $1 in
    suspend)
        for x in /sys/class/graphics/*; do
          if [ -f $x/state ]; then
            echo -n 1 >$x/state;
          fi
        done
        ;;
    resume)
        vbetool post
        for x in /sys/class/graphics/*; do
          if [ -f $x/state ]; then
            echo -n 0 >$x/state;
          fi
        done
        ;;
esac

Stefan: I think help_options() in /usr/lib/pm-utils/bin/pm-action should be adapted to the suse version, which does not support quiet a few of the mentioned options. (See /usr/share/doc/packages/pm-utils/hooks)

Yes, i'll look into that. We might support more of those options soon, though.

The A100 suspends now without any selfwritten hook with "s2ram --force --vbe_post" just "s2ram" does not work.

# s2ram -n
Machine matched entry 237:
    sys_vendor   = 'TOSHIBA'
    sys_product  = 'Satellite A100'
    sys_version  = ''
    bios_version = ''
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "TOSHIBA"
    sys_product  = "Satellite A100"
    sys_version  = "PSAA9E-099039GR"
    bios_version = "5.90   "
See http://en.opensuse.org/S2ram for details.

Why is this still not fixed with current factory? Do you need anything else?

You have added the script to s2ram with suspend-s2ram-suspend-fbcon.diff for bug #293662 .

I think just adding the machine to suspend-0.69.9/whitelist.c is enough.

Hi Felix, sorry for the delay.

This is still not totally clear. We have an A100 here that suspends fine with "S3_BIOS|S3_MODE".

Our s2ram binary now has the framebuffer suspend sysfs hack from comment #5 built in, so you don't need the script in pm-utils anymore.

I still need to find out what is different on your machine versus the one we have here. Until i can test this (and it will be next week earliest, since i will be traveling), please just use a config file in /etc/pm/config.d that
just contains "S2RAM_OPTIONS='-f -v'".

Sorry for the hassle.

I still cannot resume my A100-01L.

s2ram -n
Machine matched entry 263:
    sys_vendor   = 'TOSHIBA'
    sys_product  = 'Satellite A100'
    sys_version  = ''
    bios_version = ''
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "TOSHIBA"
    sys_product  = "Satellite A100"
    sys_version  = "PSAARE-05Q029GR"
    bios_version = "5.90   "

uname -r
2.6.22.5-31-default

I tested all of the options below, with and without the -v switch and the computer suspends in all cases (standby LED is active) but it fails to resume (the keyboard remains dead and there is no HD activity).

    * s2ram -f -a 1
    * s2ram -f -a 2
    * s2ram -f -a 3
    * s2ram -f -p -m
    * s2ram -f -p -s
    * s2ram -f -m
    * s2ram -f -s
    * s2ram -f -p
    * s2ram -f -a 1 -m
    * s2ram -f -a 1 -s 

(In reply to comment #10 from Stefan Seyfried)
> This is still not totally clear. We have an A100 here that suspends fine with
> "S3_BIOS|S3_MODE".

There are alot of differnt A100s. The number after the 100 is important too in my case 773.

Mine is:
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "TOSHIBA"
    sys_product  = "Satellite A100"
    sys_version  = "PSAA9E-099039GR"
    bios_version = "5.90   "

> Our s2ram binary now has the framebuffer suspend sysfs hack from comment #5
> built in, so you don't need the script in pm-utils anymore.
> 
> I still need to find out what is different on your machine versus the one we
> have here. Until i can test this (and it will be next week earliest, since i
> will be traveling), please just use a config file in /etc/pm/config.d that
> just contains "S2RAM_OPTIONS='-f -v'".
I am using the radeonhd driver by now and to suspend the machine I have to use:
# cat /etc/pm/config.d/config
S2RAM_OPTS="--force --vbe_post --vbe_mode --vbe_save"

Without the --vbe_post the machine dies hard on resume so that nothing is written in the logs. When just using one of [--vbe_mode, --vbe_save] the consoles do not work after suspend.

Frank has an A100, he will take care.

Birte: Could you try if it works with just s2ram -f ? As you seem to have a nvidia gfxcard it could also be possible you need bootparameter agp=off (on x86_64 systems) or Option "NvAGP" "1" in your /etc/X11/xorg.conf Device-Section.

Felix, thanks for your feedback. I sent a patch with your s2ram options for the whitelist to our upstream maintainer.

Birte: as you seem to have another satellite a100 incarnation, i'd like to ask you to open a new bug for your hardware. You may of course add me as Assignee.