On February 22, 2018 1:57 PM, 'awokd' via qubes-users <[email protected]> wrote:
>On Thu, February 22, 2018 1:49 pm, Aaron Dough wrote: > >>Good to know. Since Tuxedo especially advertises it's native >> Linux-support, I think I'll ask their support directly regarding this >> issue. It may be far fetched, but if this is really solvable with updated >> firmware, it's worth a shot :-) >> > > His case was a little different because he wanted to use them across > separate VMs. In theory that can be done if you set both devices to not > require strict reset. In your case, maybe try to assign them both to > sys-net without strict reset (but you might have already tried that too). > Yes, I've tried that too. Although I noticed that the Qubes Manager currently doesn't seem to set no-strict-reset property properly, so I tried again via command line. As soon as both devices (3:00.1 and 3:00.0) are attached, sys-net will not start, no matter the no-strict-reset flag(s). If only .1 (Ethernet) is attached, it will result in unstable behavior. With no-strict-reset=true sys-net will freeze after a standby (no reaction when I click the networking-icon, no qvm-shutdown possible, only qvm-kill). -- 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/JJqOfvco5VlYyzgmAcLUxXo3TGhv_O2p3dKsLKGSgzt6vF2UmoGNRyYTj7qNd7bYe7iEzqOWI6ESs5FwoNw1bJrVZtQox2oa5s4I20CdF9Y%3D%40protonmail.ch. For more options, visit https://groups.google.com/d/optout.
