Difference between revisions of "MacBuild Desktop Build"
Jump to navigation
Jump to search
AshleySueMas (talk | contribs) |
|||
| (71 intermediate revisions by 5 users not shown) | |||
| Line 2: | Line 2: | ||
==What we build== | ==What we build== | ||
| − | We | + | |
| − | + | We focus mainly on Intel based Systems. Unless requested, we do not build any system with a PowerPC or lower. | |
| − | + | ||
| − | + | ==Minimum Specs== | |
| − | == | + | {{MacBuild_Minimum_Desktop_Specs}} |
| − | |||
| − | |||
| − | {{ | ||
==What we don't build== | ==What we don't build== | ||
| − | We don't build anything | + | We don't build anything not in the PPC specs listed above. This means we process standard desktop systems within the PPC specs above that have a single G4 processor below 1.0 GHz with our as-is process and either sell them in the store as is or grant them out to organizations in need. |
| + | |||
| + | So what happens with systems not listed above? | ||
| + | * '''eMacs''' - 1.25 GHz and 1.42 GHz models are tested through our as-is process and sold in the store | ||
| + | * '''PowerMac G3 / G4 Graphites''' - recycled | ||
| + | * '''Old World / 68k / 9" CRT / beige Macs''' - we have an Old Mac Keeper List in MacBuild Eval and System Eval that we use for determining what we keep and what we don't. Old Mac Keepers are kept on the Old Mac shelf in the warehouse for future processing. Everything else is recycled. If a model that should be kept is presently being recycled, let a MacBuild instructor know. | ||
| + | |||
| + | ==Important note about netbooting OS X== | ||
| + | We presently have a network-bootable setup of OS X available for use on the network. It's a very handy tool, but it does have its drawbacks. Some machines will be very picky about how they netboot and as such may refuse to do so. In that scenario, you should ask the instructor for an external hard drive to boot off of. | ||
| + | |||
| + | ==As-Is Procedure== | ||
| + | Before running a system through the as-is process, look at [http://wiki.freegeek.org/index.php?title=MacBuild_Desktop_Build&action=submit#What_we_don.27t_build what we don't build] to make sure it should be tested through the as-is process. If you are uncertain, please ask an instructor. | ||
| − | |||
# Install a tested battery | # Install a tested battery | ||
| − | # | + | # Fill all RAM slots with tested RAM |
# Install optical drive, if necessary | # Install optical drive, if necessary | ||
| − | # | + | # For the HDD: |
| + | #* If the system does NOT have a built-in display, connect a wiped HDD to the primary IDE channel | ||
| + | #** '''REMEMBER:''' we are only installing this HDD for our testing purposes. It should be removed before the system is moved to the store | ||
| + | #* If the system has a built-in display, run it through our [[Hard_drive_wiping_checklist | HDD wiping procedure]] before continuing the as-is process | ||
| + | #** If the HDD wiping procedure tells us the system has a bad HDD, let an instructor know so we can either replace the HDD during a less-busy day or use it as a training tool for newer volunteers | ||
# Connect a mouse, keyboard, and monitor to system | # Connect a mouse, keyboard, and monitor to system | ||
| − | # Boot | + | # Boot the system into OS X: |
| + | #* Connect the OS X 10.4 FireWire HDD to the system | ||
| + | #* Make sure the FireWire HDD is turned on (there's a power switch on the back of the drive) | ||
| + | #* Hold the ''Option'' key on the keyboard while system starts up to enter the Startup Manager | ||
| + | #* Select the FireWire drive from the Startup Manager to boot into OS X 10.4 | ||
# When at the desktop, insert a CD into the optical drive and check if it mounts on the desktop | # When at the desktop, insert a CD into the optical drive and check if it mounts on the desktop | ||
| − | # Click on the | + | # Click on the apple icon in the upper-left corner of the screen |
# Select the '''About this Mac''' option from the menu | # Select the '''About this Mac''' option from the menu | ||
# Click the '''More info''' button to launch the System Profiler | # Click the '''More info''' button to launch the System Profiler | ||
| Line 28: | Line 43: | ||
#* If it fails to see the HD or reports the amount of memory incorrectly, the system should be recycled | #* If it fails to see the HD or reports the amount of memory incorrectly, the system should be recycled | ||
# Eject the CD | # Eject the CD | ||
| − | # Power the system down, remove the | + | # Power the system down and remove components |
| − | # | + | #* If it is a standard desktop system, remove the HDD and leave only 256 MB of tested RAM in the system |
| − | + | #* If it a system with a built-in display, leave only 256 MB of RAM in the system | |
| + | # Fill out the appropriate information on an As-Is sticker and attach it to the system | ||
| + | # Take it to the store | ||
| − | == | + | ==Wiping HDs in systems== |
| − | + | If you've just received a system from Mac Eval and need to wipe its drive without opening the system up, refer to the [[Hard drive wiping checklist]] for wiping instructions. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ==Building Instructions== | |
| − | + | Please refer to the [[MacBuild Desktop Checklist]] for build instructions. | |
| − | |||
| − | |||
| − | == | + | ==Special Configurations== |
{| fontname="Helvetica" fontsize="12" border="1" | {| fontname="Helvetica" fontsize="12" border="1" | ||
|- | |- | ||
| Line 52: | Line 62: | ||
|width="7%" align="center"|Done | |width="7%" align="center"|Done | ||
|- | |- | ||
| − | | | + | | Starting up Ubuntu on a difficult system || |
| − | + | There are startup options set by default in the bootloader, so startup will usually not require any input. However, the following are the default options that you can enter yourself if you don't want to wait for the bootloader to do it automatically. | |
| − | + | # For the first-stage Ubuntu bootstrap, enter '''l''' for Linux | |
| − | + | # For the yaboot boot prompt, enter '''Linux''' for the Ubuntu install that was just completed (it's case-sensitive, so make sure the L in '''Linux''' is capitalized) | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Some systems will not boot properly due to video issues. These systems will usually hang with a white or black screen after the yaboot boot prompt. For these systems, providing it with '''Linux video=ofonly''' at the yaboot boot prompt should fix the problem. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|| | || | ||
|- | |- | ||
| − | | | + | | Permanently make the ''video=ofonly'' addition to yaboot || |
| − | # In a terminal, edit the file ''/etc/ | + | If you needed to use the ''video=ofonly'' option to get the system to start up properly, you can permanently make the addition to yaboot. This is how you do it: |
| − | #* ''sudo nano /etc/ | + | # In a terminal, edit the file ''/etc/yaboot.conf'' as root |
| − | # | + | #* ''sudo nano /etc/yaboot.conf |
| − | # | + | # Locate the line that reads ''image=/boot/vmlinux'' |
| + | # Move the cursor to the end of the line that starts with ''append'' | ||
| + | #* The line, in its unaltered state, should read ''append="quiet splash"'' | ||
| + | # Add ''video=ofonly'' to the end of the ''append'' line (make sure to add it within the quotes of the original ''append'' entry | ||
| + | #* The line should now read ''append="quiet splash video=ofonly"'' | ||
# Save and close the file | # Save and close the file | ||
#* '''Ctrl+o''', then '''Ctrl+x''' | #* '''Ctrl+o''', then '''Ctrl+x''' | ||
| − | # Update the | + | # Update the bootloader with the changes to yaboot by running the following in a terminal: |
| − | + | #* '''''sudo ybin -v''''' | |
| − | + | # Restart the system to test the change | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | #* | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | # | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|| | || | ||
|- | |- | ||
| − | | | + | | Enable the Ubuntu startup splash screen|| |
| − | + | Sometimes a system will show a blank screen during startup instead of the normal Ubuntu splash screen. If this is the case, we can enable the Ubuntu splash screen by doing the following: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
# In a terminal, edit the file ''/etc/usplash.conf'' as root | # In a terminal, edit the file ''/etc/usplash.conf'' as root | ||
#* ''sudo nano /etc/usplash.conf'' | #* ''sudo nano /etc/usplash.conf'' | ||
| − | # | + | # Move the cursor down to the first empty line |
| − | # | + | # Type '''xres=1024''', press Tab, and type '''yres=768''' |
| + | #* So the line should read: <code>xres=1024 yres=768</code> | ||
| + | #* If you happen to know the native resolution of the display, you can try using that instead | ||
# Save and close the file | # Save and close the file | ||
#* '''Ctrl+o''', then '''Ctrl+x''' | #* '''Ctrl+o''', then '''Ctrl+x''' | ||
| − | # Update the startup files with the changed resolution values | + | # Update the startup files with the changed resolution values by running the following in a terminal: |
#* '''''sudo update-initramfs -u''''' | #* '''''sudo update-initramfs -u''''' | ||
#* The command takes a couple of of minutes to complete | #* The command takes a couple of of minutes to complete | ||
|| | || | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| − | [[Category:Macintosh]] | + | |
| + | [[Category:Macintosh Archive]] | ||
Latest revision as of 14:54, 16 February 2014
Building a desktop in MacBuild is a fairly simple process. Aside from occasionally needing specific hardware, building a desktop MacBox is virtually identical to building a standard FreekBox.
What we build
We focus mainly on Intel based Systems. Unless requested, we do not build any system with a PowerPC or lower.
Minimum Specs
PPC systems
PowerMac G5
|
PowerMac G5 Specs
|
Mac mini
|
Mac mini Specs
|
Intel systems
No minimum, we build them all
What we don't build
We don't build anything not in the PPC specs listed above. This means we process standard desktop systems within the PPC specs above that have a single G4 processor below 1.0 GHz with our as-is process and either sell them in the store as is or grant them out to organizations in need.
So what happens with systems not listed above?
- eMacs - 1.25 GHz and 1.42 GHz models are tested through our as-is process and sold in the store
- PowerMac G3 / G4 Graphites - recycled
- Old World / 68k / 9" CRT / beige Macs - we have an Old Mac Keeper List in MacBuild Eval and System Eval that we use for determining what we keep and what we don't. Old Mac Keepers are kept on the Old Mac shelf in the warehouse for future processing. Everything else is recycled. If a model that should be kept is presently being recycled, let a MacBuild instructor know.
Important note about netbooting OS X
We presently have a network-bootable setup of OS X available for use on the network. It's a very handy tool, but it does have its drawbacks. Some machines will be very picky about how they netboot and as such may refuse to do so. In that scenario, you should ask the instructor for an external hard drive to boot off of.
As-Is Procedure
Before running a system through the as-is process, look at what we don't build to make sure it should be tested through the as-is process. If you are uncertain, please ask an instructor.
- Install a tested battery
- Fill all RAM slots with tested RAM
- Install optical drive, if necessary
- For the HDD:
- If the system does NOT have a built-in display, connect a wiped HDD to the primary IDE channel
- REMEMBER: we are only installing this HDD for our testing purposes. It should be removed before the system is moved to the store
- If the system has a built-in display, run it through our HDD wiping procedure before continuing the as-is process
- If the HDD wiping procedure tells us the system has a bad HDD, let an instructor know so we can either replace the HDD during a less-busy day or use it as a training tool for newer volunteers
- If the system does NOT have a built-in display, connect a wiped HDD to the primary IDE channel
- Connect a mouse, keyboard, and monitor to system
- Boot the system into OS X:
- Connect the OS X 10.4 FireWire HDD to the system
- Make sure the FireWire HDD is turned on (there's a power switch on the back of the drive)
- Hold the Option key on the keyboard while system starts up to enter the Startup Manager
- Select the FireWire drive from the Startup Manager to boot into OS X 10.4
- When at the desktop, insert a CD into the optical drive and check if it mounts on the desktop
- 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 information for ATA and Memory in System Profiler to ensure that the system can see all devices on IDE channels and each memory module in each memory slot
- If it fails to see the HD or reports the amount of memory incorrectly, the system should be recycled
- Eject the CD
- Power the system down and remove components
- If it is a standard desktop system, remove the HDD and leave only 256 MB of tested RAM in the system
- If it a system with a built-in display, leave only 256 MB of RAM in the system
- Fill out the appropriate information on an As-Is sticker and attach it to the system
- Take it to the store
Wiping HDs in systems
If you've just received a system from Mac Eval and need to wipe its drive without opening the system up, refer to the Hard drive wiping checklist for wiping instructions.
Building Instructions
Please refer to the MacBuild Desktop Checklist for build instructions.
Special Configurations
| Steps | Notes/Detailed Instructions | Done |
| Starting up Ubuntu on a difficult system |
There are startup options set by default in the bootloader, so startup will usually not require any input. However, the following are the default options that you can enter yourself if you don't want to wait for the bootloader to do it automatically.
Some systems will not boot properly due to video issues. These systems will usually hang with a white or black screen after the yaboot boot prompt. For these systems, providing it with Linux video=ofonly at the yaboot boot prompt should fix the problem. |
|
| Permanently make the video=ofonly addition to yaboot |
If you needed to use the video=ofonly option to get the system to start up properly, you can permanently make the addition to yaboot. This is how you do it:
|
|
| Enable the Ubuntu startup splash screen |
Sometimes a system will show a blank screen during startup instead of the normal Ubuntu splash screen. If this is the case, we can enable the Ubuntu splash screen by doing the following:
|