Red Hat Bugzilla – Bug 245037
Dell Latitude D620 won't resume from suspend
Last modified: 2015-03-04 20:18:49 EST
Description of problem:
My Dell Latitude D620 laptop won't resume from suspend mode. When I press the
power button to resume it, the display remains off.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Panel menu: System -> Suspend.
2. Press the computer's power button.
The display remains blank with the backlight off. The power light is on, the
hard disk light comes on once for a second or two, and the Bluetooth light
flashes continuously (even though I have disabled Bluetooth in the BIOS).
The display comes on and shows the gnome-screensaver password prompt so I can
unlock the screen and continue working.
- I am using iwl3945, but I set SUSPEND_MODULES="iwl3945 mac80211" in
/etc/pm/config.d/unload_modules , and I get a message about iwl3945 being
unloaded when I suspend. The same behavior happened with the ipw3945 driver.
- Resume worked fine on FC6 kernels with the ipw3945 driver.
- I recently unset my system password in the BIOS. Before I unset the password,
the behavior on resume was as follows: the BIOS password prompt appears, I enter
the password, and then the display shows the four yellow letters "Linu" in the
top row of the screen on a black background.
I have the same problem
Manmathan, what model of computer and versions of software are you using?
I tried the recently released kernel-126.96.36.199-27.fc7 and the problem went away.
Thus, I conclude that the bug was in kernel-2.6.21-1.3228.fc7; I'm changing the
component accordingly. Alas, I can't use the new kernel because it does not
recognize my wireless card, which is a more serious problem for which I will
file a separate bug.
Manmathan, if you see the problem again with kernel-188.8.131.52-27.fc7, please
comment and I will reopen the bug.
(In reply to comment #3)
> Alas, I can't use the new kernel because it does not
> recognize my wireless card, which is a more serious problem for which I will
> file a separate bug.
Never mind, bug 249253 purports to solve this.