NotebookForums.com › Forums › Notebook Manufacturers › Dell Forums › Dell Home (Inspiron, XPS, Studio) › Yonah has been pinmodded!
New Posts  All Forums:Forum Nav:

Yonah has been pinmodded! - Page 2

post #21 of 157
Thread Starter 
I am currently running under Ubuntu Linux as we speak, and the tool 'KSysGuard' is telling me its running at the full 2.16Ghz. Problem is, I am not 100% good at running linux, and I have no idea what to use to benchmark it... any ideas? If Linux is working at 100% right now, then Windows MUST have a driver disabling the clocking...
post #22 of 157
Wow. Simple case in point using linux to prove the windows lockdown. Just wanted to say great job on your work so far, I'm impressed.
post #23 of 157
or linux could be reading the max cpu speed.... jsut like when you right click on my computer.
post #24 of 157
Quote:
Originally Posted by Krayziepop
I am not 100% good at running linux, and I have no idea what to use to benchmark it... any ideas?
I am not to sure either but try this link. There is a link at the top of the page called "bench.tar.gz", try that. http://www.anime.net/~goemon/benchmarks.html in the mean time I'll keep looking from another tool.
post #25 of 157
Ok i think i found something of use. Try LMbench

http://www.bitmover.com/lmbench/
post #26 of 157
ftp://pi.super-computing.org/Linux/super_pi.tar.gz try running super pi under linux

Go back to windpws, us rmclock set it to max performcance 13x and the highest voltage, then go to advance and unchek every enhanced low power state, all off them, then open cpu-z again, open crystal cpu id too and use the real time clock readind to see hows the fsb and multiplier doing.
post #27 of 157
something else i found, scroll to the bottom of the page and check put the Performance section .

http://ltp.sourceforge.net/tooltable.php
post #28 of 157
Thread Starter 
I will get back to the linux thing in a bit. I am using a Ubuntu live boot disk to get in. I am backing up some files right now, and am going to try a clean install of Vista RC1, just for giggles... I will hit up the boot disk again after I get Vista installed. I wonder if there is something in the chipset driver that prevents overclocking. On Intel's website, they offer a CPU frequency tester, that shows you the 'expected' CPU, FSB and Multiplier settings, and the actual. When I run it, the program tells me that the cpu is overclocked... perhaps Intel has made software to work via that same method, which will disable the multiplier if it detects an overclocked cpu?? Wouldnt make much sense, especially for desktop systems that have an easy FSB modifier right in the BIOS... I will know here in a while, I suppose. Thanks for the links guys, I appreciate the support a ton!
post #29 of 157
Quote:
Originally Posted by Krayziepop
I am currently running under Ubuntu Linux as we speak, and the tool 'KSysGuard' is telling me its running at the full 2.16Ghz. Problem is, I am not 100% good at running linux, and I have no idea what to use to benchmark it... any ideas? If Linux is working at 100% right now, then Windows MUST have a driver disabling the clocking...
It's definitely the OS that's the culprit here. Maybe M$ slipped an update in or something.
post #30 of 157
Another interesting find here that's sure to please. I under-volted my T2250 using RMClock, and I'm stress testing it right now. 3 hours and all is good. Check out the screen shot and my current voltage.



Can you say "LOT'S OF HEADROOM ?

If we do get these processors to overclock, I think they'll be killer.

PS: 0.95V the minimum voltage available with RMClock, failed
post #31 of 157
Thread Starter 
Well, I sorta got SuperPI for LInux figured out.. lol.

Check the screenshot below, and let me know what you think about the scores. I have a feeling they are low, but I am not sure about the command line parameters, and if I ran it correctly. Thanks guys.
LL
post #32 of 157
Thread Starter 
Well, have tried Vista also. Get exactly the same results. SuperPI in vista, came in at 57.643 seconds for one million digits of PI... Cant use NHC in Vista (havent tried very hard but it bluescreened once, and that was enough...) Sandra benchmarks are the same in vista, and also show the 6x multiplier being stuck on...

Looks like maybe this is a hardware issue after all? I am not sure what to try next now, lol. Been at this all day today and most of last night. Kinda aggravating, but this is not the first time I devoted a TON of time to something like this... Guess that makes me a devoted nerd/geek dont it!
post #33 of 157
well if there is anything we can help you do or research let us know. I for 1 would love to see this work, so i can take advantage of it and crank up my Yonah.
post #34 of 157
Thread Starter 
If you are talking about the T2400 in your M90, you will be out of luck. The T2400 already has a 666Mhz FSB speed. This method will only work on the T2050 and T2250, as they both run on the 533Mhz FSB. I am still researching for an answer, but its not looking good so far. I am running out of ideas now, and time. I have to have my puter back together for work on Sunday night, so if I haven't solved the mystery by then, it may go unsolved. You guys have all had really good suggestions so far, and its been helpful having the community behind me on this. Thanks again!
post #35 of 157
Is there a pin that you missed? Lets think for a minute, the pin identified the FSB, before you had more multiplier options now you dont, so the multiplier information had to be modified too, since the only difference was the pin mod, these means that the pinsa carries that information too, maybe it has to isolated from the core but still be there....
post #36 of 157
on the 3rd table wjat means "reserved"? i think you are running 666 low and you should dofy a pin to run in high.... that is what i can read from the table, but what pin must be modfied? have you tried cutting the 3 ins and then tried different comninations of pin / no pin?
I thnk that bsel1 in the 2050 is just there but not functional, and that is becuase you are running on low, .... maybe i am just not understanding the table, what about bpm bro0 and bpri pins? they have something to do with clocks, but the problem here is the multiplier, so maybe the COMP pins can be tthe problem bacuse they are responsable for power.
post #37 of 157
try cutting BSEL 0 to force the multiplier to high. (pin precense means L (low), so just make it stop functioning, bacuese its normally being set on a virtual level (speedsteplevel), so removing it fools the chipset into thinking that its being set to high.
post #38 of 157
Thread Starter 
Well, BSel0 is already HIGH. Its high on both 533 and 667 chips... To make a HIGH signal go LOW, you must lower the resistance. This is what we had to do with the Dothan chips. It was simple then, as all you had to do was short the socket out to a nearby ground pin. My case is that you have to make a pin the has low resistance now, have HIGH resistance. Well, by wrapping the pin in plastic, the resistance is basically infinity, because NO voltage can get through the pin... I think maybe though, some voltage still has to get through... unfortunately, the only way that you could get the exact same resistance would be using a resistor of the proper impedance to make it that way... hmm... I just had an idea. Gimme a few and I will post back... this may just work.
post #39 of 157
i am telling work with the bsel 0 its on low you need to make it high with the bsel1 on high too, its a double pin mod. I think the scores on linux are nromal,.... try it again under windows. Use the rmclock settings i told you to.
post #40 of 157
Thread Starter 
Here is the chart I am talking about...



With both 133Mhz FSB and 166Mhz FSB the BSel0 pin is already HIGH. I shouldn't have to touch that pin at all.. I just tried a couple other things that didnt work (wouldn't boot.. got lots of beeps and errors, lol...) I figured since BSel0 was already HIGH, maybe I could short BSel0 and BSel1 together on the socket, yet leave the BSel1 pin insulated... this did nothing. Then I tried it the other way around. I shorted the BSel0 and BSel1 pins together on the CPU, and left the BSel1 pin insulated with the same result... I can't think of any other logical connections to make... I sure wish I had some way to control the resistance of that BSel1 pin... I still think that a certain amount of voltage has to leak into the socket from that pin to funtion properly... I may be wrong though, as I said before they accomplished it on the Xeon processors with this exact pin insulating method..

lol.. guess I am glad I didn't go crazy and clip that pin right off. I would be stuck with a 1Ghz Core Duo until next month!
LL
New Posts  All Forums:Forum Nav:
  Return Home
NotebookForums.com › Forums › Notebook Manufacturers › Dell Forums › Dell Home (Inspiron, XPS, Studio) › Yonah has been pinmodded!