Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 37736 - grub has issues probing drives
Summary: grub has issues probing drives
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-09 13:00 UTC by Brant Gurganus
Modified: 2004-08-04 18:40 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brant Gurganus 2004-01-09 13:00:00 UTC
Grub spits out probing error messages when it probes my computer's drives.  Every message relates to probing for floppy drives.  My system does not have floppy drives.  Version of Grub that I have compiled following the Linux From Scratch 5.0 instructions do not have these errors.

Reproducible: Always
Steps to Reproduce:
1. Emerge grub if necessary
2. Run Grub
Actual Results:  
probing issues regarding floppy probes

Expected Results:  
should not have the errors
Comment 1 Torbjorn Grindhaug 2004-01-31 15:54:49 UTC
Running grub with --no-floppy should solve your problem.
Comment 2 Brant Gurganus 2004-02-12 09:31:11 UTC
I ran grub with --no-floppy and it started at least 10 times faster and didn't give the probing errors.
Comment 3 Robert Moss (RETIRED) gentoo-dev 2004-07-01 17:09:28 UTC
Perhaps we should text for the existence of /dev/fd0, and if we don't find it, disable floppy support in the build? Or is this purely runtime?
Comment 4 Robert Moss (RETIRED) gentoo-dev 2004-07-11 22:58:22 UTC
This error is due to a buggy BIOS. Fix your BIOS, or use the workaround. Please change status to RESOLVED INVALID.
Comment 5 Robert Moss (RETIRED) gentoo-dev 2004-08-04 18:40:20 UTC
As stated above, this is due to a buggy BIOS. The LFS 5.0 grub appears to have been grub-0.94, which contained a workaround for this issue AFAIK. As such this is no longer a valid bug. Closing.