It generally is worse than that. It should be almost trivial to code, if you have the internal document for each bios version laying out the structure that is stored in the nvram. The other issue is even though it is trivial, the structure could be different between bios versions in the same MB, and also could be (probably will be) different across different motherboards making support of a large number of MB's basically impossible. I have never seen anyone release said document. The underlying document may even be under NDA to all of the MB makers from the bios vendor making it not an ASUS decision alone. Without the document it would be a difficult process, one would have to save out the nvram and make a change in the bios and see how it the bits changed. So long as the bios maker is not doing anything tricky it should not be that difficult to sort out, but would need to be done in each and every motherboard + major bios revision. On Mon, Aug 22, 2022 at 1:23 AM Philip Rhoades via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > ToddAndMargo, > > > On 2022-08-22 16:11, ToddAndMargo via users wrote: > > On 8/21/22 21:29, Tim via users wrote: > >> On Mon, 2022-08-22 at 00:00 +1000, Philip Rhoades via users wrote: > >>> I have a fairly recent ASUS ROG motherboard that I want to > >>> interrogate > >>> from the CLI - specifically to see which SATA drives are > >>> hot-swappable > >>> but dmidecode does not supply that information - is there some way of > >>> getting the info without rebooting into the BIOS setup screen? I am > >>> running F36. > >> > >> Tangential approach - download the manual for the board. > > > > That won't help. They could be set either way. > > > Correct. > > > > I think he is stuck with booting into BIOS > > > It does look like it . . a bit sad . . would people on the grub list be > able to tell me how hard it would be to code? - anyone else worth > asking? I am guessing that ASUS would not have a Linux tool . . > > Thanks, > > Phil. > -- > Philip Rhoades > > PO Box 896 > Cowra NSW 2794 > Australia > E-mail: phil@xxxxxxxxxxxxx > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
