On 4/9/19 12:58 PM, Ray Joseph wrote:
Thank you for your support. I don't know what 'panel' I should see the
nm-applet opening in. I opened a terminal in sys-net and entered nm-applet and
obtained a response that said it was not meant to run in terminal and to use
NetworkManager in the
Thank you for your support. I don't know what 'panel' I should see the
nm-applet opening in. I opened a terminal in sys-net and entered nm-applet and
obtained a response that said it was not meant to run in terminal and to use
NetworkManager in the desktop. I don't see a way to open a
On Sat, Apr 06, 2019 at 07:06:41PM -0700, Ray Joseph wrote:
> I would like to config sys-net to access my wireless AP. I have not found a
> method to config the network. I looked for /etc/network/interface to see if
> anything was there but the network folder does not exist.
>
> I found
I would like to config sys-net to access my wireless AP. I have not found a
method to config the network. I looked for /etc/network/interface to see if
anything was there but the network folder does not exist.
I found suggestions that I could get to them via sys-net settings. I have
added
Thank you. It is great to learn where/what I need to read.
--
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 qubes-users+unsubscr...@googlegroups.com.
To post to
Ray Joseph wrote on 4/5/19 3:37 AM:
unman,
Thank you.
On opening sys-net, there were two USB controllers already attached, one was
00:14.0. So I removed both and added the nic. Sys-net is now running.
So I now want to test it. I thought I could just open a vm such as debian, but
I found
unman,
Thank you.
On opening sys-net, there were two USB controllers already attached, one was
00:14.0. So I removed both and added the nic. Sys-net is now running.
So I now want to test it. I thought I could just open a vm such as debian, but
I found it says it can't have networking.
On Thu, Apr 04, 2019 at 05:13:03AM -0700, Ray Joseph wrote:
> unman
>
> Thank you for the trip through the qube. Currently, sys-net is still not
> working. I have tried both strict and not. And I have rebooted also
> rebooted after the change.
>
> What looks odd is under sys-net device, the
unman
Thank you for the trip through the qube. Currently, sys-net is still not
working. I have tried both strict and not. And I have rebooted also rebooted
after the change.
What looks odd is under sys-net device, the wireless card number is 02:00.0 and
reports my card. The error message
awokd,
> You do have to do it with sudo. In dom0, you are trying "sudo ls
> /var/log/libvirt/libxl"?
Thank you. I tried that and it did not work. You brought me back and now its
working.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
On Mon, Mar 25, 2019 at 04:20:48PM -0700, Ray Joseph wrote:
> I have installed Qubes on a Toshiba laptop with wirless only. When
> attempting to start sys-net from Qube Manager, an error is emitted:
> Domain sys-net has failed to start: internal error: Unable to reset PCI
> device 000:00:14.0:
Ray Joseph wrote on 3/25/19 11:20 PM:
I have installed Qubes on a Toshiba laptop with wirless only. When attempting
to start sys-net from Qube Manager, an error is emitted:
Domain sys-net has failed to start: internal error: Unable to reset PCI device
000:00:14.0: Internal error:
libxenlight
12 matches
Mail list logo