mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-05-02 23:05:19 -04:00
Merge branch 'master' into nvidia-troubleshooting
This commit is contained in:
Enjeck Cleopatra
GitHub
commit
265d03feb0
24 changed files with 284 additions and 181 deletions
|
|
@ -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 ##
|
||||
|
||||
|
|
|
|||
118
user/troubleshooting/managing-appvm-shortcuts.md
Normal file
118
user/troubleshooting/managing-appvm-shortcuts.md
Normal file
|
|
@ -0,0 +1,118 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Managing AppVm Shortcuts
|
||||
permalink: /doc/managing-appvm-shortcuts/
|
||||
redirect_from:
|
||||
- /en/doc/managing-appvm-shortcuts/
|
||||
- /doc/ManagingAppVmShortcuts/
|
||||
- /wiki/ManagingAppVmShortcuts/
|
||||
---
|
||||
|
||||
Managing shortcuts to applications in AppVMs
|
||||
============================================
|
||||
|
||||
For ease of use Qubes aggregates shortcuts to applications that are installed in AppVMs and shows them in one "start menu" in dom0.
|
||||
Clicking on such shortcut runs the assigned application in its AppVM.
|
||||
|
||||
|
||||
|
||||
To make applications newly installed via the OS's package manager show up in the menu, use the `qvm-sync-appmenus` command (Linux VMs do this automatically):
|
||||
|
||||
`qvm-sync-appmenus vmname`
|
||||
|
||||
After that, select the *Add more shortcuts* entry in the VM's submenu to customize which applications are shown:
|
||||
|
||||
|
||||
|
||||
The above image shows that Windows HVMs are also supported (provided that Qubes Tools are installed).
|
||||
|
||||
What if my application has not been automatically included in the list of available apps?
|
||||
-----------------------------------------------------------------------------------------
|
||||
|
||||
Some times applications may not have included a `.desktop` file and may not be detected by `qvm-sync-appmenus`.
|
||||
Other times, you may want to make a web shortcut available from the Qubes start menu.
|
||||
|
||||
You can manually create new entries in the "available applications" list of shortcuts for all AppVMs based on a TemplateVM.
|
||||
To do this:
|
||||
|
||||
1. Open a terminal window to the TemplateVM.
|
||||
2. Create a custom `.desktop` file in `/usr/share/applications` (you may need to first create the subdirectory).
|
||||
Look in `/usr/share/applications` for existing examples, or see the full [file specification](https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html).
|
||||
It will be something like:
|
||||
```
|
||||
[Desktop Entry]
|
||||
Version=1.0
|
||||
Type=Application
|
||||
Terminal=false
|
||||
Icon=/usr/share/icons/Adwaita/256x256/devices/scanner.png
|
||||
Name=VueScan
|
||||
GenericName=Scanner
|
||||
Comment=Scan Documents
|
||||
Categories=Office;Scanning;
|
||||
Exec=vuescan
|
||||
```
|
||||
3. In dom0, run `qvm-sync-appmenus <TemplateVMName>`.
|
||||
4. Go to VM Settings of the AppVM(s) to which you want to add the new shortcut, then the Applications tab.
|
||||
Move the newly created shortcut to the right under selected.
|
||||
|
||||
If you only want to create a shortcut for a single AppVM, you can create a custom menu entry instead:
|
||||
|
||||
1. Open a terminal window to Dom0.
|
||||
2. Create a custom `.desktop` file in `~/.local/share/applications`.
|
||||
Look in the same directory for existing examples, or see the full [file specification](https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html).
|
||||
You may use `qvm-run` inside the `.desktop` file; see [Behind the scenes](/doc/managing-appvm-shortcuts/#behind-the-scenes) for more details.
|
||||
3. Edit the `~/.config/menus/applications-merged/<vmname>-vm.menu` file for the AppVM.
|
||||
4. Add a custom menu entry referring to your newly created `.desktop` file.
|
||||
|
||||
~~~
|
||||
<Menu>
|
||||
<Name>Webmail</Name>
|
||||
<Include>
|
||||
<Filename>custom.desktop</Filename>
|
||||
</Include>
|
||||
</Menu>
|
||||
~~~
|
||||
|
||||
What about applications in DispVMs?
|
||||
-----------------------------------
|
||||
|
||||
[See here](/doc/disposablevm-customization/).
|
||||
|
||||
|
||||
Fixing shortcuts
|
||||
----------------
|
||||
|
||||
First, try this in dom0:
|
||||
|
||||
```
|
||||
$ qvm-appmenus --update --force <vm_name>
|
||||
```
|
||||
|
||||
If that doesn't work, you can manually modify the files in `~/.local/share/applications/` or `/usr/local/share/applications/`.
|
||||
|
||||
For example, suppose you've deleted `my-old-vm`, but there is a leftover Application Menu shortcut, and you find a related file in `~/.local/share/applications/`.
|
||||
In dom0:
|
||||
|
||||
```
|
||||
$ rm -i ~/.local/share/applications/my-old-vm-*
|
||||
```
|
||||
|
||||
|
||||
Behind the scenes
|
||||
-----------------
|
||||
|
||||
`qvm-sync-appmenus` works by invoking *GetAppMenus* [Qubes service](/doc/qrexec/) in the target domain.
|
||||
This service enumerates installed applications and sends formatted info back to the dom0 script (`/usr/libexec/qubes-appmenus/qubes-receive-appmenus`) which creates .desktop files in the AppVM/TemplateVM directory.
|
||||
|
||||
For Linux VMs the service script is in `/etc/qubes-rpc/qubes.GetAppMenus`.
|
||||
In Windows it's a PowerShell script located in `c:\Program Files\Invisible Things Lab\Qubes OS Windows Tools\qubes-rpc-services\get-appmenus.ps1` by default.
|
||||
|
||||
The list of installed applications for each AppVM is stored in dom0's `~/.local/share/qubes-appmenus/<vmname>/apps.templates`.
|
||||
Each menu entry is a file that follows the [.desktop file format](https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html) with some wildcards (*%VMNAME%*, *%VMDIR%*).
|
||||
Applications selected to appear in the menu are stored in `~/.local/share/qubes-appmenus/<vmname>/apps`.
|
||||
|
||||
Actual command lines for the menu shortcuts involve `qvm-run` command which starts a process in another domain.
|
||||
Examples: `qvm-run -q -a --service -- %VMNAME% qubes.StartApp+7-Zip-7-Zip_File_Manager` or `qvm-run -q -a --service -- %VMNAME% qubes.StartApp+firefox`
|
||||
|
||||
Note that you can create a shortcut that points to a .desktop file in your AppVM with e.g. `qvm-run -q -a --service -- personal qubes.StartApp+firefox`.
|
||||
|
||||
|
|
@ -1,58 +0,0 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Sony Vaio Tinkering
|
||||
permalink: /doc/sony-vaio-tinkering/
|
||||
redirect_from:
|
||||
- /en/doc/sony-vaio-tinkering/
|
||||
- /doc/SonyVaioTinkering/
|
||||
- /wiki/SonyVaioTinkering/
|
||||
---
|
||||
|
||||
Instructions for getting your Sony Vaio Z laptop working with Qubes/Linux
|
||||
=========================================================================
|
||||
|
||||
Sony Vaio Z are great laptops -- they are very powerful, yet compact. The newer models, starting from Z12 are, however, not very well supported by Linux kernels (at least 2.6.34 that we currently use in Dom0) and thus some tinkering is needed to get Qubes working on those machines.
|
||||
|
||||
Getting the graphics card working under Linux/Qubes OS
|
||||
------------------------------------------------------
|
||||
|
||||
Newer models of Sony Vaio Z come with an "intelligent" GPU switch, that automatically chooses either Intel Integrated GPU (IGD) or the discrete NVIDIA GPU. This confuses the Linux graphics so much, that in most cases won't even be able to install a regular Linux on such a machine. Unfortunately, moving the switch into the "Stamina" position apparently doesn't work, and the automatic GPU switching is still active.
|
||||
|
||||
One solution that actually worked for me was to reflash the BIOS (I know, I know, this is scary) and to enable the so called "Advanced Menu" in the BIOS. This Advanced Menu allows you to choose the desired behaviour of the GPU switch, which in our case would be to set it to "Static" and then move the mechanical switch to the "Stamina" position, that enabled the Intel IGD (which is much better supported on Linux).
|
||||
|
||||
If you think you are ready to reflash you BIOS, here are the instructions that worked for me:
|
||||
|
||||
[http://forum.notebookreview.com/sony/473226-insyde-hacking-new-vaio-z-advanced-menu-bios.html](http://forum.notebookreview.com/sony/473226-insyde-hacking-new-vaio-z-advanced-menu-bios.html)
|
||||
|
||||
**WARNING**: We take absolutely no responsibility that the BIOS reflashing instructions given at the referenced forum are 1) valid, 2) non-malicious, and 3) work at all. Do this step at your own risk. Keep in mind that reflashing your BIOS might yield your system unusable. If you don't feel like taking this risk (which is a reasonable state of mind), look for a different notebook, or ask Sony Support to enable this option for you.
|
||||
|
||||
In practice I have downloaded the BIOS-patching tools, run them in a VM on a BIOS image I extracted from my laptop, diffed the two versions, and concluded that it doesn't *seem* malicious, and then bravely applied tha patched image. If you don't know what are you doing, just get a different laptop, really!
|
||||
|
||||
On a side note, we should note that allowing anybody to reflash the BIOS is really a bad idea from a security point of view (Hello Evil Maids!). Shame on you, Sony!
|
||||
|
||||
Getting the touchpad working during installation
|
||||
------------------------------------------------
|
||||
|
||||
In order to get the touchpad working during installation you should pass the **~~~i8042.nopnp=1~~~** option to the kernel before the installer starts.
|
||||
|
||||
\<screenshot\>
|
||||
|
||||
Applying other fixes
|
||||
--------------------
|
||||
|
||||
There are a few more fixes needed for Sony Vaio Z, and we have prepared a special package that you can install in Dom0 that applies them all. After the installation is complete, open console in Dom0 and do the following:
|
||||
|
||||
~~~
|
||||
$ sudo bash
|
||||
# qvm-dom0-networking up
|
||||
# yum install qubes-core-dom0-vaio-fixes
|
||||
# reboot
|
||||
~~~
|
||||
|
||||
This script takes care about the following:
|
||||
|
||||
- Setting i8042.nopnp for your installed system
|
||||
- Adding special option for the sound module (so you can get sound)
|
||||
- Adding pm-suspend scripts that take care about restoring your screen after resume
|
||||
|
||||
... now, having done this all, you will surely feel unprecedented satisfaction and you will love your Vaio very much! ;)
|
||||
|
|
@ -1,94 +0,0 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Lenovo ThinkPad Troubleshooting
|
||||
permalink: /doc/thinkpad-troubleshooting/
|
||||
redirect_from:
|
||||
- /doc/thinkpad_x201/
|
||||
- /en/doc/thinkpad_x201/
|
||||
- /doc/Thinkpad_X201/
|
||||
- /wiki/Thinkpad_X201/
|
||||
- /doc/lenovo450-tinkering/
|
||||
- /en/doc/lenovo450-tinkering/
|
||||
- /doc/Lenovo450Tinkering/
|
||||
- /wiki/Lenovo450Tinkering/
|
||||
---
|
||||
|
||||
# Lenovo ThinkPad Troubleshooting #
|
||||
|
||||
## Instructions to create USB installation medium 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:
|
||||
|
||||
1. On your ThinkPad, enter the UEFI setup (press F1 at startup) and make sure to set at least the following options:
|
||||
- *USB UEFI BIOS Support: Enabled*
|
||||
- *UEFI/Legacy Boot: UEFI Only*
|
||||
- *Secure Boot: Disabled*
|
||||
2. On a different computer, create a "Fedora Live USB Stick": Download a current Fedora Live CD image, and put it onto a USB stick (e.g. using dd or Rufus). Start your ThinkPad from the Fedora Live USB Stick on your ThinkPad (Press F12 at startup to select boot device). Of course, you can alternatively start a different machine from the Fedora Live USB Stick, or use an existing Fedora installation. The next steps all occur within Fedora:
|
||||
3. Install livecd-tools: `# dnf install livecd-tools`
|
||||
4. Download the desired Qubes ISO image (or attach a storage device containing it), and verify the signatures as described in the Qubes installation guide. For these instructions, I assume the ISO image is at */run/media/liveuser/qsrc/Qubes-R4.0-rc3-x86_64.iso* (so whenever you see that path going forward in these instructions, replace it with whatever your own path is)
|
||||
5. Within Fedora, attach the USB stick that you would like to turn into your Qubes Installation USB Stick. Use `dmesg` to figure out what the device name of that stick is. For these instructions, I assume it's */dev/sdd* (so whenever you see */dev/sdd* going forward in these instructions, replace it with whatever your actual device name is)
|
||||
6. Make sure your target USB stick (presumed to be /dev/sdd) has no mounted partitions: ``# umount /dev/sdd*`` (the asterisk at the end makes sure to unmount all partitions if more than one exists). If none are mounted you'll get an error that you can ignore.
|
||||
7. Use livecd-tools to copy the image: ``# livecd-iso-to-disk --format --efi /run/media/liveuser/qsrc/Qubes-R4.0-rc3-x86_64.iso /dev/sdd``. **This will erase everything on the drive. Make sure you specify the correct destination.** Then press ENTER when prompted to proceed. This process will take quite a while, be patient.
|
||||
8. When imaging is complete, change the partition label to BOOT: ``# dosfslabel /dev/sdd1 BOOT``
|
||||
9. Now create a mount point and mount the partition:
|
||||
|
||||
``# mkdir /mnt/qinst``
|
||||
|
||||
``# mount /dev/sdd1 /mnt/qinst/``
|
||||
|
||||
10. Use your favorite editor to edit the file */mnt/qinst/EFI/BOOT/BOOTX64.cfg*: Replace all instances of ``LABEL=Qubes-R4.0-rc3-x86_64`` with ``LABEL=BOOT``. There is typically no space in front of ``LABEL``, but there is a space at the end of the portion you replace.
|
||||
11. Unmount the Qubes Installation USB stick: ``# umount /dev/sdd*`` and disconnect it.
|
||||
|
||||
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 ##
|
||||
|
||||
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
|
||||
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 ##
|
||||
|
||||
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.
|
||||
|
||||
After the installation, you have to set a startup-parameter for Xen, to be able to activate VT-d again:
|
||||
|
||||
1. Open a terminal in dom0
|
||||
2. Edit `/etc/default/grub`
|
||||
3. Add to the line `GRUB_CMDLINE_XEN_DEFAULT` the setting `iommu=no-igfx`, save and quit
|
||||
4. sudo `grub2-mkconfig --output /boot/grub2/grub.cfg`
|
||||
|
||||
Then reboot, enter BIOS and re-enable VT-d.
|
||||
|
||||
### Getting scrolling with the Trackpoint and the Middle Button to work ###
|
||||
|
||||
1. Create a script with the following content:
|
||||
|
||||
~~~
|
||||
#!/bin/sh
|
||||
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 1
|
||||
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 2
|
||||
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 200
|
||||
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 6 7 4 5
|
||||
~~~
|
||||
|
||||
2. Add the script to the startup-items of your desktop environment.
|
||||
|
||||
|
||||
## Instructions for getting your Lenovo 450 laptop working with Qubes/Linux ##
|
||||
|
||||
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.
|
||||
|
||||
### Setting UEFI options to get Qubes install to boot ###
|
||||
|
||||
1. Enable Legacy USB mode
|
||||
2. Disable all Secure Boot and UEFI options, but leave this enabled: Config / USB / USB UEFI BIOS SUPPORT
|
||||
3. Save settings and reboot
|
||||
5. Install Qubes
|
||||
|
||||
... and now enjoy :) These settings may be needed also in other UEFI computers.
|
||||
|
||||
31
user/troubleshooting/vpn-troubleshooting.md
Normal file
31
user/troubleshooting/vpn-troubleshooting.md
Normal file
|
|
@ -0,0 +1,31 @@
|
|||
---
|
||||
layout: doc
|
||||
title: VPN Troubleshooting
|
||||
permalink: /doc/vpn-troubleshooting/
|
||||
---
|
||||
|
||||
# VPN Troubleshooting Guide #
|
||||
|
||||
## Tips
|
||||
|
||||
* If using qubes-vpn, check the VPN service's log in the VPN VM by running:
|
||||
~~~
|
||||
sudo journalctl -u qubes-vpn-handler
|
||||
~~~
|
||||
* Always test your basic VPN connection before adding scripts.
|
||||
|
||||
* Test DNS: Ping a familiar domain name from an appVM. It should print the IP address for the domain.
|
||||
|
||||
* Use `iptables -L -v` and `iptables -L -v -t nat` to check firewall rules. The latter shows the critical PR-QBS chain that enables DNS forwarding.
|
||||
|
||||
## VPN does not reconnect after suspend
|
||||
|
||||
This applies when using OpenVPN.
|
||||
|
||||
After suspend/resume, OpenVPN may not automatically reconnect. In order to get it to work, you must kill the OpenVPN process and restart it.
|
||||
|
||||
## VPN stuck at "Ready to start link"
|
||||
|
||||
After setting up OpenVPN and restarting the VM, you may be repeatedly getting the popup "Ready to start link", but the VPN isn't connected.
|
||||
|
||||
To figure out the root of the problem, check the VPN logs in `/var/logs/syslog`. The log may reveal issues like missing OpenVPN libraries, which you can then install.
|
||||
Loading…
Add table
Add a link
Reference in a new issue