Originally posted by Gordon1979
View Post
Announcement
Collapse
No announcement yet.
GIGABYTE Latest Beta BIOS
Collapse
This is a sticky topic.
X
X
-
For it to work you need the following
CPU support (basically every CPU with PCIe 3.0 support)
Motherboard/BIOS has to provide "rBAR" and "above 4G encoding", starting as UEFI not CSM
Graphicscard (BIOS and Driver [to utilise it])
Windows 10
On Gigabytes AMD motherboards both options are available. The BIOS doesn't care if the GPU is from AMD, Intel or Nvidia.
- Likes 1
Comment
-
Originally posted by bad_sign View PostOn Gigabytes AMD motherboards both options are available. The BIOS doesn't care if the GPU is from AMD, Intel or Nvidia.
For me option/function is not there (rBAR).
"above 4G encoding" works only Cypto.
The large memory area is not displayed in the device manager. Gigabyte has not unlocked it yet.
Additionally, the SAM/rBAR is only fully available in AGESA V2 1.1.9.0.
Comment
-
What cpu and board do you have?
Me: 5950X with B550 Aorus Pro and F11n (AGESA 1.1.0.0 D) BIOS -> both are enabled and I have the large address string in device manager.
RX480
Get the newest BIOS here https://www.tweaktownforum.com/forum...624#post976624 and flash it. Now you have rBAR
Comment
-
AMD 2700X | GIGABYTE AORUS X570 Master | 16 GB GSkill Trident Z DDR4-3600 CL18 | MSI GTX 1080 ti Gaming |
The most important question:
When comes AGESA V2 1.1.9.0
When will Gigabyte release the functions for PBO, even for the ZEN+?
MSI and Asus have all functions enabled in the PBO, which is missing at Gigabyte. See link, same CPU:
I think SAM brings little performance increase with nVidia?
Comment
-
Originally posted by Gordon1979 View PostAMD 2700X | GIGABYTE AORUS X570 Master | 16 GB GSkill Trident Z DDR4-3600 CL18 | MSI GTX 1080 ti Gaming |
The most important question:
When comes AGESA V2 1.1.9.0
When will Gigabyte release the functions for PBO, even for the ZEN+?
MSI and Asus have all functions enabled in the PBO, which is missing at Gigabyte. See link, same CPU:
https://pics.computerbase.de/8/8/2/1...0.cff8d6f0.png
I think SAM brings little performance increase with nVidia?
or BIOS with Boost Clock Override +500 (or +600 not sure)?Last edited by stasio; 01-15-2021, 01:44 PM.
Comment
-
Originally posted by stasio View Post
Did you download and try yesterday test BIOS F32a with Agesa 1.2.0.0 ?
or BIOS with Boost Clock Override +500 (or +600 not sure)?
Comment
-
Originally posted by stasio View Post
Did you download and try yesterday test BIOS F32a with Agesa 1.2.0.0 ?
or BIOS with Boost Clock Override +500 (or +600 not sure)?
Originally posted by rehsd View Post
Your previous post made it sound like F32a was using AGESA 1.1.0.0 D. Are you saying that F32a has 1.2.0.0 in it? Were different F32a versions released?
Comment
-
Originally posted by rehsd View Post
Your previous post made it sound like F32a was using AGESA 1.1.0.0 D. Are you saying that F32a has 1.2.0.0 in it? Were different F32a versions released?
Comment
-
Originally posted by Cheesecake16 View PostSo, F32a has issues with PCIe 4.0 drives because it did not see my SN850 as a bootable drive on my X570 Master. When I rolled back to F31, my SN850 showed up as a bootable drive.
Comment
-
Originally posted by Gordon1979 View PostAMD 2700X | GIGABYTE AORUS X570 Master | 16 GB GSkill Trident Z DDR4-3600 CL18 | MSI GTX 1080 ti Gaming |
The most important question:
When comes AGESA V2 1.1.9.0
When will Gigabyte release the functions for PBO, even for the ZEN+?
MSI and Asus have all functions enabled in the PBO, which is missing at Gigabyte. See link, same CPU:
I think SAM brings little performance increase with nVidia?
BAR / PBO ...
Comment
-
Originally posted by chaosophy View Post
Yeah, it looks like the F31a posted yesterday had 1.2.0.0 in it - I did download it but not tried it tbh, probably won't as it sounds like it's a really early build.
Comment
-
Originally posted by hawk7000 View Post
Indeed, I went ahead and flashed the X570 Ultra F32a version posted on the previous page and that has AGESA 1.1.0.0 according to CPU-Z (presumably rev D, but CPU-Z cannot tell the revision). It appears stasio was right the first time around about the F32a AGESA version (unfortunately, it would have been more exciting if it was indeed 1.2.0.0).
Comment
Comment