Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

HCL cleanup, fixing links

Browse Source
This commit is contained in:
Hakisho Nukama 2015-05-09 12:59:07 +00:00
parent b3e0483a6d
commit 10d7109f98
No known key found for this signature in database
GPG Key ID: F942FF5D3C618D64
8 changed files with 15 additions and 2801 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
BuildingNonFedoraTemplate.md
View File

@ -136,7 +136,7 @@ As soon as you manage to make qrexec and qubes-gui-agent working, it should be s
Several XEN libraries are required for Qubes to work correctly. In fact, you need to make xenstore commands working before anything else. For this, Qubes git can be used as several patches have been selected by Qubes developpers that could impact the activity inside a VM. Start be retrieving a recent git and identify how you can build a package from it: `git clone git://git.qubes-os.org/marmarek/xen` Several XEN libraries are required for Qubes to work correctly. In fact, you need to make xenstore commands working before anything else. For this, Qubes git can be used as several patches have been selected by Qubes developpers that could impact the activity inside a VM. Start be retrieving a recent git and identify how you can build a package from it: `git clone git://git.qubes-os.org/marmarek/xen`
Find the .spec file in the git repository (this is the file being used to build rpm packages), and try to adapt it to your OS in order to build a package similar to the target 'xen-vm'. For example, a PKGBUILD has been created for [ArchLinux?](/doc/ArchLinux/) and can be found on [http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD](http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD). Find the .spec file in the git repository (this is the file being used to build rpm packages), and try to adapt it to your OS in order to build a package similar to the target 'xen-vm'. For example, a PKGBUILD has been created for [ArchLinux](/doc/Templates/Archlinux/) and can be found on [http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD](http://aur.archlinux.org/packages/qu/qubes-vm-xen/PKGBUILD).
Don't be afraid with the complexity of the PKGBUILD, most of the code is almost a copy/paste of required sources and patches found in the .spec file provided in the git repository. Don't be afraid with the complexity of the PKGBUILD, most of the code is almost a copy/paste of required sources and patches found in the .spec file provided in the git repository.

619
HCL-R2B2.md
View File

@ -1,619 +0,0 @@
---
layout: doc
title: HCL-R2B2
permalink: /doc/HCL-R2B2/
redirect_from: /wiki/HCL-R2B2/
---
Hardware Compatibility List (HCL) for R2B2 Qubes OS Release
===========================================================
**Note:** The HCL is a compilation of reports generated and submitted by users. Except in the case of developer-reported entries, the Qubes team has not independently verified the accuracy of these reports. If using the list to make a purchasing decision, we recommend that you first test the hardware yourself, if possible.
**Legend**
**Background colors**
Green
The reporter has clearly stated that **all** components and features are working correctly.
White
The reporter has sent an HCL Info output which indicates everything is OK without any comments.
Yellow
Some non-required feature is missing (e.g., VT-d), or manual tweaking is required in order to get some components to work.
Red
Some primary feature is not working. These are usually machines with poor or nonexistent Linux support in general.
**Marks**
OK
The feature is working correctly.
X
The feature does not work or is not present.
\*
An asterisk (\*) indicates that some kind of tweaking is needed.
 
A blank cell indicates that we lack information about a feature.
**Device**
**Qubes R1**
**Qubes R2 Beta2**
**Reported by**
Standard feautures
VT-d
Remarks
Standard features
VT-x
(HVM)
VT-d
Remarks
**Developer Reported Machines**
Lenovo Thinkpad T420
OK
OK
Qubes core developers
Lenovo Thinkpad T420s
(Intel HD graphics; Sandy Bridge; i5-2520M)
OK
OK
OK
OK
OK
Requires kernel 3.2.30 to support S3 sleep (the default kernel S3 sleep causes system reboot)
Qubes core developers
Lenovo Thinkpad T61
(Nvidia Quadro NVS 140M)
OK
X
Qubes core developers
Samsung X460
OK
X
Qubes core developers
Sony Vaio Z 12
(2010 edition)
OK
OK
[read more](/trac/wiki/SonyVaioTinkering)
OK
OK
OK
[read more](/trac/wiki/SonyVaioTinkering)
Qubes core developers
Dell Latitude E6420
(Intel HD graphics; Sandy Bridge; i5-2520M)
OK
OK
needs kernel 3.4.17+
OK
OK
OK
Suspend doesn't work on 3.7.6 kernel, but work on 3.7.4
Qubes core developers
**User Reported Laptops**
Apple MacBookPro
(i7 M620)
X
OK
X
[read more](https://groups.google.com/d/topic/qubes-devel/hag-MQDH_Vs/discussion)
[Alex Dubois](https://groups.google.com/d/msg/qubes-devel/hag-MQDH_Vs/pmJ7TIWUWAsJ)
Apple MacBookPro
(Intel HD Graphics, Ivy Bridge, i5-3210M)
X
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/ZbjrseLxuPQ/discussion)
[ph145h](https://groups.google.com/d/msg/qubes-users/ZbjrseLxuPQ/5Jx5DvpnwMMJ)
ASUS UX-31
\*
[Stephen Boyd](https://groups.google.com/d/topic/qubes-devel/6I07Bbzn5M4/discussion)
ASUS X55A
X
X
[read more](https://groups.google.com/d/topic/qubes-devel/2csjvHia9Rw/discussion)
X
X
X
[read more](https://groups.google.com/d/topic/qubes-devel/2csjvHia9Rw/discussion)
[Zrubi](https://groups.google.com/d/msg/qubes-devel/2csjvHia9Rw/NRsqR0g6wIMJ)
Dell Latitude E4300
(Intel GMA 4500M; Mobile 4 Series Chipset; Core2 Duo P9600)
X
OK
OK
[read more](https://groups.google.com/d/topic/qubes-devel/LNJqSbH0cOQ/discussion)
[Pablo Costa](https://groups.google.com/d/msg/qubes-devel/LNJqSbH0cOQ/VC9EwEDrXMQJ)
Dell Latitude 5520
OK
OK
[read more](https://groups.google.com/group/qubes-devel/msg/7418e7084c2de99f?hl=en)
[Erik Edin](https://groups.google.com/group/qubes-devel/msg/7418e7084c2de99f?hl=en)
Dell Latitude E6320
(Intel HD graphics; Sandy Bridge; i5-2540M; BIOS: A06)
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/FyA7_Kzw1WA/discussion)
[Alex](https://groups.google.com/d/msg/qubes-users/F-jVh62ANak/s57rqUWTY7kJ)
Dell Latitude E6430
(Intel HD graphics; Ivy Bridge; i5-3340M, BIOS: A11)
OK
OK
OK
[Zrubi](https://groups.google.com/d/msg/qubes-users/pAVGe04ZC48/AJwY6yd7LeIJ)
Dell Latitude E6520
OK
OK
[read more](https://groups.google.com/group/qubes-devel/msg/340afc6fc2d06d0e)
[Steven Collins](https://groups.google.com/group/qubes-devel/msg/340afc6fc2d06d0e)
Dell PowerEdge T110 II
(onboard Matrox; Xeon E3-1230)
OK
OK
[Geoff](https://groups.google.com/group/qubes-devel/msg/8a894915909eeaee)
Dell Precision M4600
(i7-2860QM; NVIDIA Quadro 1000M)
OK
OK
[nqe](https://groups.google.com/group/qubes-devel/browse_thread/thread/ddf35d12a35f96a3)
Dell XPS 13
(i5; intel HD; sandy bridge; BIOS A03)
OK
OK
[read more](https://groups.google.com/d/msg/qubes-devel/jamRkZJDC0g/KTniY0Y3dioJ)
[j](https://groups.google.com/d/msg/qubes-devel/7JumqdldVJM/n9TiDVxc2jkJ)
Dell XPS 13 (L322X)
(i7-3537U; intel HD; Ivy Bridge; BIOS A09)
\*
OK
X
[read more](https://groups.google.com/d/topic/qubes-users/21kqNBzJLPw/discussion)
[Brian J Smith-Sweeney](https://groups.google.com/d/msg/qubes-users/21kqNBzJLPw/e74SMRweTMsJ)
Fujitsu S751
(HD3000; QM67; i5-2520M; BIOS 1.18)
OK
OK
OK
OK
OK
needs kernel downgrade to 3.7.4
[Zrubi](https://groups.google.com/forum/#!msg/qubes-devel/xoyNCigBvFE/ER61L6TbVpwJ)
HP EliteBook 8540p
(Arrandale; NVIDIA GT216; i5-2540M; BIOS:F.0C)
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/o_FTsPW6GD8/discussion)
[Olivier Médoc](https://groups.google.com/d/msg/qubes-users/o_FTsPW6GD8/bjAD-CSpRKsJ)
HP EliteBook 8560p
(Sandy Bridge; ATI Caicos; i5-2540M; BIOS: F.08)
\*
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/o_FTsPW6GD8/discussion)
[Olivier Médoc](https://groups.google.com/d/msg/qubes-users/o_FTsPW6GD8/bjAD-CSpRKsJ)
HP Pavilion Sleekbook 14-B030TU
(Ivy Bridge; Intel HD Graphics; i5-3317; BIOS F.06)
OK
OK
OK
[Stephen Boyd](https://groups.google.com/d/msg/qubes-devel/ZC_SQJhXVOM/4aLjEc7GIsUJ)
Lenovo Thinkpad Edge E130
(Ivy Bridge; HD Graphics i3-3217U; BIOS: 2.05)
OK
OK
OK
[Danny Cautaert](https://groups.google.com/d/msg/qubes-devel/kGnZKZ9ILKA/2vpzltNW3K4J)
Lenovo Thinkpad T430
(Ivy Bridge; HD Graphics; i5-3360M; BIOS: 2.51)
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-devel/LSVluAZ9Udo/discussion)
[Alex Dubois](https://groups.google.com/d/msg/qubes-devel/LSVluAZ9Udo/Fl3jmt4tWssJ)
Lenovo Thinkpad T430s
(i5-3320M)
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/V4PQYEBuoSg/discussion)
[cprise](https://groups.google.com/d/msg/qubes-users/V4PQYEBuoSg/udLCHyR6RUUJ)
Lenovo Thinkpad T430U
(Ivy Bridge; HD Graphics +GT 620M; i7-3517M; BIOS: 2.08)
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-devel/Z9M_k3i6dxU/discussion)
[tigerbeard](https://groups.google.com/d/msg/qubes-devel/Z9M_k3i6dxU/09CqBppyMnsJ)
Lenovo Thinkpad W510
(nVidia; i7-Q820)
OK
OK
[read more](https://groups.google.com/forum/#!msg/qubes-devel/TgDWwBs36yA/IUFZPHs716cJ)
[Sebastian Hültenschmidt](https://groups.google.com/forum/#!msg/qubes-devel/TgDWwBs36yA/IUFZPHs716cJ)
Lenovo Thinkpad X1 Carbon (LENOVO 3444CTO)
(i5-3427U)
OK
OK
[Ulrich Pfeifer](https://groups.google.com/d/msg/qubes-users/UCuF41rq758/BRhc7lTecsMJ)
Lenovo Thinkpad x220
(Sandy Bridge; HD Graphics; i5-2520M; BIOS: 1.39)
OK
OK
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/-b8b9fpo0UU/discussion)
[Stefan Boresch](https://groups.google.com/group/qubes-devel/msg/f41578eef913446a)
[Matt Tracy](https://groups.google.com/d/msg/qubes-users/-b8b9fpo0UU/RFh6HiWqt5oJ)
Lenovo Thinkpad x230
(Ivy Bridge; HD Graphics; i5-3320M; BIOS:2.51)
\*
OK
[read more](https://groups.google.com/d/msg/qubes-devel/XN6JrEXVOVA/lkxGRA00EqgJ)
\*
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/hf0vkL3TE7k/discussion)
[Chris](https://groups.google.com/d/msg/qubes-devel/XN6JrEXVOVA/lkxGRA00EqgJ)
[mgflax](https://groups.google.com/d/msg/qubes-users/hf0vkL3TE7k/VOtrW3wEbtMJ)
Toshiba Tecra S11
OK
OK
[read more](https://groups.google.com/group/qubes-devel/browse_thread/thread/fdec0ec165a87726)
[Jan Beerden](https://groups.google.com/group/qubes-devel/browse_thread/thread/fdec0ec165a87726)
Toshiba Tecra A11-15X
(i7-M620)
OK
OK
[PirBoazo](https://groups.google.com/group/qubes-devel/browse_thread/thread/c0d5f6a33d672b62)
Toshiba M780 S7240
(BIOS latest)
OK
OK
[Franz](https://groups.google.com/group/qubes-devel/browse_thread/thread/66e97c990a08d8e2)
Samsung Series 7 Chronos NP700Z5C
(nVidia Optimus; i7-3635QM; BIOS P04ABJ)
OK
[read more](https://groups.google.com/d/msg/qubes-devel/0xBeX8NZFiU/bUqxGdn6KOMJ)
OK
OK
X
[read more](https://groups.google.com/d/topic/qubes-devel/Wu1mn9f1qgM/discussion)
[Outback Dingo](https://groups.google.com/d/msg/qubes-devel/0xBeX8NZFiU/bUqxGdn6KOMJ)
Sony Vaio Z2
(2011 edition)
OK
OK
[read more](https://groups.google.com/d/msg/qubes-devel/xoyNCigBvFE/fkC6em-Wqd0J)
[Danny Fullerton](https://groups.google.com/d/msg/qubes-devel/xoyNCigBvFE/fkC6em-Wqd0J)
Zareason Ultra Lap 420
(Ivy Bridge; HD Graphics; i5-3317U)
OK
OK
[Ant](https://groups.google.com/d/msg/qubes-users/uKI-VBtKWxg/uKjsdGNSpSQJ)
**User Reported Desktops and Workstations**
ASRock Z77 Pro4
(Ivy Bridge; Xeon E3-1200 Graphics; i7-3770; BIOS: P1.40)
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/lycnE-LcJBo/discussion)
[gorka](https://groups.google.com/d/msg/qubes-users/lycnE-LcJBo/0u10xl7AMrIJ)
Dell Inspiron 660
(Xeon E3-1200 Graphics; i5-3330; BIOS: A09)
OK
OK
OK
[read more](https://groups.google.com/d/topic/qubes-users/Nq7T0l4A2b0/discussion)
[KR](https://groups.google.com/d/msg/qubes-users/Nq7T0l4A2b0/IP_pwZMn9LYJ)
Dell Precision T3400 Workstation
(NVIDIA Quadro NVS 290; Intel Q6600; BIOS: A09)
OK
OK
X
[Andrew Sorensen](https://groups.google.com/d/msg/qubes-devel/D16dM3rg8Iw/zOEZmjTJkRIJ)
GA-fxa990-ud3 (rev 3.0)
(AMD FX-8350; GTX 470)
OK
OK
X
[m astroj](https://groups.google.com/d/msg/qubes-devel/oox94EsIduQ/7w4xUoK5pxwJ)
MSI Big Bang
(i7-950; Radeon HD 6770)
OK
[read more](https://groups.google.com/d/topic/qubes-devel/TxzaoodB02o/discussion)
[Andrew Sorensen](https://groups.google.com/d/msg/qubes-devel/TxzaoodB02o/NxVHjaPoRYoJ)
Supermicro X10SAE
(Haswell; Radeon HD 5700; Xeon E3-1245; BIOS: 1.0)
X
X
[read more](https://groups.google.com/d/topic/qubes-users/V9BLpdf4xCs/discussion)
OK
OK
X
[read more](https://groups.google.com/d/topic/qubes-users/V9BLpdf4xCs/discussion)
[Qubes Fan](https://groups.google.com/d/msg/qubes-users/V9BLpdf4xCs/v4XcOjLT6uUJ)
Generating and Submitting New Reports
-------------------------------------
In order to generate an HCL report in Qubes, simply open a terminal in dom0 and run `qubes-hcl-report <vm-name>`, where `<vm-name>` is the name of the VM to which the generated HCL files will be saved. (Note: If you are working with a new Qubes installation, you may need to update your system in order to download this script.)
Users are encouraged to submit their HCL reports for the benefit of further Qubes development and other users. If you would like to submit your HCL report, please send the **HCL Info** `.txt` file to `qubes-users@googlegroups.com` (see [here](/doc/QubesLists/) information about the mailing lists) with the subject `HCL - <your machine model name>`. Please include any useful information about any Qubes features you may have tested (see the legend above), as well as general machine compatibility (video, networking, sleep, etc.). If you have problems with your hardware, please send the **HCL Support Files** `.cpio.gz` file as well.
**Please note:** The **HCL Support Files** may contain numerous hardware details, including serial numbers. If, for privacy or security reasons, you do not wish to make this information public, please **do not** send the `.cpio.gz` file to the public mailing list.

2112
HCL.md
View File

File diff suppressed because it is too large Load Diff

68
HCLR1.md
View File

@ -1,68 +0,0 @@
---
layout: doc
title: HCLR1
permalink: /doc/HCLR1/
redirect_from: /wiki/HCLR1/
---
Hardware Compatibility List for Qubes OS R1
===========================================
The following is a list of systems that have been tested and seem to work fine with Qubes OS (or mostly fine). Unless otherwise noted, all the systems have support for Intel VT-d, which is needed to properly secure driver domains in Qubes OS (netvm, usbvm, etc). Systems without VT-d are still usable, but you don't get an extra protection from driver domain separation (you still get lots of security benefit from AppVM separation though).
General system requirements
---------------------------
Minimum:
- 4GB of RAM
- 64-bit Intel or AMD processor (x86\_64 aka x64 aka AMD64)
- Intel GPU strongly preferred (if you have Nvidia GPU, prepare for some [troubleshooting](/doc/InstallNvidiaDriver/); we haven't tested ATI hardware)
- At least 20GB of disk (Note that **it is possible to install Qubes on an external USB disk**, so that you can try it without sacrificing your current system. Mind, however, that USB disks are usually SLOW!)
- Fast SSD disk strongly recommended
Additional requirements:
- Intel VT-d or AMD IOMMU technology (this is needed for effective isolation of your network VMs)
- TPM with proper BIOS support if you want to use option [Anti Evil Maid](http://theinvisiblethings.blogspot.com/2011/09/anti-evil-maid.html)
If you don't meet the additional criteria, you can still install and use Qubes. It still offers significant security improvement over traditional OSes, because things such as GUI isolation, or kernel protection do not require special hardware.
**Note:** We don't recommend installing Qubes in a virtual machine!
**Note:** There is a problem with supporting keyboard and mouse on Mac, and so Mac hardware is currently unsupported (patches welcomed!)
Specific systems known to work tested by Qubes core developers
--------------------------------------------------------------
- Lenovo Thinkpad T420 w/ Intel graphics
- Lenovo Thinkpad T420s w/ Intel graphics (requires 3.2.7 kernel to handle the panel screen correctly)
- Lenovo Thinkpad T61 w/ Nvidia graphics (Quadro NVS 140M) - works well. This system doesn't support VT-d!
- Samsung X460 - works well on both xenlinux 2.6.38 and pvops 3.2.7 kernel; after resume ethernet driver (sky2) need to be reloaded in netvm to start working again. Even though the chipset suppors VT-d, the BIOS is broken, and so the VT-d is not picked up by Xen, so it effectively doesn't work.
- Sony Vaio Z 12 (2010 edition) -- works well, but some [tinkering required](/doc/SonyVaioTinkering/)
- Dell Latitude E6420 w/ Intel graphics (Sandy Bridge), i5-2520M CPU - works well on 3.4.18 (haven't tested default 3.2.30 kernel)
Specific systems known to work tested by the Qubes community
------------------------------------------------------------
- Fujitsu S751 seems to work well, but requires BIOS update to get VT-d working. Reported by [Zrubecz Laszlo](https://groups.google.com/forum/#!msg/qubes-devel/xoyNCigBvFE/ER61L6TbVpwJ).
- Sony Vaio Z2 (2011 edition) works fine but requires some BIOS mod to enable VT-d. Reported by [Danny Fullerton](https://groups.google.com/d/msg/qubes-devel/xoyNCigBvFE/fkC6em-Wqd0J).
- Lenovo Thinkpad W510 with core I7 Q820, with proprietary Nvidia driver works fine. Reported by [Sebastian Hültenschmidt](https://groups.google.com/forum/#!msg/qubes-devel/TgDWwBs36yA/IUFZPHs716cJ).
- Lenovo Thinkpad x220 8GB RAM, Intel graphics (core i5), VT-d is working. Reported by [Stefan Boresch](https://groups.google.com/group/qubes-devel/msg/f41578eef913446a)
- Dell Latitude 5520, requires some minor fixes for networking to work. Reported by [Erik Edin](https://groups.google.com/group/qubes-devel/msg/7418e7084c2de99f?hl=en).
- Dell Latitude E6520 with i7-2760QM CPU. VT-d works fine. nVidia graphics not working, but integrated Intel does. Reported by [Steven Collins](https://groups.google.com/group/qubes-devel/msg/340afc6fc2d06d0e)
- Dell [PowerEdge?](/doc/PowerEdge/) T110 II, onboard Matrox graphics (Intel Xeon E3-1230), VT-d is working. Reported by [Geoff](https://groups.google.com/group/qubes-devel/msg/8a894915909eeaee)
- Toshiba Tecra S11. Requires [some tinkering](https://groups.google.com/group/qubes-devel/browse_thread/thread/fdec0ec165a87726) to enable 3G modem. Reported by Jan Beerden
- Toshiba M780 S7240, requires latest BIOS to have VT-d working, [some problems](https://groups.google.com/group/qubes-devel/browse_thread/thread/2b89d2dc5f999ab7) with card reader. Reported by [Franz](https://groups.google.com/group/qubes-devel/browse_thread/thread/66e97c990a08d8e2)
- Dell Precision M4600 Intel Core i7-2860QM, 16GB ram, NVIDIA Quadro 1000M, EMEA Intel Pro Wireless 6300. Reported by [nqe](https://groups.google.com/group/qubes-devel/browse_thread/thread/ddf35d12a35f96a3)
- Tecra A11-15X: RAM 8GB CPU I7 M620 2.67 ghz. Reported by [PirBoazo](https://groups.google.com/group/qubes-devel/browse_thread/thread/c0d5f6a33d672b62)
Specific systems known to not work well with Qubes
--------------------------------------------------
- All systems based on Ivy Bridge processors with the Intel integrated GPU used as the primary display. Currently our Xorg drivers in Dom0 do not support the latest Intel integrated GPUs from Ivy Bridge line. For instructions on possible workarounds see [this message](https://groups.google.com/d/msg/qubes-devel/XN6JrEXVOVA/GMTjUM2J6QEJ).
- Specific system in above category: Lenovo x230 reported by [Chris](https://groups.google.com/d/msg/qubes-devel/XN6JrEXVOVA/lkxGRA00EqgJ) - with detailed list of working and not working components

6
InstallationGuideR3.0rc1.md
View File

@ -11,9 +11,9 @@ Installation Guide for Qubes Release 3.0 rc1
2. [Download installer ISO](#download-installer-iso) 2. [Download installer ISO](#download-installer-iso)
3. [Burning the ISO onto a DVD or USB stick](#burning-the-iso-onto-a-dvd-or-usb-stick) 3. [Burning the ISO onto a DVD or USB stick](#burning-the-iso-onto-a-dvd-or-usb-stick)
4. [Upgrading](#upgrading) 4. [Upgrading](#upgrading)
5. [Troubleshooting problems with the installer](#Troubleshootingproblemswiththeinstaller) 5. [Troubleshooting problems with the installer](#troubleshooting-problems-with-the-installer)
6. [Known Issues](#KnownIssues) 6. [Known Issues](#known-issues)
7. [Getting Help](#GettingHelp) 7. [Getting Help](#getting-help)
Hardware Requirements Hardware Requirements
--------------------- ---------------------

2
QubesDocs.md
View File

@ -16,7 +16,7 @@ For Users
- [User Documentation](/doc/UserDoc/) - [User Documentation](/doc/UserDoc/)
- [Users' FAQ](/doc/UserFaq/) - [Users' FAQ](/doc/UserFaq/)
- [System Requirements](/doc/SystemRequirements/) - [System Requirements](/doc/SystemRequirements/)
- [Hardware Compatibility List](/hcl//) - [Hardware Compatibility List](/hcl/)
- [On Digital Signatures and How to Verify Qubes Downloads](/doc/VerifyingSignatures/) - [On Digital Signatures and How to Verify Qubes Downloads](/doc/VerifyingSignatures/)
- [Installation Guides](/doc/QubesDownloads/) - [Installation Guides](/doc/QubesDownloads/)
- [Troubleshooting](/doc/TroubleShooting/) - [Troubleshooting](/doc/TroubleShooting/)

2
QubesLists.md
View File

@ -34,7 +34,7 @@ The `qubes-users` Mailing List
This list is for helping users solve various daily problems with Qubes OS. Examples of topics or questions suitable for this list include: This list is for helping users solve various daily problems with Qubes OS. Examples of topics or questions suitable for this list include:
- [HCL reports](/doc/hcl/#generating-and-submitting-new-reports). - [HCL reports](/doc/HCL/#generating-and-submitting-new-reports).
- Installation problems. - Installation problems.
- Hardware compatibility problems. - Hardware compatibility problems.
- Bug reports. - Bug reports.

5
hcl.html
View File

@ -16,6 +16,7 @@ model: all
<h2 align="center">{{ page.title }}</h2> <h2 align="center">{{ page.title }}</h2>
<div align="center">Information about this list and how to contribute can be found <a class='ext-link' href='/doc/HCL/'>here</a>.</div>
<table align="center"> <table align="center">
<tr align='center'> <tr align='center'>
<th colspan=2 align='center'><b>Legend</b></th> <th colspan=2 align='center'><b>Legend</b></th>
@ -61,7 +62,7 @@ model: all
<tr> <tr>
<td align='center'><a class='ext-link' href='https://en.wikipedia.org/wiki/Hardware_virtual_machine'>HVM</a></td> <td align='center'><a class='ext-link' href='https://en.wikipedia.org/wiki/Hardware_virtual_machine'>HVM</a></td>
<td><a class='ext-link' href='https://en.wikipedia.org/wiki/Intel_VT-x#Intel-VT-x'>Intel VT-x</a> or <a class='ext-link' href='https://en.wikipedia.org/wiki/AMD-V#AMD_virtualization_.28AMD-V.29'>AMD-v</a> technology (required for running HVM domains, such as <a class='ext-link' href='/wiki/WindowsAppVms/'>Windows-based AppVMs</a>) </td> <td><a class='ext-link' href='https://en.wikipedia.org/wiki/Intel_VT-x#Intel-VT-x'>Intel VT-x</a> or <a class='ext-link' href='https://en.wikipedia.org/wiki/AMD-V#AMD_virtualization_.28AMD-V.29'>AMD-v</a> technology (required for running HVM domains, such as <a class='ext-link' href='/doc/WindowsAppVms/'>Windows-based AppVMs</a>) </td>
</tr> </tr>
<tr> <tr>
@ -71,7 +72,7 @@ model: all
<tr> <tr>
<td align='center'><a class='ext-link' href='https://en.wikipedia.org/wiki/Trusted_Platform_Module'>TPM</a></td> <td align='center'><a class='ext-link' href='https://en.wikipedia.org/wiki/Trusted_Platform_Module'>TPM</a></td>
<td>TPM with proper BIOS support (required for <a class='ext-link' href='/wiki/AntiEvilMaid/'>Anti Evil Maid</a>) </td> <td>TPM with proper BIOS support (required for <a class='ext-link' href='/doc/AntiEvilMaid/'>Anti Evil Maid</a>) </td>
</tr> </tr>
<tr> <tr>