• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

XP2400+ in KT7A-RAID v1.0 (partial success)

eloj

2[H]4U
Joined
Dec 31, 2000
Messages
3,612
After learning about AMD locking new processors I bought myself an XP2400+ to upgrade my old Thunderbird 1.333GHz.

First boot went well, the CPU was identified as "Unknow CPU 2000Hz", but after booting I'd get a lock up.

I started playing around with settings and rebooting, finding the machine very hard to get to boot at all. Either the monitor wouldn't even come on, or the machine would hang after POST, after RAID-detection or during boot.

I first started playing with multipliers. Even though the processor is locked I got different results, mainly because some multipliers would make the computer unbootable (req. CMOS reset on the motherboard) and some would 'reset' the FSB to 100MHz (CPU at 1500MHz)

I then realized that the problem was the FSB. 133MHz just wouldn't work. I read that multiplier 9x would somehow magically function, but it doesn't here. I tried to search my way around to a safe setting after finding 100Mhz stable. I tried setting it to 130.66MHz (working on the hypothesis that '133' was a special case that didn't work), but that unfortunately wasn't stable at all.

So I've settled on 124MHz FSB for now, resulting in 15x124 = 1862MHz. This setting seems stable. I've played a little BF1942. I've run 3DMark'01. I've run Memtest86+ for about ten minutes with no problems.

While I'm a little disappointed that I couldn't cruise at 2GHz, it still feels like a worthwhile upgrade for this aging board. I mostly did it because my old fan was very noisy and if I were to go in there and replace it I could as well change the CPU too, seeing how cheap they are. It would be a _very good_ upgrade if you were stuck on say, and old Duron 800 or something like that.

Overall CPU performance increased of course. Vorbis encodes that once progressed at 7-8x real-time are now up to 12-13x.

I've read that you can get 133FSB and up to work by physically grounding the 3rd, 4th or 5th multiplier pin in the socket opening 5-12.5x, 13-14x and 15-16.5x for 133+ FSB 'workage'. I might try that sometime when I'm feeling adventerous.

Pictorial evidance of this upgrade.

(The 1.4GHz Thunderbird was the last officially supported CPU by ABIT on this board, and they angered quite a few folks when it was clear that they'd never officially support the new CPUs, this back before the Palomino was released and we didn't know that they'd work after all)
 
Update: I changed "CPU Drive Strength" from AUTO to '2' in the BIOS and that seems to have been just the thing, running 15x133 = 2000MHz now.
 
wow nice

I should give that a shot in my other computer.

I have the exact same board but with a t-bird 1.2@1.4 in there.


;)
 
Interesting. I have a KT7A-Raid v1.0 and I have a 2000+ pally in it. I knew that the pallys weren't supported, but I read somewhere that the 2000+ was the highest you could go on that board. The only problem with it was if you were booting it up cold, sometimes you would have to press the restart button, and then it would be fine.
 
Back
Top