Am 03.07.2013 um 18:34 schrieb Darac Marjal:
On Mon, Jul 01, 2013 at 04:05:13PM +0200, Helmut Wollmersdorfer wrote:
how can I find out the version number of a particular kernel module
without downloading, without installing, without booting, from
https://git.kernel.org/cgit/linux/kernel/gi
On Mon, Jul 01, 2013 at 04:05:13PM +0200, Helmut Wollmersdorfer wrote:
> Hi,
>
> how can I find out the version number of a particular kernel module
> without downloading, without installing, without booting, from
>
Taking, as an example, uinput:
> - the kernel source repository
https://git.ke
On 07/02/2013 02:54 AM, Helmut Wollmersdorfer wrote:
Am 01.07.2013 um 17:52 schrieb Wayne Topa:
On 07/01/2013 10:05 AM, Helmut Wollmersdorfer wrote:
I.e. I would like the version number of a kernel module (e.g. drbd,
megaraid_sas, igb) before deciding to download, compile, or install.
#
Am 01.07.2013 um 17:52 schrieb Wayne Topa:
On 07/01/2013 10:05 AM, Helmut Wollmersdorfer wrote:
I.e. I would like the version number of a kernel module (e.g. drbd,
megaraid_sas, igb) before deciding to download, compile, or install.
# apt-cache search linux-image |grep ^linux
HTH
That'
On 07/01/2013 10:05 AM, Helmut Wollmersdorfer wrote:
Hi,
how can I find out the version number of a particular kernel module
without downloading, without installing, without booting, from
- the kernel source repository
- the debian source package
- the debian binary package
- the running kernel
Hi,
how can I find out the version number of a particular kernel module
without downloading, without installing, without booting, from
- the kernel source repository
- the debian source package
- the debian binary package
- the running kernel, or the loaded modules
I.e. I would like the vers
Hallo,
bei dem Versuch das Treibermodul für meine D-Link DFE-550TX Karte zu
kompilieren, scheitere ich nach "insmod modul.o" an folgender Fehlermeldung:
modul.o: kernel-module version mismatch
modul.o was compiled for kernel version 2.4.18
while this kernel is version
Pann McCuaig wrote:
>
> On Wed, Feb 06, 2002 at 14:24, Xeno Campanoli wrote:
> [EMAIL PROTECTED]:~$ dpkg -S /usr/include/linux/version.h
> libc6-dev: /usr/include/linux/version.h
>
> Best guess is that the current libc6 in potato was built on a machine
> running kernel-2.2.20. Sorta tacky consid
Pann McCuaig wrote:
>
> On Wed, Feb 06, 2002 at 14:24, Xeno Campanoli wrote:
>
> > I do this:
> >
> > inneal:~# cat /usr/include/linux/version.h | grep 2.2.20
> > #define UTS_RELEASE "2.2.20"
> >
> > and doing it with 2.2.19 finds nothing. This got updated from one
> > greater than the last kern
Xeno Campanoli wrote:
>
> I'm trying to do the example on pages 13-14 of Rubini's Linux Device
> inneal:~/study# insmod hello.o
> hello.o: kernel-module version mismatch
> hello.o was compiled for kernel version 2.2.20
> while this kernel is version
I'm still looking for an answer to this, and I'm sorry if I missed any
that was posted.
I'm trying to do the example on pages 13-14 of Rubini's Linux Device
Driver
book, and I get the following diagnostic message when I do an insmod:
inneal:~/study# insmod hello.o
hello.o: k
4 etc... (see web page)
3. make modules
4. make modules_install
5. depmod -a
This has raised a lot of unresolved dependencies...but not for yellowfin.o .
6. insmod yellowfin.o
And again the same error:
/lib/modules/2.0.30/misc/yellowfin.o: kernel-module version mismatch
/lib/modules/2.0.30
Hi,
I take it these are third party kernel modules you are trying
to compile and run. Welcome to the bleeding edge.
Firstly, this is likely to be tricky. Secondly, you need to
compile the module using the 2.0.32 kernel header files
(judicious use of -I/usr/src/linux/include/ in
Hi,
When I try insmod paride, which was compiled my me running kernel 2.0.32
and /usr/src/linux is link against 2.0.32 kernel, I get this error:
/lib/modules/2.0.32/misc/paride.o: kernel-module version mismatch
/lib/modules/2.0.32/misc/paride.o was compiled for kernel version 2.0.29
On Mon, 30 Jun 1997 13:35:59 BST Matthew ([EMAIL PROTECTED])
wrote:
[snip]
> I compiled the 'module' and did an insmod. Lo and Behold my CDROM drive
> worked. I'm impressed. It took some digging, but I got it to work.
>
> Now. The only problem I have is that when I insmod the 'module' I get a
I'm a bit of a Linux & Debian Newbie, so excuse me if this is a bit of a
dumb question.
I've recently changed the setup if my machine. I have two IDE hard disks
and an IDE CD-ROM drive (Oh I wish I could afford SCSI).
My motherboard is a Pentium Triton type thing with two on-board IDE
channels. I
16 matches
Mail list logo
