Can't install QUBES 3.2

[codeu...@gmail.com]

I am trying to install QUBES 3.2
I get onto the screen with penguins + 30 lines starting with '[ OK ] '
And the last line : 'Starting Switch Root...'
I have waiting several hours, nothing happened.
I am on a ASUS Z170 PRO GAMING + GTX 1060 3Go + 32 Go + i5 6600K.
I test different configuration. This one is :
- Intel Virtualisation Technology enabled
- VT-d active
- Other OS (I mean UEFI disabled)
I used rufus 2.12 for the .iso in a 16GB usb key
Please help.

[aperi....@gmail.com]

Funny enough I've run into similar issues with almost identical hardware at some point not too long ago, the one and only difference is I used a i5 6500 Processor, everything else was identical.

I'm assuming you are into gaming because you have a GTX 1060?

For starters, the graphic card: I can tell from experience that GTX 1060 does not play well with Qubes 3.2, as the Linux nouveau driver doesn't support it too well under Qubes, and the proprietary drivers from nvidia doesn't easily install on Xen.
Your on-board Intel graphics from your i5 6600 CPU on the other hand should however work excellent with silky smooth results in Qubes.
Try switch your monitors to your on-board motherboard.
Frustratingly, non-quadro Nvidia cards are a very poor choice if your plan was to GPU Passthrough to run high end gaming level graphics, i.e. to make gaming possible on Qubes. This is in part because of lack of support for GTX 1060 in Xen/nouveau development as well as nvidia trying to making extra profit by separating graphic cards that support virtual environments (Nvidia Quadro cards). It is a bitch move by nvidia, especially as many nvidia cards has the GPU passthrough feature functionality within them, but it is turned off to force people to buy expensive Quadro cards. In the future however, if Xen/nouveau start to better support GTX 1060 (which likely eventually happens), then GTX 1060 will likely come to run pretty good in Dom0 environment in the future, which incude all your VM's, but still not for gaming. But if your plans is to GPU passthrough for a specific VM to i.e. run games in that VM, then this issue is with Nvidia's profit whoring at the cost of user satisfaction, and not the missing to come future GTX 1060 development support in Xen/nouveau. At the very least as far as I understood it from the research I did into it.

If you are dual booting then you may want to get a KWM switch to switch one or more monitors from your on-board connections over to your GTX 1060 connections for i.e. gaming on Windows (I assume that is why you got the GTX 1060). This makes it much easier to dual-booting with monitors tied to both nvidia and intel graphics.

New to Qubes or just a new machine? If new to Qubes then keep in mind that dual-booting is to some level a dangerous but possibly (maybe, speculative uncommon?) security risk. But if you still want to do it, then for example this is a good starting read https://www.qubes-os.org/doc/anti-evil-maid/
It is only if you want to strive towards incremental improved security though, dual booting should be more secure than using not using Qubes OS altogether anyway.

Back to the graphics issue at hand: In BIOS be sure to set default boot to CPU graphics, not your GPU, as well as avoid/disable any shared memory between CPU/GPU found in the same BIOS sub-menu. As your setup is almost identical to the system I set up, then most likely it won't work well or at all if these two options are not set right.

You don't need to take out your graphics card, just switch monitors and change BIOS graphic focus.
You may possibly be able to boot into Qubes with GTX 1060 using out of the box open-source nouveau driver, but it will be laggy as hell. Your on-board integrated Intel CPU graphics will in contrast be silky smooth.
With this motherboard/CPU you can also easily triple monitor with your Intel integrated graphics.

Also UEFI dual-boot works fine on your hardware. Multi-boot with other OS's like Windows 10. Dunno if you had this experience before, but if you didn't then just be mindful if you install or run a major upgrade of Windows, as it potentially kills your Grub or removes EFI in BIOS despite that the EFI still physically is on the designated drive (at which point just live usb/cd any trusted Linux distro and re-install Grub, conveniently the same solution as if Grub is missing). It is pretty easy to re-install Grub to reload EFI in BIOS though. Anyway, the point is UEFI works fine as long as Windows doesn't go banana mode every now and then. Keep the "Other OS" setting with the loaded, mine is always set to "Other OS". There are two set of UEFI keys though, it is a bit tricky, I didn't investigate it further or whether that could be a problem. Factory resetting the battery on BIOS should bring back those secure keys which are different from the ones if you restore them manually via the restore button in the UEFI settings, But I never used the set of UEFI keys that are tricky to get reloaded back anyway, just the default restored ones after having removing the keys altogether. For the life of me, why are there two set of keys? anyway...

Also by any chance did you use BTRFS as your filesystem? The root error "might" be because of that. If you did, then you need to edit your Xen.cfg file on the boot partition to include a root target, because BTRFS in Qubes apparently shifts the root location by a single upstream folder, and the result is it can't find it without a slight minor but critical fix in the Xen.cfg file.

I spend a good day figuring out why Qubes wouldn't boot on hardware essentially identical to yours. Out of the box it doesn't work, but with proper adjustments it will run perfectly. Hopefully any of this may be useful to you, with memory from many months ago, I may have forgot some details by now. I think I got a lot of the issues I had covered here now.

[codeu...@gmail.com]

Hi
Ok so I have set Primary Display -> CPU Graphics instead of auto in the BIOS.
And the screen don't freeze now, the installation go on. This is a good point.
So big thx for your answer.
But now I have another problem. I have put some number in my phrase key for ssd encryption. After reboot, it ask me the key but when I tape number the screen switch. Furthermore I get this error :
[FAILED] Failed to start Load Kernel Modules
[ 18.574872][drm : i915_gem_init_stolen[i915]] *ERROR* conflict detect with stolen region : [0xb6000000] - 0xb8000000]
I noticed that in my BIOS I have now 2 disk for boot :
SATA6G_1: Crucial_CT525MX300SSD and Qubes(SATA6G_1: Crucial_CT525MX300SSD1).
I get stuck with that now. If you have any idee tell me. I ll try to find a solution.

I choose a GTX 1060 because I believed Qubes was best compliant with nvdia, and I plan to use double screens with QHD + use of blender + game if possible yes.
I am new to Qubes and it's a new machine. I prefer avoid dual boot and will get Windows in a Qubes VM for better security.
If I use BTRFS as my filesystem? I don't know.

[codeu...@gmail.com]

Ok now it's working fine.
I have restart installation but with a password without number.
It may due to a difference between FR keybord and US keybord configuration.

So now I am using the CPU chipset Graphic.
I just hope the next version of Qubes will support GTX 1060.

[harry]

I am running a GTX570. On first boot I have the same stolen region error. (albeit with a different region specified).

Switching to onboard VGA has bypassed the issue.

[codeu...@gmail.com]

Le mercredi 15 février 2017 12:13:19 UTC+1, harry a écrit :
> I am running a GTX570. On first boot I have the same stolen region error. (albeit with a different region specified).
>
> Switching to onboard VGA has bypassed the issue.

What do you mean by switching to onbord VGA ? Did you change someting on your BIOS or did you change the way you plug your monitor with your computer ? (HDMI to VGA ?)
I havn't see any option in my BIOS about onbord VGA and I have no VGA plug socket on my GTX graphic card.