Difference between revisions of "MacBuild PPC Checklist"
m (→Build: Combined Open Firmware date set and NVRAM reset in the same box) |
m (moved batterytest in front of printme so that batterylife can be entered in printme notes section (and thus the database).) |
||
Line 196: | Line 196: | ||
| Verify printme notes || | | Verify printme notes || | ||
Locate the '''build_printme.pdf'' file on the desktop. Open it up and make sure that the notes written on the Build printme sheet accurately reflect the components and special issues with the system. If they are not accurate, please make any necessary changes when you create the printme printout for the QC process. | Locate the '''build_printme.pdf'' file on the desktop. Open it up and make sure that the notes written on the Build printme sheet accurately reflect the components and special issues with the system. If they are not accurate, please make any necessary changes when you create the printme printout for the QC process. | ||
+ | || | ||
+ | |- | ||
+ | | Test battery life || | ||
+ | To start the battery test: | ||
+ | # Make sure battery is fully charged | ||
+ | # Open a web browser and go to '''''http://llama.freegeek.org/~serge/batterytest.sh''''' | ||
+ | # Save file to disk | ||
+ | # Insert an audio CD into optical drive | ||
+ | # Launch audio player, play disc, and set on repeat | ||
+ | # In a terminal, navigate to the directory you saved batterytest.sh to and run: | ||
+ | #* '''''sh batterytest.sh''''' | ||
+ | # Disconnect power supply | ||
+ | # Leave the system running until it powers off | ||
+ | To check the results of the battery test | ||
+ | # In a terminal, navigate to the directory you saved batterytest.sh to and run: | ||
+ | #* '''''sh batterytest.sh''''' | ||
+ | # Record the results in the notes section of the "printme" report | ||
|| | || | ||
|- | |- | ||
Line 218: | Line 235: | ||
#** Any special issues the machine has | #** Any special issues the machine has | ||
#** Whether computer is covered or uncovered | #** Whether computer is covered or uncovered | ||
+ | #** Battery life | ||
# Upload the '''printme.xml''' file, and print out the report | # Upload the '''printme.xml''' file, and print out the report | ||
# Remember to add the wireless card type | # Remember to add the wireless card type | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|| | || | ||
|- | |- |
Revision as of 14:20, 11 February 2010
Build
Steps | Notes/Detailed Instructions | Done |
Install/verify RAM |
Make sure the system has at least 512 MB of RAM. Keep in mind that some systems may have some RAM directly on the logic board. |
|
Install wireless card (if not present already) |
Ask the instructor |
|
Attach network cable and power cord | ||
Clear the PRAM |
While starting up, hold the Option+Apple+p+r keys. Continue holding the keys until the system chimes three times. Release the keys after the third chime is heard. |
|
Set the system clock and NVRAM in Open Firmware |
While starting up, hold the Option+Apple+o+f keys. Release the keys when the Open Firmware prompt comes up. Run the following command: decimal dev rtc [sec min hour day month year] set-time All values aside from the year should be two-digit numbers in 24-hour format. The year should be a four-digit number. Additionally, the clock needs to be set to UTC, so remember to add 7 hours to the current time if on regular time or 8 hours during Daylight Saving Time. For example, to set the clock to 1:58 PM on September 18th, 2009, the command would be decimal dev rtc 00 58 20 18 09 2009 set-time To reset the NVRAM type the following commands in the specified order: reset-nvram set-defaults reset-all The system will reboot after the reset-all command is entered. |
|
Install Ubuntu |
Please note that any values not explicitly defined here (HTTP proxies and such) should be left blank.
|
|
Start up Ubuntu |
|
|
Verify hardware in the system |
To verify the hardware in a system, open up a terminal and run: sudo lshw|less This runs a command called lshw (which stands for "list hardware") and sends the output to another command called less, which is a simple reader that allows you to scroll through lshw's output. The items to pay attention to are:
|
|
Set up the environment and install extra apps |
sudo apt-get install vlc
sudo apt-get install b43-fwcutter
|
|
Test USB ports |
USB:
If any port doesn't work, the machine should be recycled |
|
Test CD/DVD data and sound |
Note: Brasero has problems with versions of Ubuntu before Karmic (9.10). For Hardy (8.04LTS) and Jaunty (9.04) you may want to install and use k3b instead: sudo apt-get install k3b |
|
Check if wireless works |
Use Network Manager to see if you can connect to Free Geek's wireless network. If you can, the wireless card works. Remember to write the type of wireless card (e.g. AirPort, AirPort Extreme) on the printed report at the end of the build. |
|
Check for software updates |
There are a few ways to do this:
sudo apt-get update sudo apt-get upgrade Install all updates if any are found |
|
Generate "printme" report for system |
|
|
Power system down and place on the QC shelf in TARDIS |
QC (in progress)
Steps | Notes/Detailed Instructions | Done |
Attach network cable and power cord | ||
Verify that the splash screen works or that the system generates startup messages |
When powering on the system, you should see the Ubuntu splash screen on most before the desktop finishes loading. It's fine if the colors are irregular, as long as something is displayed. If the splash screen doesn't work, it should at least display startup messages. If no splash screen or startup messages are displayed, go through the steps in the Special Configuration to resolve the problem. |
|
Verify hardware in the system |
To verify the hardware in a system, open up a terminal and run: sudo lshw|less This runs a command called lshw (which stands for "list hardware") and sends the output to another command called less, which is a simple reader that allows you to scroll through lshw's output. The items to pay attention to are:
|
|
Test CD/DVD data and sound |
Note: Brasero has problems with versions of Ubuntu before Karmic (9.10). For Hardy (8.04LTS) and Jaunty (9.04) you may want to install and use k3b instead: sudo apt-get install k3b |
|
Check if wireless works (if the system has a wireless card) |
Use Network Manager to see if you can connect to Free Geek's wireless network. If you can, the wireless card works. |
|
Check for software updates |
There are a few ways to do this:
sudo apt-get update sudo apt-get upgrade Install all updates if any are found |
|
Verify printme notes |
Locate the 'build_printme.pdf file on the desktop. Open it up and make sure that the notes written on the Build printme sheet accurately reflect the components and special issues with the system. If they are not accurate, please make any necessary changes when you create the printme printout for the QC process. |
|
Test battery life |
To start the battery test:
To check the results of the battery test
|
|
Generate "printme" report for system |
|
|
Clean outside cover |
Clean case monitor face, connector panel, keyboard, and trackpad as well |
|
Attach "printme" report to system | ||
Bundle system with power supply | ||
Give the laptop to an instructor |