vbatts/grub
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

* docs/grub.texi (Installation): Document buggy BIOS install.

Browse source
This commit is contained in:
Vladimir 'phcoder' Serbinenko 2010-10-17 00:46:39 +02:00
parent ba5f65cfa1
commit 5b0276902e
2 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
ChangeLog
View file

@ -1,3 +1,7 @@
2010-10-17 Vladimir Serbinenko <phcoder@gmail.com>
* docs/grub.texi (Installation): Document buggy BIOS install.
2010-10-17 Vladimir Serbinenko <phcoder@gmail.com> 2010-10-17 Vladimir Serbinenko <phcoder@gmail.com>
* docs/grub.texi (Installation): Indent. * docs/grub.texi (Installation): Indent.

13
docs/grub.texi
View file

@ -617,6 +617,19 @@ installation. The format is defined in @ref{Device map}. Please be
quite careful. If the output is wrong, it is unlikely that your quite careful. If the output is wrong, it is unlikely that your
computer will be able to boot with no problem. computer will be able to boot with no problem.
Some BIOSes have a bug of exposing first partition of USB pendrive as a floppy
instead of exposing pendrive as a hard disk (they call it ``USB-FDD'' boot)
In such cases you need to install as following:
@example
# @kbd{losetup /dev/loop0 /dev/sdb1}
# @kbd{mount /dev/loop0 /mnt/usb}
# @kbd{grub-install --boot-directory=/mnt/usb/bugbios --force --allow-floppy /dev/loop0}
@end example
This install doesn't conflict with standard install as long as they are in
separate directories.
Note that @command{grub-install} is actually just a shell script and the Note that @command{grub-install} is actually just a shell script and the
real task is done by @command{grub-mkimage} and @command{grub-setup}. real task is done by @command{grub-mkimage} and @command{grub-setup}.
Therefore, you may run those commands directly to install GRUB, without Therefore, you may run those commands directly to install GRUB, without