Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing to start up: kldstat: can't find file nmdm: No such file or directory #136

Open
1 task done
pgj opened this issue Oct 10, 2024 · 0 comments · May be fixed by #147
Open
1 task done

Failing to start up: kldstat: can't find file nmdm: No such file or directory #136

pgj opened this issue Oct 10, 2024 · 0 comments · May be fixed by #147
Labels
bug Something isn't working

Comments

@pgj
Copy link
Owner

pgj commented Oct 10, 2024

Description

On launching Wifibox, the following errors are emitted consistently:

kldstat: can't find file nmdm: No such file or directory
kldunload: can't find file nmdm
ERROR: nmdm.ko is loaded from a different location, but cannot be replaced.

Expected behavior: the application should start up without any errors.

Host operating system

FreeBSD XXX 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 #3 releng/14.1-n267718-524a425d30fc-dirty: Sat Oct  5 22:39:04 PDT 2024     root@xxx:/usr/obj/usr/src/amd64.amd64/sys/XXX amd64

Wireless NIC

N/A

Wifibox version

0.14.0

Disk image type and version

N/A

Changes to the default configuration files

bhyve.conf has console=yes

Logs

N/A

Additional context

The host runs a custom kernel has the nmdm kernel module included in the image.

Have you tried to turn it on and off?

  • Yes, I have read all the manual pages first!
@pgj pgj added the bug Something isn't working label Oct 10, 2024
pgj added a commit that referenced this issue Feb 7, 2025
The `assert_kmod_loaded` function expects kernel modules to be
loaded from a specified location and it fails to work if the
module in question has been actually added to the kernel.  This
case was not considered before because both `nmdm` and `vmm` are
shipped as optional, loadable modules with the stock FreeBSD
kernel, and that is usually not an issue.

Relax this restriction and allow working with built-in kernel
modules.  This way users with customized kernels would be
supported.  The original motivation behind this check is to ensure
that the loadable modules are created for a compatible kernel.
But that implicitly holds when they are included there.

Fixes #136
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant