09-22-2024, 10:44 PM
Thank you. If you want to skip the majority of this reply, read this first sentence: THE PROBLEM IS SUSPENDING BY CLOSING THE LID. EVERY OTHER WAY SEEMS TO WORK!!!
My BIOS is a later release than yours, V1.04 vs 1.05. Everything else is the same.
I updated all packets from 6.8.0-44 to 6.8.0-45.
I duplicated all of your conditions exactly. USB mouse, no applications open, etc., but I made a mistake and pressed Log Out from the box after pressing the Log Out icon, rather than pressing Suspend. I had logged back in with no problem.
This time I entered Suspend correctly in the box from the Log Out icon in the menu. After 30 minutes I resumed by pressing H. Wonder of wonders, the "System behaved as expected, going straight to working desktop, reconnecting to network etc.." (quoting you).
Next, I ran the same test, but this time I closed the lid to enter suspend. After 30 minutes I raised the lid, moved the mouse, pressed H, Enter, power button, etc., but the PC did not resume. CTRL-ALT-F2 brought me to the console. One interesting point is that every time I enter a console after an unsuccessful resume I have to login with my name and password. This is not how I have Power Manager set up. I do not have to login when the PC does resume properly. Should I have to log in again to use a console? Could the problem be related to the resume routine not recognizing the current user? Remember my initial mistake when I logged out then logged in again before I did the above test that worked.
Next, I tested user credentials after shutting down with a poweroff command and rebooting. I logged out and logged back in, the same as I did before the successful resume. I duplicated everything but suspended by closing the lid again instead of using Menu > Log Out > Suspend. Resume failed. User login does not seem to be the problem.
Next, as a double check, I duplicated the exact successful suspend described at the beginning of this reply, including the logout > login. After 30 minutes, I pushed H. It resumed properly again.
Next, to retest the resume process itself without a logout > login variable, I duplicated the same successful suspend, using the menu, not the lid. Resume worked perfectly again.
The last suspend I did was to allow Power Management to suspend after 30 minutes of inactivity. I left the lid open and let the PC timeout by itself. I resumed after two hours by pressing H. Resume worked perfectly.
So, all of these trials suggest that suspending by closing the lid is the problem, not the user, not the login, not inactivity. The actual suspend > resume cycle seems to work just as it should.
Power Manager during these trials was set to suspend when the lid closes - both battery and external power.
Is there a way to check what closing the lid does differently from the other methods? Do you want to try to duplicate the issue by suspending your Aspire 722 by closing the lid? While you are there, please check if your Aspire can hibernate.
I did not attach a new resume log with this reply.
Another interesting observation is that when I log out from the menu, there is a split-second message in red that begins with "Failed to start Casper..." It is too fast for me to read the whole thing. What is that about?
Thank you, again.
My BIOS is a later release than yours, V1.04 vs 1.05. Everything else is the same.
I updated all packets from 6.8.0-44 to 6.8.0-45.
I duplicated all of your conditions exactly. USB mouse, no applications open, etc., but I made a mistake and pressed Log Out from the box after pressing the Log Out icon, rather than pressing Suspend. I had logged back in with no problem.
This time I entered Suspend correctly in the box from the Log Out icon in the menu. After 30 minutes I resumed by pressing H. Wonder of wonders, the "System behaved as expected, going straight to working desktop, reconnecting to network etc.." (quoting you).
Next, I ran the same test, but this time I closed the lid to enter suspend. After 30 minutes I raised the lid, moved the mouse, pressed H, Enter, power button, etc., but the PC did not resume. CTRL-ALT-F2 brought me to the console. One interesting point is that every time I enter a console after an unsuccessful resume I have to login with my name and password. This is not how I have Power Manager set up. I do not have to login when the PC does resume properly. Should I have to log in again to use a console? Could the problem be related to the resume routine not recognizing the current user? Remember my initial mistake when I logged out then logged in again before I did the above test that worked.
Next, I tested user credentials after shutting down with a poweroff command and rebooting. I logged out and logged back in, the same as I did before the successful resume. I duplicated everything but suspended by closing the lid again instead of using Menu > Log Out > Suspend. Resume failed. User login does not seem to be the problem.
Next, as a double check, I duplicated the exact successful suspend described at the beginning of this reply, including the logout > login. After 30 minutes, I pushed H. It resumed properly again.
Next, to retest the resume process itself without a logout > login variable, I duplicated the same successful suspend, using the menu, not the lid. Resume worked perfectly again.
The last suspend I did was to allow Power Management to suspend after 30 minutes of inactivity. I left the lid open and let the PC timeout by itself. I resumed after two hours by pressing H. Resume worked perfectly.
So, all of these trials suggest that suspending by closing the lid is the problem, not the user, not the login, not inactivity. The actual suspend > resume cycle seems to work just as it should.
Power Manager during these trials was set to suspend when the lid closes - both battery and external power.
Is there a way to check what closing the lid does differently from the other methods? Do you want to try to duplicate the issue by suspending your Aspire 722 by closing the lid? While you are there, please check if your Aspire can hibernate.
I did not attach a new resume log with this reply.
Another interesting observation is that when I log out from the menu, there is a split-second message in red that begins with "Failed to start Casper..." It is too fast for me to read the whole thing. What is that about?
Thank you, again.