tualeron over 120fsb on via apollo 133 board

[advanR]

I have an asus cuv4x. It doesnt officially support the tualatin cpu's but i got one to work by modding it. I covered the 3 pins and connected ak4 to ak26 and two others(forgot).

My 1.1a would work with stability at up to 120fsb. At 124 the keyboard and system would freeze at boot up. I fixed this by disabling the option in BIOS called "dram to prefatch transaction". Or something else like that.

Now I could use the keyboard in the bootloader, but once selected the computer would freeze at the windows loading screen. No more voltage would do it. Btw, Im using windows ME. Linux would actually boot and operate fine. Thats kindof why i believe this can be fixed.

I spoke to another member named ebc about this. He had a cuv4x and got a tualeron working with it. He had the same problem but said that disabling the bios option fixed it. He was using windows XP at the time. Maybe this is why it worked for him. Hmmmm.

I have heard of this problem with other ppl too. The other users had different boards. They were all via apollo 133 mobos though.

I think the solution might be upgrading to win2000 but ill have to find a copy then. I hate winXP. Too M$ish. I dont need everyhing to be automated, thanks. I had remembered win2000 didnt work with games in the past, but I think all of those problems are fixed now. Correct me if I'm wrong.

Also, I have gotten rid of the 1.1a. My original plan was to buy a 1.4 and then just run that at 120mhz FSB. Thats 1680. A bit better than 1320. But I just saw a 1.2 tB1 for sale on ebay. So I bought that hoping to solve this problem instead. Besides, I dont want to run the pci bus at 40mhz.

The only solutions I can think of would be:
-windows 2000 would fix it
-maybe tB1 is different in a way
-different pin mod method (short and cover different pins)
-another BIOS tweak (ive tried almost everything)
-no fix! :(

Can anyone give me any help with this? Any knowledge at all may be of help. Im putting alot of effort into this, so i hope this thread won't just fade away.

I think that's everything, thanks.

[looktall]

you should have just tried jumping straight to 133 fsb.
at 124 fsb, the PCI/AGP speeds are well out of spec and i suspect that was the cause of your problems.
jumping to 133 (i'm yet to see a 1.1A that couldn't do it) will drop the PCI/AGP speeds back to spec. (33/66mhz.)

[advanR]

At 120mhz fsb the pci is at 40mhz. at 124 the 1/4 divider kicks in. that puts it at 31mhz. Ive tried putting it to 133, trust me.

[Pbl]

I also use this mobo. Do you have any detail or web about how to mod this mobo to use with tualatin core? thank you.

[advanR]

I did the exact same thing as belinassu. Instead of telling you i will give you a link to his nice site.

http://digilander.libero.it/grandecigno/Tua_BX_41.htm

A better way to isolate the 3 pins is to slide an empty ide cable sleeve over it. then carve out the socket a little so the pins will fit snug. Also, to connect the pins i just used a wire and wrapped it with a knife. make sure the wire doesnt touch any other pins or it might die.

To go over 120mhz fsb all i know so far is to disable "dram to ****** transaction" in bios. It worked for someone else, but not for me. Im pretty sure though that this is because i use winme. the other guy used xp and it worked great.

[Taisho]

i am using an Soyo 6VCA ( Via Apollo Pro 133 A ) Mobo and have the same Problem. When I set FSB to 124 my System gets instabe. I use Windows ME too.

For FSB 124 i got to rise the Vcore to 1,75 V. Any voltage under 1,75V didn't let get the System start at all !!

At FSB 133 and 1,75V the System starts quite to Windows and then prompty freeze, so I must go higher with Vcore, but it would be dangerous having Vcore abouve 1,8V.

I too have an TualCeli 1,1 GHz, I hope that it isn't the Board, because I will buy another Celi to run at least at FSB 133.

so far

[advanR]

try the bios adjustment i wrote above first. then see if you can get into winme in safe mode. or try 98se or xp/2k.

im pretty sure this might fix it. i will be trying it with my new tb1 within the week.

goodluck

[Taisho]

my Bios don't have that Bios Option you wrote above...

I am very sure that it isn't Win ME that its holding me off overclocking... because the System won't boot at all for example at 1.65 V on FSB 124 !!! hell an 1,1 Celi should normaly make do FSB 133 at 1.6 V !!!

Many ccomputer stores sold e.g. Computers with 1,4 GHz AMD Athlons on Windows ME... so ME can handle that Speeds..

[advanR]

1.1 should do 145. :)
Im not saying winme cant handle the speed. Im saying it ****s up with THIS processor when the fsb is above 120mhz.

My system before would boot fine at up to 142fsb, but i couldnt load windows. I think our boards are a little different. If i were you i would just screw around with every setting i could in bios to make it work.

[Taisho]

thx for advice, but it is proved that my cpu need more Voltage... so it cant be an false bios option... a cpu that needs so much Voltage to do less overclocking is a bad one...

[advanR]

I think you did just get a ****ty cpu maybe. how much voltage did you need at 120fsb? I could boot it at 1.45v.

[Taisho]

i did'nt try FSB 120, because the pci devider is then at 1/3.. my HDD would make trouble..

[doer]

I'm running via apollo pro 133a and it's running fine under win2k, specs below.

[advanR]

i think the powerleap adapter is different.

[Taisho]

hmm, as far as i can say the 1,1 celi is going to make make FSB 129 @ 1,80 V stable, my temps are now max ~ 39 °C

but 1,8 V is imho too much for an 1,1 Celi with Intel HSF ?

@ doer

what HSF are you using ?

btw: did anyone know how good an Coolermaster 5G11A HSF is ?

[6502kid]

I also think you got a bad chip.

Mine does 135 at 1.65v all day like a 1483mhz coppermine.

Even when I was testing it out at 138-140, I dont think I put
more than 1.75 or so into it....

[Taisho]

have you also an via apollo 133 board ?