Feature #16925

Always add "debug nosplash" in troubleshooting mode

Added by sajolida 2019-07-30 18:11:35 . Updated 2019-11-22 07:52:29 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Wait
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

In our troubleshooting instructions we ask people at the boot loader menu to:

  • Use the “Tails (Troubleshooting Mode)”.
  • Add the “debug nosplash” boot options.

Why don’t we always add “debug nosplash” to this mode since it’s a troubleshooting mode?

Subtasks

Related issues

Blocks Tails - Feature #14788: Add anchors to the troubleshooting parts of the installation doc In Progress 2017-10-04
Blocked by Tails - Bug #16677: Journal size is too small when booting with the "debug" boot option Confirmed

History

#1 Updated by sajolida 2019-07-30 18:11:50

  • related to Feature #14788: Add anchors to the troubleshooting parts of the installation doc added

#2 Updated by sajolida 2019-07-30 18:54:38

And more generally, I’d like to know how could we use this Troubleshooting Mode to simplify the troubleshooting instructions in “Tails does not start entirely”: https://tails.boum.org/install/win/usb/#greeter.

Right now we are asking people to:

  • Try the Troubleshooting Mode.
  • Go back to the normal mode if the Troubleshooting Mode was not any better.
  • Edit the command line of the normal mode to remove quiet and add debug nosplash.

Keeping in mind that people will try the Troubleshooting Mode only if the normal mode doesn’t work, if we can ensure that the Troubleshooting Mode won’t give less interesting debugging information than the normal mode, then why not instruct people to always use the Troubleshooting Mode if the normal mode doesn’t work?

In other words, are there cases where we could give someone a useful workaround from information extracted from the normal mode with debugging but that we couldn’t give from information from the Troubleshooting Mode only.

Am I make sense at all?

#3 Updated by sajolida 2019-07-30 19:12:22

  • related to deleted (Feature #14788: Add anchors to the troubleshooting parts of the installation doc)

#4 Updated by sajolida 2019-07-30 19:12:34

  • blocks Feature #14788: Add anchors to the troubleshooting parts of the installation doc added

#5 Updated by sajolida 2019-07-30 19:33:23

  • blocks Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing added

#6 Updated by intrigeri 2019-07-30 22:51:27

> Keeping in mind that people will try the Troubleshooting Mode only if the normal mode doesn’t work, if we can ensure that the Troubleshooting Mode won’t give less interesting debugging information than the normal mode, then why not instruct people to always use the Troubleshooting Mode if the normal mode doesn’t work?

I think Bug #16677 makes “we can ensure that the Troubleshooting Mode won’t give less interesting debugging information than the normal mode” untrue in the current state of things. Once that problem is solved, then yeah, great idea!

#7 Updated by sajolida 2019-08-01 18:23:26

  • blocked by Bug #16677: Journal size is too small when booting with the "debug" boot option added

#8 Updated by sajolida 2019-08-01 18:24:30

Very good to know!

#9 Updated by sajolida 2019-11-22 07:52:29

  • Status changed from New to Confirmed
  • Type of work changed from Code to Wait

#10 Updated by sajolida 2019-11-22 07:52:44

  • blocked by deleted (Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing)