I have a strange problem with my newly built computer (CPU: 4th generation i5, dual boot Windows 8.1 and openSUSE 13.1 on SSD, home and data on a HDD, 8 GB of RAM, GRUB2-EFI, Intel DH87RL mainboard), which apart of this problem works impressively well so far. Installation was very easy.
When I try to shutdown openSUSE, it takes a while (much longer than it does when it reboots) until everything is turned off. But maybe 2 seconds later the systems turns on again and boots. The Windows shutdown works without resurrections. I apologize if this is the wrong category, but I don’t know where else it would fit better.
What I tried so far:
1.) to install acpid and start it
2.) in /etc/sysconfig/shutdown I substituted HALT=“auto” with HALT=“halt”
3.) in the boot options there is no “acpi=off” option which could be removed
At this point I don’t know what I could try anymore, and don’t want to risk the system by doing something stupid. I don’t know if it matters, but I followed this instructions https://sites.google.com/site/easylinuxtipsproject/ssd-in-opensuse
to optimize for using a SSD. One step was to remove pm-utils, but I assume that just involves hibernation?
Help is appreciated. It isn’t urgent or critical but I guess after a while it starts to bother…
The system rebooted again after 1 or 2 seconds. But then I shut it down with Windows and unlike usually I didn’t cut the energy supply. Later I noticed the LED at the LAN cable was very active. In the UEFI settings I found some kind of LAN-wake-up thing was enabled (in the “Power” tab… before I just removed it from boot order). Disabling it solved the issue. I don’t understand why it rebooted from openSUSE, but not Windows, but well, now it works, so that matters.
If Windows was pre installed it probably also had pre installed mother board drivers. This often is done and may fix the re start problem for Windows. If you installed pure generic Windows it might very well have the same problem
No, it wasn’t pre installed. I bought everything separately, the SSD and mainboard were unused, Windows generic. I still think it’s a strange default setting for a PC, but anyhow.
Somewhat yes, I downloaded and installed several things from Intel. Something to update UEFI and a manger that took care of drivers. Prior to that I didn’t shut down Windows, so I don’t know if it had had that problem too.
> The system rebooted again after 1 or 2 seconds. But then I shut it down
> with Windows and unlike usually I didn’t cut the energy supply. Later I
> noticed the LED at the LAN cable was very active. In the UEFI settings I
> found some kind of LAN-wake-up thing was enabled (in the “Power” tab…
> before I just removed it from boot order). Disabling it solved the
> issue. I don’t understand why it rebooted from openSUSE, but not
> Windows, but well, now it works, so that matters.
Probably because Windows is aware of that feature, and Linux is not.
When Windows powers off it disables wake-on-lan, unless you tell it that
you want to really wake on lan.
Just a guess.
Maybe it can also be disabled in the BIOS config :-?
Or Windows is aware of UEFI config and can interact with it.
My notebook HP ProBook 4740s had the similar behaviour when I used Kubuntu (13.10 or 14.04).
When I turned off notebook, suddenly it turned on after 2 seconds itself. It was also strange, that this did not appear always, but accidentally.
I did not have any wire LAN cable pluged in, any external mouse, only supply adaptor was pluged in.
When I transfered to Fedora and then openSUSE, this behaviour disappeared. Maybe it was some anti-ubuntu ghost:).
According above mention I suggest you to try other distributions for comparison. Because my problem was only under Kubuntu.
On 2014-08-03 09:36, galko ferdinand wrote:
>
> My notebook HP ProBook 4740s had the similar behaviour when I used
> Kubuntu (13.10 or 14.04).
> When I turned off notebook, suddenly it turned on after 2 seconds
> itself. It was also strange, that this did not appear always, but
> accidentally.
There could be interference with a feature some bios have, that when
power is restored after a poweroff, they stay off, or they switch on
automatically… say, for servers to recover after a power failure
automatically.
If there is a bug in bios, or in power off sequence, it might trigger…
I agree with you. Just a wild guess.
Because notebook works perfect under Fedora or openSUSE without this problem.
It was just a Kubuntu problem. And it seem that it was in this time, because I tried Kubuntu for a few last days without this problem.
It isn’t urgent or critical but I guess after a while it starts to bother…