Difference between revisions of "Getting the Processor Information"

From FreekiWiki
Jump to navigation Jump to search
(→‎Getting the System to POST: dept of redundancy department)
Line 51: Line 51:
 
* If it fails POST it will never boot, no matter how many floppy disks you try. This is because it doesn't access the drives until after a successful POST.
 
* If it fails POST it will never boot, no matter how many floppy disks you try. This is because it doesn't access the drives until after a successful POST.
  
* Never boot from the hard drive in System Evaluation. (This is to protect our customers' data.) Instead, power down the system instead instead and disconnect the hard drive cable.  
+
* Never boot from the hard drive in System Evaluation. (This is to protect our customers' data.) Instead, power down the system and disconnect the hard drive cable.  
  
 
* If the system is likely to be a keeper, it becomes necessary to power up the system to see if it POSTs. If it does, this usually tells us information about the system. There are a couple of cases when it's not worth it trying to get the system to POST, these are:
 
* If the system is likely to be a keeper, it becomes necessary to power up the system to see if it POSTs. If it does, this usually tells us information about the system. There are a couple of cases when it's not worth it trying to get the system to POST, these are:

Revision as of 18:56, 6 November 2005

<graphvizr>

 digraph POSTING {
   addstuff        [label="Add the RAM and VIDEO"]
   bios            [label="Try to\nget into BIOS\nCan you get the\nPROCESSOR INFO?"]
   checkconnect    [label="Check the\ncables and connections\nDoes it POWER ON?"]
   floppyboot      [label="Try to\nBOOT FROM a FLOPPY\nCan you get the\nPROCESSOR INFO?"]
   manualdetermine [label="You will need to\nMANUALLY DETERMINE\nthe processor information\n(go back to main flow chart)", shape="box", URL="/index.php/System_Evaluation_2_Overview"] 
   post            [label="Does it\nPOST?"]
   poweron         [label="Does it\nPOWER ON?"]
   powersupply     [label="Does it have a\nPOWER SUPPLY?"]
   proc            [label="Does it have a\nPROCESSOR?"]
   procinfo        [label="Can you get the \nPROCESSOR INFORMATION?"]
   ramvideo        [label="Does it have\nRAM and VIDEO?"]
   simplify        [label="SIMPLIFY\nRemove uneeded cards\nand disconnect the drives\nDoes it POST?"]
   start           [label="TRYING TO GET A\nSYSTEM TO POST\nSTART HERE", shape="box"]
   swapram         [label="Swap out the RAM\nsystematically.\nTry PC100, PC133, and PC66\nDoes it POST?"]
   triage          [label="Ready for TRIAGE\n(go back to main flow chart)", shape="box", URL="/index.php/System_Evaluation_2_Overview"] 
   start -> powersupply [taillabel="YES"]
   powersupply -> proc [taillabel="YES"]
   powersupply -> manualdetermine [taillabel="NO"]
   proc -> ramvideo [taillabel="YES"]
   proc -> triage [taillabel="NO"]
   ramvideo -> poweron [taillabel="YES"]
   ramvideo -> addstuff [taillabel="NO"]
   addstuff -> poweron
   poweron -> post [taillabel="YES"]
   poweron -> checkconnect [taillabel="NO"]
   checkconnect -> post [taillabel="YES"]
   checkconnect -> manualdetermine [taillabel="NO"]
   post -> procinfo [taillabel="YES"]
   post -> simplify [taillabel="NO"]
   procinfo -> bios [taillabel="NO"]
   procinfo -> triage [taillabel="YES"]
   bios -> triage [taillabel="YES"]
   bios -> floppyboot [taillabel="NO"]
   floppyboot -> triage [label="YES"]
   floppyboot -> manualdetermine [label="NO"]
   simplify -> procinfo [taillabel="YES"]
   simplify -> swapram [taillabel="NO"]
   swapram -> procinfo [taillabel="YES"]
   swapram -> manualdetermine [taillabel="NO"]
 }

</graphvizr>

Getting the System to POST

  • Getting a system to POST and getting it to boot are two different things. POST means Power On Self Test, and happens first. At this stage the computer is self-testing to make certain that it can boot when the time comes. It does a simple check against its BIOS, processor, and memory.
  • If it fails POST it will never boot, no matter how many floppy disks you try. This is because it doesn't access the drives until after a successful POST.
  • Never boot from the hard drive in System Evaluation. (This is to protect our customers' data.) Instead, power down the system and disconnect the hard drive cable.
  • If the system is likely to be a keeper, it becomes necessary to power up the system to see if it POSTs. If it does, this usually tells us information about the system. There are a couple of cases when it's not worth it trying to get the system to POST, these are:

When not to even try

  • If the power supply is missing, it is not worth trying to get it to POST or boot at this point. Write "No Power Supply" on the label. Pull the processor to see what kind it is, note the processor class and speed on the label, and continue on.
  • If the processor is missing, it is not worth trying to get it to POST or boot at this point. Treat the processor as 0 MHZ and refer to the system triage chart.

General instructions

  1. Open the system first. You'll need it open later anyway.
  2. In order to POST we may need to add any missing but essential components. Make certain these items are all present and properly connected and/or seated in their slots:
    • RAM
    • Video (card or onboard)
  3. Make sure everything is hooked up
    • Power supply to motherboard
    • Power supply to power
    • Video cable to monitor
    • Keyboard to keyboard port
  4. Power up the system and see if it POSTs.

Troubleshooting

Power up the system. Pay attention to the sounds the system makes. Normally, you can hear the fan and/or hard drive spinning, then a single beep. Extra beeps, or long, high pitched beeps indicate a problem. No beeps at all may indicate that the power is not hooked up (or the speakers are disconnected). Typical steps for troubleshooting systems that won't post are:

  1. Incompatible, missing. or poorly seated RAM. (Swap, install or reseat RAM.)
  2. SIMMs that are not in the first two SIMM slots. (Move SIMMs. The slots are usually labeled with teensy weensy letters or numbers.)
  3. A poorly seated card in one of the slots. (Pull unnecessary cards.)
  4. A card with a short in it. (Swap card with a known working card.)
  5. An IDE cable that is connected to the motherboard with a bad or missing IDE device. Some motherboards will not POST in this condition. (Disconnect the IDE cables from the motherboard.)

When it doesn't work

If you cannot get a system to POST, you will need to physically examine the processor to see its class and speed. NO POST is not a reason to recycle a system.

When it does work

If the system POSTs correctly, you may see a report on the amount of memory and the processor class and speed. If so, use the triage chart and this information to determine if it's a keeper or a recycler. In some circumstances, you'll need to get into BIOS to see this information. In a few cases you may even need to boot from a floppy. (If so, see Booting from a floppy disk.)