Me: [download bios]
Me: flash!
Board: no.
Me: [download older bios version]
Me: flash!
Board: No.
Me: [download still older bios version]
Me: flash!
Board: NO.
...etc...
Me: [check board version] A320M Pro 4 Rev. 2.0
Me: [look at web browser] A320M Pro 4 Rev 1.0
Me: [blink] damn.
Board: [shrug]
This is how you lose an hour you'll never get back. 😒
=> More informations about this toot | More toots from fedops@fosstodon.org
@fedops And Board did not even have the decency to tell you WHY NO?
A simple "hardware type mismatch" might have done nicely here. 🙂
=> More informations about this toot | More toots from mkj@social.mkj.earth
@mkj right? Or maybe don't change a single byte in the character salad board name and make it incompatible.
But at least that's better than the Gigabyte mc12 which I had 0 luck getting to do anything other than turn on the BMC, even with an old Ryzen 3. 🤬
=> More informations about this toot | More toots from fedops@fosstodon.org
@fedops Well, that too. But since the error condition was obviously detected, and probably identified, there's no reason why the software can't tell you why it's refusing to do what you are trying to get it to do. That last one is just lazy.
=> More informations about this toot | More toots from mkj@social.mkj.earth
@mkj absolutely. The actual message is "no image found". Which is factually wrong.
"No image that suits this board found" or even better "incompatible flash image found" would have been so so helpful.
=> More informations about this toot | More toots from fedops@fosstodon.org
@fedops Indeed. Sounds like it's using some kind of container format and whoever wrote the error messages was wearing programmer-colored glasses.
I'm sure that error message makes sense in the context of the technical implementation, but for the end user, well, no...
=> More informations about this toot | More toots from mkj@social.mkj.earth
text/geminiThis content has been proxied by September (3851b).