Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
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.
I have just put this machine together, completely new build. Currently running LMDE.
When I select "shutdown" from the desktop menu the machine seems to be shutting down... exits the DE, closes all programs, filesystems, etc. I can hear the fans turn off... then suddenly it reboots.
I tried running "shutdown -h now" from the command line and the same thing happens, so it doesn't seem like a confusion in the command. Reboot works as it should.
If I remove the side cover and watch, I can see everything turning off... the power supply fans slows almost to a stop, then when it is almost completely stopped the system boots up again!
Any ideas? I can't even tell if this is a hardware or software problem.
Running the latest LinuxMintDebian updates. Intel DZ77GA70K motherboard.
I have not yet tried updating the bios: could that be controlling this?
Here's the output from lspci:
keith@ada:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4)
00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
32:00.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
33:01.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
33:04.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
33:05.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
33:07.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
33:09.0 PCI bridge: PLX Technology, Inc. PEX 8606 6 Lane, 6 Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba)
35:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
36:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4)
38:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 30)
3a:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
I would suggest testing with a Live CD, or possibly even a couple of different ones to be thorough. If it can shutdown or reboot as commanded under a Live CD, then it is likely a problem with the software load.
Thanks, I hadn't thought of testing it with other discs, because it happens when I use the disc I loaded from. I had just assumed since everything else went fine with this install that the disc could not be the problem...
But now I find you are right on- when I boot from other Live discs the shutdown works as it should. If I boot from this LMDE disc shutdown doesn't work.
Sigh. I just spent two days configuring this box. I hate to start over from scratch with a new disc. Any ideas of other fixes? Maybe updating the kernel?
I have since tried this on another machine, and this does not happen.
I.E., when I boot from this particular LiveDVD (new LMDE) in my new machine selecting shutdown does not shutdown, but restarts.
Using this disk in a different machine shutdown works as it should.
Using other LiveDVD's in this new machine shutdown works as it should.
So, evidently there is some interaction between this LiveDVD and this new machine which is causing the problem. I have updated all software including the kernel and the BIOS.
The other thing I found last night is that the mobo has a loose connector- the USB3.0 front panel connector on the mobo. This would seem to be related to an error message I always get on bootup- xhci_hcd: Failed to enable MSI-X. Evidently xhci is related to USB3.0. So maybe there's a problem with the mobo. Unfortunately this is the only machine I have access to which supports USB3.0.
I've called Intel and have begun the process of returning the mobo. We'll see how that goes...
Try blacklisting the 'e1000e' driver. I've had similar problems with this driver and I suspect that your ethernet card is using it. Check 'lspci -k' to be sure.
Hey TexMex- Yes, the ethernet uses the e1000e driver. I had at one point turned off the ethernet in the BIOS with no change- would that be the same as blacklisting the driver?
If not, could you tell me how to blacklist it? I have tried blacklisitng things before in the past without success- it's a little more complicated than it looks at first glance.
In theory turning it off in the BIOS should be enough, but you can also try blacklisting it by adding a line like:
Code:
blacklist e1000e
to '/lib/modprobe.d/e1000e.conf' OR if there is no '/lib/modprobe.d' then to '/etc/modprobe.d/e1000e.conf' OR if there is no '/etc/modprobe.d' then to '/etc/modprobe.conf'. You may need to create the file 'e1000e.conf', the name doesn't matter, but it must end in '.conf'.
Thanks to Frank and TexMex I have found a solution.
After blacklisting the e1000e driver _and_ turning off the LAN in the BIOS the machine will now shutdown properly. BOTH actions must be done- either one by itself would not work.
More details- I have found that if I hold the front panel power button in for 5+ seconds the machine would shutdown, as you would expect.
I also found that the command:
Code:
init 0
would shut the machine down. But selecting shutdown from a menu or invoking "shutdown -h now" would cause the machine to almost shutdown then restart.
So, looks like an interaction between this particular LiveDVD (LinuxMint Debian Maya) and this machine. Since I don't need the LAN for this particular machine, turning the LAN off and blacklisting the e1000e driver is OK by me, AFAIK, at this time.
I had a similar problem and evidentially found the Bios setting BOOT ON LAN was the problem (it was set to on)this was read by Linux as do not completely shut down as it may need to wake.
Trev
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.