[qubes-users] Re: Window VM disappear when dont use

2017-06-13 Thread Mathew Evans
On Friday, 9 June 2017 03:39:26 UTC+1, phongx...@gmail.com  wrote:
> hi every one, i'm using Win7 64 bit in Quebe, I have a case that when i dont 
> use the VM in 15-20 min, window VM disappear and i cant find this vm anymore, 
> i have to restart vm or kill it to reuse it. Any one have solution for my 
> problem? Thank you

This issue stopped for me when i enabled debug mode for the HVM.

-- 
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/2f10e267-880a-4776-b087-464c76b53208%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Dual screen

2017-05-15 Thread Mathew Evans
change settings with xrandr or gdk-screensettings.

-- 
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/3b482613-5ff0-49c6-b86e-e7ab2dd32af3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] USB Hubs + sys-usb

2017-05-14 Thread Mathew Evans
Ive been using qubes for quite a while. Recently i wanted to pass my USB-Sound 
device to a appVM, which is located within a Powered Hub. I noticed that 
qvm-usb didn't display it at all. But a USB Storage device was accessable via 
the qubes-manager to attach to a appVM.

---
Location of issue:
/usr/lib64/python2.7/site-packages/qubes/qubesutils.py

lines: 472 , 473

usb_device_re = re.compile(r"^[0-9]+-[0-9]+(_[0-9]+)?$")
usb_port_re = re.compile(r"^$|^[0-9]+-[0-9]+(\.[0-9]+)?$")

As a temporary fix I replaced the above lines with:
  
usb_device_re = re.compile(r"^[0-9]+-[0-9]+(_[0-9]+)+$")
usb_port_re = re.compile(r"^$|^[0-9]+-[0-9]+(\.[0-9]+)+$")

---

Now devices in a powered USB-Hub show up for me as.
2-1.1.1.1 -> 2-1.1.1.6 (first hub)
3-1.1.1.1 -> 3-1.1.1.4 (2nd hub)

Hopefully this is of help to someone else and Devs can look after a more 
permanent fix for this issue. Additionally some Microsoft USB devices include 
the registered symbol in the USB Desc text, this causes qvm-usb to fail to 
display at all.

Issue is in same file as before but on line 474, temp fix for anyone with such 
issues replace [ -~] with [ -~(\x20-\xE0)] kinda defeats the purposes of the 
usb_desc_re regex but atleast they display with qvm-usb now.

-- 
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/5bf0b034-5886-4a5e-b140-bb27d19ee445%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: GPU passthrough: 2000 USD bounty

2017-04-22 Thread Mathew Evans
Biggest issue that limits you with nvidia is the fact that drivers detect that 
it is running in a VM / HVM etc.. It is possible to get nvidia drivers 
installed into Qubes (dont recommend it) and then you can pass a prime device 
through to a app VM with little issue. Ive done this for doing cuba-cat for 
password cracking and it works but you wont get any output on the screen at 
all. (goto dump to file) 

Would love to play games on Qubes though. implenetation of OpenGL for the Qubes 
GFX driver would go a very very long way.

-- 
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/fe1cec66-d729-4d0a-9be6-004ed041fb16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: M.2 SSD Not recognized as a bootable device

2017-04-22 Thread Mathew Evans
On Wednesday, 12 April 2017 23:30:51 UTC+1, mystre...@gmail.com  wrote:
> Hello, i hope you can help me.
> After I install Qubes to the SSD and reboot, it does not recognize the SSD as 
> a bootable device. Using the same install procedures on another SSD (SATA), 
> everything works fine. When using Qubes from the SSD (SATA) to access the M.2 
> SSD, the BOOT file is empty, so there are no files to rename as you've 
> directed in the UEFI troubleshooting. Also, I cannot access the /BOOT/EFI/ 
> file on my SSD (SATA), it says I don't have the required permissions.
> I have also compared the Partitions from my M.2 SSD and the other SSD and 
> they are the same. 
> M.2 SSD PARTITIONS: http://imgur.com/a/GPCYh
> SSD PARTITIONS: http://imgur.com/a/QIzph

You likely have a marvell based m.2 SSD they have a issue with EFI mode.
I add the following to my xen.cfg to get it to show up.

pci-phantom=00:00,2 

This is a know issue with XEN and marvell m.2 SSDs in EFI mode.

-- 
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/2e102df8-f008-4e6a-b0b2-a33d62b15bf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Nvidia drivers in dom0 still works? (need to get a GTX 1070 off the ground)

2016-12-18 Thread Mathew Evans
Just to update.

I am currently running Nvidia drivers without a issue.

dom0 Kernel: 4.4.31-11
Nvidia: 375.20
Kernel-module: compiled in dom0; 

Quick Guide:
1. dom0:   qubes-dom0-update install gcc devel-kernel ksmod linux-headers
2. appvm:  download NVIDIA-Linux-375.20-install.run (any appvm)
3. dom0:   qvm-run --pass-io  'cat /PATH/TO/NVIDIA.run' > NVIDIA.run
4. dom0:   ./NVIDIA.run --ui=none --no-x-check --keep --extract-only 
5: dom0:   cp NVIDIA-*/kernel/;  IGNORE_XEN_PRESENCE=y CC="gcc 
-DNV_VMAP_4_PRESENT -DNV_SIGNAL_STRUCT_RLIM" make module;
6: dom0:   cp nvidia.ko /lib/modules/4.4.31-11.pvops.qubes.x86_64/extra/.
7: dom0:   depmod -a; modinfo nvidia (all working will show up fine)
8: dom0:   EDIT GRUB or EFI; add rd.driver.blacklist=nouveau
9: dom0;   reboot and enjoy nvidia support.

additional: you can install nvidia extra apps etc.. if you so wish just run 
./nvidia.run --no-kernel-module -a


Hopefully this will help those of you wanting Nvidia driver instead of Nouveau.
Please note this is a ruff write up and guide not a perfect solution, and 
assumptions are made that you are always fimilar enough with *nix operating 
systems to figure out that parts i've missed out or aint put in detail.

-- 
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/5821c9b3-27a8-4853-9933-1a6e406bef57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Why it so big secret?

2016-10-12 Thread Mathew Evans
On Tuesday, 11 October 2016 23:37:33 UTC+1, Desobediente  wrote:
> Additionaly, the Bumblebee howto is here: 
> https://fedoraproject.org/wiki/Bumblebee

There is nothing new about these and frankly anyone could have found them via 
google just looking, if you managed to get Nvidia working on Q3.2 id be 
interested. my experience hasn't been successful. Ive had issue with XOrg with 
Nvidia drivers being unable to find my screens.

-- 
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/5e2684d3-a161-4e61-aeb3-ada27150108e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] [Q3.2] Fn keys stopped working.

2016-10-11 Thread Mathew Evans
I've used qubes for quite a while not and had no issues with my Fn (function) 
keys working as should do until the Qubes 3.2 release, all the release 
candidates they worked perfectly fine. Ive checked with xev in dom0 and they 
are not even detected as XF86 keys so i cant even manually map them in i3 
config.

Any ideas at all would be helpful.

Laptop: Clevo P650

-- 
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/8a036b8c-6b5f-4c43-9cff-b76a1179cf8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HVM Windows

2016-10-06 Thread Mathew Evans
On Thursday, 6 October 2016 10:30:19 UTC+1, asdf...@sigaint.org  wrote:
> Hello
> When I send a file from a appVM to windows HVM, where does it go?
> I'm searching but I don't find it
> 
> Thank you

Check your user folder, should be in there or in documents. will be in a folder 
call QubesIncoming.

-- 
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/490f31be-24ec-4b5f-9945-de1fca25742b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Why won't Google Chrome remember my Google logins?

2016-09-26 Thread Mathew Evans
On Sunday, 25 September 2016 15:33:35 UTC+1, Clark Venable  wrote:
> On Sunday, September 25, 2016 at 8:42:08 AM UTC-4, Clark Venable wrote:
> > Nope. Allow local data to be set is enabled.
> 
> It all works as I expect in Firefox, So I'm happy to leave this alone and 
> just use Firefox rather than Chrome (which is probably what the devlopers 
> intended by including Firefox in the distro. :-)

I can confirm i had the same issue with Chrome. There is somthing funky going 
on between seahorse and chrome and how in the AppVMs details are stored. As 
long as you do not restart the AppVM you can close and reopen chrome as many 
times as you want and it will work fine, even with disable background 
processes. when you restart the AppVM the info in seahorse seams to expire 
instantly.

-- 
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/697a0a56-b0fc-4bf0-a256-f6f3fdf973ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes + Synergy.

2016-09-20 Thread Mathew Evans
Long story short I'd like to share my keyboard and mouse from my Qubes 
environment to a windows environment (physically different machine) with 
synergy. Any ideas of best way to achieve this? short of adding networking to 
dom0 which I'm not willing to do.

-- 
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/8636f41b-e044-43dc-acc1-aa8d24ec8b01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] [3.2RC1] i3wm bad performance.

2016-07-17 Thread Mathew Evans
I'm getting the feeling the issue might be a lack of nvidia graphics drivers.

TLDR version:

 - Installed i3 and i3-settings-qubes
 - configured .config/i3/config how i wanted it.
 - anything CLI works perfectly fine.
 - anything GUI will render very very slowly, you can see it rendering as it 
goes down the screen.

No idea why the horrible performance, my only thought my laptop has a nvidia 
980m gpu and it isn't being used at all. IF the performance issue is likely a 
lack of nvidia drivers, is there a updated guide to install it (current one is 
outdated, xorg-x11-drv-nvidia seams to be missing for fedora23 with rpmfusion)

as a second question, is there a timeframe for Qubes to ship with improved 
nvidia support?

-- 
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/ed2e7cb7-af0d-4895-98cd-896fb592fea0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] [3.2RC1] HCL - Clevo - P65_P67SG

2016-07-11 Thread Mathew Evans
Worked perfectly with 3.1 without a issue upgraded to 3.2 to test so far no 
issues at all. No AEM due to lack of kernel support for the TPM.

Due to a marvell m.2 chipset for one of the SSDs you need to add 
pci-phantom=02:00,1 to the xen.cfg on the installer and in the boot partition 
of the hard disk (or just dont use a marvell m.2 ssd).

Additionally 3.2RC1 sets dom0 max memory to 4GB on install. removed min and max 
values in Xen boot options.

Working:
 - Wifi
 - Ethernet
 - Sound
 - Graphics
 - TouchPad
 - FN Keys

Issues:
Laptop gets very hot in sleep mode.

Not Working:
Kernel support for TPM [pcrs devices missing]

-- 
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/2b138695-d362-4e85-8fe5-4670bf234ddf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Clevo-P65_P67SG___-20160711-122928.yml
Description: Binary data


[qubes-users] Qubes-OS 3.2 RC1 : General.

2016-07-10 Thread Mathew Evans
I've got 3.2 RC1 to install and boot with UEFI perfectly fine. edited xen.cfg 
in /boot/efi . added pci-phantom= [due to a marvel m.2 ssd] and 
removed the 4Gb memory limit for dom0.

I'd like to try some of the new features, not limited to but including the i3 
tile window manager. IS there any documentation about how to activate them etc..

Additionally where did the screen resolution change option? resorted to using a 
couple of command line options instead, also thought newest KDE with 3.2RC1 was 
expected to scale on 4k better. worked flawless on the installer but stopped 
once booted up and logged in.

-- 
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/8262e19a-6f64-4651-8233-ec5c6ef6889d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.