http://bugzilla.kernel.org/show_bug.cgi?id=5809
------- Comment #70 from [EMAIL PROTECTED] 2008-05-05 20:10 ------- Hi, Thanks for the test. It seems that the LID initial state is right after the custom DSDT is used. But it brings some new problems. Will you please confirm whether the problems in comment #68 exists if not using the custom DSDT? Maybe what I said in comment #66 is not very clear. a. About the initial state of the LID even when the LID is open Maybe the microsoft windows doesn't care the initial state of the LID. It only cares whether the LID button is pressed and the LID event is received. When it receivces the LID event that the LID is pressed, it will enter the standby mode. In fact the problem is caused by the broken bios. If the state of LID is stored to the global variable of LIDS in the course of EC initialization, we can get the correct state of the LID using /proc/acpi/button/lid/LID0/state. b. takes 12 seconds to receive the LID event when the LID is pressed. From the log in comment #65 the LID event can be received when LID is pressed. But it need wait for 12 seconds to recognize the state of the LID. We had better confirm whether the windows enter the standby mode immedidately after the LID is pressed. If no, I think that it is related with BIOS. Please test it on your sister's laptop. Thanks. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
