[qubes-users] Re: HCL - intel NUC10i7FNK

How did you set up the sys-usb qube without losing the USB keyboard and mouse?

Hi Alex,

 I followed the Qubes documentation, first I added the sys\-usb Qube \[1\], then I added my USB keyboard available for login \[2\]\.

[1] https://www.qubes-os.org/doc/usb-qubes/#creating-and-using-a-usb-qube

dom0/Terminal : sudo qubesctl state.sls qvm.sys-usb

[2] https://www.qubes-os.org/doc/usb-qubes/#enable-a-usb-keyboard-for-login

dom0/Terminal : sudo qubesctl state.sls qvm.usb-keyboard

Ah, apparently it was just a glitch, second time I tried my keyboard remained functional.
However, still no luck: after I updated dom0 to the latest kernel, my Qubes system just got stuck on “Enter disk password” stage. I see some corrupted image below which slightly changes over time, and that’s it. And I cannot switch to text console to see what is happening there like I could on a regular linux. WIll try booting from a rescue image now. Anyway, Qubes on NUC10 is apparently very unstable. I wonder why there is no ISO image with the latest kernel already in place.

Ah, apparently it was just a glitch, second time I tried my keyboard remained functional.

Good.

However, still no luck: after I updated dom0 to the latest kernel, my Qubes system just got stuck on "Enter disk password" stage. I see some corrupted image below

It's same for me, I see the corrupted image on each boot (since 6 months now), but (on my host) it's only a display problem, I can give the disk password (you should see the bullet [3] for each character) and the boot process continues. Note that this step concerns giving the LUKS credentials (not the user password!), and the GUI you see is Plymouth [1] with this artwork [2].

which slightly changes over time, and that's it. And I cannot switch to text console to see what is happening there like I could on a regular linux. WIll try booting from a rescue image now. Anyway, Qubes on NUC10 is apparently very unstable. I wonder why there is no ISO image with the latest kernel already in place.

You can't switch to tty (text console) because the boot process is on the LUKS uncryption step, so the rootfs isn't yet available (so the init process isn't launch and neither the login process).

Don't worry, Qubes OS on NUC10 is stable, I use it daily.

I agree an ISO image with, on start, the choice between default or latest kernel will be great.

[1] https://wiki.archlinux.org/index.php/Plymouth

[2] https://github.com/QubesOS/qubes-artwork/tree/master/plymouth/qubes-dark

[3] https://github.com/QubesOS/qubes-artwork/blob/master/plymouth/qubes-dark/bullet.png

apparently I messed with the keyboard somehow, I cannot type in the password. it ignores all keystrokes :frowning:

   Original Message

Now, that’s strange! my dom0 is on the latest kernel, but sys-net is not, so, no network there.

Its normal, all VMs keep the default kernel, not the latest.

You should change the sys-net VM kernel to latest:

- open Qube Manager

- select sys-net

- right clic, choose Qube-settings

- Advanced tab, change the kernel to 5.x.x

- Apply and restart sys-net

I had to update it first. Also, removed rhgb to get around the password prompt bug.
What an amazing system! I installed it to evaluate if it is suitable for our company environment and instantly fell in love with it. However, the answer to my main question is still “no” :(. Unless we buy certified hardware for everyone, at least, and some of us badly need properly working Win10 guest with seamless desktop app integration and clipboard :frowning:

I had to update it first. Also, removed rhgb to get around the password
prompt bug.
What an amazing system! I installed it to evaluate if it is suitable for
our company environment and instantly fell in love with it. However, the
answer to my main question is still "no" :(. Unless we buy certified
hardware for everyone, at least,

If certified hardware is prohibitive for your company, you might investigate the ThinkPad X and T series within the past few years, beginning around the time of the X1 Carbon Gen 5. There may be certain problems (e.g., AEM or suspend not working), but they might still work well enough, depending on what your needs are.

and some of us badly need properly working
Win10 guest with seamless desktop app integration and clipboard :frowning:

Depending on why Win10 VMs are needed, there might be alternatives available, e.g., cloud apps or a Windows machine on your local network that can be accessed remotely from the Qubes machines.