View Full Version : Laptop wont shut down
kezzerdrix
Apr 7th 2008, 03:05 PM
IBM t60 will not shut down, restart, or log off with kubuntu 8.04 no errors given, system just hangs and you have to press the power button to re-initialize the shut down process.
Any ideas, help
Thanks
dibl
Apr 7th 2008, 09:19 PM
For curiosity sake, next time open a Konsole window and enter
sudo shutdown now -r and let's see whether it provides any errors.
Also, rather than use the power button, I recommend you follow this:
http://kubuntuforums.net/forums/index.php?topic=3088251.0
:)
Gumper
Apr 13th 2008, 01:17 PM
I'm having this same problem on my desktop. After shutting down, I get a blank, black screen and I have to momentarily hit the power button for the shutdown procedure to complete.
Gumper
Apr 13th 2008, 01:31 PM
Hi dibl,
I tried the command that you gave and it shutdown and restarted properly. Any idea why it doesn't do this with the Icon?
For curiosity sake, next time open a Konsole window and enter
sudo shutdown now -r and let's see whether it provides any errors.
Also, rather than use the power button, I recommend you follow this:
http://kubuntuforums.net/forums/index.php?topic=3088251.0
:)
dibl
Apr 13th 2008, 02:56 PM
It sounds like a KDE bug, since it works correctly from the command line but not from the GUI. You might search Launchpad and see if there is already a bug filed.
Gumper
Apr 13th 2008, 03:20 PM
I'll go ahead and see if I can find anything there. Thanks!
It sounds like a KDE bug, since it works correctly from the command line but not from the GUI. You might search Launchpad and see if there is already a bug filed.
damjan
Apr 17th 2008, 08:39 PM
hi,
In my case the same problem happens if ATI driver (closed source) is installed (via ENVY).
By removing it, PC works fine. So I do not think it is so much KDE problem.
br
D.
dibl
Apr 17th 2008, 08:43 PM
In my case the same problem happens if ATI driver (closed source) is installed (via ENVY).
By removing it, PC works fine. So I do not think it is so much KDE problem.
Nice catch, damjan! So we now know one cause of the problem! Thanks!
Gumper
Apr 18th 2008, 04:05 AM
I wish it was so easy for me. I'm using the standard open source flgrx drivers that come with Kubuntu and I still have this problem :-[ I even tried installing the restricted drivers, but I get the same thing.
hi,
In my case the same problem happens if ATI driver (closed source) is installed (via ENVY).
By removing it, PC works fine. So I do not think it is so much KDE problem.
br
D.
damjan
Apr 18th 2008, 04:46 AM
ok.
let me explain my problem a little bit more:
1. I had Kubuntu 7.10 and made installation of beta 8.04 over it
2. I have found that after that (installation of ENVY driver once again) notebook refuses to shut down or log out or restart ( but it restarts after installation ATI drivers in ENVY)
3. removing the ATI driver via ENVY notebook starts ok with VESA driver even made reboot, shut down etc
4. Upper post reportsthat even with OS ATI drivers problem somehow exists
5. On my notebook there is option to start with kernel 2.6.24-16 or 2.6.22-14. With last one notebook starts and shutdowns fine
to finish:
We need confirmation that this occures with upgrade from 7.10 to 8.04 if there is ATI driver installed
We need some solution to safely remove all ATI components from older release and made instaltion of new one
- or -
We need confirmation that with fresh clean install of 8.04 such a problem is none existing
br
D
miciurin
Apr 18th 2008, 05:26 AM
Its the ati driver. I have the exact same problem. If fglrx is installed, blank screen upon shutdown, but works from command line. Ati driver uninstalled, no problem with shutdown or reboot. I have seen that ati has a new driver out, 8.4. According to their release info, one of the fixes is that you no longer get a blank screen upon leaving Xserver. I have not installed it yet so i can't confirm if it fixes the shutdown or reboot hang.
Odur
Apr 18th 2008, 05:49 AM
Look at this bug https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/118605 Especially the last comment.
The patch mentioned was posted in a comment on 2008-03-19 by Ilja Pavkovic
stealthbanana
Apr 18th 2008, 01:06 PM
The quick fix to this is
sudo update-rc.d -f atieventsd remove
Gumper
Apr 18th 2008, 04:12 PM
What exactly does this do?
The quick fix to this is
sudo update-rc.d -f atieventsd remove
Odur
Apr 19th 2008, 09:54 AM
What exactly does this do?
The quick fix to this is
sudo update-rc.d -f atieventsd remove
It stops atieventsd from starting at startup. It's better to use the patch from the bug report I linked to two posts up.
Gumper
Apr 22nd 2008, 03:08 AM
Still no luck for me with getting this thing to shutdown. I even tried installing the restricted ATI drivers and then the patch found on Launchpad. No luck at all. The only way that it will shutdown is with "sudo shutdown now" command, or once I get the black screen, I momentarily press the main power button. Then it continues to shutdown and I see the splash screen.
Could anyone point me to something that I can check to possibly find out what is causing this problem? Are there any log files to check or anything like that? I'm desperate. I'll try anything.
Thanks
Odur
Apr 22nd 2008, 06:58 AM
Does it still hang on black screen if you kill atieventsd before trying to shutdown? If it does you probably have another bug than the one that the patch tries to resolve.
Gumper
Apr 23rd 2008, 03:26 AM
I just gave this a try and I get the same results ??? It's kinda weird that It hangs until I momentarily press the power button. Once I do that it continues to shutdown.
Does it still hang on black screen if you kill atieventsd before trying to shutdown? If it does you probably have another bug than the one that the patch tries to resolve.
kezzerdrix
Apr 23rd 2008, 06:48 PM
This is driving me crazy. I switched back to Ubuntu and when the screen would go to sleep or screensaver the system would lock up. I gave a detailed explanation and no one answered it. Kubuntu does everything right except it wont shut down correctly.
I installed envy through synaptic and it wont work either it just throws errors and dies.
This however is the lesser of two evils. I think openSuse works fine, just they don't have all the software and the community is kind of terse.
I could always revert to 7.10 everything worked there, I just wanted the updates and the new goodies.
Has anyone figured out a solution that works.
kezzerdrix
Apr 25th 2008, 12:12 AM
I even went to amd and downloaded the latest drivers. It still wont shut down on its own, in dual monitor mode it will not do screensavers, in fact if you even open the screensaver option box it just states it is loading .... forever.
I thought it was an issue with ati and gnome so I tried kubuntu and it appears to be an issue with ati and kde 3.5.9.... probably not something else changed from 7.10 to 8.04
Enunes
Apr 26th 2008, 02:53 AM
Another victim here ;D
quisoc
Apr 26th 2008, 07:22 AM
And another... ::)
squirrel
Apr 26th 2008, 04:30 PM
Another: Dell M1330 with Nvidia Go 8400M GS
When I push the on/off button shortly (not the emergency 10sec shutdown) it shuts down.
Snowhog
Apr 26th 2008, 04:55 PM
If you remove the quiet kernel line option from /boot/grub/menu.lst and reboot, you get to see all of the boot messages. Likewise, when you perform a shutdown, you get to see all the shutdown messages. On a laptop, you are going to see that there are two messages at the very end of the process, the last one being "System Halted"
At this point, all running processes have been stopped, and the kernel is waiting for the operator to tell it what to do next. At this point, you could type "sudo shutdown -r now" to reboot the system. Or, as you have experienced, you press the power off button for a second or so to turn the laptop off.
The underlying command that is executed with the shutdown sequence is:
shutdown -h
man shutdown tells us:
-h Requests that the system be either halted or powered off after
it has been brought down, with the choice as to which left up to
the system.
squirrel
Apr 26th 2008, 05:05 PM
Ok, but that's not the supposed behavior, right? :P
BTW: I was able to crash X11 with some little modification so it did not start anymore into the GUI (besides the Bulletproof X promise), after a 'sudo dpkg-reconfigure xserver-xorg' and a 'sudo /etc/init.d/kdm restart' it did work again :D
Snowhog
Apr 26th 2008, 05:44 PM
Ok, but that's not the supposed behavior, right? :P
Actually, I think it is (for laptops any way?). Bear in mind, that when you inform the kernel that you want to 'shutdown,' you are telling it you want to shutdown the OS. man shutdown does show you that the option -P (shutdown -P) tells the kernel to:
-P Requests that the system be powered off after it has been
brought down.
The 'problem' is in K Menu > System Settings > Advanced > Login Manager > Shutdown > Commands There you will note that Halt runs /sbin/poweroff and Reboot runs /sbin/reboot
However, /sbin/poweroff is a link to /sbin/reboot, and /sbin/reboot is a compiled executable file (so it can't be edited). I'm not (yet) comfortable with writing bash scripts, but one could be written in the /sbin directory that contained the shutdown -P command, saving it as say, turnoff, and use it instead. That should result in the laptop being turned off after the system is brought down.
squirrel
Apr 26th 2008, 05:48 PM
Actually, I think it is (for laptops any way?). Bear in mind, that when you inform the kernel that you want to 'shutdown,' you are telling it you want to shutdown the OS. man shutdown does show you that the option -P (shutdown -P) tells the kernel to:
-P Requests that the system be powered off after it has been
brought down.
Pardon me, but I doubt that. First, because this didn't happen with 7.10 and second because when I'm telling the system to shutdown (not logout) it should do 'shutdown -h 0' and nothing else. That's a desktop linux, isn't it?
Snowhog
Apr 26th 2008, 06:27 PM
But as I stated, and man shutdown shows, the -h option leaves it up to the system (OS) to decide if it's going to 'halt' or 'power off' the system. That it did as you expected in 7.10 and it isn't doing it in 8.04 is more of an indication that the programmers 'changed' something. It's quite possible that in 7.10 the underlying command was shutdown -P and not shutdown -h.
squirrel
Apr 26th 2008, 06:29 PM
Oops, sorry I did not read carefully. Nevertheless, in my opinion, it's a bug. ;D
Snowhog
Apr 26th 2008, 06:36 PM
... in my opinion, it's a bug. ;D
Keep in mind, a 'bug' is an observed behavior of a function or program that isn't what was 'programmed' to do. If, as I said, the action of the shutdown routine has been changed from -P to -h, then what is happening is by design, and therefore, not a bug. An annoyance? Yes, but not a bug. ;)
squirrel
Apr 26th 2008, 06:39 PM
Bug by design. ;D
C'mon that's not something that should happen on a easily operated desktop linux system.
Snowhog
Apr 26th 2008, 06:43 PM
I'll agree with that. One should have the option and the ability to configure the behavior of a system shutdown. Like I said, the 'link' is pointing to a compiled program, meaning, the user can't (easily) 'change the behavior' of what is clearly identified in System Settings, as a shutdown routine. That said (again), one could write a bash script to get around this problem.
squirrel
Apr 26th 2008, 06:46 PM
I get you, but that would be a workaround and not a real, permanent solution (for all users). Shouldn't we create a 'bug' (let's call it improvement) report?
BTW: After using the restricted nvidia driver my systems turns now off... ???
Gumper
Apr 27th 2008, 02:39 AM
I concur :) I think it's a bug as well.
Oops, sorry I did not read carefully. Nevertheless, in my opinion, it's a bug. ;D
kezzerdrix
Apr 27th 2008, 03:46 AM
I agree, I don't know how but this should be reported, to someone who can fix it. I can't use Ubuntu 8.04 because it won't work with ATI and dual monitors, worked fine in 7.10 but not in 8.04, if you lock the screen or if the screensaver kicks in only one monitor does what it is supposed to ... not really though because it locks up and has to be forced off.
Kubuntu worked fine in 7.10 and almost works in 8.04 with the exception of this issue and no screen savers in dual screen mode.
You know my setup doesn't seem that weird. I am the head of IT at my branch of an insurance company. I only have 500 employees that I watch over but the company has branches that scale up to over 5000. In my branch I have over 200 employees that have IBM t60's with integrated ATI x1300's hooked to a dock with two 19" monitors connected to it. I was about to suggest to some of my more advanced employees that they could try Ubuntu\kubuntu if they wanted to. But 8.04 has ruined that .... for now atleast.
stoer
Apr 27th 2008, 10:38 AM
Laptop
intel pentium 1.6m; 1.Gb ram; ATI radeon mobility 9700
Kubuntu RC with updates plus original kubuntu provided driver (ATI)
Shutdown and logging out worked.
Tried ENVY.
ENVY - Failed
reinstalled Final release, clean install.
added medibuntu sources
added ENVY, ENVY worked (ATI 8.03 driver)
Alot of video problems, shearing + stuttering when moving windows
COMPIZ added
Compiz works but has crashed twice.
Can't Log out
Can't shut down,
like the rest of you i just get a
Black screen (alt-F1, ctrl-alt-F1) = Black screen, no further effect.
Power button = shuts down.
Wierd!
Gumper
Apr 27th 2008, 02:00 PM
You can post a comment about it here:
https://bugs.launchpad.net/ubuntu/+bug/217079
Maybe it will eventually get fixed.
I agree, I don't know how but this should be reported, to someone who can fix it.
kezzerdrix
Apr 28th 2008, 08:20 PM
found a solution, revert back to 7.10
stoer
Apr 30th 2008, 08:32 AM
Been searching and searching,
finally found this on the Ubuntu forums.
http://ubuntuforums.org/showthread.php?p=4300658#post4300658
My laptop now lets me logout, shut down, hibernate & wake up - when i want it to!
Hope this helps some of you people out as well.
Gumper
May 13th 2008, 03:28 AM
For me it appears that my problem is coming from having "Keytouch" running on my system. If anyone else here is having shutdown problems and has "Keytouch" installed, try killing the process "keytouchd", and then shutting down. This works for me.
I created a script to do this but I don't know how to have this run automatically before shutting down. Could anyone help me out here?
For more info on this problem see the link below:
https://bugs.launchpad.net/ubuntu/+source/keytouch/+bug/186713
Gumper
May 13th 2008, 03:52 AM
I figured out how to run my script before shutdown. I created the folder "~/.kde/shutdown" and placed my script there. Now everything works as it's supposed to. Hope this helps someone. This was driving me nuts not being able to shutdown correctly.
Snowhog
May 13th 2008, 03:57 AM
Haven't tried it yet, although I did change the setting this evening:
K Menu > System Settings > Advanced > Session Manger > Default Shutdown Option > Turn off computer (the default setting is End current session)
I'll know if this works (and actually powers off my laptop) when I logout later.
ElZorro
May 13th 2008, 04:50 AM
In my previous post I described the same problem with my desktop AMD 64 3000+ Gigabit triton chipset nforce 4.
Where are the Developers? Please help with this one folks!
This did not happen with the Heron alpha or the betas, and it was the same KDE version I believe.
Thus I do not believe it is a KDE problem but something done by the developers in the config files or python coding.
This has only happened in the LTS final release.
Hope a fix and some LTS is in the works very soon.
Sure glad I am not the only one in the universe with this glitch, as one should not have to do a terminal shutdownn -h now every time.
Even logout user is afflicted with the "blank screen bug" too a real pain.
Regards
El Zorro 8)
ElZorro
May 13th 2008, 12:14 PM
Hi
Its the accelerated ATI driver that causes these problems that asks to be installed at login.
So refuse this invitation until it is fixed.
Cheers
El Zorro
Snowhog
May 14th 2008, 03:09 AM
After I made the change, and logged out last night, there was no difference. I still got the "system halted" final message, at which point I pressed the power button. That said, maybe it will be different tonight. Maybe I had to 'reboot' before that change would take effect. I don't have 'high expectations' in this reguard, but 'doing' will tell.
stego_s_aurus
May 26th 2008, 10:36 PM
I Found the Real problem!
It definitely has to do with ATI drivers: I posted about it on the ubuntuforums, here:
http://ubuntuforums.org/showthread.php?t=808543
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.