hello. Following up on my module question of last night, I now have
the module loading
and unloading successfully. However, when I try to open the devices I've
associated with the
module, I get a device not configured error.
Under NetBSD-5, Major number 196 was available, and the ope
Hi,
I've restarted working on a micro-NetBSD project I've documented back in 2020
here:
https://imil.net/blog/posts/2020/fakecracker-netbsd-as-a-function-based-microvm/
The idea being to create a micro-service virtual machine that starts a NetBSD
kernel and a dedicated service in less than 200
hello. Thank you so much for the answer. Yes, the problem was that I
had two source
files that declared they wer a module. Since they were modules of different
names, I assumed
they could all be compiled into one object file. A small change to the code
has allowed me to
compile the
WARNING: module error: `link_set_modules' section wrong size (got 16,
wanted 8)
WARNING: module error: cannot fetch info for `zaptel', error 8
Yeah, I chased this down some time back: I wanted to load the DRMKMS
modules on the command-line like you can with Linux/FreeBSD, but,
coudn't because
On Mon, 30 Jan 2023, Brian Buhrow wrote:
[...] but when I try to perform a modload on the
final .kmod file, I get the following output:
DEBUG: module: Loading module from
/stand/amd64/9.99.77/modules/zaptel/zaptel.kmod
DEBUG: module: Loading plist from
/stand/amd64/9.99.77/modules/zaptel/zap
