The Core Dump

It updates the blog, or it gets the hose again.

By Nic Lindh | Tuesday, 19 August 2014 | FacebookTwitter

Flashing a Gigabyte BIOS should be easier than this

Once again user-interface ineptitude and Internet idiots make things harder than they have to be.

This post is just here so Google can find it and hopefully save some other poor soul some time.

And lo, there is much sadness in the land of the Hackintosh, as my machine with a Gigabyte H87n-WiFi board has an unfortunate tendency to keel over every few weeks: Hard lock, nothing in the logs, just instant death. So I’ve been looking around for what to do to get this otherwise excellent rig to stop having seizures. And sigh there’s a lot of magical thinking in Hackintosh land. But going back to first principles it makes sense to update the BIOS to see if Gigabyte fixed some bugs. Can’t be too hard, right? It’s just a BIOS update, right? Like we’ve been doing for effing decades, right?

Well, gather round, children while uncle Nic tells you a sad tale.

Turns out Gigabyte have finally realized that not everybody who buys their boards are running Windows (thank you!) so you no longer have to download a weird Windows app to update the motherboard. Which, when you think about it, was insane. But those dark days are behind us now: Newer GigaByte boards have a Q-Flash utility right on the BIOS. You download the updater, put it on a FAT-formatted USB stick and boom!

Except you’ll get a “File size incorrect!” error.

Urgh.

So let’s Google that. And get a lot of noise about how the BIOS file got too big so you have to use a Windows utility called @Bios to update the BIOS to make it understand the BIOS is larger now.

Say it with me, kids: “Sigh.”

This turns out to be incorrect. The BIOS file you download from Gigabyte is a zip file and you have to decompress it, then put the actual update file on the USB stick and you’ll be golden. Hint: The actual flash file is the one that doesn’t end in .exe or .bat.

At this point you may be asking yourself things like, “Couldn’t Gigabyte just have put this information in the Readme file?” or “Shouldn’t people not post shit on the Internet where they’re just guessing?”

Those are valid questions, indeed.

But for now, go forth and update ye olde BIOS firmware and put thine thumbs together to hope it fixes thine problem.

In the meantime I’ll be over here shaking my head.

« Red immigration meat in the Arizona primaries

 »


Enjoy the ten latest posts:

Space Shuttle Endeavour

Endeavour is a symbol of hope for a better future.

Review: The Revenant

A great 90 minute movie smothered in a 2-and-a-half-hour wreck.

Thoughts on the 2016 Prius v after a road trip

After a 1,000 mile road trip in his new Prius, Nic has thoughts and gripes.

Apple Watch, six months in

Thoughts on Apple Watch after half a year of daily usage.

It’s upgrade time: 2016 Prius v first impressions

Moving from a 1997 Honda Accord to a 2016 Prius is kind of a big deal.

Review: ELAC B6 bookshelf speakers

A great value for your sound system.

Magical thinking about encryption and privacy

Predictably, the Paris attacks brought the anti-encryption crowd back out of the woodwork. They're at best being willfully disingenuous.

Review: Spectre

A long-time Bond fan looks at the latest installment in the series and has thoughts.

Book roundup, part 20

Includes The Antidote, One Nation, Under Gods, Losing the Signal, The Todd Glass Situation, The Last Policeman, The Three-Body Problem, The Dark Forest, Beacon 23, Killing Pretty and Queen of Fire.

Building a static site for an investigative journalism project

Things to consider when planning to build a site on a compressed time table.