E6520 Owner's Thread

@lennartb
Same situation here: microcode version 15 with A05, version 1A with A07. I can install 1B under linux, downloading it from Intel, but nothing changes with respect to the turboboost. In my case turboboost does not work neither under linux nor under windows 7 (checked with hwinfo).

Either Scott has a newer CPU (with microcode 1B) that works with A07, or he is using some "non standard" BIOS. Scott, could you help us understanding what is happening? How old is your PC/CPU?

 

I am using the same Dell distributed BIOS others are using. The 2720QM I have in the E6520 did come from a new Precision M6600 with a production date of 09/26/2011. Before removing the processor, I did flash the BIOS of the M6600 which also updates the microcode so it could be possible the processor is disregarding whatever is causing the issue for others because of some elusive coding. The E6520 was also flashed prior to the processor upgrade so maybe this specific 2720QM thinks it is still in the M6600.

Although the common system data utilities used are a good reference, I also like to use the actual Intel processor diagnostics and indentifier utilties shown below. They should give you accurate feedback on the general operation of your processor.

Scott-

Intel Processor ID Tool

Intel 64bit CPU Diagnostic Tool

 

I meant the machine cannot boot up. Windows enters into BSOD and next time I attempt to boot I have to use restore to a previous configuration.

Not long ago the Dell Client System Update attempted again to update the video driver and again killed windows.

I used to buy low end machines from HP so this time I decided to buy a reliable Dell Latitude and i think I never had so many situations where the machine doesn't boot up. Furthermore the DELL manual client system update keeps offering me drivers that I have installed long ago and the cue of updates never clears up.

In December I'll buy a SSD and reinstall everything from scratch. I hope that will fix all.

 

I'm on a E6520 with quadcore, with A07 BIOS running Ubuntu 11.10 x64.

Linux can install a newer microcode. On Ubuntu, I did:

Code:

sudo apt-get install intel-microcode

Now my dmesg shows:

Code:

[  831.770204] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x1a
[  831.771762] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x1a
[  831.773225] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x1a
[  831.774591] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x1a
[  831.776202] microcode: CPU4 sig=0x206a7, pf=0x10, revision=0x1a
[  831.777943] microcode: CPU5 sig=0x206a7, pf=0x10, revision=0x1a
[  831.779679] microcode: CPU6 sig=0x206a7, pf=0x10, revision=0x1a
[  831.781510] microcode: CPU7 sig=0x206a7, pf=0x10, revision=0x1a
[  831.783793] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[  831.827795] microcode: CPU0 updated to revision 0x1b, date = 2011-07-14
[  831.828430] microcode: CPU1 updated to revision 0x1b, date = 2011-07-14
[  831.829053] microcode: CPU2 updated to revision 0x1b, date = 2011-07-14
[  831.829760] microcode: CPU3 updated to revision 0x1b, date = 2011-07-14
[  831.830380] microcode: CPU4 updated to revision 0x1b, date = 2011-07-14
[  831.831002] microcode: CPU5 updated to revision 0x1b, date = 2011-07-14
[  831.831613] microcode: CPU6 updated to revision 0x1b, date = 2011-07-14
[  831.832219] microcode: CPU7 updated to revision 0x1b, date = 2011-07-14

for reference, some of my CPU info as reported by Linux:

Code:

processor	: 7
vendor_id	: GenuineIntel
cpu family	: 6
model		: 42
model name	: Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
stepping	: 7
cpu MHz		: 2195.163
cache size	: 6144 KB

 

Mmmm looks great, seems like the 1b is really a newer version.

Do you have a dual boot available to check if it makes a difference?

Besides that, my linux knowledge isn't perfect at all but when I use a ubuntu livecd, can I do the same?

 

It should work on a Live CD.

Understand, this is a soft-upgrade of the CPU. I assume a reboot puts it back to the BIOS version, but on every boot Linux upgrades it again. Windows and OSX do the same.

The reason for these soft-upgrades is due to hardware vendors (like Dell) who do not keep up to date in their BIOS. It is easier for the operating system vendors to deploy updates.... especially after a system is 1 or 2 years old and BIOS updates mostly stop (especially retail consumer laptop lines).

 

I can verify that Dell doesn't keep an up to date microcode in their BIOS. It's version 0x07, and I seem to be stuck with it since windows does not recognize my ES CPU so it does not load a new microcode. This is with BIOS A07 too. I flashed to see if I got a newer microcode and I didn't.

I did not get any turbo problems with A07.

 

@veritas72

I called DELL today they uninstalled Intel and Nvidia drivers then installed latest Intel and Nvidia drivers booting at every single step and the problem went away.

I had an issue with Client System Update that it was never in synch with my driver versions and the tech suggested me to uninstall it and monitor DELL's site for driver updates from time to time. He said that it is unreliable and causes more problems than solutions.

 

As I said in one of my previous messages, I already tested with the 1B microcode loaded by Linux, but there is no difference with respect to the turboboost issue. Could be that Linux loads the microcode late, when the BIOS already runned. Indeed, the microcode is lost and must be reloaded at every reboot (by the BIOS or the OS).

BTW, this suggests that the fact that Scott's CPU works correctly cannot be related with the microcode "preloaded" when the CPU was still on the precision. That microcode is lost. Probably his CPU is new enough to have the 1B version in rom.

 

Hi Rossim,
I read your message a bit too late After trying it. No changes here too.
I agree with everything you said but as far as I know, a microcode is updated in the CPU itself. So when Scott updates his bios in his precision and afterwards put the CPU in his E6520, the microcode should be the same. Unless he flashed A07 on the E6520 again (probably don't want to try that Scott ;-) )

Well, I think throttlestop will be the solution for now, looking forward to a A08 bios...