Project

General

Profile

Feature #16925

Always add "debug nosplash" in troubleshooting mode

Added by sajolida 4 months ago. Updated 3 months ago.

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

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

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?


Related issues

Blocks Tails - Feature #14788: Add anchors to the troubleshooting parts of the installation doc In Progress 10/04/2017
Blocks Tails - Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing Confirmed 01/08/2016
Blocked by Tails - Bug #16677: Journal size is too small when booting with the "debug" boot option Confirmed

History

#1 Updated by sajolida 4 months ago

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

#2 Updated by sajolida 4 months ago

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 4 months ago

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

#4 Updated by sajolida 4 months ago

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

#5 Updated by sajolida 4 months ago

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

#6 Updated by intrigeri 4 months ago

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 #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 3 months ago

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

#8 Updated by sajolida 3 months ago

Very good to know!

Also available in: Atom PDF