You are not logged in.
Installed Arch on this intel nuc system, its actually a custom build by a company called Centrium (feacking banana country). But apparently is based on the intel kit: https://downloadcenter.intel.com/produc … DN2820FYKH
Couldn't find much info on the issue, barely any, except for one other user: http://askubuntu.com/questions/623711/c … -intel-nuc
I recently reformatted and reinstalled a fresh copy of 15.04, and after doing so I am now unable to reboot or shutdown, via terminal or from the GUI. Upon doing either, I get the purple loading screen, and there it stays.
...
Still not fixed, although now I can see that the freeze occurs after "reached target shutdown." A quick Google search seems to show that my intel NUC bios just doesn't recognize the shutdown command being issued, although it worked on previous ubuntu versions
He has the same sympton, it simply stops after reaching systemd "target shutdown". Which is probably the new default on ubuntu, eg why it didn't had issues previously.
Any way to work around the issue, maybe some legacy signal to go along with systemd's way?
Last edited by gfurst (2016-01-25 17:41:06)
Offline
I think I'm seeing a similar issue. After issuing a `poweroff` the system shuts down, fans spin down, but the blue LED remains on indicating something's still running.
A force poweroff (long power button press) is needed to actually shut down. Any news on this?
Offline
I think I'm seeing a similar issue. After issuing a `poweroff` the system shuts down, fans spin down, but the blue LED remains on indicating something's still running.
A force poweroff (long power button press) is needed to actually shut down. Any news on this?
Hey there, it seems the issue solved it self for me... not sure if dependent on bios update I performed...
turned out my retail bios was very old, I remember though it didn't solve it at first...
but somehow the 'poweroff' and 'reboot', systemd commands normally after that...
Offline
@gfurst, please mark your thread as solved and also change "does" to "doesn't" in the thread title.
Offline
This was resolved for me by disabling the CIR (infrared sensor)
Offline
@gfurst, please mark your thread as solved and also change "does" to "doesn't" in the thread title.
sure thing...
This was resolved for me by disabling the CIR (infrared sensor)
could be something, though I use the remote frequently... maybe the bios upgrade sorted that out.
Offline