Boot problems when USB drive attached
Posted: Thu Jul 18, 2013 3:26 am
I recently replaced my old Fit-PC with a Fit-PC3. Overall, I'm very happy with the additional speed and capacity, but I'm having one problem that I'd like to resolve.
The system would not boot when one of my Seagate external USB drives was attached; it would freeze on the "Press F2 for System Utilities" screen. I found that disabling "USB Legacy Support" in the BIOS makes booting work properly. but it also disables use of my USB keyboard in GRUB. The keyboard works for interacting with the BIOS and and for Linux, but not GRUB. (I can provide more information about the drive and my overall configuration, if that will help.)
I am currently running version 2.1.0.333_11 of the BIOS, and I noticed that the latest BIOS would modify the boot priorities, so I decided to install the latest BIOS (2.1.0.333_13) to see if it would correct my boot problem. Unfortunately, the md5 checksum in the wiki (C8D319E9CE0089C4704F5FA221FB9451) doesn't match the value I get by running md5sum against the downloaded file (75b72881c70f4c90ccf72d97be63b0d6).
So, two questions:
1. Can someone resolve the md5sum discrepancy, and
2. Is installing the new BIOS likely to solve my problem?
Thanks.
David Walker
The system would not boot when one of my Seagate external USB drives was attached; it would freeze on the "Press F2 for System Utilities" screen. I found that disabling "USB Legacy Support" in the BIOS makes booting work properly. but it also disables use of my USB keyboard in GRUB. The keyboard works for interacting with the BIOS and and for Linux, but not GRUB. (I can provide more information about the drive and my overall configuration, if that will help.)
I am currently running version 2.1.0.333_11 of the BIOS, and I noticed that the latest BIOS would modify the boot priorities, so I decided to install the latest BIOS (2.1.0.333_13) to see if it would correct my boot problem. Unfortunately, the md5 checksum in the wiki (C8D319E9CE0089C4704F5FA221FB9451) doesn't match the value I get by running md5sum against the downloaded file (75b72881c70f4c90ccf72d97be63b0d6).
So, two questions:
1. Can someone resolve the md5sum discrepancy, and
2. Is installing the new BIOS likely to solve my problem?
Thanks.
David Walker