diff --git a/doc.md b/doc.md index 743c6477..f782dfe9 100644 --- a/doc.md +++ b/doc.md @@ -112,7 +112,6 @@ Core documentation for Qubes users. * [Making Any File Persistent Using `bind-dirs`](/doc/bind-dirs/) * [GUI Configuration](/doc/gui-configuration/) * [Resizing Disk Images](/doc/resize-disk-image/) - * [Troubleshooting UEFI](/doc/uefi-troubleshooting/) * [Troubleshooting Newer Hardware](/doc/newer-hardware-troubleshooting/) * [Mounting and Decrypting Qubes Partitions from Outside Qubes](/doc/mount-from-other-os/) * [KDE](/doc/kde/) @@ -122,6 +121,7 @@ Core documentation for Qubes users. ### Troubleshooting * [Installation Troubleshooting](/doc/installation-troubleshooting) + * [UEFI Troubleshooting](/doc/uefi-troubleshooting/) * [Home directory is out of disk space error](/doc/out-of-memory/) * [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/) diff --git a/user/troubleshooting/installation-troubleshooting.md b/user/troubleshooting/installation-troubleshooting.md deleted file mode 100644 index c54dd07d..00000000 --- a/user/troubleshooting/installation-troubleshooting.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -layout: doc -title: Installation Troubleshooting -permalink: /doc/installation-troubleshooting/ ---- -# Installation Troubleshooting # - -## "An unknown error has occured" error during installation ## - -Some people have encountered this error message when trying to install Qubes on drives that already have data on them. -The solution is to exit the installer, wipe all data or delete all partitions, then restart the Qubes installation. - -## Trouble installing from USB stick ## - -If you are facing issues when booting using UEFI mode, see the [UEFI troubleshooting guide](/doc/uefi-troubleshooting/). - -There are a variety of other problems that could arise when using a USB installation medium, and some of the issues can be fixed by doing one or more of the following: - -* **Use a different USB drive:** -If possible, try several drives of different sizes and formats. -This determines whether the problem stems from the flash drive or Qubes installer. -Some laptops cannot read from an external boot device larger than 8GB. -If you encounter a black screen when performing an installation from a USB stick, ensure you are using a USB drive less than 8GB, or a partition on that USB less than 8GB and of format FAT32. -* **Verify your Qubes ISO:** -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. -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. - - -## Boot screen does not appear / system does not detect your installation medium ## - -If the boot screen does not appear, there are several options to troubleshoot. -First, try rebooting your computer. -If it still loads your currently installed operating system or does not detect your installation medium, make sure the boot order is set up appropriately. - -The process to change the boot order varies depending on the currently installed system and the motherboard manufacturer. - -If **Windows 10** is installed on your machine, you may need to follow specific instructions to change the boot order. -This may require an [advanced reboot](https://support.microsoft.com/en-us/help/4026206/windows-10-find-safe-mode-and-other-startup-settings). - -## "Not asking for VNC because we don't have a network" / "X startup failed, aborting installation" / "Pane is dead" error during installation ## - -The boot mode in use may be causing these error messages. -Try to install after enabling both UEFI and legacy boot modes. -If that doesn't help, then disable one and try the other. -Visit the [UEFI Troubleshooting guide](/doc/uefi-troubleshooting/) if other errors arise during UEFI booting. - -These errors may also occur due to an incompatible Nvidia graphics card. If you have one, follow the following instructions: -1. Disable secure/fast boot and use legacy mode -2. Enter GRUB, move the selection to the first choice, and then press the Tab key. -3. Now, you are in edit mode. Move the text cursor with your arrow key and after ``kernel=`` line, add: - - ``nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off`` - - If the above code doesn't fix the problem, replace it with: - - ``noexitboot=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau --- intitrd.img`` - -For more information, look at the [Nvidia Troubleshooting guide](/doc/nvidia-troubleshooting/#disabling-nouveau). - - -## Installation freezes at "Setting up Networking" ## - -If you are facing this problem on an Apple computer, check out the [Macbook Troubleshooting guide](/doc/macbook-troubleshooting/). - -This issue occurs due to the network card, which may be missing some drivers or is incompatible with Qubes. - -First, install all available drivers for the card. -You can install the drivers without internet access by first downloading them on another machine, then transferring them over to the current machine (e.g., with a USB drive). - -If installing the available drivers does not help, disable the network card in the BIOS and perform the installation before re-enabling the card. -If this solves the issue, it confirms the PCI card is incompatible with Qubes. -In this case, you may want to consider replacing it with a network card of a different brand. -Broadcom cards are notoriously problematic with Qubes. - - - diff --git a/user/advanced-configuration/uefi-troubleshooting.md b/user/troubleshooting/uefi-troubleshooting.md similarity index 87% rename from user/advanced-configuration/uefi-troubleshooting.md rename to user/troubleshooting/uefi-troubleshooting.md index d9feffcc..fd36527a 100644 --- a/user/advanced-configuration/uefi-troubleshooting.md +++ b/user/troubleshooting/uefi-troubleshooting.md @@ -4,11 +4,9 @@ title: UEFI Troubleshooting permalink: /doc/uefi-troubleshooting/ --- -Troubleshooting UEFI related problems -======================================== +# Troubleshooting UEFI related problems # -Change installer kernel parameters in UEFI ---------------------- +## Successfully installed in legacy mode, but had to change some kernel parameters ## If you've installed successfully in legacy mode but had to change some kernel parameters for it to work, you should try installing in UEFI mode with the same parameters. @@ -25,12 +23,14 @@ If you've installed successfully in legacy mode but had to change some kernel pa 05. Save your changes, unmount and dd to usb device -Installation freezes before displaying installer ------------------------------------------------------------ +## Installation freezes before displaying installer ## + +If you have an Nvidia card, see also [Nvidia Troubleshooting](/doc/nvidia-troubleshooting/#disabling-nouveau). + +### Removing `noexitboot` and `mapbs` ### Some systems can freeze with the default UEFI install options. You can try the following to remove `noexitboot` and `mapbs`. -If you have an Nvidia card, see also [Nvidia Troubleshooting](/doc/nvidia-troubleshooting/#disabling-nouveau). 1. Follow the [steps here](/doc/uefi-troubleshooting/#change-installer-kernel-parameters-in-uefi) to edit the `[qubes-verbose]` section of your installer's `BOOTX64.cfg`. You want to comment out the `mapbs` and `noexitboot` lines. @@ -59,9 +59,26 @@ This is also a good time to make permanent any other changes needed to get the i 5. Go back to `tty6` (Ctrl-Alt-F6) and click `Reboot`. 6. Continue with setting up default templates and logging in to Qubes. +### Changing `options=console=` parameter to `none` ### -Installation freezes before displaying installer / disable EFI runtime services ------------------------------------------------------------------------------- +If removing `noexitboot` and `mapbs` did not help, you can try changing the `options=console=` parameter to `none`. The detailed solution can be found in the comments of [this GitHub issue](https://github.com/QubesOS/qubes-issues/issues/5383) + +1. Follow the [steps here](/doc/uefi-troubleshooting/#change-installer-kernel-parameters-in-uefi) to edit the `[qubes-verbose]` section of your installer's `BOOTX64.cfg`. + You want to change `options=console=vga` to `options=console=none`. + The end result should look like this: + + ~~~ + [qubes-verbose] + options=console=none efi=attr=uc + noexitboot=1 + mapbs=1 + kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 + ramdisk=initrd.img + ~~~ + +2. Boot the installer and continue to install as normal + +### Disable EFI runtime services ### On some early, buggy UEFI implementations, you may need to disable EFI under Qubes completely. This can sometimes be done by switching to legacy mode in your BIOS/UEFI configuration. @@ -105,13 +122,11 @@ Consider this approach as a last resort, because it will make every Xen update a Whenever there is a kernel or Xen update for Qubes, you will need to follow [these steps](/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing) because your system is using the fallback UEFI bootloader in `[...]/EFI/BOOT` instead of directly booting to the Qubes entry under `[...]/EFI/qubes`. -Installation from USB stick hangs on black screen ---------------------- +## Installation from USB stick hangs on black screen ## -Some laptops cannot read from an external boot device larger than 8GB. If you encounter a black screen when performing an installation from a USB stick, ensure you are using a USB drive less than 8GB, or a partition on that USB lesser than 8GB and of format fat32. +Some laptops cannot read from an external boot device larger than 8GB. If you encounter a black screen when performing an installation from a USB stick, ensure you are using a USB drive less than 8GB, or a partition on that USB lesser than 8GB and of format FAT32. -Installation completes successfully but then boot loops or hangs on black screen ---------------------- +## Installation completes successfully but then boot loops or hangs on black screen ## There is a [common bug in UEFI implementation](http://xen.markmail.org/message/f6lx2ab4o2fch35r) affecting mostly Lenovo systems, but probably some others too. While some systems need `mapbs` and/or `noexitboot` disabled to boot, others require them enabled at all times. @@ -152,8 +167,7 @@ Or if you have already rebooted after the first stage install and have encounter 4. Continue with setting up default templates and logging in to Qubes. -Installation completes successfully but then system crash/restarts on next boot -------------------------------------------- +## Installation completes successfully but then system crash/restarts on next boot ## Some Dell systems and probably others have [another bug in UEFI firmware](http://markmail.org/message/amw5336otwhdxi76). These systems need `efi=attr=uc` enabled at all times. @@ -180,8 +194,7 @@ Or if you have already rebooted after the first stage install and have encounter 4. Continue with setting up default templates and logging in to Qubes. -Boot device not recognized after installing ------------------------------------------- +## Boot device not recognized after installing ## Some firmware will not recognize the default Qubes EFI configuration. As such, it will have to be manually edited to be bootable. @@ -202,8 +215,7 @@ This will need to be done after every kernel and Xen update to ensure you use th cp /boot/efi/EFI/qubes/xen-4.8.3.efi /boot/efi/EFI/BOOT/BOOTX64.efi -Installation finished but "Qubes" boot option is missing and xen.cfg is empty --------------------------------------------------------------------------------------- +## Installation finished but "Qubes" boot option is missing and xen.cfg is empty / Installation fails with "failed to set new efi boot target" ## In some cases installer fails to finish EFI setup and leave the system without a Qubes-specific EFI configuration. In such a case you need to finish those parts manually. @@ -237,8 +249,7 @@ You can do that just after installation (switch to `tty2` with Ctrl-Alt-F2), or efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda -p 1 "placeholder /mapbs /noexitboot" -Accessing installer Rescue mode on UEFI ---------------------------------------- +## Accessing installer Rescue mode on UEFI ## In UEFI mode, the installer does not have a boot menu, but boots directly into the installation wizard. To get into Rescue mode, you need to switch to tty2 (Ctrl+Alt+F2) and then execute: