Dual Pentium 3

[janipewter]

Hi all, got a slight problem. I picked up an old server a while ago from a friend (a fellow forum member too). It is an old P3 box with a server motherboard, two CPU slots (yes slots, not sockets). I was using it up until 6 months ago or so when the OS install got corrupted during a power cut.

Anyways, rummaging through a friends box of PC bits, I found another P3 proc which looked similar to the one I already had, so he let me keep it. Well it turns out this proc is almost identical (see pics below). I've installed it in the server, but now I get a lot of trouble trying to use it. If I try to install Windows, it gets part way through the "Setup is loading Windows" and dumps a bsod. I Google'd the error code and a lot of results were suggesting hardware problems, specifically CPU/RAM (no surprise there, and btw the RAM is fine).

Booting from an Ubuntu live cd isn't great either, there are major problems with the display and I get no mouse or keyboard input (again, mouse and kb are fine).

So now I'm wondering whether there is more I need to do to get the procs working together? I couldn't find anything in BIOS for it, but then again it's not the most amazing BIOS.

Proc 1:

http://img86.imageshack.us/img86/369/dsc00643ko8.jpg

Proc 2:

http://img122.imageshack.us/img122/1817/dsc00644ik7.jpg

Thanks.

 

[xwb]

Just a wild shot. Remove the other CPU, install the OS the put the CPU back and check whether it works.

Is there any documentation on the jumpers on the motherboard? There might be a 1 or 2 CPU option.

 

[Freestone]

Older servers that I have worked required a VRM (Voltage Regulation Module

http://en.wikipedia.org/wiki/Voltage_regulator_module)

for each processor installed. Not sure if this is true in your case.

 

[janipewter]

I have absolutely no documentation for the box at all. VRM, hmm will have to look in to it. Currently installing Debian to see if it sees both procs. Will report back soon.

 

[janipewter]

Right. Setup has failed for Debian, Ubuntu and Win2k3. I have now conceded that the problem is bad RAM