Yet another shutdown problem

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
tonyb2
Level 1
Level 1
Posts: 3
Joined: Wed Jan 23, 2013 7:04 am

Yet another shutdown problem

Post by tonyb2 » Wed Aug 27, 2014 6:02 am

I've tried all the suggestions from /viewtopic.php?f=90&t=175203 (now marked solved), also a host of other options suggested elsewhere (noefi, shutdown netman, change video driver, turn off wifi,...) and still have the problem. Shutdown gets as far '[x.y] reboot : Power down'. I have to use the laptop power button to switch off. Something not mentioned elsewhere - my other OSes (Mint 15 and Win8.1) no longer (since Mint 17 install) shut down either, the only difference being that Windows doesn't leave the HDD light glowing. A question - does GRUB get involved in the shutdown process? I'm using grub-efi, which I don't think I was using in Mint 15. Any suggestions would be welcome.

User avatar
Kalyk
Level 5
Level 5
Posts: 771
Joined: Wed Mar 12, 2014 5:29 pm
Location: The Netherlands

Re: Yet another shutdown problem

Post by Kalyk » Thu Sep 04, 2014 9:38 am

Hello and welcome to this forum!!!

As far as I can tell it is not possible that a new Linux-installation also prevents an older installation and Win8.1 to shutdown.
So I would first look in the BIOS if you disabled something that was previously enabled.
Or put it back to factory defaults and try again.
You might also try to update the firmware.

If there is a reason for the problem occuring that Linux can see while shutting down then you might look in the logfiles under /var/log, perhaps it gives a clue.

If this all gives no solution then doing a disk check (perhaps best from Windows since it is on the disk too) might resolve something, worth a try I think.
Add (Solved) to the topic-title of the first post when appropriate so others know they might find a solution here.

tonyb2
Level 1
Level 1
Posts: 3
Joined: Wed Jan 23, 2013 7:04 am

Re: Yet another shutdown problem

Post by tonyb2 » Sat Sep 06, 2014 5:12 am

Actually the problem appears to be in GRUB2, or the GRUB2/UEFI interface. I have found that I can re-create it quite easily; just a short press on the power button when the GRUB2 menu is on the screen puts it into some sort of loop. The disc light comes hard on, the keyboard is unresponsive and the 10 second countdown freezes. I'm looking now for ways to debug or update GRUB2!

User avatar
Kalyk
Level 5
Level 5
Posts: 771
Joined: Wed Mar 12, 2014 5:29 pm
Location: The Netherlands

Re: Yet another shutdown problem

Post by Kalyk » Wed Sep 10, 2014 3:12 am

Sorry I can't help you there as I have no experience with UEFI.
Hope someone else can shed some light on this problem.
Add (Solved) to the topic-title of the first post when appropriate so others know they might find a solution here.

HarzVieh
Level 4
Level 4
Posts: 264
Joined: Sat Nov 20, 2010 8:01 am
Location: Germany

Re: Yet another shutdown problem

Post by HarzVieh » Wed Sep 10, 2014 4:05 am

Hope someone else can shed some light on this problem.
https://en.wikipedia.org/wiki/Advanced_ ... _Interface
You can try disable ACPI in Bios.. but then, when we can't reproduce something, how can we help?
Here is Quote from Upgrading and Repairing PC's:
As power-management techniques continued to develop, maintaining the complex information states
necessary to implement more advanced functions became increasingly difficult for the BIOS.
Therefore, another standard was developed by Intel, Microsoft, and Toshiba. Called Advanced
Configuration and Power Interface (ACPI), this standard was designed to implement power-management
functions in the OS. Microsoft Windows 98 and later automatically use ACPI if ACPI functions are
found in the system BIOS. The need to update system BIOSs for ACPI support is one reason many
computer vendors have recommended performing a BIOS update before installing Windows 98 or
later on older systems.
ACPI was initially released in 1996 and first appeared in the Phoenix BIOS around that time. ACPI
became a requirement for the Intel/Microsoft “PC’97” logo certification in 1996, which caused devel-
opers to work on integrating ACPI into system designs around that time. Intel included ACPI support
in chipsets starting with the PIIX4E South Bridge in April 1998, and ACPI support was included in
Windows starting with the release of Windows 98 (June 25, 1998) as part of what Microsoft called its
“OnNow” initiative. By the time Windows 2000 came out (February 17, 2000), ACPI had universally
replaced APM on new systems. ACPI 4.0a was released in April 2010, and the ACPI 5.0 Specification is
currently under development. The official ACPI specifications can be downloaded from http://www.acpi.info.
Placing power management under the control of the OS enables a greater interaction with applica-
tions. For example, a program can indicate to the OS which of its activities are crucial, forcing an
immediate activation of the hard drive, and which can be delayed until the next time the drive is
activated for some other reason. For example, a word processor may be set to automatically save files
in the background, which an OS using ACPI can then delay until the drive is activated for some other
reason, resulting in fewer random spin-ups of the drive.
ACPI goes far beyond the previous standard, APM, which consisted mainly of processor, hard disk, and
display control. ACPI controls not only power but also all the Plug and Play (PnP) hardware configura-
tion throughout the system. With ACPI, system configuration (PnP) and power-management configu-
ration are no longer controlled via the BIOS Setup; they are instead controlled entirely within the OS.
ACPI enables the system to automatically turn internal peripherals on and off (such as CD-ROM
drives, network cards, hard disk drives, and modems) as well as external devices such as printers,
monitors, or any devices connected to serial, parallel, USB, video, or other ports in the system. ACPI
technology also enables peripherals to turn on or wake up the system. For example, a telephone
answering machine application can request that it be able to respond to answer the telephone within
1 second. Not only is this possible, but if the user subsequently presses the power or sleep button, the
system only goes into the deepest sleep state that is consistent with the ability to meet the telephone
answering application’s request.
ACPI enables system designers to implement a range of power-management features that are compati-
ble with various hardware designs while using the same OS driver. ACPI also uses the Plug and Play
BIOS data structures and takes control over the Plug and Play interface, providing an OS–independent
interface for configuration and control.
ACPI defines several system states and substates. There are four Global System states, labeled from G0
through G3, with G0 being the fully operational state and G3 being mechanically turned off. Global
System states are immediately obvious to the user of the system and apply to the entire system as a
whole. Within the G0 state, there are four CPU Power states (C0–C3) and four Device Power states
(D0–D3) for each device. Within the C0 CPU Power state, there are up to 16 CPU Performance states
(P0–P15).
Device Power states are states for individual devices when the system is in the G0 (Working) state. The
device states may or may not be visible to the user. For example, it may be obvious when a hard disk
has stopped or when the monitor is off; however, it may not be obvious that a modem or other
device has been shut down. The Device Power states are somewhat generic; many devices do not have
all four Power states defined.
Within the G1 Global Sleep state are four Sleep states (S1–S4). The G2 Global Soft Off state is also
known as the S5 Sleep state, in which case the system is powered off but still has standby power.
Finally, G3 is the Mechanical Off state, where all power is disconnected from the system.
The following list shows the definitions and nested relationship of the various Global, CPU/Device
Power, and Sleep states:
■ G0 Working—This is the normal working state in which the system is running and fully oper-
ational. Within this state, the Processor and Device Power states apply. The Device Power states
are defined as follows:
■ G0/D0 Fully-On—The device is fully active.
■ G0/D1—Depends on the device; uses less power than D0.
■ G0/D2—Depends on the device; uses less power than D1.
■ G0/D3 Off—The device is powered off (except for wakeup logic).
■ The Processor Power states are defined as follows:
■ G0/C0 CPU On—Normal processor operation.
■ G0/C1 CPU Halted—The processor is halted.
■ G0/C2 CPU Stopped—The clock has been stopped.
■ G0/C3 CPU/Cache Stopped—The clock has been stopped and cache snoops are ignored.
G1 Sleeping—The system appears to be off but is actually in one of four Sleep states—up to
full hibernation. How quickly the system can return to G0 depends on which of the Sleep states
the system has selected. In any of these Sleep states, system context and status are saved such
that they can be fully restored. The Sleep states available in the Global G1 state are defined as
follows:
■ G1/S1 Halt—A low-latency idle state. The CPU is halted; however, system context and sta-
tus are fully retained.
■ G1/S2 Halt-Reset—Similar to the S1 sleeping state except that the CPU and cache con-
text is lost, and the CPU is reset upon wakeup.
■ G1/S3 Suspend to RAM—All system context is lost except memory. The hardware main-
tains memory context. The CPU is reset and restores some CPU and L2 context upon
wakeup.
■ G1/S4 Suspend to Disk (Hibernation)—The system context and status (RAM contents)
have been saved to nonvolatile storage—usually the hard disk. This is also known as
Hibernation. To return to G0 (Working) state, you must press the power button, and the sys-
tem will restart, loading the saved context and status from where they were previously
saved (normally the hard disk). Returning from G2/S5 to G0 requires a considerable
amount of latency (time).
■ G2/S5 Soft Off—This is the normal power-off state that occurs after you select Shutdown or
press the power button to turn the system off. The system and all devices are essentially pow-
ered off; however, the system is still plugged in and standby power is coming from the power
supply to the motherboard, allowing the system to wake up (power on) if commanded by an
external device. No hardware context or status is saved. The system must be fully rebooted to
return to the G0 (working) state.
■ G3 Mechanical Off—Power is completely removed from the system. In most cases this means
the system must be unplugged or the power turned off via a power strip. This is the only state
in which it is safe to disassemble the system. Except for the CMOS/clock circuitry, power con-
sumption is completely zero.
In normal use, a system alternates between the G0 (Working) and G1 (Sleeping) states. In the G1
(Working) state, individual devices and processors can be power-managed via the Device Power
(D1–D3) and Processor Power (C1–C3) states. Any device that is selectively turned off can be quickly
powered on in a short amount of time, from virtually instantaneous to only a few seconds (such as a
hard disk spinning up).
When the system is idle (no keyboard or mouse input) for a preset period, the system enters the
Global G1 (Sleeping) state, which means also selecting one of the S1–S4 sleep states. In these states,
the system appears to be off, but all system context and status are saved, enabling the system to
return to exactly where it left off, with varying amounts of latency. For example, returning to the G0
(Working) state from the G1/S4 (Hibernation) state requires more time than when returning from the
G1/S3 (Suspend) state.
When the user presses the power button to turn the system off or selects Shutdown via the OS, the
system enters the G2/S5 (Soft Off) state. In this state, no context is saved, and the system is com-
pletely off except for standby power. Fully disconnecting AC or battery power causes the system to be
in the Global G3 (Mechanical Off) state, which is the only state in which the system should be disas-
sembled.
During the system setup and boot process, ACPI performs a series of checks and tests to see whether
the system hardware and BIOS support ACPI. If support is not detected or is found to be faulty, the
system typically reverts to standard Advanced Power Management control, which is referred to as
legacy power management under ACPI. Virtually all ACPI problems are the result of partial or incom-
plete ACPI implementations or incompatibilities in either the BIOS or device drivers. If you encounter
any of these errors, contact your motherboard manufacturer for an updated BIOS or the device manu-
facturers for updated drivers.

tonyb2
Level 1
Level 1
Posts: 3
Joined: Wed Jan 23, 2013 7:04 am

Re: Yet another shutdown problem

Post by tonyb2 » Thu Sep 11, 2014 6:34 am

Thanks for that. ACPI was always a bit of a mystery to me; I'll look into it further when I have time. It's not really a great problem to me, just a bit of a nuisance. I don't see any signs that shutting down with the power button is causing any other problems.

kunkeler
Level 1
Level 1
Posts: 1
Joined: Sat Oct 04, 2014 11:26 am

Re: Yet another shutdown problem

Post by kunkeler » Sat Oct 04, 2014 11:32 am

I had the same problem with Mint 17 Cinnamon on:
Intel NUC Kit D54250WYK
processor 4250U i5
Intel HD Graphics 5000
this worked for me:
update the BIOS and put ACPI off
Mint 17 shutsdow normally without the reboots.

Greetings, Eric.

Post Reply

Return to “Installation & Boot”