Bug #9708

Known issues: add X220 to https://tails.boum.org/support/known_issues#index16h2

Added by BitingBird 2015-07-08 09:56:45 . Updated 2015-08-10 05:31:43 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Hardware support
Target version:
Tails_1.5
Start date:
2015-07-08
Due date:
% Done:

100%

Feature Branch:
emmapeel/feature/9708-x220-known_issues
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

X220 also boots fine with manually installed USB, doesn’t when installed with Tails Installer.

Subtasks

History

#1 Updated by intrigeri 2015-07-08 10:03:11

  • Assignee set to BitingBird
  • QA Check set to Info Needed

> X220 also boots fine with manually installed USB, doesn’t when installed with Tails Installer.

IIRC it depends on the UEFI boot settings in the BIOS, but I don’t remember exactly which settings work or not. Before we can document this, we need to know if Tails boots on that machine:

  • with UEFI enabled in the BIOS:
    • manually installed USB
    • device created with Tails Installer
  • with UEFI disabled in the BIOS (aka. legacy MBR boot):
    • manually installed USB
    • device created with Tails Installer

#2 Updated by BitingBird 2015-07-08 10:08:53

Answer from the user:

The only configuration listed in which it will boot is manually installed in legacy mode, if i try to boot a manually installed in uefi mode it instantly returns to the boot menu
Manually installed - Legacy: Yes, UEFI: No - Tails Installed: Neither

#3 Updated by intrigeri 2015-07-08 10:22:50

OK, thanks. What exactly happens when UEFI boot is enabled in the BIOS (but Secure boot is disabled), with a device created with Tails Installer?

#4 Updated by BitingBird 2015-07-08 11:02:45

A white background with black text (the live and live failsafe)
I can tab to edit boot options, but as soon as I try to boot, the system locks up and I have to hard reset
and an inverse gradient, the logo is not there, it’s weird

#5 Updated by intrigeri 2015-07-08 11:22:35

  • Status changed from New to Confirmed
  • QA Check deleted (Info Needed)

OK, looks like we now have all the info we need. Thanks!

#6 Updated by BitingBird 2015-07-08 11:35:04

  • Assignee deleted (BitingBird)

#7 Updated by intrigeri 2015-07-08 12:12:54

  • Assignee set to emmapeel

Please reassign to current frontdesk :)

#8 Updated by emmapeel 2015-07-10 04:31:26

  • Status changed from Confirmed to Fix committed
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to emmapeel/feature/9708-x220-known_issues

Please review emmapeel:feature/9708-x220-known_issues

#9 Updated by emmapeel 2015-07-10 04:31:45

  • Assignee deleted (emmapeel)

#10 Updated by sajolida 2015-07-10 12:24:44

  • Assignee set to sajolida

#11 Updated by intrigeri 2015-07-11 07:07:55

  • Status changed from Fix committed to In Progress

FYI, “Fix committed” means that a change has been merged into the branch next release will be based on, but not released yet.

#12 Updated by BitingBird 2015-07-29 09:14:07

  • Target version set to Tails_1.5

#13 Updated by sajolida 2015-08-04 04:57:43

  • Target version deleted (Tails_1.5)

#14 Updated by Anonymous 2015-08-09 12:06:43

Applied in changeset commit:da6196ce1f54004bfa6f5f4e160ccfba5bedbbc4.

#15 Updated by sajolida 2015-08-09 12:06:43

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

Applied in changeset commit:2c60507a478edcad4cac2c7be899052c16e96453.

#16 Updated by sajolida 2015-08-09 12:07:05

  • Assignee deleted (sajolida)
  • QA Check changed from Ready for QA to Pass

That was easy!

#17 Updated by BitingBird 2015-08-10 05:31:43

  • Target version set to Tails_1.5