Mention loading wifi interface driver in loader.conf for lagg.

[pauamma_gundo.com]

Summary

Requested by cperciva_ in EFNet #bsddocs.

See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246506.

Test Plan

Doc tested in lynx.
Instructions *not* tested due to lack of a wifi interface absent in GENERIC.

[cperciva]

I don't know what &rel121.current; &rel114.current; and &rel113.current; refer to -- are those 12.1-RELEASE, 11.4-RELEASE, and 11.3-RELEASE?

I would remove ", not <filename>/etc/rc.conf</filename>" -- on 12.1-RELEASE at least (maybe 11.x as well?) devmatch autoloads wifi drivers without them needing to be mentioned in rc.conf.

[pauamma_gundo.com]

In D25881#573256, @cperciva wrote:

I don't know what &rel121.current; &rel114.current; and &rel113.current; refer to -- are those 12.1-RELEASE, 11.4-RELEASE, and 11.3-RELEASE?

Yes, that's what they mean.

I would remove ", not <filename>/etc/rc.conf</filename>" -- on 12.1-RELEASE at least (maybe 11.x as well?) devmatch autoloads wifi drivers without them needing to be mentioned in rc.conf.

I just booted a 11.4 VM and it doesn't look (judging by "man devmatch" and "which devmatch") that devmatch is available there at all.

[cperciva]

Ah, I see. In that case, let's take mention of 11.3 and 11.4 out of this entirely -- on those systems, any way of loading the wifi drivers (loader.conf or rc.conf) will get them loaded early enough to have the device present before lagg is initialized.

The issue only exists on 12.1 (and 12.0, I suppose, but that's EoL) and the fix is "load the wifi driver explicitly rather than relying on devmatch" -- either loader.conf or rc.conf will work.

[pauamma_gundo.com]

In D25881#573303, @cperciva wrote:

Ah, I see. In that case, let's take mention of 11.3 and 11.4 out of this entirely -- on those systems, any way of loading the wifi drivers (loader.conf or rc.conf) will get them loaded early enough to have the device present before lagg is initialized.

OK, I'll remove them.

The issue only exists on 12.1 (and 12.0, I suppose, but that's EoL) and the fix is "load the wifi driver explicitly rather than relying on devmatch" -- either loader.conf or rc.conf will work.

Are you positive (eg, have you tested) that loading the driver in rc.conf will work as well? That's not what you seemed to me to be saying in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246506 and my notes from our IRC conversation, in both of which you mention loader.conf but not rc.conf.

[cperciva]

In D25881#573327, @pauamma_gundo.com wrote:

In D25881#573303, @cperciva wrote:

The issue only exists on 12.1 (and 12.0, I suppose, but that's EoL) and the fix is "load the wifi driver explicitly rather than relying on devmatch" -- either loader.conf or rc.conf will work.

Are you positive (eg, have you tested) that loading the driver in rc.conf will work as well? That's not what you seemed to me to be saying in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246506 and my notes from our IRC conversation, in both of which you mention loader.conf but not rc.conf.

I haven't tested, but /etc/rc.d/addswap has "REQUIRE: kld" and "BEFORE: netif" so it seems safe to assume that /etc/rc.d/kld will run before /etc/rc.d/netif.

I suspect that I simply forgot about the option of setting kld_list in rc.conf when I was debugging this earlier...

[pauamma_gundo.com]

• Address cperciva's review comments.

[bcr]

en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml

3749

I'd split this up into two sentences to make it easier to understand.

.. by adding <userinput><replaceable>driver</replaceable>_load="YES"</userinput> to it and rebooting.
A better way is to add the driver to ...

[pauamma_gundo.com]

• Split sentence per bcr's comment and change some of the too many "it"s in these sentences to more explicit phrases.

[bcr]

That looks good now. I'll get it committed. Thank you!