Is it possible to drive the Board with 150MHz FSB?

Are any undocumented Jumpersettings available? I miss 105MHz and the
second 133MHz setting, with 44.3MHz PCI instead of 133/4 33.3MHz!? It´s
described but only the setting for 133/33 operations is shown.



Best Regards,

Daniel Mandic

P.S.: I could have a Mushkin 128MB (SSided 16Mx8) PC150 Cl.2... but
could a P2B run at 150?

Daniel Mandic wrote:

> Is it possible to drive the Board with 150MHz FSB?

Nope - well, not unless you figure out how to install a 150Mhz-capable
clock generator, which would be quite challenging as no pin-compatible
chips were made AFAIK.

> Are any undocumented Jumpersettings available? I miss 105MHz and the
> second 133MHz setting, with 44.3MHz PCI instead of 133/4 33.3MHz!? It´s
> described but only the setting for 133/33 operations is shown.

P2B 1.02 has an ICS9148BF-26 clock generator, with three FSB selection
inputs for bus frequencies between 50 and 133Mhz. You have three FSB
jumpers on the board, so all 8 possible settings are available to you.

The clock generator datasheet is available if you're interested:

http://www.icst.com/datasheets/ics9148-26.pdf

150Mhz-capable clock generators used on other P2B series boards have a
4th FSB selection input, and a higher pin count (56 vs 48).

P2B

> Best Regards,
>
> Daniel Mandic
>
> P.S.: I could have a Mushkin 128MB (SSided 16Mx8) PC150 Cl.2... but
> could a P2B run at 150?

P2B wrote:

>
>
> Daniel Mandic wrote:
>
> > Is it possible to drive the Board with 150MHz FSB?
>
> Nope - well, not unless you figure out how to install a
> 150Mhz-capable clock generator, which would be quite challenging as
> no pin-compatible chips were made AFAIK.
>
> > Are any undocumented Jumpersettings available? I miss 105MHz and the
> > second 133MHz setting, with 44.3MHz PCI instead of 133/4 33.3MHz!?
> > It´s described but only the setting for 133/33 operations is shown.
>
> P2B 1.02 has an ICS9148BF-26 clock generator, with three FSB
> selection inputs for bus frequencies between 50 and 133Mhz. You have
> three FSB jumpers on the board, so all 8 possible settings are
> available to you.
>
> The clock generator datasheet is available if you're interested:
>
> http://www.icst.com/datasheets/ics9148-26.pdf
>
> 150Mhz-capable clock generators used on other P2B series boards have
> a 4th FSB selection input, and a higher pin count (56 vs 48).
>
> P2B


Thanks a lot.


Could you say a P2B 1.02 is running stable at 133FSB, everything other
properly set up? PCI GfX.




Kind Regards,

Daniel Mandic

Daniel Mandic wrote:

> P2B wrote:
>
>
>>
>>Daniel Mandic wrote:
>>
>>
>>>Is it possible to drive the Board with 150MHz FSB?
>>
>>Nope - well, not unless you figure out how to install a
>>150Mhz-capable clock generator, which would be quite challenging as
>>no pin-compatible chips were made AFAIK.
>>
>>
>>>Are any undocumented Jumpersettings available? I miss 105MHz and the
>>>second 133MHz setting, with 44.3MHz PCI instead of 133/4 33.3MHz!?
>>>It´s described but only the setting for 133/33 operations is shown.
>>
>>P2B 1.02 has an ICS9148BF-26 clock generator, with three FSB
>>selection inputs for bus frequencies between 50 and 133Mhz. You have
>>three FSB jumpers on the board, so all 8 possible settings are
>>available to you.
>>
>>The clock generator datasheet is available if you're interested:
>>
>>http://www.icst.com/datasheets/ics9148-26.pdf
>>
>>150Mhz-capable clock generators used on other P2B series boards have
>>a 4th FSB selection input, and a higher pin count (56 vs 48).
>>
>>P2B
>
>
>
> Thanks a lot.
>
>
> Could you say a P2B 1.02 is running stable at 133FSB, everything other
> properly set up? PCI GfX.

Absolutely!

I have a P2B 1.02 running a P3-S 1.4Ghz CPU on a Slot-T adapter, 768MB
Corsair PC133 CL2, U2W SCSI controller, and a couple of 10K U160 disks -
stable as a rock 7x24. Video is GF4 AGP, but I've run Voodoo3 PCI at
133Mhz FSB on other P2Bs, no problems.

After building numerous systems with Tualatin processors and scrounged
P2B 1.02 boards, I haven't met one that doesn't play nicely at 133Mhz
FSB :-)

P2B

> Kind Regards,
>
> Daniel Mandic

P2B wrote:

> > Could you say a P2B 1.02 is running stable at 133FSB, everything
> > other properly set up? PCI GfX.
>
> Absolutely!
>
> I have a P2B 1.02 running a P3-S 1.4Ghz CPU on a Slot-T adapter,
> 768MB Corsair PC133 CL2, U2W SCSI controller, and a couple of 10K
> U160 disks - stable as a rock 7x24. Video is GF4 AGP, but I've run
> Voodoo3 PCI at 133Mhz FSB on other P2Bs, no problems.
>
> After building numerous systems with Tualatin processors and
> scrounged P2B 1.02 boards, I haven't met one that doesn't play nicely
> at 133Mhz FSB :-)
>
> P2B

Wow, nice System. It´s sounds to be solid.


My main System is only at 103MHz with the P3-S 1.4GHz, but the
stability amazes me every time. Nice to hear from you that even 1.02
P2B´s are solid rock stable at 133MHz.


I am thinking around about RAM to CPU latency...... I take the liberty
to ask you something.
Does a lower Multiplier (i.e. X2) have a lower latency than a higher?
Maybe 133x2 gives me a better system-responsibility than 100x3!?
What would you say?

My first Instance is a good and fast (stable)connection to the
ISA-Card. MIDI-Games etc. etc. Abandon etc.. ;-)
Only Windows95 (Best 3.1 Windows ;-)) is of matter. DOS is working so
and so (at all). Maybe I get VXD-Errors, when going with 133MHz!?




Best Regards,

Daniel Mandic

Daniel Mandic wrote:
> P2B wrote:
>
>
>>>Could you say a P2B 1.02 is running stable at 133FSB, everything
>>>other properly set up? PCI GfX.
>>
>>Absolutely!
>>
>>I have a P2B 1.02 running a P3-S 1.4Ghz CPU on a Slot-T adapter,
>>768MB Corsair PC133 CL2, U2W SCSI controller, and a couple of 10K
>>U160 disks - stable as a rock 7x24. Video is GF4 AGP, but I've run
>>Voodoo3 PCI at 133Mhz FSB on other P2Bs, no problems.
>>
>>After building numerous systems with Tualatin processors and
>>scrounged P2B 1.02 boards, I haven't met one that doesn't play nicely
>>at 133Mhz FSB :-)
>>
>>P2B
>
>
> Wow, nice System. It´s sounds to be solid.
>
>
> My main System is only at 103MHz with the P3-S 1.4GHz, but the
> stability amazes me every time. Nice to hear from you that even 1.02
> P2B´s are solid rock stable at 133MHz.

P2B-S 1.04 is even better. My file server runs a Celeron 1A at 1.5ghz,
150Mhz FSB - so both CPU and motherboard are overclocked 50%. I was a
little surprised when the SCSI RAID controller had no problem with the
overclocked PCI bus, but it's rock solid - has now been up for 87 days
continuously (I turned it off while on summer vacation).

My main system runs dual P3-S 1.4s @ 1470Mhz, 140Mhz FSB, on a P2B-DS
1.06 (P2B-DS can run one CPU at 150Mhz, but not two - the second CPU is
too far away from the chipset).

> I am thinking around about RAM to CPU latency...... I take the liberty
> to ask you something.
> Does a lower Multiplier (i.e. X2) have a lower latency than a higher?
> Maybe 133x2 gives me a better system-responsibility than 100x3!?
> What would you say?

I'm not sure I understand the question, but memory throughput is a
bottleneck on P2B series boards running faster CPUs - so you want the
FSB as high as possible. RAM timings make very little difference to real
world performance, so it's better to run the RAM at CL3 than reduce the
FSB to run CL2.

> My first Instance is a good and fast (stable)connection to the
> ISA-Card. MIDI-Games etc. etc. Abandon etc.. ;-)
> Only Windows95 (Best 3.1 Windows ;-)) is of matter. DOS is working so
> and so (at all). Maybe I get VXD-Errors, when going with 133MHz!?

My systems mostly run XP, which is more demanding on the hardware. You
won't have any problems running older Windows at 133Mhz provided your
RAM is decent.

P2B

P2B wrote:

> > My main System is only at 103MHz with the P3-S 1.4GHz, but the
> > stability amazes me every time. Nice to hear from you that even 1.02
> > P2B´s are solid rock stable at 133MHz.
>
> P2B-S 1.04 is even better. My file server runs a Celeron 1A at
> 1.5ghz, 150Mhz FSB - so both CPU and motherboard are overclocked 50%.
> I was a little surprised when the SCSI RAID controller had no problem
> with the overclocked PCI bus, but it's rock solid - has now been up
> for 87 days continuously (I turned it off while on summer vacation).
>
> My main system runs dual P3-S 1.4s @ 1470Mhz, 140Mhz FSB, on a P2B-DS
> 1.06 (P2B-DS can run one CPU at 150Mhz, but not two - the second CPU
> is too far away from the chipset).
>

Hi!


My Adaptec 2940 (U) did run on many machines, and 37.5MHz were always
possible. At 41 it did´nt find drives, cd etc. anymore.

> > I am thinking around about RAM to CPU latency...... I take the
> > liberty to ask you something.
> > Does a lower Multiplier (i.e. X2) have a lower latency than a
> > higher? Maybe 133x2 gives me a better system-responsibility than
> > 100x3!? What would you say?
>
> I'm not sure I understand the question, but memory throughput is a
> bottleneck on P2B series boards running faster CPUs - so you want the
> FSB as high as possible. RAM timings make very little difference to
> real world performance, so it's better to run the RAM at CL3 than
> reduce the FSB to run CL2.

I say exactly the opposite.

Well, 150FSB is the best playground for any further processing. Now I
have 5/2 112MHz FSB x2.5= 280MHz P2 (Xeon - I say... as this beast
really have a zero latency on the 2nd Cache, half clocked)
It´s pretty fast with windows 95 :-). My 280SE Benz :-)

I should try 150x2 with cl.2, which gives also the océd PCI (37.5) and
a 2/1 divider... faster than 5/2. But I am also already satisfied.

My personal testings concerning cl.2 cl.3, are done with ATARI´s
Neverwinter Nights. The KT133A behaved with Cl.2 much faster .... with
cl.3 it lagged more and did never (caching) get better.
No No, Cl.2 is a must :-). Especially like me, swapping merely kb´s and
bytes through the system. I don´t have to fullfill quests of
megatexturing, of 2-3MB the smallest :-) etc etc..
But why should I wait more cycles for some kb´s. Cl.2 is brisker.
Well, in benchmarks you see no difference even if you would use
5-5-5-10 ;-). Better is 2-2-2-? (0.5?)


>
> > My first Instance is a good and fast (stable)connection to the
> > ISA-Card. MIDI-Games etc. etc. Abandon etc.. ;-)
> > Only Windows95 (Best 3.1 Windows ;-)) is of matter. DOS is working
> > so and so (at all). Maybe I get VXD-Errors, when going with 133MHz!?
>
> My systems mostly run XP, which is more demanding on the hardware.
> You won't have any problems running older Windows at 133Mhz provided
> your RAM is decent.
>
> P2B

Yes, of course. Now I remember.... seemingly working sys´s, are
crashing with NT (blue-screen), at last. Thanks.





Best Regards,

Daniel Mandic