Re: [njbfs-devel] Whats up?

[<joe...@ne...>]

> depmod -ae
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19/kernel/fs/njbfs/njbfs.o
> depmod:         _mmx_memcpy
> depmod:         schedule_timeout
> depmod:         __generic_copy_from_user
> depmod:         usb_bulk_msg
> depmod:         generic_file_write
> depmod:         unlock_page

This shouldn't happen. Maybe depmod is confused. E.g. you build a kernel =
from=20
source but you have different headers in /usr/include/linux. Or the kerne=
l=20
build wasn't clean, disturbed by older kernel object files, maybe a missi=
ng=20
'make mrproper'.

> Tomorrow I'm heading off to the bookstore to pick up the linux drivers
> o'reilly book. I tried tracking down what was causing the unresolved
> symbols to gain insight into why modules_init was failing. I didnt get =
too
> far with that, but I did learn a bit about how modules work.

The O'Reilly book is a little bit outdated, it relies more on the 2.2 ker=
nel.
The missing symbols are generated by the tools of the modutils package by=
=20
Keith Owens, and I think it is a build problem. There can be changed symb=
ol=20
exports between 2.4.18 and 2.4.19 - which I do not expect - or a version=20
mismatch of kernel modules/kernel object files. Modutils has a sophistica=
ted=20
method to recognize different kernel versions.

> Anyways, I figured I'd just pass on the info in case anyone notices any
> glaring errors in what I'm doing or had any suggestions as to things to
> try.

Thank you, it helps a lot, if I get the same messages.

J=F6rg