Shuttle SG45H7 — Firewire bug in BIOS SG45U10O

EDIT 2009/11/12: Shuttle has released BIOS SG45S10S which encapsulates the fix mentioned below, though you won’t find mention of the problem in their ChangeLog. Thanks to George King for getting Shuttle to release an updated BIOS publicly!

Below is a copy of an Email I sent Shuttle yesterday, indicating that I had found a bug in their latest BIOS for the Shuttle SG45H7. The bug is described below.

From: Jeremy Chadwick
To: support@tw.shuttle.com
Subject: SG45H7 — bug in BIOS version SG45U10O

Support,

There is a bug introduced in BIOS version SG45U10O (date 03/11/2009) for the Shuttle SG45H7. The bug is the following:

If the 1394 controller is Disabled in the BIOS, upon the next reboot, the BIOS crashes/locks up (BIOS startup screen is never seen, POST never happens). Clearing the CMOS is the only way to get the machine usable again.

Please see about fixing this.

If you need any other information from me (motherboard version, etc.) just ask.

Thanks.

I received two responses from Shuttle within 24 hours. The first confirms the bug (nice QA!):

From: support S
To: Jeremy Chadwick
Subject: RE: SG45H7 — bug in BIOS version SG45U10O

Dear Jeremy
Thank you choosing Shuttle.
Regarding your concern about SG45SH7 problem.
We found out the issue like what you described.
We are going to modify and release it as soon as we can.
Please feel free to let me know if you have any questions or concerns

Shuttle Inc.
Technical Support

And the second providing a beta BIOS — which I am not willing to try given that there are obviously other changes within (note the subrevision letter has gone from O to Q. What was P? Sorry, I don’t play roulette with my BIOSes):

From: support S
To: Jeremy Chadwick
Subject: RE: SG45H7 — bug in BIOS version SG45U10O

Dear Jeremy
Thank you choosing Shuttle.
Attached is the BETA BIOS that can solve your problem, please try it.
Please feel free to let me know if you have any questions or concerns

Shuttle Inc.
Technical Support

Regardless, it’s good to see a company taking bug reports seriously. Now I’m left wondering if I should tell them about a bug in their ACPI DSDT which FreeBSD whines about upon boot-up. Hmm…