Matthew Garrett wrote:
               Vendor: Hewlett-Packard
-               Version: 68BDD Ver. F.0F
-               Release Date: 07/23/2004
+               Version: 68BDD Ver. F.11
+               Release Date: 11/22/2004


Ok, so you both have different BIOS versions and different CPUs.

S3 works for me with both BIOS F.0F, which I was using before, and F.11, which I flashed today after learning it existed.


Everything else looks pretty identical. Could you both
stick /proc/acpi/dsdt up somewhere so I can check if there are any
relevant looking differences?

I would advise trying to compile a custom kernel from scratch with my .config first.


I got S3 working first with a very basic kernel config, but I couldn't get it to work with my usual kernel. Assuming it was some feature that caused the problem, I started disabling features in the hope of getting it to work, but I ended up with two different kernels with seemingly irrelevant differences, of which one would succesfully resume and one wouldn't. So I started added features to the other kernel, and I never found out what caused the problem.

I'm not saying that this is not deterministic, but I am saying that, at least in my case, it's not obvious what it is that stops S3 from working. :-)


Cheers, Lorenzo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Reply via email to