date:20200216

Re: [qubes-users] Re: Tor not connecting over DSL

2020-02-16 Thread 'awokd' via qubes-users

Anil:

Tor in sys-whonix doesn't know or care what kind of Internet connection

sys-net is using. If you use some other computer not running Qubes, can
Tor connect over that same DSL? You might be getting blocked upstream.

Looking at the logs, it seems to be related to swdate, although the date
command output is correct and the correct date is displayed on the taskbar.
Sometimes there is an error about time synchronization. It could also be
related to the DSL modem settings, as the same connection with an older
modem was working on the same computer with the same Qubes installation. I
tried various things in the DSL modem settings, but since I don't know what
kind of problems occur with DSLmodem, I don't really have an idea about
what to change. The new modem anyway has very settings, whereas the older
modem had a lot of settings which could be changed. That was a probably
used modem given to me and it was pre-configured. I don't have another
computer with Qubes installed.

The new modem does not show the correct date when I select automatic time
update in the settings, but when I deselect it, it doesn't show any date or
time. This is why I think it may be related to time settings.

By the way, even with other internet connections, when I try to connect

connect to Tor with the Connection Wizard, it always says Unknown

Bootstrap

Tag and please report it. Does that indicate some problem?

Not sure which wizard you mean, but I don't see that on mine.

The Anon Connection Wizard in sys-whonix. It was there by default on my
every installation.

I had trouble sometimes with swdate in Whonix 14. It would find some
source that was two or more weeks off, and refuse to connect. Are you
using an older install? Might be worth reinstalling Qubes 4.0.3 which
comes with Whonix 15. Also, I meant to test that DSL connection with a
computer running Tor, but not Qubes.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/c495953c-5185-eb3a-0605-4b3dc1a27040%40danwin1210.me.

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

2020-02-16 Thread 'awokd' via qubes-users

aihey:

I spent a yesterday afternoon looking into this. I built Qubes 4.1 (stable
version) following the instructions in
https://www.qubes-os.org/doc/qubes-builder/. I did this on the actual machine
and had to re-install the OS with Fedora 31 as the building tool didn't support
my original OS (Linux Mint 19.3, debian based). I was able to build and
generate the ISO file successfully using the standard configuration. Loaded the
ISO file into an USB using dd and it booted fine up to GRUB.
Unfortunately, I was not able to go further from GRUB and got identical
behaviour as before. Tried standard install, USB testing and troubleshooting
mode but non of these worked.

You mention that the video drivers might be included in Qubes 5.x- would you be
able to point me to building instructions for this? I was not able to find any
information on how to configure the building tool for version 5. I've only
followed the standard+stable configuration- do you know how to add the
necessary drivers as part of the building process?

Good work figuring out the builder. Took me a while. Anyways, meant a
Linux kernel 5.x, Qubes 5.x. It should be available in one of the Qubes
repos (testing?).

I came across this post https://www.qubes-os.org/doc/install-nvidia-driver/
which suggests a fix to issues with NVIDIA/AMD video drivers. I was hoping to
use this to built-in the necessary drivers into the Qubes 4.1 OS build but was
not able to get that far. Any ideas on how to do this?

Could be useful if you can figure out which version of the Linux kernel
includes video drivers for your Ryzen. If the 5.x one in Qubes repos
does, you might be in business.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/f448f665-60ec-8ad1-dbe2-34c2d5ebf08b%40danwin1210.me.

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

2020-02-16 Thread A E

søn. 16. feb. 2020 kl. 19.01 skrev Chris Laprise :

> On 2/16/20 10:32 AM, A E wrote:
> > søn. 16. feb. 2020 kl. 16.18 skrev Chris Laprise  > >:
> >
> > On 2/15/20 10:20 AM, A E wrote:
> >  > If it isn’t possible to change the settings of the screensaver
> that
> >  > Qubes OS is actually using, then I would like to hear how I can
> > either
> >  > disable or delete it in Qubes ?
> >
> > The setting to disable screensaver does work for KDE in dom0.
> Switching
> > to KDE has fixed a number of GUI problems for me.
> >
> > --
> > Chris Laprise, tas...@posteo.net 
> > https://github.com/tasket
> > https://twitter.com/ttaskett
> > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
> >
> >
> > Okay, how do I switch to KDE ?
> >
> > And what are the cons with switching to KDE... ?
> >
> > I shall probably mention that I’m a Linux and Qubes newbie.
>
> This guide only requires a few steps in the dom0 terminal:
>
> https://www.qubes-os.org/doc/kde/
>
> Make sure you also do the lightdm->sddm changes because lightdm is where
> some of the problems originate.
>
> The downsides to KDE are that it uses about 200MB more RAM (IMO, very
> much worth it) and the Network Manager applet icon appears blank (its
> still easy to use once you know its there in the systray).
>
> --
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
>

Okay, I have seen here (link: https://m.youtube.com/watch?v=fo45bo1jvZI )
that new versions of KDE uses less ram than XFCE.

Which version of KDE do you use in Qubes OS ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CABRRaUEj7t%2BmEkFBAsS81C6HjCuxJpRePAbJv5GfSAk6C5KCjw%40mail.gmail.com.

Re: [qubes-users] Reattaching firewall vm to untrusted vm without killing the untrusted vm.

2020-02-16 Thread pillule


On Sun, Feb 16 2020, billol...@gmail.com wrote:

> Qubes folk,
>
> So, I have a debian-based untrusted vm that is attached to a mullvad
> vpn through Sweden; the mullvad vpn gets its networking from sys-
> firewall (i.e. sys-net -> sys-firewall -> mullvad-vpn -> untrusted vm.
>
> I have another "local" vm that is directly attached to sys-firewall
> (i.e sys-net -> sys-firewall -> local vm).  Nothing other than sys-usb
> starts automatically on boot.
>
> The mullvad-vpn is a standalone vm, set up per the Qubes mullvad
> instructions, while the untrusted and local vms are based on the
> debian-10 template.
>
> I'm running Qubes release 4.0.2.
>
> When I change locations without rebooting the box and switch wireless
> networks, the sys-net, sys-firewall, and local vms automatically
> update.  Unfortunately, the mullvad-vpn vm does *not* update
> automatically.  In order to get networking on the untrusted vm, I have
> to kill it *and* the mullvad-vpn vm, and restart them -- which means I
> have to kill any running apps, which is a pain when I'm doing big image
> tasks in the background.
>
> Is there a way to tell a standaloneVM like my mullvad-vm to either
> update automatically, or a command to get it to re-set its networking
> to a changed sys-firewall vm?
>
> Thanks,
>
> billo

Hi,

You can switch the 'netvm' of any VM on the fly with Qubes Manager or
via command line
`[user@dom0 ~]$ qvm-prefs "vmname" netvm none`
then switch back when ready.

--


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/87r1yu5kkp.fsf%40host.localdomain.

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

2020-02-16 Thread Chris Laprise

On 2/16/20 10:32 AM, A E wrote:
søn. 16. feb. 2020 kl. 16.18 skrev Chris Laprise >:

On 2/15/20 10:20 AM, A E wrote:
> If it isn’t possible to change the settings of the screensaver that
> Qubes OS is actually using, then I would like to hear how I can
either
> disable or delete it in Qubes ?

The setting to disable screensaver does work for KDE in dom0. Switching
to KDE has fixed a number of GUI problems for me.

--
Chris Laprise, tas...@posteo.net

https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

Okay, how do I switch to KDE ?

And what are the cons with switching to KDE... ?

I shall probably mention that I’m a Linux and Qubes newbie.

This guide only requires a few steps in the dom0 terminal:

https://www.qubes-os.org/doc/kde/

Make sure you also do the lightdm->sddm changes because lightdm is where
some of the problems originate.

The downsides to KDE are that it uses about 200MB more RAM (IMO, very
much worth it) and the Network Manager applet icon appears blank (its
still easy to use once you know its there in the systray).

--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

Re: [qubes-users] Reattaching firewall vm to untrusted vm without killing the untrusted vm.

2020-02-16 Thread Chris Laprise

On 2/16/20 12:34 PM, billol...@gmail.com wrote:

Qubes folk,

So, I have a debian-based untrusted vm that is attached to a mullvad
vpn through Sweden; the mullvad vpn gets its networking from sys-
firewall (i.e. sys-net -> sys-firewall -> mullvad-vpn -> untrusted vm.

I have another "local" vm that is directly attached to sys-firewall
(i.e sys-net -> sys-firewall -> local vm). Nothing other than sys-usb
starts automatically on boot.

The mullvad-vpn is a standalone vm, set up per the Qubes mullvad
instructions, while the untrusted and local vms are based on the
debian-10 template.

I'm running Qubes release 4.0.2.

When I change locations without rebooting the box and switch wireless
networks, the sys-net, sys-firewall, and local vms automatically
update. Unfortunately, the mullvad-vpn vm does *not* update
automatically. In order to get networking on the untrusted vm, I have
to kill it *and* the mullvad-vpn vm, and restart them -- which means I
have to kill any running apps, which is a pain when I'm doing big image
tasks in the background.

Is there a way to tell a standaloneVM like my mullvad-vm to either
update automatically, or a command to get it to re-set its networking
to a changed sys-firewall vm?

This refusal to change in the mullvad vm could be due to a common
openvpn behavior where it tries to revive the current connection over a
5 minute period. This is good for a VPN server, but for a PC it will
look like it is unable to re-connect.

The Qubes-VPN-support tool sets a max openvpn timeout of 40 seconds; on
average it will re-connect in about 20 sec. after losing the old connection:

https://github.com/tasket/Qubes-vpn-support

--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

[qubes-users] Re: Reattaching firewall vm to untrusted vm without killing the untrusted vm.

2020-02-16 Thread billollib

As an aside, these are the instructions I used to set up the mullvad vpn.

https://mullvad.net/en/help/qubes-os-4-and-mullvad-vpn/

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/065c5aa6-d382-48a9-8ec0-8f3f02947ac0%40googlegroups.com.

[qubes-users] Reattaching firewall vm to untrusted vm without killing the untrusted vm.

2020-02-16 Thread billollib

Qubes folk,

I have another "local" vm that is directly attached to sys-firewall
(i.e sys-net -> sys-firewall -> local vm). Nothing other than sys-usb
starts automatically on boot.

The mullvad-vpn is a standalone vm, set up per the Qubes mullvad
instructions, while the untrusted and local vms are based on the
debian-10 template.

I'm running Qubes release 4.0.2.

Is there a way to tell a standaloneVM like my mullvad-vm to either
update automatically, or a command to get it to re-set its networking
to a changed sys-firewall vm?

Thanks,

billo

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/340a74a2-ed1b-4853-a22d-f111e65a1e98%40googlegroups.com.

Re: [qubes-users] Disk image backup - dd / partclone / clonezilla?

2020-02-16 Thread Chris Laprise

On 2/15/20 6:39 AM, General wrote:

Many thanks for your helpful reply Chris.

You also have to configure Qubes not to disable USB at boot time if

your boot drive is USB.

Ah, this is why it was not working for me! I shall try installing the OS
directly onto the USB drive and then make the clones from there. It
occurs that the USB isolation in Qubes is valuable and therefore running
a USB boot drive may not be sensible.

If backup speed is the main issue, take a look at Wyng

I have installed this in Dom0 and made a backup, also using your helpful
instruction:

file: /lib/systemd/system-shutdown/10_root_snapshot.shutdown
```
#!/bin/sh
/usr/sbin/lvremove --noudevsync --force -An qubes_dom0/root-autosnap || true
/usr/sbin/lvcreate --noudevsync --ignoremonitoring -An -kn -pr -s
qubes_dom0/root -n root-autosnap
```

to enable snapshots of the root volume.

Incremental backups are indeed very fast and this is what I was looking
for. I need to build another box to run a test restore procedure.
Perhaps this could be scripted now.

Thanks again.

Glad I could help!

FWIW, the root-autosnap is not strictly necessary since Linux does allow
snapshots to be taken of live LVs (e.g. you could point wyng to 'root'
and it would make its own snapshot of 'root' while it is live) but I
guess the above method is a bit safer.

Since Wyng doesn't yet handle Qubes config for individual VMs, restoring
a full Qubes system state with Wyng would require at least restoring
Qubes configuration (such as qubes.xml and firewall.xml) but that is
covered if you backup/restore the 'root' volume. OTOH, if your Qubes VM
settings are default or you made notes about them, then the xml files
aren't needed and you can restore the data volumes into freshly created
VMs (e.g. after reinstalling Qubes).

--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

Re: [qubes-users] Manual VPN installation issues

2020-02-16 Thread Chris Laprise

On 2/14/20 6:40 PM, 'e.sparks15' via qubes-users wrote:

Hello,
Sorry that this is a bit long, but I've been working on the problem for
awhile, and even though I've tried to give the most succinct explanation
I can of what I've tried so far, it still takes up some space.

I'm attempting to install expressvpn in a qube designated specifically
for that purpose. When I try to install it manually as per the
instructions in step two of the Qubes VPN documentation
, but the config files I
can get from expressvpn don't seem to be in that format. I tried using
their manual config process instead, but it's for ubuntu, and since I'm
a total linux newb I wasn't able to figure out how to convert it.

I did get as far with express' config as to get the config files in the
right place so that I had a vpn connection listed in network manager but
it can't connect, probably because when i tried 'sudo dnf-install
network-manager-openvpn-gnome' it always said that
network-manager-openvpn-gnome was not a valid target. I then contacted
expressvpn's tech support and they asked me to reboot and try again.
When I did, I found that everything had disappeared. I found some stuff
online about a bug on Fedora 24 with non-persistence, but that was
awhile ago and it doesn't seem to apply.

That sounds like you installed to an AppVM instead of a template; that
can make something you installed disappear. In Qubes, you would go into
the template to have an app installation persist, but for user data to
persist you would add it to an AppVM.

There are two things I'll add that might be helpful to people smarter
than me. First, I've been getting the following error on startup since I
last performed upgrades:

Also, I haven't been able to perform any upgrades since then.

And second, it seems like there are a couple of different places that
talk about vpn setup. The documentation above, expressvpn's page, and
more Qubes documentation . I think
I've kept them all separate and not done myself in by combining multiple
methods, but at this point I'm not sure.

Thanks so much for taking the time to read! I greatly appreciate it, and
if you can think of anything I should try, I'd greatly appreciate you
letting me know that, as well!

There are two expressvpn links you should look at, which correspond to
the two different configuration methods you can choose from in the Qubes
vpn doc. The first is using Network Manager, and the second is for using
shell scripts:

https://www.expressvpn.com/support/vpn-setup/manual-config-for-linux-ubuntu-with-openvpn/

https://www.expressvpn.com/support/vpn-setup/manual-config-for-linux-with-openvpn/#download

If the process seems too complicated, you can try my VPN support tool,
which automates most of the steps (you would download the config files
from the second link to use with this):

https://github.com/tasket/Qubes-vpn-support

--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

2020-02-16 Thread A E

søn. 16. feb. 2020 kl. 16.18 skrev Chris Laprise :

> On 2/15/20 10:20 AM, A E wrote:
> > If it isn’t possible to change the settings of the screensaver that
> > Qubes OS is actually using, then I would like to hear how I can either
> > disable or delete it in Qubes ?
>
> The setting to disable screensaver does work for KDE in dom0. Switching
> to KDE has fixed a number of GUI problems for me.
>
> --
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
>

Okay, how do I switch to KDE ?

And what are the cons with switching to KDE... ?

I shall probably mention that I’m a Linux and Qubes newbie.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CABRRaUGhoKXDETHbhEXjW%3DW7cRX_V7bRnGBwi%3DSiP2BMkEFrSw%40mail.gmail.com.

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

2020-02-16 Thread Chris Laprise


On 2/15/20 10:20 AM, A E wrote:
If it isn’t possible to change the settings of the screensaver that 
Qubes OS is actually using, then I would like to hear how I can either 
disable or delete it in Qubes ?


The setting to disable screensaver does work for KDE in dom0. Switching 
to KDE has fixed a number of GUI problems for me.


--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ccbf8322-a585-738b-560d-6a957f0e2e1e%40posteo.net.

Re: [qubes-users] How to install and get Linux Mint running in Qubes OS 4.0.3 ?

2020-02-16 Thread unman

On Sun, Feb 16, 2020 at 08:16:59AM +0100, A E wrote:
> s??n. 16. feb. 2020 kl. 02.50 skrev unman :
> 
> > On Sat, Feb 15, 2020 at 07:50:53AM -0800, A wrote:
> > > 1)  How to install and get Linux Mint running in Qubes OS 4.0.3 ?
> > >
> > Download a mint iso in to a qube - make sure you have enough space to do
> > this - up Private storage size if needed.
> >
> > Create an HVM and boot it from a Mint iso. (Instructions on this can be
> > found here - https://www.qubes-os.org/doc/standalone-and-hvm/ )
> > Or use the GUI - in Qube Manager, select Qube - "Create New qube".
> > Give it name and set type "Empty  Standalone qube.."
> > Select "open Settings after creation."
> > In Settings window go to Advanced pane and set initial memory to 4000MB
> > - you can always reduce after installation.
> > Then select "Boot qube from CDROM" button, and select the qube where you
> > downloaded the Mint iso.
> > On start you should see Mint boot in live mode.
> > Note the IP address of the new mint qube (either from Qube Manager , or
> > using `qvm-ls -n `
> > Edit the Network settings for ipv4 to "manual" and enter the IP address
> > and gateway. For DNS you can use 9.9.9.9
> > Select option to install to disk.
> >
> > After installation, shutdown the qube.
> > Restart.
> > Your new Mint qube should start up.
> > If you get a black screen, kill it. In terminal in dom0 , use
> > `qvm-features  video-model cirrus` and restart.
> >
> > Since Mint is based off Ubuntu, you can try installing some qubes
> > packages built for Ubuntu , to et copy/paste etc working. (I have
> > packages at qubes.3isec.org you could try, but I haven't tested this
> > myself - i suggest you get Mint running properly, then clone it and try
> > installing packages in to the clone.)
> >
> > > 2)  Is it possible to use Linux Mint for surfing the net in a secure
> > way, and if so how ?
> > >
> >
> > ???
> >
> > --
> > 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/jBHgC2TFggY/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> > qubes-users+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/qubes-users/20200216015008.GA8620%40thirdeyesecurity.org
> > .
> >
> 
> Thank you very much for your detailed guide.
> 
> Just to be sure: Shall I create the new qube the same way if I install
> Linux Mint from a DVD ?
> 

If you can pass through the DVD to the `qvm-start` commadn, yes.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200216145606.GA11221%40thirdeyesecurity.org.

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

2020-02-16 Thread 'aihey' via qubes-users

> Have you tried to installing Qubes OS 4.1 both in UEFI and in legacy mode 
> without success... ?

Yes, tried both UEFI and legacy modes and both of these failed. Only difference 
was the GRUB dialog- in UEFI was black+white and in legacy with a blue coloured 
background.


‐‐‐ Original Message ‐‐‐
On Sunday, 16 February 2020 11:46, A  wrote:

> Have you tried to installing Qubes OS 4.1 both in UEFI and in legacy mode 
> without success... ?
>
> ---
>
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/b92997ad-c856-4da7-8527-10843e7b2091%40googlegroups.com.


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/MvKE1RlxeeaLdoqbA7hWW_JG-aKtXWG8dgvg9eEvwuWq-R3XSzedQrUPpntoSjhOkLsw2PIRsqeLQ7pA-zoToN_fmt4sWSxLnuwtvrsviZQ%3D%40protonmail.com.

Re: [qubes-users] Re: Tor not connecting over DSL

2020-02-16 Thread Anil

Tor in sys-whonix doesn't know or care what kind of Internet connection
> sys-net is using. If you use some other computer not running Qubes, can
> Tor connect over that same DSL? You might be getting blocked upstream.
>

Looking at the logs, it seems to be related to swdate, although the date
command output is correct and the correct date is displayed on the taskbar.
Sometimes there is an error about time synchronization. It could also be
related to the DSL modem settings, as the same connection with an older
modem was working on the same computer with the same Qubes installation. I
tried various things in the DSL modem settings, but since I don't know what
kind of problems occur with DSLmodem, I don't really have an idea about
what to change. The new modem anyway has very settings, whereas the older
modem had a lot of settings which could be changed. That was a probably
used modem given to me and it was pre-configured. I don't have another
computer with Qubes installed.

The new modem does not show the correct date when I select automatic time
update in the settings, but when I deselect it, it doesn't show any date or
time. This is why I think it may be related to time settings.


> >> By the way, even with other internet connections, when I try to connect
> to
> >> connect to Tor with the Connection Wizard, it always says Unknown
> Bootstrap
> >> Tag and please report it. Does that indicate some problem?
>
> Not sure which wizard you mean, but I don't see that on mine.
>

The Anon Connection Wizard in sys-whonix. It was there by default on my
every installation.

-- 
अनिल एकलव्य
(Anil Eklavya)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAPfsu8ebeKWNeK44AVHLOBMMdA8WNmhpL6gghD8spuLVwp5Sg%40mail.gmail.com.

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

2020-02-16 Thread A

Have you tried to installing Qubes OS 4.1 both in UEFI and in legacy mode 
without success... ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b92997ad-c856-4da7-8527-10843e7b2091%40googlegroups.com.

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

2020-02-16 Thread 'aihey' via qubes-users

> Looks like your Dell is a Ryzen with integrated AMD graphics, correct?

that's right: it's a AMD Ryzen 5 3500U with Radeon Vega Mobile

> Don't think the kernel included Qubes 4.0.3 has video drivers for it. To 
> confirm, you could try to install in text mode and see if you get further. 
> You should be able to switch to a terminal session (ctrl-alt-F2?) during 
> install to see the temporary logs.

I'm only able to get a bit further with a bunch of different tricks which I've 
described in my original post. The ctrl-alt-F2 during install has not worked 
for me.

> If text mode does get further, you might need to build a custom ISO with the 
> latest 5.x kernel to get the video drivers. There are also test builds of 
> Qubes 4.1 you can try. Believe they include 5.x as well.

I spent a yesterday afternoon looking into this. I built Qubes 4.1 (stable 
version) following the instructions in 
https://www.qubes-os.org/doc/qubes-builder/. I did this on the actual machine 
and had to re-install the OS with Fedora 31 as the building tool didn't support 
my original OS (Linux Mint 19.3, debian based). I was able to build and 
generate the ISO file successfully using the standard configuration. Loaded the 
ISO file into an USB using dd and it booted fine up to GRUB.
Unfortunately, I was not able to go further from GRUB and got identical 
behaviour as before. Tried standard install, USB testing and troubleshooting 
mode but non of these worked.

You mention that the video drivers might be included in Qubes 5.x- would you be 
able to point me to building instructions for this? I was not able to find any 
information on how to configure the building tool for version 5. I've only 
followed the standard+stable configuration- do you know how to add the 
necessary drivers as part of the building process?

I came across this post https://www.qubes-os.org/doc/install-nvidia-driver/ 
which suggests a fix to issues with NVIDIA/AMD video drivers. I was hoping to 
use this to built-in the necessary drivers into the Qubes 4.1 OS build but was 
not able to get that far. Any ideas on how to do this?

Many thanks for your suggestions!

‐‐‐ Original Message ‐‐‐
On Wednesday, 12 February 2020 15:58, 'awokd' via qubes-users 
 wrote:

> 'aihey' via qubes-users:
>
> > Unfortunately this has not worked for me but thanks for your suggestion.
> > Does anyone happen to know if the installation messages are saved 
> > somewhere? I would like to find out what triggers the installation to 
> > freeze (it all happens very quickly before it goes blank).
> > ‐‐‐ Original Message ‐‐‐
> > On Tuesday, 11 February 2020 13:11, fiftyfourthparal...@gmail.com wrote:
> >
> > > My Dell is newer and simply doesn't have legacy boot. I know that the 
> > > altered parameter is used during boot because it was the only thing I 
> > > changed to make my installations turn from failures to successes.
>
> Looks like your Dell is a Ryzen with integrated AMD graphics, correct?
> Don't think the kernel included Qubes 4.0.3 has video drivers for it. To
> confirm, you could try to install in text mode and see if you get
> further. You should be able to switch to a terminal session
> (ctrl-alt-F2?) during install to see the temporary logs.
>
> If text mode does get further, you might need to build a custom ISO with
> the latest 5.x kernel to get the video drivers. There are also test
> builds of Qubes 4.1 you can try. Believe they include 5.x as well.
>
> --
>
> -   don't top post
> Mailing list etiquette:
>
> -   trim quoted reply to only relevant portions
> -   when possible, copy and paste text instead of screenshots
>
> --
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/b1273a0d-453d-15d2-9f89-e57a2cdd47da%40danwin1210.me.
>

-- 
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 view this discussion on the web visit

Re: [qubes-users] Re: Tor not connecting over DSL

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

Re: [qubes-users] Reattaching firewall vm to untrusted vm without killing the untrusted vm.

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

Re: [qubes-users] Reattaching firewall vm to untrusted vm without killing the untrusted vm.

[qubes-users] Re: Reattaching firewall vm to untrusted vm without killing the untrusted vm.

[qubes-users] Reattaching firewall vm to untrusted vm without killing the untrusted vm.

Re: [qubes-users] Disk image backup - dd / partclone / clonezilla?

Re: [qubes-users] Manual VPN installation issues

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

Re: [qubes-users] How to install and get Linux Mint running in Qubes OS 4.0.3 ?

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

Re: [qubes-users] Re: Tor not connecting over DSL

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

Re: [qubes-users] Re: failed Qubes 4.0.3 install on Dell Inspiron 14 5485

17 matches

Site Navigation

Mail list logo

Footer information