To see the names of the available tests use the -show-tests or -show-tests-full options. To run just one or a few tests rather than the default set of batch tests, one can specify the test name too. Sudo fwts -batch -interactive -power-states One can mix and match these tests to run the different classes of tests in one go, e.g.: These tests can be selected with the -u or -utils options. So if a test fails, it is useful to run these and append the data to the results log to help diagnose and debug issues with the firmware. These are not strictly tests, but will gather system information useful for kernel developers to debug a system.Select these tests using -P or -power-states options. These run suspend (S3) and hibernate (S4) power management tests and may hang the machine, hence they are not in the default batch test category.Selected with the -interactive-experimental option. These are beta quality interactive tests.These tests require user interaction, such as pressing keys, closing laptop lids, disconnecting/connecting power supplies etc.One can select these tests with the -batch-experimental option.
#Uefitool microcode code
This tests require no user intervention and contain code that may give false positive results - much akin to beta quality code.However, one can select these with the -b or -batch option. These run automatically by default and require no user intervention.However, if require, one can specify specific tests to run rather than the default set. Running fwts with no options will run through all the batch tests that require no user interaction and by default append test results into a log file called "results.log". Many of these tests need super user access to read BIOS data and ACPI tables, so the tool requires running with super user privileges (e.g. They've started with 210 and persist till now, even in your version.The tool fwts comprises of over fifty tests that are designed to exercise and test different aspects of a machine's firmware. I assume that it is rather a BIOS feature.Īnd again, none of these problems appeared on my stock BIOS. That was perfect =(Ībout waking from keyboard, there is no option in power management that allows to disable it while sleeping. The LED on power button stayed off in sleep mode and the front one blinked shortly once in a couple of seconds.
#Uefitool microcode software
ROG Small (Not Used)- 0A22794E-69D4-42F8-B75B-2EBBF612F317ģ) I dont see a bios setting but I believe you can do that with software in the windows power managementĤ)Yes, you can safely flash back to stock and even older versions, I have done it numerous times.Ībout LEDs and waking from keyboard, these problems started when I've flashed 210 stock BIOS and persisted even when I flashed old 205 version. Make sure whatever image you replace them with, that they are the same file size, resolution, and color space. Here are the locations of all the image files in the bios. A cleaner method that I did was simply unplug the cable that goes to the front LED board.Ģ) You don't like my Static splash screens?! j/k Yes, the splash screens can be changed using UEFITool. Sorry no bios option but a piece of electrical tape over the lights works nice. I have no brick yet but it is curious for me is it safe to flash stock versions back.ġ) LOL, Yes, those lights are super annoying. You've noted that the only way to repair a brick is to solder a new BIOS chip. Is it possible to disable wake from keyboard?Ĥ. Any way to change splash screen on boot?ģ. Is there an option to manage LED blinking during sleep mode? These two leds on front and on power button make me crazy))Ģ.
I have several questions about it's configuration:ġ.
#Uefitool microcode mod
Man, your BIOS mod is amazing! You've done a great job!
0 kommentar(er)
