AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() ![]() In UEFI, many settings, such as boot orders, are stored in variables. To be short, the BIOS settings is stored in the NVRAM and thanks to the standard, they can be accessed using UEFI runtime services. Actually I'm also not familiar with UEFI things.So those are two different and independent ways. I'm not familiar with UEFIPatch, but I guess it works like patching the firmware to directly unlock MSR 0圎2 regardless of the BIOS settings, while using the grub tool modifies BIOS settings to unlock it.First test reading known settings value (present in BIOS settings UI) to verify is a good idea. BiosSetup seems reasonable, but oddly it appeared twice.setup_var 0x02 0x01 cat sets the value of the variable cat at offset 0x02 to 0x01. So be careful not to put number here if you only intend to read value.Īnd if you want to set value then it's very easy to change that "read" to the value, e.g. To preserve compatibility, the third parameter is still the value, here in example I used a word "read" to prevent modify value and it could be any word that is not number to prevent modification. if you want to get the value of the variable cat at offset 0x01, then use setup_var 0x01 read cat. Yes it should be enough, and a programmer backup first is recommended as the rom files from Internet (even the official ones) lacks machine-specific informations such as NIC MAC address.Īnd this is another build which allows you to specify the variable name and make testing more convenient.īoth three setup_var commands are patched and it's usage is setup_var offset.Sorry I forgot it, you could use set pager=1 before setup_var to prevent auto scrolling (just like the UNIX less).
0 Comments
Read More
Leave a Reply. |