Tails

#3 Updated by goupille 2018-08-09 15:30:21

goupille wrote:

> note that another user with an Asus ux550 (same chipset, proc and GPUs) saw the same issue, unfortunately, even if tails can boot with them, the boot parameters break the screen backlight.

for this particular computer, according to the user, the following parameters fix the issue without messing with the backlight :

acpi_osi=! acpi_osi="Windows 2009" nouveau.modeset=0

#4 Updated by goupille 2018-08-09 16:45:33

goupille wrote:

> > note that another user with an Asus ux550 (same chipset, proc and GPUs)

sorry it is an Asus FX503VD, same processor and GPUs

#6 Updated by intrigeri 2018-08-15 09:48:50

> A user reported being showed a “soft lockup - CPU#X stuck for 22s” at boot with a Dell XPS 15 9560, with a core i7-7700 dual GPU (Intel HD Graphics 630 and NVIDIA GeForce GTX 1050).

> just using the nouveau.modeset=0 parameter didn’t solve the issue, however, the following parameters did :

>

> acpi_osi=linux acpi_backlight=vendor nouveau.modeset=0
> 

According to the online resources you’ve pointed me to, acpi_rev_override=1 is a better solution, so please have the user try acpi_rev_override=1 nouveau.modeset=0; and if that does not work, acpi_rev_override=1 acpi_backlight=vendor nouveau.modeset=0.

#7 Updated by goupille 2018-08-16 19:17:50

intrigeri wrote:

> I’ll document the workaround for this one too but I cannot write “break the screen backlight”: I don’t even know what it means. Does it mean that the screen brightness cannot be controlled via hardware buttons? And/or cannot be controlled via the GNOME system menu?

sorry about that, according to the user, by “break the screen backlight” I mean that the screen brightness is set to 0, the user can see that something is displayed on the screen but there is no backlight. pushing the brightness cursor to the maximum with the keyboard or the Gnome menu, in the greeter or on Tails desktop, doesn’t change anything.

#9 Updated by goupille 2018-08-21 13:11:48

several users answered that

acpi_rev_override=1 nouveau.modeset=0

fixed the issue, including one user showed with a “hard lockup” error on an Asus ux550.

However the user with the asus FX503VD (brightness issues) said that these parameters present the same problem

#11 Updated by intrigeri 2018-09-11 08:36:31

Same question with 3.9.

#12 Updated by AtomiKe 2018-09-13 22:01:47

intrigeri wrote:
> Excellent, thanks! One last thing: did any of “your” users test with 3.9~rc1? If not, can you please ask them to test with and without acpi_rev_override=1 nouveau.modeset=0?

> Same question with 3.9.

Tested on an XPS 9560, with Tails 3.9. It doesn’t work without acpi_rev_override=1 nouveau.modeset=0.

#13 Updated by intrigeri 2018-09-14 06:37:44

> Tested on an XPS 9560, with Tails 3.9. It doesn’t work without acpi_rev_override=1 nouveau.modeset=0.

Thank AtomiKe! For avoidance of doubt:

• It does work with acpi_rev_override=1 nouveau.modeset=0, right?
• Neither of these two single options is sufficient in itself, right?

Once I have confirmation on these two questions, I’ll document the workaround :)

#14 Updated by intrigeri 2018-10-16 13:19:31

I got one report (c52297adde8509e04bcdf685eb7b5fbe) that says that acpi_osi=! nouveau.modeset=0 works fine on this laptop.