*HP HDX 9000 DRAGON Owners Lounge, Part 2*

Discussion in 'HP' started by 2.0, Sep 3, 2010.

  1. RickiBerlin

    RickiBerlin Notebook Deity

    Reputations:
    609
    Messages:
    979
    Likes Received:
    18
    Trophy Points:
    31
    Sorry, I'm still looking at.
    I could not even find the fan control.
    As seen in F.41 are the same values​​. Now, however, under C328. (in "F.35E"it was C327)

    There are however plenty of other changes. I further testing.

    "F.41 original = dsdt_8510x.dsl"

    See here is an excerpt:

    Code:
    Name (C327, Package (0x02)
            {
                Package (0x07)
                {
                    0x0AAC, 
                    0x0BD8, 
                    0x0C3C, 
                    0x0CA0, 
                    0x0D04, 
                    0x0D68, 
                    0x0DCC
                }, 
    
                Package (0x07)
                {
                    0x0C0A, 
                    0x0C6E, 
                    0x0CD2, 
                    0x0D36, 
                    0x0D68, 
                    0x0DFE, 
                    0x0E30
                }
            })
            Name (C328, Package (0x05)
            {
                0x64, 
                0x46, 
                0x3C, 
                0x2D, 
                0x14
            })
            Method (C329, 0, Serialized)
            {
                If (LGreaterEqual (\_SB.C04C, 0x02))
                {
                    Store (C326, Index (C325, 0x01))
                }
                Else
                {
                    C32A ()
                }
    
                If (LEqual (\_SB.C04C, 0x05))
                {
                    Store (C327, Index (C325, 0x01))
                }
            }
    
            Method (C208, 1, Serialized)
            {
                Store (0x00, Local0)
                C32B (Local0, 0x00)
                C32C ()
                If (Arg0)
                {
                    Notify (\_TZ.TZ1, 0x80)
                    Notify (\_TZ.TZ2, 0x80)
                    Notify (\_TZ.TZ3, 0x80)
                    Notify (\_TZ.TZ4, 0x80)
    Thank you "nando4"
     
  2. 2.0

    2.0 Former NBR Macro-Mod®

    Reputations:
    13,368
    Messages:
    7,741
    Likes Received:
    1,022
    Trophy Points:
    331
    PLL TME-UNLOCK FRONT SIDE BUS/CPU OVERCLOCK:


    TME unlock of PLL ICS 9LPRS501PGLF


    What you possibly stand to gain:

    Installed ProcessorStock SpeedFSB O/C'd to 245Mhzw/ Dual IDA Enabled
    T95002.6 GHz @ 13x3.2 Ghz @ 13x3.4 Ghz @ 14x
    T93002.5 Ghz @ 12.5x3.06 Ghz @ 12.5x3.3 Ghz @ 13.5x
    T83002.4 Ghz @ 12x2.94 Ghz @ 12x3.18 Ghz @ 13x
    T81002.1Ghz @ 10.5x2.57 Ghz @ 10.5x2.82 Ghz @ 11.5x
    X=CPU max multiplier.​

    What you'll need:

    • SetPLL v.1.0e4-HDX Best tested version.
      Includes PLL lut files HDX9000.lut and ICS9LPRS501PGLF.LUT
      With FSB clocks from 200-265mhz in increments of 2Mhz under 250Mhz, 1Mhz over 250Mhz.
      (SetPLLv1.0e4-HDX compiled by Nando4. HDX9000.lut/ics9lprs501.lut FSB Mhz increments by 2.0™)


    • OPTIONAL: SetFSB (shareware edition). Cost $10 US.

    • 1K ohm resistor (1/8) watt. RadioShack catalog#: 271-004. Cost $0.99 US (5pack)
      You can use 1/4 or 1/2 watt resistor also. The size of them may be too big to mount near PLL.
      Find a nice spot for it to fit with top cover over it and run a wire to it.

    • PC2-6400 800Mhz RAM or PC2-5300 667Mhz RAM .

    • ThrottleStop
    • SPDTool
    • CPU-Z
    • Intel Burn Test
    • WPrime benchmarking.

    Total Project cost:



      • ~$1 if you use free SetPLL
      • ~$11 if you use SetFSB
    More if you don't have the proper tools like soldering iron, solder, volt/ohm multimeter, electrical tape, Philips screwdriver.



    Procedure:

    (Click on any image to see full size.)
    • Remove Keyboard, Rear Cover, and Top Cover of the HDX to expose topside of the motherboard.

      Recommend using the Service Manual.

      Disassembly videos in FLV format specific to this job courtesy of RickiBerlin - 28.6MB: Download here.

    • Locate the PLL on the left side of the motherboard. You will need to find pin 4. Leading off from pin 4 there is a solder pad of which you can use to solder a wire to.

      [​IMG]

      Pin 4 is located as the 4th pin from the left on the bottom side of the PLL.
      [​IMG]

      [​IMG]

    • Solder one end of the 1K ohm resistor to the end of that wire you soldered to pin 4's solder pad. Then solder the other end of the resistor to ground. There are many copper ground rings which are ground. All the copper surrounding screw holes is also ground. I chose a copper ring near where the touchpad sits.

      Don't worry, in the pic above, the solder is not touching the pad to the left (which belongs to pin 5).


      [​IMG]
    • In the pic above, you can see the completed job. Be sure to use electrical tape or other effective insulator to make sure any exposed wire is not touching anything on the motherboard. Don't be afraid to put electrical tape over components.

      If you have an ohm meter, you can ohm out pin 4 and the side of the resistor facing ground to make sure there's continuity.

    • reassemble the HDX.



    Flashing RAM for CAS 6:

    Why must the RAM be flashed?

    Facts:

    The stock 667Mhz RAM operates @ 333.33Mhz x 2 (Hence DDR - Dual Data Rate 2).
    The stock FSB speed in the HDX is 200 Mhz.
    The FSB to RAM ratio in the HDX is 3:5.

    Calculated: 200Mhz FSB x 5 / 3 = 333.33Mhz required RAM speed. Or 1/2 the speed the RAM must operate at.

    Let's look at what happens to the RAM (which is on the FSB) when you overclock the FSB (which overclocks RAM).

    TD]5% Good[/TD][/TR]TD]10% Good[/TD]TD]15% Not so good[/TD]TD]20% Naughty[/TD]TD]25% Bad[/TD]TD]30% Evil[/TD]TD]32.5% Merciless[/TD]
    FSB OverclockRequired RAM Speed%O/C of 333.33Mhz RAM%O/C of 400Mhz RAM
    210 Mhz350.00 MHz ---
    220 Mhz366.67 Mhz ---
    230 Mhz383.33 Mhz ---
    240 Mhz400.00 Mhz Parity
    250 Mhz416.67 Mhz 4% Good
    260 Mhz433.33 Mhz 8% Good
    265 Mhz441.67 Mhz 10% Good
    What does this mean?

    With stock PC-5300 RAM @ 333Mhz RAM (667Mhz) 5-5-5-15, you cannot reliably overclock higher than 225Mhz FSB. You will experience a BSOD if you try. You need to flash it to run @ 400 Mhz, 6-6-6-18.

    With stock PC-6400 RAM @ 400Mhz RAM (800Mhz) 6-6-6-18, if you can select only CAS 6, you can overclock to the limit of whatever your CPU can handle.


    So you need to change your RAM CAS timing tables. To do that you will need SPDTool.
    **Do only one RAM module at a time in case you mess up***

    Procedure:

    For PC2-5300 667Mhz 5-5-5-15 RAM ONLY: Changing into PC2-6400 CAS6 Only RAM

    • Run SPDTool. Click File menu.
    • Select Read module 0 installed
    • Select Save (so you have a backup in case things go FUBAR or if you want to flash back).
    • Select SDRAM cycle time at maximum supported CAS latency in the bottom pane and choose 2.50ns(400Mhz)
    • Then click any labeled row box on the left side to prepare for next selection.
      Otherwise, SPDTool does a weird thing with the pull down selector menus. You'll see. :D
    • select CAS latencies supported in the bottom pane and choose the one that has CAS 6 only. (Default for RAM is 3,4,5)
    • select fix checksum in edit menu. (Very important)
    • Select Write module 0 installed

    Before​
    After​
    [​IMG][​IMG] [​IMG][​IMG] (*My actual screen shots of success, tested with 240Mhz FSB overclock.) You're done! Now do the same to the other RAM module, Module 2. Advanced: If you find that your 667Mhz RAM has timings other than the following either before or after... tRCD.. 15ns tRP.... 15ns tRAS.. 45ns tRC.... 60ns You may need to change these settings to match above as this is what most PC2-6400 6-6-6-18 RAM have. BTW, the numbers 6-6-6-18 refers to the timings of (CAS)-(tRCD)-(tRP)-(tRAS). tRC should = tRAS tRP. Lower leads to data corruption. Higher leads to increased stability, lower performance. For more info on timings, here's a good primer: Memory Timings Explained

    For PC2-6400 800Mhz 6-6-6-18 RAM ONLY: Changing to CAS 6 only.

    [IMaG]http://i583.photobucket.com/albums/ss276/DDerek20/spdtool.png[/IMG][​IMG] That's it. Use CPU-z's SPD tab to verify that there is only 1 CAS table for the RAM you just modified. It will look like this: [​IMG] (*My actual screen shots of success, tested with 245Mhz FSB.) Then do the same for the other RAM module, Module 2.
    OVERCLOCK TIME! Before we overclock, have to make sure that TME is unlocked. Run SetFSB. Select PLL ICS9LPR501SGLF (Soon, we will have our actual PLL, ICS9LPRS501PGLF.) Hit GET FSB. [​IMG] Byte 09 (highlighted in blue) will give a read out in the BIN box. If the 2nd bit = 0, then TME is unlocked. (Should look like 00xxxxxx - basically, what you see above) If the 2nd bit = 1, then you messed up the soldering job. Could be a cold soldering joint or a short. Go back a redo the soldering job. If TME is unlocked, then you're ready to overclock. At this point, take the battery out. (You'll thank me later) You have to overclock in increments. You can't just jump to max. System will hard freeze or hard crash. Increments that worked: 209.x Mhz, 218.x Mhz, 226.x Mhz, 236.x Mhz, 244.x Mhz, 213.x Mhz ,223.x Mhz, 233.x Mhz ,245.x Mhz But your CPU may need other intervals. You have to experiment. Open up CPUz. (To watch the CPU frequency increase). Now slide the top slider in SetFSB over to 209.x Mhz. Then hit SET FSB Nice! Right? Do this for each level. Stop when you get to the 230's and run Intel Burn test. Then run Wprime. (Note with wPrime v1.55, you need to set 2 threads.) If it passes, then go to 240Mhz. If 240 passes, go up by 1mhz until it fails. If 240Mhz fails, go down by 1 mhz until it doesn't. It's good to back off a few Mhz from where it failed for realtime use. If you have Dual IDA set using Throttle Stop, you will be able to get 2 extra multipliers for even higher overclock. Also with Thottlestop, MAKE SURE YOU SET VOLTAGE TO MAXIMUM!!! Otherwise you won't reach your maximum overclock potential. Once you are satisfied, you can put the battery back in. The reason you leave the battery out is in case of Hard crash, you will need to simply pull the power plug out to reset the computer.
    • You can set up a script in a batch file to launch SetFSb and run the ramp up in FSB Mhz. Open notepad Type in:
      Code:
      setfsb -i9 -cg[ics9lpr501sglf] -s245
      Save as .bat file. (select save as, then select all as file type, then save as "Ramp Overclock.bat") What that does is to tell SetFSB to set the PLL in 9mhz intervals, using PLL ICS9LPR501SGLF and stop @ 250mhz Then you can set this bat file to run at startup. You can make a shortcut to it and drag that shortcut into startup folder on start menu. Or you can simply make that .bat file into a .exe file to pin to the taskbar to engage overclock. See the section (Aesthetics:) for how to accomplish that. An enhanced no GUI popup, minimal delay version:
      Code:
      setfsb -q -w0 -i9 -cg[ics9lpr501sglf] -s245

    PART II
    Alternate Method using SetPLL: **Using SetPLL you can overclock after resume from standby. How to use setpll:
    • Download and run setpll10e4-HDX (or latest version). It's an auto-extracting zip file which will install itself to C:\setpll
    • Open a command prompt as administrator. Navigate to the setpll directory. Type cd c:\setpll
    • Issue the following commands:
      Code:
       setpll -read 0x0D setpll hdx9000 209
      You should issue the read command before writing to the PLL. The hdx9000 is the name of the .lut definition file. (You substitute with ics9lprs501pglf.lut) You should open this file to see the available FSB clock settings. Listed under [BCLK] section. The 209 after hdx9000 is the FSB Mhz you want to overclock to. If you want to ramp up to 245mhz, you do the following:
      Code:
      setpll -read 0x0D setpll hdx9000 200.209.218.227.236.245
      If you need to add a delay between PLL writes:
      Code:
      setpll -read 0x0D setpll hdx9000 200.209.218.227.236.245 2
      The "2" at the end adds a 2 second delay between each clock setting. If you need more than 2, use any number in seconds you require. It's good to start off ramp at 200, to acclimate/prime the PLL for overclock. But you have to find your perfect ramp. The ramp intervals in this guide may not work for all CPUs. Another ramp interval that works: 200,213,223,233,245 As before you should test levels above 245 with Intel Burn Test and Wprime (note wPrime v1.55, set 2 threads) . When you are satisfied, you can make a batch file that checks the FSB clock speed and overclocks if not overclocked:
      Code:
      :: Set current directory to c:\setpll cd c:\setpll :: Get the current cpu_bclk. If it's greater than 201 :: then system already OC'ed so no need to do OC :: you can also use call setpll -report -quiet instead of call cpu -quiet call cpu -quiet if %cpu_bclk% GTR 201 goto :end :: Read the PLL to ensure it is reset, especially after resume, then write. :: Reading it twice helps to ensure that it is ready for overclock. call setpll -read 0x0D call setpll -read 0x0D :: Do a ramp up in FSB frequency to avoid hard freeze/crash. :: Gives other components time to acclimate to the change in Mhz. :: The ramp up can be done with as little as 3 separate frequencies :: or as many as 6. You will have to experiment to find optimal ramp. call setpll hdx9000 200.209.218.227.236.245 :end exit
      Place this batch file in the SetPLL directory. It will ramp up the FSB if and only if the FSB is < 201 Mhz. Why is that important?
      • Because if you already overclocked in a session, doing it again will crash the system.
      • If you restart or log off, overclock is maintained. Doing it again will crash the system.
      • After resume from standby, overclock is lost. Running the batch file will restore it since it senses that FSB <201 Mhz
      Contents of HDX900.lut & ICS9LPRS501PGLF definition files:
      Code:
      ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: PLL: ICS9LPRS501PGLF :: SYSTEM: HDX 9000 :: BCLK: 200MHZ - 270MHZ :: PCIE: 100MHZ :: AUTHOR: 2.0&#8482;(Derek) and Nando4 :: :: The way 'setpll [PLL] [FSB] [PCIE]' works is it opens the [PLL].lut :: file, finds [INIT], then looks up the [FSB] and (optional) [PCIE] :: substituting [BCLK_B1], [BCLK_B2] .. [BCLK_B5] (opt.) [PCIE_B1], :: [PCIE_B2] .. [PCIE_B5] contained for the specified BCLK/PCIE in the :: [INIT] string, then sents it to the PLL via R-W everything. :: ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [INIT] is the PLL as when setfsb does a "SET". This will be filled in :: for you when you do a 'setpll -read'. 'bytecount' is the number of :: bytes to be send to the PLL. Note the bytes that change :: when alter the BCLK in setfsb, placing [BCLK_B1], [BCLK_B2] .. :: [BCLK_B5] in those positions. Optional PCI-E clocks: note the bytes :: that change when alter the PCIE clock, placing [PCIE_B1], [PCIE_B2] :: ..[PCIE_B5] in those positions. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: Setting byte 21 in local 2 (byte before [BCLK_B1] to 02 solves :: PCIe x1 issues. (eSATA, Wifi, etc.) :: DO NOT Set it to 00,01, or 03 otherwise PCIe x1 issues return. :: Also, DO NOT try to disable spread spectrum. Local 0, Byte 04 :: with FC, FD or FE. That will also cause PCIe x1 issues. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: [INIT] set bytecount=0x000000000000003F set Local0=0x4105FC77FFF09091 set Local1=0x10277D003F05D1F2 set Local2=0x23A8F4F22302[BCLK_B1][BCLK_B2] set Local3=0x8475750DEE00D2E8 set Local4=0x00B300F200080000 set Local5=0x05003206448000FE set Local6=0x00040000C04F7307 set Local7=0x0003000000000000 :: If USING [PCIE] then set a default PCIE clock if no command line pcie :: parameter is given. Default to 100Mhz :: if "%pcie%"=="" set pcie=100 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [BCLK] Move setfsb's FSB slider noting the BCLK and the data bytes :: setFSB when move the slider noting the BCLK they correspond to. ::[BCLK], [BCLK_B1], [BCLK_B2], [BCLK_B3], [BCLK_B4], [BCLK_B5] ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: [BCLK] 200, B6, B0 202, B6, B4 204, B6, B9 206, B6, BD 208, B6, C1 209, B6, C4 211, B6, C8 213, B6, CC 215, B6, D1 217, B6, D5 218, B6, D7 219, B6, D9 221, B6, DE 223, B6, E2 225, B6, E6 227, B6, EA 229, B6, EF 231, B6, F3 233, B6, F7 236, B6, FE 237, 76, 00 240, 76, 07 242, 76, 0B 244, 76, 0F 245, 76, 11 247, 76, 16 249, 76, 1A 250, 76, 1C 251, 76, 1E 252, 76, 20 253, 76, 23 254, 76, 25 255, 76, 27 256, 76, 29 257, 76, 2B 258, 76, 2E 259, 76, 30 260, 76, 32 261, 76, 34 262, 76, 36 263, 76, 38 264, 76, 3A 265, 76, 3D 266, 76, 3F 267, 76, 41 268, 76, 43 269, 76, 45 270, 76, 48 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: (opt) [PCIE] section. Move setfsb's PCIE slider noting the PCIE clock :: [PCIE], [PCIE_B1], [PCIE_B2], [PCIE_B3], [PCIE_B4], [PCIE_B5] ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: [PCIE] 
      Here is a .vbs script to use to automatically set overclock with a delay after resume. Just edit the user-editable section to your requirements. Copy to notepad, select save as, choose all files in drop down menu, and save as resume-setpll.vbs. Place in setpll directory. Read setpll instructions included in setpll package for usage. (Contributed by Nando4)
      Code:
      '************************************************************************** ' resume-setpll.vbs ' Automatically calls your AC/DC command upon start, resume-from-hibernate ' or standby or when change your power source ' ' the script loops forever, so you will have to kill it using the task ' manager if you want to stop it, look for wscript.exe '************************************************************************** Option Explicit '************************************************************************ 'User-edittable section '************************************************************************ ' start_delay: the delay time in msec to delay prior to running AD/DC script ' AC/DC_script: the script/command to run on AC/DC Const start_delay=2000 Const AC_script="c:\setpll\setpll ics9lprs387 334" Const DC_script="c:\setpll\setpll ics9lprs387 266" '************************************************************************* 'Main routine '************************************************************************* Dim wmiPowerManagementEvent, oShell, strcomputer, objWMIService, colMonitoredEvents,strLatestEvent,run_it 3` Const cntEventEnteringWakeup = 7 Const powerStateChange = 10 set oShell=createobject("WScript.Shell") strcomputer="." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colMonitoredEvents = objWMIService.ExecNotificationQuery ("Select * from Win32_PowerManagementEvent") power_detect() ' sets run_it to AC or DC script based on power source ' MsgBox ("Running: " & run_it) oShell.Run run_it,7, true Do set strLatestEvent = colMonitoredEvents.NextEvent() If strLatestEvent.EventType = cntEventEnteringWakeup Then set oShell=createobject("WScript.Shell") power_detect() ' sets run_it to AC or DC script based on power source ' MsgBox ("Running: " & run_it) oShell.Run run_it & " " & "resume",7, true End If If strLatestEvent.EventType = powerStateChange Then If power_detect() Then ' MsgBox ("Running: " & run_it) oShell.Run run_it,7, true End If End If Loop '******************************************************************************** ' Subroutines '******************************************************************************** Function power_detect() ' This Function will return true if a AC or DC power power transition is detected ' Return value: ' True if running on AC or DC, otherwise False (there is an intermediate NULL state during transition!) ' Also double-checks to ensure a transition does occur ' sets run_it to either AC_script or DC_script Dim obWMIService, colItems, objitem Set obWMIService = GetObject("winmgmts:\\.\root\cimv2") Set colItems = obWMIService.ExecQuery("Select * from Win32_Battery",,48) power_detect=false For Each objItem in colItems If objItem.BatteryStatus = 1 then ' Found DC power if run_it=DC_script then ' Cannot double-switch to DC Exit for end if run_it=DC_script power_detect=true Exit for end if If objItem.BatteryStatus = 2 then ' OK - found AC power if run_it=AC_script then ' Cannot double-switch to AC Exit for end if run_it=AC_script power_detect=true Exit for End If wscript.sleep(start_delay) Next End Function
      NOTE: you can rename "setpll" folder in c: to SetPLL. Notice the caps? Directories are not case sensitive. ;)
      Aesthetics: If you want to convert your batch (.bat) file into an .exe file so you can pin it to taskbar... Download Batch to EXE converter
      It does what it says. And can also assign/attach an icon to the exe using this program. You can find icon files (.ico)
      here.

      Example overclock .bat file made into an exe with icon pinned to taskbar: (Grey chip icon next to SetPLL folder)
      [​IMG]


      That's it folks! Enjoy.




      NOTES:
      • You should set all applications associated with overclocking the FSB to privilege level "Run as administrator."
        You do this by right clicking on the application, then properties, then compatibility tab.

      • Overclocking in power scheme "Balanced" may result in more reliable overclocking. Provided that that power scheme has minimum CPU set to 5%. (Needs more testing to confirm but appears to be the case.)

      • Naturally, temps will be about the same since you are not overvolting, just overclocking. Slight increase in temps on top end.

      • You might be tempted to use other resistor values. Don't. I tried 10K and it doesn't work. It can't hold TME unlock. And when tesedt in circuit, the resistance is only 5K. Obviously, anything under 1K doesn't work either. Tried that to. Perhaps a 2K resistor would work.

      • VERY IMPORTANT: With HWMonitor, in the ini, you must set USE_ACPI=0. Otherwise you will burn up your GPU.

      • IMPORTANT: While suspend/hibernate does work, if you go into suspend/hibernate, when you wake, you will lose overclock. YOU CANNOT TRY TO OVERCLOCK AGAIN USING SETFSB AS THAT WILL HARD CRASH THE SYSTEM. You must reset the PLL so you can overclock again. To do that, you need to shut down (not restart) and power on (boot up) again. That's just the nature of the game. So just don't use suspend/hibernate. Or if you do, just remember not to try to overclock. Though Dual IDA will still work.

        Note: SetPLL is able to overclock after resume from standby/hibernation. See below for how to accomplish that.

      • Overclock is maintained through restarts. In fact, system will boot faster with overclock engaged restarting.
        (A restart is not the same as shutting down and then pressing the power button to boot up. That's a cold boot. Overclock is not maintained. You will have to re-engage overclock in this instance.)

      • REMEMBER: Sleep disengages/resets overclock. It's the best way to undo overclock.




      RECOVERY:

      Should it ever lock up/freeze, hard crash (where screen turns entirely one color) or BSOD...

      Pull the power plug out, remove the battery, and hold down the power button for 20-30 secs.

      Sometimes resetting the BIOS to default states may help after crashes.

      Special for SetPLL users: after a hard crash, before overclocking again, open a command window:
      Code:
      cd c:\setpll
      setpll -read 0x3F
      Reading 63 bytes (0x3F) will better reset the PLL and ready it for a write again.​



      RESULTS:

      Here are my results: (Dual IDA engaged.) CPU @ 3.366GHZ (13.5x), GPU @ 610/975/1525

      [​IMG]

      [​IMG]

      [​IMG]
      [​IMG]




      ISSUES: (Strikeout = fixed)
      • <s> eSATA will not work reliably while overclock is set. Sometimes it won't be recognized. Or if recognized before overclock was set, it will unmount or become unreadable with overclock set. If it works with overclock, movies played off of eSATA drive will stutter. </s> FIXED in definition file.

      • <s>Wifi download speeds can be erratic and generally lower than no-overclock. Ping is good though. </s> FIXED in definition file.

      • <s>It appears that anything connected to the PCI bus is adversely affected by PLL overclock.</s> FIXED in definition file.

        *(Above issues fixed for SetPLL in definition file by setting Byte 21 to 02
        - set Local2=0x23A8F4F22302[BCLK_B1][BCLK_B2]).
        That sets for overclock of FSB/CPU only and not SRC or PCI. See page 23 of PLL datasheet (link below)*
      • Above wifi/eSATA (PCI express x1) issues will occur with SetFSB. M. Abo was notified by email about the issue and fix. It should be included in the PLL entry for ICS9LPRS501PGLF for next version of SetFSB. You will be able to tell by looking at byte 21. It should read 02.

      • If you try to disable spread spectrum (byte 04) in either of these ways:
        1. (set Local0=0x4105FC77FFF09091 to set Local0=0x4105FC77FCF09091) you will experience hard crash.
        2. (set Local0=0x4105FC77FFF09091 to set Local0=0x4105FC77FDF09091) you will experience PCI Express x1 issues.
        3. (set Local0=0x4105FC77FFF09091 to set Local0=0x4105FC77FEF09091) you will experience PCI Express x1 issues.

        Moral of the story, HDX doesn't like spread spectrum disabled. Leave byte 04 as FF.

      • You cannot overclock after resume from standby using SetFSB, only SetPLL. SetFSB will Hard crash the system.

      • It appears that you can set for automatic startup of overclock at boot. Simply by making a shortcut of your PLL ramp bat file and dragging it to the startup folder on the start menu. Or it can be set as a task.

        Though I wouldn't recommend auto-starting overclock with boot or auto-starting after resume with a .vbs script until overclock is rock-solid after many tests.

        If you find that auto-start isn't working out for you, simply boot into safe mode and remove whatever method you choose to auto-start.

        The same would be the case after waking from standby/hibernate. Need a delay of at least 10 seconds before overclocking again.

      • Setpll -read 0x0D is ideal (instead of reading all 63 bytes [0x3F] in the same manner in which they are written). Reading the first 13 bytes is enough to start a reliable overclock. Especially after resume from standby/hibernate. Reading more than that appears to cause issues (hard crashes, freezes) after resume.



      ADDITIONAL MOD:

      To get a higher overclock, more voltage would be required. Consider a VID3 or VID4+Vss CPU pinmod.

      Using a T9300 for example:

      Based on ark.intel.com, the T9300 has a voltage range of 0.95V-1.25V, giving the VID table as shown below.

      [​IMG]

      We see the RED VID4+Vss is all that you require. That would increase Throttlestop's 1.1125-1.25V listing by 0.2V to now actually be 1.3125-1.45.

      All voltages b/w 0.95-1.10 will be unaffected since they already have VID4=0, so your battery life will be unaffected.

      If you did a VID3+Vss mod, then the VID3 entries BLUE entries would see their voltage increase by 0.1V.
      (Text and chart courtesy of Nando4)

      HOW TO DO THE PIN MOD:

      [​IMG]
      (Pics courtesy of Naton.)

      At this point, you may also want to consider doing an FSLx pin mod on the PLL (pin 57) which means you would have a permanent overclock @ 266Mhz FSB.
      See this post for how: http://forum.notebookreview.com/hp-...on-owners-lounge-part-2-a-54.html#post6946397

      But may want to consider doing a voltage regulator mod instead: Read here.

      That would cover 1.050v and 1.087V which is not increased by VID3/4+VSS.

      Before doing that it is recommend to use Throttlestop to lock the CPU at x6 multiplier, make sure that Processor Power Management->Minimum Processor State is set to 100%, and click EIST. Then ramp up the BCLK(FSB) past 250Mhz to see what the rest-of-system' (northbridge, RAM, internal CPU cache) maximum BCLK limit is and decide if it's worth trying to overvolt the CPU to try to get it near that FSB frequency or to do an FSLx pin mod.

      (above testing method courtesy of Nando4)

      Another test method to see if FSLx & VID4+VSS mod would yield success is to disable one core:

      • Open the start menu, click on Run, type in msconfig and click on OK or hit return.
      • In the System Configuration window click on the start sub menu and the on Advanced Options button.

        [​IMG]
      • In the second window that appear, you should be provided with an option for enabling and disabling the number of processors you want to use. (See window on left side above.)
      • Validate your entry by clicking on OK.
      • Restart your PC.


      Check that only one core is operable. You can use a temp monitoring program. It will only list temps for one core.

      Then use SetFSB to overclock in small increments all the way past 266Mhz FSB. If it can hold past 266mhz w/o BSOD, then chances are VERY likely that FSLx & VID4+VSS mod will be successful.



      Technicals:

      PLL ICS9LPRS501PGLF datasheet in PDF format: 9LPRS501.pdf


      ACKNOWLEDGMENTS:

      MANY THANKS TO NANDO4(SetPLL), MORAL HAZARD(SetPLL), UncleWebb (creator of Throttlestop) and Mitsuyoshi Abo (creator of SetFSB) - each has contributed greatly to the success of this project. Without their work, help, and time spent it would not be possible. Also to RickiBerlin for proofing, brainstorming and contributing. Cheers to all!


      HISTORY:

      The first FAILED attempt using 33ohm and 100ohm resistors: http://forum.notebookreview.com/hp-...dragon-owners-lounge-2-a-145.html#post7169539

      The link to what started it all (Thanks Nando4): http://forum.notebookreview.com/hp-...on-owners-lounge-part-2-a-54.html#post6946397


      Epilogue:

      It would be wise to save this page in MHTML or some format that keeps it whole with pictures in the event the photobucket account used to store these pictures used in this guide goes over monthly view limit or get disabled. In that unfortunate event, the pictures would be replaced with placeholders.
    [/IMaGe][/IMaGe]
     
    Last edited: Jun 19, 2015
  3. dv7t

    dv7t Notebook Deity

    Reputations:
    174
    Messages:
    713
    Likes Received:
    2
    Trophy Points:
    30
    my question is, why don't/didn't the dragon designers/engineers just make it this way to begin with, since they are having parts soldered, etc. from the factory...
     
  4. moral hazard

    moral hazard Notebook Nobel Laureate

    Reputations:
    2,779
    Messages:
    7,957
    Likes Received:
    86
    Trophy Points:
    216
    I have a suspicion that if you use setpll, you will not have that suspend/hibernate problem;)
     
  5. 2.0

    2.0 Former NBR Macro-Mod®

    Reputations:
    13,368
    Messages:
    7,741
    Likes Received:
    1,022
    Trophy Points:
    331
    If only I could get that to work... :(

    LOL. That's a long conversation. Though some manufacturers do sell notebooks that use unlock versions of PLLs.
     
  6. 2.0

    2.0 Former NBR Macro-Mod®

    Reputations:
    13,368
    Messages:
    7,741
    Likes Received:
    1,022
    Trophy Points:
    331
    *************************​

    *{ Theoretical GPU upgrade path }*

    *************************​





    Thanks to NANDO4 who discovered that a poster (Zerg32) on forum MyDigitalLife has developed software that can unpack/pack HP ROMPAQ BIOS.

    Read about it here and here.

    This may enable the use of Nvidia 280M GTX or 3700M by extracting MXM VBIOS from the card and inputting it into the section of the HDX's system BIOS that deals with video.

    Requirements:

    • HDX with Nvidia motherboard 464591-001. (If you have the 8800M GTS, you already have the mobo.)
    • Need an MXM v2.1 version of Nvidia 280M GTX or 3700M. (Avoid MXM v3.0a/b cards as they are incompatible, connector-wise.)
    • HP BIOS unpacker/packer (as detailed above)
    • Dremel or file to alter heatsink. Corner of heatsink will sit atop one of the components of the video card preventing the heatsink from mating with the GPU's heatspreader.
    • Thermal paste (for GPU) and thermal pads (for VRAM)

    I kid you not, this is very advanced stuff. :D

    I would advise having everything necessary to recover your BIOS in the event of failure before starting. See page 1 for various methods for recovery.

    Procedure:

    • Somehow, you will have to acquire the video card of choice's VBIOS. Asking the owner of a notebook with one of these cards to extract it for you is one way. another way is searching the web for one.
    • Using the unpack/pack tool, extract the HDX's BIOS and replace the 8800M GTS VBIOS in the HDX's system BIOS and replace it with the VBIOS of the card you wish to install.
    • Download the same BIOS you have now and modify it by swapping the NV.cab file with the one you just modded.
    • At this point, you now have a BIOS ready to install. You can install the BIOS now.
    • Shut the system down. DO NOT DO A RESTART.
    • Now disassemble the HDX and swap out the 8800M GTX. Install the new GPU (280M GTX or 3700M)
    • reassemble the HDX partially. Just enough so you can boot up. Install the top cover, rear cover and keyboard, but do not screw them down yet.
    • Boot up. If the BIOS wasn't bricked, you are one step ahead in the game. at this point, you may have reached a successful conclusion
    • Run tests/benchmarks. Check temps. If you use HWmonitor, set Use_ACPI=0 in ini file.

    *** Have a camera ready to take pictures of your work. Take screen shots of your BIOS edits, benchmarks, temps, etc.

    BECAUSE... pics or it didn't happen. We've had a few posters make claims without proof when it comes to upgrading the video card.

    Upload your modified BIOS file for others to use. Mediafire is a good place to use. It's free and you can upload to it without registering.

    Project costs/risks:

    • 280M GTX can be acquired through RJTech for ~$800 LINK or you may find it on eBay.

    • The 3700M can be acquired from HP Parts, third party HP part resellers or from eBay. Part numbers: 493984-001, 488125-001, 460734-001. Cost: $175-$800+

    • In the event of HDX system BIOS failure: BIOS CHIP pre-flashed from Grains BIOS repair located in the UK. Cost: ~$30+shipping
      Or USB Floppy Drive to do floppy method of recovery. Cost: $15-$25. (Though this method may not work in this instance, considering.)

    • Thermal paste (Shin-Etsu X23-7783D, Arctic Silver 5, Arctic Ceramique, etc.) and thermal pads. Cost: $20-$35

    Good luck to whomever tries this.
     
    Last edited by a moderator: May 12, 2015
  7. cutthroat_jake

    cutthroat_jake Notebook Consultant

    Reputations:
    4
    Messages:
    155
    Likes Received:
    2
    Trophy Points:
    31
    Great guide 2.0. Written in easily understandable chunks, making it a tempting option.
    Will this FSB O/C work with any processor, such as a X9000 CPU and if so, what are the potential gains?

    Thanks,

    CJ
     
  8. 2.0

    2.0 Former NBR Macro-Mod®

    Reputations:
    13,368
    Messages:
    7,741
    Likes Received:
    1,022
    Trophy Points:
    331
    Thanks.

    Yes, any CPU. However, in the old days before Throttlestop, this would have been necessary for the X9000. Now that we have TS, Extreme processors which have unlocked multipliers, can simply use TS to overclock. And TS is especially necessary for X series processors because it allows increase of voltage (VID).
     
  9. lordgoblin

    lordgoblin Notebook Enthusiast

    Reputations:
    0
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    5
    I'VE REPAIRED MY HDX9490EL REPLACING MY BIOS CHIP!!!

    THANKS A LOT "2.0" AND GRAIN BIOS CHIP!!!


    Perhaps i've damaged my keyboard flat cable, working on the motherboard. some buttons aren't working. where I can find a new keyboard and what's the price? (ITA KEYBOARD)
     
  10. Dominick_7

    Dominick_7 Notebook Deity

    Reputations:
    113
    Messages:
    1,969
    Likes Received:
    29
    Trophy Points:
    66
    Wow this is great news! Congrats! How much of a real world difference you seeing with the cpu increase.. like somethings you can do easier or faster now? Also while the pll mod sounds wonderful its pretty intimidating for someone like myself to try.. I may have to open my hdx anyways because that noise was actually coming from the hard drive.. I think both may be dead..if not something related to where the hard drives connect.:( where the hard drives connect may also be messed up.. I'm trying to format and install windows 7 and it says it was corrupted.. I was so frustrated with the racket i kept bumping them (thinking it was just the fan) in order to make the noise shut off.. not a good idea.. the gpu info.. wow! I wonder who will get it done first? Thanks so much for all your contributions 2.0, Nando etc!
     
Loading...

Share This Page