MSI K7T-Turbo, T-bird and 133 FSB problems

[Icebear]

Hi all!
I have the following configuration
Antec 1030 case with 300W PS.
MSI K7T-turbo
T-bird 1100 100 MHz, unlocked with conductive silver and it works with all multipliers.
Taisol HSF

Now to the problem.
I can't get 133 FSB to work.
Setting the multiplier to 7, power off, unplug the 133 jumper.
When i start DLED gives me 4 red which means power on but refuses to go further.

I am using the latest BIOS.

Any suggestions?

 

[Poof]

What RAM?

 

[Icebear]

I am using 2 sticks of 128 Mb Mosel Vitelic rated CAS 2 at 133

 

[Poof]

IIRC, taking that jumper off kicks it right to 133 at boot (hopefully it would do this). Have you tried kicking the Vcore up some and then cranking to 133?

 

[Icebear]

The Vcore current was at 1.90 when i tried it.

I read some on the web that there where problems with non C revisions of Athlon and 133 with the MSI board?

Is there anyone who has got this to work??

 

[joeblo123]

This is a known prob with the MSI Turbos...there are lots of posts under MOBO that define the prob but here is the basics of it...

Apparantly, when the system first boots up, it boots up at the Default multiplier for the CPU, in your case 11, for a split second. Since you are trying to boot up at 133 FSB, in essence, the system is trying to boot up at 11x133(1436mhz). Even though it's only doing it for a slpit sec, it seems to be too much for the MOBO to handle.

I don't think there's a known fix for it yet.

Hope this helps.

 

[Poof]

I've been going through a thread over on motherboards (since I do have a K7T Pro2a), and noticed that some reported going into the BIOS, setting the FSB to 100, setting the lower multiplier in prep. for 133, saving that, shutting down, doing the 133 jumper bit, and then booting.

Icebear - try that...

 

[Icebear]

Hi!

That is what I've been doing, doesn't seem to work...

I guess I will have to hold out for a new BIOS update...

 

[Mavo]

Are your L7 bridges connected or did you change your voltage in the bios?

 

[joeblo123]

Icebar, as I posted, the prob is that no matter what multiplier you set it to, it boots up at the default (x11) for you. That's what's causing the prob. The people who are able to get around this prob are people who have Durons or TBirds below the 1Ghz.

 

[Icebear]

joeblo123 I think you are definately right,
This is what I came up with after going through the MSI newsgroup.
//
It won't run at 133 because when the system is booted the default multiplier
is applied for a short period of time no matter what you have the multiplier
set to in the bios. The only way to circumvent this problem is to change the
default multiplier by cutting and bridging the L3, L4 and L6 bridges as
appropriate.

There is no differance between Athlon "B" and "C" cpus, just the default
multiplier.
//

 

[Cenco]

How do you do it with the bridges?

any weblink?

regards

Cenco