Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-05-02 14:56:13 -04:00
Code Issues Projects Releases Packages Wiki Activity

Convert absolute to relative links

Browse source 
Absolute links break automatic onion redirection:
https://groups.google.com/g/qubes-users/c/NJdzP27wvmM/
This commit is contained in:
Andrew David Wong 2020-12-07 17:04:29 -08:00
parent 17544f4633
commit 30e7112f4a
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
16 changed files with 22 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

2
user/troubleshooting/usb-troubleshooting.md
View file

@ -75,7 +75,7 @@ On boot, the keyboard may be inactive, preventing you from entering your LUKS de
When you enable a USB qube, it hides all the USB controllers from dom0, even before it gets started.
So, if your only keyboard is on USB, you should undo this hiding.
To solve the problem, disable the USB qube by not having it autostart, or unassigning your USB controller(s) from it. If you had created the USB qube by checking the box in the installer, then your USB controller(s) are probably hidden from dom0. To unhide them, reverse the procedure described in the [USB Qubes documentation](https://www.qubes-os.org/doc/usb-qubes/#how-to-hide-all-usb-controllers-from-dom0) (under "How to hide all USB controllers from dom0"). That is, remove `rd.qubes.hide_all_usb`, instead of adding it.
To solve the problem, disable the USB qube by not having it autostart, or unassigning your USB controller(s) from it. If you had created the USB qube by checking the box in the installer, then your USB controller(s) are probably hidden from dom0. To unhide them, reverse the procedure described in the [USB Qubes documentation](/doc/usb-qubes/#how-to-hide-all-usb-controllers-from-dom0) (under "How to hide all USB controllers from dom0"). That is, remove `rd.qubes.hide_all_usb`, instead of adding it.
Note that this procedure will attach your USB controllers to dom0, so do this only with USB devices you trust.

2
user/troubleshooting/vm-troubleshooting.md
View file

@ -10,7 +10,7 @@ redirect_from:
## VM Kernel troubleshooting ##
This troubleshoot applies to the non-default kernel choice described in the [Managing VM docs](https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm).
This troubleshoot applies to the non-default kernel choice described in the [Managing VM docs](/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm).
In case of problems, you can access the VM console using `qvm-console-dispvm VMNAME` in dom0, then access the GRUB menu.
You need to call it just after starting the VM (until `GRUB_TIMEOUT` expires); for example, in a separate dom0 terminal window.