ES Xeon Discussion
- Thread starter britinpdx
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
again, there is almost no second market, just many whole sellers.
you can get a cheap 1st gen because some has upgraded to 2nd gen. and has a CPU left.
same for 4th gen. but there are no upgrade CPU for LGA4189 so there are no spare CPU to compare prices with.
Yes, with S/N. However they might require a particular reason for D vers.
3 years ago, a member @spyroot also fought with gigabyte for a week. Then he got F01 version GitHub - spyroot/ms33ar0 . Could you please share this D version so others can have a access to it?
Last edited:
The reason that independent users need to spend days and even weeks waiting for a reply from GB, GB definitely have their own issue(s) need to be solve to improve the customer's experience. However the D ver BIOS not just include some early features, also with plenty of bugs and more unknown issues compare with any later versions if the unusual hardware(s) occurred. Any possible operations could cause the consequence which difficult and painful to solve. I will try to find is the file if it is still on this computer(consider that I lose the access of my foreign net drive account and cleaned this computer few days ago) and PM you if the file is still available.
However if you need F04 or later to fill the project's gap I could PM you now consider that it is on my F ver folder just checked.
Last edited:
Yes, could found the ver# in the F ver's release log. T might be the early stage of R? Can't find them in the F release log
took 5 weeks for me to get CPLD Firmware for MS33-AR0 to run Xeon Max HBM only mode,
my board gave error without RAM. i had to lie about my processor because 9480 is not on GB QVL.
( note not all GB need that CPLD Firmware update/downgrade, if upgrade fails, you need repair by GB )
Last edited:
i remembered a friend had the same issue some months ago, he has better contacts to GB and they told him CPLD as the reason.
i tried on my MS33-CPA (OEM) and it worked with HBM only.
doubt that. just faulty AIDA BCLK measurement.
if the system timer is misaligned, nobody can measure BCLK accurately.
what tells HWinfo / CPU-Z you ?
edit: if you have VBS enabled all data is not valid.
Last edited:
Hi everyone,
I am trying to downgrade the BIOS on my GIGABYTE MS73-HB1 motherboard from R07 to R02. Both of them are directly downloaded from gigabite without mod.
Currently, the system is running R07. I have tried the following:
I am trying to downgrade the BIOS on my GIGABYTE MS73-HB1 motherboard from R07 to R02. Both of them are directly downloaded from gigabite without mod.
Currently, the system is running R07. I have tried the following:
- Via AFUWIN (Windows): I encountered the error 18 - Error: Secure Flash Rom Verify fail and a warning stating Check RomLayout .................. Changed.
- Via BMC Web Interface:
- I uploaded the R02 image.RBU file found in the official BIOS package.
- I selected "BIOS" as the update type.
- The BMC processed the file and reported a "Successful Update."
- However, after a reboot (fully cut the power, even remove the battery on MB), the BIOS version is still showing the previous newer version, not R02.
did your motherboard and CPU pass full POST ?
after successful POST the BIOS sends actual version to BMC, no POST = old BIOS shown.
Last edited:
Hi, dear community!
Could you please help to find the right direction....
I have three servers of equal configuration (2xQ2SR, MS73-HB, [BMC Firmware version 13.06.09 BIOS Firmware Build Date 06/14/2023 BIOS Firmware version T01 CPLD Firmware version MB: 09] + intel520 nic), and on two of them - proxmox 8.4.0 is installed, on third just ubuntu server.
One of the proxmox servers started to reboot periodically (one time a week, of sometimes two times), and it doesn't depend on the load, it often reboots at night without load. The CPU temperature is ok (under 55 degrees) and VRM are also a little warm under load, the power in the server room is also ok. But IPMI log contains "sensor of type Power Unit logged a BMC Event : Power unit is off and sensor of type Power Unit logged a BMC Event : Power unit is on." PSU is super flower 1600W titanium in all three servers.
I bought new FSP PSU, but not installed yet, because not sure that it is the root cause. Second server with proxmox last year also reboouted, but only once (with same error in IPMI), and server with ubuntu never.
Could you please advice what it can be?
Could you please help to find the right direction....
I have three servers of equal configuration (2xQ2SR, MS73-HB, [BMC Firmware version 13.06.09 BIOS Firmware Build Date 06/14/2023 BIOS Firmware version T01 CPLD Firmware version MB: 09] + intel520 nic), and on two of them - proxmox 8.4.0 is installed, on third just ubuntu server.
One of the proxmox servers started to reboot periodically (one time a week, of sometimes two times), and it doesn't depend on the load, it often reboots at night without load. The CPU temperature is ok (under 55 degrees) and VRM are also a little warm under load, the power in the server room is also ok. But IPMI log contains "sensor of type Power Unit logged a BMC Event : Power unit is off and sensor of type Power Unit logged a BMC Event : Power unit is on." PSU is super flower 1600W titanium in all three servers.
I bought new FSP PSU, but not installed yet, because not sure that it is the root cause. Second server with proxmox last year also reboouted, but only once (with same error in IPMI), and server with ubuntu never.
Could you please advice what it can be?