[sf-lug] Best way to install a .exe firmware updater
Rick Moen
rick at linuxmafia.com
Sat Nov 23 00:37:03 PST 2019
Quoting Akkana Peck (akkana at shallowsky.com):
> The Gen 7 is a great Linux laptop, with only a couple of problems:
> in particular, a glitchy trackpad addressed by a firmware update
> that Lenovo only distributes as a .exe.
So, you're reasonably certain that's a _Windows_ 64-bit executable, and
not a DOS one? I've always dreaded the situation you describe, but I
always hoped that the utilities to update firmware would remain simple
non-graphical utilities as the were in days of yore. And DOS utilities
could be run, if need be, from a FreeDOS boot. (But there's a risk even
to that, which I'll get to next.)
If such a utility is designed to be run in the Microsoft Command Prompt
window (i.e., is a DOS utility) or is designed to be run under
MS-Window, unfortunately the prudent and minimum-risk course of action
is to run it in the real Microsoft environment, without trying to cheat
by (e.g.) trusting to MS-Windows in VirtualBox. Why? Because in the
latter case, the necessary direct hardware access may not be there or
(worse) may fail during reflashing.
So, if I had such a laptop and needed to run a Windows or DOS-based
firmware updater utility, I'd bite the bullet and (1) get a HD or SSD
that can be temporarily devoted to this purpose, (2) set it to be the
primary boot device (probably requires removing or disconnecting the
Linux drive), and (3) install real native MS-Windows on it. Then
reboot the laptop from the Windows drive, and run the firmware updater.
Anything short of that risks failed update, possibly bricking the
component in question.
That having been said, does Linux Vendor Firmware Service yet support
the Gen 7?
https://www.omgubuntu.co.uk/2018/08/lvfs-lenovo-firmware-updates-linux
Hmm, searching https://fwupd.org/ it appears you might be in luck.
More information about the sf-lug
mailing list