All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: [PATCH 5/7] docs/grub: document --emu-512b install option
Date: Sun, 24 May 2020 13:43:06 +0200	[thread overview]
Message-ID: <20200524114308.1009-6-ionic@ionic.de> (raw)
In-Reply-To: <20200524114308.1009-1-ionic@ionic.de>

---
 docs/grub.texi | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/grub.texi b/docs/grub.texi
index 1ce9993a5..f071487d6 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -6433,6 +6433,21 @@ validate the contents of the bootloader embedding area, or in more
 modern systems with GPT-style partition tables (@pxref{BIOS
 installation}) where GRUB does not reside in any unpartitioned space
 outside of the MBR.  Disable the Reed-Solomon codes with this option.
+
+@item --emu-512b
+By default on x86 BIOS systems, @command{grub-install} assumes a 512
+bytes sector size when generating and writing the core image. This
+option makes grub use the disk's native sector size for addressing the
+core image's blocks and a 512 bytes read block size, as often found
+with old/buggy system firmware. To that effect, the core image is
+spread out so that each read block starts on a proper hardware sector.
+Additionally, it enables read block and sector size autodetection in
+the @samp{biosdisk} access module by setting the
+@samp{biosdisk_autodetect_sector_size} variable to @samp{1}. You should
+@emph{only} use this option if you @emph{know} that your system
+firmware is buggy and can't handle disks with sector sizes bigger than
+512 bytes correctly and your machine is trying to boot off such a disk.
+It @emph{will} otherwise break normal operation.
 @end table
 
 @node Invoking grub-mkconfig
-- 
2.25.1



  parent reply	other threads:[~2020-05-24 11:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 11:43 [PATCH 0/7] support >512b sector disks with old/buggy firmware Mihai Moldovan
2020-05-24 11:43 ` [PATCH 1/7] biosdisk: autodetect hardware sector size (opt-in) Mihai Moldovan
2020-05-24 11:43 ` [PATCH 2/7] biosdisk: restore LBA mode after read/write failures Mihai Moldovan
2020-05-24 11:43 ` [PATCH 3/7] setup: add support for native sector addressing w/ 512-bytes lengths Mihai Moldovan
2020-05-24 11:43 ` [PATCH 4/7] grub-install: hook up --emu-512b to sector size autodetection in biosdisk Mihai Moldovan
2020-05-24 11:43 ` Mihai Moldovan [this message]
2020-05-24 11:43 ` [PATCH 6/7] diskfilter: write out currently scanned partition Mihai Moldovan
2020-05-24 11:43 ` [PATCH 7/7] gpt: respect native sector size if set/detected Mihai Moldovan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200524114308.1009-6-ionic@ionic.de \
    --to=ionic@ionic.de \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.