Recently installed F-18 system doesn't shut down properly. The symptoms are:
* I click Shut Down, using KDE * System appears to stop normally: fan stops, screen goes blank, etc. EXCEPT that the light around the power switch doesn't go completely dark; it continues to glow faintly blue. I don't know what this means; no documentation. * The system won't restart till it is reset. This can be done either by pressing Reset on the computer or by powering the system down and then powering it up. * When the system is restarted, a message from systemd-fsck appears to indicate that the disk drives were not closed cleanly. /var/log/boot.log is attached.
Apart from this, the system runs fine.
Motherboard is ASUS M3A78-EM with a 4-core CPU.
On Wed, 06 Mar 2013 09:15:36 -0800 Jonathan Ryshpan wrote:
* I click Shut Down, using KDE
I've never been able to figure out what the heck the different GUI versions of shutdown actually do, they often seem broken for some reason. Try typing this in a terminal instead:
sudo shutdown -h now
If that doesn't shutdown, then there is a real shutdown problem, otherwise there is a KDE problem.
On 03/06/2013 09:35 AM, Tom Horsley issued this missive:
On Wed, 06 Mar 2013 09:15:36 -0800 Jonathan Ryshpan wrote:
* I click Shut Down, using KDEI've never been able to figure out what the heck the different GUI versions of shutdown actually do, they often seem broken for some reason. Try typing this in a terminal instead:
sudo shutdown -h now
If that doesn't shutdown, then there is a real shutdown problem, otherwise there is a KDE problem.
The shutdown app in the various desktops should perform clean logouts from the desktop first (e.g. save current layout, save current session, etc.), then actually run the shutdown command. The one I have in XFCE does the job fairly well.
On one machine, I do occasionally have issues with the window manager not starting properly on a reboot but I suspect that's another issue. That machine has been upgraded from F14 through F17 and there's still cruft left over from those older OS versions. Methinks it sometimes gets confused...much like its owner. :-) ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - When you don't know what to do, walk fast and look worried. - ----------------------------------------------------------------------
On Wed, Mar 6, 2013 at 9:44 AM, Rick Stevens ricks@alldigital.com wrote:
On 03/06/2013 09:35 AM, Tom Horsley issued this missive:
On Wed, 06 Mar 2013 09:15:36 -0800
Jonathan Ryshpan wrote:
* I click Shut Down, using KDEI've never been able to figure out what the heck the different GUI versions of shutdown actually do, they often seem broken for some reason. Try typing this in a terminal instead:
sudo shutdown -h now
If that doesn't shutdown, then there is a real shutdown problem, otherwise there is a KDE problem.
The shutdown app in the various desktops should perform clean logouts from the desktop first (e.g. save current layout, save current session, etc.), then actually run the shutdown command. The one I have in XFCE does the job fairly well.
On one machine, I do occasionally have issues with the window manager not starting properly on a reboot but I suspect that's another issue. That machine has been upgraded from F14 through F17 and there's still cruft left over from those older OS versions. Methinks it sometimes gets confused...much like its owner. :-) ------------------------------**------------------------------**----------
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
-- When you don't know what to do, walk fast and look worried. -
------------------------------**------------------------------**----------
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
With f18, my system sometimes gets hung on a dracut command prompt; I didn't know what to do at first, but now I just type "poweroff" or "reboot" and the system is fine.
Hope this helps
On Wed, 2013-03-06 at 09:54 -0800, Richard Vickery wrote:
With f18, my system sometimes gets hung on a dracut command prompt; I didn't know what to do at first, but now I just type "poweroff" or "reboot" and the system is fine.
Thanks for the info, but I'm not sure it's relevant, since after the apparently successful logout attempt, there is no shell prompt to enter "poweroff", etc. into.
jon
On Wed, 2013-03-06 at 09:44 -0800, Rick Stevens wrote:
On 03/06/2013 09:35 AM, Tom Horsley issued this missive:
On Wed, 06 Mar 2013 09:15:36 -0800 Jonathan Ryshpan wrote:
* I click Shut Down, using KDEI've never been able to figure out what the heck the different GUI versions of shutdown actually do, they often seem broken for some reason. Try typing this in a terminal instead:
sudo shutdown -h now
If that doesn't shutdown, then there is a real shutdown problem, otherwise there is a KDE problem.
The shutdown app in the various desktops should perform clean logouts from the desktop first (e.g. save current layout, save current session, etc.), then actually run the shutdown command. The one I have in XFCE does the job fairly well.
I attempted to take both Rick Stevens' and Tom Horsley's advice as follows:
1. Log off my KDE session using the GUI. 2. Open a console window using CTRL/ALT/F2 3. Log in as root 4. Enter shutdown -h now
Result, exactly the same as before. System appears to halt properly except for faint light around the start button, but can't be rebooted without being reset, messages from systemd-fsck in boot.log.
Thanks - jon
On 03/06/2013 12:56 PM, Jonathan Ryshpan issued this missive:
On Wed, 2013-03-06 at 09:44 -0800, Rick Stevens wrote:
On 03/06/2013 09:35 AM, Tom Horsley issued this missive:
On Wed, 06 Mar 2013 09:15:36 -0800 Jonathan Ryshpan wrote:
* I click Shut Down, using KDEI've never been able to figure out what the heck the different GUI versions of shutdown actually do, they often seem broken for some reason. Try typing this in a terminal instead:
sudo shutdown -h now
If that doesn't shutdown, then there is a real shutdown problem, otherwise there is a KDE problem.
The shutdown app in the various desktops should perform clean logouts from the desktop first (e.g. save current layout, save current session, etc.), then actually run the shutdown command. The one I have in XFCE does the job fairly well.
I attempted to take both Rick Stevens' and Tom Horsley's advice as follows:
1. Log off my KDE session using the GUI. 2. Open a console window using CTRL/ALT/F2 3. Log in as root 4. Enter shutdown -h nowResult, exactly the same as before. System appears to halt properly except for faint light around the start button, but can't be rebooted without being reset, messages from systemd-fsck in boot.log.
I'm wondering if perhaps that's something from the BIOS causing that... like "wake on LAN" or something. You might want to reboot the machine and verify that the BIOS permits going to a full powerdown state as opposed to some hibernation state. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Veni, Vidi, VISA: I came, I saw, I did a little shopping. - ----------------------------------------------------------------------
On Wed, 2013-03-06 at 17:52 -0800, Rick Stevens wrote:
I attempted to take both Rick Stevens' and Tom Horsley's advice as follows:
1. Log off my KDE session using the GUI. 2. Open a console window using CTRL/ALT/F2 3. Log in as root 4. Enter shutdown -h nowResult, exactly the same as before. System appears to halt properly except for faint light around the start button, but can't be rebooted without being reset, messages from systemd-fsck in boot.log.
I'm wondering if perhaps that's something from the BIOS causing that... like "wake on LAN" or something. You might want to reboot the machine and verify that the BIOS permits going to a full powerdown state as opposed to some hibernation state.
A good thought. But I had no trouble with powering down till I installed Fedora-18. Sleep works fine now, as it always did.
One change in BIOS settings: I disabled "Quick Boot", since I was having trouble getting into the BIOS by pressing DEL during BIOS hardware test A new keyboard, which plugs into a USB port was not being recognized by the BIOS at test time; disabling "Quick Boot" slows down the boot process and allows me to get into the BIOS reliably. I'll try re-enabling "Quick Boot" tomorrow to see if it makes any difference.
jon
-
Jonathan Ryshpan -
Richard Vickery -
Rick Stevens -
Tom Horsley