> > > Now, if even this one can't be resolved, some must be
> wrong with your
> > > setup.
>
> With 'setup' I mean glibc/kernel headers issues.
> As dosnet needs the _real_ kernel headers, it may lead to problems
> when the glibc /usr/include does have copies of the kernel headers
> instead of a symlink to the kernel for which the module is intended.
>
Well, I've checked and i have /usr/include/linux as a symlink to
/usr/src/linux/include where are all the .h files. It doesn't seem a problem
with header files, because in the compilation there's no problem, i.e. not
even a warning.
The problem only happens when i do a insmod dosnet.o or modprobe dosnet.o.
Can be a problem of modutils? In this box I have modutils 2.1.86-9 (redhat
5.2 default version). In the other machne where it worked, I've updates to
modutils 2.1.121 (not sure, can't check now), because of kernel 2.2.x, so I
suspect that this may have something to do with this. And I've seen that I'm
not the only one thos find this behavior in dosnet.o.
> what, that its not normal if printk doesn't resolve? ;-)
>
I know, but why doesn't this happen in other modules? Yes, they use printk.
:)
> The original Author (Vinod) tested it at 1.x, but it was
> reworked later by
> Marcus and AFAIK he tested it under the latest kernels.
Ok, I didn't knew that. But still, i find this strange because it worked in
2.2.3 kernel (system updated with other packages necessary to make 2.2.3
work). Do you need any further details about the system where this fails?
Package versions os something like that?
regards,
--
Mario Moreira
DID/CET Portugal Telecom
+351 34 8913200
