Overclocking the Sager NP9260 ( D901C )

Kozi,

Can you run this ??

http://www.esupport.com/global/index.cfm?refererid=52

This company does work with all of the different bios developers..

If you run there utility.. If you run it and give me the info.. I will go to them to see if they have an update or could update that version...

Its on step 2.. Small executable and looks pretty safe...

Thanks,

joe

 

You can see the Q6600 datasheet from Intel here:

http://download.intel.com/design/processor/datashts/31559206.pdf

On page 27, table 16 you'll see the pin voltages for determining FSB frequency. So shorting BSEL2 to VCC you'll enable 333 FSB base freq.

On page 40 you can see the pinout footprint. BSEL2 is at location G30. The pin they short it to in the OC post is J30 (although you could also short to K30). This would force BSEL2 "high" and enable FSB1333 detection in BIOS.

Pretty nifty -- I guess all it took was for someone to actually read the data sheet .

 

yes im reading it now

 

Kozi... Are you getting balsy????

I really can't wait to get my new laptop..

Not sure if I will try as soon as I get it...

Joe

 

The problem acording to the thread might be the BIOS or the motherboard chipset. That is, even if the BIOS detected the 1333 FSB, the standard voltage needs to be enough to power the thing. Otherwise it might nor even post as I guess we can' change it throught the BIOS making the CPU unusable for the purpose if conductive paint is used (can't be erased?). I heard that a good way to try is insteed of using a conductive "paint" is using a carbon pensil that could be easily erased but I honestly don't have ebough knowledge in electronics to try it out myself and diagnose any problem in case (mine hasn't even arrived yet).

Stay cool,

Trance
PS: Increasing the FSB to 1333 would in theory make the CPU work at 3Ghz (Q6700). Even if the system worked at startup I doupt that d901c has enough thermal leverage to deal with 4 cores running at that clock speed. Now for Q6600 it would work at 2.6Mhz (Sweet a cheap Q6700!), far more acceptable but don't know.

 

Lol i'm lost i dont understand the mechanics of it but i follow directions well lol

 

You could 'scrape' the conductive paint off if the 1333 FSB doesn't boot. The paint is similar to that found in a car rear defroster repair kit. Since the paint is at the edge of CPU it could be easily scraped off with a small blade. Not scraped from the pads of course... that wouldn't be safe. You only need to break the connection to restore the 1066 FSB.

I tried using the PLL tools last night. Not much success at all. Most don't even run in Vista 64. SetFSB functioned and had the 954227 PLL. However it locked up the computer as soon as I tried it and the LCD went blank. I haven't given up on it since I think you can somehow lock/unlock the LCD clock.

What I didn't like is the memory bus was tied to the FSB clock in SetFSB. You can't OC the FSB base to 333 without OC'ing the memory (according to setFSB). That worried me a bit.

 

ok you guys are WAY past me good luck

 

Well, that may well happen with the hardware mod also. As far as I suspect usually both CPU Clock, Memory and FSB are linked unless the BIOS straps them (that is changes on FSB don't change memory speed and so on) but I doupt it as it is indeed usual.

Trance

 

Interestingly enough those 3 CPU bus selection pins route to the ICS954227 chip. Specifically pin 53 on the PLL is the one that needs to be pulled high to VCC. So you could either jumper the CPU or short pin 53 on the PLL (assuming that shorting a pin driven high by the CPU to ground will not damage it -- but that's what the CPU jumper fix does)

 

I tried the 333 FSB Mod on my D901C with a Quad 6700. No luck unfortunate. Goes till bootup screen. When loading Windows, PC resets. On bootup it still shows 2.66 Ghz.

Adoe

 

Can you post some pics showing your modification?

It's likely this mod will not work on a Q6700 because the multiplier is 10 (instead of 9 for the Q6600). So the result is your Q6700 will be overclocked to 3.333 GHz. That's really pushing the limits and I'm encouraged by the fact you booted at all.

When doing the mod on a Q6600, the result is overclocking to 3.0 GHz. A number a lot of desktop OCers get with the E/Q6600.

Did you remove the mod or are you still running with it?

 

I removed the mod. I just made a bridge usinge a wire on the pins beneath the cpu.

Adoe

 

If it boots at normal speed means that the mod is not applied correctly as far as I've read. I wish someone connected the pins properly and then posted some result.

Good try anyway.

Trance

 

Well I looked at the mod and it is interesting.. I am tempted to try it but the problem is the memory and the fact that I have the old 9260 mobo with 1066. Even if I had the 1333 Mobo I doubt it will work because it will overclcok the memory and I doubt that the memory will run at 333. Maybe my bios will allow 1333 (only one way to find out..huh?), which brings me to believe that maybe if we could have RMClcok, through a register edit, drop the memory frequency to 667; shut down the computer then do the mod, it might just work. Now I am no authority on RmClock but Zodttd is and maybe he can help in that area. I will be willing to try the mod on my E6700 if we can somehow get the Ram to run at a lower multiplier.

Another thing; there was an Intel mobo that had zero options in the bios (kinda like ours..lol), but if you were to short 2 pins where the CMOS reset pins are, it will boot up in a trouble shoot mode with access to all the BIOS goodies. R&D and Tech Support use that mode to find out the limits of the mobo and other components. I am wondering if there is a mod like that for our mobo. Some where the R&D boys at Clevo have to have an option like that to be able to test the mobo.. or maybe they just don’t want to give us the REAL Bios that they use for testing..

Oh well it is time to hire a BIOS hacker, if only I could find one..

And the quest continues..

 

I'm going to map the PLL register settings with SetFSB and compare the values to the document Zodttd provided.

Rather than use the easy sliders on setFSB, it may be best to manipulate the registers directly. There are some LCD specific registers. I hoping to find some sort of LCD clock "lock" since the display wigs out as soon as we try and tweak the other clocks.

 

If you attempt the modification, run setFSB afterwards. You can go to the "diagnostic" tab and see the PLL registers.

Register 6 shows the three bus selection pins from the FPGA. The low order 3-bits show the value. For no mods the last three bits should be zero.

With the modification, the bottom three bits should be 100 == 4. Just convert the register value to binary and it should be: xxxxx100 (where the x's are "don't cares").

 

Thanks for the info Kozi. My only concern is that if I do the mod and the memory does not like the fsb it might not let me boot to Windows. If I do get to Windows then I'll adjust the settings like you mentioned. However I will be away for 10 days. I'll play with it when I get back. If nothing else it will be fun trying and try I will.. The other thing to work on is the LCD. It locks up on me too as soon as I adjust the values..

 

The memory clock should be separate from the FSB clock. The FSB is dedicated between the CPU and the North Bridge. The North Bridge chip interfaces with all the peripherals including the RAM (in dual channel mode using the RAM clock).

The PLL will set the FSB based upon the three bus selection inputs. It doesn't change the RAM clock just because your FSB base clock is now 333 MHz (otherwise how would the 1333 FSB CPUs work).

So it's mostly a question of getting the mod to work as well as hoping your Q6600 runs at 3.0 GHz.

 

I've mapped out the registers using a nifty excel spreadsheet I made (it breaks down all the register values and hilights which settings are enabled/disabled).

Took me a couple hours to do. Unfortunately it didn't yield any success in trying to overclock the FSB. I was bummed to find the LCD clock was already disabled for M/N adjustment. For kicks I tried enabling it which quickly blanked out my display and forced a hard reboot.

I'm a little frustrated with trying to change the PLL register. I'd like to try the mod to the Q6600 but it would be nice to know if I can even run at 3GHz first.

 

Ok, I gave it a go with my Q6600. It took me a little time to make the mod. I used a fine gage wire (actually a single strand from a 22 gage stranded wire). I tapped the wire onto the two pads using on of my soldering stations.

Everything went smooth... but damn I have shakey hands. I guess that happens when you approach 40?

Good news: The mod works and my core appears as 2.99 GHz in the system properties of windows.

Bad news: My Q6600 is not stable at that frequency . wPrime fails half way through the 32M test.

A bit of a bummer for sure. Too bad I can just OC it a little using the BIOS. That would be nice. I removed the mod and I'm running at stock clocks again.

I guess we can sum it up as follows:

1. The mod works but your Q6600 may not be stable
2. If you are going to buy a 9261, pick the faster CPU for now since you can't OC it without the mod

 

Kozi...

Thanks for trying!!!!! Sorry it didn't turn out like you planned...

I have the Q6700 and likely the box will be overl**** the cpu too high...

I wonder if its the actual memory because your raising the fsb that can't handle the change??

Anyway.. Thank for trying...

I still haven't heard anything from the BIOS company... Looks like thats probably not going to work...

If only someone would give us a good bios update......

I guess we can't have everything

Joe

 

Hey Kozi... What are using to watch core and hd temps?

I am running vista x64... I have been using speedfan...

Joe

 

Use Everest Ultimate to monitor GPU, CPU, HD temps.

Greetz...

 

I'm using the RivaTuner Monitor. The cool part is it will overlay the information in any OpenGL or DirectX created window.

 

Everest shows a +9 degree temp diff from SpeedFan....

I did notice Rivatuner and Everest show the same temp for the GPU's..

Now I am not sure what to go with....

Is Everest reliable for CPU temps??? I have seen some posts saying that it is usually off...

Joe

 

Everest can monitor the dye temp and the outher temps of the cpu, also known as mainboard temp. Speedfan will only show you the outher temp, monitored from the mainboard sensor.

 

I didn't try raising the CPU core voltage. This isn't settable in BIOS so it would have to be one of the software based tools.

The downside is temp/power dissapation is a quadratic relationship with core voltage. It would be pretty stressful to the system to raise core voltage.

 

Here's my problem


SpeedFan gives me each core value.

Core 0:27
Core 1:27
Core 2:25
Core 3:25

So I have it configured in the taskbar to give me the highest value of each.


In Everst, I get this

CPU: 38
Core 0:42
Core 1:38
Core 2:38
Core 3:37

Both values are running at the same time and my max fans is turned on.

Which one do I go by?

Joe

 

The coretemps. The CPU temp is monitored by the mainboard. A sensor nearby the CPU monitors the temp. The coretemps are monitored on the dye.

 

I understand that...

But my problem is which one has the correct core dye temps?


Joe

 

4 cores, 4 temps.... simple....

 

Do you not get it?

SpeedFan gives me 4 different values than Everest does...

Which one is correct...Everest or SpeedFan...

Is that simple enough for you?

Joe

 

That's funny. When I tried it with both tools, I get the same temps in both programms.

 

My temps are 7-10C Degrees of in the 2 programs, Everest runs hotter. I checked the GPU temps back to the Nvidia monitor and they were reading the same. So I am thinking that Everest might be closer. If I get a chance I will look around for another program to check with.

 

I haven't had a chance to look around much, but if you want to make speed fan read the same as everest you can change the offset. Click on the configure button, then go to the advanced tab. In the drop down labled "chip" select "intel core at $0 on ISA" (my only option). Then select the core you want to set the offset for, then in the drop down labled "set to" change to ""corect"" value.

RIght now I am thinking everset is correct just based on the GPU reading. I have had the same reading for the GPU in 3 programs so I am confident it is correct.

 

I knew about the offset change...

I just wish I could confirm which values are the correct ones....

Looks like I might have to check a couple other programs first..


Joe

 

I was looking around last night and found and found coretemp, but it doesn't play nice with vista. Not WHQL certified driver or some crap. There is a "fix" for it but I haven't tried it yet.

 

I just found this program. I'm going to try it out tonight.

 

SetFSB is out again?? Attempting to download now. Thanks!

 

Ok got it downloaded. Just a warning though.

Warning !!!
If you are a beginner, do not use this software.
This software is for power users only.
Use "SetFSB.exe" at your own risk.

This can and does change some things accidentally. I had it change my raid settings. So be careful.

 

Your right overclocking is nothing to play around with.

I found the newest version 2.0.b.18g.

 

I was playing with yesterday and I got to the point I could read the information. But every time I tried to write back it would hang and give a white screen. I am considering pulling a video card and trying again to see if this helps. I was thinking it might have to do with SLI setup and it getting hung up there.

Any thoughts??

 

bump
The folks the the RU have been able to OC their CPU.
There has to be away to do with with the d901c

I will be getting mine this week and would love to find away to do this. with that extra byte or whatnot. we should revive this and figure something out.

this thread is going in a great direction and we should keep it up.

 

Yep, I discovered the PLL in the D901C . I was tired of all the guessing en trying to discover which PLL should be in the Laptop. I opened the case of my 9261 and there was nothing to see on the backside of the mobo. Well, the PLL must be on the inside of the laptop. Whoala.... there it is.... The ICS9LPR363ELGF. Unfortunate there are no programm's to support this PLL. I have tried several parameters, but no luck .

 

same crap with my 1710 dell. they will never code it into the programs.

not used enought. and too unique

 

I'm busy with the creator of SetFSB to make this PLL work. Be patient everyone. I'll hope it will succeed

 

same with the peeps with the 7600 non G for a year. and nothing came out.

 

Hop you succeed Adoe, that would be amazing for us Q6600 owners. If you need a hand just shoot as I have some dev skills.

Trance

 

I am waiting for a reply from IDT. I requested the datasheet.