Feature #7230

Update the most important bits of documentation wrt. UEFI support

Added by intrigeri about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Tails_1.1
Start date:
2014-05-13
Due date:
% Done:

100%

Feature Branch:
feature/uefi
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

For Tails 1.1, we likely won’t have UEFI support 100% documented, but we should at least update:

  • Start Tails
  • Tails does not start
  • Known issues
  • Hardware requirements
  • Mac installation doc
  • manual test suite

Subtasks

Related issues

Blocks Tails - Feature #6562: Complete documentation for UEFI boot Resolved

History

#1 Updated by intrigeri about 11 years ago

#2 Updated by intrigeri about 11 years ago

  • blocks Feature #6562: Complete documentation for UEFI boot added

#3 Updated by intrigeri about 11 years ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Feature Branch set to feature/uefi

#4 Updated by intrigeri about 11 years ago

  • Assignee changed from intrigeri to sajolida
  • % Done changed from 10 to 20
  • QA Check set to Ready for QA

What I’ve done is:

  • On the known issues page, ask test reports on Tails 1.1+ for all systems that should now be supported in UEFI mode. Also, removed issues that are fixed by the UEFI support in 1.1.
  • On the “Tails does not start” page, suggest toggling between legacy BIOS <—> UEFI, instead of only UEFI—>legacy BIOS
  • On the page about starting Tails, documented how to start a UEFI-compatible Tails on Mac.
  • Moved UEFI known issues from the blueprint to support/known_issues.
  • Adapted a bit the text about Mac on the hardware requirements page.

#5 Updated by intrigeri about 11 years ago

@sajolida: when merging, please also mark the parent ticket “Fix committed”.

#6 Updated by sajolida about 11 years ago

  • Assignee changed from sajolida to intrigeri

#7 Updated by intrigeri about 11 years ago

  • Assignee changed from intrigeri to sajolida
  • QA Check changed from Ready for QA to Info Needed

I see nothing new on feature/uefi, and I cannot find any email that would tell me what I’m supposed to review. Your last email says “I fixed a bunch of documentation styling and merged it” => please clarify :)

#8 Updated by sajolida about 11 years ago

  • Assignee changed from sajolida to intrigeri
  • QA Check changed from Info Needed to Ready for QA

> I see nothing new on feature/uefi, and I cannot find any email that would tell me what I’m supposed to review. Your last email says “I fixed a bunch of documentation styling and merged it” => please clarify :)

Sorry, I think that I forgot to push. Now it should be there in
feature/uefi and merged into testing.

#9 Updated by intrigeri about 11 years ago

> Sorry, I think that I forgot to push. Now it should be there in
> feature/uefi and merged into testing.

Thanks! But… how am I supposed to find out the commits I’m supposed to review?

#10 Updated by intrigeri about 11 years ago

  • Assignee changed from intrigeri to sajolida
  • QA Check changed from Ready for QA to Info Needed

#11 Updated by intrigeri about 11 years ago

  • Status changed from In Progress to Fix committed
  • Assignee deleted (sajolida)
  • % Done changed from 20 to 100
  • QA Check changed from Info Needed to Pass

Hmm, sorry. I’ve reviewed the commits on top of feature/uefi, that I didn’t author. Good!

#12 Updated by BitingBird about 11 years ago

  • Status changed from Fix committed to Resolved