[qubes-users] Re: Why is there no built-in nvidia driver support? aka GTX 980 issues
On Saturday, April 8, 2017 at 3:26:58 AM UTC+9:30, john.c...@ucdconnect.ie wrote: > On Friday, 16 September 2016 08:09:46 UTC+1, almigh...@gmail.com wrote: > > Qubes was working flawlessly on my GTX 670, recently upgraded to a GTX 1070 > > and now I can't even load the installer > > What drivers did you install for the 670? > > I'm on a 660 atm, and haven't installed any drivers, but am getting screen > tearing when fullscreening netflix/youtube. No particular drivers, everything works (is usable) from the start. I've never tried watching videos using Qubes before so I can't really suggest anything. -- 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/186f5d0a-d0f3-4682-b0bc-0a5003ca9ec9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] What decides which VM is the FirewallVM?
On Sunday, January 1, 2017 at 2:21:49 PM UTC+10:30, WillyPillow wrote: > In short, there's not really an "one and only FirewallVM" in the system, but > FirewallVMs that are assigned to each AppVM. I see now, thanks. Each ProxyVM acts as the FirewallVM for whichever VMs use it as a NetVM. -- 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/b2848f2c-57fd-41ad-b9fc-0ba190588afc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] What decides which VM is the FirewallVM?
Hi, >From my understanding, the FirewallVM is where the firewall rules are put into >place from the Qubes VM Manager. The sys-firewall VM acts as the FirewallVM by >default but what decides which VM gets that role? Is it automatically the >first ProxyVM connected through the NetVM? Does naming a ProxyVM >"sys-firewall" make it the FirewallVM? I can't find anything on how the >FirewallVM is decided in the documentation at >https://www.qubes-os.org/doc/firewall/. It would be handy to know if creating >all VMs from scratch instead of using the defaults when Qubes OS is installed. Thanks -- 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/941d11b0-4ea0-49c4-953e-dc5794a1c8b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to manually remove a VM?
On Monday, December 19, 2016 at 4:33:06 PM UTC+10:30, Andrew David Wong wrote: > How did you perform this step? Did you manually edit qubes.xml? The VM Manager allowed me to 'remove' the VM. Because the VM was renamed, as far as I can tell it just removed it from qubes.xml. On Monday, December 19, 2016 at 5:27:45 PM UTC+10:30, v3g4n wrote: > I will let someone more knowledgeable on the manual removal process > answer, but why not just remove it using Qubes VM Manager? Just curious > about the manual process? A bug in the VM Manager occured when I went to rename a VM, the VM files were renamed but the VM Manager didn't update it's records and still showed the old name. It leaves a bunch of references to something that no longer exists (in the VM Manager and in the application menu). I haven't succeeded in reproducing this bug, I was renaming a HVM template I had just installed an OS onto and shutdown. Of course manually removing VMs is not the ideal way to do it, but unfortunately things sometimes go wrong like it did for 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 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/ba9cd3b9-c029-403e-a6c1-67abd9fa4b51%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How to manually remove a VM?
So I made a HVM Template and renamed it through VM Manager, something went wrong and the VM Manager did not reflect the name change. (Can't seem to reproduce this bug) I was just wondering if I've successfully removed the HVM Template manually. The process I went through was: 1. Remove template folder from /var/lib/qubes/vm-templates 2. Remove old template reference from VM Manager (or manually from qubes.xml) 3. Remove template's *.desktop files from ~/.local/share/applications Is there any files I have missed? Also, perhaps a short doc with this would be useful for when things go wrong and a VM needs to be manually removed. Thanks -- 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/65ffe4eb-85b6-434c-b043-0767fc202a78%40googlegroups.com. 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
I have been doing some tests using a GTX 1070, on Qubes R3.2, I think it is
fair to say GTX 900 and 1000 series cards are unusable right now going by user
reports.
Booting in BIOS mode without self-test:
Starting installer, one moment...
*black screen*
Booting in BIOS mode with self-test:
Starting installer, one moment...
*scrolls too fast to read*
17:47:03 Not asking for VNC because we don't have a network
17:47:03 X startup failed, falling back to text mode
Then I am placed in the anaconda CLI install. Trying to go through with the CLI
installer fails while trying to set an install destination. Selecting LUKS
results in the following errors:
Generating updated storage configureation
storage configuration failed: autopart failed:
Encryption requested for LUKS device sdc2 but no encryption key specified for
the device.
Booting using UEFI doesn't work either. It shows the 4 tux images and says:
[ 0.00] efi: EFI_MEMMAP is not enabled.
[ 0.00] esrt: ESRT header is not in the memory map.
[ 5.760317] dracut-pre-trigger[401]: cat: /tmp/dd_disk: No such file or
directory
[ 37.945613] hid-generic 0003:1044:7A03.0008: item 0 1 0 8 parsing failed
[ 38.003314] hid-generic 0003:1044:7A03.0008: No inputs registered,
leaving
[ 39.170611] sd 6:0:0:0: alua: Attach failed (-22)
{ 9.139264] dracut-initqueue[506]: mount: /dev/sdd is write-protected,
mounting read-only
The display then freezes, trying to switch tty doesn't show any effect.
I think this has something to do with nouveau. Searching around shows nouveau
only got support for the GTX 1000 series in July. Perhaps Qubes is using an
outdated version?
--
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/8e0fa814-9da2-4d03-b5e3-4211f43bf5d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Why is there no built-in nvidia driver support? aka GTX 980 issues
> > Qubes was working flawlessly on my GTX 670, > > So why did you change anything if things were working? > > > Achim Qubes isn't my main OS and I wanted an upgrade -- 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/aa021aae-69f9-4d5b-bede-16ac5eb1bb5a%40googlegroups.com. 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
Qubes was working flawlessly on my GTX 670, recently upgraded to a GTX 1070 and now I can't even load the installer -- 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/ece01772-290a-4b3f-8d96-0f6323f9069c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Possible R3.1 incompatibility with Samsung T3 portable SSD
Update: I have invented a temporary workaround. Requirements: Another usb or harddrive of 32gb (qubes system requirement) Qubes installer or another *nix system 1. Install normally onto a USB or harddrive 2. Use the qubes installer (ctrl+alt+f2) or another *nix system to dd the installed OS to the Samsung T3 Portable SSD Use lsblk -f to find the appropriate drive letters. Example: dd if=/dev/sdc of=/dev/sdd bs=1M /dev/sdc being the installed OS, /dev/sdd being the portable SSD. I haven't tested the copy extensively, but it's able to boot and run VMs normally. -- 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/3cb4ba3f-545a-4120-a409-df9b00174dcb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Possible R3.1 incompatibility with Samsung T3 portable SSD
Hi, I am also having problems installing Qubes R3.1 to the Samsung T3 External SSD 500GB. Using a pgp and hash verified iso that passes the media verification test. Running on a Intel Core i5-4570 @ 3.20GHz. The install fails on the "creating swap" step with an "unknown error". devices.py line 788 is at the top of the error. Also, manual partitioning doesn't work. Trying to create the "/" or "/boot" parition results in the error "cannot create aligned partition" or something. Clicking the "automatically create partitions" link in the partition page gives an error along the lines of "the root / partition does not exist" and "the boot partition does not exist". I have tried switching the external SSD from a 3.0 port to a 2.0 port to avail. -- 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/2671f718-abaa-4f97-91e9-459866ce95e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
