BIOS_RCVR Gigabyte boards

Hi Folks,

I’m new to this forum, so please correct me if there is a sub-forum to ask.

Does anyone know the correct procedure how to use this jumper BIOS_RCVR? The gigabyte manual does say anything. I only found it on new intel boards. You have to put the ROM file on the flash drive. Now Gigabyte did not indicate any step. Do you need to rename or not or any particular structure (directory etc)? I tried different combinations but never saw that board trying to access the flash disk in all cases. I’m asking if I need to start the motherboard in some specific way so it starts reading ROM files.

This intel doc and it more or less documented.
https://www.intel.com/content/www/us/en/support/articles/000024411/server-products/server-boards.html

Board Gigabyte mr33-ar00. ( I believe all c741 uses same layout)

Initial BIOS that posted on my system MS33-AR0_F01.
(Gigabyte doesn’t want provide this build not sure why and I never took backup :frowning: )

Thank you

There’s a bios recovery procedure described in the manual if you still have an uncorrupted boot block.
Otherwise GSM software allows to flash bios firmware:

Still warranty?

What happenend?

Hi,

Thank you very much for check ! Honestly I tried everything. 4 days already fighting and trying figure out. The GSM client always show a success but never actually do anything. The same story for IPMI, BMC Web UI.

Hence, I checked intel docs for jumper recovery, they indicate startup.nsh while Gigabyte renamed all files. So it is tough to figure out whether they need MBR or GPT or any special button pressing magic. I did four different flash drives and renamed all files, but still, I don’t see any read access from the flash when I switch positions. (by the way, if you know the default ssh password, please let me know, I don’t think they provide a root access but im sure it has default pass)

Regarding the warranty, I waited three weeks for shipment and then the CPU, so by the time I received the CPU, I was out of a 30-day guarantee… So sux… really.

Initially, the motherboard detected CPU and memory, but the Samsung NVME, board detected as Intel after reading the release note for BIOS mention that; Hence I upgraded BMC, and after BIOS to the latest B17 for MS33-AR0-rev after reboot, BIOS disappeared. After checking the RBU file, I noticed it contains an ME/Microcode bunch of other stuff, so the update process from BMC broke or corrupted a BIOS.

Thank you.

30 days warranty seems very short? You’re sure?

Can you backup / dump the firmware via BMC?

I managed to get initial BIOS and now I do see VGA output. I think the problem is not with jumper I think it has bug with USB , essentially they never detect USB device and new BIOS nukes VGA output. … I do see both issue reported in release note in BIOS so it looks to me BMC and BIOS half backed really. This the only way to read POST on this board…

java -jar ./GbtUtility-2.1.61.jar -H 192.168.254.18 -U admin -P MGAP5100046 postcode current


  • GIGABYTE(TM) GbtUtility v2.1.61     *
    

[192.168.254.18] Start to get current BIOS post code.
[192.168.254.18] Post code length : 54
0x01 0x02 0x03 0x04 0x05 0x06 0x23 0x23 0x00 0x02 0x7F 0x48 0x0E 0x49 0x4A 0x4D
0x15 0x52 0x55 0x19 0x31 0x00 0xA1 0xA3 0xA3 0xA7 0xA9 0xA9 0xA2 0xA2 0xA7 0xA7
0xA7 0xA9 0xA9 0xA8 0xAA 0xAE 0xE0 0xE0 0xE0 0xE1 0xE4 0xE3 0xE5 0xAF 0xAF 0xB0
0xBF 0xB5 0x7E 0xCF 0x7E 0xCD 0xB0 0x7E 0xC1 0x70 0xB1 0xB1 0x7E 0xC2 0x7E 0x70
0x7E 0x7E 0xC4 0xB1 0xB1 0xB1 0x7E 0xB4 0x7E 0xB8 0xC5 0xB2 0xC6 0xB3 0xB3 0xB3
0xB6 0xB6 0xB6 0xB0 0xB7 0xB6 0xB7 0xB6 0xB6 0x7E 0x7E 0x7E 0x7E 0xB7 0xB7 0xB6
0xB6 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xD8 0xB7 0xB7 0x7E 0xB7 0xB7 0x70 0x70 0x70 0x70 0x7E 0xB7
0x7E 0xB7 0xB7 0xBE 0xBE 0x7E 0x7E 0xD2 0x7E 0xD2 0xD6 0x70 0xB9 0xB9 0xB9 0xB9
0x7E 0xB7 0xB7 0xB7 0xB7 0xB8 0xB8 0xB8 0xD7 0xC9 0xDA 0xD9 0xDB 0xBA 0xB9 0x70
0x70 0x70 0x7E 0x70 0x70 0x7E 0x7E 0xCB 0xBB 0xBB 0xBB 0xBB 0xBB 0xBB 0xBB 0xBB
0xBB 0xBB 0x7E 0x7E 0xD0 0x7E 0xD0 0x7E 0xD0 0x7E 0xD1 0x7E 0xD1 0x7E 0x70 0x7E
0xB7 0xCA 0xCA 0xDC 0x7E 0xCC 0xBC 0xBC 0xBC 0xBC 0xBC 0xCE 0xC6 0x7E 0xBF 0xAF
0xE6 0xE7 0xE9 0xEB 0xEC 0xED 0xEE 0x03 0x23 0x02 0x22 0x00 0x02 0x7F 0x48 0x0E
0x49 0x4A 0x4D 0x15 0x52 0x02 0x22 0x50 0x00 0x04 0x06 0x0B 0x0C 0x0D 0x15 0x7F
0x00 0x7F 0x40 0x41 0x42 0x47
postcode process complete … (1/1)


  •   GIGABYTE(TM) CLI "postcode" Command Executions Summary       *
    

Target IP: | Command Name: | Status: | Total elapsed times:
192.168.254.18 | postcode | Success | 0.184 sec.
Total success nodes : 1 fail nodes : 0


It’s hard to understand what you were doing and what you want to describe.

  1. Sorry, what I was saying is that all new BIOS brick the VGA out on this board and never post. So I manage to get the initial BIOS. Now I use a procedure from BMC and downgrade the BIOS, essentially re-enabling VGA output, but it does not post. ( It stops on the POST code I posted before)

  2. Now I’m 100% positive that downgrade also downgraded the ME. Hence my question. Suppose I flip the BIOS_RCVR jumper and ME_RCVR jumper.

Question one for gigabyte server motherboard what file name it expects (for Gen4 c741 boards) ? (Gigabyte docs all over the place) Right now, I see BIOS Recovery on the screen; after 120 seconds, I see it led on the flash driver but no IO reading from the FLASH drive. I assume BIOS Recovery needs a particular file. I tried amphibious.rom, startup.rom, the file name in the zip from BIOS that Gigabyte provided. Added startup.nsh etc.

My second question is if you do BIOS_RCVR and ME_RCVR will that downgrade both BIOS and ME ? ( I did check the BIOS file from Gigabyte. It has embedded in the BIOS ME partition)

I hope it makes sense :slight_smile: If not, I’ll try it again.

Please dump the current content of the bios via BMC software and attach it.

I actually posted all github since it took me almost 7 days fighting with Gigabyte to get initial BIOS that did post initially.

F0 is the one that did work , anything else F10/F14/F17 and new BMC ver put entire system down.

Not interested in Gigabytes files

Dump the current content of the bios chip via BMC software and attach it.

bios_image_dump.bin.zip (9.5 MB)

That’s the F01 firmware almost unchanged.

ME data partition has changes, that’s expected.
NVRAM has some new entries, that’s expected, too.
FD is identical to stock, DevExp1, ME code partitions are identical to stock, rest of bios region is identical to stock.

The system should be able to boot fine with this.

I’m sorry, but this doesn’t seem to be firmware related- and this ‘finding’ is consistent with the fact that you flashed a number of firmwares without significant changes.

1 Like

It did only after I swap CPU. It looks like it doesn’t like QXP, the crazy part that initially F01 did boot with QXP but after I upgrade to F14 it nuked the system, I downgraded to F01 with ME jumper force upgrade, but that didn’t not help. Do you think QXP completely useless now ?

Since not firmware related, I have nothing to add. Good luck.