Chewy@discuss.tchncs.de to Linux@lemmy.ml · 11 months agoJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.comexternal-linkmessage-square103fedilinkarrow-up1367arrow-down114
arrow-up1353arrow-down1external-linkJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.comChewy@discuss.tchncs.de to Linux@lemmy.ml · 11 months agomessage-square103fedilink
minus-squaresadreality@kbin.sociallinkfedilinkarrow-up9arrow-down1·11 months agoWould resetting bios clear this?
minus-squarefl42v@lemmy.mllinkfedilinkarrow-up7·11 months agoMore like reflashing entirely or just changing the image. Alternatively, you can often disable showing the.logo somewhere in the settings. What’s known as resetting bios is more like removing the stuff saved in CMOS, AFAIK
minus-squareNyfure@kbin.sociallinkfedilinkarrow-up2·11 months agoMost fastboot options dont show the logo until windows bootloader comes along. Though i am not sure how or why the logo is displayed when windows loads? Is that the same image? Loaded and displayed again or just didnt clear the display?
minus-squarebinboupan@lemm.eelinkfedilinkarrow-up1·11 months agoLoaded and displayed again, yes. It is stored in the BGRT table.
Would resetting bios clear this?
More like reflashing entirely or just changing the image. Alternatively, you can often disable showing the.logo somewhere in the settings.
What’s known as resetting bios is more like removing the stuff saved in CMOS, AFAIK
Most fastboot options dont show the logo until windows bootloader comes along.
Though i am not sure how or why the logo is displayed when windows loads? Is that the same image? Loaded and displayed again or just didnt clear the display?
Loaded and displayed again, yes. It is stored in the BGRT table.