Document AQ envs, and some more for AQ_NO_MODIFIERS (#776)

* document AQ_NO_MODIFIERS

* document all AQ env vars

pages/Configuring/Environment-variables.md

@@ -40,6 +40,14 @@ environment on traditional Linux distros.
 - `HYPRLAND_NO_SD_NOTIFY=1` - If systemd, disables the `sd_notify` calls.
 - `HYPRLAND_NO_SD_VARS=1` - Disables management of variables in systemd and dbus activation environments.
 
+## Aquamarine Environment Variables <!-- ref https://github.com/hyprwm/aquamarine/blob/main/docs/env.md -->
+
+- `AQ_TRACE=1` - Enables more verbose logging.
+- `AQ_DRM_DEVICES=` - Set an explicit list of DRM devices (GPUs) to use. It's a colon-separated list of paths, with the first being the primary.
+  E.g. `/dev/dri/card1:/dev/dri/card0`
+- `AQ_MGPU_NO_EXPLICIT=1` - Disables explicit syncing on mgpu buffers
+- `AQ_NO_MODIFIERS=1` - Disables modifiers for DRM buffers
+
 ## Toolkit Backend Variables
 
 - `env = GDK_BACKEND,wayland,x11,*` - GTK: Use wayland if available. If not: try x11, then any other GDK backend.

pages/FAQ/_index.md

@@ -35,6 +35,13 @@ _[wiki page](../Crashes-and-Bugs)_
 For Nvidia graphics - This issue appears to be resolved when using Nvidia
 Drivers 525.60.11 or later, but it may persist with older drivers.
 
+For systems with limited hardware (Ex. iGPU, USB-C, USB Hubs) - Set `env = AQ_NO_MODIFIERS,1` in your config \
+To diagnose if you have the exact problem above you can get a [DRM log](https://wiki.hyprland.org/Crashes-and-Bugs/#debugging-drm-issues) and look for
+
+```
+Requested display configuration exceeds system DDB limitations
+```
+
 Outside those, there is a way to fix it that _might_ work for you though:
 
 **Option 1:** Use _only_ the external monitor