loader and/or documentation broken
The ehci driver is automatically loaded upon boot. To disable this
behavior temporarily, the ehci_load variable can be unset at the loader
prompt (see loader(8)). To disable it permanently, the
hint.ehci.0.disabled tunable can be set to 1 in /boot/loader.conf.
But when operating from the loader prompt the ehci_load variable has no effect
at all, it seems to only be checked from the menu, which is useless if you are
operating from the prompt.
This is confusing at best, but I am leaning more towards steaming pile. The
loader or the documentation needs to be reworked.
#1 Updated by swildner over 2 years ago
I agree the loader(8) docs need upgrading. In fact, I even wholeheartedly
agree. Nothing of the dloader stuff Matt did touched the documentation
unfortunately, so it's pretty much in the state we had before.
That said, I don't think this particular issue is related to the docs not being
up-to-date, though. What did you do exactly to prevent loading ehci.ko? Note
that the variable has to be _unset_ (as the manpage says) and not _set_ to NO
#2 Updated by thomas.nikolajsen over 2 years ago
on loader prompt works.
The problem is local vs kernel env variables:
set / unset works on kernel env variables only;
this can have the effect that a variable has an instance
both as local and kernel env variable, but with different value.
IMO set / unset should also do operation on local variable.
Local variables was introduced by dloader, mainly to store menu stuff,
which the kernel has no use for.
I did update loader docs (man & help file) after dloader introduction,
so I think it is in a rather good shape :)
#3 Updated by swildner over 2 years ago
On Sun, 09 Oct 2011 23:13:37 +0200, Thomas Nikolajsen (via DragonFly issue
tracker) <firstname.lastname@example.org> wrote:
> Thomas Nikolajsen <email@example.com> added the comment:
> on loader prompt works.
> The problem is local vs kernel env variables:
> set / unset works on kernel env variables only;
> this can have the effect that a variable has an instance
> both as local and kernel env variable, but with different value.
> IMO set / unset should also do operation on local variable.
> Any objections?
Isn't there lunset for this purpose?
> Local variables was introduced by dloader, mainly to store menu stuff,
> which the kernel has no use for.
> I did update loader docs (man & help file) after dloader introduction,
> so I think it is in a rather good shape :)
Oops, sorry, must've forgot that.
#5 Updated by thomas.nikolajsen over 2 years ago
Or (will do same; forgot I had done 2nd cmd below):
I have committed fix: just description of kenv vs local variables.
Problem is wrong docs, as you write, we didn't note that 'loadall'
uses local (_load) vars and 'boot' uses (the old) kenv vars.
Same problem for acpi_load.
After release I might fix loader to remove this confusing
(schizophrenic ?) facility that a variable can have two instances with
different value; I see no use for it.