Duron (Morgan Core) anybody OC'ing with 133FSB?

[gtd2000]

Anybody got this nice little CPU to run at 133FSB yet?

I can't 🙁

 

[unknown8585]

This may answer your question

 

[gtd2000]

Nope thats not the answer - it does not apply to the KT7A - it boots at 100FSB before going into 133FSB mode - so when I boot at say 9x133 that should be only 900Mhz at the initial boot point or even 10x100FSB if it chooses the default multiplier.

There is also an ASUS board that works just like the KT7A - other boards (brands) do not boot with 100FSB then revert to 133FSB unfortunately. Only the ASUS and ABIT do this.

 

[gtd2000]

I'm wondering if this is something to do with the initial boot timing issue which is not supported with the older chipsets?

 

[Herkulese]

I am not sure that I understand the details that you have tried to cover, and forgive me if this is does not apply, but you might give this artical a read, unless you are already aware of this information.

http://www.anandtech.com/guides/showdoc.html?i=1440&p=1

It basicly involves lowering the default multiplier just incase you are trying to post at the original defult multiplier x 133 before the BIOS kicks in to set the selected Mult x 133.

 

[gtd2000]

Herkulese,
Yep - according the articles that I have read this is correct apart from the ABIT KT7A (and one of the ASUS boards) which is a completely jumperless board (for CPU settings) and will always (supposedly) initially boot using the 100FSB before changing to the 133FSB.

Using that logic - even if the CPU boots at default 10x then that should in theory be 1000Mhz.

I have tried booting at much lower multipliers but without success - perhaps the articles are incorrect (initial 100FSB) and I should try setting the multiplier with a pencil - but to be honest I'm very happy with the 100FSB (Host + PCI Clock setting) performance 😉

 

[Herkulese]

I see no reason why your CPU should not post at 133fsb, given a proper default multiplier.
Hopefully someone can shed some light on this for us.

My Duron 700 has no problem at 133 but in this case the factory default multiplier is 7 and with a 133fsb is only 998mhz, not much of a problem for these CPU's, given that you have a good HSF. If it had been a 750 or higher, I would probably have had to set a lower default multiplier with the CPU bridges, per the artical that I listed earlier.

If you truly want to get to the bottom of the issue you may want to do as the article states and try setting the bridges at a safe default multiplier for the 133fsb (one that you know you want to run at, as well as one that you know will post).

On the other hand, if you are happy with it at 100fsb, you may not want to bother.

Good luck, and if you decide to hardwire a new default multiplier with the bridges, let us know how it goes.

 

[gtd2000]

I know that the CPU is unlocked as it will run at any multiplier with 100FSB.

My old Duron 700 works perfectly in the same board at 933Mhz or even 1000Mhz using the 133FSB but is not 100% stable at the faster setting.

My problem is only specific to the new Morgan core CPU that I'm using.

 

[Herkulese]

Can you give the specs of the two Durons that you are using?

Even though the CPU is unlocked and you yave set your BIOS to run at a given multiplier, the CPU still has a default multiplier that may simply be too fast at 133. If your MoBo is booting at 133 x the default multiplier, instead of 100 x the default multiplier, for those few seconds before the BIOS takes over, your machine will simply not post.

The article that I linked you to gives the details of which set of bridges controles the default multiplier, and gives a clear chart of which bridges need to be connected or cut in order to set each multiplier. If you are lucky, you may find a lower multiplier that only requires you to connedt bridges and not have to cut any. It is a dicy projedt to cut them.

 

[gtd2000]

Yep - I'll check to see if I can change the mulitplier from 10x to 9x with the old pencil trick - otherwise I'll just leave it alone 😉