Re: [qubes-users] HCL - Intel NUC NUC5i5RYK, Samsung 850 EVO - 250GB - M.2 SATA III SSD, Crucial 16GB RAM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-10-30 11:37, Max wrote: > Overall, works very well. > > Tried very briefly (a day or two) with 3.1 but since the release of 3.2 have > used this only. > > With Qubes 3.1, I couldn't use my Logitech TK820 USB wireless keyboard or > Elecom mouse during installation or to enter the decryption password. Once > the user login prompt appeared this worked fine. > > For Qubes 3.2, the wireless keyboard and mouse have been fine all through > installation and from decryption to login. > > > For both Qubes 3.2 and 3.1 ethernet and WiFi have worked without issue. > Playing video and sound are no issues through both the headphone jack and the > HDMI. > > The only issue I have had is from using an Asus VX228 Monitor (HDMI to > miniHDMI or the mini display port). Switching the screen off and on is fine, > waking from sleep is ok but if I unplug the monitor and plug it back in again > the screen is blank and I cannot wake it. This issue doesn't occur when using > booting from another Linux distribution such as TAILS or Fedora 24. > > I haven't yet downloaded any further drivers as I am unclear whether this is > required. Any advice on how to resolve this? I would like to be able to leave > Qubes operating on the NUC without a monitor and locked as I intend to have > programs operating continually. > My opinion is that you should only download additional drivers if you really need them. (If you have to ask, you probably don't really need them.) - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYGAcUAAoJENtN07w5UDAwhsAP/3wfN2HpHd6Z9WaDwXFptQyU MQcPM5kLK9A5WiMLK0LQJ1iBoLoIucFYCrvf3bZglOC57zRLabfU81SKkOV/HAjP hBVoQs2hdv4sqjZVvNGALRtxdiaIIRyv6n3P9BdoEQ0M3vTd5bBTRBGps3X1DuP9 pPFHK7c4EH54Ma7lg1386dtfAdEZCd4w8ddLt08GlUlQX8ICF6oKUNGQwuqBGz/I HzPAZx/9U6Nz4Bujk5mRUere9CSj+mEEmcFLrHQTyT760Dlnbc2KKD0PcGyuratm 0MGM8dyiHTkX4D2BGbezYaMfz/sNTy6LgPjedJ8yDhj/DL4S95qjvP5oEgJ1V6Hl E0iBjfrNZasVZxVqBj25xfAuSLHDsgj1KBZutbzH/cppy3XrIVz+4fQG0phiyV0A XTSb5DF0suobkKG3ZtsMR6pj/Q6VwLRpIb5HmZIXNTuuriOZXtHuOmV2+/iNWM/B 38RPCzAlnIUJuL+PBujwQglzZs4nXNwAwF3B/EGRDGx1JK79i6bTFCow4UOVUJtz /db8EfiPr++oRYVTMN9Oi2yU7dekmWY3AMrNireFYjWs+Z1hTGNak0X8V6M+NhJp +RaFTgyxEsFCBe7OtyPYjY9UlO/Wis1rlyHOnzBzKJGdO9PXNtdwEGqX+LfpE4eb HFUFpB5RqdAZNmrghAgs =fH8a -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/70e98827-9930-5e53-4e0a-f4c9e40f2da0%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can TeamViewer or similar work with Qubes..?
I use TeamViewer in Linux Mint 17.3 HVM. I presume TeamViewer works in any HVM. For PV, other options are: - use reverse SSH to login to PV - have SaltStack master running somewhere and add SaltStack minion software to PV -- 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/4ea4e440-7795-4a3d-bee1-366dd4bcd973%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL Asrock X99E_ITX_ac
W dniu poniedziałek, 31 października 2016 08:17:05 UTC+1 użytkownik Grzesiek Chodzicki napisał: > W dniu niedziela, 23 października 2016 16:25:45 UTC+2 użytkownik Grzesiek > Chodzicki napisał: > > W dniu niedziela, 23 października 2016 16:22:28 UTC+2 użytkownik Grzesiek > > Chodzicki napisał: > > > VT-x VT-D and EPT work, require enabling in BIOS beforehand > > > > > > USB controllers require strictreset set to false in order to attach them > > > to sys-usb. > > > > > > Motherboard has one PS/2 connector, I don't know whether its a true PS/2 > > > controller or a converter connected internally to a USB controller, I'm > > > waiting for AsRock cs team to reply to my query. Will update immediately. > > > > > > If you have any questions regarding the motherboard, feel free to ask. > > > > TPM header available, untested. > > AsRock team replied. PS/2 connector uses its own controller and thus can be > assigned to Dom0. Wi-Fi card shows up as two different devices, one is standard NIC the other is Vendor Specific Class device which curiously shows up in lsusb output. -- 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/98d882d0-4914-41d6-a71a-ab8c300d8b1c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 - Whonix GW VM Update
On Friday, 28 October 2016 22:01:18 UTC-5, 3n7r...@gmail.com wrote: > On Saturday, October 29, 2016 at 2:18:35 AM UTC, Vincent Elliott wrote: > > Hi, > > > > I am very new to Qubes. > > > > In trying to update the Whonix GW VM, the updater reports that the file > > sizes are different from what the server reports. In every instance I have > > rolled back the updates. > > > > Is this normal? > > > > Vincent > > It's not normal in that it shouldn't be happenning. It is normal in that it > is happening to everyone. > But no need for concern: > https://forums.whonix.org/t/size-of-file-dists-jessie-main-binary-amd64-packages-gz-is-not-what-the-server-reported/3074/2 Thanks a mil. Vincent -- 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/2ab3c3ae-e9fa-426a-b889-4035c74182ce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qvm-block issues
On Sun, Oct 30, 2016 at 09:24:43PM -0700, Drew White wrote:
> Hi folks,
>
> Well, I mounted an image to the guest.
> Then I finished, so I unmounted it in the vm and went to remove it to attach
> it to another guest...
>
> I tried several different methods...
>
> [{username}@dom0 {foldername}]$ qvm-block -d {vmname}:xvdi
> Usage: qvm-block -l [options]
> usage: qvm-block -a [options] :
> usage: qvm-block -A [options] :
> usage: qvm-block -d [options] :
> usage: qvm-block -d [options]
> List/set VM block devices.
>
> qvm-block: error: Invalid VM or device name: {vmname}:xvdi
> [{username}@dom0 {foldername}]$ qvm-block -d {vmname}:/dev/xvdi
> Usage: qvm-block -l [options]
> usage: qvm-block -a [options] :
> usage: qvm-block -A [options] :
> usage: qvm-block -d [options] :
> usage: qvm-block -d [options]
> List/set VM block devices.
>
> qvm-block: error: Invalid VM or device name: {vmname}:/dev/xvdi
> [{username}@dom0 {foldername}]$ qvm-block -d {vmname}:/dev/xvdi1
> Usage: qvm-block -l [options]
> usage: qvm-block -a [options] :
> usage: qvm-block -A [options] :
> usage: qvm-block -d [options] :
> usage: qvm-block -d [options]
> List/set VM block devices.
>
> qvm-block: error: Invalid VM or device name: {vmname}:/dev/xvdi1
> [{username}@dom0 {foldername}]$ qvm-block -d {vmname}
> [{username}@dom0 {foldername}]$
>
> So, the only one that worked was " qvm-block -d {vmname} "
>
> But that detaches everything. I only wanted to detach xvdi
>
> To attach it I used
>
> [{username}@dom0 {foldername}]$ qvm-block -A {vmname}
> dom0:/run/media/{username}/{partition_label}/{imagename}.img
>
>
>
> I did this when it was saying that the device wasn't there, just to make 100%
> sure it was.
>
> [root@{vmname} {foldername}]# ls /dev/xv*
> /dev/xvda /dev/xvdb /dev/xvdc /dev/xvdc1 /dev/xvdd /dev/xvdi /dev/xvdi1
> [root@{vmname} {foldername}]#
>
>
>
>
> What is it that has gone wrong here?
Hello Drew,
Check the man page -
what you want is this:
qvm-block -d -f
You can just specify the device as xvdi, in your example.
That works for me with vanilla 3.2
This will leave other devices attached.
The help and man page are not that clear - why not submit a PR to help?
regards
unman
--
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/20161031102017.GA10015%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL Asrock X99E_ITX_ac
W dniu niedziela, 23 października 2016 16:25:45 UTC+2 użytkownik Grzesiek Chodzicki napisał: > W dniu niedziela, 23 października 2016 16:22:28 UTC+2 użytkownik Grzesiek > Chodzicki napisał: > > VT-x VT-D and EPT work, require enabling in BIOS beforehand > > > > USB controllers require strictreset set to false in order to attach them > > to sys-usb. > > > > Motherboard has one PS/2 connector, I don't know whether its a true PS/2 > > controller or a converter connected internally to a USB controller, I'm > > waiting for AsRock cs team to reply to my query. Will update immediately. > > > > If you have any questions regarding the motherboard, feel free to ask. > > TPM header available, untested. AsRock team replied. PS/2 connector uses its own controller and thus can be assigned to Dom0. -- 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/35d7eba4-7a83-4d77-8259-5ed491cdb12d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qvm-block issues
On 10/31/2016 05:24 AM, Drew White wrote:
> Hi folks,
>
> Well, I mounted an image to the guest. Then I finished, so I
> unmounted it in the vm and went to remove it to attach it to another
> guest...
>
> I tried several different methods... []
> But that detaches everything. I only wanted to detach xvdi
>
> To attach it I used
>
> [{username}@dom0 {foldername}]$ qvm-block -A {vmname}
> dom0:/run/media/{username}/{partition_label}/{imagename}.img
>
>
Hi Drew,
afair qvm-block needs the name of the original VM where the device is
attached for removal. So, if you attached your device from dom0, you
will need to use dom0 for removal too. As an example, but using usbvm:
dom0$ qvm-block -a work usbvm:sdd
This attaches /dev/sdd in usbvm to work
dom0$ qvm-block -d usbvm:sdd
This now detaches /dev/sdd in usbvm from work
And this is why, in the --help output, the -d command has
instead of just , to highlight the fact that
you need the original vm name. If you want to detach everything you can
use the second syntax suggested by --help, using the vm name, and this
will detach everything from that vm.
I do know that you are mounting an image file; and I don't know if this
works this way too - i.e. if you need to specify the full path to the
file, like this:
dom0$ qvm-block -a work dom0:/mnt/foo/bar.img
and then
dom0$ qvm-block -d dom0:/mnt/foo/bar.img
to detach it
You can probably check the output of "qvm-block" without parameters,
once the image file is mounted; the first column of the output contains
the names used to identify the devices (or files, I suppose) to be managed.
Hope this helps,
--
Alex
--
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/129ebc17-9407-8b41-6554-b39ad9afa229%40gmx.com.
For more options, visit https://groups.google.com/d/optout.
