MacBuild Intel Checklist
OS X Triage
Getting Started
Attach keyboard/mouse, monitor, network cable, and power cord (as necessary)
Install components for triage
- If working on a standard desktop system:
- Install a tested/wiped HDD
- Install tested RAM in each available memory slot
- Install a tested battery
- If working on a system with a built-in display:
- Install tested RAM in each available memory slot
- NOTE: certain models (iMac G4s in particular) use SODIMMs (laptop memory) instead of/in addition to standard desktop memory. Go ahead and use untested memory for the SODIMM slot, as we'll test that memory later in the process
- Install a tested battery if it is easily accessible (if the system uses a 3.6v battery, it can be done while installing RAM)
- Install an AirPort/AirPort Extreme wireless card
- Install tested RAM in each available memory slot
- If working on an oddball system (e.g. Mac mini):
- Ask an instructor for further direction
You may need to install more parts than specifications require in order to test the system (e.g. you may need to install more RAM in a system than we'd actually need for building because we want to test all the RAM slots at once). If that's the case, remember to remove any excess components after the triage is complete.
Hardware Testing
Boot into OS X from the network
- Hold the n key as the system starts up
- Release the n key once a globe starts flashing on the screen
- Press the m key at the bootloader to boot into OS X
- Wait a few minutes while the OS loads
- Depending on the system's specifications, it may take a few minutes to boot into the OS
- If a system shows a black rectangle in the middle of the screen, complains about a kernel panic, asks for a restart, or does something other than load the OS, notify an instructor and set the system aside for troubleshooting
Log into OS X
- The username is oem, and the password is freegeek.
Confirm hardware
- Click on the apple icon in the upper-left corner of the screen
- Select the About This Mac option from the menu
- Click the More Info button to launch the System Profiler
- Check the ATA and Memory sections of System Profiler to confirm that it matches what you've added to the system so far
- If it fails to see the HDD or reports the amount of memory incorrectly, ask an instructor for assistance
Test CD/DVD writing
- Open Disk Utility
Check if WiFi works
- Click on the AirPort icon near the upper-right corner of the screen
- Check to see if the Freegeek wireless network shows up on the list
- Do NOT select a wireless network out of the list
Label the system
- Check off what worked and what didn't on a label, and attach the label to the system
Shut down and remove excess components
- Ask an instructor to confirm what, if anything, should be removed from the system
Build
Getting Started
Attach keyboard/mouse, monitor, network cable, and power cord (as necessary)
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 and shift quickly to the Option+Apple+o+f keys.
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. In order to set the system clock in open firmware, you need to run a set of commands Open Firmware understands. The command you will be running uses the following syntax:
decimal dev rtc [seconds minutes 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.
Installation
Start the network installation and run badblocks if necessary
To access this install, hold down the n key (for network) while the computer starts. As soon as the network icon starts blinking on the screen you may release the n key.
- At the first boot prompt enter an l (for linux). At the second boot prompt:
- If the system has a G4 processor, press return to default to installing the PPC version of Ubuntu 9.04.
- If the system has a G5 processor, you must install the 64-bit version of Ubuntu 9.04. To do so, type jaunty64 at the second boot prompt and press return.
- The installation will stop at the keyboard selection. Accept the defaults (No or USA) for the next 3 screens and the installation will continue automatically.
- If prompted to choose between wired and wireless network choose eth0 (wired)
- When prompted for a hostname, delete the current entry and enter macbox in its place
- When prompted for HD partitioning we need to make a decision.
- If this is a computer that has had a wiped and tested hard drive installed, or if it successfully completed badblocks, we can accept the default and let the installation proceed.
- If this is a computer that came straight from Mac Eval or TARDIS, it needs to have the hard drive tested with badblocks. To do this we choose "Go Back" and then select "Execute a shell" from the menu. At the prompt, run the following:
badblocks -wvvf -c1024 -e1 /dev/hda
- If that command fails, try
badblocks -wvvf -c1024 -e1 /dev/sda
- It will take anywhere from 3 to 8 hours to run badblocks.
- If there are any bad blocks we must replace the hard drive.
- If there are no bad blocks, you can proceed with the installation. To do this type "exit" to leave the shell, select "Partition drives" from the list, choose "Guided Partitioning" when the partitioner starts and then accept the defaults and the rest of the installation will proceed automatically.
The remainder of the installation will take approximately 30 minutes and the computer will automatically reboot following the installation.
Hardware/Software Testing
Start up Ubuntu
- Log into the system using the username oem and password freegeek.
- If the system has problems starting up, refer to the Special Configurations list
Set up the environment and verify hardware in the system
- Add the Terminal to the panel so it can be launched quickly. You can do this by dragging and dropping the terminal icon to the top panel.
- Check to see if the splash screen has been enabled. To do this, run the following in a terminal:
cat /etc/usplash.conf
- If the splash screen has been configured to work already, you should see an entry that looks like this (the numbers may be different, but the syntax will be the same):
xres=1024 yres=768
- If no entry is found, one must be added. To do so, do the following:
- If you are working on a system with a built-in display, determine the display's native resolution.
- If you can't figure out your display's native resolution, just stick to the numbers used below
- Run the following in a terminal to open up the config file in an editor:
sudo nano /etc/usplash.conf
- Add the appropriate resolution to the file in the following syntax:
xres=1024 yres=768
- Save the file and exit the editor
- Run the following in a terminal:
sudo update-initramfs -u
- If you are working on a system with a built-in display, determine the display's native resolution.
- Verify the hardware in a system
- Run the following in a terminal:
sudo lshw
- This runs a command called lshw (which stands for "list hardware") The items to pay attention to are:
- Read through the output of the command and find:
- Amount of system memory
- You should be able to find this under the memory heading in lshw. If you installed the memory yourself, this readout should display the same amount of memory as what you installed.
- Systems we build should have, at minimum, 512 MB of RAM. Ask your instructor to confirm that your system has the correct amount of memory installed.
- Type of optical drive
- This can be found under the cdrom heading in lshw.
- Presence of wireless card
- This should be under one of the network headings. You should look for an entry that mentions something about "Wireless interface" or "Broadcom". If that exists, the system has a wireless card.
- Amount of system memory
- Run the following in a terminal:
- This is a good time to shut down the system and install additional memory or a wireless card if they are missing. Ubuntu will not run well with 256MB of memory and will sometimes generate errors that don't occur when 512MB or more memory is installed.
- If you have a dual processor machine you may notice that the second processor (cpu1) has "DISABLED" listed after it in lshw. In order to enable the second processor run the following command:
sudo apt-get install linux-powerpc-smp
Test CD/DVD data and sound
- Insert, play, and eject a music CD
- If machine has a CD-RW or DVD-RW, use K3b to erase a CD-RW disk, and create/burn a new data project.
- If machine has a DVD drive:
- insert a data DVD, inspect directory contents
Check if WiFi 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.
Generate "printme" report for system
- Set up the printer by selecting System - Administration - Printing. When the printers window opens, select server and then settings and click on the top box (access printers shared by other computers). Close the printing window.
- In a terminal, type printme
- Enter your volunteer ID in the Volunteer ID field
- Job should be changed to Builder
- System ID should be left blank
- Type should be changed to Apple
- Keeper label type should be set to No Sticker
- Choose whether the computer is covered or not
- Notes should include the following information:
- Version of Ubuntu installed
- Any components that show up in lshw (modems, certain wireless cards) that aren't supported by Ubuntu should be listed
- Any special issues the machine has
- When asked where to print the report, select the printer Double.