Archived from groups: alt.comp.periphs.mainboard.abit (
More info?)
On Sat, 29 May 2004 09:17:29 +0200, Hayno wrote:
> Wes Newell schrieb:
>> On Fri, 28 May 2004 17:16:56 +0200, Hayno wrote:
>>
>>
>>>okay, let's see:
>>>i have got a 1700+ jiucb and opened the 5th L3-bridge (8x bit low>hi),
>>>to acces higher multipliers above 13.
>>>the cpu than bootet with 20*100, which is not acceptable (known problem).
>>>i than did the trick with al25 and am24 to get mapped multipliers.
>>>what i got was:
>>>7.5 boots 19
>>>8.5 boots 20
>>>9.0 boots 13
>>>9.5 boots 13.5
>>>10.0 boots 14
>>>10.5 boots 21
>>>all others don't boot because of mobile or reserved settings or other
>>>strange behavior.
>>>what i want to get is a multiplier remap to 14.5 and 15 to take the cpu
>>>to the 2ghz-limit and beyond.
>>>atm the processor runs @1.55v and 14*133 (1866mhz).
>>>
>>>the socket-mod at ocforums (online again
😉) is quite different from
>>>what i used.
>>>do you know that mod or do you know(!) how to get multipliers between 14
>>>and 19 to work?
>>>
>>
>> If you cut L3-5 and L3-4 (setting default to 15x) that will give you
>> access to multipliers from 15-24 without a wire mod. 9 (17x) will work
>> with a 133MHz FSb, but that's the only one. That's the standard cross
>> reference. Most can get it to run with the 9 setting at 2266MHz with a
>> little more vcore. If that doesn't work for you, you can either follow
>> the notes in the cross reference guide to get other multipliers that will
>> work with 133MHz FSB, OR, you can set the cpu multiplier manually using
>> the L3 bridges to whatever multiplier you want and then lock it by cutting
>> the L1 bridges. Locking the cpu allows any FSB setting up to whatever your
>> board will do. Since you're probably limited to under 145MHz for the FSB,
>> I'd use either the default 15 or 16 as a locked setting. You can determine
>> how fast your cpu will run using the default unlocked setting before
>> choosing a permanant locked setting. A 16 would probably be the best. You
>> can get 17 by default, and you probably won't have much luck with anything
>> higher than that with a 133Mhz FSB that you couldn't get with the default
>> 17 and raising the FSB a little (17x145.45=2472MHz). AFAIK, there is no
>> way to get 14-19 to work at the same time with a 133MHz FSB without
>> changing the mod around. Hope this helps. It's about all I can think of
>> right now.
>>
>
> okay, thanks again.
> so all i can get is a changeable multiplier of 17 with fsb 133?
I'm not sure what you mean here, but there's 3 choice of mods for
multipliers that work with a 133MHz FSB. Copied from website:
Just ground one of the multiplier bits from the socket (3rd =2x, 4th=4x or
5th=8x). This way I was able to boot with fsb 133 and up.
3rd pulled LO at least multipliers 15-16.5 works with fsb 133
4th pulled LO multis 13-14 works with fsb 133
5th pulled LO multis 5-12.5 works with fsb 133
The bit you want to ground depends how far your memory can take the fsb. If
you cannot complete the boot sequence with 17x133 then try lower multi with
higher fsb (not 2.26Ghz but still faster).
> everything with fsb 100 ist not worth a thought...
I don't know why not. There's only about a 3% performance hit between 133
and 100.
> i don't want a fixed multiplier because of the fixed power consumption.
Huh? Multiplier doesn't control power consumption, Vcore and CPU speed
do. With a 17 multiplier at 133MHz as default, you can just lower vcore
and FSB to 100 to conserve power.
> if there is no way to get easily changeable multipliers of (let's say)
> 14 AND 15 AND 16 with fsb 133
See above.
> i will stay at 1866mhz, which is quite good for the old
> infrastructure and way better than anything like 20*100.
2000Mhz on a 100MHz FSB will outperform 1866MHz on a 133MHz FSB in
everything except memory benchmark test maybe, which are of no real value
since 90% of memory fetches are serviced by the cpu cache.
--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
http://mysite.verizon.net/res0exft/cpu.htm
Facebook
Twitter
Instagram