Re: [qubes-users] I added VGA device and now Black Screen on Startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/07/16 23:12, ewashb...@metroconnects.com wrote: > On Friday, July 15, 2016 at 1:46:27 PM UTC-5, donoban wrote: >> On 15/07/16 19:36, ewashb...@metroconnects.com wrote: >>> Using Qubes R3.1. Was working fine until I added VGA device >>> under devices and now after I enter the password for encryption >>> screen goes Black. Is there any way to remove that VGA Device >>> from the command line at boot or what would be the best way to >>> remove that setting from the Grub prompt. >>> >> >> Try to boot with a rescue system, mount your root fs, chroot it >> and use qvm-pci command. > > Donoban, Thank you. Still new to Qubes, Do you know off hand what > qvm-pci commands I would use to remove the VGA device that was > activated? > Are you still having problems with this? you should do: 'qvm-pci --offline-mode -d ' you can use first 'qvm-pci --offline-mode -l' and find the device you want remove. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXjHWgAAoJEBQTENjj7QileFkQAJRyq9cNtL6x0bZvOjAk9GOI f7cod3jX1ZNNOfeDMweW8lOsVuhFgHWiKMx2MoSH8/8V8jp8+V+4xIiKXFUSmdTZ DoHXf3jcUsmvpYqVmSCyENMIxDj7sLtPJQlgrjajcn0SEn+nlupAZpK+5BzGFrcQ 2dlxDlSsrZ+hiknykQzINlVa8cpv8crrNDdFfoxL6EIySA9AvxLm5RAk4g4c5ApY BwQuQCQO72bQhpdavLXLX1ypg8tlqGRjLmV+0BjWD3TZ7emO3faawdEGDa7ngJkE 3wrdp9c2HD2cWCjdkjamioDuqFGuwcGjkHS8g8j7yrGTC758tveEfHITTNF2IBed tQ6zpHfGffnfOy7pKSPYJQmEt3JlPhScejDuu9otYLARhQAoma1CxTLEX4dFfu9n GFNzxWtFxjwyNq26GRqMw41bVKHs4yzZ1D8VOraaNmzVAQ+qeG2e9YjFbZk3ftzK yzZhW5twbZA2ijPVlQpoBeZFtCxkxpgBrwgpuX7RzSgnmc1CHgLDki69IRzNvqY8 fjBjhtaG1bkZ+XH/zebHP4wsooDsSU908wJJZn0BWrgsgRLlbmo5ewvi99jr2uCA Mlxy8E4Z1ZtQhC6+e9Y8LZaXQTuNl3GpNqUyutbkQPyiqDcsFgNNUt7tV0xDVAaR p5RBMo2Q+pTvQZIPRBWn =FgbY -END PGP SIGNATURE- -- 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/e86fc1cb-5905-a170-09f1-4343726d1a6a%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] using Arduino development environment with Qubes OS
I'm converting a machine I used for Arduino development to use Qubes. The docs indicate support for USB stick, keyboard, and mouse. I'm wondering if I can gain access to /dev/ttyACM0 or similar devices in a specific VM? This is a usual USB-to-serial interface used by Arduino. Peter Olson -- 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/08fce32d-da2e-4379-acf2-eaacdf539358%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] I miss the KDE cpu sensor
It was the only way i had in qubes to see true total cpu use, nothing else shows it. qubes manager or top in dom0, neither does the xfce addon to cpu monitor i'm using called cpu graph. now I just have to go by feel haha and hope because my pc is so crappy that I notice something off just with that. :) -- 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/257a9dea-0f8c-4f5d-b1b1-0ed0b45aceb4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Networking
On Saturday, July 16, 2016 at 2:57:02 AM UTC-4, Drew White wrote: > On Saturday, 16 July 2016 16:25:50 UTC+10, raah...@gmail.com wrote: > > > > lol, are you sure you are not creating problems for yourself? You would > > make a great beta tester, but it doesn't seem you are using qubes like a > > normal person. > > > > Strange that it would work on 3.2 but not in 3.1. I wonder why that is. I > > was just guessing that it worked after you immediated testing after a fresh > > install. I'm sure if we gave you time on 3.2 you'd do something it on > > there too lmao... > > lol, not at all. I'm using like a normal person actually. > I'm using it as a developer at work, and a normal person at home. I'm having > the same issues when at work or home, whether I'm using it as a developer OR > a "normal person". > > I mean, I'm a user, not an end-user, when at home. > > Qubes isn't really made for end-users anyway. It's too complicated for the > general end-user. > > And no, even on a FRESH INSTALL, it has the same issues. > Even when using a 4 Gbps NIC, it has the same issues in 3.1 > Nothing broken or altered at all, and the issue exists. > > So I'm not to blame for the issue. I don't know who/what is, but I know it's > not me. (at least for this issue/problem [lol]) > > As a beta tester, I would be good, because I push things to their limits, > unlike other people who just think "this is what it's mean to be able to do, > I'll only do half of that". > > So.. Please define "Normal Person"... > > 3.2 has some changes to it. The networking works perfectly from linux -> > linux -> Network. > What is different I don't know, but it works. and it has the SAME CHANGES > that I made in 3.1 to improve security and all. And it works fine. > Windows is the only one that has a 100 Mbps NIC inside Windows, instead of > Gigabit. Qubes really isn't that hard to use, but for some reason its got that stigma attached to it. Its different is all it is. Anyone who uses windows and doesn't need to play games can use it imo. I taught my family how to update qubes, attach usb block device from usbvm, use the different vms for different tasks, copy and paste, transfer files between vms. Its all with mouse and gui, whats the big deal? I dunno I just wonder how you find 200 bugs lol. most people using qubes don't have such problems. When your a normal person you don't go looking for problems. As long as it can do what you want to do. All these problems don't seem to be the case for most users. Is there really a difference in networking between 3.1 and 3.2? I wonder what it is. You sure you using the best drivers? Maybe the kernel is the difference. -- 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/4dd2204c-4dbd-4a00-9e76-6dd31ae5ec0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] rsync ssh connection in AppVM failing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-07-17 15:18, paulstans...@gmail.com wrote: > Hello, > > I've recently installed Qubes-3.1 and I'm trying to rsync files from my > home desktop to my Qubes machine. > > I have about 30 GB to transfer, but each time I try to pull files from the > desktop to the Qubes Personal AppVM using rsync I find it stops > transferring after about 100 to 200 MB. I'm running rsync on the Qubes > side which does not crash, but I have to kill it with Ctrl-C as is seems to > freeze. > > Also, monitoring the transfer rate shows it to be very on-and-off and > stuttery with long delays where nothing is being transferred until > eventually it stops altogether. > > I can run and kill rsync a few times before I get "ssh: port 22: No route > to host" messages. At this point "service sshd status" tells me the > process is "Active: inactive (dead)". I can try to restart it with > "service sshd restart" which seems to work as "service sshd status" tells > me the process is "Active: active (running)", but after this rsync still > fails with "ssh: port 22: No route to host" messages. > > At this point I resort to rebooting my Qubes machine and going through the > process again with similar results. > > I can do similar transfers between other home machines just fine. > > Any ideas why Qubes is having problems? > > Thanks > Does the AppVM have enough free space to accommodate the whole transfer? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXjC0RAAoJENtN07w5UDAwCxQQAM4Qcl3OVJEI53iZk4xHh5sx PW5rZdGfoPIyCorpz/lTPaYIRWxlgKGtigKfc0x3S/QxU1QaQzNkHj1lgG12Ma7M h34Ni8lBu2Kxt+LrvkKb3O2TU7zf8tePjBsPayhl/5QtfjNzE25jz1Om5OembJlG QFHtZ9Z8eflzHzAOnwH1t3J2fYGluT3eqbYPvF9Hkv2f+igL8Rg2QWoQsECXCCT+ 7uWQ7GgMacumdTkvfaj3aw2vIo1T3Yr6tbIVzumP02DyHWtibQq59m6iwoeffZGm TEZZqjDSuomyJktfpQlItq9Y1N8V6V25c/RE2fsSwfOqWmJSNIzZaJzcx1S05M2Y /HK1I1QfrKZ1uI+h/6FQqVzdNnIVbTwHEYRWrycLrC6YHzIW3tN0sJKpzAX5nwwK 4jstO7n7EqwQFT4u84EpHsyPLkZW5n0oprN7RUa+1lz/rW3yaB5S8ZcwTX2XjU8u /y+d+ekOcBWXfkDoxm2h0Im7DgIEEHJmR8Z2rCAPRczuLcW1+Et/q58wTV5wvheC 4tBVV+Lns2Xp8I3SLzDJEPlVWqv+Ss90MMDet+lIjdRZ6xYBwkLElejN4E+GJjLs M3E5Yv3JTbLpxJpLcr6akq71432D5qgWL8CuRhSXlTiLXzVF0BsSrPf2gvdTS7VN 91jidt+HLzGkZc3Zwt9G =6bRa -END PGP SIGNATURE- -- 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/a7b2328a-0136-b233-31c6-9ab652ee53c1%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] rsync ssh connection in AppVM failing
Hello, I've recently installed Qubes-3.1 and I'm trying to rsync files from my home desktop to my Qubes machine. I have about 30 GB to transfer, but each time I try to pull files from the desktop to the Qubes Personal AppVM using rsync I find it stops transferring after about 100 to 200 MB. I'm running rsync on the Qubes side which does not crash, but I have to kill it with Ctrl-C as is seems to freeze. Also, monitoring the transfer rate shows it to be very on-and-off and stuttery with long delays where nothing is being transferred until eventually it stops altogether. I can run and kill rsync a few times before I get "ssh: port 22: No route to host" messages. At this point "service sshd status" tells me the process is "Active: inactive (dead)". I can try to restart it with "service sshd restart" which seems to work as "service sshd status" tells me the process is "Active: active (running)", but after this rsync still fails with "ssh: port 22: No route to host" messages. At this point I resort to rebooting my Qubes machine and going through the process again with similar results. I can do similar transfers between other home machines just fine. Any ideas why Qubes is having problems? 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/71ebdf28-6178-43ca-937e-35d666b1ea2e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: SUCCESS: GPU passthrough on Qubes 3.1 (Xen 4.6.1) / Radeon 6950 / Win 7 & Win 8.1 (TUTORIAL + HCL)
On Friday, July 15, 2016 at 6:47:59 AM UTC+10, Marcus at WetwareLabs wrote: > Some more experimentation with GTX980: > > - Tried Core2Duo CPUID from KVM VM > - Ported NoSnoop patch from KVM > > Sadly, neither of these would help with BSODs / Code 43 errors. > > I posted the results (with patches and more detailed information) on > Xen-devel > (https://lists.xenproject.org/archives/html/xen-devel/2016-07/msg01713.html). > I hope the experts there might have more suggestions. I'm guessing that it has to do with the nvidia-specific quirks implemented where the PCI BAR's are used to access the PCI Config Space and other BAR's. See: https://github.com/qemu/qemu/blob/master/hw/vfio/pci-quirks.c I think before others worked around it somewhat by reserving the memory and having 1:1 mappings ( http://www.davidgis.fr/blog/index.php?2011/12/07/860-xen-42unstable-patches-for-vga-pass-through ), but that isn't really a proper solution. -- 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/f0648096-35e1-444a-a276-f0c55379b875%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] NTP?
Andrew David Wong writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-07-16 22:04, Niels Kobschätzki wrote: >>> $ cat /var/log/cron >> >> That file doesn't exist. >> > > If you're on Fedora 23 in dom0 (R3.2-rc1), then I guess there was some change > since Fedora 20. That's the reason then probably. Niels -- 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/871t2s2mzh.fsf%40mailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL and 3.2RC1 observations
New user to Qubes over the last few months. Many thanks to the developers for creating this clever OS, and the users who have contributed to this group. My setups were smoother as a result! I've been successfully using 3.1 on a T420. Attached is a HCL for System76's Meerkat. Nice little machine, but appears to have only one USB controller, so keyboard, mouse, USB drives are all in dom0. Under 3.2RC1, the only major issue I'm having (on the meerkat) is this (under xfce): If I manually turn off my external HDMI monitor, or if system suspends it, upon powering it back up, the monitor reports "no signal." I have to reboot the machine... Turning off suspend is my short term solution. This situation did NOT occur on the T420, RC1, xfce, and VGA. I tried using KDE, and essentially the same error occurred, but KDE returned the following before becoming unstable: "Executable plasmashell PID: 4007 Signal: Segmentation fault (11)" Confirming the below bug report in RC1: Enigmail 1.9 is incompatible with Split GPG on Debian 8 https://github.com/QubesOS/qubes-issues/issues/2170 In my case, "vault" is stock fedora-23 and client is gently modified whonix-ws. Worked under 3.1, VMs migrated to RC1 by backup/restore. Happy to provide any further debugging info, just please be explicit in your directions as I'm a noob at the command line in linux. Thanks, Doug -- Doug Hill AB77 9B0D F85F 786E 2276 3CF1 8F88 AE89 13E2 89F6 -- 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/98b75bd6-56e7-651d-b0bc-06a7e76bb1ce%40riseup.net. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-System76__Inc_-Meerkat-20160717-083155.yml Description: application/yaml signature.asc Description: OpenPGP digital signature
Re: [qubes-users] NTP?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-07-16 22:04, Niels Kobschätzki wrote: >> $ cat /var/log/cron > > That file doesn't exist. > If you're on Fedora 23 in dom0 (R3.2-rc1), then I guess there was some change since Fedora 20. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXi28cAAoJENtN07w5UDAwS3kP/0bVtUUYzA5JcO3cfzkl+23X n3h8A7q2/0x3dbABLZv5eCMIibsK5TyTF2IoAFD7jAeC7vlaub22WKlNUboKPHqj lVSYpBhezwoZCKecHnvh1lptWl3HU4tQnSVWSXf4BVQN12aQ53aNKRx+o8Wf7p0/ BtCIhV6ekyafStX7lQoqtLg9yBaDDpiKuhdWaYgDFnGsL59d0U4rN1FGL97W1+/R hF8fj6W+0+oQYZTGOR6RnnTEaQLmujYBjjlgFpTC1Qxh6ev147CLVQiP2YDxvsIc OY4jrmbImeb0lujBxXWacTiYnT6U6BRfEVt02hi4wZFV2+FNyMFrFu4JosH2g3JB 54Lx19GSTO3IEXOOJbszgaVaywbZ/c75VtSzuew6Nr9c6bxIakB52WsbiftTxotO APjPker5Dhq+9+ot4DxZ5sy5zKx618k51EoATVTqh/QniXhF6MAHlyTofmMEbbRF 9uIn/thJDCRIgQ4VyL20Cna/C1bnpnEJyg9qeiu4SQI7uiZzua6pTsDxwAbeQOBA da/8fq6oKlSZYU3Wq3zvsDXW5hsmBWhZm+dHVQtlTp4qxN8XbcmTIPZ94b6rWgZu nBglWi4U5DeIUghSvPMokOwXTt/ovZliLWWiqZYzMsM5l5E+cacqfM5Cyo9W5oZZ hVlnWx5Sj0YYkmjTB+cx =Nrgw -END PGP SIGNATURE- -- 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/a58729b0-f750-e64b-8a21-dbdd55af955f%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] [3.2RC1] i3wm bad performance.
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.
Re: [qubes-users] Setting up OpenVPN (Can't understand documentation)
On 07/17/2016 04:26 AM, ajshdas7...@sigaint.org wrote: Under "Using iptables and openvpn" @ https://www.qubes-os.org/doc/vpn/ It says to create the proxyvm, but it does not say if the following steps should be taken in the template or in the proxyvm. Does anyone know? That part should be clearer. However, the intent is to setup the proxyvm. Chris -- 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/3aec5d45-5e21-56ad-1f9a-e3181a5563bc%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Setting up OpenVPN (Can't understand documentation)
Under "Using iptables and openvpn" @ https://www.qubes-os.org/doc/vpn/ It says to create the proxyvm, but it does not say if the following steps should be taken in the template or in the proxyvm. Does anyone know? -- 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/a16352801fa4c2719579de16ab63a9da.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
