Tails

#4 Updated by intrigeri 2019-11-01 10:49:20

Public part of Bug #16875#note-3:

• Tails 3.16
• computer is dell xps 15 9560
• Intel Corporation HD Graphics 630 [8086:591b] (rev04)

None of the 4 aforementioned workarounds is effective.

#6 Updated by numbat 2019-11-26 12:20:37

A user with the same graphic board claims troubleshooting mode works. I’m asking them to try out boot options from https://tails.boum.org/support/known_issues/graphics/#index3h2

#7 Updated by numbat 2020-01-01 16:36:15

All options have been tried out, no success. Screen freezes.

I asked the user to try out Debian Live.

#8 Updated by numbat 2020-01-02 15:01:10

Another report from a user with the latest Tails. Perhaps we should add this board to the list of known graphic cards that don’t work?

#10 Updated by goupille 2020-01-16 17:33:49

a user facing this error when starting Tails tried to start Debian-live stable succefully (the computer froze when shutting down, tho), but it seems that this computer doesn’t have only one GPU (a screenshot mention ‘nouveau’, I asked the user to confirm).

#11 Updated by numbat 2020-01-21 10:35:10

A user has reported that using Tails 4.2.2 with the option nouveau.noaccel=1 seems to work. This user has multiple graphic cards, the other one is a NVIDIA GTX 1650 mobile.

#12 Updated by goupille 2020-01-21 16:54:08

I just took a look at the user affected on my plate and it seems that at least 2 of them have an nvidia pascal (gtx 1050), I asked them to try the workarounds we usually propose for those gpu, but I wonder if the error screen does mention the right GPU…

#13 Updated by numbat 2020-01-24 10:30:38

Same issue with AMD GPU on Mac

Error starting GDM with your graphics card: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:7340] (rev 40).

User tried radeon.modeset=0 (no result)

System Info:
MacBook Pro - 16" 2019)
2.4 GHz 8-Core Intel Core i9
Intel UHD Graphics 630 1536 MB
AMD Radeon Pro 5500M

#14 Updated by emmapeel 2020-01-30 09:27:21

A user with:

• Intel UHD Graphics 630
• 4095MB NVIDIA GeForce GTX 1650

reports that only the startup option nouveau.noaccel=1 makes their laptop start.

#15 Updated by goupille 2020-02-08 12:31:21

2 new users affected, one with a gtx 1050 (fixed with nouveau.noaccel=0) and the other with an unknown nvidia card (fixed with nouveau.noaccel=1)

#16 Updated by goupille 2020-03-05 14:31:46

another user affected, nvidia geforce gtx 1050 and Intel HD graphic 630 [8086:591b] rev 04, the issue was solved with (the other usual workarounds were not working)

nouveau.modeset=0

#17 Updated by intrigeri 2020-03-15 18:18:09

Hi @numbat,

> Another report from a user with the latest Tails. Perhaps we should add this board to the list of known graphic cards that don’t work?

First, I’d like to know if this graphics card was actually used: most recent reports of this problem were about dual-GPU computers and the workarounds that helped suggest that the Intel GPU was not used.

#18 Updated by intrigeri 2020-03-15 18:31:33

Hi @numbat,

> A user has reported that using Tails 4.2.2 with the option nouveau.noaccel=1 seems to work. This user has multiple graphic cards, the other one is a NVIDIA GTX 1650 mobile.

The way I see it, the fact that nouveau.noaccel=1 fixes the problem indicates that 1 of these 2 things is happening:

• Either this puts the NVIDIA card in a mode that GNOME won’t support, so the Intel HD 630 card is used instead, and it works fine. If that’s the case, then this ticket can be closed as resolved.
• Or the NVIDIA card is used and the workaround fixes it. I’ve documented the workaround. In this case, the Intel HD 630 card is not used so this is off-topic on this ticket.

In the future, for dual-GPU computers, we need to check in the logs which card is actually used, before assuming the problem is with Intel HD 630 support.

#19 Updated by intrigeri 2020-03-15 18:32:31

Hi @numbat,

> Same issue with AMD GPU on Mac
>
>

> Error starting GDM with your graphics card: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:7340] (rev 40).
> 

Was the Intel HD 630 card used? If not, then it’s a problem with the AMD one.

#20 Updated by intrigeri 2020-03-15 18:33:02

Hi @emmapeel,

> A user with:
> * Intel UHD Graphics 630
> * 4095MB NVIDIA GeForce GTX 1650
>
> reports that only the startup option nouveau.noaccel=1 makes their laptop start.

I’ve documented this for the GTX 1650.

In the future, for dual-GPU computers, we need to check in the logs which card is actually used, before assuming the problem is with Intel HD 630 support.

#21 Updated by intrigeri 2020-03-15 18:37:09

Hi @goupille,

> 2 new users affected, one with a gtx 1050 (fixed with nouveau.noaccel=0)

Wow, this one is new to me and a bit surprising (I’m ready to be surprised, especially in nvidia-land ;)

Could you confirm it’s really nouveau.noaccel=0, and not for example nouveau.modeset=0?

Either way, it does not hurt (much) so I’ve documented it!

> and the other with an unknown nvidia card (fixed with nouveau.noaccel=1)

This one is documented for most nvidia cards already ⇒ nothing to do :)

#22 Updated by intrigeri 2020-03-15 18:39:17

Hi @goupille,

> another user affected, nvidia geforce gtx 1050 and Intel HD graphic 630 [8086:591b] rev 04, the issue was solved with (the other usual workarounds were not working)
>
>

> nouveau.modeset=0
> 

OK, this one is already documented for GTX 1050, and here as well, I’m pretty sure the Intel HD 630 is not used.