I already emailed Polygon about this, because I couldn't register at the forum, but he fixed me up. So I can post the problem here now.
Here is the problem:
quote:I own a Gigabyte GA-880GA-UD3H which I use for my NAS (FreeNAS) system. Though it's working okay, I am experiencing a serious issue with this motherboard. With running 6 harddisks for my NAS, it will lockup whenever I press DEL during post. Always at the same exact point; during the harddisk check with onboard AMD AHCI ROM.
After spending several hours tracking this issue and what is causing it, I have narrowed it down to the outdated version of the AMD AHCI ROM.
The current one in the bios (even the latest bios) is version 3.0.7 which dates back to 2009 (!). The latest available AMD AHCI ROM version is version 3.0.C.2 which dates from 2011.
Not only were there some performances tweaks to this new ROM, but moreso it also contains several fixes and removes several bugs. It also removes the problem I am experiencing (when pressing DEL to access bios, it locks up).
Now I have tried contacting Gigabyte, but as you might understand, they don't care at all about my problems. They even stated I need to download the latest AMD Drivers for Windows?! Ehr.... Right. Like stated before; I am runnign FreeNAS, which is based on FreeBSD. What the .... does AMD Windows drivers have to do anything with this? Clearly the support staff over at Gigabyte are clearly incapable to answer these support tickets. Sigh.
Then I decided to start editing the latest BIOS from Gigabyte myself with CBROM32. Though I managed to release the old ahci.BIN and inserting the latest ahci.BIN (sb800.bin), I cannot get Q-Flash, FlashSPI to accept the damn BIOS. Everytime I get an "Invalid BIOS Image"-message. I even tried @BIOS from Gigabyte in Mini Windows XP, though it flashed without any problems, I was presented with the following message on the next boot:
Warning: MAIN BIOS CHECKSUM ERROR! Retrieving recovery source from HPA... HPA BIOS not available!!
Result? It started to use the backup BIOS (from Gigabyte's Dual BIOS function), so I am back to square one again.
Now I have read your post about "Award BIOS and Sensitive Modules", and I am starting to think that this is the problem, why I am not allowed to flash my motherboard with a modified BIOS and therefor getting the "Invalig BIOS Image"-messages.
Though I feel confident with editing a BIOS file with CBROM32, I am not so confident with HEX-editing a file.
Now I am really hoping someone is willing to do this for me, so I can finally use the motherboard without problems or issues. My hope that Gigabyte will fix this is non-existent. So I am really hoping that someone is willing to update the BIOS with the latest AMD AHCI ROM.
The sb800.bin should replace the current ahci.BIN within the BIOS.
Hopefully someone is willing to do this for me. Cause I clearly cannot do it myself. And buying a new motherboard is not an option nowadays (money problems).
Thanks already in advance! Every effort is highly appreciated!
Posts: 7 | From: Earth | Registered: Jan 2012
posted
Woops missed the OS note... I haven't edited a BIOS in almost 5 years but sounds like the checksum didn't get updated... I'm downloading your link now and will take a look if I can remember how! hahaha..
-------------------- Too Many Computers,... Too Little Time ..... Com'on ???..! Posts: 27985 | From: Fire Island, NY | Registered: Feb 2003
posted
No problem. It was a lot of text. I just wanted to make it as complete as possible.
I think it has to do with the "Award BIOS and Sensitive Modules" on which you also posted something about.
I tried it with CBROM32 myself already several times (even tried older bios files and different ROMS). But all come down to the same things "Invalid BIOS Image".
Something that I noticed as well, which maybe causing problems as well, is that when you check the original BIOS file with CBROM32 /D it shows PCI ROM[B] is on the 17th position. After replacing the PCI ROM[B] (or extracting and adding the new one) with the new rom, it will show the ROM on the 26th position.
So I don't know if it's possible, though I am really happy that a pro is taking the effort!
Posts: 7 | From: Earth | Registered: Jan 2012
posted
Well the good news is that the 2 AHCI modules are both exactly the same size. They could just be copy and pasted in place. But the bad news is that their checksums are different which means the BIOS checksum must be corrected. And the CBROM does that I believe. (forgotten everything)...
But my gut feeling when looking at the 30 or so modules that the BIOS contains, is that only Gigabyte can modify it. We don't have BIOS tools that can do what is needed and I'm pretty sure that is on purpose... I'll continue to look at it out of interest in trying to remember, but like I said, my gut says "sensitive modules" when I see 30 or more.. And that never allows modification.
EDIT: WRONG! The AHCI module checksums are both 00h..
-------------------- Too Many Computers,... Too Little Time ..... Com'on ???..! Posts: 27985 | From: Fire Island, NY | Registered: Feb 2003
I am going to keep a reminder to myself; never buy a Gigabyte motherboard again. I want to have control over my own motherboard and it's BIOS. Especially since Gigabyte doesn't care about updating ROM's in a BIOS, even if they are outdated by more than 2 years.
Sigh.... Anyways thank you for trying at least. Highly appreciated!
Posts: 7 | From: Earth | Registered: Jan 2012
posted
Replying to your post about the module moving from 17th to 26th position, that is because CBROM does a delete and add. And the "add" goes in at the bottom of the list. Sensitive modules BIOS's, do not like that. Only way to do it is paste the new module over the already installed module and fix the checksum. But even them, it usually won't boot...
-------------------- Too Many Computers,... Too Little Time ..... Com'on ???..! Posts: 27985 | From: Fire Island, NY | Registered: Feb 2003
posted
Now scratching my head on trying to remember ho to "uncompress" the BIOS.. I forget the name of the compression technique... It is common but quite old..
EDIT: OK. It is "iha255" compression.. Now can't remember how or if it can be uncompressed... )
-------------------- Too Many Computers,... Too Little Time ..... Com'on ???..! Posts: 27985 | From: Fire Island, NY | Registered: Feb 2003
posted
Well that's the part I mentioned in my first post; I know CBROM32 (a little), but I don't have clue regarding HEX-editing and stuff like that. Posts: 7 | From: Earth | Registered: Jan 2012
The compressed sb800.bin(the new ahci module) is bigger when compressed then the already installed ahci file...
That means it is not an exact copy and paste overwrite. The new one is coming out bigger then the old one and the sensitive modules will cause the BIOS to be corrupt and not boot.... Sorry.... We tried...
-------------------- Too Many Computers,... Too Little Time ..... Com'on ???..! Posts: 27985 | From: Fire Island, NY | Registered: Feb 2003
posted
In this screen shot of the before(top) and after(bottom), you can see that the bytes following the highlighted code, starting with 25 F32D 6C69, are at different addresses as shown in the left hand column...
Edit: I tried the technique a 2nd time in case I made a mistake and get the exact same results.
-------------------- Too Many Computers,... Too Little Time ..... Com'on ???..! Posts: 27985 | From: Fire Island, NY | Registered: Feb 2003
![[Smile]](smile.gif)
Com'on ???..!
![[Frown]](frown.gif)
