GA-880GA-UD3H - unlock cores on Phenom II 555 BE

[b_force]

I'm currently e-mailing with the technical staff of Gigabyte.
I also have exactly the similar problem with unlocking the X2 555 on a 880GMA-UD2H

I've tested the same CPU on a MSI 785GM-E51 board and it unlocks without any troubles and problems (and running really stable exactly).
On the latest reply to me, the Gigabyte staff was talking about a F5 version of the BIOS.
I can't find it, but maybe they were confused with the 880GM (without the "A")??

To be really honest, I'm a bit disappointed.
I had the choice to buy this board a a little cheaper board.
I chose the more expensive 880GMA-UD2H board because of the simple and better unlock function (according to the Gigabyte website).
Unfortunately, it isn't working at all 

[proxy]

Dark Mantis, you're absolutely right about better binning, and luck of the draw, however, the issue here isn't so much unstable unlocked cores as it is inability to detect and unlock cores at all on 8xx boards.  The BIOS incorrectly shows the unlock options as only Core 0 and Core 1, instead of Core 2 and Core 3 and does not unlock them, whereas other motherboards do.

b_force I'd be very interested in the dialog between yourself and Gigabyte Support, so please keep us updated.  I have tried the F4 and the F5 (latest version as of this post) BIOS on the 880GA-UD3H with no luck so far.  I have faith in Gigabyte though, and they have a solid reputation for a reason.  I'm sure they'll find a solution to this issue  .

I'm likely going to grab an Asus M4A88TD-V for this build so I can deliver it on time for the user and hang onto the 880GA-UD3H for now.  It really is a terrific board and I'd hate to have to return it, beside restocking fees hurt a bit  .

[b_force]

Unfortunately the technical staff isn't replying that fast, so hopefully I've a reply tomorrow.
I can not blame them, but it seems that they tell the same story over and over again (but in other words).

Here you see a document that they send.
Nothing more than the basic steps for unlocking.

BTW. Can I use the GA-880GA-UD3H BIOS for the 880GMA motherboard?

[absic]

BTW. Can I use the GA-880GA-UD3H BIOS for the 880GMA motherboard?

Simple answer, no. If you download a different Mobo's BIOS for your motherboard, when you try to install it you should get a checksum error and the update will fail.

[domino]

I wonder if you guys can replicate this result on 880 chipsets.

I have an ASUS board, contacted them, they contacted their test beds.  Problem is, when core unlocker is enabled, I can't even run as a dual core or single core on my 555.  When unabled, I can.  Stable, 4GHz, excellent temp and voltage monitoring.  Awesome board.

They weren't able to replicate the problem, nor did they really have a clue.  For those who are unable to unlock cores on the 880 chipsets, are you able to replicate this issue?  Try running with the core unlocker enabled and run it as you would normally run as (dual core for a x2 555).

Wonder if this could bring insight to the problem.

[b_force]

Ok, I've again reply from Gigabyte staff.
They uploaded the F5 BIOS and I updated my motherboard BIOS.

Result?

........nothing 

I've told them that there are more people with exactly the same problem.
I'm wondering if maybe the different revisions are an issue?
@ domino
I can disable one core of the two, so in other words, running a X2 555 with only one core.

[proxy]

Yeah I've been following the thread over at http://www.overclock.net/amd-cpus/535501-official-amd-k10-5-core-cache.html.  I'm waiting for BIOS version F6 beta myself hopefully if and when that comes out it'll resolve the issues.

And yes, I did see that Test555.doc as well, doing the steps there just allows you to run a single core processor 

[b_force]

A reply from Dark Mantis (or any Gigabyte member) would be appreciated  

[absic]

Hi,
sorry that I haven't replied earlier but I have been trying, without success, to find out a bit more about this problem before posting.
As my old mum always says, "If you haven't got something useful to say, don't say anything."

I am trying to get an answer so please bear with me as it might take a bit of time.

[Dark Mantis]

A reply from Dark Mantis (or any Gigabyte member) would be appreciated  

I will leave this to absic as this is his jurisdiction and he knows a lot more about the AMD platform than I do.

[b_force]

A reply from Dark Mantis (or any other Gigabyte member) would be appreciated  

I will leave this to absic as this is his jurisdiction and he knows a lot more about the AMD platform than I do.

HAha, it's all right.
I just want to be sure that some people actually reading my posts  

@absic
I think it's strange/odd that the Gigabyte staff successfully unlocked the cores.
Maybe they lie (I don't believe that) or maybe it has something to do with different revisions.
Unfortunately I can't find what the differences are between Rev 1.0 and Rev 2.x.

[Dark Mantis]

I am sure absic will be able to sort it out for you if anyone can. He will just keep digging at it until he finds the fault.
I would say one thing and that is did you clear the DMI when you did the BIOS update to F5? If not you might want to try that while you are waiting for absic.

[absic]

Yes, we're reading them, just don't have an answer yet.  

This is proving to be a little trickier than just a bad driver or power lead not plugged in properly.

[b_force]

Those were to quick replies  
See my edit in my post please  

I use @BIOS with the DMI clear function on.

absic, if you have any questions or if I can help you with any tests, please ask.
(I've knowledge about electronics, so maybe there is something to measure or so)

[Dark Mantis]

Just for the record I wouldn't advise using the @BIOS program it is much more dangerous than the QFlash utility that we recommend.