HCL - intel NUC10i7FNK

[Ludovic Bellier]

The intel NUC 10 works great with Qubes-OS 4.0 but need some settings,
see below.


The default provided kernel didn't recognize the included NIC (I-219V,
in sys-net no listed network device with `ip a`) and the GPU used the
restricted 800x600 pixel resolution.


Reason: the too old 4.8.5 kernel doesn't recognize this fresh hardware.


The solution, use the 5.6 kernel:

- first use an USB NIC adapter

- sys-net : remove all devices in Qube setting

- dom0: detect the USB NIC identifier with 'qvm-usb' (ex: sys-usb:3.3)

- dom0: 'qvm-usb attach sys-net sys-usb:3.3' (attach the USB NIC to sys-net)

- sys-net : 'usb-devices' should display the USB NIC

- sys-net: check network works ('ip a', ping, new connection
notification, red network icon in tray-bar),

- dom0: switch to the latest-kernel with 'qubes-dom0-update
kernel-latest', got 5.6 kernel,

- qubes-os : shutdown, unplug the USB NIC, restart the host

- check GPU driver provides a better resolution (>= full HD display),

- sys-net: set new kernel for sys-net in Qube setting,

- sys-net: reboot,

- sys-net: remove all devices, and attach only the '00:1f.6 Ethernet
controller' (i.e.: I-219V device) with the 'no-strict reset' option,

- sys-net: reboot,

- check sys-net uses the I-219V NIC and network works ('ip a', ping, new
connection notification, red network icon in tray-bar).


I didn't check wireless and sleep because I don't use them for this host.


Regards,

Ludovic

[zhao...@gmail.com]

在 2020年7月20日星期一 UTC+8上午8:47:49，Ludovic Bellier写道：

The intel NUC 10 works great with Qubes-OS 4.0 but need some settings,
see below.

......

Thanks for the guidance!
I also have nuc 10i7fnk. but I have problems installing qubes OS 4.0.  I hope I can get answers from you.
I Set legecy mode, security booting off, use USB stick to install OS.
The following warning maseges&error is displayed when booting.

"WARN anaconda: /usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning: add_option is deprecated and will be removed in pykickstart-3.  Use add_argument instead.

   op.add.option("--minlen",type="int")

......

WARN anaconda.stdout:Not asking for VNC because we don't have a network

......

WARN anaconda:X startup failed: Xorg exited with status 1

WARN anaconda.stdout:X startup failed,aborting installation

ERR anaconda.stdout:X startup failed, aboting installation"

Do I miss setting something in bios or do I need to install the OS with DVD?

Thanks a lot!

[Ludovic Bellier]

[Note: sorry for not replying directly to the original thread, but I
wasn't yet registered to the mailing-list, so I can't do a reply with my
MUA]

Original copy-paste mail from zhaojx88  (see :
https://groups.google.com/d/msg/qubes-users/vRKrs5ZIg9c/WUepmWP9BwAJ):

> Thanks for the guidance!
> I also have nuc 10i7fnk. but I have problems installing qubes OS
4.0.  I hope I can get answers from you.
> I Set legecy mode, security booting off, use USB stick to install OS.
> The following warning maseges&error is displayed when booting.
> "WARN anaconda:
/usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning:
add_option is deprecated and will be removed in

> pykickstart-3.  Use add_argument instead.
>    op.add.option("--minlen",type="int")
> ......
> WARN anaconda.stdout:Not asking for VNC because we don't have a network
> ......
> WARN anaconda:X startup failed: Xorg exited with status 1
> WARN anaconda.stdout:X startup failed,aborting installation
> ERR anaconda.stdout:X startup failed, aboting installation"
>
> Do I miss setting something in bios or do I need to install the OS
with DVD?
> Thanks a lot!

zhaojx88,

    you got a *network error*, so may be, you should follow my steps
with a USB Network Interface Controller (aka USB ethernet), because the
internal ethernet card isn't recognized by the default 4.9 linux kernel.

    My BIOS setting:

Boot (section)

  Secure Boot        Disabled

  UEFI Boot            Enabled

  Legacy Boot        Enabled

  > Secure Boot (sub-section)

    System Mode    User

    Secure Boot      Disabled

    Not Active (title)

    Secure Boot Mode   Standard

  > Boot Priority

    UEFI Boot       x (i.e. checked)

    Legacy Boot   x (i.e. checked)

    USB                x (i.e. checked)

    I used the 4.0.3 ISO from https://www.qubes-os.org/downloads/  on a
USB storage stick. On boot I used the F10 key for choosing the *UEFI*
USB device stick. And I installed Qubes-OS on my SSD with the help of
the Qubes-OS documentation.

    Note also than my first 4GB USB stick was too small for the iso,
finally I used a 32GB stick (but 8GB will be fine).

    If this doesn't resolve your problem, give more information (BIOS
screenshots, when you got the above error message, ...)

--

Ludovic

[zhao...@gmail.com]

Thanks a lot!

I  tried just as you mentioned. Now it's working!

The problem was that I didnot use "UEFI" booting mode.

Thanks again!

[Alex Smirnoff]

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

[Ludovic Bellier]

Le 30/10/2020 à 16:37, Alex Smirnoff a écrit :
> 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

[Alex Smirnoff]

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.

[Ludovic Bellier]

Le 30/10/2020 à 17:57, Alex Smirnoff a écrit :
> 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

[Alex Smirnoff]

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

Sent from my BlackBerry -- I don't believe it's more secure, but I've got a physical keyboard!

  Original Message  

Good.

[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

--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/vRKrs5ZIg9c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a3f5a5ad-346c-71ed-54b3-f3e30b7fb75f%40zyrianes.net.

[Alex Smirnoff]

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

[Ludovic Bellier]

Le 30/10/2020 à 19:52, Alex Smirnoff a écrit :
> 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

[Alex Smirnoff]

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 :(

[Andrew David Wong]

On 10/31/20 11:55 PM, Alex Smirnoff wrote:
> 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 :(
>

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.

> On Friday, October 30, 2020 at 9:28:26 PM UTC+2 Ludovic Bellier wrote:
>
>> Le 30/10/2020 à 19:52, Alex Smirnoff a écrit :
>>> 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
>>

--
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

[Stephan Hagen]

Hello all,

I got it running on Intel NUC10FNH and use already latest kernel and network is up and find.

Can you give me a hint what you want to tell with 

" - check GPU driver provides a better resolution (>= full HD display), "

I have already 4k resolution but only software rendering.

My xorg.0.log told me:   AIGLX error: Calling driver entry point failed. ...reverting to software rendering."

I can not find what I have to change. Graphics is lousy. 

In my EFI - Boot settings at xen.cfg   is already (without my changes)   options   "iommo=no-igfx" and kernel "i915.alpha_support=1"  like described

May be somebody can help me to fix my graphic.

Thank you

Stephan

[Stephan Hagen]

Ok, I just found small solution for stable display without artifacts and blackouts. But I think hardware rendering is still of. May be I´ll get a hint here.

For making it stable I found following solution:

https://github.com/QubesOS/qubes-issues/issues/6311