Hi Andriy,
> if you escape to prompt directly loader didn't loaded all it's config
> so there is no modulepath defined, you need to 'boot-conf' to load the
> configuration files.
You might prefer to use 'read-conf' instead of interrupting 'boot-conf''s
countdown.
Regards.
--
Olivier Certner
Whoops, meant cli.lua(8), of course.
> On 20. Oct 2022, at 13:58, Toomas Soome wrote:
>
>
> the problem with ‘?’ command is that it only does list commands written in C,
> it does not list scripted commands. cli_lua(8) should list lua specific ones.
> And at least my stable/13 branch does
the problem with ‘?’ command is that it only does list commands written in C,
it does not list scripted commands. cli_lua(8) should list lua specific ones.
And at least my stable/13 branch does seem to confirm, enable-module,
disable-module, toggle-module and show-module-options should be
On 20/10/2022 13:20, Toomas Soome wrote:
Also, instead of manual load, you may want to use enable-module.
Emmanuel, Toomas,
thank you very much for the suggestions.
It seems like my installation may be messed up or outdated somehow, see below
(and sorry about those ^M-s). I do not seem to
Also, instead of manual load, you may want to use enable-module.
Sent from my iPhone
> On 20. Oct 2022, at 13:08, Emmanuel Vadot wrote:
>
> On Thu, 20 Oct 2022 13:03:26 +0300
> Andriy Gapon wrote:
>
>>
>> I recently needed to recover a system by manually preloading a driver.
>> To a bit of
On Thu, 20 Oct 2022 13:03:26 +0300
Andriy Gapon wrote:
>
> I recently needed to recover a system by manually preloading a driver.
> To a bit of surprise, simple 'load $modname' did not work, I had to use 'load
> /boot/kernel/$modname.ko'. I didn't have to do this in a long time, but I
>
I recently needed to recover a system by manually preloading a driver.
To a bit of surprise, simple 'load $modname' did not work, I had to use 'load
/boot/kernel/$modname.ko'. I didn't have to do this in a long time, but I
recall that the short command used to work. Additionally, required
