#11923 NORM 12.1.0: XO 1.5 with os13 takes long time to boot the first time and doesn't show the Boot Screen
Zarro Boogs per Child
bugtracker at laptop.org
Sun Jun 10 21:17:42 EDT 2012
#11923: XO 1.5 with os13 takes long time to boot the first time and doesn't show
the Boot Screen
---------------------------------+------------------------------------------
Reporter: humitos | Owner: dsd
Type: defect | Status: new
Priority: normal | Milestone: 12.1.0
Component: distro | Version: Development build as of this date
Resolution: | Keywords: os13
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
---------------------------------+------------------------------------------
Changes (by Quozl):
* version: not specified => Development build as of this date
Comment:
Replying to [comment:2 godiard]:
> Probably the first boot is slower because of filesystem resizing.
This is speculation. We have no proof in this ticket ''yet'' that the
filesystem resize is responsible for the slowness. The test results in
#10040 and elsewhere suggest a time of the order of seconds for the
resize, not four minutes. A kernel log of a first boot would verify this,
since the resize emits progress timestamps there. Let's look at a log.
Replying to [comment:6 humitos]:
> Why this resize is performed at first boot?
See #10040 for discussion. A resize is necessary so that only a single
image needs to be provided, instead of .zd2, .zd4 and .zd8 according to
the size of the internal storage of the laptop. If the resize is not done
on first boot, then the amount of free space on first boot will be
incorrect. First boot seems to be the right time. Alternative
suggestions welcome, maybe we missed some opportunity.
Also, next time you are reporting a boot problem, could you please attach
a serial cable and see if you can capture console output? The pictures
took a long time for me to download. Let us know if you need serial
adapter and cable.
Regarding your trac usage questions; for builds leading up to a release,
such as os13, the version can be set to "Development build as of this
date". Component can be left unchanged if you don't yet know what
component is likely to be the cause.
Your first ticket description was very well written, thanks. Way above
the quality we normally see.
--
Ticket URL: <http://dev.laptop.org/ticket/11923#comment:7>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list