can i use it for k5??
The driver should work for any mainboard with a Realtek Codec.
The driver should work for any mainboard with a Realtek Codec.
If anyone is interested I have a modded version of F9c for the Gaming 5. From what Iāve seen though its no better than F9a at all and definitely worse than my reverse engineered F9b simply by lack of proper P-State overclocking and no EZ OC Memory option.
So with Gaming K5 Iām actually able to push my G.Skill F4-3200C14D-32GTZ to rated speed (with tweaks) with F5a. Previously, I was able to push it to 2933, any higher and it wouldnāt even boot, had to kill power and reset cmos.
Would be absolutely amazing if you found the time to mod the F5a for Gaming K5
Thank you!
Iāll be releasing a batch of UEFIs based on all the newest beta versions over the next day or two. I really do recommend people go buy an Asrock, Biostar, Asus, or MSI board though their all a lot better than what Gigabyte have.
Links are up for modified and updated versions of all the latest beta UEFIs. Grab them from the first post. Theres more options Iāve unhidden/enabled with these, should cover all the options people might find useful now.
Any change for the gaming K7?
Yes, some tweaks here and there as well as adding some more options.
If weāve flashed one of your modified UEFIs before, do you advise that we still pull the battery to clear the CMOS? Or should that not be necessary any more?
Also, we can now use Q-Flash to flash your modified UEFIs. Correct? Or do you recommend that we still use the DOS flashing tool provided?
You can pull the battery if you want itāll ensure everything is "clean" after the flash but its not absolutely essential. Flashing through Q-Flash is just for added convenience but personally I usually use the DOS method still to get as close to the bare metal as I can.
Anyone want to report the bugs Iāve found with UEFI F9c for the Gaming 5? See first post. Iāve lost count of the amount of times Iāve tried telling Gigabyte and they still havenāt fixed those issues. They have been there for months.
I found other ones (might have forgot some others) on the K7 port for K5 (F9b) :
* Setting CSM Mode to "Disabled" while not modifying the OS parameter to "Windows" or "Windows WHQL", the setting wont be modified and back to "Enabled" after rebooting
* A profile saved after having booted with SATA mode as RAID and OS as Windows (WHQL or not) and CSM disabled cannot be loaded if booted without all these parameters set : It will freeze at the loading of the profile and require a reboot
* Loading a profile that has an "XMP profile" configured while no "XMP profile" was set wont update the memory speed and voltage to the XMP values (at least visually)
* Seems that i am hitting the soft brick lately : When the computer is on standby or off, most of the times if i press the power button : nothing seems to happen (except that i can hear a coil whine on my PSU so its definitely drawing more power than before) and sometimes when i press the power switch behind the PSU (a 850w Platinum made by Seasonic) to shut down the powerā¦ the system starts to boot for a second or two before the power is depleted ; if i switch quickly to OFF then ON again the system usually boots ! If i plug my phone and my headset on the front USB ports it seems to makes it even harder to boot, having to wait 20-30seconds with the PSU switch to OFF for the power to be depleted on the mobo before being able to boot again and sometimes it takes 3 or 4 tries ; unplugging 8pins power connectors from the graphic card (a Radeon R9 Fury) also seems to make it easier to boot but its not usable this wayā¦ ; removing the battery seems to work most of the time but then having to re-apply overclocking parameters makes the mobo to rebootā¦ and to be stuck again most of the times
* PState configuration is not saved on profiles
ps: did you upgrade the K7 port for Gaming 5 as well?
Iāve experienced that issue as well, and it is not just visual. This can cause unexpected bootloops (which is what happened to me), Iāve reported it to Gigabyte and was promptly ignored as usual. They donāt fix anything unless it is absolutely critical. The workaround is after loading the profile, toggle the XMP setting on and off.
The reverse engineered K7 UEFI is for the Gaming 5 only. I ran it for several days and did not have any boot / POST problems and that was with various USB devices connected to the front and back USB ports. Theres quite a lot of options that are not saved to profile that I noticed some time ago but due to the sheer number of options that arenāt saved Iām inclined to think thats a intentional design choice, albeit an extremely bizarre one. Some of your problems definitely sound like ones experienced when a PSU has a problem or developing one so if possible trying a different PSU would be recommended. Overall one or two extra options aside the K7 UEFI has I did not see any difference between it and the modified Gaming 5 UEFI. Iāll fix what I can with the tools I have but otherwise people MUST report bugs through the Gigabyte eSupport system and complain about them in the thread I linked to its the only way Gigabyte are going to take their thumb out of their arse.
Is it just me or have Gigabyte gone oddly quiet regarding the UEFIs of their AM4 boards? Anyone heard or seen anything? I hope something has forced them in to a radical rethink. Lets hall hope for the bestā¦ but expect the worst.
Last post with the latest Beta BIOS versions was two weeks ago, since then nothing. Guess letās hope for AGESA 1.0.0.7? Or at least a bigger update. But more likely the devs are just busy with Threadripper and now Coffee Lakeā¦
Yep - doesnāt seem like much going on at allā¦
Well, if the next UEFI for the Aorus boards is still garbage Iāll be throwing this test board in the bin and start work on testing another board. Donāt worry, Iāll still make modified UEFIs for the Aorus boards. Someone has to try and give the poor people stuck with these shitty Gigabyte boards something resembling a vaguely complete and thought out UEFI at least.
If they donāt fix their shit until the end of the year, Iām honestly thinking about switching with Ryzen 2 next year again. Probably would go with Asrock or Asus this time.
Hopefully I can get Gigabyte to fix some of the more major issues at least. I wonāt go in to details right now but one of the answers I got to one of the bugs I reported to them (under a completely different name of course) is so stupid it actually broke my brain. They said the orange colour setting that actually has the LEDs turn yellow on the Gaming 5 (and likely K7 as well) when you select the orange profile is a āhardware limitationā (lol, hint: its not) and that Gigabyte are going to implement (ie; āfixā) the problem on the next chipset AMD release. They then went on to say to set the LEDs to orange manuallyā¦ after me telling them how to fix the problem manually. Derp.
From the answer to that bug we can conclude two things; A: None of the coders can be bothered to change a few characters of code in a UEFI update so the LEDs do actually you know, turn orange and not yellow. B: they contradicted themselves by saying this problem is a hardware limitation then going on to say you can set the LEDs to orange manually. I donāt think I need to explain here why its not a hardware limitation if you can go and correct it yourselfā¦
Well on the K7 orange is orange and yellow is yellow ,not only in the bios but also in windows or linux