GitLab

https://www.plainlanguage.gov/guidelines/words/avoid-noun-strings/

We don't have a call for feedback there anymore, and don't need
more people to tell us these cards are not all well supported:
we already know, and can't do anything about it.

We keep getting reports about other affected graphics cards in these families,
that are not explicitly listed, and then users did not try the workaround,
because they thought it did not apply to their hardware.

Due to a misunderstanding, so far Help Desk did not forward this info anywhere,
so we did not add those cards to the list. And then other users would report the
same problem over and over again.

So, let's:

 - Give users better means to figure out what workaround they should try,
   so they can solve the problem themselves.

 - As a consequence, decrease the workload of Help Desk (processing such
   reports) and FT (adding cards to the list).

Closes #17399

We don't have a call for feedback there anymore, and don't need
more people to tell us these NVIDIA cards are not all well supported:
we already know, and can't do anything about it.

Help Desk tells me they get lots of reports from users about documented
workarounds not being sufficient.

The fact these workarounds don't always work is entirely expected: many of them
are more in the "worth trying, fingers crossed" category than confirmed
working solutions.

So, let's set users' expectations in a more realistic manner,
and don't ask them to tell Help Desk things we already know
(Help Desk has to check every time if this is indeed something we already know).

Another approach could be to document workarounds, and their status
(confirmed working or worth trying) for every graphics card.
I don't think it's realistic that we build and maintain this database:

 - Some workarounds are confirmed working for 1 graphics card in a given
   family, and worth trying on other graphics cards from the same family.

 - The status of every workaround can change from one Tails version to the next.
   We won't learn about this nor update our doc accordingly.

Regression brought by 4.12, for some reason.

the output format slightly changed

Closes #17155

Closes #17759

#17759 (comment 151077)

On some systems with an Intel integrated graphics card and a Nvidia or AMD
discrete one, setting xorg-driver=modesetting forces X.Org to use the Intel
card, which works.

On some systems with an Intel integrated graphics card and an AMD discrete one,
setting xorg-driver=modesetting forces X.Org to use the Intel card,
which works.

Now all this section is about the Welcome Screen only.

These options are mostly useful for debugging hardware support and power
users so they belong in "Advanced topics".

The NV160 column on https://nouveau.freedesktop.org/wiki/FeatureMatrix/ is
basically a list of "TODO" items, so let's not make users and help desk
waste too much time trying and debugging.

I've asked goupille to confirm it was really this workaround that fixed
a problem on a GTX 1050, but let's be optimistic.