1810t TME MOD

its still an advanced MOD !!!! this soldering spots are damn small !!!!
but a little easier as before

big thx to der_mali for the orginal instructions and the help by finding this out

 

Good work
Added to Timeline Tweaks.

 

By doing the bridge pre-resistor, does this not put more of a strain on R147?

 

i had some probs with random reboots but it was a ram problem.
with the orginal samsung modul modded to ddr800-CL6 i can get 1.9Ghz !!!

 

Congratulations. Your cpu has a stack of headroom. 200->272Mhz FSB should see a substantial increase in X4500 graphics speed, better if you had 2 modules running dual-channel config. If you are using Linux/grub2, you can have the overclock start right after bios bootup, before booting into the OS. See sig if interested.

 

yepp . ut2004 runs really nize 1280x768 with 6 bots mediums details on dm-antalus -> 50-70 fps

with dualchannel i geht only 250mhz stable!

i dont need setfsb @ boottime, most time i use hibernate and overclock only when its really needed.

i made a profile in my 1810tray app for setfsb

/inteks

 

My pll is SLG8SP513V,and is in TME mode too!
I hope I can crack it by using your method!THX

 

What is TME?

 

hardware overclocking protection , with TME enabled SetFSB doesnt work

 

How is cooling coping with overclocked CPU and NB+GPU?

 

no problem so far. on heavy gaming the temp goes up to 58-60°C so the fanspeed is on medium-high.

more a problem is the right memory. my old OCZ ddr800 give me random bluescreens. now i have a second samsung modul and everything work fine

and 1810tray reminds the clockspeed after resume. and creates a scheduledtask to reset the FSB on reboot. because the disk is not dedectet if you reboot whlie overclocked.

 

Hm, highest T I have seen was during 1080p playback, that was well over 70, close to 80.
I don't want to solder on my 1810tz because it is under warranty so I hope a softmod is discovered as I can't play all 1080p content smoothly on stock clocks and dual ddr2-800.

 

What OS/player/filters are you using to play 1080P? After following this and installing the latest Intel graphics driver I was able to play this.

 

splash player on w7 64bit and 151614 GPU drivers. During mkv playback, temp are not so high, but playing a VC1 1080p rip seems to cook it right up (it was in VLC if I remember correctly).

 

Splash-Player is bull...it only accelerates H.264 Videos (and only standard confirm ones) and no VC-1 videos. That information is even on the homepage of splash-player

Use MPC-HC (or its decoders), this way I have 5% CPU-Usage with H.264, 7% with VC-1 and 5-10 with XviD (not accelerated). Temps are as low as always this way and everythign plays smooth.

Also RAM-Footprint is better with MPC-HC (31MB) or KMPlayer (36MB), instead of Splash-Player (136MB!)
(Tested with a 250 MB avi-File)
Sorry for offtopic

 

I don't mind Link for the movie doesn't work btw. I will try to set up MPC correctly, tried it on my desktop and was getting worse results as with VLC and splash. You are using w7 or xp?
VC1 gpu acceleration works better in splash 1.1 I am getting 5-10% CPU util as for h264 I am getting it below 10% as well (figures are from desktop machine).

 

I use Windows 7 x64.

Just follow the guide above, and you should play every file smooth...
But Splayer wont help much on our netbooks. It just too bloated and doesnt utilize much of our GPU.

 

Could anyone upload a photo of the tme mod when it´s already done?
In the photo it says remove this? Do you mean remove the connection the the moterboard on the left side? and connect a thin wire between the 2 points?

A picture in makro of the whole mod would be great.

But it makes me wonder.. is it possible to mod the multiplier higher? change the bios or anything?

 

remove the resistor. then connect the 1 pad from the resistor (right side) with the second point

 

Ok, so im just gonna have to solder the whole resistor off? take it away?

And then solder a thin wire between the 2 points?

I have a acer 1810tz with su4100.. does it still work?

No im not planning on doing it myself becasue i don´t have the right tools, but i know someone. just need to be 110% sure that´s why i would like to have a picture

So if someone is kind enough to take a picture pls

 

Is this mod needed for overclocking the U7300?

 

Hi, does this mod work for the Acer 1410 series with the SU2300 Processor?

 

It doesn't matter what CPU you have, just the PLL (clock generator).

The mod is the same as long as you have the same PLL.

 

Ok great, but has anyone done this mod to a 1410? Just wondering...

 

Can anyone post a pic after TME mod?

 

Or does anyone know if the PLL on the 1410 with the SU2300 processor can be modded??

 

Nobody has a overclock 1410?? Bumpin this topic cos its been a week...lol

 

C´mon guys.. a little help here.. a more detaild explenation of the procedure?

It will help us alot.. i will show some pics directly after i´ve done it

 

Just look at your datasheet for the PLL, you will see that to overclock you need to first ground the TME pin.

So you disconnect the TME pin from whatever it's currently connected to, then connect it to GND.

That disables TME and you can then use setfsb to overclock.

 

CULV BSEL mod doesn't lock you to lowest multiplier?

1810 owners take note. Alienware M11x achieves it's SU4100/SU7300 1.3->1.73 (200->266Mhz) overclock by altering the PLL's FSLx pins directly. Those pins are tied to the BSEL pins on the CPU itself. Seems the CPU+chipset *does not* go into lowest multiplier lockout, as is usually the case when applying BSEL mods to non-CULV CPUS.

Meaning, if anyone is willing, can try the same overclock method by:

1. flashing the DDR2 RAM to PC2-6400 spec so has a 400Mhz SPDtable entry as described here.
2. Applying a strong pull down resistor (2k to GND) to the PLL's FSLb pin to do a 200->266Mhz overclock. FSLb is pin 64 on the PLL as shown here).

This overclock would be preferred since then the rest of the system would be calibrated correctly for this higher FSB, ie: RAM would use the 400Mhz SPDTable instead of the 333Mhz SPDtable, X4500's core and render clock speed would be adjusted by the chipset correctly.

Once overclocked with these parameters, if the TME MOD has been applied, the system may be even capable of going beyond the 266Mhz FSB by using setfsb. You may still need more voltage to the CPU for it to be stable. If can disable speedstep in the bios, then perhaps the CPU can be booted up in the lowest multiplier, stable long enough to then load rmclock to up the CPU voltages for the various dividers.

More details on M11x's overclock is here. If anyone tries it, please report your results. It would be interesting to know how far a SU4100-1.3 or SU7300-1.3 can be overclocked.

 

I'd be interested to know if this could actually work. I have the SLG8SP513V PLL that doesn't work with the TME Mod.

 

Anybody found a TME mod for SLG8SP513V?

 

So the connectors of the SLG8SP513V are different? i.e. i cannot use the mod as described in this topic to remove TME from SLG8SP513V?

Because i think i have the PLL SLG8SP513V, because the other PLL from the start post gives a PLL error when i load it in setFSB.

 

Anybody? Nobody? I would really like to know

 

Hmm, no love for the SLG8SP13V here?

According to this thread, the mod should be the same for the SLG8SP13V:

Acer Aspire One User Forum • View topic - Overclocking zg5, not easy but works.

What he describes is, in essence, changing the pullup on pin 11 of the PLL to a pulldown, same as this mod.

I will try this when I'm bored.

 

OK so I was bored today ...

Here are my findings:

- my clock chip is indeed and SLG8SP13V
- the tme mod works - you can write to the clock registers with SetFSB
- hdd locks up on "small" clock change
- underclocking is possible - slider seems to work:



- FSB mod works, but the multiplier is locked at 6.0 by the BIOS. This seems to be the only possible mod so far.



- underclocking and then moving the clock back up - computer hangs
- maybe higher frequencies possible using fast ram (ddr2-1066). I tried to increase the RAM timings using MemSet, but the CL value seems to be locked. These s at acer (I'll call them acerholes from now on) made it really difficult for decent, hard working americans to overclock their machines. Anyone know a way to reprogram the SPD in windows 7?
- removing the idiotic black strip on the fan removes the buzzing sound. Much quieter now.

 

Update: I just booted Linux to do a quick kernel compile (which is much quicker now), and /proc/cpuinfo showed this:

Code:

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Genuine Intel(R) CPU           U4100  @ 1.30GHz
stepping	: 10
cpu MHz		: 1733.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm
bogomips	: 3457.88
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Genuine Intel(R) CPU           U4100  @ 1.30GHz
stepping	: 10
cpu MHz		: 1733.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm
bogomips	: 3457.82
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

When I load the CPU in Windows (e.g. using Prime64), both CPU-Z and CoreTemp report only 1.6 GHz. So either the display is wrong or the multiplier is locked only in Windows. Anyone have an explanation?

 

Check EIST with throttlestop.

If EIST is disabled, that would mean the multi is stuck.

If EIST is enabled then you should be getting your higher multi.

If it's disabled you can try to enabled it.

 

EIST is disabled and greyed out in throttlestop. What does this mean? Obviously it's enabled in Linux, because Linux switches between 1.6 and 1.73 GHz. Is there a software to enable EIST in Windows 7?

What I find weird is, why can my old Pentium M Dothan switch between 800 and 2133 MHz in small increments while the SU4100 can only switch between 1.2 and 1.3 GHz? Seems kinda pointless to me. Does the SU4100 have other power saving measures?

Another thing, when I run the prime64 blend test in windows, the hdd light turns on and the system hangs. I can still move the mouse pointer though. The other two tests run without errors.

In Linux, all prime64 tests work flawlessly and I've compiled a kernel with no problems. What gives?

 

Do you have a datasheet for your PLL?


I'm going to send a PM to the throttlestop author about that EIST thing.

Because if it's disabled and greyed out in throttlestop, it should also be disabed in linux (I think).

 

My PLL is a Silego SLG8SP513V. 100% sure, I've read it off the IC. Here's the datasheet:

http://www.silego.com/resources/pdf/xSLG8SP513r10_07242007.pdf

Some of the 'reserved' registers are described in this datasheet:

http://www.silego.com/resources/pdf/xSLG8UM540r03_10232007.pdf

 

Can you try changing bit 1 of byte 0, that might change the source for the SATA clock.

Might as well try changing bit 2 of byte 0 also.

 

Heh, don't laugh, but I've already tried that while trying to do the soft overclock. Also tried to enable bit 7 of byte 13 beforehand. Always got the HDD freeze as soon as bit 1 of byte 0 is enabled.

 

Did you do a BSEL mod or did you pin mod the PLL?

Because if you grounded pin 55 it should not have locked out the multi.

But with a BSEL mod, it is expected to have the multi locked at the lowest value.

 

I connected pin 1 of the PLL to GND. Don't know what that's called in fancy talk

Edit: some more info:

byte 0 = 0x07 standard HDD hang
byte 0 = 0x03 black screen, reboot, and then the SATA controller seems to be dead as the notebook tries to boot from LAN. fixed by power cycling.

 

Sorry I was looking at the wrong datasheet.

Pin 64 is FS_B, I assume you connected that to GND to get a 266mhz FSB right?


The BSEL mod is when you pin mod the CPU.

I don't see why EIST would be disabled when you only did a PLL pin mod.

Do you have any bios options for speedstep or anything like that?

 

Sorry you're right, I meant pin 64.

In the BIOS you can set the date and the password and that's about it. It's made by insyde, if that helps.

Couldn't the bios check if the CPU runs at the correct frequency, and disable EIST and set the multi to 6, to discourage overclocking? And then Linux somehow reenables it, but Windows doesn't?

 

Yes in the case of a BSEL mod, but when you do a PLL mod it shouldn't be doing this.

Or at least this is the first time I've seen anyone report it on any forum.

I don't see why throttlestop wouldn't be able to enable if it's enabled in linux.

That's why I sent a PM to the throttlestop author, maybe he can tell us a bit more about this.

 

I wish I had some more info to explain what's going on but I don't. As far as I know, the bios was in charge of setting up the EIST bit and deciding whether to lock access to it or leave it unlocked. nando4 was able to modify a few different bios versions so when Windows booted up, EIST was no longer locked and ThrottleStop was then able to toggle it.

It doesn't make any sense how Windows boots up and this bit is locked while Linux boots up on the same system and the EIST bit is unlocked. I know once you are in Windows, when EIST has been locked, there is no way to change its state. Maybe when Linux is booting up, there is some secret way to turn the lock bit off.

The register that controls this is MSR 0x1A0

bit[16] is the EIST state
bit[20] is the lock bit

In Windows, bit[20] is write once so if it is cleared, you can write to it once to lock bit[16] so it can't be changed. In the processors I've tried, once bit[20] has been set, it is impossible from within Windows to clear it which makes it impossible to change bit[16].

 

Here's the MSR in Linux

Code:

# rdmsr -0 0x1a0
0000005364962489

In Windows it's 000000536C962489

There's only one bit changed, and it's not the one that should be the EIST bit.

I set the MSRs in Windows to the Linux value using Crystal CPUID, but that didn't result in the CPU switching clocks.