• mvirts@lemmy.world
    link
    fedilink
    arrow-up
    16
    ·
    2 months ago

    Pretty sure you can brick your system real quick using efivarfs

    https://docs.kernel.org/filesystems/efivarfs.html

    some systems dont let you write but some do.

    Theres a similar system i was messing with to read and write the firmware code… reading through this may be informative.

    efivars should let your change any bios/uefi settings if thats what youre looking for.

    • zaknenou@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      2 months ago

      thank you! I think this is what needed to explore
      It is not my level to edit these things, I’m just Linux newbie exploring the possibilities.

      But I still can’t wrap my head over dd not being able to wipe a storage device out, despite being described as a “low level tool that can write zeroes to targets” in the discussion I viewed online.

      • BCsven@lemmy.ca
        link
        fedilink
        arrow-up
        9
        ·
        2 months ago

        The bios isn’t like a regular storage device presented to the kernel for mounting.

      • bloodfart@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        Dd can’t overwrite a burned cdr either. If the thing you wanna mess with is read only there’s no way to use it as a dd of.

  • Kyrgizion@lemmy.world
    link
    fedilink
    arrow-up
    20
    arrow-down
    4
    ·
    2 months ago

    It resides on the MB itself in a separate chip, so no, although there are probably tools to make it possible.

      • NaN@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        7
        ·
        2 months ago

        They should still be possible. It’s not clearing the BIOS though, it is clearing variables loaded into the BIOS. The OS needs to be able to write to them. A good one limits what an OS can write or rebuilds them, a bad one bricks.

  • VeganCheesecake@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    2 months ago

    You can mount the efi partition, but I don’t think you can usually mount the uefi or bios. I’ve only ever edited vbios, and haven’t done so in quite some time, but I remember needing to clamp the vbios chip. Dunno if motherboards make their bios chips more accessible, but I kinda doubt it.

    Some motherboard support starting bios/uefi updates from a booted OS, so there might be a vector to be found there.

    • nyan@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Early true BIOSen were stored on EPROM, which couldn’t be rewritten while on the board, so those were read-only.

      Later BIOSen were often on EEPROM or other chips that could be reflashed while on the board. According to Wikipedia, that started in the mid-1990s. However, you usually needed physical access and/or special software tools to do an overwrite—you couldn’t mount these as a filesystem.

      UEFI is quite different from legacy BIOSen and can be mounted as a filesystem, but how much it can be tampered with varies between implementations and devices.

      So you would have been correct up until about 30 years ago, but not for modern systems.