Thursday, December 30, 2010

ATi Radeon HD 6950 to HD 6970 Mod

email post

AMD Radeon HD 6950 to HD 6970 Mod

Introduction

A few weeks ago AMD released the Radeon HD 6970 and Radeon HD 6950. Both cards are based on AMD's new Cayman core which is their first graphics processor to use a VLIW4 shader configuration.
AMD/ATI Highend GPU structureJust like on all other similar products, AMD's two Cayman variants, called Cayman Pro and Cayman XT, are based on the exact same GPU silicon. The model variant a GPU chip becomes is decided after the die is produced, at some point before it is put on the card. Creating new SKUs from the same silicon by locking features has been common practice in the industry since at least the Radeon 9500 in 2002. This article is to unlock the Radeon HD 6950. The HD 6970 has nothing that can be unlocked.
The picture above shows the disabled HD 6950 shaders in red. When unlocked, these deactivated units become active, resulting in a substantial performance increase. AMD has two methods of locking the shader count on all of their recent GPUs. The first one relies on fuses inside the GPU, or on the substrate - a mechanism similar to Intel's multiplier locking. It is not reversible as far as we know. The second mechanism is the one we are interested in, AMD can configure the VGA BIOS in a way that it disables extra shaders, in addition to the ones disabled via the on-die fuses. This method is mostly used to create engineering samples or reviewer cards that match the target specifications. Usually production cards come with the shader count configured in the fuses, so that it can not be changed. Apparently currently shipping Radeon HD 6950 cards from all manufacturers - which actually are all the same card with different sticker - have their shaders locked via the BIOS method, so we can exploit it easily.

Unlocking the shaders

Unlocking the additional shaders is done by flashing the card with a HD 6970 BIOS. You can find a few in our VGA BIOS collection. Any of these BIOSes will work on any reference design HD 6950 card. You could use the ASUS BIOS which comes with higher clocks & Overdrive limits and enables voltage changes via SmartDoctor, or stick with one of the reference BIOSes in case you are afraid the clocks might be too high. I will describe the method for flashing from within Windows, which is safe enough on these cards because of the dual BIOS feature that enables easy recovery.
  1. Grab ATI Winflash from here (32 & 64-bit).
  2. Download HD 6970 BIOS. The Sapphire one I linked to will work on all reference design cards from any vendor.
  3. Make sure the BIOS switch on the card is set to the 1 position (pictured further down if you don't know where it is).
  4. Run ATI Winflash, click Save to save your BIOS, so you have a backup in case something goes wrong.
  5. Load the HD 6970 BIOS into Winflash by clicking Load Image, followed by Program.
  6. Let the flashing process complete and reboot your system.
  7. Check the shader count using GPU-Z, it should show 1536. Make sure you use version 0.5.0 or newer, the official 0.4.9 version does not support HD 6900 Series properly. If you see a shader count of 1600, your GPU-Z version is outdated.
  8. To ensure maximized performance open Catalyst Control Center, go to the Overdrive tab and set the PowerTune slider to the +20% setting. The "Testing" section of this article has more data on that.
  9. Check stability in Windows desktop applications and games.
If you get an error like ID mismatch or Could not erase ROM, then you'll have to do some extra work in a Windows command prompt (or DOS): Run atiwinflash -unlockrom 0 followed by atiwinflash -f -p 0 bios.bin where bios.bin is the path and filename of the HD 6970 BIOS you downloaded. Update: I have uploaded a pack of all the files required together with some batch files to ease the process for less experienced users. You can download it here, please report success or any issues with the scripts in the comments for this article. Feel free to post in the discussion thread for this article if you need additional assistance with the flashing process.

Testing

We can see that enabling the shaders without any clock increases improves performance. Once the clock speeds are adjusted to match the HD 6970, the card effectively performs just as well as a full blown Radeon HD 6970. I did some additional power consumption tests and it seems that AMD's PowerTune power limiting system does not get "upgraded" by the BIOS flash. We see that even when modded, the HD 6950 (at HD 6970 shaders and clocks) runs into the PowerTune limit earlier than the regular HD 6970 which results in reduced power draw but also reduced performance in Furmark. With a power consumption of 202 W, the modded HD 6950 is well below the 225 W specification limit of the HD 6950 power configuration. Once we up the power limit in Catalyst Control Center by +20%, we see that the modded HD 6950 draws 252 W, which exceeds its specification (225 W) by 27 W. This move also improves rendering performance by a good deal, so I would recommend it to all users who perform this mod and have a half-decent power supply. Going 12% beyond the specified power limit will not have any ill effects on your hardware and is well covered by manufacturing tolerances and overspeccing, but it reduces the possibility of stuttering or other performance slowdowns caused by AMD PowerTune.

What if something goes wrong?

So you flashed the BIOS and your card doesn't work for one reason or the other? If your card boots fine but does not work reliably in 3D, you can just boot the card and flash back the original BIOS of your card (that's why you should always save your BIOS before doing any flashing experiments. In case your card does not boot at all you can use AMD's new backup BIOS feature:
  1. Set the BIOS switch (pictured above) in the 2 position to enable the recovery BIOS and restart the computer. This will let you boot the card without problems.
  2. Boot into Windows/DOS prompt and get ready to flash the card - do not start the flashing process just yet.
  3. Set the BIOS switch in the 1 position with the system running and ready to flash.
  4. Flash your saved BIOS to the card.
  5. Reboot, done.
The dual BIOS feature is just an added convenience for easier recovery, it is not a requirement for this kind of modding, nor is it evidence that AMD has planned their cards with unlocking in mind.

Test Results

Please report your findings in this thread (or e-mail me) so we can update the statistics. (Last updated Dec 27, 19:40 CET)

ATi Radeon HD 6950 to HD 6970 Mod

ManufacturerCards
tested
Unlocks and
works fine
Unlocks but
rendering errors
Does not
unlock
AMD1100
HIS3300
ASUS2200
PowerColor5500
Sapphire9900
XFX3300
Club3D3300
Gigabyte2200

The latest in hardware and gaming

email post
AMD Radeon HD 6950 Can be Unlocked to HD 6970
Looks like Santa brought an extra present for us hardware enthusiasts this year. Thanks to a less secure locking method AMD's new Radeon HD 6950 can be unlocked to a full blown HD 6970 with a few mouse clicks. As detailed in our article, you can safely perform the flashing process from within Windows. In case something goes wrong it is easier than ever to recover the card thanks to AMD's new Dual-BIOS feature. We tested the unlock on three HD 6950 cards: one AMD engineering sample, one HIS media sample and one ASUS retail card. All of them unlocked perfectly and run at HD 6970 speeds now. More success reports are compiled into a table at the end of the modding article.

Sunday, December 26, 2010

Notepad++ 5.8.6 release

email post
Notepad++ 5.8.6 release

jelly2188.blogspot.com - Domain - McAfee Labs Threat Center

email post
jelly2188.blogspot.com - Domain - McAfee Labs Threat Center+
ad link:


   Conclusion + "": DO NOT trust their ranking are all about money. mywot.com is an untrustworthy on-line community service. The WOT community would rate your site to the worst if you out their tool on your site and do not pay for the trust seal.

Upgrade ESX 4 Update 2 to ESX 4.1

email post
Upgrade ESX 4 Update 2 to ESX 4.1

Problems with VUM (VMware Update Manager) lead me to upgrade our ESX 4 U2 hosts to ESX 4.1 using the command line. During the upgrade, I was getting an error about a certain rpm package that would not uninstall properly (esxupdate error 15), so I've included that as part of my instructions.

To prepare for the upgrade, you need to download the ESX pre-upgrade zip file as well as the 4.1 upgrade zip file. I used WinSCP to copy them to the /tmp directory on each ESX host, then put the hosts in maintenance mode using vCenter before doing the upgrade. The whole process is pretty quick once you've downloaded and staged the zip files.

Note these instructions assume you use sudo for admin tasks, if not, leave it out.

1. install pre-relase patch: sudo esxupdate update --bundle=/tmp/pre-upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip

2. install upgrade: sudo esxupdate update --bundle=/tmp/upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip

3. remove RPM from update 2 that won't remove autmatically (the first command checks to see if it is still installed, the second removes it if it is still there): sudo rpm -q vmware-esx-apps-4.0.0-2.17.261974 sudo rpm -e vmware-esx-apps-4.0.0-2.17.261974

4. reboot sudo reboot

5. Afterwards, you can log back in and check the host version: sudo vmware -v

Jerry Blogger's Prediction

email post
Jerry Blogger's Prediction:

On , there would be a big accident in around Toronto area which would involve a good amount of people.


I sense it half year ago actually. A very strong feeling that would occur on the Mid-night of 27th or maybe 28th since it would be a the moment of date changing.

So, I suggest people stay home on 26th to 28th

Sunday, December 19, 2010

Total Commander, Version 7.56a

email post
Total Commander, Version 7.56a, is a Shareware file manager for Windows® 95/98/ME/NT/2000/XP/Vista/7, and Windows® 3.1.

Total Commander

New (December 17, 2010): Total Commander 7.56a for Windows released July 31, 08: Total Commander CE/Pocket 2.51 released October 23, 06: Problems with self-extracting ZIP archives on Windows XP November 2, 02: Name change to Total Commander! Important note: Changes for orders from Germany, U.K. and Belgium! Features in Total Commander 7.56a now include : * Two file windows side by side * Multiple language and Unicode support * Enhanced search function * Compare files (now with editor) / synchronize directories * Quick View panel with bitmap display * ZIP, ARJ, LZH, RAR, UC2, TAR, GZ, CAB, ACE archive handling + plugins * Built-in FTP client with FXP (server to server) and HTTP proxy support * Parallel port link, multi-rename tool * Tabbed interface, regular expressions, history+favorites buttons * Thumbnails view, custom columns, enhanced search * Compare editor, cursor in lister, separate trees, logging, enhanced overwrite dialog etc. * Unicode names almost everywhere, long names (>259 characters), password manager for ftp and plugins, synchronize empty dirs, 64 bit context menu, quick file filter (Ctrl+S) * New: USB port connection via special direct transfer cable, partial branch view (Ctrl+Shift+B), and many improvements to ftp, synchronizing and other functions * And many more!
 Download:

Saturday, December 18, 2010

Usb internet radio + TV player in True Sense

email post
Usb internet radio + TV player
Usb internet radio + TV player in True Sense

There is something call "USB Worldwide Internet Radio TV Dongle Recorder Player" sell in the whole world. Ebay, China, everywhere is selling this thing. It look like a TV receiver or a plug and play internet TV Hardware which would made your computer be able to play Internet TV such as Google TV.

Please DON'T BE FOOLED. It is actually a normal usb harddisk stick ONLY.The stick contains a autoplay file which is a self-made player like PPS.

Thursday, December 16, 2010

EHCI Specification

email post

Specification

The Enhanced Host Controller Interface (EHCI) specification describes the register-level interface for a Host Controller for the Universal Serial Bus (USB) Revision 2.0. The specification includes a description of the hardware/software interface between system software and the host controller hardware. This specification is intended for hardware component designers, system builders and device driver (software) developers.