@unman The dom0 updates setting is set correctly and working as intended
through the VPN qube, I haven't tried browsing from the VPN qube itself but I
can definitely browse from an AppVM connected to it and I can confirm that all
the browsing being done there is tunneled through the VPN.
I'm
Chris:
Hi all!
Welcome!
Successfully booted into Qubes but couldn't get network working.
1. Physically, port LEDs go off and start blinking after awhile. Keeps
repeating.
2. Network icon on top right is red and shows 'loading animation'
3. Network adapter can negotiate speed and duplex but
By all means hold your horses on asking if Qubes is vulnerable to every single
one of those lol
I used to be paranoid about Computer Security but if you ain't even gonna
bother to delve deep down from how computers work up to the way computer
applications/programs work then you should just
Hi all!
It's my first time installing Qubes and I need some help with my network
adapters.
I am using Qubes 4.0.1
The hardware is Fitlet2 with Intel Celeron J3455 (supports both VT-x and VT-d).
It comes with 4 Gigabit Ethernet ports using Intel i211.
Installation was successful but EFI boot
On 6/26/19 7:56 AM, 'awokd' via qubes-users wrote:
Chris:
Hi all!
Welcome!
Successfully booted into Qubes but couldn't get network working.
1. Physically, port LEDs go off and start blinking after awhile. Keeps
repeating.
2. Network icon on top right is red and shows 'loading animation'
After I Add network controller to sys-net I go to applications to add network
shortcut but no applications appear but when I try to refresh I get the
following error: ‘Domain sys-net has failed to start: internal error:
libxenlight failed to create new domain sys-net’
I can’t edit anything
On Wed, Jun 26, 2019 at 02:54:04AM -0700, Sphere wrote:
> @unman The dom0 updates setting is set correctly and working as intended
> through the VPN qube, I haven't tried browsing from the VPN qube itself but I
> can definitely browse from an AppVM connected to it and I can confirm that
> all
On 6/26/19 9:06 AM, unman wrote:
On Wed, Jun 26, 2019 at 02:54:04AM -0700, Sphere wrote:
@unman The dom0 updates setting is set correctly and working as intended
through the VPN qube, I haven't tried browsing from the VPN qube itself but I
can definitely browse from an AppVM connected to it
After I Add network controller to sys-net I go to applications to add network
shortcut but no applications appear but when I try to refresh I get the
following error: ‘Domain sys-net has failed to start: internal error:
libxenlight failed to create new domain sys-net’
I can’t edit anything
Now I see this affects Debian templates also. Its just that Debian is a
little more persistent and may succeed sometimes.
I believe the culprit is with the fedora-30 version of the updates proxy
– it seems to be un-blocking the update procedure before it is ready to
handle traffic.
--
I wouild like to use wasbi in a whonix VM.
Can any one tell me how to make it work step by step_
Thansk for youre time and suport
--
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
thanks awokd. works perfectly
--
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 this group, send email to
It worked, Thanks a lot!
--
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 this group, send email to
So I've gone through all the trouble installing blueman and exposing my
hypervisor to all the building.
I have found out that bluetooth headphones operate at 2.4ghz which happens to
be the same frequency as my Dell's wireless card. So if you attempt to listen
to music via youtube, evntually
And I get the same libxenlight error for sys-whonix and disp7764 but I can’t
add Bus because of the dynamic memory balance
--
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
On 6/25/19 2:13 AM, 'awokd' via qubes-users wrote:
danotty via qubes-users:
Hello
Does exist a software to capture video-screen in Qubes?
Check under Productivity on
https://github.com/Qubes-Community/Contents/tree/master/code.
you would install a debian or fedora package that does a
On 6/21/19 10:37 PM, ljul8047-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
So I’m still learning about Qubes but I have a question please. I was told that
if dom0 gets infected, everything in the laptop can be found and read. The ip
is not a problem but I’m not sure about the MAC address? If
'[NOTIFICATION]' via qubes-users:
Attachment: Qubes 401 Emergency.jpg
Can't seem to install Qubes 4.0.1 on the RAZER BLADE GTX and even on the RTX
models. Keeps sending to emergency mode. Using the USB SOFTARE in the link. It
is known as ETCHER.
What causing this installation being sent to
PS: And since what I said is not specific to Qubes, there doesn't seem to be a
good reason to use the internal laptop bluetooth in any operational system at
all.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group
On 6/26/19 1:33 PM, Chris Laprise wrote:
On 6/26/19 7:56 AM, 'awokd' via qubes-users wrote:
Chris:
Hi all!
Welcome!
Successfully booted into Qubes but couldn't get network working.
1. Physically, port LEDs go off and start blinking after awhile.
Keeps repeating.
2. Network icon on top
'awokd' via qubes-users:
> ehag...@gmail.com:
>> I wouild like to use wasbi in a whonix VM.
>>
>> Can any one tell me how to make it work step by step_
There's some discussion here:
https://forums.whonix.org/t/wasabi-wallet-in-whonix/7597.
Basically just download it, verify signature, run it,
Now the error is: fedora-29 has failed to start after I try to import
applications. Based off of what you helped me with so far, I’m going to assume
the remaining systems just need to be assigned a PCI device? I’m just not sure
which goes where.
--
You received this message because you are
shamaarmarti...@gmail.com:
And I get the same libxenlight error for sys-whonix and disp7764 but I can’t
add Bus because of the dynamic memory balance
Don't add devices to other VMs. If you've made changes to VMs besides
sys-net, undo them. Does sys-net start now and your networking work?
--
shamaarmarti...@gmail.com:
Now I get the error: Unable to reset PCI device :00:1f.4 no FLR PM reset or
bus reset available.
Set that device to not require strict reset, either by clicking the
large button at the bottom of the Devices tab, or
ehag...@gmail.com:
I wouild like to use wasbi in a whonix VM.
Can any one tell me how to make it work step by step_
Assuming Wasabi is a cloud provider and assuming it has some Linux
client (would be good if you provided more detail so people don't have
to guess), the direct answer to your
shamaarmarti...@gmail.com:
It worked, Thanks a lot!
I saw you started a couple other threads. Are you still having trouble
with sys-net? Looks like you have one of those buggy Realtek adapters.
Try also adding the Realtek Cardbus device to sys-net the same way you
added the wifi adapter,
I am not sure if this is related to recent updates but after updating today and
doing a reboot, my sys-firewall and other appVMs are not getting DNS resolving
working.
- sys-net (fedora30) starts up with out an issue, can resolve and connect to
the internet
- sys-firewall starts up and gets an
Now I get the error: Unable to reset PCI device :00:1f.4 no FLR PM reset or
bus reset available.
I also get a failed to start kernel module when booting but I log in fine.
I also forgot to mention that I created a couple installation partitions during
my earlier failed attempts( stupid on my
On 6/27/19 1:10 AM, Chris wrote:
Quickest thing to try is to switch sys-net's template to Debian. Also,
experiment with
I tried the Debian template but it still doesn't work. Same symptoms
https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues attach
options.
I need some help
> I don't think you said which template you are using for sys-net did you?
The default was Fedora-29.
And some observations..
When I shutdown sys-net, the physical LED of the network adapter is still going
through the blinking and off cycle. This probably means that it has nothing to
do
@unman: thanks for that
I also noticed that qubes-updates-proxy.service fails by default on startup and
I'm unsure if that is a minimal template-only problem but I was able to fix it
thanks to it indicating that the problem is a missing folder:
/var/run/qubes-service/qubes-updates-proxy
Pretty
Seems like security risk so I didn’t. Sys-net comes to a hault but no error
code when starting.
--
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
> Quickest thing to try is to switch sys-net's template to Debian. Also,
> experiment with
I tried the Debian template but it still doesn't work. Same symptoms
> https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues attach
> options.
I need some help here. Couldn't find the
Qubes 3 runs Fedora 23 as the dom0. For this reason I assume you are
trying to upgrade from Qubes 3 to Qubes 4.
This configuration of upgrades is not supported. You must reinstall
Qubes using the Qubes 4 installer, then restore your VMs from a backup
of your Qubes 3 install.
On 20/06/2019
34 matches
Mail list logo
