[OpenAFS] problem with openafs on a recompiled 2.4.20-8 kernel
Johann Cohen-Tanugi
johann.cohen@pi.infn.it
12 Jun 2003 17:28:51 +0200
On Thu, 2003-06-12 at 17:06, Derek Atkins wrote:
> If you are going to reconfigure a Red Hat kernel then you MUST
> remove the pre-computed ksyms from include/linux/modules/*
>
ok, currently I have:
[root@localhost linux-2.4.20-18.9]# ls ../linux-2.4.20-8/
include/linux/modules/
processor.stamp processor.ver
stamp is 0 size (ok) and ver has a line about acpi. I don't know why
these only are here, but essentially there is nobody in there...
On the contrary I am currently trying to compile the newer .20-18.9
kernel and there indeed there is a galaxy of such pairs .stamp .ver.
Let see, what you are saying is that maybe I recompiled the kernel with
all these syms present in include/linux/modules/ dir. As a result,
everything went fine (kernel and modules compilation + installlation +
boot and use) but it would impede somehow the compilation of 3rd party
source, even if now these symbols have disappeared. Am I understanding
correctly?
In such a case I am a bit surprised that nobody has mentioned it in the
doc I read, but I believe you :)
I am going to try removing these from the newer kernel directory and see
if this solve my compilation problem.
Let me know if I understood correctly you point, in which case I will
recompile the 2.4.20-8 kernel as well.
Johann
> -derek
>
> Johann Cohen-Tanugi <johann.cohen@pi.infn.it> writes:
>
> > Hi,
> > thanks for answering quickly.
> >
> > On Thu, 2003-06-12 at 16:20, Derek Atkins wrote:
> > > Did you completely remove Red Hat's ksyms before you rebuilt your
> > > kernel with a different configuration?
> > >
> > I had no clue about it until you mentioned it. Then I looked at the man
> > of ksyms, etc.... So, to answer your question I never did anything about
> > these symbols. Can you tell me more about removing ksyms? I never saw
> > any mention of it before! I just make xconfig,, make dep, make bzImage,
> > modules etc...
> > But as a matter of fact I am currently experiencing problems compiling
> > kernel 2.4.20-18.9 modules andit seems to be a config problems because
> > it incorrectly parse kernel.h and/or module.h, starting at lines using
> > "extern"
> >
> > > Were your kernel sources available when you rebuilt AFS? Did
> > > AFS find them?
> > >
> > yes to both questions.
> >
> >
> > Please let me know what you expect me to do about these ksyms before
> > compiling.... Note that I also tried the binaries provided by openAFS...
> > Why would these also fail?
> >
> > thanks,
> > Johann
> >
> > > -derek
> > >
> > > Johann Cohen-Tanugi <johann.cohen@pi.infn.it> writes:
> > >
> > > > Hi,
> > > > I recompiled 2.4.20-8 in order to get acpi support on my laptop. Now I
> > > > would like to get afs to work. I tried both the binary release and the
> > > > sources that I recompiled using rpmbuild -bb
> > > >
> > > >
> > > > In both cases, I get the following:
> > > >
> > > > [root@localhost redhat]# service afs start
> > > > Hmm... I can't seem to find an AFS kernel module suitable for your
> > > > Linux
> > > > kernel. That means you will need to build or obtain a suitable module.
> > > > The following information may be of some use in obtaining assistance:
> > > > CPU Type: 1586.intel.2
> > > > Linux version: 2.4.20-8 #7 Wed May 21 19:26:33 CEST 2003
> > > > RedHat release: Red Hat Linux release 9 (Shrike)
> > > > Symbol versions:
> > > > iget4 7b369432
> > > > iget4 7b369432
> > > > sock_create 7a0451b7
> > > > Did not find matching module in SymTable
> > > > Failed to load AFS client, not starting AFS services.
> > > >
> > > > [root@localhost redhat]# insmod
> > > > /usr/vice/etc/modload/libafs-2.4.20-8-i586.o
> > > > /usr/vice/etc/modload/libafs-2.4.20-8-i586.o: unresolved symbol
> > > > sock_release_R69bcec9f
> > > > /usr/vice/etc/modload/libafs-2.4.20-8-i586.o: unresolved symbol
> > > > sock_create_R13178b72
> > > > /usr/vice/etc/modload/libafs-2.4.20-8-i586.o: unresolved symbol
> > > > zone_table_R4b76a6ed
> > > > /usr/vice/etc/modload/libafs-2.4.20-8-i586.o: unresolved symbol
> > > > sock_recvmsg_R1244a0c2
> > > > /usr/vice/etc/modload/libafs-2.4.20-8-i586.o: unresolved symbol
> > > > sock_sendmsg_R57ce31c5
> > > > /usr/vice/etc/modload/libafs-2.4.20-8-i586.o:
> > > > Hint: You are trying to load a module without a GPL compatible license
> > > > and it has unresolved symbols. The module may be trying to access
> > > > GPLONLY symbols but the problem is more likely to be a coding or
> > > > user error. Contact the module supplier for assistance, only they
> > > > can help you.
> > > >
> > > >
> > > >
> > > > note that all the drivers fail with these types of messages. This one
> > > > has the fewest....
> > > > thanks for any help.
> > > >
> > > > Johann
> > > >
> > > > _______________________________________________
> > > > OpenAFS-info mailing list
> > > > OpenAFS-info@openafs.org
> > > > https://lists.openafs.org/mailman/listinfo/openafs-info
> >