Bug #9044

Chromebook C720-2800 requires tweaks to boot properly

Added by emmapeel 2015-03-10 17:31:28 . Updated 2015-05-12 18:41:14 .

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

100%

Feature Branch:
bugfix/9044-syslinux-on-chromebooks
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Reported by user, hardware related:

The Chromebook is 64 bits, but when booting from vmlinuz2/initrd2.img is not booting (restarts some seconds after boot screen)

Changing vmlinuz2/initrd2.img to vmlinuz and initrd on the boot menu makes it boot.


Subtasks


History

#1 Updated by intrigeri 2015-03-12 13:06:09

  • Subject changed from Chromebook C720-2800 tries to boot with wrong image to Chromebook C720-2800 requires tweaks to boot properly
  • Assignee set to emmapeel
  • Target version changed from Tails_1.3 to Tails_1.3.2
  • QA Check set to Info Needed

Some Chromebooks need something like mem=1500m to boot properly, as discussed a few months ago (possibly without any conclusion reached, nor action taken to document it) on our support mailing-list. Is it the case for that one? I suspect the 32-bit kernel boots (as opposed to the 64-bit one) simply because it doesn’t recognize all the available RAM, or similar.

(Also, please don’t set “Target version” to a release that’s already out — thanks :)

#2 Updated by BitingBird 2015-03-12 20:45:02

This should be added to the know issues, it’s currently not listed.

#3 Updated by intrigeri 2015-03-13 08:51:43

> This should be added to the know issues, it’s currently not listed.

Indeed, we’ve removed it with commit:b793bc1 since we were told that it wasn’t needed anymore. But since then we’ve had a few reports that some mem= parameter was needed.

#4 Updated by BitingBird 2015-03-13 13:17:30

Maybe we could just revert this commit and see if we still get reports?

#5 Updated by intrigeri 2015-03-17 11:55:50

> Maybe we could just revert this commit and see if we still get reports?

That would be a good start. I suspect the entry in known issues should be made a bit more generic, because the workaround is apparently needed for various kinds of Chromebooks. That’s frontdesk job.

Frontdesk: bonus points if you look into your tails-support@ archives to dig the useful information, pointers and testing reports we’ve gathered about this some months ago.

#6 Updated by intrigeri 2015-03-19 09:16:37

This might actually be caused by a bug in syslinux:

A patch was proposed upstream, applied in Ubuntu, and then proposed to Debian.

emmapeel, assuming I publish an ISO with that patch applied, will you be able to ask the bug reporter to test it?

#7 Updated by mercedes508 2015-03-19 21:05:31

I might ask at least one user to try that ISO.

#8 Updated by BitingBird 2015-03-19 23:26:05

  • Assignee changed from emmapeel to intrigeri
  • QA Check deleted (Info Needed)

#9 Updated by emmapeel 2015-03-20 09:49:02

intrigeri wrote:
> A patch was proposed upstream, applied in Ubuntu, and then proposed to Debian.
>
> emmapeel, assuming I publish an ISO with that patch applied, will you be able to ask the bug reporter to test it?

sure! he seemed prone to tinkering…

#10 Updated by emmapeel 2015-03-20 09:49:56

intrigeri wrote:
> A patch was proposed upstream, applied in Ubuntu, and then proposed to Debian.
>
> emmapeel, assuming I publish an ISO with that patch applied, will you be able to ask the bug reporter to test it?

sure! user seemed prone to tinkering…

#11 Updated by intrigeri 2015-03-20 10:33:56

  • Status changed from Confirmed to In Progress

Applied in changeset commit:df0275a4bf241e09615aab2c9902d02225376329.

#12 Updated by intrigeri 2015-03-20 10:34:48

  • % Done changed from 0 to 10

#13 Updated by intrigeri 2015-03-20 21:48:28

Applied in changeset commit:a16f7efb78323e2c56a6348773bb47b13d6b8e66.

#14 Updated by intrigeri 2015-03-20 23:20:57

  • Assignee changed from intrigeri to mercedes508
  • QA Check set to Info Needed

The latest Tails/Jessie experimental nightly build has the syslinux patch => please ask affected users to try it and report back. Thanks!

#15 Updated by mercedes508 2015-03-24 19:00:31

  • Assignee changed from mercedes508 to intrigeri

The only user I could ask to test that image reported that it works fine.

#16 Updated by intrigeri 2015-03-25 13:02:43

  • Target version changed from Tails_1.3.2 to Tails_1.4
  • QA Check deleted (Info Needed)

I’ll probably won’t have time to deal with that for 1.3.2. Also, I’d like to give a little bit more time to upstream to comment on the proposed patch (applied by Ubuntu and in Tails/Jessie, but not in Debian nor upstream yet).

#17 Updated by intrigeri 2015-03-26 17:21:32

  • Assignee deleted (intrigeri)
  • % Done changed from 10 to 50
  • QA Check set to Ready for QA

#18 Updated by anonym 2015-04-15 09:25:18

  • Assignee set to intrigeri
  • QA Check changed from Ready for QA to Info Needed
  • Feature Branch set to bugfix/9044-syslinux-on-chromebooks

See review’n’merge request thread on tails-dev@.

#19 Updated by intrigeri 2015-04-15 12:42:28

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

#20 Updated by anonym 2015-04-28 14:04:22

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:7142f681ee9497edda51df784a5500c9bb95cc7b.

#21 Updated by anonym 2015-04-28 14:04:42

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

#22 Updated by BitingBird 2015-05-12 18:41:14

  • Status changed from Fix committed to Resolved