Yeah, there's a fan already installed, and it came already connected. Works like a charm when I power it up.
I have checked what the beeps mean from the Abit USA forums, and this problem is very, very widespread. A Finnish forum I peruse on technical matters has several NF7-S ambulance owners as well. The Silent Breeze II is specified to work on up to AXP 3000+, and some folks are overclocking this processor with it to AXP 3200+ and beyond.
Like I said, I've tried out everything I could find that has been suggested: turning the alarm off, setting the alarm temperatures up, memory placings, reseating the heatsink, and updating the BIOS to the newest version. I'm going to take out the PSU fan monitor next, see if its rpm readings are still messing it up.
The FSB/DRAM ratio is set by the mobo automatically, I thought it was misidentifying my RAM when it showed it as DDR333, when in fact it had independently set it to match my FSB.
One thing I could do is flash in a slightly older BIOS and reflash to the newest, since my problem was explicitly addressed in the BIOS I have now, so maybe it somehow didn't happen properly.
I have checked what the beeps mean from the Abit USA forums, and this problem is very, very widespread. A Finnish forum I peruse on technical matters has several NF7-S ambulance owners as well. The Silent Breeze II is specified to work on up to AXP 3000+, and some folks are overclocking this processor with it to AXP 3200+ and beyond.
Like I said, I've tried out everything I could find that has been suggested: turning the alarm off, setting the alarm temperatures up, memory placings, reseating the heatsink, and updating the BIOS to the newest version. I'm going to take out the PSU fan monitor next, see if its rpm readings are still messing it up.
The FSB/DRAM ratio is set by the mobo automatically, I thought it was misidentifying my RAM when it showed it as DDR333, when in fact it had independently set it to match my FSB.
One thing I could do is flash in a slightly older BIOS and reflash to the newest, since my problem was explicitly addressed in the BIOS I have now, so maybe it somehow didn't happen properly.
Comment