[qubes-users] Re: Dual screen

['Slideshowbob' via qubes-users]

 Original Message 
Subject: [qubes-users] Re: Dual screen
Local Time: May 24, 2017 3:03 PM
UTC Time: May 24, 2017 1:03 PM
From: mfree...@zoho.com
To: qubes-users@googlegroups.com

On 05/15/2017 01:13 PM, Mathew Evans wrote:
> change settings with xrandr or gdk-screensettings.

Agree. On my hardware, I found that xrandr worked well, and
xfce4-display-settings didn't. See:

https://groups.google.com/forum/#!msg/qubes-users/DkTLbWxIkQI/UxR-X6RZAAAJ

arandr works (mostly) fine for me (needs a qubes-dom0-update arandr first). 
Could never figure out the args for xrandr :).

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/vGCEbzDrGTHSrJdVVIqydwgd21xhB2B2Uot285QSi6Iofo1fDzywk6X0QKpQi8i1e64nMOGx6dzEp8OF2BK_Hp9o3RUTRWBtfIxXyWR_g3I%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Why is there no built-in nvidia driver support? aka GTX 980 issues

['Slideshowbob' via qubes-users]

 Original Message 

Subject: [qubes-users] Re: Why is there no built-in nvidia driver support? aka 
GTX 980 issues
Local Time: March 8, 2017 11:58 PM
UTC Time: March 8, 2017 10:58 PM
From: rkny...@nymantechnology.com
To: qubes-users 
almightyl...@gmail.com

Did this ever get resolved? I am fighting this very battle. I'm assuming that 
trying to hack through anaconda JUST TO GET THE INSTALLER TO WORK is a waste.

Is there something I can try? How can I help?

=rk=

I had lots of weird errors and a non working installer, too. Booting using 
nouveau.modeset=0 made all my issues go away. Worth a try :).

ssb

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dWMc4j2yqNwyZD_B_TCnLp6wg7INl83-Lu6r5XJH84mYp-0Ohpmtm7LFo0K8KdaH1IzKqjh-q0GE9FRp8yo90RB62jIEvTo1ugEBSu0yXcc%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: sys-net stopped working after update

['Slideshowbob' via qubes-users]

 Original Message 
Subject: Re: [qubes-users] sys-net stopped working after update
Local Time: February 28, 2017 10:27 PM
UTC Time: February 28, 2017 9:27 PM
From: va...@statfact.org
To: qubes-users  va...@statfact.org, 
tas...@openmailbox.org

It starts. But there is no ip resolution.

(resent because I forgot to CC qubes-users)

You could try to create a new net-vm, assign your network hardware and start 
this instead. Maybe it's some incompatability with the config files. If it 
works, set it as standard net-vm.

Another thing you could try is: before shutting down your net-vm, right-click 
on the NetworkManager applet and untick "Enable Networking". I have to do this 
when I'm in one specific wlan, because otherwise after a restart of the net-vm 
I won't get an ip assigned (no clue why but this reliable solves the issue for 
me).

slideshowbob

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ywGvX4uf0BB-HvR7LdEAMVurHStDCc1qvE4N8P-3sQeIv1s-jENSOoVY0G1xNeUS-rPVzpjYHNoJegKMh9RmWL6T1a_zmw-ph92SdEUBYkg%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Kernel issues preparing for 3.1 - 3.2 Upgrade

['Slideshowbob' via qubes-users]

 Original Message 

Subject: [qubes-users] Kernel issues preparing for 3.1 - 3.2 Upgrade
Local Time: March 1, 2017 10:46 AM
UTC Time: March 1, 2017 9:46 AM
From: qubes-users@googlegroups.com
To: qubes-users@googlegroups.com 

I've always had difficulties booting the default kernel of 3.1 (4.1.24.10), 
graphic corruption making it impossible to complete a boot. As such I've just 
always used 3.18.17-8 which behaves fine on my hardware.

Am now preparing to make the upgrade to 3.2, but want to ensure if at all 
possible there is a kernel that will boot before I do. Is it possible / logical 
to test the same kernel version that will be available / default with 3.2 on 
3.1 or is it much more a suck-it-and-see if it sucks sort of situation?

Thanks


I'd recommend you make a test installation on a usb stick (needs 32 GB or 
bigger). I could not run 3.2 on my pc and having it on usb gives you time to 
fix the issues (if there are any) without having a non working pc. Oh and of 
course don't forget to make backups.

slideshowbob

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4yckQ7jUlPVZY36OzTTMla8EUixRVRXratElteoh_6kWJFzrqJ0Bbi_KbEPgpBtiltjfjJrVtFs4KX8BUksN6DAGHya976eEMujWFB0tZuw%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Disable sys-net autostart?

['Slideshowbob' via qubes-users]

 Original Message 

Subject: Re: [qubes-users] Disable sys-net autostart?
Local Time: February 24, 2017 2:16 AM
UTC Time: February 24, 2017 1:16 AM
From: un...@thirdeyesecurity.org
To: Slideshowbob <slideshow...@protonmail.ch>
qubes-users@googlegroups.com <qubes-users@googlegroups.com>

On Thu, Feb 23, 2017 at 01:13:40PM -0500, 'Slideshowbob' via qubes-users wrote:
> Hi,
>
> is there a way to disable autostart for sys-net? Unticking the checkbox 
> (including VMs which might trigger a sys-net start) doesn't work. Also, what 
> are the security implications of doing this? Would network devices not in use 
> by sys-net appear in dom0?
>
> I'm trying to upgrade from 3.1 to 3.2 since the first RCs but the new version 
> somehow behaves bat shit crazy on my system (6440HQ, I/O MMU and HAP/SLAT 
> active on 3.1). As this is my main system and support for 3.1 comes to an end 
> soon I finally need to find a solution somehow.
>
> I was able to install und boot 3.2 by not creating the standard VMs in the 
> post installer setup tool. I created the sys-net VM manually and was able to 
> start/stop it without issues.
>
> Since I created the net VM I'm unable to boot anymore. It hangs during the 
> sys-net startup. The error message I get after a few minutes is:
>
> BUG: soft lockup - CPU#1 stuck for 22s! [libvirtd:1769]
>
> Anyone knows how to debug or fix this? The VM worked fine when started after 
> the system was fully booted, it just fails if started during booting.
>
> Greets,
>
> slideshowbob
>

There are a couple of open issues about this autostart issue.

The simplest solution is to disable the auto start in
/etc/systemd/system/qubes-netvm.service - you can edit the file or
disable the service. If you do make sure that you aren't starting any
other qubes that rely on sys-net. (That would include your clockVM.)
That way at least your Qubes will start up and then you can start the
individual qubes.
If you cant boot at all, you should be able to boot from a live distro,
mount the drive and edit that file in place.

Hope this helps

unman

Thanks for your response!

Would the hardware assigned to the net VM gain access to dom0 by disabling 
autostart?

I've got some noobish questions about that part of the security concept, maybe 
someone could explain that:
Is a pci device in dom0 able to do bad stuff if there's no driver loaded in 
dom0 using the device (I'd assume yes)?
How is dom0 protected from malicious pci devices during the time frame between 
starting xen and starting the related net VM?
I just noticed that lspci (in dom0, v3.1) shows the device which is currently 
assigned to my running net VM. Is that supposed to be the case? Are there xen 
commands to show which pci devices are actually active and which VMs they're 
assigned to?
While writing this I noticed there's 'xl pci-assignable-list'. Are those the 
currently non active pci devices?

On a side note, I'm currently still on 3.1, the 3.2 installation is on a usb 
stick for testing purposes. I want to solve all issues before I make the switch 
(can't have the main system in a broken state for long). Some time ago I made a 
regular 3.2 installation to hard disk and had the same issue so I assume it's 
not related to the usb installation.

slideshowbob

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ufWTP-w1O9FvAURK_61ft0JTHPK7o6m_0LdHemlaDGCmi6dhk50qEibYNdoATzPIwoRQcrWXOaH29Mp7J_mwI-OJRtX0-3PG3yaJBqAnmqg%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Disable sys-net autostart?

['Slideshowbob' via qubes-users]

Hi,

is there a way to disable autostart for sys-net? Unticking the checkbox 
(including VMs which might trigger a sys-net start) doesn't work. Also, what 
are the security implications of doing this? Would network devices not in use 
by sys-net appear in dom0?

I'm trying to upgrade from 3.1 to 3.2 since the first RCs but the new version 
somehow behaves bat shit crazy on my system (6440HQ, I/O MMU and HAP/SLAT 
active on 3.1). As this is my main system and support for 3.1 comes to an end 
soon I finally need to find a solution somehow.

I was able to install und boot 3.2 by not creating the standard VMs in the post 
installer setup tool. I created the sys-net VM manually and was able to 
start/stop it without issues.

Since I created the net VM I'm unable to boot anymore. It hangs during the 
sys-net startup. The error message I get after a few minutes is:

BUG: soft lockup - CPU#1 stuck for 22s! [libvirtd:1769]

Anyone knows how to debug or fix this? The VM worked fine when started after 
the system was fully booted, it just fails if started during booting.

Greets,

slideshowbob



Sent with [ProtonMail](https://protonmail.com) Secure Email.

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/aUm9t8LhDo46ODVHlsyd2XFy06VV8chxIxb-bOE6BJKnSHJHpDd9LLvWsvEG0KSva3Ei7CTS4UsI4bqWlOXl64Ybxe8SDfHb0gN5XuXirmQ%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: !! GREETINGS !!!

['Slideshowbob' via qubes-users]

 Original Message 
Subject: Re: [qubes-users] !! GREETINGS !!!
Local Time: 23. Februar 2017 2:10 PM
UTC Time: 23. Februar 2017 13:10
From: un...@thirdeyesecurity.org
To: qubes-users 

On Thu, Feb 23, 2017 at 03:40:44AM +, hassan karam wrote:
> Hello
>
> I am Mr. Hassan Karam, from Syria due to brutal civil war in my country, I am 
> seeking your
> partnership in going into a private investment venture. I am interested in 
> investing in your
> country, so I will like us to begin our acquaintance through this medium so 
> we can deliberate
> more.I hope to hear from you soon thanks.
>
> Yours faithfully,
> Hassan Karam
>

Is this part of the Qubes commercialization program?

lool

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/QLTz6zAyIdo2WAC8GvYMzpJtPzE_DlHE_F_6tF5_MAatJd7CHIZ3H95OIdIZsOQcm2ptgKSA8Xm7bSGHfjeh_2x8crJaM1VQudAqmMWex7E%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [Qubes R3.1] Installation problem: "NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s!"

['Slideshowbob' via qubes-users]

 Original Message 
Subject: [qubes-users] Re: [Qubes R3.1] Installation problem: "NMI watchdog: 
BUG: soft lockup - CPU#2 stuck for 22s!"
Local Time: 22. November 2016 3:48 PM
UTC Time: 22. November 2016 14:48
From: th.revi...@gmail.com
To: qubes-users 

On Saturday, May 14, 2016 at 1:48:37 PM UTC+3, Danny Eagle wrote:
> Full error message:
> [5578494253.737246] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! 
> [NetworkManager: 1057]
>
> After choosing "Install Qubes" option this message pops up.
> I'm installing it on desktop not laptop.
>
> If i take "Check hardware and install Qubes" I get to second window and it 
> freezes.

Same bug here. Sometimes it says CPU#2, sometimes CPU #5. I algo get [Xorg 
1224] at the end.

It's a more recent Asus laptop with Core i7 6700HQ (Skylake) CPU. I should also 
mention that when I get the installation menu it says "processing" for 
installation source, and when I select it, it only gives me options for DVD, 
local iso, an network install - but I'm trying to install from a USB. What's up 
with that? The installation did boot from the USB and I chose DD mode in Rufus.

I have that CPU stuck bug, too. But only on R3.2, R3.1 works fine for me. CPU 
is i5-
6440HQ.

-- 
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 qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/YSqrIkv1bVrjSM3JCSkzPKOurekNRxYjZea4iXVhDQPIiKg6ihb30vIkkfuae2G_0iqeUe9FYHQwwSfCrqh_hN7B5quqt44GeGJQEXkgKOk%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.