I have resolved my problem. I will document here to help out anyone
else who has this issue in the future.
This is a Zotac ZBOX Nano CI320 (ZBOX-CI320NANO).
My BIOS version is "B219P 026 x64" with a date of "05/19/2015". That is
current as I write this. I also saw this problem with previous versions
of BIOS.
The root cause of the problem was that I set the "Boot Mode" to "Legacy
Only" and "OS Selection" to "Windows 7". Instead, set it to "Windows 8.X".
I saw the following problems when the OS Selection was Windows 7:
Reboots, poweroff, suspend, and hibernate all hung.
Installation of Debian and Ubuntu hangs on "Running dpkg" under
"Select and install software".
When set to "Windows 8.X", The system reboots Linux as expected.
Be sure to update the BIOS if you have not already. I used FreeDOS on a
USB flash drive made with unetbootin. Copy the firmware .zip files onto
the root of the flash drive. Boot into FreeDOS and load no drivers (Safe
Mode). Type "cd C:" and then you should see the files there. Run the
"batch.bat" file and that should update the firmware.
There is also a USB hub firmware upgrade available for this system, but
I wouldn't bother since it requires Windows 7 to install, and I had a
lot of problems doing it.
Beware that these BayTrail-M systems (Intel NUC, Gigabyte BRIX, HP
Stream, Asus ChromeBox, Asus Vivo, and a huge number of laptops) have a
large number of reported problems with USB also causing problems:
About the reboot hang issue with EHCI driver on the Baytrail platform
http://www.spinics.net/lists/linux-usb/msg112624.html
[SOLVED] Random hang/freze on reboot/shutdown/suspend, only under Arch
https://bbs.archlinux.org/viewtopic.php?id=192821
On 6/25/15 2:42, Jesse Molina wrote:
Hi all
I have a new Zotac ZBOX Nano CI320. It's a mini-PC based on an Intel
Celeron N2930 (Bay Trail).
This has been a very problematic system. I blame my troubles on the
less-than-quality Zotac (AMI) BIOS.
My current problem is that the system will not reboot or poweroff
correctly. It just hangs.
I have upgraded the BIOS to the current version, which fixed a lot of
other issues, but not this one.
I've confirmed this bad reboot/poweroff behavior on Debian 8.1 and the
current unstable. One thing to note is that I was having some
intermittent success adding the kernel argument "reboot=bios" on
Debian 8.1, but now that I've upgraded to unstable, it's not working
any more. I need to do more testing to verify what works and what
doesn't, but everything is mostly not-working.
I also confirmed this bad behavior with the current Fedora release.
Interestingly, the current Linux Mint seems to reboot and poweroff
normally:
http://www.linuxmint.com/edition.php?id=172
Other than testing various linux "reboot=" arguments, what other
things should I look into?
For permanent application, that reboot= would go into
/etc/default/grub, right?
Any other advice before I bug this?
Thanks for reading.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/558e0b97.8020...@opendreams.net
