[qubes-users] HCL - Dell Precision 5810

2018-01-17 Thread Gaijin
Had to switch BIOS to Legacy to install Qubes. Otherwise everything else
seems to be working well with R3.2.

-- 
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/c141a4978bc271d0631edcc2accda646%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Dell_Inc_-Precision_Tower_5810-20180118-140542.cpio.gz
Description: GNU Zip compressed data
---
layout:
  'hcl'
type:
  'tower'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  Dell Inc.
model: |
  Precision Tower 5810
bios: |
  A20
cpu: |
  Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [8086:6f00] 
(rev 01)
chipset-short: |
  FIXME
gpu: |
  Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
  Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Intel Corporation Ethernet Connection I217-LM (rev 05)
memory: |
  130985
scsi: |
  DVD+-RW GTA0NRev: A1C1
  SK hynix SC311 S Rev: 0P10
  ST2000DM001-1ER1 Rev: CC27
  ST2000DM001-1ER1 Rev: CC27
usb: |
  3
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R3.2
  xen: |
4.6.6
  kernel: |
4.9.56-21
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---



Re: [qubes-users] PCI passthrough working in Qubes R4.0?

2018-01-17 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Jan 18, 2018 at 01:05:46AM +, mossy-nw wrote:
> Marek Marczykowski-Górecki:
> > On Wed, Jan 17, 2018 at 11:54:23PM +, mossy-nw wrote:
> >> Dear Qubes community,
> > 
> >> Has anyone using Qubes R4.0 been able to resolve any issues (e.g. with
> >> wifi) by setting PCI permissive mode? (as described in:)
> > 
> >> https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues
> > 
> >> I successfully used this in Qubes R3.2 to get wifi working for dell xps
> >> 13 9350 (bcm4350) but am having no luck using this method in R4.0_rc3.
> > 
> >> This situation seems identical (driver errors that persist but
> >> nonetheless wifi works using permissive mode) resolved by in a previous
> >> (R3.2) qubes-users thread by miaoski --
> >> https://groups.google.com/forum/#!msg/qubes-users/m4GzpfOVBiQ/bf5XCEc-DQAJ
> > 
> >> I'm hesitant to give up and go back to R3.2 on this machine, so I don't
> >> have access to the R3.2 dom0 dmesg output for PCI spermissive mode, but
> >> I recall before setting permissive mode dmesg suggested doing so.  This
> >> is not the case in R4.0_rc3 however.
> > 
> >> Some dmesg output, if this gives anyone any ideas:
> > 
> >> [dom0 ~] lspci | grep -i network
> >> 3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless
> >> Network Adapter (rev 08)
> > 
> >> Before setting permissive mode:
> >> [dom0 ~]$ sudo dmesg | grep
> >> [7.222306] pci :3a:00.0: [14e4:43a3] type 00 class 0x028000
> >> [7.222348] pci :3a:00.0: reg 0x10: [mem 0xdc40-0xdc407fff 
> >> 64bit]
> >> [7.222379] pci :3a:00.0: reg 0x18: [mem 0xdc00-0xdc3f 
> >> 64bit]
> >> [7.222618] pci :3a:00.0: supports D1 D2
> >> [7.222619] pci :3a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
> >> [7.222766] pci :3a:00.0: System wakeup disabled by ACPI
> >> [8.053279] pciback :3a:00.0: seizing device
> >> [   68.211970] xen_pciback: vpci: :3a:00.0: assign to virtual slot 0
> >> [   68.212362] pciback :3a:00.0: registering for 4
> >> [   68.217475] pciback :3a:00.0: enabling device ( -> 0002)
> > 
> > Did you get anything after that message? Permissive mode helps mostly
> > with cases reported in dom0 dmesg with message like this:
> > 
> > pciback :03:00.0: Driver tried to write to a read-only
> > configuration space field at offset 0x110, size 4. This may be harmless,
> > but if you have problems with your device:
> > 1) see permissive attribute in sysfs
> > 2) report problems to the xen-devel mailing list along with details of
> > your device obtained from lspci.
> > 
> > Interesting would be to see messages in sys-net about that device
> > driver.
> > You may also try updated kernel for VM, there is
> > kernel-qubes-vm-4.14.13-1 package in current-testing repository:
> > https://www.qubes-os.org/doc/software-update-dom0/#testing-repositories
> > 
> > 
> 
> Thanks, Marek--I will try the updated kernel (though sys-net has the
> appropriate driver binary file, and this was working under R3.2 for many
> months i.e. with older kernels).  Here are relevant messages from sys-net:
> 
> [user@sys-net ~]$ lspci -k
> 00:05.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless
> Network Adapter (rev 08)
>   Subsystem: Dell Device 0023
>   Kernel modules: brcmfmac
> 
> [user@sys-net ~]$ sudo dmesg | grep brcmfmac
> [1.703756] usbcore: registered new interface driver brcmfmac
> [1.970170] brcmfmac: brcmf_chip_recognition: SB chip is not supported
> [1.970185] brcmfmac: brcmf_pcie_probe: failed 14e4:43a3

Do you see other relevant kernel messages about that time (not necessary
containing brcmfmac)?

I assume this is after enabling permissive mode, right?
Simon, is setting permissive mode in dom0 enough? Or maybe qemu in
stubdomain perform some additional filtering?

> [user@sys-net ~]$ modinfo brcmfmac | grep -E
> '^(description|author|depends):'
> description:Broadcom 802.11 wireless LAN fullmac driver.
> author: Broadcom Corporation
> depends:mmc_core,brcmutil,cfg80211
> 
> Trying advice from -
> https://www.qubes-os.org/doc/wireless-troubleshooting - I tried
> disabling/reenabling brcmfmac and some combinations of those others
> (mmc_core,brcmutil,cfg80211; reversing remove/add order), but no luck.
> 
> I also tried using as the sys-net template qubes-template-debian-9 with
> broadcom-sta-dkms and others (which I recall got this working for
> running non-Qubes debian on this laptop), to no avail.
> 
> Thanks again,
> 
> -m0ssy

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpf9Z0ACgkQ24/THMrX
1yz77gf+JxndavVwAAduAI/vwF6dHWtP9nrTCEESUh/4zna2lWZzWnhbvq8lufOe

Re: [qubes-users] PCI passthrough working in Qubes R4.0?

2018-01-17 Thread mossy-nw
Marek Marczykowski-Górecki:
> On Wed, Jan 17, 2018 at 11:54:23PM +, mossy-nw wrote:
>> Dear Qubes community,
> 
>> Has anyone using Qubes R4.0 been able to resolve any issues (e.g. with
>> wifi) by setting PCI permissive mode? (as described in:)
> 
>> https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues
> 
>> I successfully used this in Qubes R3.2 to get wifi working for dell xps
>> 13 9350 (bcm4350) but am having no luck using this method in R4.0_rc3.
> 
>> This situation seems identical (driver errors that persist but
>> nonetheless wifi works using permissive mode) resolved by in a previous
>> (R3.2) qubes-users thread by miaoski --
>> https://groups.google.com/forum/#!msg/qubes-users/m4GzpfOVBiQ/bf5XCEc-DQAJ
> 
>> I'm hesitant to give up and go back to R3.2 on this machine, so I don't
>> have access to the R3.2 dom0 dmesg output for PCI spermissive mode, but
>> I recall before setting permissive mode dmesg suggested doing so.  This
>> is not the case in R4.0_rc3 however.
> 
>> Some dmesg output, if this gives anyone any ideas:
> 
>> [dom0 ~] lspci | grep -i network
>> 3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless
>> Network Adapter (rev 08)
> 
>> Before setting permissive mode:
>> [dom0 ~]$ sudo dmesg | grep
>> [7.222306] pci :3a:00.0: [14e4:43a3] type 00 class 0x028000
>> [7.222348] pci :3a:00.0: reg 0x10: [mem 0xdc40-0xdc407fff 64bit]
>> [7.222379] pci :3a:00.0: reg 0x18: [mem 0xdc00-0xdc3f 64bit]
>> [7.222618] pci :3a:00.0: supports D1 D2
>> [7.222619] pci :3a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
>> [7.222766] pci :3a:00.0: System wakeup disabled by ACPI
>> [8.053279] pciback :3a:00.0: seizing device
>> [   68.211970] xen_pciback: vpci: :3a:00.0: assign to virtual slot 0
>> [   68.212362] pciback :3a:00.0: registering for 4
>> [   68.217475] pciback :3a:00.0: enabling device ( -> 0002)
> 
> Did you get anything after that message? Permissive mode helps mostly
> with cases reported in dom0 dmesg with message like this:
> 
> pciback :03:00.0: Driver tried to write to a read-only
> configuration space field at offset 0x110, size 4. This may be harmless,
> but if you have problems with your device:
> 1) see permissive attribute in sysfs
> 2) report problems to the xen-devel mailing list along with details of
> your device obtained from lspci.
> 
> Interesting would be to see messages in sys-net about that device
> driver.
> You may also try updated kernel for VM, there is
> kernel-qubes-vm-4.14.13-1 package in current-testing repository:
> https://www.qubes-os.org/doc/software-update-dom0/#testing-repositories
> 
> 

Thanks, Marek--I will try the updated kernel (though sys-net has the
appropriate driver binary file, and this was working under R3.2 for many
months i.e. with older kernels).  Here are relevant messages from sys-net:

[user@sys-net ~]$ lspci -k
00:05.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless
Network Adapter (rev 08)
Subsystem: Dell Device 0023
Kernel modules: brcmfmac

[user@sys-net ~]$ sudo dmesg | grep brcmfmac
[1.703756] usbcore: registered new interface driver brcmfmac
[1.970170] brcmfmac: brcmf_chip_recognition: SB chip is not supported
[1.970185] brcmfmac: brcmf_pcie_probe: failed 14e4:43a3

[user@sys-net ~]$ modinfo brcmfmac | grep -E
'^(description|author|depends):'
description:Broadcom 802.11 wireless LAN fullmac driver.
author: Broadcom Corporation
depends:mmc_core,brcmutil,cfg80211

Trying advice from -
https://www.qubes-os.org/doc/wireless-troubleshooting - I tried
disabling/reenabling brcmfmac and some combinations of those others
(mmc_core,brcmutil,cfg80211; reversing remove/add order), but no luck.

I also tried using as the sys-net template qubes-template-debian-9 with
broadcom-sta-dkms and others (which I recall got this working for
running non-Qubes debian on this laptop), to no avail.

Thanks again,

-m0ssy

-- 
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/f00b4628-626f-d63c-cb5e-40415e1019ac%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)

2018-01-17 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jan 14, 2018 at 03:24:04AM -0800, Vít Šesták wrote:
> Good point, I forgot this one. of course, it would, but I am not sure if 
> Qubes is ready for that.
> 
> But it could be useful to use 32-bit stubdoms for those reasons. They do 
> rather I/O-bound work (=> minimal performance penalty) and they don't need so 
> much memory to utilize more than 32-bit pointers. (Also, using 32-bit 
> pointers can make a minor performance gain.)
> 
> On other VMs than stubdoms, it is not so easily deployable, because user 
> might have some 64-bit only software there. At least, it is impossible to 
> deploy it automatically (via update) without breaking anything.
> 
> It is possible to use 32-bit stubdom on a 64-bit system?

That's interesting idea. Simon, what do you think about it?

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpf8uUACgkQ24/THMrX
1yxZbgf/SFCNG6DfWSgriXHlfmNR/eOI6Bdzr+6EpI7rA5AjSu+wERZbFMBFDg0I
M5SKJUiKBexC96eUDktrG3wQnEhJ9aJHGFlQ/8jBSCx023yWpFYCtvKgjYlYEUjE
2J32lEvcT0Mv2e/7OouWO9w3oeJD+Qg189naRuKXZKJkF3B9z4iu7eTP9QePFbSg
6QEN3QHpHBZTfkufYJHuqdMyoZ0XiXaYnFBJQ83hsJSSllP1liCA0mKXLHoo+pD2
L/mVT/4Z337EiCdg/zYHoksWALr3I7rxbvRgzEmIyx6c1YbVZR3qfzYWe6VpPXjb
uW5/rt/XqSX5g+MaJLX/S78dOEeT2g==
=GqGk
-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/20180118010541.GD12450%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] PCI passthrough working in Qubes R4.0?

2018-01-17 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jan 17, 2018 at 11:54:23PM +, mossy-nw wrote:
> Dear Qubes community,
> 
> Has anyone using Qubes R4.0 been able to resolve any issues (e.g. with
> wifi) by setting PCI permissive mode? (as described in:)
> 
> https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues
> 
> I successfully used this in Qubes R3.2 to get wifi working for dell xps
> 13 9350 (bcm4350) but am having no luck using this method in R4.0_rc3.
> 
> This situation seems identical (driver errors that persist but
> nonetheless wifi works using permissive mode) resolved by in a previous
> (R3.2) qubes-users thread by miaoski --
> https://groups.google.com/forum/#!msg/qubes-users/m4GzpfOVBiQ/bf5XCEc-DQAJ
> 
> I'm hesitant to give up and go back to R3.2 on this machine, so I don't
> have access to the R3.2 dom0 dmesg output for PCI spermissive mode, but
> I recall before setting permissive mode dmesg suggested doing so.  This
> is not the case in R4.0_rc3 however.
> 
> Some dmesg output, if this gives anyone any ideas:
> 
> [dom0 ~] lspci | grep -i network
> 3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless
> Network Adapter (rev 08)
> 
> Before setting permissive mode:
> [dom0 ~]$ sudo dmesg | grep
> [7.222306] pci :3a:00.0: [14e4:43a3] type 00 class 0x028000
> [7.222348] pci :3a:00.0: reg 0x10: [mem 0xdc40-0xdc407fff 64bit]
> [7.222379] pci :3a:00.0: reg 0x18: [mem 0xdc00-0xdc3f 64bit]
> [7.222618] pci :3a:00.0: supports D1 D2
> [7.222619] pci :3a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
> [7.222766] pci :3a:00.0: System wakeup disabled by ACPI
> [8.053279] pciback :3a:00.0: seizing device
> [   68.211970] xen_pciback: vpci: :3a:00.0: assign to virtual slot 0
> [   68.212362] pciback :3a:00.0: registering for 4
> [   68.217475] pciback :3a:00.0: enabling device ( -> 0002)

Did you get anything after that message? Permissive mode helps mostly
with cases reported in dom0 dmesg with message like this:

pciback :03:00.0: Driver tried to write to a read-only
configuration space field at offset 0x110, size 4. This may be harmless,
but if you have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of
your device obtained from lspci.

Interesting would be to see messages in sys-net about that device
driver.
You may also try updated kernel for VM, there is
kernel-qubes-vm-4.14.13-1 package in current-testing repository:
https://www.qubes-os.org/doc/software-update-dom0/#testing-repositories

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpf7kIACgkQ24/THMrX
1yzK7Qf/bu/GFioi0K4hWy5L5DgzI08Q1CcIGoupw3gXXMhOxzecyy/Ak+W1xPYs
m1PBk7EAaCLa2Rr9iUCZiP2vXKiMEdKT6NvxDF7GU/c4YlLRiAHcOXtKnPQjy/GT
TH29dN4oXNLzQhgcXxVg7qKvigE3BeDY5a1EYbByW+2gacwRqjPxnDvTjnMx/G4r
h/GhdjOs4qhQYQ04OdbIBxmx4Yec+SWznS6xDCzaO3lA4f6/LiyW9+UiXpNb1o92
4yVTZEdEu086eurndITYnS2lEI7h3r7OP8YySFFKlZlaNMOkqZa+eOyGQLhUw+Jz
jNIEyqwwgJVj+ggKXd9Y9vt6Rki1dA==
=o9wL
-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/20180118004554.GC12450%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] PCI passthrough working in Qubes R4.0?

2018-01-17 Thread mossy-nw
Dear Qubes community,

Has anyone using Qubes R4.0 been able to resolve any issues (e.g. with
wifi) by setting PCI permissive mode? (as described in:)

https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues

I successfully used this in Qubes R3.2 to get wifi working for dell xps
13 9350 (bcm4350) but am having no luck using this method in R4.0_rc3.

This situation seems identical (driver errors that persist but
nonetheless wifi works using permissive mode) resolved by in a previous
(R3.2) qubes-users thread by miaoski --
https://groups.google.com/forum/#!msg/qubes-users/m4GzpfOVBiQ/bf5XCEc-DQAJ

I'm hesitant to give up and go back to R3.2 on this machine, so I don't
have access to the R3.2 dom0 dmesg output for PCI spermissive mode, but
I recall before setting permissive mode dmesg suggested doing so.  This
is not the case in R4.0_rc3 however.

Some dmesg output, if this gives anyone any ideas:

[dom0 ~] lspci | grep -i network
3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless
Network Adapter (rev 08)

Before setting permissive mode:
[dom0 ~]$ sudo dmesg | grep
[7.222306] pci :3a:00.0: [14e4:43a3] type 00 class 0x028000
[7.222348] pci :3a:00.0: reg 0x10: [mem 0xdc40-0xdc407fff 64bit]
[7.222379] pci :3a:00.0: reg 0x18: [mem 0xdc00-0xdc3f 64bit]
[7.222618] pci :3a:00.0: supports D1 D2
[7.222619] pci :3a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[7.222766] pci :3a:00.0: System wakeup disabled by ACPI
[8.053279] pciback :3a:00.0: seizing device
[   68.211970] xen_pciback: vpci: :3a:00.0: assign to virtual slot 0
[   68.212362] pciback :3a:00.0: registering for 4
[   68.217475] pciback :3a:00.0: enabling device ( -> 0002)

After setting permissive mode (and rebooting):
[dom0 ~]$ sudo dmesg | grep 3a:00
[7.256107] pci :3a:00.0: [14e4:43a3] type 00 class 0x028000
[7.256150] pci :3a:00.0: reg 0x10: [mem 0xdc40-0xdc407fff 64bit]
[7.256181] pci :3a:00.0: reg 0x18: [mem 0xdc00-0xdc3f 64bit]
[7.256419] pci :3a:00.0: supports D1 D2
[7.256421] pci :3a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[7.256568] pci :3a:00.0: System wakeup disabled by ACPI
[8.099473] pciback :3a:00.0: seizing device
[   57.896166] pciback :3a:00.0: enabling permissive mode
configuration space accesses!
[   57.896168] pciback :3a:00.0: permissive mode is potentially unsafe!
[   72.466856] xen_pciback: vpci: :3a:00.0: assign to virtual slot 0
[   72.467231] pciback :3a:00.0: registering for 2
[   72.472685] pciback :3a:00.0: enabling device ( -> 0002)

could it be anything to do with assign to virtual slot 0, or qvm-pci?

Many thanks for anyone's input,

-m0ssy

-- 
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/8eebd8f1-4f78-b069-3354-9b6e22ebd752%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] How to play videos in qubes? says needs codec H.264, Mpeg-4 something

2018-01-17 Thread Sergio Matta
Em quarta-feira, 17 de janeiro de 2018 08:05:07 UTC-2, Tim W  escreveu:
> On Tuesday, January 16, 2018 at 2:53:54 PM UTC-5, [799] wrote:
> > Hello Jerry, 
> > 
> > What are you trying to accomplish? 
> > I have a complete How-to which you can just follow per copy & paste to get 
> > a multimedia AppVM which is based on Debian-8 and can be used to listen to 
> > Spotify, watch DVD and use Amazon Prime or Spotify.
> > If you are interested I can send you the installation script.
> > 
> > [799]
> 
> why not post up the how to as I think many would find it beneficial with so 
> many new users.

I choose fusion to complete my appvm template. First I did a clone of the 
original template: qvm-clone fedora-25 vm-fedora
Then I start a terminal on vm-fedora and install all this:
sudo dnf config-manager --set-enabled rpmfusion-free rpmfusion-nonfree

sudo dnf install amrnb amrwb faad2 flac ffmpeg gpac-libs lame 
libfc14audiodecoder mencoder mplayer x264 x265 gstreamer-plugins-espeak 
gstreamer-plugins-fc gstreamer-rtsp gstreamer-plugins-good 
gstreamer-plugins-bad gstreamer-plugins-bad-free-extras 
gstreamer-plugins-bad-nonfree gstreamer-plugins-ugly gstreamer-ffmpeg 
gstreamer1-plugins-base gstreamer1-libav gstreamer1-plugins-bad-free-extras 
gstreamer1-plugins-bad-freeworld gstreamer1-plugins-base-tools 
gstreamer1-plugins-good-extras gstreamer1-plugins-ugly 
gstreamer1-plugins-bad-free gstreamer1-plugins-good

Then, I change the personal template to vm-fedora. And finally I open the menu 
"VM-Fedora: VM Settings" and at the Application tab I refresh the applications.

-- 
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/99dcdb85-ce01-4c12-9242-e130d22aae71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Graphic Tablet Compatibility (basic features)

2018-01-17 Thread Fabrizio Romano Genovese
Well, I blacklisted the relevant module and recompiled the driver as the guide 
said. The hid-core.c file hasn't the line described in the guide tho: It has a 
definition by cases that collapses  the wacom driver to the standard one if 
wacom specific driver is not loaded. In doubt, I eliminated any reference to 
Wacom in the hid-core.c, and replaced the old drivers with the new one. Still, 
no effect whatsoever. 

Interestingly enough, giving 
cat /sys/kernel/debug/usb/devices
tells me that 
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  4 Spd=12   MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs=  1
P:  Vendor=056a ProdID=00dd Rev= 1.02
S:  Manufacturer=Wacom Co.,Ltd.
S:  Product=CTL-470
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr= 98mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=  10 Ivl=2ms
I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=82(I) Atr=03(Int.) MxPS=  64 Ivl=2ms

So the driver used is the right one. Only, usbhid doesn't recognize my tablet 
as a mouse. I feel like I'm out of options :/

-- 
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/27e9182d-6bb7-4271-83e8-1d81eee6bede%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] DebianTemplate for DVM with additional software is flagging an update(despite already updated)? 3.2

2018-01-17 Thread donoban
On 01/17/2018 04:33 PM, vel...@tutamail.com wrote:
> Running Qubes 3.2the Debian Template I created for printing is showing an 
> update is needed in my GUI interface (Green arrow pointing down). I updated 
> this template and other Debian templates but my printer template keeps 
> showing an update is needed?
> 
> *Tried an update again from GUI-Terminal said nothing needed
> *Restarted computer
> *Did a manual update directly from terminal using: sudo apt-get update && 
> sudo apt-get dist-upgrade
> 
> Is there another option I can try before rebuilding the template?
> 
> Thanks
> 

I had this problem with a Debian template with backports enabled. I am
not sure about the source of the problem but I don't think you will fix
it rebuilding the template.

One day I discovered that running apt-get update/upgrade on the template
was reporting different results if it has internet available. With
internet it was up to date, without it it had tons of packages for
upgrade. Finally I checked some packages were at right version and I
also was receiving updates when debian-security announced them so I
stopped worrying about it.

Probably some of my offline AppVMs was reporting  an update was needed
erroneously.

-- 
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/25cc0505-a379-cb6e-146c-15174615a744%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] Please help with 8th Generation Intel i5

2018-01-17 Thread donoban
On 01/17/2018 08:24 PM, Krišjānis Gross wrote:
> Hi, 
> 
> Was using Qubes 3.2 on 4th generation i5 processor when decided to upgrade my 
> hardware. 
> 
> Purchased 8th gen i5 processor and MB. Now when I start my Qubes only dom0 is 
> started. no other VM is started unfortunately. 
> 
> Here is the hardware details:
>MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp
>CPU: Intel® Core™ i5-8600K 
> https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz
>RAM: 16 GB DDR4
> 
> 
> Qubes 3.2. boots but feels very slow. e.g. when I type the characters appear 
> with considerable delay. Mouse is not working. I can only do something with 
> PS2 keyboard. 
> 
> I tried to run Qubes installation but failed to do that. 3.2 did not start 
> the installation at all. 
> Qubes 4.0rc3 installation did get to some point and resulted in error. 
> I have attached some screen shots of 4.0 installation.
> 
> Not sure what to do next. Read in some other topics that others had an issue 
> with new hardware. 
> 
> Please help to resolve this. I really really want to continue using Qubes. it 
> is such an awesome system! 
> 

Try to switch to log or shell with alt+tab or ctrl+alt+F2 / ctrl+alt+F3

If you get a shell look in /tmp for log files

Did you try another Linux distribution?

-- 
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/c4aff5eb-a4c5-df12-0569-8ab0441de037%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] Re: QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)

2018-01-17 Thread Ilpo Järvinen
On Wed, 17 Jan 2018, Lorenzo Lamas wrote:

> On Thursday, January 11, 2018 at 3:57:50 PM UTC+1, Andrew David Wong wrote:
> > ## Qubes 3.2
> > 
> > For Qubes 3.2, we plan to release an update that will make almost all
> > VMs run in a fully-virtualized mode. Specifically, we plan to backport
> > PVH support from Qubes 4.0 and enable it for all VMs without PCI
> > devices. After this update, all VMs that previously ran in PV mode (and
> > that do not have PCI devices) will subsequently run in PVH mode, with
> > the exception of stub domains. Any HVMs will continue to run in HVM
> > mode.
> 
> Is this the shim-based approach from XSA-254?

No, it won't be a shim-based approach (see also the Marek's mail in this 
thread).

> Then it should be made clear that the VM's will be more vulnerable to 
> Meltdown: 

Even if shims would be used, that "more" claim is false as Meltdown 
against the host hypervisor from PVs that are currently used in R3.2 
expose both host and also the guest through the host hypervisor (its 
memory). With shims only the guest is still vulnerable, this time through 
the intermediate xen instance running in the HVM/PVH encapsulating the PV 
guest. Clearly it's "less" vulnerable rather than "more".

Qubes has been trying to migrate away from PVs altogether (rather than 
e.g., placing PVs into those shims) due to PV vulnerabilities in general. 
In fact, even before these HW vulnerabilities were discovered, the process 
towards PVH was ongoing which is why R4.0 rcs as is are much better 
protected already. These vulnerabilities only accelerated this process.
There will be, unfortunately, be one limitation to this migration still 
due to PCI passthrough: VMs with PCI devices need to remain PV (or their 
stubdoms in R4.0).

> "Note this shim-based approach prevents attacks on the host, but leaves
> the guest vulnerable to Meltdown attacks by its own unprivileged
> processes; this is true even if the guest OS has KPTI or similar
> Meltdown mitigation."
> https://xenbits.xen.org/xsa/xsa254/README.which-shim

Also, note that one of the fundamental assumption with Qubes security 
model is that the VMs _will get compromised_ (regardless of HW exploits). 
What Qubes aims to protect against is escalation from a compromised VM
to host or to another VM.


-- 
 i.

-- 
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/alpine.DEB.2.20.1801172252250.29076%40whs-18.cs.helsinki.fi.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - SAMSUNG_ELECTRONICS_CO___LTD_-300E4C_300E5C_300E7C

2018-01-17 Thread Benjamin Depaula


-- 
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/CAFfkFnEfDESjtLPEUqJFRgmvUoQZKH71uBaY7%2BoDHkESKjdnmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-SAMSUNG_ELECTRONICS_CO___LTD_-300E4C_300E5C_300E7C-20180117-181047.yml
Description: application/yaml


Re: [qubes-users] Re: sys-usb / template install yubikey tools ?

2018-01-17 Thread Alex Dubois
On Wednesday, 17 January 2018 15:15:45 UTC, ThierryIT  wrote:
> No, I am still under R3.2
> 
> Le mercredi 17 janvier 2018 16:54:58 UTC+2, awokd a écrit :
> > On Wed, January 17, 2018 2:09 pm, ThierryIT wrote:
> > > "https://github.com/adubois/qubes-app-linux-yubikey;
> > >
> > >
> > > Le mercredi 17 janvier 2018 16:05:52 UTC+2, awokd a écrit :
> > >
> > >> On Wed, January 17, 2018 1:09 pm, ThierryIT wrote:
> > >>
> > >>> Nobody ?
> > >>>
> > >>>
> > >>>
> > >>> Le mercredi 17 janvier 2018 09:23:34 UTC+2, ThierryIT a écrit :
> > >>>
> > >>>
> >  Hi,
> > 
> > 
> > 
> >  I am going to install a new sys-usb.
> >  I have before to install all what I need to the template (fedora-26)
> >   first. When following your procedure:
> > 
> > 
> >  ykpers has been installed but: I cannot do the same for
> >  qubes-yubikey-vm and qubes-yubikey-dom0 :
> > 
> >  no match for argument
> > 
> >  ideas ?
> > >>
> > >> Not quite sure what you are trying to do here. What procedure? What
> > >> command are you entering?
> > 
> > Are you trying this on Qubes 4.0? Those Yubikey packages might not be in
> > the Qubes repo yet.

Hi,

I have not maintained this for some time. So long that I can't remember if the 
packages had been created/tested, I don't think they have.

Best is you follow the steps to build it on a new temporary VM, don't be afraid 
it should not be too hard:
- Execute the yum command in "Build dependancies"
- Also install pam-devel
- Follow the steps in preparing the build and build
- Deploy the code in Dom0 and the USB VM.

I am about to upgrade to Qubes 4.0 rc4 (when released) so won't probably be 
able to help until this is done.

Any help from someone who is used to packaging under Fedora would be nice.

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/24175c57-8792-4beb-b1b4-ab96f9beccdf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: off topic - invite codes to 'riseup'

2018-01-17 Thread juandi1
I am also in need of two invite codes to sign up for riseup.net if anyone could 
help it would be greatly appreciated. thanx 

-- 
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/dfa8557b-e6e3-400a-99e0-d042d5950f5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to play videos in qubes? says needs codec H.264, Mpeg-4 something

2018-01-17 Thread cooloutac
On Tuesday, January 16, 2018 at 12:40:16 PM UTC-5, jer...@disroot.org wrote:
> i can't install this codec from fedora 26 from software add ons.. also i've 
> tried doing yum search h.264, there's nothing that seems like this codec..

Its been a while,  but I think its gstreamer1-libav.Like another poster 
said it might be just easier to use debian instead.

-- 
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/bff583e3-19b0-4107-8d8a-fcb53aa6885b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] How to play videos in qubes? says needs codec H.264, Mpeg-4 something

2018-01-17 Thread Steve Coleman
Use DNF to look for ffmpeg, and install that, if it is not already. 
Likely it is not installed.


After that, if it still does not play, then start by telling us what app 
you are using to play the video. There are usually plugins that connect 
an app to the otherwise encumbered/licensed/patented algorithms, which 
is the bane of free and open software. The plugin architecture allows a 
separation of the encumbered parts from that of the software application 
core.



On 01/16/2018 11:50 AM, jerr...@disroot.org wrote:
i can't install this codec from fedora 26 from software add ons.. also 
i've tried doing yum search h.264, there's nothing that seems like this 
codec..


--
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/0fceeb06479346b8c2dbdf67ea572f59%40disroot.org 
.

For more options, visit https://groups.google.com/d/optout.


--
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/7fc3ad35-56d5-5027-7f68-f0784baf47c0%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)

2018-01-17 Thread Lorenzo Lamas
On Thursday, January 11, 2018 at 3:57:50 PM UTC+1, Andrew David Wong wrote:
> ## Qubes 3.2
> 
> For Qubes 3.2, we plan to release an update that will make almost all
> VMs run in a fully-virtualized mode. Specifically, we plan to backport
> PVH support from Qubes 4.0 and enable it for all VMs without PCI
> devices. After this update, all VMs that previously ran in PV mode (and
> that do not have PCI devices) will subsequently run in PVH mode, with
> the exception of stub domains. Any HVMs will continue to run in HVM
> mode.

Is this the shim-based approach from XSA-254?
Then it should be made clear that the VM's will be more vulnerable to Meltdown:
"Note this shim-based approach prevents attacks on the host, but leaves
the guest vulnerable to Meltdown attacks by its own unprivileged
processes; this is true even if the guest OS has KPTI or similar
Meltdown mitigation."
https://xenbits.xen.org/xsa/xsa254/README.which-shim

-- 
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/2ed7448b-7d79-479b-ba9f-85a5583bbbcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] DebianTemplate for DVM with additional software is flagging an update(despite already updated)? 3.2

2018-01-17 Thread velcro
Running Qubes 3.2the Debian Template I created for printing is showing an 
update is needed in my GUI interface (Green arrow pointing down). I updated 
this template and other Debian templates but my printer template keeps showing 
an update is needed?

*Tried an update again from GUI-Terminal said nothing needed
*Restarted computer
*Did a manual update directly from terminal using: sudo apt-get update && sudo 
apt-get dist-upgrade

Is there another option I can try before rebuilding the template?

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/58e39c33-b5e2-437e-9db5-e33e9d3959e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: sys-usb / template install yubikey tools ?

2018-01-17 Thread ThierryIT
No, I am still under R3.2

Le mercredi 17 janvier 2018 16:54:58 UTC+2, awokd a écrit :
> On Wed, January 17, 2018 2:09 pm, ThierryIT wrote:
> > "https://github.com/adubois/qubes-app-linux-yubikey;
> >
> >
> > Le mercredi 17 janvier 2018 16:05:52 UTC+2, awokd a écrit :
> >
> >> On Wed, January 17, 2018 1:09 pm, ThierryIT wrote:
> >>
> >>> Nobody ?
> >>>
> >>>
> >>>
> >>> Le mercredi 17 janvier 2018 09:23:34 UTC+2, ThierryIT a écrit :
> >>>
> >>>
>  Hi,
> 
> 
> 
>  I am going to install a new sys-usb.
>  I have before to install all what I need to the template (fedora-26)
>   first. When following your procedure:
> 
> 
>  ykpers has been installed but: I cannot do the same for
>  qubes-yubikey-vm and qubes-yubikey-dom0 :
> 
>  no match for argument
> 
>  ideas ?
> >>
> >> Not quite sure what you are trying to do here. What procedure? What
> >> command are you entering?
> 
> Are you trying this on Qubes 4.0? Those Yubikey packages might not be in
> the Qubes repo yet.

-- 
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/79f4fc4c-14a6-4d44-a7b3-e752aa8cdb29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: sys-usb / template install yubikey tools ?

2018-01-17 Thread 'awokd' via qubes-users
On Wed, January 17, 2018 2:09 pm, ThierryIT wrote:
> "https://github.com/adubois/qubes-app-linux-yubikey;
>
>
> Le mercredi 17 janvier 2018 16:05:52 UTC+2, awokd a écrit :
>
>> On Wed, January 17, 2018 1:09 pm, ThierryIT wrote:
>>
>>> Nobody ?
>>>
>>>
>>>
>>> Le mercredi 17 janvier 2018 09:23:34 UTC+2, ThierryIT a écrit :
>>>
>>>
 Hi,



 I am going to install a new sys-usb.
 I have before to install all what I need to the template (fedora-26)
  first. When following your procedure:


 ykpers has been installed but: I cannot do the same for
 qubes-yubikey-vm and qubes-yubikey-dom0 :

 no match for argument

 ideas ?
>>
>> Not quite sure what you are trying to do here. What procedure? What
>> command are you entering?

Are you trying this on Qubes 4.0? Those Yubikey packages might not be in
the Qubes repo yet.

-- 
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/aa0b03063ad9be3e537c78c4eca9b5f7.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: sys-usb / template install yubikey tools ?

2018-01-17 Thread ThierryIT
"https://github.com/adubois/qubes-app-linux-yubikey;

Le mercredi 17 janvier 2018 16:05:52 UTC+2, awokd a écrit :
> On Wed, January 17, 2018 1:09 pm, ThierryIT wrote:
> > Nobody ?
> >
> >
> > Le mercredi 17 janvier 2018 09:23:34 UTC+2, ThierryIT a écrit :
> >
> >> Hi,
> >>
> >>
> >> I am going to install a new sys-usb.
> >> I have before to install all what I need to the template (fedora-26)
> >> first. When following your procedure:
> >>
> >>
> >> ykpers has been installed but: I cannot do the same for qubes-yubikey-vm
> >> and qubes-yubikey-dom0 :
> >>
> >> no match for argument
> >>
> >> ideas ?
> 
> Not quite sure what you are trying to do here. What procedure? What
> command are you entering?

-- 
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/f465fd71-bb25-4050-91be-ca577635c7f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: sys-usb / template install yubikey tools ?

2018-01-17 Thread 'awokd' via qubes-users
On Wed, January 17, 2018 1:09 pm, ThierryIT wrote:
> Nobody ?
>
>
> Le mercredi 17 janvier 2018 09:23:34 UTC+2, ThierryIT a écrit :
>
>> Hi,
>>
>>
>> I am going to install a new sys-usb.
>> I have before to install all what I need to the template (fedora-26)
>> first. When following your procedure:
>>
>>
>> ykpers has been installed but: I cannot do the same for qubes-yubikey-vm
>> and qubes-yubikey-dom0 :
>>
>> no match for argument
>>
>> ideas ?

Not quite sure what you are trying to do here. What procedure? What
command are you entering?

-- 
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/10c35cb9c19a9aa99269b0bce776f1f5.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes enthusiast to support small company in Zug, Switzerland (MUST be resident within the area)

2018-01-17 Thread mbaarchos
Dear Qubes Community,

I appreciate the positive feedback received on the previous post, but I am 
reaching out again this way, as I would like more candidates for this part time 
"jack of all trades" IT position, which requires good knowledge of Qubes to an 
extent where he/she is able to implement this in a small office environment 
with a handful of users. There will also be other tasks, such as setting up 
alarm system / video monitoring, networking infrastructure, server, secure 
communications etc. etc. 

We envision this can be 50 - 100% workload (in large parts up to you and your 
other commitments) for a few weeks, after which we expect possibly 10 - 25% 
workload after that (can possibly be evening/weekend work, maybe remotely).

In short, very flexible, BUT it is a 100% requirement that you are able to come 
to our office in Sihlbrug/Baar in Switzerland (just off the highway ... busstop 
200 meters away). Whilst appreciating interest from abroad, that is just not 
feasable for the tasks at hand.

Due to the nature of work, and given that we cannot offer a full time position, 
we would expect a young person who is studying or is an apprentice, who would 
like to have some additional challenges and earn some extra money. However, it 
could also be someone older who's in between jobs. 

Important is knowledge/experience with Qubes, general IT/networking, 
electronics and the ability to handle and solve challenges as well as being 
flexible, self-starter and work independently. 

If you are interested, please send me a short description of your background 
and your motivation and general situation as well as contact details.

Also, if you know of someone who could be interested, please let them know (or 
let me know). 

I will be looking forward to hearing from you on the following e-mail address: 

mba (at) corpconsult (dot) info or as a reply to this post.

Best regards 
Mogens Berg Andersen 
MBA Consulting GmbH

-- 
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/52a411a0-588b-49cc-9808-116d1cd3ba35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: sys-usb / template install yubikey tools ?

2018-01-17 Thread ThierryIT
Nobody ?

Le mercredi 17 janvier 2018 09:23:34 UTC+2, ThierryIT a écrit :
> Hi,
> 
> I am going to install a new sys-usb.
> I have before to install all what I need to the template (fedora-26) first.
> When following your procedure:
> 
> ykpers has been installed but:
> I cannot do the same for qubes-yubikey-vm and qubes-yubikey-dom0 :
> 
> no match for argument
> 
> ideas ?
> 
> Thx

-- 
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/e52f7ec9-af27-4a45-8ce8-b00234956475%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: ANN: Qubes network server

2018-01-17 Thread Manuel Amador (Rudd-O)
On 10/09/2017 04:49 PM, Thierry Laurion wrote:
>
> Considering Qubes 4.x has switched to HVM, what needs to be done to support 
> this mode of operation? 
> Opened a ticket to track this issue: 
> https://github.com/Rudd-O/qubes-network-server/issues/4
>

Thank you for opening the ticket.  It may be difficult for me to adapt
to 4.0, so I kindly request anyone with the required skillset to send a
pull request adapting it to 4.0.

-- 
Rudd-O
http://rudd-o.com/

-- 
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/ae3a61fa-809e-d388-1358-25727847974a%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Lenovo ThinkPad, won't boot

2018-01-17 Thread Tim W
On Monday, January 15, 2018 at 6:23:55 PM UTC-5, demio...@gmail.com wrote:
> My Lenovo ThinkPad fails to boot after installing Qubes.  I had to boot the 
> USB drive via legacy boot for Qubes to install at all, but the EFI setup 
> doesn't happen.


need a model number and spec.  should not need legacy mode if hardware/cpu 
matches tp qubes oversion 3 vs 4s 

-- 
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/f03d3112-29ba-4d1c-a421-98a821893b8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] How to play videos in qubes? says needs codec H.264, Mpeg-4 something

2018-01-17 Thread Tim W
On Tuesday, January 16, 2018 at 2:53:54 PM UTC-5, [799] wrote:
> Hello Jerry, 
> 
> What are you trying to accomplish? 
> I have a complete How-to which you can just follow per copy & paste to get a 
> multimedia AppVM which is based on Debian-8 and can be used to listen to 
> Spotify, watch DVD and use Amazon Prime or Spotify.
> If you are interested I can send you the installation script.
> 
> [799]

why not post up the how to as I think many would find it beneficial with so 
many new users.

-- 
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/19abb006-4b28-4003-8d0c-62826a776427%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Troubleshooting IOMMU compatibility

2018-01-17 Thread Zrubi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 01/17/2018 01:58 AM, jspiegelm...@airmail.cc wrote:
> so I'm wondering how to troubleshoot it and see if it's just an 
> improper configuration by the motherboard manufacturers that can
> be fixed in some way.
> 

The only way is to ask your device manufacturer.
As the proper IOMMU support is depends on :
- - CPU
- - motherboard chipset
- - BIOS

all of those are just a "black box" for us.


(I have seen some cheap devices where the BIOS was hiding the
virtualization features intentionally)


- -- 
Zrubi
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJaXxANAAoJEBozWgtUjzdkdnsQAMeMT81QNZipus1LZv6xuYn6
yfWd23l0XUNtXMZa/ULot9UbBjrnn7UlRcgt2kqBgWAFUUHv1ouQKucQoeI99nF8
1FKO2477IbRJj8rAWk8iDgQnLbBsyh/1KIe8eiGS9rDSEblnpHDmNzo/GHRW887n
BK1sufp4YlfTmXV+5KZjGMt4FIeyTIR1Q9Q1ZcjiKhQjq+DHi9v3f4Aw8RZ2vKgZ
17VsjRRP+akXMVSi/uBP7uzmRlKpbNMN2ZzKC/BamW1fqhjwDzHyWbAUS4h+kfG9
ZFLtyNSh71+7qfLBZoQOOHI41qBXPIqvSNMUPlRZSX/efD0t5nOaHBo8xrWzvxTf
jMxcD7xQ7lHyMugTSAMla7yt0gXXgmv+g3m5mP/mFFJARmWWug08LV+8VtDnZgfR
C3v91uKISdMCOT02Lsk4jg322/KdFXkxH+orOjige+2GceGlwgxGdYKY5bkc9Jk3
kKrVcJJw0lKBa8D9zOGWcqJ2ZWIKZyDnFX2YTJsfhzE8yY+LvWJ8bMo7ZOPZ1KBZ
S+dhMdMQQYrPv8hCf75KkbLhwdJGqwaqwsXrif7h+rnPm1bjsqvBdU6M+vAU+azR
o7DbJVZAtgdmAJrxt0WVahjqK/iFXw+Id18jR8EoYhIXHDZpUK1e1EJEjtGgJBoz
54E0c+7AFvOb/86fiMRH
=o5/W
-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/f8d4a276-e41a-714f-4e7b-da6f2a960be9%40zrubi.hu.
For more options, visit https://groups.google.com/d/optout.