Hello,
I've inherited an SMP machine for which I've no documentation and don't
have convenient access to the hardware itself. The computer has a
single Xeon 2.8GHz CPU and I'd like to purchase another CPU. Question
is, can I simply match another Xeon of the same speed and expect it to
work? If
Hello,
On Wed, Oct 19, 2005 at 03:44:46PM -0500 or thereabouts, Doug Poland wrote:
> I've inherited an SMP machine for which I've no documentation and don't
> have convenient access to the hardware itself. The computer has a
> single Xeon 2.8GHz CPU and I'd like to purchase another CPU. Question
On Oct 19, 2005, at 4:44 PM, Doug Poland wrote:
I've inherited an SMP machine for which I've no documentation and
don't
have convenient access to the hardware itself. The computer has a
single Xeon 2.8GHz CPU and I'd like to purchase another CPU. Question
is, can I simply match another Xeon o
At 01:44 PM 10/19/2005, Doug Poland wrote:
Hello,
I've inherited an SMP machine for which I've no documentation and don't
have convenient access to the hardware itself. The computer has a
single Xeon 2.8GHz CPU and I'd like to purchase another CPU. Question
is, can I simply match another Xeon
Charles Swiger wrote:
> On Oct 19, 2005, at 4:44 PM, Doug Poland wrote:
>
>> I've inherited an SMP machine for which I've no documentation and don't
>> have convenient access to the hardware itself. The computer has a
>> single Xeon 2.8GHz CPU and I'd like to purchase another CPU. Question
>> i
At 03:57 PM 10/19/2005, Kurt Buff wrote:
Charles Swiger wrote:
> On Oct 19, 2005, at 4:44 PM, Doug Poland wrote:
>
>> I've inherited an SMP machine for which I've no documentation and don't
>> have convenient access to the hardware itself. The computer has a
>> single Xeon 2.8GHz CPU and I'd li
Hello,
On Wed, Oct 19, 2005 at 06:26:54PM -0500 or thereabouts, Doug Poland wrote:
> Well, I have dmesg output and the output from dmidecode. I may be dense
> but I don't see the sSpec number in the output. Can it be derived from
> these data?
Well I don't know anything at all about sSpec num
Glenn Dawson wrote:
At 03:57 PM 10/19/2005, Kurt Buff wrote:
[ ... ]
You want to get the same speed, FSB, and family number of Xeon, and it
is preferable to get the same stepping number if possible.
It's better to match the sSpec numbers...those include the stepping, and
not all processors
At 04:48 PM 10/19/2005, Chuck Swiger wrote:
Glenn Dawson wrote:
At 03:57 PM 10/19/2005, Kurt Buff wrote:
[ ... ]
You want to get the same speed, FSB, and family number of Xeon, and it
is preferable to get the same stepping number if possible.
It's better to match the sSpec numbers...those inc
On Wed, Oct 19, 2005 at 07:48:34PM -0400, Chuck Swiger wrote:
> Glenn Dawson wrote:
> >At 03:57 PM 10/19/2005, Kurt Buff wrote:
> [ ... ]
> >>>You want to get the same speed, FSB, and family number of Xeon, and
> >>>it is preferable to get the same stepping number if possible.
> >
> >It's better to
On Thu, Oct 20, 2005 at 12:15:26AM +0200, martin hudec wrote:
> Hello,
>
> On Wed, Oct 19, 2005 at 03:44:46PM -0500 or thereabouts, Doug Poland wrote:
> > I've inherited an SMP machine for which I've no documentation and
> > don't have convenient access to the hardware itself. The computer
> > ha
> Well, I have dmesg output and the output from dmidecode. I may be dense
> but I don't see the sSpec number in the output. Can it be derived from
> these data?
from what I understand you get the sSpec number from
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.01-MHz 686-class CPU)
Origin = "Genuin
12 matches
Mail list logo
