Pentium D920 only as uniprocessor.

Motherboard is Abit NI8 SLI GR and the processor is Intel (Pentiu) D
920.

I have now installed XP Pro UK SP2, that doesn't see the processor as
two, just one..

BIOS recognises the processor correctly as 2 CPU's
Rask manager shows only one CPU (one graph per cpu is gray/not avaible)
CPU-Z 1.31 recognises the processor correctly, BUT, only as one
core/cpu (processor selection box is gray/unavaible)
Device manager had ACPI Uniprocessor HAL installed, Changed to ACPI
Multiprocessor HAL.
Under the processor in device manager, only one processor is avaible,
atleast on EE955 has here two processors..

Definately seem to be a problem with windows, but what to do ?

Drivers and updates are up-to-date.

Did you flash your BIOS? For Windows to take advantage of your CPU, you need
to flash your BIOS with these new CPU's.

"Fudgemaster@gmail.com" wrote:

> Motherboard is Abit NI8 SLI GR and the processor is Intel (Pentiu) D
> 920.
>
> I have now installed XP Pro UK SP2, that doesn't see the processor as
> two, just one..
>
> BIOS recognises the processor correctly as 2 CPU's
> Rask manager shows only one CPU (one graph per cpu is gray/not avaible)
> CPU-Z 1.31 recognises the processor correctly, BUT, only as one
> core/cpu (processor selection box is gray/unavaible)
> Device manager had ACPI Uniprocessor HAL installed, Changed to ACPI
> Multiprocessor HAL.
> Under the processor in device manager, only one processor is avaible,
> atleast on EE955 has here two processors..
>
> Definately seem to be a problem with windows, but what to do ?
>
> Drivers and updates are up-to-date.
>
>

Yeah.

I got the 1.2 bios on the board. flashed it.
No help.

Can't find any help on the web either, strange.


"Ryan" wrote:

> Did you flash your BIOS? For Windows to take advantage of your CPU, you need
> to flash your BIOS with these new CPU's.
>
> "Fudgemaster@gmail.com" wrote:
>
> > Motherboard is Abit NI8 SLI GR and the processor is Intel (Pentiu) D
> > 920.
> >
> > I have now installed XP Pro UK SP2, that doesn't see the processor as
> > two, just one..
> >
> > BIOS recognises the processor correctly as 2 CPU's
> > Rask manager shows only one CPU (one graph per cpu is gray/not avaible)
> > CPU-Z 1.31 recognises the processor correctly, BUT, only as one
> > core/cpu (processor selection box is gray/unavaible)
> > Device manager had ACPI Uniprocessor HAL installed, Changed to ACPI
> > Multiprocessor HAL.
> > Under the processor in device manager, only one processor is avaible,
> > atleast on EE955 has here two processors..
> >
> > Definately seem to be a problem with windows, but what to do ?
> >
> > Drivers and updates are up-to-date.
> >
> >

try asking over in

alt.comp.periphs.mainboard.abit

good group of abit experts there. D9xx series is new, and I have heard
that the D930 especially needs a recent bios update to even run. You at
least are up and running.

How did you change the HAL? By rerunning XP Setup I assume. Did you let
XP Setup connect to the net to retrieve any setup updates? That may be
needed to deal w/ these new processors. Try a KB search on "Intel D920"
or some other Dxx value. Also, the most recent Intel Chipset Drivers
should be installed soon after XP Setup has worked.

Okay. let's see what they think in that alt. group.

I had my computer connected to the net from dead to desktop intalled
and let it use the net as it liked.
Drained the windows updates and installed about all of them.

I changed the HAL manually by changing the driver like I used to do
when Using Abit BP6/VP6 and doing ja one to two processor upgrade in
w2k.

And this motherborad does not have a intel chipset but a NVIDIA C19/
MCP04.

Fudgemaster@gmail.com wrote:
> Okay. let's see what they think in that alt. group.
>
> I had my computer connected to the net from dead to desktop intalled
> and let it use the net as it liked.
> Drained the windows updates and installed about all of them.
>
> I changed the HAL manually by changing the driver like I used to do
> when Using Abit BP6/VP6 and doing ja one to two processor upgrade in
> w2k.
>
> And this motherborad does not have a intel chipset but a NVIDIA C19/
> MCP04.

Did you previously have a different CPU on this motherboard? I have seen
cases where a repair install of XP was required before a hyperthreading CPU
was recognized properly. Usually if the ACPI Uniprocessor HAL is loaded the
ACPI Multiprocessor HAL will be automatically loaded when switching to a new
CPU. If it doesn't do it automatically on first boot with the new CPU then I
haven't been able to get switching it manually to work. A repair install was
needed. This was when upgrading from a Celeron to a P4 Hyperthreading CPU.
Dual core would probably be similar.

Kerry

>> I had my computer connected to the net from dead to desktop intalled
>> and let it use the net as it liked.
>> Drained the windows updates and installed about all of them.
>>
>> I changed the HAL manually by changing the driver like I used to do
>> when Using Abit BP6/VP6 and doing ja one to two processor upgrade in
>> w2k.
>>
>> And this motherborad does not have a intel chipset but a NVIDIA C19/
>> MCP04.
>
>Did you previously have a different CPU on this motherboard? I have seen
>cases where a repair install of XP was required before a hyperthreading CPU
>was recognized properly. Usually if the ACPI Uniprocessor HAL is loaded the
>ACPI Multiprocessor HAL will be automatically loaded when switching to a new
>CPU. If it doesn't do it automatically on first boot with the new CPU then I
>haven't been able to get switching it manually to work. A repair install was
>needed. This was when upgrading from a Celeron to a P4 Hyperthreading CPU.
>Dual core would probably be similar.

This is a brand spanking new computer all together for the first time
now.

So no old hardware / drivers / software spooking around.
Windows just had installed as uniprocessor hal for some reason.

- Sami Partanen .
--
Kuvia ratapäiviltä, autonäyttelyistä jne.
http://www.partanen.net/
It's an insane world, but I'm proud to be a part of it.

Windows usually has a good reasons to decide that machine is uniprocessor.
Also, Microsoft specially cautions against forcing other HAL than one the
Setup choses (see KB309283).
This means that your machine has a problem.

A suggestion: run the DOS version of Intel Processor Frequency ID Utility
and see how it detects the machine.

http://downloadfinder.intel.com/scr...8&OSFullName=OS Independent&lang=eng

Regards,
--PA


"Sami Partanen" wrote:
> >> I had my computer connected to the net from dead to desktop intalled
> >> and let it use the net as it liked.
> >> Drained the windows updates and installed about all of them.
> >>
> >> I changed the HAL manually by changing the driver like I used to do
> >> when Using Abit BP6/VP6 and doing ja one to two processor upgrade in
> >> w2k.
> >>
> >> And this motherborad does not have a intel chipset but a NVIDIA C19/
> >> MCP04.
> >
> >Did you previously have a different CPU on this motherboard? I have seen
> >cases where a repair install of XP was required before a hyperthreading CPU
> >was recognized properly. Usually if the ACPI Uniprocessor HAL is loaded the
> >ACPI Multiprocessor HAL will be automatically loaded when switching to a new
> >CPU. If it doesn't do it automatically on first boot with the new CPU then I
> >haven't been able to get switching it manually to work. A repair install was
> >needed. This was when upgrading from a Celeron to a P4 Hyperthreading CPU.
> >Dual core would probably be similar.
>
> This is a brand spanking new computer all together for the first time
> now.
>
> So no old hardware / drivers / software spooking around.
> Windows just had installed as uniprocessor hal for some reason.
>
> - Sami Partanen .
> --
> Kuvia ratapäiviltä, autonäyttelyistä jne.
> http://www.partanen.net/
> It's an insane world, but I'm proud to be a part of it.
>

>Windows usually has a good reasons to decide that machine is uniprocessor.
>Also, Microsoft specially cautions against forcing other HAL than one the
>Setup choses (see KB309283).
>This means that your machine has a problem.
>
>A suggestion: run the DOS version of Intel Processor Frequency ID Utility
>and see how it detects the machine.
>

Thanks, I'll check that.
And now to train the brain, making a bootable CD for not having a
floppy drive.

- Sami Partanen .
--
Kuvia ratapäiviltä, autonäyttelyistä jne.
http://www.partanen.net/
It's an insane world, but I'm proud to be a part of it.

>Windows usually has a good reasons to decide that machine is uniprocessor.
>Also, Microsoft specially cautions against forcing other HAL than one the
>Setup choses (see KB309283).
>This means that your machine has a problem.
>
>A suggestion: run the DOS version of Intel Processor Frequency ID Utility
>and see how it detects the machine.

I ran the dos util and it didn't recognise the cpu at all.
http://partanen.net/tmp/cpu2.png
But the windows util recognises correctly.
http://partanen.net/tmp/cpu.png
--
Kuvia ratapäiviltä, autonäyttelyistä jne.
http://www.partanen.net/
It's an insane world, but I'm proud to be a part of it.