dual processor upgrade = lockup on boot

[Dan]

I am adding a second processor to a Netfinity M20 server
running Windows 2000 server. After upgrading the BIOS,
installing the processor and the VRM I boot up and the
machine shows the initial IBM boot screen and then locks
up. I can't get into the diagnostics. The initial line
lists 2 processors present so it is identifying the
processors. If the VRM was faulty, would it even identify
the 2nd processor?

The processors are identical - same stepping #, I have
switched the processors and they both work as the primary
processor. The VRM is new but I have no way of testing
it. The next item to load in the boot process is the bios
for Adaptec SCSI bios.

Any suggestions are appreciated.

Dan

 

[*Vanguard*]

"Dan" said in news:[email protected]:

I am adding a second processor to a Netfinity M20 server
running Windows 2000 server. After upgrading the BIOS,
installing the processor and the VRM I boot up and the
machine shows the initial IBM boot screen and then locks
up. I can't get into the diagnostics. The initial line
lists 2 processors present so it is identifying the
processors. If the VRM was faulty, would it even identify
the 2nd processor?

The processors are identical - same stepping #, I have
switched the processors and they both work as the primary
processor. The VRM is new but I have no way of testing
it. The next item to load in the boot process is the bios
for Adaptec SCSI bios.

Any suggestions are appreciated.

Dan

Did you boot from the Windows 2000 CD to use its Repair selection to perform
an in-place upgrade so the standard HAL (hardware abstraction layer) got
replaced with the multiprocessor HAL?

While the KB article at http://support.microsoft.com/?kbid=234558 tells you
how to switch the HAL, it assumes that you can actually load Windows and run
Device Manager. Since you get locked up during the Windows startup, that's
not an option. The article explains how to use recovery console mode to
switch the HAL files. My guess is to perform an in-place upgrade
(http://support.microsoft.com/?kbid=292175) and hope that it detects the
multiple processors and so it then installs the multiprocessor HAL instead
of the standard uniprocessor HAL.

Before making the change, however, you might want to revert to one
processor, bootup to make sure it comes up okay, and then do a full backup
or drive image to ensure you can recover if the attempt to switch to the
multiprocessor HAL screws up the system.

 

[Guest]

Or you can remove 1 processor, reboot, and update HAL from device manager(have w2k install disk handy) as shown in following link
http://support.microsoft.com/?kbid=29217
Shutdown PC and then install the 2nd processor.

 

[Vance Green]

Doesn't IBM use a propietary machine-specific HAL like
Compaq? That may be the problem...

 

[Matthew Mucker [MSFT]]

Dan,

Ensure you're running the latest BIOS on this machine.

This is the voice of experience speaking here. I've seen *lots* of
similar problems solved with a BIOS update.

-Matt

 

[nut cracker]

No

And Compaq hasnt had a proprietary hal since the days of the System Pro.
(pre pentium)

NuTs

 

[nut cracker]

Yes... this is what I would suggest.

Or you can remove 1 processor, reboot, and update HAL from device

manager(have w2k install disk handy) as shown in following link: