timohour

I don't think that anybody would care. The only way is if we find this out ourselves. I have checked through the schematics pg. 29 (a few months ago) but haven't found anything that would give an answer, so I gave up. This is a ss from pg 29 where you can see the JSATA2 connector. As I have commented a while ago, this is a double sided sata odd connector. On one side is a normal sata (inside the red "circle") and the other is a unique pcie connector. The pins that I highlighted are those needed for the PCIe connection (either x2 using EC or x4 using the above mentioned). I you read the thread from the beginning there was a discussion on this matter. @sskillz also detached his JSATA 2 connector but we had no luck enabling these PCIe lanes. The answer is probably inside this P5MKF usb 3.0 bay. But I never got my hands on it. Since this was a computer I bought to use @ work I couldn't justify the extra cost on it.

Kind of. The changes you need to make are part of the descriptor region, not the ME. And yes you can set every combination of the following (tested myself) port 1, 2, 3, 4 all @ x1 port 1 with 2 @ x2 port 3, 4 @ x1 port 1 with 2 @ x2 port 3 with 4 @ x2 port 1, 2, 3, 4 @ x4 Schematics show that port1 is WWAN port2 is WLAN port 3 is EC and port 4 is the modular bay. There is no confirmation though that the modular bay is port 4 or that it can be enabled. I have been looking myself for the USB 3.0 bay to check if it is port 4 and which signal trigers its activation but I couldn't find it at a reasonable price (at least when I was searching). Also there is no hardware for the x4 connection, you need to build something yourself.

Don't get this What do you mean?

You were right the red pin is B33 from pcie lane 14 and the other pins you mentioned are not used at all (mem channel B ) another think I found which is worth mentioning is the fact that GK107 and GF117 are mentioned as compatible (at least the pinout) Most probably a vBIOS issue. What do you mean no GF117 with the same memory interface as the nvs5200m?

Thanks, but I couldn't search without the photo from the board where every row has its letter. (I don't have mine around). I agree with you though that it must be a pin from the first RX-TX pair or one of very few pins used for detection in order for it to fail to be detected. Do you think that it could be due to the incorrect setting of the straps? Or straps are only used after detection? I am sorry for my noob Q but never tried such a swap. On these schematics pg. 22 you can see different straps used for different N13P chips and memory configurations. GF108 seems to be N13P-GL. I don't think it would help though. On these pg. 4 it seems like our GF108 (N13P-GL) is probably interchangeable (same straps) with the GF119 (N13M-GE) which has 48 cores instead of 96... The GK107? & (N13P-GS most probably GT640M or GT645M) would be a good bet too (according to the first schematics, & here).

no but I could check through the schematics.

That's kind of weird. GF117 according to multiple sources was supposed to be Die-Shrink of the GF108 chip. Is it possible that your GF117(N13M-GS) chip is defective? If you have a photo we can find out which pins were destroyed. I also think that it is highly unlikely those were crucial but just to be sure.

I created two file into this folder: You can use FDx1 to set or ports @ x1 and FDx2 to set ports 1 & 2 @ x2. Flash your Descriptor using fpt -desc -f FDx1.bin

This is only possible when using the two mpcie ports. You set the #1 PM100C in port 1 (WWAN) and the #2 PM100C in port 2 (WLAN). I suggested you grab an extra EC100C adapter in case you want to give away your current adapter.

follow this link http://www.hwtools.net/Adapter/PE4C%20V2.1.html and select PE4C-PM100C V2.1 along with PM100C v1.0 as you can see in the following screenshot http://www.hwtools.net/Adapter/PE4C%20V2.1.html That's a total of 103$ including s/h If you want to use this adapter with your EC (and maybe sell the old adapter online) you can buy the PE4C-EC100C v2.1 along with 2 x PM100C v1.0. total cost will be $129.

WWAN is port 1 and WLAN is port 2. It is disabled because you asked for x2.2 that means that port 2 is disabled. Under the WWAN module there is another port (port5) I assume that you put your wifi there. Unfortunately I do not know of any way to enable/disable the WiFi with the hardware switch. you can do it through software though.

So far there are mixed results. It depends on your CPU's memory controller. Some CPUs can do it, some won't. But they will be able to run @ 1866MHz and you can tighten the timings.

Well the origbios.bin image you dumped consists of several regions. If you open it with FITC you will realise that. You can see that there are four different regions. There is the Descriptor Region (This is were you should make the change in order to permanently unlock the regions you want to frequently modify. Also this is where you can set options like x2.2 or PCIe reversal) there is the GbE Region, the ME region (This is the part we need to mod in order to allow BCLK OCing) and the BIOS region (this is where the manufacturer's BIOS is stored). I suppose that you understand from the above that you don't need to reflash your BIOS region (since you made no change there) if you are going to mod your ME FW. Also you don't want to mess with your ME FW region when you want to change values in the Descriptor Region. That's why we use different flag according to the region we want to mod. No reason to mess with the other regions. Minimizing the changes we make, we minimize the possibility of a brick in case of a mistake. Since you are interested in flashing a modded ME FW I would recommend you to mod your own extract. Using the one supplied here on a different bios version than the original, may cause you trouble if you want to upgrade/downgrade your BIOS later in the way. You will need to reflash the original ME FW in order to be able to upgrade/downgrade.

Great!!! It seems like your memory controller can perform.. Could you post some performance results when you find the sweet spot?

Thanks, I knew Thaiphoon, just thought that there was another one called Sharkoon. It must be an older name I was not aware of. Try to set this to 0xFF. this worked for captnastro (just for one stick though)

Could please check the reported tRFC value with setup_var? it seems like although it is set as an 16bit value, setup_var is setting an 8bit value making it impossible to boot with tRFC = 0x16 (22). Try to set tRFC to 0xFF (255) which is the maximum 8bit value. Also, where can I download the Sharkoon Burner? Is this a new program?

You change this to 0x2. This way you set CR (Command Rate) to 2. Try that and report if it works. maybe you will have to tweak other settings too.

Got a old-specced (LVDs screen) iGPU E6440 for my brother and an i7-4700MQ off ebay. He wans't interested in crazy performance so I didn't opt for a pricier 4800/4900MQ. I didn't have much time yesterday to test, but I can confirm that changing the multiplier using NVRAM works for the E6440 too. You can set the i7-4700MQ to run with the extra 2 multipliers turbo (x34 4C - x35 2C - x36 1C) confirmed with Throttlestop too. It will be possibly TDP throttled, but didn't have enough time to test extensively. Saddly enough BIOS version A06 (that came originally with the laptop) seems to have corrected the microcode issue that would allow the 4700MQ to run like an XM chip. When I have time with his laptop (not soon probably since he is hardly here) I am probably going to try to downgrade BIOS to A01 or A02 if possible and check if they have the older microcode which will let me to unlock the multiplier!

Reading your other posts I saw that your laptopis the L502x, correct? If I am not mistaken according to your laptop's schematics your laptop should probably be able to get an x2.2 connection combining port 1 (WWAN) and port 2 (WLAN). Can you try to locate your SDATA-OUT (or SDOUT) signal in order to unlock flash descriptor? EDIT: It is on page 38 pin 5 on your ALC665 chip. I think that my guide takes it from here. Do you have the available hardware to do the x2.2 connection? AFAIK the PE4C v3.0 doesn't offer an second connection as the v2.1 did.

I realise now that all of them either used 1866MHz 2133MHz modules or used Thaiphoon Burner to add JEDEC or XMP timings to their existing RAM as did Tempest here. You can try though to set tighter timings to your 1600MHz modules let's say CL 7... It would interesting to test and benchmark with those timings (if applicable). Try something like 1600 @ 8-8-8-21... or even lower 7-7-7-20... Seems like there is no other way... Maybe there is some other variable that waits to be found, but I haven't found anything so far.

Something like this... Don't touch the 0x1e7 variable... It is used for a second channel which is not available on the E6430 and it may cause problems with the stability of your system. If it doesn't work try to set the timings (follow the guide on the previous post) If you don't understand something ask

I have initially tried but I finally used the XMP profiles to go to 1866 and then used some PnP Kingston modules to go to 2133. There are two way to OC RAM. One is to use BCLK OC and gain 4,5% more meaning that your 1600MHz memory module will run @ 1672. This works following the guide to unlock your Descriptor and mod your ME FW to allow BCLK OCing. The other is to run with a different multiplier meaning that you can run @ 1866MHz or even 2133MHz (I have seen my ram going @ 2000MHz sometimes when using 2133MHz XMP Profiles that had tight timings.) Some users reported that memory tweaking works, Khenglish though reported that You can try for yourself and report back. This post had everything regarding RAM tweaking variables by kondilac but somehow are lost (he maybe deleted it?), I don't know why... I am giving you some hints from the part of the IFR file that contains the most RAM tweaking variables. Even if you don't manage to alter your frequency you will definetely be able to tighten your timings and increse your performance.

That's true... It is worse with the 9 cell battery too.. I was talking about the new copper heatsinks though... I saw that you used Alumina Adhesive, so they are no removable, right?

All started when my brother's ASUS H61 motherboard died and I got his Celeron G540 (socket 1155). I also had an mITX case with a dead custom PSU that I don't intend to fix (Hantol HC ITX02). He now needs another PC in his bookshop, so, I decided to buy a cheap mITX 1155 socket motherboard that would use an External power brick. And I found a great deal on a Lenovo m91p motherboard @ 22$ plus shipping. Or so I thought. This motherboard uses non reference cooler holes making it impossible to fit the stock Intel cooler (or any other cooler that I had laying around and would fit the case). So I decided to use the old cooler from a Celeron D 330 (2.66GHz) a friend gave me after his motherboard died... It seems to have a big amount of aluminum in the middle and have aluminum fins... It just needed some trimming on the side cause there are some capacitors. I kind of hooked it on the motherboard using an 14" fan protector I got from a dead Thermaltake and some M3 screws and nuts. Add some MX2 the old stock Intel cooler on top of it and the results where ~ 26C @ idle and ~52C @ full load (using stress on Fedora 22). Pretty solid! I then decided to add an silent 92mm Scythe fan and the results where even better ~20-21C @ idle and ~ 45C @ full load... I lastly tried to use it passively, after an hour idle temperature was merely @ 66C and It took 30min of full load for the temperature to reach 100C. This means that I can probably run it with one or two case fans only. This will be tested. The results show that the old Celeron's D (73W rated TDP) had some pretty solid cooling solutions, that you may want to mod and use for cheap projects like this. I don't have an 1155 4C to test, but i am pretty sure that this cooler would outperform even the Copper Intel stock cooler shipped with these CPUs. More pictures with subs... http://imgur.com/a/DbOLW

Seems like it is probably not a setting, but a change in the iGPU vBIOS. Nothing we can do unless someone is willing to mod the A17 BIOS with A07 vBIOS. Pretty useless, since it works OK with A07. Nicely done.. This was a great idea using smaller copper pieces.. 7-10° lower is a great advantage... i assume that your fan is kicking now less often when at idle.. And the only drawback seems to be the extra weigh I assume that now you can't remove the extra copper pieces right?