Fedora This forum is for the discussion of the Fedora Project. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
01-24-2007, 01:15 PM
|
#1
|
Member
Registered: Jan 2006
Distribution: Debian Testing
Posts: 675
Rep:
|
FC6 - Shutdown Question
I'm having a problem on my mythbox which is running FC6. When I shutdown the computer the screen goes black and I see the mouse cursor. It doesn't go into the shutdown process at all. This is using the shutdown command from the command prompt. When I click the shutdown button in KDE nothing the same thing happens. However when I use reboot, it reboots correctly. Another note, originally on shutdown it did finish until it got to the end and you saw acpi_poweroff. Which I'm assuming is the command to turn off the computer but it isn't working. Any help would be appreciated thank you.
Nomb
|
|
|
01-24-2007, 05:21 PM
|
#2
|
LQ Guru
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
|
Your machine may not be apci compliant. Give this a try. On boot when it gets to the kernel choices hit the e key and add the option ' noapci ' to the end of the kernel line. Hit b to boot. Shutdown and see if that works.
Brian
|
|
|
01-25-2007, 05:29 AM
|
#3
|
Member
Registered: May 2006
Distribution: Ubuntu10.04, < fedora12
Posts: 347
Rep:
|
So did that work????
I've got exactly the same problem, but it doesn't happen every time, probably about 80% fail 20% OK. I'm fairly sure this machine is apci compliant, but I'll give that trick a try and see what happens.
This machine also goes into hibernate OK which is effectivelly the same as shutdown + saving current state.
Also responds perfectly well to "halt" from a root terminal.
|
|
|
01-25-2007, 06:52 AM
|
#4
|
Member
Registered: Jun 2004
Location: Tragic City,Michigan,USA
Distribution: Fedora 23 Fedora 22
Posts: 244
Rep:
|
I had the same problem a while back along with others who were having "shutdown" problems. This is the solution that works for me and others who had same problem.
Quote:
Originally Posted by Jack Malmostoso
Hi guys,
I have been having this same problem on my old PIII 550 on a BX440 motherboard with a 1999 BIOS.
That said, the kernel argument that does the trick is "acpi=force". You have to edit /boot/grub/menu.lst so that your "kernel" lines read something like this:
|
Code:
kernel /boot/vmlinuz-2.6.XX-XXXX acpi=force ro root=LABEL=/ rhgb quiet
Quote:
If you put the argument at the end of the file, it won't do anything, cause it won't be parsed correctly.
I have tested this solution and it works just perfectly.
|
Hopefully this should get your machine to stop completely.
Last edited by Ryptyde; 01-25-2007 at 06:54 AM.
|
|
|
01-25-2007, 07:28 AM
|
#5
|
Member
Registered: May 2006
Distribution: Ubuntu10.04, < fedora12
Posts: 347
Rep:
|
Quote:
Originally Posted by Ryptyde
I had the same problem a while back along with others who were having "shutdown" problems. This is the solution that works for me and others who had same problem.
Code:
kernel /boot/vmlinuz-2.6.XX-XXXX acpi=force ro root=LABEL=/ rhgb quiet
Hopefully this should get your machine to stop completely.
|
Thanks Ryptyde, I was wondering why acpi was still starting up, was going to try and move the comand to where you have it.
Strange thing is, although acpi has still been starting it's been shutting down OK.
I hate intermitent problems!!! You don't know when they are fixed.
I'll try your suggestion for a while and see what happens, I'll try and remember to get back here with results.
|
|
|
01-25-2007, 08:56 AM
|
#6
|
Member
Registered: Jan 2006
Distribution: Debian Testing
Posts: 675
Original Poster
Rep:
|
Thank you to all who replyed. I will be home (finally) later tonight and will try all the solutions posted here.  I would ssh in and make the modifications but my work blocks my dyndns host  and I haven't found a bounce around yet...
nomb
|
|
|
01-25-2007, 09:32 AM
|
#7
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187
|
FYI, the most recent update to kdm seems to have broken the logoff/shutdown functionality. You would only see the problem if your /etc/sysconfig/desktop file has the DISPLAYMANAGER set to KDE. Mine looks like this now:
Code:
$ cat /etc/sysconfig/desktop
DESKTOP=KDE
DISPLAYMANAGER=GNOME
#DISPLAYMANAGER=KDE
#DISPLAYMANAGER=XDM
which fixed my shutdown problem. ( GNOME is the default setting, so -- if you've never changed it -- this is not likely to be your problem.)
<edit>
I prefer the kdm because it gives you much better control over the login screen and, for example, lets you change the background for the KDE start-up. It also used to be required for the "switch user" functionality to be available, but that's no longer the case.
</edit>
Last edited by PTrenholme; 01-25-2007 at 09:38 AM.
|
|
|
01-25-2007, 10:29 AM
|
#8
|
Member
Registered: Jan 2006
Distribution: Debian Testing
Posts: 675
Original Poster
Rep:
|
Ok so your saying, since I'm using KDE (which is my first time) then that file has gdm by default. But it should be kdm. Is that right?
No wait ur saying since I'm using kde my display manager is kde so i need to go change the display manager setting to be gnome.
Is that correct?
Last edited by nomb; 01-25-2007 at 10:31 AM.
|
|
|
01-25-2007, 11:09 AM
|
#9
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187
|
Quote:
Originally Posted by nomb
Ok so your saying, since I'm using KDE (which is my first time) then that file has gdm by default. But it should be kdm. Is that right?
No wait ur saying since I'm using kde my display manager is kde so i need to go change the display manager setting to be gnome.
Is that correct?
|
No, the dm setting is, essentially, independent of the windowing environment.
The "display manager" is the layer between the screen and the windowing environment. In Fedora you have three choices, gdm, kdm, and xdm, unless you've added (via yum or some other, deliberate, method) another choice. All three of the default display managers will support either GNOME or KDE as your windowing envronment.
On Fedora the default choice is gdm since the default environment is GNOME, but that choice works for either GNOME and KDE (and several other desktop environments) so most users will never change it. And, really, you shouldn't change it unless you have a need to do so.
To see what you have set, do a cat /etc/sysconfig/desktop. I suspect that you've never changed that file, and that it will contain the default settings:
Code:
$ cat /etc/sysconfig/desktop
DESKTOP=GNOME
DISPLAYMANAGER=GNOME
If this is the case, you should probably leave it alone. Only if your dm setting is KDE would the problem I described be relevant. If it is KDE, try setting it to GNOME. The DESKTOP setting is, perty much, irrelevant since you can over-ride it from the login menu.
|
|
|
01-26-2007, 01:50 AM
|
#10
|
Member
Registered: May 2006
Distribution: Ubuntu10.04, < fedora12
Posts: 347
Rep:
|
So, this is weird, I have FC4 & FC6 on this machine, core 4 has no shutdown problems, /etc/sysconfig/desktop has
DESKTOP=GNOME
no mention of displaymanager.
FC6 wich has intermitent shutdown problems, /etc/sysconfig/desktop is blank!!!!
But I think the display manager is gdm, gnome is certainly the default desktop.
I've probably down too many things at once here, last night added the acpi=force to grub.conf and have just added DESKTOP=GNOME and DISPLAY=GNOME to the blank desktop file.
|
|
|
01-26-2007, 04:08 AM
|
#11
|
Member
Registered: May 2006
Distribution: Ubuntu10.04, < fedora12
Posts: 347
Rep:
|
Sorry guys, neither of them worked, it's just failed to shut down again. And it was going so well, must have shutdown at least 5 times without a hickup.
Was that meant to be noacpi=force, instead of acpi=force?
Are we trying to stop acpi or force it to happen??
Can't see how this is possible but there seems to be a correlation with me using wine, I'll do some more experimenting.
|
|
|
01-26-2007, 06:40 AM
|
#12
|
Member
Registered: Jun 2004
Location: Tragic City,Michigan,USA
Distribution: Fedora 23 Fedora 22
Posts: 244
Rep:
|
decrepit you can check this link where I found my solution maybe there is something there that will suggest more options.
Shutdown_Problem
.
|
|
|
01-26-2007, 08:49 AM
|
#13
|
Member
Registered: Jan 2006
Distribution: Debian Testing
Posts: 675
Original Poster
Rep:
|
They did have some good ideas in that thread aswell. To answer you question it would be acpi=force. But there are a few other options in the above thread.
|
|
|
01-26-2007, 10:07 AM
|
#14
|
Member
Registered: Mar 2003
Location: UK Darlington
Distribution: Fedora Freebsd Centos
Posts: 296
Rep:
|
What happens when you type poweroff or init 0 at the command prompt as root?
|
|
|
01-26-2007, 10:29 AM
|
#15
|
Member
Registered: Jan 2006
Distribution: Debian Testing
Posts: 675
Original Poster
Rep:
|
same exact thing happens.
nomb
|
|
|
All times are GMT -5. The time now is 05:25 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|