Installation on NUC6i7KYK

353 views
Skip to first unread message

Mark Elston

unread,
Apr 17, 2017, 3:38:26 PM4/17/17
to qubes-users
I tried searching on this platform and qubes and haven't found anyone yet who has posted anything so here goes. I tried to install 3.2 on the Intel Skull Canyon Skylake NUC with Iris Pro Gfx. Tried UEFI mode and it seems to install fine but when I reboot it says "No bootable.." on startup. If I try to install in Legacy Mode it seems unable to start graphical installer and goes into a text-only mode. So finally I took a working install from a small/regular NUC that has been working fine, and when it boots it seems to go into text mode as well. I'm guessing maybe a gfx driver issue, but not sure if there is an easy way to update/fix. Any ideas?

Thanks,
Mark

babel

unread,
Apr 17, 2017, 3:41:56 PM4/17/17
to qubes-users

I just finished an install on a NUC. Hopefully I can help... one minute I'll write down.

babel

unread,
Apr 17, 2017, 3:53:36 PM4/17/17
to qubes-users
On Monday, April 17, 2017 at 9:38:26 PM UTC+2, Mark Elston wrote:


You are following the guide written at the Qubes website here...
https://www.qubes-os.org/doc/uefi-troubleshooting/
Which is not very easy to follow..

Your problem is either the first or the third (I did not really understand which mine was either, so I followed both).

1) reinstall qubes, and at the end of the install, follow # 4, 5, 11, 12, etc. on the first "problem".

2) On reboot, boot into a live cd of some sort (anything where you can get a terminal, I used Ubuntu because it's easy on the eyes). You are now trying to fix the third problem on the "troubleshooting" page.
When I tried to copy the /boot/efi/EFI..., I got an fstab error. Because the drive isn't mounted. I ran..
""
sudo umount /dev/YourQubesDrive
mkdir /tmp/MyDrive
sudo mount -o rw /dev/YourQubesDrive /tmp/MyDrive
"""
where YourQubesDrive is the drive you have just installed qubes on. I used gparted to make sure that it was the right one, but you can look where you're installing qubes as you're installing it or there is probably some linux command to do so.
I got that info from..
https://askubuntu.com/questions/794468/mount-cant-find-dev-sdb1-in-etc-fstab-or-etc-mtab

Then you can copy the stuff over from within the folder you made. reboot after.
cd /tmp/MyDrive

babel

unread,
Apr 17, 2017, 3:57:47 PM4/17/17
to qubes-users

And I realized you can just do the second step while you're doing the first one..
Hey, it's a learning process.

Mark Elston

unread,
Apr 17, 2017, 4:03:25 PM4/17/17
to qubes-users

Thanks babel. Is your NUC a Skull Canyon NUC? I have it running on regular NUC, but seeing different problems on Skull Canyon.

Ely105

unread,
Apr 17, 2017, 4:08:21 PM4/17/17
to qubes-users

Sorry, I didn't make it clear that I moved an SSD from a working NUC to the NUC6i7KYK and it started bootup but it seemed to fail on loading x11/gui. So it seems like a gfx driver issue.

babel

unread,
Apr 17, 2017, 4:28:02 PM4/17/17
to qubes-users

No, I've got a kaby lake i3 so nuc7i3bnh...
Using a m.2 I was running into issues on a new install. Wouldn't start boot-up, so I stuck an ssd with qubes in on it and that would boot up half-way. That's when i went to and did the uefi instructions.
I'm still new, so definitely could be a driver issue. And on that note, if you've got a similar bios and ever figure out what the best options for the graphics aperature options are, it would save me a headache.

informati...@gmail.com

unread,
Apr 27, 2017, 3:24:41 AM4/27/17
to qubes-users

Did you ultimately succeed?

I have also have an Intel NUC 6i7KYK and have gotten Qubes 3.2 installed on
the M2 SSD.
However, it won't boot.
I'm going to try the helpful instructions from babel, but there are some questions. Here are the files on the USB install drive:
-rwxr-xr-x 1 982K Dec 10 2015 BOOTX64.efi
drwxr-xr-x 2 2.0K Sep 20 2016 fonts
-rw-r--r-- 1 1.1K Sep 20 2016 grub.cfg
-rw------- 1 22M Sep 20 2016 initrd.img
-r--r--r-- 1 1.6K Sep 20 2016 TRANS.TBL
-rw-r--r-- 1 5.7M Jul 18 2016 vmlinuz
-rw-r--r-- 1 586 Sep 20 2016 xen.cfg
-rw-r--r-- 1 2.1M Jul 26 2016 xen.efi

The instructions under Boot Device Not Recognized After Installing say:
Copy /boot/efi/EFI/qubes/ to /boot/efi/EFI/BOOT/.
Rename /boot/efi/EFI/BOOT/xen.efi to /boot/efi/EFI/BOOT/BOOTX64.efi.
Rename /boot/efi/EFI/BOOT/xen.cfg to /boot/efi/EFI/BOOT/BOOTX64.cfg.

However,
1. There is no qubes directory
2. Do they really mean to *overwrite* the BOOTX64.efi file?

I'm guessing these instructions might have been meant for a previous version of Qubes.

Anyway, I can go ahead and try it. I was just curious how it went for you.
Also, I'm slightly concerned about driver support for the various NUC capabilities.

Ely105

unread,
Apr 27, 2017, 11:32:15 PM4/27/17
to qubes-users
Actually I was able to get it to work. After many failed attempts I did use UEFI mode to do installation and then I did do those instructions for "no bootable device" you show. I didn't try babels instructions. After I did that it booted right up. And it's been working ok even after an update to dom0, even though it said after kernel updates you have to do it again. I was noticing a weird issue where a browser in a given domain would freeze and I have to open another browser session to unfreeze it.

But one thing I did notice: i tried using the minidisplayport connector instead of hdmi and it would not boot. If I switched back to hdmi it was fine. So I think one Bkm is to use HDMI ONLY for qubes.

-m

Reply all
Reply to author
Forward
0 new messages