-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2016-10-08 01:14, Shakthi Kannan wrote:
> Hi,
>
> I have installed Qubes 3.1 on a Lenovo E460 with VT-d enabled in the
> BIOS. Also, booting with "Legacy only" and "Secure boot" disabled.
>
> (I initially tried with 3.2, but, after loading initrd.img, the boot
> messages proceeded until "Dom0 has 2 CPUS" and the installer failed to
> start.)
>
> Couple of questions:
>
> 1. I would like to know if there are any proprietary binary blobs in
> Qubes OS. If yes, how can they be replaced? I came across this thread:
>
>
https://groups.google.com/forum/m/#!topic/qubes-devel/w2ssPzYemQ8
>
> Is dom0 completely free? I do not have linux-firmware installed and
> mostly use ethernet or USB-wireless. Suspend/resume work fine.
>
AFAIK, dom0 is *not* completely free of proprietary binary blobs.
I don't know how (or even whether) they can be replaced, but someone
else here probably does.
> 2. I see Puri.sm shipping Qubes OS. How is it different from the 3.1
> or 3.2 release? Please let me know.
>
It should be either Qubes 3.1 or Qubes 3.2, not something different.
You may have to ask Purism which version they're shipping if they
don't specify the version.
> I shall submit the HCL report soon.
>
> Thanks!
>
> SK
>
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJX+Zz+AAoJENtN07w5UDAwIToP/0JgTcBxfmJvkBu2B2L3RxvE
CjY3/VXEa8i/dUZspGmKyuZ1GmqBB2NVgOsCyWGiLrZXRLNLNMVlpyJKEjsqBP26
UlKhJPOeVwBMI0OHcWeg0BWQV1lgqJ/16XFiR9uFJ+LPWiEhbMDKnhhJYDKTNwWe
fZ0bEQTCGrHmfKMApNYdzRMn9D9QCWjbnAiSt1I/eH1G/+ztDcWkdmgVtm/HXDtG
abjUUkkvScojNIqsXTXAbNe58knh2HKhEZxVOQ22LqwKBieq0VCM1SUeWPXyJvhz
oH/1r+AGU724JBNAo8DMqHw21RIaQqh7OewIJoYeWA2yND4moqfjnppVkrXty0ye
DP3AzEdFovemJxttIf+PdaHTuvpYBfgivYOrhv0a+yf0+3ZlLF1+mBSP6cWuq7th
6VdpN/ZaXOslwjX0Ew5J6hBhyjmNFnIbVNDTa5aeVVpMNe13DBM8/SzEc/qam8+U
+7JHgcfE3zuEMBFyw4nA8L24r0H6+Pz3dfG6V4WY7X5H2h4ydhU0V3ePULLRGn0D
+y8aoHXZGP3Os55Z3h+/Qv+M/Cc/sWIUZoL4shS65LOeQNugjtLvme07Vh+kIUI/
2tVsnamL6QJuQuCc2I3bING1kxYXXhwmnIkZKtj/0QHKmYhN63e41v2omZbODyli
8OHlyZjG+d23nd7KNrKW
=iCp1
-----END PGP SIGNATURE-----