@bios 2.32.b13.0829.1

[screwtech02]

Like the title says, who has it and where can I get it to download? Need this to Flash back to F2 bios to confirm that my E52650 will detect pci-e 3.0 cards before the F3 and up series bios's were released.

Thanks in advance.

[profJim]

Re: @bios 2.32.b13.0829.1

Check out the "best solution" post in i7-4820K with Gigabyte GA-X79-UP4 [Solved] - Intel i7 - CPUs that says:

I have that same board with a 3930k. The F4 bios is very untested. It shut off my ability to use my screen saver or power saving to shut off the screen. it would stay powered up and fully active 24/7. What a pain in the behind. I finally got a utility (@bios version 2.32) from Gigabyte support to backdate to the F2 bios I had previously to get it working again. After that, I found out there is a F3u bios from a 3rd party that updates the firmware on the Marvell SATA chips for better raid 1 performance and updates the bios to recognize the IB-E chips. It works great on my system.

I don't know if my dropbox public links still work, but here:
@bios: https://dl.dropboxusercontent.com/u/...atbios_x79.exe
F3u bios: https://dl.dropboxusercontent.com/u/...X79UP4_mod.F3u

I was able to download the atbios_x79 file but I'm not able to confirm the version.

Good luck!

[profJim]

Re: @bios 2.32.b13.0829.1

If the above @bios download does not work for you do a web search using: download z79 @bios 2.32

My web search also found atbios232.rar from a German website.

Comparing the file dates in each of the downloaded files showed that some of the dates differed by several days.

[profJim]

Re: @bios 2.32.b13.0829.1

Some of the file dates in the atbios232.rar file match up with the @bios 2.32.b13.0829.1 version number:

[screwtech02]

Re: @bios 2.32.b13.0829.1

Thanks guys, I will try this again tonight.

[screwtech02]

Re: @bios 2.32.b13.0829.1

Working fine now after reflashing to F2, My ES proc sees all 4 of my 270 Toxic cards just fine. So much for it NOT being a BIOS issue.......

[profJim]

Re: @bios 2.32.b13.0829.1

Thanks for the update, glad to hear that all of your video cards are finally working.

<--- bios engineer/Q.A. tester

[screwtech02]

Re: @bios 2.32.b13.0829.1

ProfJim, my underlying question is what got "broken" after the F2 bios and demise of the 3D screen? Gigabyte support wanted me to send my board in for them to test, even after I proved the cards were not the issue. Now, this is the ONLY bios that works with my 2650 ES proc, and my 270's. Seems that somewhere, something was overlooked. Or, they are they gonna play the "you have a ES processor, not supported" card??

[profJim]

Re: @bios 2.32.b13.0829.1

To me it looks like regression testing was inadequate with the newer F3 bios versions.

From Regression testing - Wikipedia:

Regression testing is a type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas of a system after changes such as enhancements, patches or configuration changes, have been made to them.

The intent of regression testing is to ensure that changes such as those mentioned above have not introduced new faults.[1] One of the main reasons for regression testing is to determine whether a change in one part of the software affects other parts of the software.[2]

Common methods of regression testing include rerunning previously completed tests and checking whether program behavior has changed and whether previously fixed faults have re-emerged. Regression testing can be performed to test a system efficiently by systematically selecting the appropriate minimum set of tests needed to adequately cover a particular change.

Contrast with non-regression testing (usually validation-test for a new issue), which aims to verify whether, after introducing or updating a given software application, the change has had the intended effect.

Background

Experience has shown that as software is fixed, emergence of new faults and/or re-emergence of old faults is quite common. Sometimes re-emergence occurs because a fix gets lost through poor revision control practices (or simple human error in revision control). Often, a fix for a problem will be "fragile" in that it fixes the problem in the narrow case where it was first observed but not in more general cases which may arise over the lifetime of the software. Frequently, a fix for a problem in one area inadvertently causes a software bug in another area. Finally, it may happen that, when some feature is redesigned, some of the same mistakes that were made in the original implementation of the feature are made in the redesign ....

[sa5441]

Re: @bios 2.32.b13.0829.1

Sorry for bothering
Does anyone still got @BIOS 2.32
I try to downgrade the bios version but just could't find any @BIOS 2.32