[Acer Aspire 1410/1810t/1810tz] Timeline Tweaks (2)

Unselecting "Intel Rapid Memory Power-Management" in the graphics drivers settings might help.

Use SLG505YC264BT.

5-5-5-18 won't go very far when overclocking, but let's talk about that later. Try the first two steps and report back

 

Thanks for the suggestions...but no luck.

Even if I move the slider just one click (from 447/760 to 478/760), the system will almost immediately lock up. Bigger moves (to 531/760, which equals 233.1MHz FSB) lock the screen in a blizzard of diagonal color stripes.

Any ideas what's going on here???

Other details - I'm running Win 7 x64 (Home Premium) with the latest drivers - do I have to do anything special with SetFSB for x64? And I use RightMark to undervolt (although I've tried resetting the voltage back to the original default of .9000).

 

What happens if you just click on Get FSB and then Set FSB without changing anything?

 

For anyone interested (or brave enough) to install the second pci-e adapter, I have a few observations. First, there is no power on pins 2 and 52 - normally these pins are at 3.3 volts. So, we'll have to patch in voltage.

Second - it's not a full pci-e port. Only the USB signals, sim lines, wlan led line, and voltage and ground are brought out to the slot. Clearly the second pci slot was only ever mean to support a hsdpa card of some sort.

And for those interested in the sim tracings, there's no voltage there either.

 

thanks! i'm going to order it

 

Bad news - system locks up within about 5 seconds.

 

The module in the pictures has a 8 pin cable. the 1410 only has a 6 pin connector. I dont see that module working unless the picture is incorrect on the auction. Anyone know of a cable source?

I ordered a 3810 module by mistake that looks just like the one in the picture and does not work. The module seems to fit perfectly, but the cable wont work. Does anyone know the pinout. If they do, I will probably just solder in a cable.

 

You should click on diagnosis and save a screenshot of the register settings. Then click on Set FSB and quickly make another screenshot before it freezes and compare the two screenshots after reboot. Maybe SetFSB changes something the system doesn't like. There are other ways to overclock by accessing the registers directly. I'll post something tomorrow, I've got to sleep now.

 

This is right.
But you can't take a screenshot, so use a camera.

I had this problem. You can read about it in the thread in my sig.

Basically I found that my system locks up when setfsb changed the source for SATA clock from SATA = SRC_Main to SATA = PLL2.

For my PLL it was bit 1 of byte 0.

I suggest you also try changing the source for the sata clock to see if that locks up your system.

Then you can send a quick email to Abo (creator of setfsb) and he will give you a test version that will leave the source for the sata clock alone.

 

Here's the exact Ebay one that I bought. It's a 5pin cable. The cable's a bit long since it was meant for another model but it fits and works perfectly.

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=250380682726&ssPageName=STRK:MEWNX:IT

 

Which guide did you follow, i coul'dnt find one.

 

thanks. can you again confirm that exactly this one has 5 pin cable and works with 1810t?

 

@SANdood
Here are the instructions how to overclock by editing registers directly.
More possible values in the table on page 4 of this document(although the next step is 266MHz and wont work):
http://www.silego.com/resources/pdf/xSLG8UM540r03_10232007.pdf

 

7.15.10.1908 (Vista) and 8.15.10.1892 (Win7).. Noticed your results, the total opposite of mine. Strange.


Another "problem", more like a glitch.. BatteryBar worked 100% for a day or so, now it's showing numbers that are totally off.
Right now I have 2h 34 min of battery left according to BatteryBar. At the same time the mouse over tells me I have 28 805 mWh left and is currently discharging at 5 800 mW/h. Im not a math genius, but 28 805/5 800 is close to 5h, not 2h 30 min.
It's not "correcting" itself over time either, just counting down veeery slow, like every BatteryBar-minute is two minutes IRL. "Full Lifeteime" is around 6h 30min, no matter how much i stress or idle the computer.
Anyone else experienced the same? The program is generally great, but right now totally useless.

 

@der_mali

Attached is a screenshot of SetFSB just after GetFSB. Note that register 14 doesn't seem to contain ANY of the values you describe.

@moral_hazard

My symptoms are exactly as you describe in that thread- my HDD light locks on for several seconds then BSOD. Is the bit in question (for the SATA PLL) bit 0 of PLL Control register 0 (0x41)? - and you say it should STAY 0x41 when I SetFSB it?

And my apologies and appreciation to you both - I am obviously a noob here (I last overclocked an 80386 back many, many years ago when life was simpler and CPU speeds were measured in MHz instead of GHz). Still, if we can figure this out, it will likely be helpful to others with the same PLL. That said, I fear @abo will classify me NOOB if I as for his assistance.

 

@SANdood
Register 14 can't contain those values yet because you didn't set them yet
Currently it is set to 200fsb(bit3 is 1). Bit0 and bit1 don't get changed. Bit7 is for allowing software overclocking and bit6:2 are the fsb bits. Just do it like I describe in my last post and report back if it works.
If it doesn't it might be a smbus problem.

 

Yes either do as der mali said, or you can do what I did on my thread:
Try to overclock, when it freezes use a camera to take a photo of the registers in setfsb.

Then after the notebook restarts, just manually enter the values in the photo you took with the camera. Except do not change the source for the SATA clock.

Then hit apply and hope that it doesn't lock up

 

@moral hazard
With directly changing fsb I want to determine if the SMbus is the problem here. If it still locks up, we can stop finding a solution. If it doesn't lock up, checking the other register settings SetFSB changes is the next step.

 

ok, I see.

 

@chilko
http://cgi.ebay.ca/ws/eBayISAPI.dll?ViewItem&item=230381030584. This is the one that I bought. Exactly the same as your auction, same vendor, same write up, same pictures - just a bit more expensive becuase I bought it two weeks ago. Yes, it does picture an 8 wire to 8 wire cable, but it comes with the 5 pin cable. I am sure that the picture is stock and simply a reference only. All the ACER models he quotes as compatible have a five pin mb bluetooth connector.

I guess if you're really concerned, a quick email could confirm the correct cable, but initially I went with the title of the auction and the picture of the 1410/1810 mb that clearly shows the five pin mb connector. And again, mine installed without a problem. It came with the correct cable (although auction does show the wrong one). Windows Vista even recognized it as an ACER Bluetooth Module... though I did have to then download the drivers from the link the auction provides.

 

@der_mali

I was able to set Register 14 to A9 (206MHz 10101001). When I Apply, SetFSB reports that the frequency changes from 1397.2MHz to 1440.0MHz. Unfortunately, CPU-Z seems to lock up and doesn't report a change...and while I can still mouse and even use Aero Peek, If I do anything that touches the disk, it seems not to respond...I eventually had to power off/reboot. But it didn't seem to lock up as hard as before.

Screen shot attached.

 

@SANdood
I very much think that your system doesn't like how SetFSB accesses the SMBus. I did some tests on my Aspire One a few months ago and tried RW-everything to change PLL registers. In block mode it wrote zeros to many other registers beyond the PLL registers and killed the system. I even had to take out the battery to be able to reboot then.

I suggest that you reinstall SetFSB because the binary sometimes destroys itself when overclocking locks up the system and then try the 206MHz setting again. If it still doesn't work I advise to install a 32bit OS on a second partition or so and try again.

Another thing that makes me wonder is that your SMBus I/O register value at 06h differs from Cusem's for example, who has a SLG8SP513V.

You should reopen your 1410 and check the PLL markings first before you continue fiddling with overclocking.

 

@SANdood
Wait!

Redownload SetFSB and check Register 06 of "SMBus I/O registers". If it is still 41 click on it, put 03 in the "Hex" field and click "Out". Then try overclocking again.

 

I reinstalled SetFSB, and found that my SMBus register 06 default was 0x00. Tried setting PLL register 14 to 0xA9 again - same lockup/BSOD. Restarted, set SMBus register 06 to 0x03, clicked Out, then set PPL register 14 to 0xA9 again, and exactly the same results.

In every case, the moment I click "Apply", my hard drive light locks on hard, and stays on until I get the BSOD.

I won't be able to pull this thing apart today (I'm visiting friends to watch a football game).

 

Thanks everyone & especially der mali for all of the great tweaks here. What an awesome resource.

Additional data on flashing the RAM - I ordered an additional 2GB 667mhz Crucial RAM from Amazon along with my 1410. Turns out it's Samsung RAM with a slightly different model number than the original stick.

Original: Samsung M4 70T5663EH3-CE6
Crucial: Samsung M4 70T5663CZ3-CE6

I followed your instructions for both sticks and was able to flash both of them successfully using the same SPD dump (Samsung M4 70T5663QZ3-CF7). Might be helpful for anyone who buys the same stick of RAM.

 

@SANdood

I think it has nothing to do with the SMbus.
I think you should try to change the source for the SATA clock and see if your system locks up. If your system locks up from just changing that one bit, then it should be simple to solve.

Please try my suggestion.

 

I can confirm that I've done exactly the same thing with the Crucial Ram, and it works fine. I wish I saw a real difference in speed though.

 

When he sets the FSB via register 14 nothing else is changed. The source for the SATA clock stays at default. The SATA clock might only change when moving the slider to overclock

 

Yes I know that, but my suggestion is more simple because it is only one bit to change.

It takes one second to change bit 1 of byte 0, and you will imediatly know if the sata source is the problem. Which I really think it is

 

It will lockup when he changes SATA source. It even locks up when he presses Set FSB without touching anything. If it's an SMBus problem it should lock up whatever he does

Edit:
I don't know if RW-Everything works on Win7 x64. It would be interesting to check if it works with RW-Everything when accessing the SMBus in Byte-mode to change register 14 but that wouldn't work via remote support.

 

When you press setfsb (even without changing anything) it will still change the source for the sata clock. I know this for a fact.

Check on your system, just press getfsb and setfsb and you will see some of the registers change even though you don't overclock.

I am 90% sure this has to do with the source for the sata clock. That is why you see the HDD light go crazy

Here are my instructions:
1. press getfsb.
2. change bit 1 of byte 0.
3. press update.
4. press apply.
5. do not press setfsb at any point!

You should see the system lock up.


Now try this:
1. press getfsb.
2. change a harmless bit for example bit 0 of byte 4.
3. Hit update and apply.
4. The system should not lock up.
5. this will prove it's not an SMbus issue

That is an easy way to test who is right

 

That's the reason I asked him to change register 14 and not to overclock via slider. Check SANdood's screenshots, the SATA source didn't change

It's not about being wrong or right, but it's about drawing the right conclusion

 

Yes, and you see it didn't lock up like before.

You can't just change the M/N programing registers and expect it to work.
You need to change more, otherwise you get lockups.

Look, if it was an SMbus issue then he would not be able to change the bits.
Or at least that is what I have found.

Basically the steps to take are:

1. Press getfsb.
2. move the top slider.
3. press setfsb.
4. before the notebook restarts, take a photo of the registers with a camera.
5. After it restarts, enter the register values manually leaving the source for the SATA clock alone.
6. hit apply.

The notebook should not lock up and you should have it overclocked.

After this, send a quick email to Abo. Ask him for a test version of setfsb that doesn't change the source for the sata clock.
Be polite in your email or he will not support you. Lots of users get "you are not polite, I do not support you" from abo.

test the test version when you get it, if I am right (and I really really think I am) then the test version will work perfectly.

 

And I forgot this:

Try using my PLL in setfsb, because it doesn't change the source for the sata clock. The PLL is ICS9LPR501SGLF.

I didn't check if we have the same MN programing registers, but it shouldn't hurt to try.

 

It did lock up, that's what he wrote, if I'm not mistaken
Register 14 is not a M/N divider control register. It's a unique Silego feature that let's you change FSB. SetFSB uses M/N divider control and changes sources so that's why I suggested trying this alternative.

The SMBus connects many more system devices than only the clock generator. If it isn't opened and closed correctly it might affect other system communications.

IDT and Silego clock generators are not compatible so this won't work. And again Byte0 is 41h both before and after changing Byte14 so SATA source definitely is out of the question.

 

Sorry I missread it.

I thought he had the idt chip.
I guess I made another mistake

 

Another nice sleeve which fits perfectly: Dicota 11.3

 

@ATH
Thanks, added

 

With all the trouble SANDood is having, isn't it possible the technician screwed up the unlock?

@der_mali: most if not all of us who have unlocked TME according to your post aren't having a problem. I gotta' think that either SANDood has a completely other PLL (unlikely), a problematic motherboard, or a bad unlock.

BTW 1.7GHz here following your post without a problem.

 

So today I got my brand new AS1810T
Thanks to this awesome thread, it's time for some tweaking. I've got the 3GB version and according to CPU-z the 2GB module is M4 70T5663EH3-CE6 and the 1GB module is M4 70T2864EH3-CE6. So the 2GB module is the same as in your guide, so now I just wonder if the 1GB module should work if I choose M4 70T2864QZ3-CF7 in the Thaiphoon database as said above in your quote. No one who got the same 1GB module as I and tested?
I saw the post you wrote about restoring a module if the flash went bad, so I guess I could try, and revert if it fails?

 

I guess it's possible, but before I had it unlocked, I was unable to effect ANY changes with SetFSB - nothing would happen if I tried.

 

Nice to hear that it worked for you

I think that SANdood is the first with an Silego PLL who did the unlock so it might not be a bad unlock what is causing this. We'll find out.

Congratulations
You would be the first to test it so this is new territory. Restoring a module worked for me, but hotplugging a RAM module is a bit out of specification lol

 

Ohh...new BIOS on Acer website today, 3120. Wonder whats new

EDIT: Yay, I successfully flashed both the 1GB and 2GB modules, so now I run my 3GB of RAM in 800mhz!

 

visually I did not find differences in the new BIOS setup

 

I don't understand why Acer doesn't provide any changelog for new BIOS versions :/

 

is it bad to continually flash your BIOS? Like for every new update

 

I'm still on stock v3113. So far I had no bugs that bothered me, so I didn't feel the urge to flash my BIOS, yet.
There is always a certain risk involved when flashing a BIOS. Personally I principally flash in DOS mode. I'm kind of old school and don't trust Windows BIOS flashing (yet).

 

It's going to be a few days before I get to pick this little overclock challenge back up. I'll probably pop open the case next and verify the PLL model (and visually inspect the unlock). But it may not be until the weekend.

Thanks for all the help so far!

 

For those of you looking for a case rather than a sleeve, here's one I got. It fits perfectly (zipper scratch safe), and has additional pocket for both AC adapter and car charger, and some other goodies...

11.1" Netbook Fitted CaseCrown Double Memory Foam Thin Netbook Case Bag With Front Pocket(Black) at Amazon.

Cheers!

 

Anyone already tried a 4 GB so-dimm? I recall someone mentioned the chipset does support it. Wanted to do it but the modules are bit expensive, hence the q.