From fa61755afde5d4c5c473e6f815d261c69c4f09be Mon Sep 17 00:00:00 2001 From: PROTechThor Date: Tue, 3 Nov 2020 14:51:22 +0100 Subject: [PATCH 1/7] Amend installation guide and troubleshooting --- user/downloading-installing-upgrading/installation-guide.md | 2 ++ user/troubleshooting/installation-troubleshooting.md | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/user/downloading-installing-upgrading/installation-guide.md b/user/downloading-installing-upgrading/installation-guide.md index b6f5cb3e..f7fab4c5 100644 --- a/user/downloading-installing-upgrading/installation-guide.md +++ b/user/downloading-installing-upgrading/installation-guide.md @@ -367,6 +367,8 @@ The [Qubes backup system] allows you to do this securely and easily. We urge you to read it! It may very well contain the answers to your questions. (Since the documentation is a community effort, we'd also greatly appreciate your help in [improving] it!) + * If issues arise during installation, see the [Installation Troubleshooting](/doc/installation-troubleshooting) guide. + * If you don't find your answer in the documentation, please see [Help, Support, Mailing Lists, and Forum] for places to ask. * Please do **not** email individual members of the Qubes team with questions about installation or other problems. diff --git a/user/troubleshooting/installation-troubleshooting.md b/user/troubleshooting/installation-troubleshooting.md index f3d51fcb..89e8f58b 100644 --- a/user/troubleshooting/installation-troubleshooting.md +++ b/user/troubleshooting/installation-troubleshooting.md @@ -27,10 +27,10 @@ If a machine can not boot from a bigger USB, it may be too old to run Qubes. Errors will occur if the Qubes installer is corrupted. Ensure that the installer is correct and complete before writing it to a flash drive by [verifying the ISO](/security/verifying-signatures/#how-to-verify-qubes-iso-signatures). * **Change the method you used to [write your ISO to a USB key](/doc/installation-guide/#copying-the-iso-onto-the-installation-medium):** -Some people use the ``dd`` command (recommended), others use tools like Rufus and balenaEtcher. +Some people use the ``dd`` command (recommended), others use tools like Rufus, balenaEtcher or the GNOME Disk Utility. If installation fails after using one tool, try a different one. For example, if you are facing trouble installing Qubes after writing the ISO using Rufus, then try using other tools like balenaEtcher or the ``dd`` command. - +In case the boot partition is not set to "active" after copying the ISO, you can use some other tool like `gparted` on a Linux system to activate it. ## Boot screen does not appear / system does not detect your installation medium ## From b0fd14f7f85962a5be98c55e98c0f42c62af9925 Mon Sep 17 00:00:00 2001 From: PROTechThor Date: Tue, 3 Nov 2020 18:08:12 +0100 Subject: [PATCH 2/7] Edit Thinkpad Troubleshooting --- doc.md | 2 +- .../troubleshooting/thinkpad-troubleshooting.md | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) rename {user => external}/troubleshooting/thinkpad-troubleshooting.md (95%) diff --git a/doc.md b/doc.md index dfb58635..734904c8 100644 --- a/doc.md +++ b/doc.md @@ -275,10 +275,10 @@ For more, please see [Qubes Community Documentation](https://github.com/Qubes-Co ### Troubleshooting + * [Lenovo ThinkPad Troubleshooting](/doc/thinkpad-troubleshooting/) * [Installing on system with new AMD GPU (missing firmware problem)](https://groups.google.com/group/qubes-devel/browse_thread/thread/e27a57b0eda62f76) * [How to install an Nvidia driver in dom0](/doc/install-nvidia-driver/) * [Nvidia troubleshooting guide](/doc/nvidia-troubleshooting/) - * [Lenovo ThinkPad Troubleshooting](/doc/thinkpad-troubleshooting/) * [Apple MacBook Troubleshooting](/doc/macbook-troubleshooting/) * [Getting Sony Vaio Z laptop to work with Qubes](/doc/sony-vaio-tinkering/) * [Intel Integrated Graphics Troubleshooting](/doc/intel-igfx-troubleshooting/) diff --git a/user/troubleshooting/thinkpad-troubleshooting.md b/external/troubleshooting/thinkpad-troubleshooting.md similarity index 95% rename from user/troubleshooting/thinkpad-troubleshooting.md rename to external/troubleshooting/thinkpad-troubleshooting.md index 8615920c..fe58324f 100644 --- a/user/troubleshooting/thinkpad-troubleshooting.md +++ b/external/troubleshooting/thinkpad-troubleshooting.md @@ -15,7 +15,7 @@ redirect_from: # Lenovo ThinkPad Troubleshooting # -## Instructions to create USB installation medium for newer (UEFI-only) ThinkPads ## +## Installation from USB stick fails for newer (UEFI-only) ThinkPads ## Some newer ThinkPads (e.g. T470, T470p, [P51](https://www.svensemmler.org/blog/2017/12/17/qubes-on-thinkpad-p51.html), ThinkPad 25, but not the [P53](https://github.com/QubesOS/qubes-issues/issues/5851)) are likely to fail installation attempts made from a USB stick that was created with dd or Rufus, and even from a DVD burned using official ISO images - if the ThinkPad is configured for UEFI boot. If you don't want to use Legacy Mode as a workaround, the following instructions should help you create a Qubes Installation USB stick that works in UEFI-only mode. In a nutshell, you need to use the Fedora livecd-tools to make a Qubes Installation USB Stick from the Qubes ISO image, then update the label on the partition of that USB stick to "BOOT", and then update the BOOT/EFI/BOOTX64.cfg file on the USB stick so that all labels point to BOOT. In more detail: @@ -42,7 +42,7 @@ In a nutshell, you need to use the Fedora livecd-tools to make a Qubes Installat That's it! You can now reboot the machine with the Qubes USB Installation stick attached, and press F12 to select it as the boot device at startup. Proceed to install Qubes OS normally. Enjoy! -## ThinkPads with Intel HD 3000 graphics ## +## Random reboots on ThinkPads with Intel HD 3000 graphics ## Several ThinkPad models have Intel HD 3000 graphics, including the T420s and the T520. Some users with these laptops have experienced random reboots, which were @@ -50,7 +50,7 @@ solved by adding `i915.enable_rc6=0` as a kernel parameter to `GRUB_CMDLINE_LINUX` in the file `/etc/default/grub` in dom0. -## Instructions for getting your Lenovo Thinkpad X201 & X200 laptop working with Qubes/Linux ## +## Can't boot the installer from a USB on Thinkpad X201 & X200 ## For being able to boot the installer from USB, you have to disable VT-d in the BIOS. Enter the BIOS by hitting F1, go to Config - CPU and then disable VT-d there. @@ -79,7 +79,7 @@ Then reboot, enter BIOS and re-enable VT-d. 2. Add the script to the startup-items of your desktop environment. -## Instructions for getting your Lenovo 450 laptop working with Qubes/Linux ## +## Can’t boot from USB stick on Lenovo 450 ## Lenovo 450 uses UEFI, so some settings are needed to get Qubes (or Fedora) to boot, otherwise Qubes install USB stick will reboot right after boot selector screen and not continue install. From 7fd6d050f6bf1d2989d3bca4937dab6e7564addc Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Tue, 3 Nov 2020 14:08:39 -0800 Subject: [PATCH 3/7] Add step for creating application shortcuts Closes #1071 --- user/common-tasks/software-update-domu.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/user/common-tasks/software-update-domu.md b/user/common-tasks/software-update-domu.md index 1ddd1ffb..3bc6b44b 100644 --- a/user/common-tasks/software-update-domu.md +++ b/user/common-tasks/software-update-domu.md @@ -25,6 +25,8 @@ To permanently install new software in a TemplateVM: 3. Install software as normally instructed inside that operating system (e.g. using `dnf`, or the dedicated GUI application). 4. Shut down the TemplateVM. 5. Restart all [TemplateBasedVMs] based on the TemplateVM. + 6. (Optional) In the relevant [TemplateBasedVMs]' **Qube settings**, go to the **Applications** tab, select the new application(s) from the list, and press OK. + These new shortcuts will appear in the Applications Menu. ## Updating software in TemplateVMs From 8e65bbf62296eb1f29cb8968242f32bd873953bc Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Tue, 3 Nov 2020 14:17:40 -0800 Subject: [PATCH 4/7] Add screenshot and link to troubleshooting Also capitalize the "S" in "Qube Settings". Unfortunately, this is somewhat inconsistent between the Qube Manager and the Qubes Domains widget. Hopefully, capitalizing both words makes it clear that this is also the title of something, rather than the commonplace but erroneous capitalization of the term "qube" to refer to a VM. See QubesOS/qubes-issues#4723. This is a follow-up to #1071. --- user/common-tasks/software-update-domu.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/user/common-tasks/software-update-domu.md b/user/common-tasks/software-update-domu.md index 3bc6b44b..379e812c 100644 --- a/user/common-tasks/software-update-domu.md +++ b/user/common-tasks/software-update-domu.md @@ -25,8 +25,11 @@ To permanently install new software in a TemplateVM: 3. Install software as normally instructed inside that operating system (e.g. using `dnf`, or the dedicated GUI application). 4. Shut down the TemplateVM. 5. Restart all [TemplateBasedVMs] based on the TemplateVM. - 6. (Optional) In the relevant [TemplateBasedVMs]' **Qube settings**, go to the **Applications** tab, select the new application(s) from the list, and press OK. + 6. (Optional) In the relevant [TemplateBasedVMs]' **Qube Settings**, go to the **Applications** tab, select the new application(s) from the list, and press OK. These new shortcuts will appear in the Applications Menu. + (If you encounter problems, see [here][shortcuts] for troubleshooting.) + +![[The Applications tab in Qube Settings](/attachment/wiki/ManagingAppVmShortcuts/r4.1-dom0-appmenu-select.png)](/attachment/wiki/ManagingAppVmShortcuts/r4.1-dom0-appmenu-select.png) ## Updating software in TemplateVMs @@ -321,4 +324,5 @@ Note that the app will autostart only when the AppVM starts. If you would like t [service framework]: /doc/qubes-service/ [How to Reinstall a TemplateVM]: /doc/reinstall-template/ [installing contributed packages]: /doc/installing-contributed-packages/ +[shortcuts]: /doc/managing-appvm-shortcuts/ From 4e50924d3c9b42f9b5aa2d32d359dc842b6b1ff9 Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Tue, 3 Nov 2020 14:23:31 -0800 Subject: [PATCH 5/7] Move "Managing AppVM Shortcuts" to Troubleshooting As mentioned in #1071, this page is really about troubleshooting. Reading this page normally shouldn't be required, so it doesn't really belong under "Common Tasks." The only exception to this would be non-Linux VMs for which a manual sync is required. That's one argument in favor of moving this under "Advanced Configuration" rather than "Troubleshooting," but at least half of this page is undeniably about troubleshooting. There's also a "behind the scenes" section at the end that belongs in the Developer Documentation. --- .../{common-tasks => troubleshooting}/managing-appvm-shortcuts.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename user/{common-tasks => troubleshooting}/managing-appvm-shortcuts.md (100%) diff --git a/user/common-tasks/managing-appvm-shortcuts.md b/user/troubleshooting/managing-appvm-shortcuts.md similarity index 100% rename from user/common-tasks/managing-appvm-shortcuts.md rename to user/troubleshooting/managing-appvm-shortcuts.md From 18be4c7e1fbbb1de32d31e9ef6745fe2923f0a51 Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Tue, 3 Nov 2020 14:30:25 -0800 Subject: [PATCH 6/7] Move "Application Shortcuts" to Troubleshooting --- doc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc.md b/doc.md index dfb58635..a295c582 100644 --- a/doc.md +++ b/doc.md @@ -77,7 +77,6 @@ Core documentation for Qubes users. * [PCI Devices](/doc/pci-devices/) * [Device Handling](/doc/device-handling/) * [Optical Discs](/doc/optical-discs/) - * [Application Shortcuts](/doc/managing-appvm-shortcuts/) * [Fullscreen Mode](/doc/full-screen-mode/) ### Managing Operating Systems within Qubes @@ -123,6 +122,7 @@ Core documentation for Qubes users. * [Installation Troubleshooting](/doc/installation-troubleshooting) * [UEFI Troubleshooting](/doc/uefi-troubleshooting/) * [Suspend/Resume Troubleshooting](/doc/suspend-resume-troubleshooting/) + * [Application Shortcut Troubleshooting](/doc/managing-appvm-shortcuts/) * [VM Troubleshooting](/doc/vm-troubleshooting/) * [HVM Troubleshooting](/doc/hvm-troubleshooting/) * [Disk Troubleshooting](/doc/disk-troubleshooting/) From 0921e18e970df9877189571c6f43841d3d7c988a Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Tue, 3 Nov 2020 16:05:02 -0800 Subject: [PATCH 7/7] Explain why repos are enabled permanently Closes QubesOS/qubes-issues#4667 --- user/common-tasks/software-update-domu.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/user/common-tasks/software-update-domu.md b/user/common-tasks/software-update-domu.md index 379e812c..86b126a5 100644 --- a/user/common-tasks/software-update-domu.md +++ b/user/common-tasks/software-update-domu.md @@ -110,6 +110,10 @@ sudo dnf config-manager --set-enabled rpmfusion-nonfree-updates sudo dnf upgrade --refresh ~~~ +This will permanently enable the RPM Fusion repos. +If you install software from here, it's important to keep these repos enabled so that you can receiving future updates. +If you only enable these repos temporarily to install a package the Qubes update mechanism may persistently notify you that updates are available, since it cannot download them. + ### Reverting changes to a TemplateVM