Tails

#1 Updated by mercedes508 2018-01-08 16:04:40

• Status changed from New to Confirmed

#2 Updated by intrigeri 2018-01-10 15:51:40

• Assignee changed from intrigeri to goupille
• QA Check set to Info Needed

Potential fixes:

1. Ensure the system boots in UEFI mode and not in Legacy BIOS mode.
2. Add the intel_pstate=disable boot option.
3. Ensure the BIOS is up-to-date.
4. If on a Windows computer, disable fastboot (“hiberboot”): https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html, https://www.trishtech.com/2013/07/how-to-disable-hiberboot-in-windows-8/

Now, I doubt that “Error parsing PCC subspaces from PCCT” is the actual problem.

#3 Updated by goupille 2018-01-13 18:36:57

• Subject changed from Gnome fails to start with an HP pavillion (broadwell chipset) to Tails fails to start with an HP pavillion (broadwell chipset)
• Assignee changed from goupille to intrigeri
• QA Check deleted (Info Needed)

Actually, the user confused ‘Tails greeter’ and ‘Boot Loader Menu’. The computer reboots just after the boot menu, whatever mode the user choose (tails or troubleshooting).

regarding the workaround suggested previously:

the computer seems to have graphics issues when booting tails in UEFI (light grey boot menu instead of the regular black), there is no BIOS update provided by the vendor at the moment, fastboot has been disabled, the suggested boot parameter added, and yet, Tails still doesn’t start and the computer keeps rebooting after the boot loader menu.

#4 Updated by intrigeri 2018-01-15 11:46:26

• Description updated

goupille wrote:
> Actually, the user confused ‘Tails greeter’ and ‘Boot Loader Menu’. The computer reboots just after the boot menu, whatever mode the user choose (tails or troubleshooting).

I had guessed, but thanks anyway. Adjusted the description accordingly.

> the computer seems to have graphics issues when booting tails in UEFI (light grey boot menu instead of the regular black),

As discussed on XMPP that’s the expected behavior in UEFI mode.

> there is no BIOS update provided by the vendor at the moment, fastboot has been disabled, the suggested boot parameter added, and yet, Tails still doesn’t start and the computer keeps rebooting after the boot loader menu.

:/

So that’s probably a regression in the kernel (we’ve upgraded to 4.13 in Tails 3.3). It would be interested to know which “previous versions of Tails” did work, but frankly I don’t think we can do better than 1. document the problem (I’ll do it right away); 2. ask the OP to test with newer kernels (e.g. 4.14.13 should be available later today); 3. wait for someone to fix this regression upstream.

Now, as usual with low level bugs, if the OP is technical enough to report this upstream and compile kernels, they could do that.

#5 Updated by intrigeri 2018-01-15 11:46:38

• blocks Feature #13245: Core work 2018Q1: Foundations Team added

#6 Updated by intrigeri 2018-01-15 11:56:36

• Status changed from Confirmed to Resolved
• % Done changed from 0 to 100

Applied in changeset commit:449ca234bdec82a6d1ee5a3e30658b80e43fbc9a.

#7 Updated by anonym 2018-01-23 19:59:36

• Status changed from Resolved to Confirmed
• QA Check set to Info Needed

This ticket was not supposed to be resolved, right?

#8 Updated by intrigeri 2018-01-24 06:55:06

• Status changed from Confirmed to In Progress
• Assignee changed from intrigeri to anonym

anonym wrote:
> This ticket was not supposed to be resolved, right?

Yes, I closed it intentionally. What else do you think we should do?

#9 Updated by intrigeri 2018-02-20 08:50:01

• Target version set to Tails_3.6

Ping?

#10 Updated by bertagaz 2018-03-14 11:32:28

• Target version changed from Tails_3.6 to Tails_3.7

#11 Updated by anonym 2018-03-28 09:42:14

• Status changed from In Progress to Resolved
• QA Check deleted (Info Needed)