Show how booting in a SATA system will fail. Use the `toggle' plugin.

1 files changed, 12 insertions, 2 deletions

diff --git a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn
index 7ddd931c..9deb65d5 100644
--- a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn
+++ b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn
@@ -13,7 +13,7 @@ GNU Mach current only supports the `x86` (alias `ia32` or `i386`) architecture.
 `amd64`/`ix64` should work in `32-bit` compatibility mode. However, in practice
 `amd64` systems seem to be troublesome more often than not. This is probably
 related to the same (chipset-related) problems we often see with recent
-machines; but it seems that amd64 ones use problematic chipsets particularily
+machines; but it seems that `amd64` ones use problematic chipsets particularily
 often. So far we haven't heard of similar problems with Intel's eqivalent
 `ix64` (or `EM64T` as it used to be called) -- but maybe that just means fewer
 people tried running the Hurd on such machines :-)
@@ -54,7 +54,17 @@ IEEE 1394 is not supported at this time
 
 Most IDE drives are known to work. Some drive geometries do not work. If you find a specific IDE drive that does not work, make a note of the model and technical specifications here.
 
-SATA drives may work in compatibility mode.  <!-- Sure?  --[[tschwinge]] -->
+[[toggle id="SATA" text="SATA drives may work in compatibility mode."]]
+<!-- Sure?  --[[tschwinge]] -->
+
+[[toggleable id="SATA" text="""
+This is how booting a [[GNU/Hurd_system|hurd]] will typically fail if GNU Mach
+couldn't connect to the hard disk, e.g., in a SATA system without IDE
+compatibility mode:
+
+    start (hd0,3)/hurd/ext2fs.static: (hd0,3)/hurd/ext2fs.static
+    device:hd0s4: No such device or address
+"""]]
 
 # Device Drivers