XO Troubleshooting PowerOn: Difference between revisions
(Removed redundant reference to a three year old problem, plus a pointer to a US-centric repair policy (this document was developed for deployments)) |
|||
| (33 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
{{OLPC}}{{Translations}} |
|||
This is the portion of the [[XO Troubleshooting Guide|XO Troubleshooting Guide]] for diagnosing problems turning on an [[ |
This is the portion of the [[XO Troubleshooting Guide|XO Troubleshooting Guide]] for diagnosing problems turning on an [[Hardware_specification#Laptop_Hardware|XO laptop]]. |
||
XO-1 laptops which can't boot because of an "'''invalid system date'''" should run the [[Fix Clock|"Fix Clock"]] procedure to reset the system date, and should perhaps replace the clock battery. |
|||
==Hello== |
|||
==Welcome== |
|||
For an introduction to the different boot options selectable while powering on, see the [[Cheat codes]]. |
For an introduction to the different boot options selectable while powering on, see the [[Cheat codes]]. |
||
All of these tests assume that |
All of these tests assume that two known good sources of power are available: a charged battery and a power adapter. To debug problems with the power source, and battery charging issues, see [[#Power_and_Battery_problems|Power and Battery problems]]. |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
Start by pressing the power button for a second. |
|||
| ⚫ | |||
Please try [[XO_Full_Reset|Resetting the Embedded Controller]]. |
|||
| ⚫ | |||
'''Please try [[XO_Full_Reset|resetting the Embedded Controller]].''' Pay attention to the battery LED when power is first reapplied. It should flash orange momentarily (about a quarter of a second). |
|||
| ⚫ | |||
If it does not flash, then the [[Embedded_controller|Embedded Controller]] is not operating properly, and the motherboard should be replaced. |
|||
:In these cases, the [[Embedded_controller|Embedded Controller]] Flash chip should be replaced as the first attempt to repair the motherboard. See [[XO_Replacing_SPI_flash|replacing the embedded controller flash]]. |
|||
If the power LED doesn't turn on, but '''the laptop proceeds to illuminate the backlight and even boot''', the problem may be either the LEDs themselves or the power LED driver (Q39, DDTC144EUA). The LEDs are in series, so if one fails they may both fail to light. |
|||
If both power sources are working, then the motherboard is broken. The possible failure modes are numerous, and deserve a second troubleshooting guide. |
|||
On rare occasions, the power button becomes stuck mechanically. In this case, the laptop does not detect the depression of the power button, and does not turn on. '''Ensure that the power button is moving freely.''' |
|||
(This section needs a step-by-step through the normal start-up sequence with branching options for each possibility. This section needs to take into account possibilities which include broken power LED, boot sound disabled in software, screen backlight broken or disconnected, possibilities of booting from a non-standard source (was an SD card accidentally left in the slot?) or secure vs. insecure startup, etc. I would also argue only diagnosis steps should appear here, with recovery steps located in a different section.) |
|||
''Insert photo of 'stuck' power button vs. 'unstuck' power button'' |
|||
If the battery LED flashed on restoration of power, the power button isn't stuck, and no other signs of life are detected, then the failure mode is unknown. Replace the motherboard to repair. |
|||
| ⚫ | |||
:In these cases, the [[Embedded_controller|Embedded Controller]] Flash chip is a common source of problems. Using a serial cable, check to see what Open Firmware reports while booting. If it reports an error like "FortDEAD" or "Unimplemented Package Interface" or "Error unpacking code" it should be replaced as the first attempt to repair the motherboard. See [[XO_Replacing_SPI_flash|replacing the embedded controller flash]]. |
|||
As the XO starts, the power LED turns on and the screen should be initialized with text or graphics displayed. |
|||
The backlight for the screen may or may not be active. |
|||
== |
==Does the display activate ? == |
||
The power LED indicates that the |
The power LED indicates that the [[Embedded_controller|Embedded Controller]] has enabled the power to the CPU. [[Open Firmware]] (OFW) begins executing. The next visible step is turning on the display. The LCD display should be initialized with white, then begin to show text or graphics. The backlight for the screen should be turned on, even if the backlight was previously turned off. |
||
If this does not happen then the boot sequence may not be reaching [[Open Firmware]] or |
If this does not happen then the boot sequence may not be reaching [[Open Firmware]], or OFW may be crashing early in the boot process. The way to tell is to look at the Microphone activity LED. The default state of the microphone LED is lit. One of the first steps [[Open Firmware]] does is to turn off the microphone LED. '''If the power LED and the microphone LED are both lit then a serious boot error has occurred and the motherboard needs replacing.''' |
||
On an XO-1.5, watch the microphone LED as you press the power button ... if the microphone LED is lit, then fades away, the motherboard needs replacing. <!-- #10314 --> |
|||
If the power LED is lit and the Mic LED is not then backlight for the screen may or may not be active, the LCD may be non-functional or the [[Fix_Clock|RTC Problem]] may have occured. |
|||
Did the boot sound play ? |
|||
===Display does not initialize. Boot sound does not play=== |
|||
This usually indicates a broken motherboard or a [[Fix_Clock|Real Time Clock battery problem in conjunction with early firmware]]. |
|||
=== |
===Boot sound does not play=== |
||
| ⚫ | This usually indicates a broken motherboard or a [[Fix_Clock|Real Time Clock battery problem in conjunction with early firmware]]. Some machines in our early production runs (before Jan. 2008) both had a problem with the Real Time Clock battery holder and had a version of [[Open Firmware]] (earlier than Q2D07) which locked up when it encountered a reset clock. The [[Fix_Clock|problem and its solutions]] are discussed elsewhere. |
||
| ⚫ | |||
===Boot sound plays=== |
|||
| ⚫ | |||
| ⚫ | |||
The [[Fix_Clock|problem and its solutions]] are discussed elsewhere. |
|||
=== |
===Laptop boots normally, but no boot sound plays=== |
||
| ⚫ | If no boot sound is played, but the machine boots normally and has audio, it is possible that the user has changed the default boot volume to 0. While the boot sound is playing, a user can adjust the volume using the ''volume adjust'' keys. This modified volume setting is saved and used for future boots. Try increasing the volume right after starting the laptop a few times, and see if the boot sound returns. |
||
| ⚫ | |||
| ⚫ | If no boot sound is played, but the machine boots normally and has audio, it is |
||
| ⚫ | |||
| ⚫ | |||
The display is active (including backlight), but no text or graphics appear. |
|||
This is typically a problem with the [[Embedded_controller|Embedded Controller]]'s Flash ROM. It can be caused by removing power to a laptop while it is upgrading the firmware. In the field, the motherboard should be replaced. |
|||
| ⚫ | |||
:This diagnosis may be verified by connecting to the processor serial port (J1) and watching the early [[Open Firmware]] boot process. In some cases, it may be possible to manually reprogram the EC Flash from a USB key. In other cases, the EC Flash will have to be [[XO_Replacing_SPI_flash|replaced]]. |
|||
| ⚫ | |||
''Not quite the correct wording. Anyone remember the exact words ?'' |
''Not quite the correct wording. Anyone remember the exact words ?'' |
||
Early versions (before Q2D14) of the firmware would stop execution if a firmware update was scheduled, but two sources of power (a battery and a power adapter) aren't present ( |
Early versions (before Q2D14) of the firmware would stop execution if a firmware update was scheduled, but two sources of power (a battery and a power adapter) aren't present ( |
||
[http://dev.laptop.org/ticket/5422 Trac ticket #5422]). If this is the problem, provide both sources of power and reboot. The laptop should proceed with a firmware update and boot normally. |
|||
==The display is showing an XO icon== |
==The display is showing an XO icon== |
||
This means that Open Firmware has started the boot process. |
This means that Open Firmware has started the boot process. |
||
| ⚫ | You can see much more information from [[Open Firmware]] by holding the '✓' (check) button (above the power button) after powering on. That will make Open Firmware display more detailed messages about what it is doing during the secure boot process (including early boot messages from the Linux kernel). The messages are in English only. |
||
| ⚫ | |||
| ⚫ | If the laptop powers up, but stops when displaying the XO icon in the middle of the screen, followed by a serial number (e.g. CSN74902B22) and three icons (SD disk, USB disk, Network signal strength), it is looking for its activation lease. This should eventually print "Activation lease not found" at the top of the screen and power-off soon thereafter. |
||
| ⚫ | The solution is to re-activate the laptop. Obtain a copy of the lease (or a new lease) from your country activation manager, place it (named "lease.sig") on the root directory of a USB key and boot the laptop. See [[Activation_and_Developer_Keys#What_to_do_when_You_Receive_Your_Activation_or_Developer_Keys|what to do with your activation keys]]. |
||
===XO icon with a "sad face"=== |
===XO icon with a "sad face"=== |
||
This means that Open Firmware couldn't find a signed operating system on the internal flash memory. (It will also look on USB memory sticks and SD cards.) |
This means that Open Firmware couldn't find a signed operating system on the internal flash memory. (It will also look on USB memory sticks and SD cards.) |
||
| ⚫ | |||
Try [[Secure_Upgrade|upgrading or re-installing the software]]. |
Try [[Secure_Upgrade|upgrading or re-installing the software]]. |
||
===XO icon with a single dot below it=== |
===XO icon with a single dot below it=== |
||
If laptops powers up, but stops when just displaying the XO icon in the middle, with a single dot below it, it means that something is wrong when the Linux |
If laptops powers up, but stops when just displaying the XO icon in the middle, with a single dot below it, it means that something is wrong when the Linux operating system starts operation. |
||
This happens for a number of reasons, such as NAND Flash being full ([http://dev.laptop.org/ticket/5317 Trac ticket #5317]), user "interaction" with the operating system or a hardware problem with the NAND Flash ROM. The suggested solution to try is [[Secure_Upgrade|upgrading or re-installing the software]]. |
|||
( TEXT MISSING HERE! (^_^) ) |
|||
One solution to try is [[Secure_Upgrade|upgrading or re-installing the software]]. |
|||
| ⚫ | |||
| ⚫ | If the laptop powers up, but stops when displaying the XO icon in the middle of the screen, followed by a serial number (e.g. CSN74902B22) and three icons (SD disk, USB disk, Network signal strength), it is looking for its activation lease. This should eventually print "Activation lease not found" at the top of the screen and power-off soon thereafter. |
||
If this has happened to the same laptop more than one time, it may have a Flash ROM block that has gone bad. See [[XO_Flash_Bad_Blocks|fixing bad blocks]]. |
|||
| ⚫ | The solution is to re-activate the laptop. Obtain a copy of the lease (or a new lease) from your country activation manager, place it (named "lease.sig") on the root directory of a USB key and boot the laptop. See [[Activation_and_Developer_Keys#What_to_do_when_You_Receive_Your_Activation_or_Developer_Keys |
||
[[Category: Repair]] |
[[Category: Repair]] |
||
Latest revision as of 02:07, 21 April 2012
This is the portion of the XO Troubleshooting Guide for diagnosing problems turning on an XO laptop.
XO-1 laptops which can't boot because of an "invalid system date" should run the "Fix Clock" procedure to reset the system date, and should perhaps replace the clock battery.
Welcome
For an introduction to the different boot options selectable while powering on, see the Cheat codes.
All of these tests assume that two known good sources of power are available: a charged battery and a power adapter. To debug problems with the power source, and battery charging issues, see Power and Battery problems.
Regularly test that both the power adapter and battery used in these tests are working. This may be done easily using another laptop. A laptop may be unable to power itself from its battery or power adapter (for a number of reasons).
Start by pressing the power button for a second.
Does the Power LED turn on ?
When the power button is pressed once, and the power LED doesn't turn on, verify the following:
Please try resetting the Embedded Controller. Pay attention to the battery LED when power is first reapplied. It should flash orange momentarily (about a quarter of a second). If it does not flash, then the Embedded Controller is not operating properly, and the motherboard should be replaced.
- In these cases, the Embedded Controller Flash chip should be replaced as the first attempt to repair the motherboard. See replacing the embedded controller flash.
If the power LED doesn't turn on, but the laptop proceeds to illuminate the backlight and even boot, the problem may be either the LEDs themselves or the power LED driver (Q39, DDTC144EUA). The LEDs are in series, so if one fails they may both fail to light.
On rare occasions, the power button becomes stuck mechanically. In this case, the laptop does not detect the depression of the power button, and does not turn on. Ensure that the power button is moving freely.
Insert photo of 'stuck' power button vs. 'unstuck' power button
If the battery LED flashed on restoration of power, the power button isn't stuck, and no other signs of life are detected, then the failure mode is unknown. Replace the motherboard to repair.
- In these cases, the Embedded Controller Flash chip is a common source of problems. Using a serial cable, check to see what Open Firmware reports while booting. If it reports an error like "FortDEAD" or "Unimplemented Package Interface" or "Error unpacking code" it should be replaced as the first attempt to repair the motherboard. See replacing the embedded controller flash.
Does the display activate ?
The power LED indicates that the Embedded Controller has enabled the power to the CPU. Open Firmware (OFW) begins executing. The next visible step is turning on the display. The LCD display should be initialized with white, then begin to show text or graphics. The backlight for the screen should be turned on, even if the backlight was previously turned off.
If this does not happen then the boot sequence may not be reaching Open Firmware, or OFW may be crashing early in the boot process. The way to tell is to look at the Microphone activity LED. The default state of the microphone LED is lit. One of the first steps Open Firmware does is to turn off the microphone LED. If the power LED and the microphone LED are both lit then a serious boot error has occurred and the motherboard needs replacing.
On an XO-1.5, watch the microphone LED as you press the power button ... if the microphone LED is lit, then fades away, the motherboard needs replacing.
Did the boot sound play ?
Boot sound does not play
This usually indicates a broken motherboard or a Real Time Clock battery problem in conjunction with early firmware. Some machines in our early production runs (before Jan. 2008) both had a problem with the Real Time Clock battery holder and had a version of Open Firmware (earlier than Q2D07) which locked up when it encountered a reset clock. The problem and its solutions are discussed elsewhere.
Boot sound plays
If the display doesn't initialize, but the boot sound plays, then this is probably a problem with the display. See Display Problems.
Laptop boots normally, but no boot sound plays
If no boot sound is played, but the machine boots normally and has audio, it is possible that the user has changed the default boot volume to 0. While the boot sound is playing, a user can adjust the volume using the volume adjust keys. This modified volume setting is saved and used for future boots. Try increasing the volume right after starting the laptop a few times, and see if the boot sound returns.
If no boot sound is played, and the machine boots normally but has no audio see Audio Problems.
The display remains blank
The display is active (including backlight), but no text or graphics appear.
This is typically a problem with the Embedded Controller's Flash ROM. It can be caused by removing power to a laptop while it is upgrading the firmware. In the field, the motherboard should be replaced.
- This diagnosis may be verified by connecting to the processor serial port (J1) and watching the early Open Firmware boot process. In some cases, it may be possible to manually reprogram the EC Flash from a USB key. In other cases, the EC Flash will have to be replaced.
The display says "Connect to power to proceed"
Not quite the correct wording. Anyone remember the exact words ?
Early versions (before Q2D14) of the firmware would stop execution if a firmware update was scheduled, but two sources of power (a battery and a power adapter) aren't present ( Trac ticket #5422). If this is the problem, provide both sources of power and reboot. The laptop should proceed with a firmware update and boot normally.
The display is showing an XO icon
This means that Open Firmware has started the boot process.
You can see much more information from Open Firmware by holding the '✓' (check) button (above the power button) after powering on. That will make Open Firmware display more detailed messages about what it is doing during the secure boot process (including early boot messages from the Linux kernel). The messages are in English only.
XO icon with a serial number and three icons below it
If the laptop powers up, but stops when displaying the XO icon in the middle of the screen, followed by a serial number (e.g. CSN74902B22) and three icons (SD disk, USB disk, Network signal strength), it is looking for its activation lease. This should eventually print "Activation lease not found" at the top of the screen and power-off soon thereafter.
The solution is to re-activate the laptop. Obtain a copy of the lease (or a new lease) from your country activation manager, place it (named "lease.sig") on the root directory of a USB key and boot the laptop. See what to do with your activation keys.
XO icon with a "sad face"
This means that Open Firmware couldn't find a signed operating system on the internal flash memory. (It will also look on USB memory sticks and SD cards.)
Try upgrading or re-installing the software.
XO icon with a single dot below it
If laptops powers up, but stops when just displaying the XO icon in the middle, with a single dot below it, it means that something is wrong when the Linux operating system starts operation.
This happens for a number of reasons, such as NAND Flash being full (Trac ticket #5317), user "interaction" with the operating system or a hardware problem with the NAND Flash ROM. The suggested solution to try is upgrading or re-installing the software.
If this has happened to the same laptop more than one time, it may have a Flash ROM block that has gone bad. See fixing bad blocks.