mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Invalid module format?
Date: Fri, 19 May 2006 13:21:08 -0700	[thread overview]
Message-ID: <20060519132108.ab528a59.rdunlap@xenotime.net> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA0012B3269@chicken.machinevisionproducts.com>

On Fri, 19 May 2006 11:38:23 -0700 Brian D. McGrew wrote:

> Seems my failure to post the complete set of files has caused great
> confusion.  Is that a sign of stress or frustration or both???  
> 
> Here is a complete listing of all the files, including the Makefile.  I
> think this is everything now.
> 
> I'm facing two problems.  First, the 2.6.16 kernel won't load this
> driver; throws an invalid module format as where 2.6.15 loads it just
> fine.
> 
> Secondly, the driver is supposed to allocate kernel memory that's
> accessable from userspace.  If you see the function
> alloc_ibb_user_shared(IbbSoftDev *) and the function
> alloc_ibb_image_table_mem(IbbSoftDev *, int); you'll see where I've a
> couple of attempts at calling __get_free_pages as well as a shot at
> vmalloc.  I've narrowed it down to this one section that's killing me.  
> 
> If anyone can offer help, that would be great because I'm just stuck on
> this and have been for six months!!!

Are you running the hardware/kernel in 32-bit mode?  or 64-bit?
(I don't know what a Dell PE1800 has/does.)
I'm guessing 32-bit due to all of the warnings I see in x86_64 mode.

The problem could be something as simple as the modules don't have
a MODULE_LICENSE() in them.  Are you running a RH/FC kernel or your
own custom kernel?  I get this when I load them:

ibb: module license 'unspecified' taints kernel.

I can load/unload both of them.

---
~Randy

  reply	other threads:[~2006-05-19 20:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 18:38 Brian D. McGrew
2006-05-19 20:21 ` Randy.Dunlap [this message]
2006-05-20 17:37   ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2006-05-19 17:23 Brian D. McGrew
2006-05-19 17:11 Brian D. McGrew
2006-05-19 17:19 ` Randy.Dunlap
2006-05-19 17:55 ` Randy.Dunlap
2006-05-19 21:35 ` Sam Ravnborg
2006-05-18 14:01 Brian D. McGrew
2006-05-19  1:50 ` Arjan van de Ven
2004-06-12  0:38 Invalid module format ? J.A. Magallon
2004-06-12  0:51 ` Matt H.
2004-06-12  0:55   ` J.A. Magallon

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=20060519132108.ab528a59.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=brian@visionpro.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®