It might be worth explaining how to load firmware during a fresh install, and warn about the dangers of mounting over /mnt. This functionality was introduced in 4.4.
While getting online for an install is not really necessary, I like to download my sets from the internet. Index: faq/faq4.html =================================================================== RCS file: /cvs/www/faq/faq4.html,v retrieving revision 1.479 diff -u -p -r1.479 faq4.html --- faq/faq4.html 3 Sep 2016 13:53:40 -0000 1.479 +++ faq/faq4.html 9 Dec 2016 08:42:12 -0000 @@ -42,6 +42,7 @@ <li><a href="#Signify" >Problems with signatures</a> <li><a href="#site" >Customizing the install process</a> <li><a href="#Multibooting">Multibooting</a> +<li><a href="#Firmware" >Loading firmware</a> </ul> <hr> @@ -954,6 +955,28 @@ Writing MBR at offset 0. </pre></blockquote> To discard all unwritten changes, use <tt><b>exit</b></tt> instead. + +<h2 id="Firmware">Loading firmware</h2> + +The ramdisk kernel will look for firmware in <tt>/mnt/etc/firmware</tt>. + +<p> +For example, if you need to use the <tt>iwm</tt> driver, get the necessary firmware package from +<a href="http://firmware.openbsd.org/firmware/";>http://firmware.openbsd.org/firmware/</a>, +extract it and put it on a USB drive in the <tt>etc/firmware</tt> directory. +Then, before starting the install script, drop to a shell, mount the drive in <tt>/mnt</tt> and reload the interface: + +<blockquote><pre> +ifconfig iwm0 down +ifconfig iwm0 up +</pre></blockquote> + +And then unmount the drive. + +<p> +Be aware that the installer uses <tt>/mnt</tt> to copy the +distribution sets to disk, and thus loading the firmware must be +performed before it is started. <p> </body> -- Michal Mazurek
