Difference between revisions of "Build Checklists"
Jump to navigation
Jump to search
(→HARDWARE AND SOFTWARE TESTING: changed process for running printme to print from desktop) |
|||
| (33 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
=QC Checklist= | =QC Checklist= | ||
| − | + | {{:QC_checklist}} | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | { | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<hr class=PAGE-BREAK> | <hr class=PAGE-BREAK> | ||
| − | = | + | =Assembly Checklist= |
| − | + | {{:Assembly_checklist}} | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | { | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 12:27, 22 May 2012
QC Checklist
 This page has been migrated to a document on Free Geek's Google Drive. Information remaining behind may no longer be relevant. MIGRATOR: When you have tagged this page as migrated, (Link to new page immediately below.) |
There is a version of this checklist in Spanish for use in Spanish Build; that version is located here.
Welcome to the Build Workshop! Quality checking a few systems that others have built will be your first step, then you'll be ready to move on to assembling and checking software on systems.
Work through every step as well as you can, and then ask a neighbor or your Build instructor if you still have questions. Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.
Use your resources! There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under Build tips or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide).
BEFORE YOU POWER ON
Check what needs to be quality checked
- Grab a system from the QC shelves in the build room, and carry it to an open Build station.
Do you hear a rattling noise, caused by a screw or other loose component, upon moving the system?
- If so, find the culprit and secure/remove it.
Is the case properly put together and secure?
- If not, fix it!
Are all slots and bays covered?
- If not, cover 'em! Check to make sure they're screwed in tightly by pushing on each one with your finger - if a slot cover falls out it can short out the motherboard.
Do you see more than one video, sound, or network ports?
- Later, when you're testing audio, headphone jacks and standard sound ports should be tested.
- Orange/Black/Gray sound ports are surround sound and do not need to be tested.
- Any damaged ports will need to be reported to the build instructor or staff member on duty.
Are there branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?
- If there are, take them off.
- Make sure to remove "City of Portland Help Desk" stickers from the case.
DO NOT remove Microsoft Windows Certificates of Authenticity, FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.
Is the system exterior clean?
- If not, use cleaner and rag to clean. The vacuum cleaner will help remove dust clogged in case fans. Hand sanitizer, Goo Gone and/or isopropyl (rubbing) alcohol can help loosen any stickers; ask your instructor where to find scraping tools to remove them.
Open up the system and check inside for:
- Blown capacitors (If found, the system must be rejected!)
- What type of DDR RAM your system has installed - write this down
- The RAM speed (will be the second number on the sticker) - write this down
- Any dust accumulation - please vacuum or brush it out!
Attach monitor, keyboard, mouse, network, sound and power cords
BOOT AND ENTER BIOS
Get into BIOS (Setup)
- Turn on the computer. If you see a flash screen before boot-up, it will give the keystroke to enter BIOS, and the keystroke for a Boot Menu, if applicable. Delete, Escape, F1, F2, F9, F10, F12 and Enter are typical.
- Get into BIOS, and write down both the BIOS and Boot Menu keystrokes; this info will come in handy later.
- If you see "Ubuntu" on your screen, you have gone too far; reboot from the power button icon on the bottom-right corner of the screen, and try again. All BIOS are different. Feel free to explore how the BIOS you're using is set up.
Check boot order
- It should be: 1st- CD-ROM; 2nd-Hard Drive. If possible, disable other boot device options, such as floppy (sometimes called Diskette), network, or USB. Depending on the BIOS model, you may need to enable active drive ports and disable inactive ones, in addition to arranging them in the boot sequence.
If possible, edit the following setting:
- Enable Quick Boot (may be called "Fast Boot" in some BIOS)
Save and exit BIOS
- The system should boot to the Mint operating system.
HARDWARE AND SOFTWARE TESTING
Login to the system
- username will be oem
password = freegeek
What Specification Category does the system fall under?
- Compare the CPU speed listed on the system's Green Light sticker with the FREE GEEK Specification Sheet, or "Spec Sheet," on the wall to determine the category of specifications, or "specs," to which the system should be built. If you aren't sure what type of box you are working with, please check with your instructor to see how to proceed.
Is the system standard?
- Check the Spec Sheet on the wall to see what else should be installed for your spec category, then compare your system's spec category to the Build Printme document saved to the Desktop. Does the box have any parts that are extra, or missing, or built to incorrect specifications? Take out and replace parts as necessary to ensure that all specs are correct, paying special attention to properly seating/securing parts to ensure that they won't come loose. Ask an instructor if you are unsure how to do this.
Update the software
- Open a Terminal by pressing "Ctrl+Alt+t". Type the following command "sudo apt-get update && sudo apt-get upgrade -y" and then hit enter, when prompted, enter the password "freegeek." It may take some time to download and install packages, so feel free to continue on with other steps while this runs in the background.
Find the terminal icon on the launcher panel at the bottom of the screen
- Navigate to the bottom of the screen with your mouse. Click the terminal icon >_or use the shortcut "Ctrl+Alt+t" to open a terminal window.
Stress test the system for a few minutes
- navigate to your terminal and run "stress-test". Wait a few minutes while it runs, and look for error messages. If you want to know more about what it's doing, open up another terminal and run "man stress". This may take some time; feel free to continue on to the next step while you wait.
Run "basiccheck"
- Click on the terminal icon to open it. Type "basiccheck", then press enter to begin the program. There are basiccheck checklists hanging on the supply shelves which will help with verifying whether each test passes or not. Feel free to ask your peers and the instructor what parts of basiccheck mean so that you understand what each test is checking. When you're finished, close the terminal.
Test USB
- Plug in a USB mouse, see that the cursor moves and can interact with things.
- Repeat with all USB ports, including ports on the front of the system, if any.
- If any ports don't work, they may need to be enabled in BIOS; ask your instructor how to proceed.
Check date and time
- Displayed in the right corner of your top panel. If incorrect:
- Make sure network cable is plugged in.
- Navigate to Menu>>>Settings>>>Settings Manager
- Open the Calender, set Time Zone to America/Los Angeles
Play an audio CD
- Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each optical drive. Also repeat for any additional sound ports. If any sound ports (typically colored green, sometimes blue) don't play audio, cover them up with port covers or electrical tape. If you have functional onboard sound, and a sound card, the card will need to be removed and replaced with a slot cover.
- If you have surround sound ports (usually orange and gray) ignore them; we do not have the means to test this function.
Read data CD
- If your file browser (listed under Places in the top panel) sees files on the drive, it can read data files. Repeat for each optical drive.
If you have a DVD Drive, Read DVD
- Insert a video DVD (movie, TV show, etc.). A media player should open automatically and the DVD should start to play. If you are prompted to search for suitable plugins or codecs close the message and the media player, then check with an instructor. Repeat for each DVD-ROM drive.
If you have an Optical Drive with CD-RW function, as of 12/20/13 we are no longer testing this function
If you have an Optical Drive with DVD-RW function,as of 12/20/13 we are no longer testing this function
Remove all CDs and DVDs from the drive(s)
Reboot the system
- Open a terminal and type sudo reboot. Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.")
- If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.
Run "printme" from terminal
- From a terminal, type "printme," this will generate a questionnaire in Command Line.
- Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable.
- When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification. Press enter to create a web document.
Copy system ID (IMPORTANT!)
- Copy the system ID from the printme onto a blank sticker and put it on back of computer, ideally in a location that isn't covering any fans, other ventilation, or removable case parts such as slot covers.
Add Free Geek Sticker
- Affix on the front of the system, in a sensible location! (Usually adjacent to or above/below the Processor tag)
Check in with Build Instructor
- The Build Instructor will check the printme and edit it to sign it off.
- Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step.
Save Printme to the Desktop
- After your Build Instructor has inspected the system, click "Print" in the browser that opens. Choose "Print to file." Save the file to the Desktop and name it "QC Printme", then click "Print" to save. Click on the QC Printme icon on the Desktop to open it up.
Enable network printers:
- Go to Menu >> System >> Printing
- Select Server >> Settings and check the box marked Show Printers Shared by Other Systems and click OK.
- Wait for a few moments and click the refresh icon. A selection of printers should appear.
Print a hard copy of Printme
- Close the "Printing - localhost" window that opens and select the "build-printer" printer from the Print menu once it appears. Click Print and retrieve the sheet from the printer in the back (SW) corner of the room.
- Have your Build Instructor sign off on the printed sheet. Then fold it in half (lengthwise) and tape it to the top of the system (the side of the page with the instructor's initials facing up.)
Shut down and shelve the system
- Open a terminal and type "sudo halt -p" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and ask a build instructor where to put the system once shutdown is complete.
Clean up work area if it is your last QC of the day
- Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up.
Assembly Checklist
This page has been migrated to a document on Free Geek's Google Drive. Information remaining behind may no longer be relevant. MIGRATOR: When you have tagged this page as migrated, (Link to new page immediately below.) |
There is a version of this checklist in Spanish for use in Spanish Build; that version is located here.
Work through every step as well as you can, and then ask a neighbor or your build instructor if you still have questions. Try and learn the reason for each of the steps: this knowledge will come in handy later when, inevitably, things aren't going as smoothly.
Use your resources! There are lots available to you - your neighbor, the Build assistants and instructors and, of course, the internet. Searching the web for answers to the challenge you are facing is one of the best ways to learn. You can also access tips and troubleshooting ideas on our wiki (http://wiki.freegeek.org) under Build tips or in our Troubleshooting Guide (http://wiki.freegeek.org/index.php/Build_Troubleshooting_Guide).
Supplies like cards, rails, hard drives, cleaning supplies, etc. can be found on the metal racks in the center of the build workshop. Here you will also find a box containing an assortment of common DDR memory.
BEFORE YOU POWER ON
Check what needs to be built on the white board
- Head to the To Be Built Rack and scope out a system you would like to build.
- Be sure to pay attention to the Build label. It will give you a lot of important information, like the type of video, if it did not POST, if the processor is Dual Core, etc. Make sure that the box you are about to Build is appropriate for its spec.
- If everything looks good, Grab the system from the To Be Built Rack, take it back to your build station, and figure out how to pop it open.
Check capacitors
- Visually inspect motherboard capacitors for bulges/leaks. If you find one, ask your instructor for a "Rejected" sticker.
Secure the case
- Cover any open bays or slots. Replace any other missing case parts. (You can substitute a CD-ROM drive if no compatible bay cover is available. Please make sure that it works after installation.) Some cases require specific (proprietary) parts. If we don't have extras on hand, we unfortunately have to recycle them...
- Ensure that all components are securely fastened.
- Check for/remove any loose screws or unnecessary cables. If you're unsure of how to do this, ask an instructor.
Are there Asset tags? (identifying the last owner)? Or branded hardware tags on the faceplate (identifying original components such as RAM, HDD, Optical Drive etc)?
- If there are, remove them.
DO NOT remove Microsoft Windows Branding (Certificates of Authenticity) FG-PDX, "uncovered electronic device" Processor/graphics tags or Green Light stickers.
Clean and vacuum out box
- There is a vacuum available on the Build supply shelf by the cleaning supplies. The most effective way to clean out a box is to use a paint brush to kick up the dust while vacuuming.
Test battery
- Grab a voltmeter and set it to DCV=20. Place one wand on the battery itself and one wand on a metal part of the case. The battery passes if its voltage shows as 3.0 or greater.
Install RAM
- For DDR2, try speed 533 (PC2-4200) first. If that doesn't work, try higher speeds. Sometimes the BIOS will tell you the needed speed.
- If your system's memory slots will not accept DDR2 memory, they will require another type. DDR3 is acceptable - ask your instructor for DDR3 RAM. DDR1 systems should be rejected and sent back to Prebuild as yellow-light systems.
- NOTE: Usually RAM should be paired in dual channels for higher performance (i.e., 2 sticks of RAM used in specific slots, often color-coded). Make sure you try all combinations of slots if you are having trouble getting the system to recognize the RAM, and consult an Instructor if you're still having trouble.
- Write down what type and speed of RAM you installed; this info will come in handy later.
Install video card if needed
- You do not need to install a video card if there is functional onboard video.
- Ask an instructor if you need a PCI-e card; AGP cards are available in the Build room.
Attach monitor, keyboard, mouse, network, sound and power cords
Initial power on
- See if expected memory value is displayed during POST or in BIOS.
Power down
Remove floppy drive if possible
- Remove the floppy drive if you can find a matching face plate to cover it. If there are no covers available, you can leave the drive in, but make sure it is unplugged from the motherboard and power supply. Make sure the floppy drive (sometimes called Diskette) is disabled in BIOS and removed from the boot sequence if possible.
Check for onboard NIC ((Network Interface Card, or ethernet.)
- If none can be found, install a network card.
Install hard drive
- Get the appropriately sized (according to spec sheet) hard drive from the supply shelf, or from an instructor. Also check to see if you need an IDE or SATA hard drive and make sure you have the necessary cables and power connections.
- Install the hard drive and attach it to the power supply and motherboard. (If the drive has IDE connections, make sure the jumper is set to the Master position. Ask an instructor for more info.)
- You will need to ask an instructor for any high end hard drives.
Install sound card if needed
- If there's onboard sound, there's no need to install a sound card.
Install CD/CDRW/DVD/DVD-RW Drive(s)
- If there are already optical drives installed in your system, take a look at their face-plates to determine their capabilities. If the drives are within spec for the box you're building and have IDE connections, confirm they're properly jumpered as Master/Slave, or just Master if there's only one drive.
- If the the drives are outside of spec, pull them out and sort them into the appropriate boxes on the Build shelves. Replace with appropriate drives as needed.
Cover open slots and bays
- Make sure you have coverings for all spaces that will not be filled with a card or drive. Look at similar cases for examples of what case pieces may look like. Be sure that these are screwed in tight and test them by pushing on each with your finger. If a slot cover falls out while a computer is on it can short out the motherboard.
BOOT AND ENTER BIOS
Enter BIOS setup
- Turn on the computer. The keystroke to enter BIOS should be displayed on the flash screen, before bootup, as well as the Boot Menu key, if applicable. If no flash screen appears, you have to guess the BIOS keystroke. Delete, Escape, Enter, F1, F2, F9, F10, and F12 are typical.
- Get into BIOS, and write down both the BIOS and Boot Menu keystrokes; this info will come in handy later.
Check date and time
- Check date and time in BIOS and change to the correct time if needed.
Restore BIOS defaults
- You might need to search around to find the BIOS values that need checking. While you search, enjoy the pleasure of learning about BIOS configuration!
Detect hard drive
- Search BIOS to see if it is recognizing the hard drive.
Set boot order
- It should be: 1st-CD-ROM; 2nd-Hard drive. If possible, disable all other boot devices such as floppy drive or network boot from the boot sequence.
Where possible, edit any/all of the following settings:
- Enable USB ports
- Enable Hyper-threading
- Disable Quick Boot
- Disable Logo Display (Sometimes called Silent or Quiet Boot)
- Disable Plug & Play OS
- SATA Operation: set to RAID Autodetect/AHCI
Save and exit BIOS
- The system should reboot to the Ubuntu operating system.
HARDWARE AND SOFTWARE TESTING
Login to the system
- username will be Default User
- password = freegeek
Run "basiccheck"
- From a terminal, type "basiccheck" Read through each of the tests and verify that they pass. When the last test is finished, close the terminal.
- Refer to the basiccheck checklists hanging on the supply shelves to help determine whether each test passes or not.
Test USB ports
- Plug in a USB mouse, move the mouse and make sure the cursor moves on-screen. Repeat with all USB ports, including front ports, if any.
Run the Restricted Extras & DVD Codecs Installer
- Support for DVD playback, Adobe Flash, and several other features are not included in Xubuntu by default, but can be added with the following steps.
- Plug in an ethernet cable from the workbench if you are not currently connected.
- To Install Restricted Extras & DVD Codecs.
- Navigate to Menu >> Other >> Install Restricted Extras & DVD Codecs
- Answer Yes when prompted to confirm the installation and provide the default password when prompted.
- Wait for the installation to complete and close the completion notification when it appears; if the notification informs you that the installation has failed then proceed to the alternate installation steps below.
Alternate Installation Steps
- If for some reason the automated installer fails it can generally be corrected with the following steps.
- Open a terminal window
- Type sudo apt-get install ubuntu-restricted-extras and press Enter. Provide password if prompted.
Play an audio CD
- Do you hear what you expect? Is it loud enough to be heard easily? Repeat for each CD-ROM drive. Repeat for additional sound ports.
- Note if any standard sound ports do not work. These will need to be covered with electrical tape. If all onboard sound does not work, install a sound card.
Read data CD
- If your file browser sees files on the drive, the CD-ROM can read files. Repeat for each CD-ROM drive.
If you have a DVD Drive, Read DVD
- Insert a video DVD (movie, TV show, etc.). A media player should open automatically and the DVD should start to play. If you are prompted to search for suitable plugins or codecs close the message and the media player, then try the Alternate Installation Steps for the Restricted Extras & DVD Codecs Installer listed above. If you still see the message then check with an instructor. Repeat for each DVD-ROM drive.
- If you are getting multi-color lines when testing video playback, replace the hard drive.
If you have an Optical Drive with CD-RW function, as of 12/20/13 we are no longer testing the writing & blanking
If you have an Optical Drive with DVD-RW function, as of 12/20/13 we are no longer testing the writing function
Remove all CDs and DVDs from the drive(s)
Reboot the system
- Open a terminal and type sudo reboot. Wait while it reboots, and ensure that the system powers on and offers a login screen without user intervention (e.g. requiring you to "press F1 to boot.")
- If it doesn't boot smoothly, double-check your boot priority options in BIOS and try again.
Run "printme" from terminal
- From a terminal, type "printme," this will generate a questionnaire in Command Line.
- Refer to your written notes for the RAM type and speed, the BIOS key and Boot Menu key, if applicable.
- When it asks what is notable about this system, refer to the white board for what should be included, and ask your instructor for any needed clarification. Press enter to create a web document.
Check in with Build Instructor
- The Build Instructor will check the printme and edit it to sign it off.
- Your instructor may ask you to replace certain components, which will require re-running the "printme" form. Some changes may also need to be made in the web browser. If your instructor gives the "thumbs-up," proceed to the next step.
Save Printme to the desktop
- After your Build Instructor has inspected the system, click "Print" from the printme on the web document. "Choose "Print to File" and select "Desktop" as the folder in which to save it. Name the file "Build Printme" and click print.
Shut down system and place on QC shelf
- Open a terminal and type "sudo halt -p" then press enter. When the system has shut down, unplug all cables, double-check that the case is secured properly, and place it on the QC shelf in the Build room.
Clean up work area if it is your last Assembly of the day
- Please put all tools away, throw out any garbage or sticker remains, put screws in the appropriate bins, wrap cords around your keyboard and mouse, turn off your speakers and monitor, and generally straighten up.
Thank You For Volunteering!
- If you are interested in further learning opportunities after finishing the Build program, ask your instructor about Post-Build options!
- We want to know what you think! Go to http://freegeek.limequery.com/48992/lang-en to fill out the Build Program Exit Survey.