From: Dmitriy Geels <dmitriy.geels@gmail.com>
To: Alek Du <alek.du@intel.com>
Cc: Anssi Hannula <anssi.hannula@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: hid-pidff bug: fails to find all required reports of saitek gamepad
Date: Tue, 9 Jun 2009 11:37:30 +0400 [thread overview]
Message-ID: <78f5d6bf0906090037j7ec79074je8517b2c8c88369a@mail.gmail.com> (raw)
In-Reply-To: <20090609140949.78d4448a@dxy.sh.intel.com>
As I understood, since some alpha, ubuntu packagers enabled module
versioning. I used old ubuntu alpha in virtualbox to test changes
(also I used my own built kernel there), now I tried to build module
for current running kernel.
Some discussions, I found about this error, tell that Module.symvers
is somehow causing it. Copying Module.symvers from current kernel
headers didn't help.
But I know that it is possible to build module -- dkms builds 3
modules successfully. I just didn't find out how to do this.
2009/6/9 Alek Du <alek.du@intel.com>:
> Seems your module was not compiled against your running kernel. Are you using the right tree and config?
>
> On Tue, 9 Jun 2009 13:02:45 +0800
> Dmitriy Geels <dmitriy.geels@gmail.com> wrote:
>
>> Now it built ok, but for some reason kernel doen't like new module:
>> dmig@dmig-laptop:~/workspace/linux-source-2.6.29$ sudo insmod
>> drivers/hid/usbhid/usbhid.ko
>> insmod: error inserting 'drivers/hid/usbhid/usbhid.ko': -1 Invalid module format
>>
>> Have any idea why?
next prev parent reply other threads:[~2009-06-09 7:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 19:45 hid-pidff bug: fails to find all required reports of saitek gamepad Dmitriy Geels
2009-02-02 15:50 ` Anssi Hannula
2009-02-02 18:29 ` Dmitriy Geels
2009-02-02 18:48 ` Dmitriy Geels
2009-02-07 12:28 ` Anssi Hannula
[not found] ` <78f5d6bf0902092146x2abaf45an79e4546e75a80356@mail.gmail.com>
2009-02-10 7:49 ` Dmitriy Geels
2009-02-10 7:49 ` Fwd: " Dmitriy Geels
2009-02-10 16:06 ` Anssi Hannula
2009-02-11 9:12 ` Dmitriy Geels
2009-02-11 16:27 ` Anssi Hannula
2009-02-12 18:06 ` Dmitriy Geels
2009-02-12 18:42 ` Anssi Hannula
2009-02-13 8:33 ` Dmitriy Geels
2009-02-13 19:43 ` Anssi Hannula
[not found] ` <78f5d6bf0902141125m1bf9ac00xb2b414e81d81b869@mail.gmail.com>
[not found] ` <49972478.3060207@gmail.com>
2009-02-14 22:33 ` Dmitriy Geels
2009-02-17 12:16 ` Dmitriy Geels
2009-02-18 15:45 ` Anssi Hannula
2009-02-19 6:56 ` Dmitriy Geels
[not found] ` <78f5d6bf0902182254v191cc485x62eb211baaddd36@mail.gmail.com>
[not found] ` <499D7C66.6090000@gmail.com>
2009-02-26 21:21 ` Dmitriy Geels
2009-02-27 16:24 ` Anssi Hannula
2009-03-02 18:41 ` Dmitriy Geels
2009-03-02 20:35 ` Anssi Hannula
2009-03-03 6:28 ` Dmitriy Geels
2009-03-03 18:35 ` Dmitriy Geels
2009-03-07 14:38 ` Anssi Hannula
2009-03-08 5:18 ` Dmitriy Geels
2009-03-08 10:16 ` Anssi Hannula
2009-03-09 19:08 ` Dmitriy Geels
2009-05-07 23:45 ` Anssi Hannula
2009-05-07 23:57 ` Anssi Hannula
[not found] ` <78f5d6bf0906041227w3a58bde0u554a3d3336e17fa6@mail.gmail.com>
2009-06-06 12:14 ` Anssi Hannula
2009-06-09 5:02 ` Dmitriy Geels
2009-06-09 6:09 ` Alek Du
2009-06-09 7:37 ` Dmitriy Geels [this message]
2009-06-11 9:38 ` Dmitriy Geels
2009-06-11 20:11 ` Dmitriy Geels
2009-07-09 17:41 ` Dmitriy Geels
2009-07-09 17:58 ` Anssi Hannula
2009-11-06 9:06 ` Dmitriy Geels
2009-11-09 12:00 ` Dmitriy Geels
2009-11-20 14:17 ` Dmitriy Geels
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=78f5d6bf0906090037j7ec79074je8517b2c8c88369a@mail.gmail.com \
--to=dmitriy.geels@gmail.com \
--cc=alek.du@intel.com \
--cc=anssi.hannula@gmail.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).