Suspend/Hibernate do not function on Dell Inspiron 9300

if you sure that this bug report is not duplicate, and you pretty sure that this is a real bug.

You can set it to Confirmed and assign it to laptop-team

Tenshu

Verified this on both Breezy and Dapper. I've located many reports of the same (for example see http://ubuntuforums.org/archive/index.php/t-76021.html) so it's probably not a fluke on my part.

I suspect that this could be specific to the NVidia Geforce Go 6800 graphics chipset or some other peculiarity with some series of the Inspiron 9300, as I have seen reports of suspend working in Breezy with the ATI-equipped version of the machine (see http://rtr.ca/dell_i9300/breezy.html http://www.oreillynet.com/pub/wlg/8736?wlg=yes) but none for the NVidia version. Since I suspected the NVidia graphics chip is part of the problem, I've tried both the restricted binary and the open source X drivers for this chipset, but that has made no difference.

I was going to file a new bug, but I think I will add some additional information to this bug first. Please let me know if this information warrants a new bug:

1. I am also seeing this problem on a new Dell Inspiron 9400. At first I thought it might be related to the Core Duo, but maybe not - it also occurrs when booting a single processor kernel.

2. I have seen this with both Breezy, and with the current Dapper kernel (as of 2/5/2006).

3. This Inspiron 9400 does have an Nvidia card (Geforce go 7800), but I have also tried with the xorg NV driver, and also from non-X configuration with the same results.

4. I tried installing powersaved and hibernating with the powersave scripts, but the result is the same - hang on resumeing. At least powersave doesn't blank the screen, so I can see where it hangs (I will attach an image of the screen at the hang point).

5. I have also installed SUSE 10.0 which is able to resume from hibernate out of the box, so it must be possible with at least some versons of swsusp.

6. I will attemp to attach a picture I took of the screen at the point where it hangs. This was taken using "powersave --suspend-to-disk" instead of the normal ubunbu "/etc/acpi/hibernate.sh" because the latter blanks the screen and I cannot see anything.

Regards,
Dave

This is the image of the Inspiron 9400 screen at the point that the resume process resumes. I don't know if this will provide any useful information, but here it is. As noted before, this was resuming from using "powersave --suspend-to-disk" starting from a non-X console (X not running at all). If I use /etc/acpi/hibernate.sh, the screen is blank and there is no useful information.

Regards

Dave

Sorry, in the above comment, I meant to say that the screen image was taken at the place where the resume process _hangs_, (not resumes).

Dave

I have an inspiron 9300 with an 6800 go. I use the 2.6.15.+ patches from rtr.ca and the binary drivers plus the patch from

http://www.nvnews.net/vbulletin/showthread.php?t=62021
1.0-8178 for x86-64/em64t and x86 updates (01-22-2006)

Suspending/resuming (s3/s4) inside X seems to work fine using the binary drivers, the x.org native driver was not able to restore the screen
on resume.

However the vt's are not restored, I tried vbetool post/save/restore but none of the options seem to restore the screen. Please note I did not use the suspend script from rtr.ca ( echo mem > /sys/power/state )

Use driver video propietary or not propietary?

I'm problem in susspend and hinbernate with driver propietary.

Revise:
https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresarioV2417LA

Regeards,
Caravena

I had a similar problem with a Dell Latitude D610 running Dapper Flight 6. My laptop would seemingly suspend fine, but when I powered back on the screen would remain off, but the system seemed to be live.

I scoured dozens of search results before finding this:

http://www.kcore.org/?menumain=4&menusub=2

I created a script called 01-wakeuplcd.sh in /etc/acpi/resume.d. Inside that I simply placed echo 0x80000001 > /proc/acpi/video/VID/LCD/state

Laptop now seems to be suspending to RAM and resuming ok.

Could this be a duplicate of Bug #34648: "Dell Inspiron 500m / No Recovery after Sleep"

(this MAY be a seperate bug)

I have a Dell Inspiron E1505 (6400).

The system suspends but has issues coming out of suspend.

The system seems to do one of two things coming out of suspend. 1) It will lock up with the screen off. I do not get disk activity and can't seem to do anything with the system... or 2) The system goes back to my desktop... But in reality the disk or disk driver has crashed. (If I go to the console and try to log in I get disk errors).

A few notes:
* I have tried the hard drive reset option in acpi-support with similar results.
* I have tried both the 386 and 686 kernels with similar results.
* I have tried setting acpi_sleep=s3_bios with similar results. (seems to encourage the later example explained above)

Currently using hybernate.... but would love suspend to work :)

Exactly same bug using Inspiron 9400

Ubuntu 7.10
Compiz-Beryl activated
Intel Duo Core 2 Ghz
Nvidia Geforce 7900 GO GS (using proprietary drivers)
Intel 3945ABG (using proprietary drivers)
Running kernel 2.6.22-14-generic
I also have Bluetooth activated

Suspend or Hibernate don't work at all

i'm running an hp pavillion amd athlon 2ghz with nvidia gforce 4 integrated on nforce 2.
i did not have a problem in dapper drake (6.10). but suspend and hibernate do not work in gutsy.
system goes to sleep or hibernates normally but never restores.
i am writing this post to tell everyone that this bug is not only for dell inspiron laptops.

I can confirm that this bug also occurs on HP Pavilion Laptops (dv5000). I am running Gusty (7.10) with a 2Ghz Intel Core Duo (T2500) and a Nvidia Go 7400. I have experienced the problem with both the restricted drivers and the Nvidia released drivers. I have the same experience, the system goes to sleep, but fails when trying to resume. I get a split second of disk activity and then the system just hangs at a black screen. All I can do is power down.

Suspend and hybernate have been a recurent problem under ubuntu since I use it (2 years) for Inspiron 9400. I think, and I'm sad to say, this is absolutely not one of the first concerns of kernel developpers. I just hope it will eventually works as it is a major bug and it's hard to convince people to switch to linux when such a "simple" function doesn't work at all.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Jeremy Thornhill : Can you test current intrepid and say if kernel 2.6.27 fixes the problem?

I have a inspiron 9300 and I tested intrepid 2.6.27 kernel and it resumes correctly after suspend. I have problems with ati driver after resuming, nm crashes and bluetooth seems to stop working. I don't reproduce any other issues so far.

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

It works for me, thanks!

Summary of the below: 7.10 suspend & hibernate didn't work; 8.10 does; on Dell
Inspiron 9300 with ATI graphics & Intel wifi.

Details:

I was using 7.10 Gutsy on my Inspiron 9300, using ATI proprietary fglrx driver, and
neither suspend nor hibernate worked. They would go through the motions, but
after a suspend it would not resume for any stimulus, and after a hibernate the next
boot would act as if there was no saved image.

I recently installed 8.10 Intrepid (to a new hard disk, having damaged the old one).
Suspend and hibernate now both work almost perfectly. I am again using the ATI
proprietary fglrx driver.

Successes:

  - hibernate, then boot up and resume
  - suspend, then resume
  - multiple suspend/resume cycles from a single boot (10+ cycles, no problem)

Slight issues:

  - Network Manager behavior is slightly variable, sometimes it comes out of a
    suspend and immediately connects to the local WLAN, other times it comes
    up with [ ] Enable Networking un-checked and I must check it before the WLAN
    comes up. In all cases it does successfully connect once I get nm's attention.

  - Once (only, out of 30+ suspend/resume and 3 hibernate/resume cycles), my
    USB mouse was not detected. This is an optical mouse with easily visible red
    LED. In the bad resume, the LED lit up (showing that the mouse had power),
    and it would show up in `lsusb` output, but moving and clicking the mouse had
    no effect on X. I unplugged and replugged the mouse several times to the
    same USB port and then to different ones. On about the 4th replug, it started
    working. /var/log/messages showed all of the plug/unplug events, I didn't see
    any differences in the USB stack setup each time, it just insisted on being
    "seen but not heard" for a while.

  - One horrible bug I experienced: once when trying to suspend using the power
    button, the system wasn't recognizing the button (normally it does). I gave up
    after a few seconds and used the "Switch users or shut down" Fast User
    Switch Applet menu to suspend.

    Later, on resume, I immediately started using the mouse, moved it to some UI
    element on the screen and left-clicked _just in time_ for the much-delayed
    power button action to finally come through. As I was reaching for the mouse
    button it popped up the "Shut Down the Computer" dialog; my click landed
    right on "Restart" -- so I unintentionally rebooted!

    Suggestion (I will raise this as a separate bug report): during resume from
    either suspend or hibernate, clear all human interface device input queues.
    Any sort of typeahead, mouseahead or (in this case) power-button-
    event-ahead after a resume is going to be unexpected at best.

    But this seems like a generic issue, nothing to do with Dell 9300.

HW & supporting SW details, tested to work through resume cycles:

  Dell Inspiron 9300 (Ubuntu 8.10 Intrepid Ibex, 2.6.27-9 kernel, gnome)
  Broadcom BCM4401-B0 100baseT NIC (b44 driver)
  Intel PRO/Wireless 2915ABG [Calexico2] wireless NIC (ipw2200 driver)
  ATI M22 [Mobility Radeon X300] (fglrx driver v. 8.54.3; compiz fully operational)
  Intel I...