Some Info That might lead to overclocking the 533MHz native notebooks - Page 3

Ding ding ding. That would be the way. I looked into this awhile back, but the chances of the the chipset doing 166MHz without a voltage mod are very slim, and even then you have to deal with that dinky cooling solution. I would recommend supply FS_C with the 3.3v so that the system runs at 100MHz, that way you know it's possible to modify the clock rates without damaging your hardware. I wish you the best of luck and wish I could help here, but I'm at school and my laptop is my lifeline .

wait wait wait, did you read my post? you DO need a new BIOS, you DO need new RAM, and i think you also need a new driver for the chipset. If you only have 1gb, it'd be a good investment.

You might not need a new BIOS, this is a very basic hardware change, and the BIOS might just be able to run with it. Although memory speed and it's divider is definitely a concern, I'm thinking that once pin-modded, the RAM should still force its JEDEC standard, which is 533MHz @ 4-4-4-11, and SHOULD run flawlessly. All of this is easy to correct though, right now we should just found out of there is a possibility.

Looking at the charts again, I would connect pin 42 (VDDCPU) to pin 12 (FS_A) and that should give you 100MHz frequency. If it works, we know that the pins can be changed . Anyway, I can't do this for another week, so please, Krax or someone else try this out

by new bios I'm assuming you mean a 9400's bios, if this has to be done then the 7800 might not work at full speed as that board supports the 6 cell battery and comes with a 90 watt ps. ???

I just checked dells site and the chipset drivers for the e1705/9400 are the same as the 9300 drivers

All Intel chipsets use the same installer, so I'm afraid that isn't particularly significant.

Flashing, or a new BIOS, doesn't necessarily mean we need the same as the 9400s. We're trying to get something set to 133 to run at 166. Thats different than telling something to run at 166 right away.

All I'm saying is that the one guy who did the mod, said he did something with the BIOS, with the chipset driver, and smthg with a wire on the mobo, and the new RAM.

@tentonine what do you mean by that? That they might still have different drivers?



Question: I never thought about trying to understand this... but maybe, it's time i learn a little (i doubt i can mod my comp as a pioneer- im only 17= death if anything goes broke). We're trying to connect two pins, one with electricity and one without, so that the one without does get the volts, consequently opening up (its transistor(s?) (assuming state "1", referring to binomials?). If that pin gets "1", our system is set to 166mhz? My guess would be thought that the mobo needs to know this(driver) and the entire system extra (BIOS). Therefore it's a bit risky to set it to 100mhz, since wed need a modded driver and bios. going to 166 though we'd need the RAM, since we can't run with too low RAM.

Is that right?

The 9400 may well be a different driver to the 9300....you would have to take a look at the .inf files inside the intel chipset installer to see.

Well, we're positive that they *are* different though because they have differen MOTHERBOARDS...

I am merely pointing out that, although someone above said that the chipset driver between the 9300 and 9400 on Dell's site seems to be the same, this doesn't actually mean anything.

im 14 and i dont understand a single thing here...AT ALL...maybe if i spent a few days reading and rereading it....

>>>THIS THREAD<<<

I'd just like to let you know, the i915 chipset used in the dell laptops is certainly capable of 166mhz operation, and most limit out around 260mhz without vmods. I've linked this thread to xtremesystems.org, hopefully someone can help out here.

also, i'd like to point out that ram might very well be the limit here.

I agree with the chipset and the 667mhz ram handling the 667 speed, but what about a 2.0, 2.13 or 2.26 ghz cpu 533 handling the jump without a volt mod?

Ok these questions have been answered to everyone involved in this:

1.) You DEFINETLY need 667 mhz RAM to run the FSB at 667. And yes, that is the limit, the RAM I mean.

2.) Of course the CPU would need a volt mod, but at roughly 1.4v (=my guess), it won't get much hotter than ~65°C, which is still in the green.

It'd be cool if someone could help with this . Could anyone answer my question from above? Thx ^^

well within the next week I'll be ordering a 2 gig kit and I might as well order a 667 set and try it out, only thing I might need is a modded bios as you stated earlier.

and the new driver....

Hi guys,

Been reading this thread for the first time this morning. My answer might be long, I'll be writing it as if I'm taking notes.

I am a PCB designer for a well known telecom company (my location might help you there), I know these datasheets wordings and such. I will try to help out with the interpretation of the datasheet (refered to as DS from now on).

1- I would not try to go 100MHz with the 101 setting. On Page 3 of the DS, Note 2 says this would put you in Test Mode. Nobody wants that.

2- The next pages show the register description of the device. This is set through frimware/software (bios/os) via the SMBbus interface. If you jump to Page 8, Data Byte 6, Bits 0-1-2, you will notice that these are the frequency select bits. They are READ ONLY. Meaning that no external program will be able to change those on the fly. It has to be through the pins.

3- Figure 1-2-3 on Pages 9 and 10 are the key. That is because the clock frequency pins FS_A, FS_B and FS_C are multipurpose pins. Their "setting" is only sampled in State 2 (S2) of the state machine, VTT_PWRGD# has to go low for this to happen.

This means you can't go and hold a wire to the pin. The wire has to affect the pin during sampling time.

4- All three FS pins are multipurpose. FS_A is the scariest, it turns to an output after it has been sampled. If by mistake you try to wire this pin directly to VDD or VSS (GND), when the output starts to drive it might blow, sourcing too much current. FS_B and FS_C are inputs all the time, safer.

5- We want to change FS_B from a 0 value to a 1 value. Because of my number 4 here, you CANNOT tie FS_B with FS_A.

6- Since FS_B is multipurpose but its second purpose might be unused then it might be ok to override its default 0 value. It is very likely that this pin is pulled to VSS. Pulled means using a resistor in series, something like 1k or 3.3k from the pin to VSS.

(If someone could measure the impedance between pin 16 and 29 we would know the value of the pulldown resistor).

7- If the pin is pulled down by a resistor, to inject a 1 value and override the 0 you need to pull harder, a lot harder. You could try to wire pin 16 directly to pin 1. If the pin was not pulled with a series resistor, this will short power and ground. Not good.

(Note that no intelligent board designer would connect an input signal directly to power or ground. There's too many disadavantages to this and longterm reliability would be affected.)

8- The chip is a TSSOP package. With the right skills and tools it is easy to lift a pin, I've done it countless times. It then becomes easy to solder to the lifted pin, giving it the value we want. I would prefer that approach. I'd probably grab a resistor from 1kohms to 10kohms, whichever you have. And I'd wire the resistor from the pin to VDD (pin #1).

(To lift the pin: Use your soldering iron, heat up the pad on the pcb. Use a tool with a "hook", or make a hook with a wire. Lift pin. Careful of shorting the pins next to it.)
(When I do this, it's in our lab, with microscope, dentist-like picks. Yes I've shorted countless pins, but the tools allow me to fix and view each time).


Conclusion: It is not easy if you dont have access to the right tools. I carry my laptop with me to work every day, it'd take me at most 15 minutes to try #8. Unfortunately I bought it in September and don't want to void my warranty.

I will try to answer any questions you guys might have.

Keops

*yay*

so is this mod going to be impossible to do just at home? because my bro has a 9300 1.6 --> 2.13. obivously this isn't the same pin modding as he did but is this going to be much more complicated than changing the FSB from 400 to 533?