public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian Groessler" <cpg@aladdin.de>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] kernel modules
Date: Fri, 21 Jul 2000 15:08:58 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205220@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205210@msgid-missing>



Hi,

On 07/19/2000 04:44:08 PM GMT "Stephens, Mike" wrote:
>
>> But it crashed at load time. The crash seems to be happening at
>> a function call itself, as a printk exactly before the call is
>> displayed and a printk right at the beginning of the called
>> function isn't. Seems like the module hasn't been linked
>> correctly.
>Unless you make changes to the Makefile they don't get linked correctly.
>The current IA64 version modutils can't load a module if it (or the
kernel)
>was compiled with the -mconstant-gp flag, which is part of the CFLAGS
define
>in arch/ia64/Makefile.
>
>Using a 2.4.0-test1 + 0609 patch (or newer kernel) and compile without the
>constant-gp flag about 95% of the modules I have tried work.

Thanks. When compiling w/o constant-gp the parport modules work, but...

>>
>> Then I upgraded modutils to 2.3.12, and now when I do lsmod
>> it aborts with "get_kernel_syms: Function not implemented".
>This is caused by a problems in the configure and makefile that
>cause the modutils to get link wrong for IA64. The quick fix is
>add USE_SYSCALL=n to the top of util/Makefile.

Regardless of USE_SYSCALL=n is there or not, I get the "Function
not implemeted" error with modutils-2.3.12.
I reverted to using the (precompiled) modutils which came on
the RedHat CD...

regards,
chris





      parent reply	other threads:[~2000-07-21 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-19 13:45 [Linux-ia64] kernel modules Christian Groessler
2000-07-19 16:44 ` Stephens, Mike
2000-07-21 15:08 ` Christian Groessler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590678205220@msgid-missing \
    --to=cpg@aladdin.de \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox