Difference between revisions of "Motherboards"

From FreekiWiki
Jump to navigation Jump to search
(removed categories from page marked {{delete}})
 
(26 intermediate revisions by 9 users not shown)
Line 1: Line 1:
==Welcome to mobo land==
+
{{delete}} replaced with new page [[MotherBoard Testing]]
  
** this is about how to test motherboards.
+
== Boards We Like to Test ==
 +
* [[wikipedia:Socket 423|Socket 423]]
 +
* [[wikipedia:Socket 462|Socket 462]]
 +
* [[wikipedia:Socket 478|Socket 478]]
 +
* [[wikipedia:Socket 479|Socket 479]]
 +
* [[wikipedia:Socket 603|Socket 603]]
 +
* [[wikipedia:Socket 754|Socket 754]]
 +
* [[wikipedia:Socket 775|Socket 775]]
 +
* [[wikipedia:Socket 939|Socket 939]]
 +
* [[wikipedia:Socket 940|Socket 940]]
 +
* [[wikipedia:Socket AM2|Socket AM2]]
  
*there is some knowledge needed to test motherboards properly.
+
== How to Test ==
 
+
* Grab a Motherboard, check for visual defects (blown caps, mutilated components)
here is a list of commands I think one should know. (besides the basics)
+
* Secure MoBo to plate, ensuring the risers are not grounding out the board.
 
+
* Test battery,
*mount(8)
+
* Add a tested processor and a fan for that MoBo
  You use this command to mount devices. Like a hard drive or a floppy disk.
+
* Add tested memory
  Some knowledge of the /dev directory is needed but not a whole lot. have fun.
+
* Attempt to post
       
+
** Connect the minimal things needed to post (power, keyboard, video, etc).
            mount /dev/fd0 /place/in/file/system/to/mount/device
+
** If it does not post replace the processor (do an internet search with the socket number to find the range the range of compatible processors).
                                    ^
+
* Power down, then attach:
                                  /|\
+
** Imaged hard drive to IDE1 (Primary)
                                    |  this is most of the time /mnt/floppy
+
** CD Drive to IDE2 (Secondary
  if you type " umount /dev/fd0 " after that command you would unmount the device from the
+
** Floppy Drive to FD controller
  file system.
+
** Peripherals (mouse, keyboard, Video)
 
+
* Boot into BIOS
*dmesg(8)
+
** Set the clock and date.
  This is a very nifty command. It tells all. As in it tells every thing about your
+
** Change the boot order to be CD Rom first , Hard Drive second, Floppy disconnect.
  system (well most of the time). it is used with the command less(1) a lot. At least with me
+
* Boot to Memtest, Let it run for a minute. Test all memory slots. (The memtest program is a boot option on the hard drive)
  or grep.
+
* Boot up to Operating System
+
** Check that the mouse and keyboard work.
          Try and type:  
+
** If you have on board video check that it works.
                        dmesg | less
+
** Test all the USB ports with a mouse.
            or
+
** If you have on board sound play a audio cd, if not then open a terminal and run basiccheck -m
                        dmesg | grep hdc  # to see what device is attached to /dev/hdc
+
** Open terminal and run stress-test.
  TRY IT it's fun.
+
** Test all card slots by plugging in a video card, turn on computer, if you get a screen turn off computer and repeat with all slots.
 
+
*Some cases might call for testing
==So You have all the parts and a knoppix disk.==
+
**SATA
 
 
*First make sure everything is pluged in yeah.
 
 
 
  If you have never booted from a live linux cd or knoppix now is the time to learn.
 
  After the system POSTs you will be met by a command prompt it will say some where
 
  to press F2 or F3 for a cheat sheet, feel free to do so. or you could just type:
 
     
 
        knoppix 2
 
 
  then enter. That command well boot the system into run level 2
 
  which is short for start the system with out the X server.
 
 
 
* next check if the system can see all the hardware and anything else you pluged into it.
 
 
 
  hint: use dmesg
 
 
 
*well, what if?
 
 
 
What if what!! It should work right RIGHT! Not all the time is right sometimes It just doesn't work.
 
 
 
hint number two: check for bad capacitors. what are bad caps?? well google it or ask Dave Haskins ;)
 
, but most if the time if it doesn't work then it just doesn't work.
 
  
 
==HAVE FUN==
 
==HAVE FUN==

Latest revision as of 11:46, 1 December 2010

deletion

This page has been requested to be deleted.
If you disagree, discuss on the talk page.
Whenever possible, could an Admin please remove this page?

replaced with new page MotherBoard Testing

Boards We Like to Test

How to Test

  • Grab a Motherboard, check for visual defects (blown caps, mutilated components)
  • Secure MoBo to plate, ensuring the risers are not grounding out the board.
  • Test battery,
  • Add a tested processor and a fan for that MoBo
  • Add tested memory
  • Attempt to post
    • Connect the minimal things needed to post (power, keyboard, video, etc).
    • If it does not post replace the processor (do an internet search with the socket number to find the range the range of compatible processors).
  • Power down, then attach:
    • Imaged hard drive to IDE1 (Primary)
    • CD Drive to IDE2 (Secondary
    • Floppy Drive to FD controller
    • Peripherals (mouse, keyboard, Video)
  • Boot into BIOS
    • Set the clock and date.
    • Change the boot order to be CD Rom first , Hard Drive second, Floppy disconnect.
  • Boot to Memtest, Let it run for a minute. Test all memory slots. (The memtest program is a boot option on the hard drive)
  • Boot up to Operating System
    • Check that the mouse and keyboard work.
    • If you have on board video check that it works.
    • Test all the USB ports with a mouse.
    • If you have on board sound play a audio cd, if not then open a terminal and run basiccheck -m
    • Open terminal and run stress-test.
    • Test all card slots by plugging in a video card, turn on computer, if you get a screen turn off computer and repeat with all slots.
  • Some cases might call for testing
    • SATA

HAVE FUN