n440bx (phoenixbios?) beep codes

ottothecow

Senior member
Aug 30, 2005
228
0
0
I have a motherboard that seems to be having trouble. It is an intel n440bx dual slot-1 server board that worked fine for me before.

Now when I turn it on, I get no video at all from the integrated video (tried a PCI video card but it was a questionable card, and I dont know how to get serial console up) and I get 4 long beeps. I can't find this beep code listed anywhere in the intel manual or elsewhere online. I think that intel uses phoenix bios on this board but I dont know how to confirm that (since I get no video) so that might make it easier.

Anyone have any clue what 4 beeps would mean? The manual has a lot of potential POST problems listed with their port-80 code but I dont have an PCI/ISA diagnostic card and I dont know any other way of checking these codes.
 

imported_Kiwi

Golden Member
Jul 17, 2004
1,375
0
0
Although there are plenty of web sites on which to look up beep codes (Google it), AT doesn't have such a table, and this isn't my regular Inet PC today. I might've had a bookmark on the other PC before a recent Mozilla bookmark file loss. Google is your friend.


:D
 

ottothecow

Senior member
Aug 30, 2005
228
0
0
I googled a fair amount for this code using the knowledge I have of these systems but I found nothing. The point is that I couldnt find online or in the intel documentation what a 1-1-1-1 beep code would mean.

I found all kinds of other beeps but nothing for 4 long beeps.
 

ottothecow

Senior member
Aug 30, 2005
228
0
0
I bought a pci diagnostic card and it also doesnt show anything in conjunction with this beep code

Anyone else want to weigh in on what 4 beeps could mean?
 

swarsys

Junior Member
Feb 22, 2006
1
0
0
Hi,

Just wanted to say I am having exactly the same problem (4 loud and long beeps) with an Amilo K7600. I just found out that it must be a problem with the power source. When I press the battery to ensure a perfect connection, the laptop boots normally. I'll see with a technician how this can be solved. Hope it's not a motherboard problem after all.

Cheers!

Mariano