Shutdown problem in Dell Inspiron E1505

[ant2ne]

My Bug: I can go into suspend mode just fine. But if I try to restart or shut down in anyway other than "powerdown now" It hangs up with a dark screen. And doesn't shut down or restart. I'm also having other problems related to my graphics card so I think the issue is somewhere there. My card is an i810.

Dell Inspiron E1505 running Kubuntu 6.10 and Beryl

(I was told by Paul Sladen -> ant2ne: Hi, your issue sounds like a new one; please could you open a new bug report specifically for your laptop (please put "Dell Inspiron E1505" somewhere in the subject).)

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Beryl is neither provided nor supported by Ubuntu so could you please try recreating the issue without using beryl? Thanks in advance.

[ant2ne (tony-78280z)]

Sorry yea, I should have mentioned that. With or without Beryl running it has this shut down bug.

When I first installed the Kubuntu OS I had no problems. I could shut down and restart properly in every way. This bug only manifested after updating, installing the ndiswrapper and r1409747.exe for my wireless card, and making other modifications for this particular computer model.

Since it still shuts down with the "sudo shutdown now" command I haven't uninstalled Beryl or any other device as I can live with this bug.

[Brian Murray (brian-murray)]

What other issues are you having with your video card?

[ant2ne (tony-78280z)]

I can't change most display settings at all. And I can't change my monitor off power saving features without crashing my GUI on my next restart. (Beryl or no Beryl). Read about it here...

http://kubuntuforums.net/forums/index.php?topic=3080844.new;topicseen#new

I have other Beryl bugs, but like you said you don't support it. But the bugs are wierd. And are not consistant. Read about it here...

http://kubuntuforums.net/forums/index.php?topic=3080925.new;topicseen#new

I'm thinkin I had one other minor issue, but I can't remember right now. If I do I'll post more.

[Brian Murray (brian-murray)]

Are you still having an issue shutting down your system?

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

[Jonathan Anderson (jonathan-anderson)]

My problem sounds a lot like this one. I also have an Inspiron 6400/E1505.

My video card is a Mobility Radeon X1400 (open-source Avivo driver), but since I have the same problem at the command line and the original reporter has Intel graphics, I'm gonna guess this is some kind of BIOS issue.

[Jonathan Anderson (jonathan-anderson)]

More information!

The following methods give me a perfect suspend+resume cycle:

sudo /etc/acpi/sleep.sh force
sudo /usr/sbin/hibernate-ram (after killing ipw daemon)
sudo pmi action suspend

Note that I've installed the "hibernate" package manually while diagnosing the issue.

The following methods have problems:

"Suspend" in KDE Logout Dialog
Suspends OK, resumes to a blank screen. I can switch to a VT (blind), login and sudo reboot (also blind; not even the VTs come back from suspend). The screen comes back to life when I hit the shutdown usplash.

/usr/lib/hal/scripts/hal-system-power-suspend
I get an error message:
org.freedesktop.Hal.Device.UnknownError
No back-end for your operating system

/usr/lib/hal/scripts/linux/hal-system-power-suspend-linux
Script seems to hang; after 30s or so I Ctrl+C'd it with no problem.

sudo /etc/acpi/sleep.sh
Script returns immediately; no error messages get printed.

It's my understanding that all of these roads should lead to Rome (a good suspend+resume cycle), but there are clearly big differences. The really troubling bit is that my screen is dead when I come back from a KDE-initiated suspend.

I use kpowersave... is this a problem? I can try the guidance power manager (as well as echo "mem" > /sys/power/state)...

[Jonathan Anderson (jonathan-anderson)]

Even more info!

kde-guidance-powermanager's Suspend feature and the raw sysfs suspend (echo "mem" > /sys/power/state) both result in behaviour that's very much like the KDE Logout dialog's Suspend; the only difference is that the screen remains dark until reboot (not even the shutdown splash screen shows up).

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for the kernel version the bug was submitted about. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.

[Jonathan Anderson (jonathan-anderson)]

I neglected to mention that I am currently running Gutsy... I think it was a problem on Feisty, as well, but before Avivo, I always blamed it on FGLRX.

[Jonathan Anderson (jonathan-anderson)]

uname -a:
Linux nick 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux

/proc/version_signature:
Ubuntu 2.6.22-10.30-generic

[Brian Murray (brian-murray)]

Jonn - Could you please also provide the additional information requested at https://wiki.ubuntu.com/DebuggingACPI . Thanks in advance.

[Jonathan Anderson (jonathan-anderson)]

I followed the procedure at https://wiki.ubuntu.com/DebuggingKernelSuspend... I now have a bunch of /var/log files that show being edited in AD 1916, but there's also something that looks useful:

[ 2.032000] Magic number: 7:951:842
[ 2.032000] hash matches device ptyu8
[ 2.032000] hash matches device ptyrb

https://wiki.ubuntu.com/DebuggingKernelSuspend says that I should rmmod the second driver (ptyrb), but lsmod | grep pty shows absolutely nothing.

I'll try suspend/resume with ptyrb in /etc/default/acpi-support's MODULES list.

Is there anything else I can do that might help?

[Jonathan Anderson (jonathan-anderson)]

Suspend/resume with ptyrb in the MODULES list (of /etc/default/acpi-support) has no effect... KDE's suspend still resumes with a blank screen.

[sqlpython (sqlpython)]

Solved: Dell 1501 amd64 won't Shutdown after fglrx install.

 After I installed ATI fglrx on my Del 1501 amd64 it would not Reboot/Shutdown/Logout..
I am running Feisty 7.04 AMD64 kenel..
Here is my fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON XPRESS Series
OpenGL version string: 2.0.6334 (8.34.Cool

Here is what I did to fix the Problem. I hope it helps someone else.

******************
** These 3 steps correct/allow per KDE GUI Logout/Reboot/Shutdown

# Kubuntu 7.04 amd64 w/ ATI fglrx Installed
# Now Won't Shutdown w/ KDE GUI Log Out
# The fix 3 Steps
#
1.. Modify GRUB's menu.lst
#
/boot/grub/menu.lst
add to kernel line acpi=force
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=a8862269-c6ee-4525-bb66-94f53824fdc1 ro quiet splash acpi=force
#
2.. Change KDE Session Manager
#
Also K > Settings > KDE Components > Session Manager
Change [Default Shutdown Option] to (X) Turn Off Computer
#
3.. Modify kdmrc
# /etc/kd3/kdm/kdmrc
# ADD to Section
#[X-*-Core]
TerminateServer=true
************************
Th-The Th-The Th-The That's All Folks! (C) Looney Tunes

[Alexander Kriegisch (alexander-kriegisch)]

I also have a Dell Inspiron 1501 and am running Kubuntu 7.10 32-bit (i386):
Linux xander 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Somewhere else I read that warnings like these are caused by running a 32-bit Ubuntu on a 64-bit system:
[ 0.516000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[ 0.604000] PCI: BIOS BUG #81[49435000] found
[ 0.628000] PCI: Cannot allocate resource region 7 of bridge 0000:00:05.0
[ 0.628000] PCI: Cannot allocate resource region 8 of bridge 0000:00:05.0

I tried different kernel switches and combinations thereof, e.g.
  - pci=nomsi
  - pci=nomsi noapic nolapic
  - noapic nolapic
  - acpi=force
  - acpi=force irqpoll
but to no avail. I cannot restart the system of shot down with switch-off. I alsways have to manually switch off the system.

BTW, I am running the latest firmware with high precision timer and tried switching it on as well as off. No difference in behaviour. I really don't know what else to try.

[Alexander Kriegisch (alexander-kriegisch)]

LOL, typo:
> I cannot restart the system of shot down with switch-off.
was meant to be:
I cannot restart the system or shut down with switch-off.

Don't worry, nobody was shot down. ;-)

[Broderick (employeeno5)]

I use the same computer. I'm using Ubuntu 7.10 though not Kubuntu

I have the same shutdown/restart hang, at least from how you described it. The desktop closes and I would be left with just a blank black screen until holding down the power button. For a long time I did not know what was up. However, I had another bug that was preventing me from seeing the shutdown splash screen.

Now when shutting down I get the orange meter emptying. Once it's empty, it sits there for a minute and then spits out the following output (I had to take this down by hand).

----------

NetworkManager: <warn> nm_signal_handler(): Caught signal 15, shutting down normally.

NetworkManager: <info> Caught termination signal

NetworkManager: <debug> [120447559.667015] nm_print_open_socks(): Open Sockets List:

NetworkManager: <debug> [120447559.667015] nm_print_open_socks(): Open Sockets List Done.

NetworkManager: <info> Deactivating device eth0.

NetworkManager: <info> Deactivating device eth1
_

---------

The underscore at the end is meant to represent the blinking cursor that will sit there and blink forever if I don't force my computers power off. So now I get this instead of the blank screen.

It makes sense though because when I have my wired connection plugged in the computer will hang on shutdown everytime without fail. If I'm connected wirelessly it will NEVER hang and always do a smooth shutdown/restart.

However, what to do about this problem I have no idea. I tried a variety of solutions offered up in this thread:
http://ubuntuforums.org/showthread.php?t=591229

I have had no results. If you checkout this thread read it carefully because though this problem seems to eventually be identified as relating to the network manager, there are many other people posting in it with hangs that have different descriptions or are related to video drivers or other things.

I even at one point simply removed the network manger and reinstalled it later. I've had no results with anything; the problem remains consistent.
I don't know if this matches your issue or not, but seeing as how we have the same computer I thought it might be helpful.

Many thanks to everyone trying to work this out.

[Launchpad Janitor (janitor)]

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 bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

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.

[Leann Ogasawara (leannogasawara)]

*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".