BX chipset max cache accepted?

Post Reply
jaybird
Posts: 301
Joined: Tue Jul 30, 2002 9:21 pm

BX chipset max cache accepted?

Post by jaybird »

I read or heard some where that the BX chipset will only support up to 512 meg of cache? True or false?

The reason I am asking is that I just completed my second PIII modded BP6 running dual 1100E's (1100/256/100/1.75V) @ 110 FSB.

This board is at its' max potential and then some (all caps replaced, EC10 mod and VTT regulator mod as well as a few others).

The only way I can see getting more out of it is to install 1.4 PIII's and under-clock them. The only major advantages here are the larger cache size and the additional instruction sets but if the BX will only accept 512 then I don't want to waste my time and money on the 1.4's.

Does anyone have the answer to this question?

Regards,

jaybird
purrkur
Linux Guru
Posts: 687
Joined: Fri Dec 12, 2003 5:57 pm
Location: Sweden
Contact:

Post by purrkur »

This might be correct. I still haven't found any information on the BX but I do know that the ZX (BX's smaller sybling) only supports 256 megs of cache. I wouldn't be surprised if the roof was 512, which would still be pretty good considering the age of the chipset.
2x533MHz@544MHz, 2.0V
640MB PC100 memory
Realtek RTL-8139 NIC
Maxtor 6Y080L0 80GB hdd
Debian Linux stable with 2.4.8 kernel
KliK
Posts: 350
Joined: Fri Mar 11, 2005 3:56 pm
Location: Zagreb, Croatia
Contact:

Post by KliK »

you could try too put some P3 with 512kB L2 and try it...but, as i remember BX was made for Xeon processors also, and they have 1MB L2!!!
so it's had to say...
hyperspace
Board Admin
Posts: 1395
Joined: Wed Jul 24, 2002 7:39 am
Location: Lincoln, NE USA
Contact:

Post by hyperspace »

In a couple Intel BX440 Designs docs, I found cache sizes of 128-KB and 256-KB (Celeron and Pentium-III, respectively). In another Intel BX440 Design doc, to discussed the cache size of 512-KB for a Pentium-II. So, maybe purrkur is right about a maximum size of 512-KB for the BX440.
Quantum WormHole

Image
lost in hypertime...
Post Reply