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.

keithostertag

12-26-2012 09:16 PM

Hi Frank-

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?

Keith

keithostertag

12-27-2012 09:17 AM

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...

H_TeXMeX_H

12-27-2012 11:34 AM

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.

keithostertag

12-27-2012 02:12 PM

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.

thanks,
Keith

H_TeXMeX_H

12-28-2012 03:38 AM

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'.

keithostertag

12-31-2012 08:55 AM

Solved

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.

Keith Ostertag

trevoratxtal

12-31-2012 10:57 AM

Please check your Bios.

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