On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
> Hi,
>
> resume from suspend to ram doesn't work for my laptop and never
> has. So, this is not a regression.
>
> Hibernate (aka suspend to disk) works, however.
>
> When I resume, everything seems to come up (fan becomes busy, disk and
> dvd spin up for a short time),
Hmm, what about the screen?
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
"Rafael J. Wysocki" <[email protected]> writes:
> On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
>> When I resume, everything seems to come up (fan becomes busy, disk and
>> dvd spin up for a short time),
>
> Hmm, what about the screen?
When the laptop is dead, screen remains black.
When I skip acpi_enter_sleep_state(), the screen works like everything
else.
Regards, Olaf.
On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
> "Rafael J. Wysocki" <[email protected]> writes:
>
> > On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
> >> When I resume, everything seems to come up (fan becomes busy, disk and
> >> dvd spin up for a short time),
> >
> > Hmm, what about the screen?
>
> When the laptop is dead, screen remains black.
>
> When I skip acpi_enter_sleep_state(), the screen works like everything
> else.
I think you should try s2ram (http://en.opensuse.org/s2ram) as the first step.
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
"Rafael J. Wysocki" <[email protected]> writes:
> On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
>> "Rafael J. Wysocki" <[email protected]> writes:
>>
>> > On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
>> >> When I resume, everything seems to come up (fan becomes busy, disk and
>> >> dvd spin up for a short time),
>> >
>> > Hmm, what about the screen?
>>
>> When the laptop is dead, screen remains black.
>>
>> When I skip acpi_enter_sleep_state(), the screen works like everything
>> else.
>
> I think you should try s2ram (http://en.opensuse.org/s2ram) as the first step.
It doesn't work. I tried all options "s2ram -f (-s, -p, -m, -r, -a 1, -a 2,
-a 3)" one after the other.
Since the screen (or any other device) works without problems, when I
skip acpi_enter_sleep_state(), I don't think it's screen related.
Regards, Olaf.
On Saturday, 2 June 2007 00:17, Olaf Dietsche wrote:
> "Rafael J. Wysocki" <[email protected]> writes:
>
> > On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
> >> "Rafael J. Wysocki" <[email protected]> writes:
> >>
> >> > On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
> >> >> When I resume, everything seems to come up (fan becomes busy, disk and
> >> >> dvd spin up for a short time),
> >> >
> >> > Hmm, what about the screen?
> >>
> >> When the laptop is dead, screen remains black.
> >>
> >> When I skip acpi_enter_sleep_state(), the screen works like everything
> >> else.
> >
> > I think you should try s2ram (http://en.opensuse.org/s2ram) as the first step.
>
> It doesn't work. I tried all options "s2ram -f (-s, -p, -m, -r, -a 1, -a 2,
> -a 3)" one after the other.
>
> Since the screen (or any other device) works without problems, when I
> skip acpi_enter_sleep_state(), I don't think it's screen related.
No, it might be, actually. If you skip acpi_enter_sleep_state(), your machine
doesn't really suspend, so in fact you only confirm that your drivers implement
.suspend() and .resume() hooks correctly.
First, you can check if the patch
http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc3/patches/20-ACPI-preserve-the-ebx-value-in-acpi_copy_wakeup_routine.patch
helps, by chance.
Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
place where it really fails.
Also, please read Documentation/power/basic-pm-debugging.txt .
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
Hi.
On Sat, 2007-06-02 at 00:37 +0200, Rafael J. Wysocki wrote:
> On Saturday, 2 June 2007 00:17, Olaf Dietsche wrote:
> > "Rafael J. Wysocki" <[email protected]> writes:
> >
> > > On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
> > >> "Rafael J. Wysocki" <[email protected]> writes:
> > >>
> > >> > On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
> > >> >> When I resume, everything seems to come up (fan becomes busy, disk and
> > >> >> dvd spin up for a short time),
> > >> >
> > >> > Hmm, what about the screen?
> > >>
> > >> When the laptop is dead, screen remains black.
> > >>
> > >> When I skip acpi_enter_sleep_state(), the screen works like everything
> > >> else.
> > >
> > > I think you should try s2ram (http://en.opensuse.org/s2ram) as the first step.
> >
> > It doesn't work. I tried all options "s2ram -f (-s, -p, -m, -r, -a 1, -a 2,
> > -a 3)" one after the other.
> >
> > Since the screen (or any other device) works without problems, when I
> > skip acpi_enter_sleep_state(), I don't think it's screen related.
>
> No, it might be, actually. If you skip acpi_enter_sleep_state(), your machine
> doesn't really suspend, so in fact you only confirm that your drivers implement
> .suspend() and .resume() hooks correctly.
Actually, you don't even confirm that. Chips that would be powered down
by entering the sleep state will not be powered down in this scenario,
so failures to properly reinitialise them in resume routines won't be
noticed.
Regards,
Nige
On Sat, June 2, 2007 00:17, Olaf Dietsche wrote:
> It doesn't work. I tried all options "s2ram -f (-s, -p, -m, -r, -a 1, -a 2,
> -a 3)" one after the other.
>
> Since the screen (or any other device) works without problems, when I
> skip acpi_enter_sleep_state(), I don't think it's screen related.
I use "s2ram -f -p -s -a 3", maybe you need some exotic combination too.
Greetings,
Indan
Olaf Dietsche wrote:
> resume from suspend to ram doesn't work for my laptop and never
> has. So, this is not a regression.
>
> Hibernate (aka suspend to disk) works, however.
>
> When I resume, everything seems to come up (fan becomes busy, disk and
> dvd spin up for a short time), but the machine is not responding to
> anything - neither keyboard, mouse nor ping from another machine. The
> laptop is effectively dead and only a power cycle helps.
>
I understand that every case of failed resume is different, but this looks
quite similar to the problem I have:
http://bugzilla.kernel.org/show_bug.cgi?id=7499, at least symptoms :)
> I've tried a minimal config and init=/bin/bash as well, but the result
> is the same.
>
One more similarity :) And BTW s2ram does not work either.
-andrey
Hi Olaf,
I'm also having troubles with the resume part of STR, although since
your hardware is significantly different to mine, the cause is likely
to be different.
On 6/2/07, Rafael J. Wysocki <[email protected]> wrote:
> > >>
> > >> > On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
> > >> >> When I resume, everything seems to come up (fan becomes busy, disk and
> > >> >> dvd spin up for a short time),
>
> First, you can check if the patch
>
> http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc3/patches/20-ACPI-preserve-the-ebx-value-in-acpi_copy_wakeup_routine.patch
>
> helps, by chance.
(Rafael's suggestion may help you but it didn't help me)
> Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
> place where it really fails.
I modified my kernel source so it uses PM_TRACE to trace both the
suspend, and whether the BIOS ever jumps back into the kernel on
resume. (In my case, I don't think the BIOS is doing the jump).
I also compiled with only the bare minimum of options turned on, and
use an initramfs to rule out device interactions.
If what I did is useful to you, you can find it here:
http://bugzilla.kernel.org/show_bug.cgi?id=7988
And if you haven't already (and your problem occurs with a stock
kernel), you might want to log this as a bug like I did.
Hope this helps.
Mitch.
"Rafael J. Wysocki" <[email protected]> writes:
> Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
> place where it really fails.
First I augmented my minimal config kernel with some TRACE_RESUME()s:
--- a/kernel/power/main.c 2007-05-27 23:48:05.000000000 +0200
+++ b/kernel/power/main.c 2007-06-03 22:28:46.000000000 +0200
@@ -223,6 +223,7 @@
pr_debug("PM: Finishing wakeup.\n");
suspend_finish(state);
Unlock:
+ TRACE_RESUME(error);
mutex_unlock(&pm_mutex);
return error;
}
@@ -303,6 +304,7 @@
error = enter_state(state);
else
error = -EINVAL;
+ TRACE_RESUME(error);
return error ? error : n;
}
With this test script:
#! /bin/sh
sync
echo 1 >/sys/power/pm_trace
echo mem >/sys/power/state
shutdown -rn now
I got alternating
hash matches drivers/base/power/resume.c:58
and
hash matches kernel/power/main.c:307
> First, you can check if the patch
>
> http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc3/patches/20-ACPI-preserve-the-ebx-value-in-acpi_copy_wakeup_routine.patch
Then I applied this patch, but it doesn't change anything.
But either way the script never reaches "shutdown -rn now". So, it
seems, that my laptop does a full resume every other reboot, but it
never returns to userspace.
> Also, please read Documentation/power/basic-pm-debugging.txt .
Regards, Olaf.
On Sunday, 3 June 2007 23:20, Olaf Dietsche wrote:
> "Rafael J. Wysocki" <[email protected]> writes:
>
> > Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
> > place where it really fails.
>
> First I augmented my minimal config kernel with some TRACE_RESUME()s:
>
> --- a/kernel/power/main.c 2007-05-27 23:48:05.000000000 +0200
> +++ b/kernel/power/main.c 2007-06-03 22:28:46.000000000 +0200
> @@ -223,6 +223,7 @@
> pr_debug("PM: Finishing wakeup.\n");
> suspend_finish(state);
> Unlock:
> + TRACE_RESUME(error);
> mutex_unlock(&pm_mutex);
> return error;
> }
> @@ -303,6 +304,7 @@
> error = enter_state(state);
> else
> error = -EINVAL;
> + TRACE_RESUME(error);
> return error ? error : n;
> }
>
> With this test script:
>
> #! /bin/sh
>
> sync
> echo 1 >/sys/power/pm_trace
> echo mem >/sys/power/state
> shutdown -rn now
>
> I got alternating
> hash matches drivers/base/power/resume.c:58
> and
> hash matches kernel/power/main.c:307
>
> > First, you can check if the patch
> >
> > http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc3/patches/20-ACPI-preserve-the-ebx-value-in-acpi_copy_wakeup_routine.patch
>
> Then I applied this patch, but it doesn't change anything.
>
> But either way the script never reaches "shutdown -rn now". So, it
> seems, that my laptop does a full resume every other reboot, but it
> never returns to userspace.
I'm still suspecting that the problem is related to your graphics adapter.
What graphics adapter do you have in the box?
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
"Rafael J. Wysocki" <[email protected]> writes:
> On Sunday, 3 June 2007 23:20, Olaf Dietsche wrote:
>
>> But either way the script never reaches "shutdown -rn now". So, it
>> seems, that my laptop does a full resume every other reboot, but it
>> never returns to userspace.
>
> I'm still suspecting that the problem is related to your graphics adapter.
Maybe it's the most common problem, but why do you think so? Even with
a black screen the kernel should return to userspace.
> What graphics adapter do you have in the box?
0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0148 (rev a2) (prog-if 00 [VGA])
Subsystem: QUANTA Computer Inc: Unknown device 0729
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at c4000000 (32-bit, non-prefetchable) [size=64M]
Region 1: Memory at d0000000 (64-bit, prefetchable) [size=128M]
Region 3: Memory at c1000000 (64-bit, non-prefetchable) [size=16M]
Expansion ROM at c2000000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] #10 [0001]
Regards, Olaf.
On Monday, 4 June 2007 18:43, Olaf Dietsche wrote:
> "Rafael J. Wysocki" <[email protected]> writes:
>
> > On Sunday, 3 June 2007 23:20, Olaf Dietsche wrote:
> >
> >> But either way the script never reaches "shutdown -rn now". So, it
> >> seems, that my laptop does a full resume every other reboot, but it
> >> never returns to userspace.
> >
> > I'm still suspecting that the problem is related to your graphics adapter.
>
> Maybe it's the most common problem, but why do you think so? Even with
> a black screen the kernel should return to userspace.
Not necessarily. I have a test box that just crashes if the graphics card is
not posted.
> > What graphics adapter do you have in the box?
>
> 0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0148 (rev a2) (prog-if 00 [VGA])
> Subsystem: QUANTA Computer Inc: Unknown device 0729
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0, Cache Line Size: 0x08 (32 bytes)
> Interrupt: pin A routed to IRQ 10
> Region 0: Memory at c4000000 (32-bit, non-prefetchable) [size=64M]
> Region 1: Memory at d0000000 (64-bit, prefetchable) [size=128M]
> Region 3: Memory at c1000000 (64-bit, non-prefetchable) [size=16M]
> Expansion ROM at c2000000 [disabled] [size=128K]
> Capabilities: [60] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
> Address: 0000000000000000 Data: 0000
> Capabilities: [78] #10 [0001]
You may try to use 's2ram --force --vbe_post --vbe_mode', if you haven't tried
that already.
Still, if the card is a 7300 or higher, that need not work (at present we don't
know what magic is required to make these cards work).
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
Hi!
> > Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
> > place where it really fails.
>
> First I augmented my minimal config kernel with some TRACE_RESUME()s:
>
> --- a/kernel/power/main.c 2007-05-27 23:48:05.000000000 +0200
> +++ b/kernel/power/main.c 2007-06-03 22:28:46.000000000 +0200
> @@ -223,6 +223,7 @@
> pr_debug("PM: Finishing wakeup.\n");
> suspend_finish(state);
> Unlock:
> + TRACE_RESUME(error);
> mutex_unlock(&pm_mutex);
> return error;
> }
> @@ -303,6 +304,7 @@
> error = enter_state(state);
> else
> error = -EINVAL;
> + TRACE_RESUME(error);
> return error ? error : n;
> }
...
> I got alternating
> hash matches drivers/base/power/resume.c:58
> and
> hash matches kernel/power/main.c:307
>
> > First, you can check if the patch
> >
> > http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc3/patches/20-ACPI-preserve-the-ebx-value-in-acpi_copy_wakeup_routine.patch
>
> Then I applied this patch, but it doesn't change anything.
>
> But either way the script never reaches "shutdown -rn now". So, it
> seems, that my laptop does a full resume every other reboot, but it
> never returns to userspace.
But it returns to kernel... can you use more trace points to figure
out where it hangs?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
"Rafael J. Wysocki" <[email protected]> writes:
> You may try to use 's2ram --force --vbe_post --vbe_mode', if you haven't tried
> that already.
Unfortunately, this doesn't work either.
> Still, if the card is a 7300 or higher, that need not work (at present we don't
> know what magic is required to make these cards work).
It's a GeForce 6600 Go. Anyway, you were right with your assumption.
I installed the nvidia.ko (1.0-9755) kernel module and now the machine
comes back to life. Although the screen stays black as before, I can
type blindly "shutdown -r now" or ssh into the laptop.
Regards, Olaf.
Pavel Machek <[email protected]> writes:
>> But either way the script never reaches "shutdown -rn now". So, it
>> seems, that my laptop does a full resume every other reboot, but it
>> never returns to userspace.
>
> But it returns to kernel... can you use more trace points to figure
> out where it hangs?
I haven't looked, but I guess this is somewhere in sysfs.
I made some small progress. With the nvidia.ko kernel module loaded,
my laptop returns to userspace. I'll investigate this further.
Regards, Olaf.
On Thu 2007-06-07 21:54:51, Olaf Dietsche wrote:
> Pavel Machek <[email protected]> writes:
>
> >> But either way the script never reaches "shutdown -rn now". So, it
> >> seems, that my laptop does a full resume every other reboot, but it
> >> never returns to userspace.
> >
> > But it returns to kernel... can you use more trace points to figure
> > out where it hangs?
>
> I haven't looked, but I guess this is somewhere in sysfs.
>
> I made some small progress. With the nvidia.ko kernel module loaded,
> my laptop returns to userspace. I'll investigate this further.
So it _was_ video card related :-). With working console, it should be
easy to debug with printk.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Olaf Dietsche <[email protected]> writes:
> I installed the nvidia.ko (1.0-9755) kernel module and now the machine
> comes back to life. Although the screen stays black as before, I can
> type blindly "shutdown -r now" or ssh into the laptop.
Here's an update: when I additionally install the complete nvidia
package, including the binary X server modules, my screen becomes
active on resume.
This is not really satisfactory, since my console stays black. Anyway,
this is another step forward, nonetheless.
Regards, Olaf.
Hi!
> resume from suspend to ram doesn't work for my laptop and never
> has. So, this is not a regression.
>
> Hibernate (aka suspend to disk) works, however.
>
> When I resume, everything seems to come up (fan becomes busy, disk and
> dvd spin up for a short time), but the machine is not responding to
> anything - neither keyboard, mouse nor ping from another machine. The
> laptop is effectively dead and only a power cycle helps.
>
> I've tried a minimal config and init=/bin/bash as well, but the result
> is the same.
Beeping patch? It is in -mm now. noapic nolapic and nosmp are useful,
too.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Pavel Machek <[email protected]> writes:
>> resume from suspend to ram doesn't work for my laptop and never
>> has. So, this is not a regression.
[...]
> Beeping patch? It is in -mm now. noapic nolapic and nosmp are useful,
> too.
With the proprietary nvidia module, the laptop resumes, but the screen
stays black. Meanwhile I tested the nvidiafb module, with identical
results: machine comes back from suspend, but with a black screen. Now
I cann ssh into it and do a proper shutdown or whatever. This is of
course nonsatisfying and I'm still playing around.
I haven't tested noapic, nolapic so far. This is a UP kernel.
Regards, Olaf.
Hi all!
On Die, 12 Jun 2007, Pavel Machek wrote:
> > When I resume, everything seems to come up (fan becomes busy, disk and
> > dvd spin up for a short time), but the machine is not responding to
> > anything - neither keyboard, mouse nor ping from another machine. The
> > laptop is effectively dead and only a power cycle helps.
> >
> > I've tried a minimal config and init=/bin/bash as well, but the result
> > is the same.
>
> Beeping patch? It is in -mm now. noapic nolapic and nosmp are useful,
> too.
Ok, no beeping at all. Nothing after resume, only fan. And I did not
forget to activate the BEEP line.
So where can I go from here? DSDT hacking? Anything else?
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <[email protected]> Vienna University of Technology
Debian Developer <[email protected]> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
Anyone who is capable of getting themselves made President
should on no account be allowed to do the job.
--- Some wisdom from The Book.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
Hi!
> >> resume from suspend to ram doesn't work for my laptop and never
> >> has. So, this is not a regression.
> [...]
> > Beeping patch? It is in -mm now. noapic nolapic and nosmp are useful,
> > too.
>
> With the proprietary nvidia module, the laptop resumes, but the screen
> stays black. Meanwhile I tested the nvidiafb module, with identical
> results: machine comes back from suspend, but with a black screen. Now
> I cann ssh into it and do a proper shutdown or whatever. This is of
> course nonsatisfying and I'm still playing around.
>
> I haven't tested noapic, nolapic so far. This is a UP kernel.
noapic/nolapic will not help with video issue. try s2ram from
suspend.sf.net.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Thu, 2007-06-14 at 19:56 +0000, Pavel Machek wrote:
>
> noapic/nolapic will not help with video issue. try s2ram from
> suspend.sf.net.
Also there is (unashamed plug)
http://people.freedesktop.org/~hughsient/quirk/
Richard.
Pavel Machek <[email protected]> writes:
> noapic/nolapic will not help with video issue. try s2ram from
> suspend.sf.net.
I already tried s2ram, no improvement so far.
Regards, Olaf.
Hi Pavel, hi all,
On Son, 22 Jul 2007, Pavel Machek wrote:
> > Ok, no beeping at all. Nothing after resume, only fan. And I did not
> > forget to activate the BEEP line.
> >
> > So where can I go from here? DSDT hacking? Anything else?
>
> Hmm, it was 'hardware debugger' time when I hit similar problem few
> years ago :-(.
Something else helped, don't ask me what, but with
2.6.32-rc2
and
s2ram -f -p
it does work. Even with X and 3D running. Nice.
Anything I should do now?
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <[email protected]> Vienna University of Technology
Debian Developer <[email protected]> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
RAMSGATE (n.)
All institutional buildings must, by law, contain at least twenty
ramsgates. These are doors which open the opposite way to the one you
expect.
--- Douglas Adams, The Meaning of Liff
On Sun 2007-08-12 18:52:02, Norbert Preining wrote:
> Hi Pavel, hi all,
>
> On Son, 22 Jul 2007, Pavel Machek wrote:
> > > Ok, no beeping at all. Nothing after resume, only fan. And I did not
> > > forget to activate the BEEP line.
> > >
> > > So where can I go from here? DSDT hacking? Anything else?
> >
> > Hmm, it was 'hardware debugger' time when I hit similar problem few
> > years ago :-(.
>
> Something else helped, don't ask me what, but with
>
> 2.6.32-rc2
>
> and
>
> s2ram -f -p
>
> it does work. Even with X and 3D running. Nice.
>
> Anything I should do now?
Submit whitelist entry to [email protected]?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html