I have been able to get my machine up and running Qubes 3.2 with good hardware 
support: keyboard, touchpad, touchscreen and stylus all work nicely. The one 
sticking point is wireless networking.

In terms of the hardware build, I'm dealing with a machine that has everything 
mentioned above on one PCI-USB device. This is assigned to dom0.

Networking doesn't seem to work in dom0; no wireless SSIDs appear. I don't know 
if this is a problem or simply dom0 not allowing it by design.

However, when I do qvm-usb the network card is listed as an available USB 
device, so the system is at least aware of it. Additionally, I tested Fedora 23 
on this machine and was able to use the network card so long as the Linux 
kernel was 4.3 or greater, which is the case in Qubes 3.2.

I'd like to assign the USB networking card to sys-net (or a new netvm USB qube 
if need be) if that's possible. However, it cannot be separated out; the entire 
PCI-USB device must be assigned, which means all of the input devices go as 
well.

As I understand it, the keyboard can be allowed to pass input to dom0 from a 
USB qube; would treating sys-net this way be making is a USB qube for such 
purposes?

I've tried making this work by adding "sys-net dom0 allow" to the 
qubes.InputKeyboard file in /etc/qubes-rpc/policy as described in the qubes 
online documentation, then assigning the PCI device to sys-net.

This does not seem to work. Upon re-start, input is no longer received by dom0. 
I can do nothing at that point. So, I am either misunderstanding what should be 
possible, incorrectly attempting it, or missing something.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1b03b3ed-8c51-4183-a47e-503584743d4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to