Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bad crash



On Monday 02 December 2002 11:17 pm, John Abreau wrote:
> Yes, the extended beep meant either the memory wasn't seated properly
> or the power supply was bad. The code for a bad CPU fan would have been
> four short beeps.
>
> Phil Molloy looked at it, and he's convinced that the motherboard is fried.
> He didn't have a spare CPU fan on hand, though. If you have one that will
> fit my CPU, it wouldn't hurt to give it a try. It's a Socket-A Athlon
> T-bird 1.2GHz.

Nope, sorry.  It's unlikely that just the fan would prevent the system from 
booting.  Unless the fan failure has already caused the CPU to fry.


-------------------------------------------------------------------
DDDD   David Kramer                   http://thekramers.net
DK KD  "The Hitchhiker's Guide to the Galaxy also mentions alcohol. 
DKK D  It says that the best drink in existance is the Pan Galactic
DK KD  Gargle Blaster."
DDDD             Douglas Adams, "Hitchhiker's Guide to the Galaxy".




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org