Check the box contents and record serial numbers. Try to get the ethernet MAC address so it can be registered with the firewall. Intel NUCs have the MAC address on a sticker on the bottom.
Beware: This machine has no memory, no disc and no operating system. You will need to obtain your operating system from another source. This of course is simple, inexpensive and legal for Linux.
What's in the box:
Intel Inside Core i5.
The power supply has interchangeable pins. None of them have a grounding pin. For the type letters see the IEC World Plugs website. These pin assemblies are provided:
The side walls of the chassis are aluminum, 2mm thick, and black anodized.
Leave the plastic film on the top cover until assembly is complete. People say that the cover picks up scratches.
On the table put a paper towel or eating mat, and a square of aluminum foil over it. Whenever you are handling memory, discs, or any parts inside the NUC, have your bare skin touching the aluminum foil and the chassis of the NUC. It's best not to touch any conductive (metal) parts on the memory, disc or motherboard; handle memory by the edges.
Remove the screws at each corner of the bottom cover. They are captive; they don't detach from the cover. Pull up on diagonally opposite screws for easier removal. Flip the cover towards the front of the machine.
Lift up the drive bay and move it to the front (don't need to unplug it) giving access to the motherboard.
They give you a preinstalled post for an 80mm long M.2 accessory (SSD); leave it alone (unless you're installing one; I'm not), but the post for 42mm is in a plastic bag. Install it now lest you lose it. You need both for an 80mm SSD.
Insert the memory cards. It will help to make them distinguishable, e.g. write 'A' or 'B' on the labels. Repeat this procedure for each one, starting with the bottom socket. (Designated 'A' in the BIOS.) Stick the memory into its socket, label up, above the visible row of contacts, at about a 30 degree angle, clearing the grabbers of the upper socket. There is a notch that defines the correct orientation. Make it go into the socket so the contacts (103 on each side) are barely visible, well under 1mm exposed. Now rotate the card down flat until the edge grabbers engage. The metal parts of the grabbers should be centered in the notches in the memory card. At this point at most 0.5mm of the card's contacts are visible.
To remove a memory card, pry outward on the grabbers until they let go (one at a time). Then rotate the card upward 30 degrees and pull it out.
Insert and screw down the SSD in the M.2 socket, per the setup guide. (I don't actually have a SSD.) There is also a 22x30mm M.2 card for Wi-fi, which is preassembled, and which you should leave alone.
Slide the 2.5in rotating disc or SSD into the drive bay with the label down. Push it into the SATA connector. Fasten the 2.4x3mm screws, 4 places. Relocate the drive bay inside the chassis. It will be held in place by the bottom cover's screws.
Replace the bottom cover. Note the arrow pointing to the front. Since the SATA cable pushes the drive bay upward, you may have to shove the cover down, to get the screws to engage.
The WiFi antennae in the top cover are preassembled; you don't have to mess with them.
Peel the protective films off the top and front of the machine.
Intel Inside and hostname stickers on the front.
To attach the pins to the power supply:
Iris (the 5i5RYH, with memory but no hard disc) wouldn't boot the USB stick. It turned out that I had not completely seated the memory. It gave me 3 blinks on the power button (and would have beeped if speakers or phones were plugged in). Blink and Beep Codes for Intel NUC:
Function keys while booting: If you have UEFI boot turned on, there is no splash screen with its list of function keys. But it does still respond to the keys, during an about one second interval when the splash screen would have been shown.
Booting from USB storage: Get into BIOS setup by pressing F2 during boot.
On the left side of the start screen is the
Boot Order panel. Use your
USB mouse; shift from the UEFI to Legacy tab. Double click on whichever
device, to boot from it immediately. Or you could have used the F10 boot menu.
Obtain the updated BIOS (before installing the OS). This machine has an Intel Management Engine (IME) and needs a recent BIOS to plug a gaping security hole.
Any Operating System. (Makes your life easier.)
BIOS Flash Update. This page is also accessible from the regular setup on F2.
Unknown Device. Scroll down to this line and hit Enter.
This should be done after the BIOS update because that resets at least some options to factory defaults.
To get off the home page, click on Advanced in the top row and choose one of the traditional categories. In later pages there is a tab bar with categories in the top row.
Realtime clock. It's set to civil time in timezone +8, i.e. China. Linux should set this by itself, but just for sanity upon boot, let's change to UTC. Where it says 09:08 next day, change to 01:08 next day. Minutes were 2min off (fixed).
Boot order: It has UEFI, but need to change to Legacy. Gotcha: there's some kind of weirdness so if you have only Legacy booting it won't recognize your bootable partition. You need to turn on both Legacy and UEFI. Legacy devices are available in this order:
Cooling: Control mode is
Balanced, with fan off temp = 40C.
I changed to
Quiet, changing the fan off temp to 45C.
Performance: I changed these items:
Security: I didn't change anything. Key items:
Power (primary): Default is max performance; changed to low power. You need to un-check it to pick a different one. If none of the three patterns is chedked, individual controls are shown.
Power (secondary): Key items; default was unchanged except as noted.
When finished, hit F10 to save and reboot.
Booting from Diamond's old disc. Power it off. Attach the old disc to the SATA-USB cable and plug that into a USB port. Power on and hit F10 for the boot menu. Select the USB device. See if it boots. Grub loads the kernel and initrd, but it's stuck trying to read /dev/sda2 (which doesn't exist yet) for hibernation. Takes about 2 mins to time out. Continues with normal booting. Diamond is up and on the net. If I had thought of it, I could have edited (in Grub) the kernel command line to omit the resume=/dev/sda2 parameter, avoiding the long timeout.
Copying Old to New Disc:
Mistake: I booted from the rescue system on an old v42.1 installation DVD. It boots with no problems. But I wanted to use yast2 and the rescue system doesn't have it. So I booted the old disc again.
/dev/sda (new disc) has no partition table.
/dev/sdb (old disc) partition table: MSDOS, 500Gb total. Beware, sizes are in powers of 2 unless you use the "units" command, i.e. 1kb = 1024b.
optimally aligned. Partition 1 is OK at 1Mb. But partition 2 had to be expanded to 38.8Mb. Maybe because it was FAT32?
advancedmenu on the partitioner's overview page.
New partition table:
|2||30Mb*||fat16||boot, esp||efi <(38.8Mb)|
Gotcha: partition 3's legacy_boot flag got lost and it can't be
booted. Do parted /dev/sda ; then set 3 boot on . Growl, didn't help.
Relevant forum post. On a NUC6CAYH the OP selected legacy boot and
disabled UEFI boot, and got the message
A bootable device has not
been detected (my symptom). Workaround: enable both UEFI and legacy
boot. That lets it boot, but it doesn't show the hotkeys or
NUC splash screen. It does, however, respond to the hotkeys if you
press them during the one second interval when the splash screen would
have been shown.
Copy partitions: ssync -a -x /home/ /new-home/
Using dd to copy the VM partitions. 100Mb/s on partition 6, 87.5Mb/s on partition 7. (Why the difference?)
Installing Grub on the new disc: use these commands:
mount -o bind /proc /new-root/proc
mount -o bind /sys /new-root/sys
mount -o bind /dev /new-root/dev
mount /dev/disk/by-label/0bbf-home /home
grub2-install /dev/sda #NOT /dev/sda3, you want it in the MBR
/usr/diklo/lib/daily/grubdflt.J #jimc's fixup script
exit #From chroot jail
umount /new-root/dev /new-root/sys /new-root/proc
It bitches about an improperly nested partition hostdisk//dev/sda,gpt6,msdos2 . The problem was that /dev/sda6 contained a wacked-out set of Windows partitions from an old incarnation of Baobei; #1 was 105Mb long and #2 was 52.3Gb long, which was bigger than the partition. I wiped it. Now grub installation is error free. It was actually successful before, but just for paranoia…
Boot on the new disc. Power off and disconnected the old disc first. Weird, it wanted to do a network boot despite the new disc being first. I used the boot menu (F10) and it booted. checkout.sh discreps: Only alsa-restore was wrong; created the new ALSA conf file.
Virtual machine hosting works; both Oso and Baobei started OK. However, Oso has always had network problems on Diamond and continues to do so; I don't want to debug this now, and I moved it to another host. Baobei's networking is fine but its nemesis is power management, specifically shutting down or rebooting, where it gets stuck. It had this problem before and continues to have it. Baobei runs Windows, and a configuration issue in qemu is blamed. I put a lot of work into fixing this with limited success (at least it boots now), but Baobei is mission critical, and we're going to give it a bare metal body.
Gotcha in hibernation: If Alice is the only user, she can hit
Hibernate and it happens. But if there's a root session (via ssh),
she is asked to authenticate (root password) to get permission to
take the machine down with multiple users on it. And then hibernation
does not occur.
systemctl hibernate (as root) works.
Speed test on Jimc's benchmark. All numbers are in kbytes/sec.
|SHA512||206760||CPU speed, kbytes/sec, doing a sha512 sum on concatenated large files preloaded into the buffer cache, using 1 core.|
|SHA512*cores||413520||Same, times the number of cores (2), not counting hyperthread if any.|
|Disc Read||11406||Speed in kbytes/sec to read OS files, way beyond the buffer cache.|
|Composite||134928||Composite score, 0.5*(I/O speed) + 0.375*(sha512) + 0.125*(sha512)*(number of cores).|
Unlike on the Fit-PC Pro and LP, the NUC has only one USB bus and all of the ports connect to it. This bus is provided with a XHCI (USB-3.0) and a EHCI (USB-2.0) controller.