diff --git a/about/faq.md b/about/faq.md
index 5ec48656..34eefc0e 100644
--- a/about/faq.md
+++ b/about/faq.md
@@ -303,7 +303,11 @@ A device that does not support reset is not safe and generally should not be ass
 
 Most likely the offending controller is a USB 3.0 device. 
 You can remove this controller from the usbVM, and see if this allows the VM to boot.
-Alternatively you may be able to disable USB 3.0 in the BIOS.
+Alternatively you may be able to disable USB 3.0 in the BIOS.  
+If the BIOS does not have the option to disable USB 3.0, try running the following command in dom0 to [force USB 2.0 modes for the USB ports][force_usb2]:
+
+        lspci -nn | grep USB | cut -d '[' -f3 | cut -d ']' -f1 | xargs -I@ setpci -H1 -d @ d0.l=0
+
 
 Errors suggesting this issue:
 
@@ -475,3 +479,4 @@ No. Unlike many other virtualization systems, Qubes takes special effort to keep
 This has been achieved thanks to the careful use of Xen's stub domain feature. 
 For more details about how we improved on Xen's native stub domain use, see [here](https://blog.invisiblethings.org/2012/03/03/windows-support-coming-to-qubes.html).
 
+[force_usb2]: https://www.systutorials.com/qa/1908/how-to-force-a-usb-3-0-port-to-work-in-usb-2-0-mode-in-linux