Document workaround for Tails freezing with NVIDIA GTX 1080 when HTC Vive headset is connected to HDMI
- Problem: Tails freezes (not sure at which time exactly)
- Workaround: unplug that headset before starting Tails
- Affected hardware:
- at least NVIDIA GTX 1080, but most likely all Pascal GPUs
- at least HTC Vive headset, and perhaps more HDMI devices
More generally, various reports tell us that a number of problems with nouveau drivers for NVIDIA graphics can be workaround’ed by unplugging non-essential devices connected to the NVIDIA thing (e.g. 2nd display, sound outputs etc.) or by plugging displays on a different port.
It might be worth pointing to https://nouveau.freedesktop.org/wiki/CodeNames/ (so users can identify their hardware) and https://nouveau.freedesktop.org/wiki/FeatureMatrix/ (so that users can tell whether the issue they’re experiencing is Tails-specific or not).
Related to Tails -
Related to Tails -
Blocks Tails -
#9 Updated by 110100111011 2017-11-22 05:02:08
Tails no longer crashes in 3.3 with a HTC Vive connected.
It starts correctly, just with the issue that the HTC Vive is seen by Tails as the primarmy monitor. So the Tails Greeter and everything else will appear on the HTC Vive Display, and since you can’t see anything on that due to the lenses, you practically have to disconnect the HTC Vive again to be able to use Tails.
Feature #14965 would work without the encryption, that would fix this issue since then Tails could already turn off the HTC Vive Display before the Greeter appears.
#12 Updated by sajolida 2018-02-16 19:30:34
- Status changed from Confirmed to Resolved
- Assignee deleted (
- Target version deleted (
Bug #14697#note-9, I think that it’s not worth documenting this.
It might be worth documenting the generic workaround that intrigeri describes in the description of the ticket: “number of problems with nouveau drivers for NVIDIA graphics can be workaround’ed by unplugging non-essential devices connected to the NVIDIA thing (e.g. 2nd display, sound outputs etc.) or by plugging displays on a different port.”
So please reopen this ticket if more such reports are coming in after Tails 3.3.