From: dillon <dillon@web>
Date: Thu, 17 Sep 2009 03:47:15 +0000 (-0700)
Subject: (no commit message)
X-Git-Url: https://gitweb.dragonflybsd.org/ikiwiki.git/commitdiff_plain/73cedf59cffeb33661aed7a0ab7d78c07da87342

---

diff --git a/issues24/index.mdwn b/issues24/index.mdwn
index e9a0921e..2d51f6dc 100644
--- a/issues24/index.mdwn
+++ b/issues24/index.mdwn
@@ -10,8 +10,11 @@
  * Once you get the system up you may have to remount / read-write, then
    fix /etc/fstab and adjust /boot/loader.conf as necessary to specify
    the root mount using vfs.root.mountfrom="hammer:serno/<SERIALNUMBER>.s1d"
-   (for example).  We recommend specifying mount points by serial number,
-   using /dev/serno/<SERIALNUMBER>.s1<partition> as necessary.
+   (for example).
+ * We recommend specifying mount points by serial number, using
+   /dev/serno/<SERIALNUMBER>.s1<partition> as necessary.  Also remember
+   you may have a device specification in your /etc/rc.conf (for the dump device),
+   and of course the root mount specification in /boot/loader.conf.
 
 * Your kernel and world are out of sync.
  * tty's and pty's may not work properly in this case, you may have
@@ -29,6 +32,13 @@
    partition, naming it 'a'.  Then copy the HAMMER /boot into it
    (directly, not as a subdirectory called 'boot').
 
+* You have an AHCI SATA controller but the new AHCI driver is having
+  problems detecting your drives.
+ * There is a boot menu option to disable the AHCI driver, which will
+   cause the kernel to fall back to the NATA driver.  Setting
+   hint.ahci.disabled=1 in /boot/loader.conf will accomplish the same
+   thing.
+
 ## Known Issues
 
 * Occasional panic after burning a CD.  This is a known issue