Bug #9092

Start page should mention to disable fast boot, secure boot etc

Added by BitingBird 2015-03-22 13:05:27 . Updated 2015-08-13 02:38:46 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2015-03-22
Due date:
% Done:

100%

Feature Branch:
doc/9092-start_tricks
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

https://tails.boum.org/doc/first_steps/start_tails links to external doc, but the major ideas should be mentionned: disable fast boot, secure boot etc


Subtasks


History

#1 Updated by sajolida 2015-03-22 21:52:24

Why not. Keep in mind that we have this already in “Tails does not start”. See /doc/first_steps/bug_reporting/tails_does_not_start.

#2 Updated by BitingBird 2015-03-23 02:27:03

  • Target version set to Tails_1.4

#3 Updated by BitingBird 2015-03-27 02:19:09

  • Status changed from Confirmed to In Progress
  • Assignee changed from BitingBird to sajolida
  • QA Check set to Ready for QA
  • Feature Branch set to bitingbird:doc/9092-start_tricks

I moved most of “Tails does not start” instructions about BIOS settings in “start Tails”. More and more users have computers that require this, so I think it doesn’t make sense to put it somewhere else.

I created a dedicated section for it (called “Advanced BIOS settings”), with a toc and a link from “Tails does not start”. I kept the advice about upgrading the BIOS in “Tails does not start”, but I put it in a note. I removed the “if you know about BIOS configuration”, because it’s scary, and disabling secure boot is not more complicated than changing boot order. I gave a hint to look a vendor’s websites for BIOS upgrades.

Built, looks good. Please review and merge :)

#4 Updated by sajolida 2015-04-24 14:38:26

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Dev Needed

Thanks for working on this.

I think you’re going in the right direction but we can further improve
the structure of your doc.

The “Advanced BIOS” section only applies to PC actually (Mac don’t
really have a BIOS as we know it), so I suggest merging it with the
already existing “PC” section on the same page. This will avoid making
people jump around too much and read irrelevant information.

Then I propose to restructure it as a numbered list in the order to you
started to implement:

1. Edit the boot order.
2. Propose to disable funky features (Fast boot, Secure mode).
3. Switch UEFI to Legacy and vice versa (Legacy mode, CSM boot).
4. Try to upgrade your BIOS version.

Making it clear that people should try to restart between each step.

Then on /doc/first_steps/bug_reporting/tails_does_not_start.mdwn this
new stuff should only advertised if “Tails does not start at all”.

Also note that most BIOS have a shortcut to select a boot device
(instead of modifying the boot order once and for good) and that this
should be enough in most cases. We’ll try to work on that as part of the
web assistant so don’t kill yourself over it.

#5 Updated by BitingBird 2015-05-04 08:49:38

  • Assignee changed from BitingBird to sajolida
  • QA Check changed from Dev Needed to Ready for QA

Implemented all the changes you suggested, except the shortcut to select a boot device, as I think the explanations would be really long.

Built, had to fix the indentation to have the list numbered right, looks good now :)

Please review and merge !

#6 Updated by sajolida 2015-05-12 14:35:46

  • Assignee changed from sajolida to BitingBird
  • Target version deleted (Tails_1.4)
  • QA Check changed from Ready for QA to Dev Needed
  • Feature Branch changed from bitingbird:doc/9092-start_tricks to doc/9092-start_tricks

Good!

I would merge it as it is right now. But as a last thing, could you rewrite the introductory sentence about “PC” to adjust to the new boot menu. “You should see a welcome screen prompting you to choose your language.” This is not the case anymore since we have Tails Greeter. Maybe you can insert the image that we already have from the boot menu.

I pushed a few commits so make sure to fetch them.

#7 Updated by BitingBird 2015-07-05 04:45:33

  • Target version set to Tails_1.5
  • % Done changed from 0 to 50

#8 Updated by BitingBird 2015-07-05 07:20:37

  • Assignee changed from BitingBird to sajolida
  • QA Check changed from Dev Needed to Ready for QA

Removed the reference to the language prompt, replace with a link to startup_options#boot_menu. I didn’t copy the image, because I don’t see the point in repeting information (maybe a version of the image without the options at the bottom would make sense, but I didn’t find one).

Built, looks good - please review :)

#9 Updated by sajolida 2015-08-04 04:58:45

  • Target version deleted (Tails_1.5)

#10 Updated by BitingBird 2015-08-04 05:18:13

  • Target version set to Tails_1.6

#11 Updated by sajolida 2015-08-09 11:35:29

  • Assignee changed from sajolida to BitingBird

Don’t reviewing this. We’re almost there. I had an image of the boot menu without option ready in the Windows scenario of the future Installation Assistant so I moved it to the main documentation and inserted it on top of the page (it’s useful in any case).

I also fixed some other references to the old boot menu (for DVD and Mac).

So please review 2d9bd03..7628785 and then I can merge this :)

#12 Updated by BitingBird 2015-08-10 05:24:58

  • Assignee changed from BitingBird to sajolida
  • QA Check changed from Ready for QA to Dev Needed

Well, in 7628785a you removed the link to boot menu. I think it should be added to each occurrence instead, don’t you think?

#13 Updated by sajolida 2015-08-11 04:27:43

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Dev Needed to Info Needed

I did that on purpose. Since I added an image of the boot menu on top of the page, I felt like linking to /doc/first_steps/startup_options was superflous because the notion of “boot menu” is defined already on the same page by the image and actually counterproductive since we don’t want people to jump back to /doc/first_steps/startup_options with no actual concrete benefit.

But maybe I misunderstood. What would be, for you, the benefit of this link on top of having the image embed on this image as added by 5a1bb2f?

#14 Updated by BitingBird 2015-08-11 04:32:10

  • Assignee changed from BitingBird to sajolida
  • % Done changed from 50 to 80
  • QA Check changed from Info Needed to Pass

OK, checked again and I see how that’s not needed anymore.

Please merge then :)

#15 Updated by sajolida 2015-08-12 09:59:59

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

Applied in changeset commit:e7d23c2be8d3fb818ed7192fc6bba1eb763cc3fb.

#16 Updated by sajolida 2015-08-12 10:00:44

  • Assignee deleted (sajolida)
  • QA Check deleted (Pass)

Merged, then :)

#17 Updated by BitingBird 2015-08-13 02:38:46

Youhou :)