Difference between revisions of "MacBuild Desktop Build"
Line 35: | Line 35: | ||
# Boot the system into OS X: | # Boot the system into OS X: | ||
#* Connect the OS X 10.4 FireWire HDD to the system | #* Connect the OS X 10.4 FireWire HDD to the system | ||
− | #* Make sure the FireWire HDD is turned on | + | #* 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 | #* 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 | #* Select the FireWire drive from the Startup Manager to boot into OS X 10.4 |
Revision as of 18:17, 5 October 2010
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 presently work on certain PowerMac G4 models, all Mac minis, all iMac G4s, all iMac G5s, and all systems with Intel processors. The specs we build the most common models to are as follows:
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 10.5 available for use on the network. It's a very handy tool, but it does have its drawbacks. In particular:
- The OS X 10.5 netboot image is over 11 GB in size. This is data that has to be transferred over our network and onto whatever system we happen to be working on. Though not all of the 11 GB of the netboot image are used on each machine that is netbooted into OS X, keep in mind that there are multiple systems in place at Free Geek that use up a considerable amount of our internal bandwidth (system imaging and installs, in particular), and this usage will greatly impact how quickly a system netboots.
- The netboot image loads very, very slowly on some systems, particularly on G4 systems without much RAM. Even if the system specifications are sufficient to run OS X 10.5, it is not uncommon to wait over five minutes while a system finishes the netboot process.
So, what should you take away from all this? Essentially, use external HDDs when possible, and use the netboot setup only when the external HDDs are unavailable.
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:
|