Update the instructions for loading wifi drivers on FreeBSD versions

with or without devmatch. Mention that loading of drivers in
loader.conf or via rc.conf may be required for certain versions. It
should be done in order to have the lagg interface properly set up
at boot time.

Thanks to Pau Amma for providing the patch.
While here, fix some overly long lines in the note above.

PR:             246506 (documentation part)
Submitted by:   pauamma_gundo.com
Requested by:   cperciva (on IRC)
Reviewed by:    cperciva, bcr
Approved by:    bcr
Differential Revision:  https://reviews.freebsd.org/D25881
This commit is contained in:
Benedict Reuschling 2020-07-30 15:39:50 +00:00
parent 6175d3e6e8
commit b2b4206ac7
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=54386

View file

@ -3732,11 +3732,27 @@ ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover
interface.</para>
<note>
<para>In theory, either the Ethernet or wireless MAC address can
be changed to match the other. However, some popular wireless
interfaces lack support for overriding the MAC address. We
therefore recommend overriding the Ethernet MAC address for this
purpose.</para>
<para>In theory, either the Ethernet or wireless MAC address
can be changed to match the other. However, some popular
wireless interfaces lack support for overriding the MAC
address. We therefore recommend overriding the Ethernet
MAC address for this purpose.</para>
</note>
<note>
<para>If the driver for the wireless interface is not loaded
in the <literal>GENERIC</literal> or custom kernel,
and the computer is running &os;&nbsp;&rel121.current;,
load the corresponding <filename>.ko</filename> in
<filename>/boot/loader.conf</filename> by adding
<userinput><replaceable>driver</replaceable>_load="YES"</userinput>
to that file and rebooting. Another, better way is to
load the driver in <filename>/etc/rc.conf</filename> by
adding it to <varname>kld_list</varname> (see
&man.rc.conf.5; for details) in that file and rebooting.
This is needed because otherwise the driver is not loaded
yet at the time the &man.lagg.4; interface is set
up.</para>
</note>
<para>In this example, the Ethernet interface,