VDR User wrote:
> On Sun, Mar 7, 2010 at 2:03 PM, Theodore Kilgore
> wrote:
>> It seems that the problem is solved by a local re-compile of the kernel plus
>> its modules, using the original distro .config settings in order to do this.
>> What I suspect has happened is that there was a simultaneou
On Sun, Mar 7, 2010 at 2:03 PM, Theodore Kilgore
wrote:
> It seems that the problem is solved by a local re-compile of the kernel plus
> its modules, using the original distro .config settings in order to do this.
> What I suspect has happened is that there was a simultaneous minor upgrade
> of gc
On Sun, 7 Mar 2010, VDR User wrote:
On Fri, Mar 5, 2010 at 7:37 PM, Mauro Carvalho Chehab
wrote:
I suspect that it may be related to this:
# Select 32 or 64 bit
config 64BIT
bool "64-bit kernel" if ARCH = "x86"
default ARCH = "x86_64"
---help---
Say yes to buil
On Sun, 7 Mar 2010, VDR User wrote:
On Fri, Mar 5, 2010 at 7:37 PM, Mauro Carvalho Chehab
wrote:
I suspect that it may be related to this:
# Select 32 or 64 bit
config 64BIT
bool "64-bit kernel" if ARCH = "x86"
default ARCH = "x86_64"
---help---
Say yes to buil
On Fri, Mar 5, 2010 at 7:37 PM, Mauro Carvalho Chehab
wrote:
> I suspect that it may be related to this:
>
> # Select 32 or 64 bit
> config 64BIT
> bool "64-bit kernel" if ARCH = "x86"
> default ARCH = "x86_64"
> ---help---
> Say yes to build a 64-bit kernel - formerl
ic to
debian or slackware. Even though you've got it working now, the
source of the problem should be investigated.
--
It's been several years since I last saw this error and I don't recall
what caused it then.
The message "Invalid module format" comes from either of modpro
t;> debian or slackware. Even though you've got it working now, the
>>>> source of the problem should be investigated.
>>>> --
>>>
>>> It's been several years since I last saw this error and I don't recall
>>> what caused it the
an or slackware. Even though you've got it working now, the
source of the problem should be investigated.
--
It's been several years since I last saw this error and I don't recall
what caused it then.
The message "Invalid module format" comes from either of modprobe and/o
;>>> I experienced the same problem and posted a new thread about it with
>>>> the subject "Problem with v4l tree and kernel 2.6.33". I'm a debian
>>>> user as well so apparently whatever is causing this is not specific to
>>>> debian
he problem should be investigated.
--
It's been several years since I last saw this error and I don't recall
what caused it then.
The message "Invalid module format" comes from either of modprobe and/or
insmod when the kernel returns ENOEXEC to a module (load) syscall.
Someti
he problem should be investigated.
--
It's been several years since I last saw this error and I don't recall
what caused it then.
The message "Invalid module format" comes from either of modprobe and/or
insmod when the kernel returns ENOEXEC to a module (load) syscall.
Someti
an or slackware. Even though you've got it working now, the
>> source of the problem should be investigated.
>> --
>
> It's been several years since I last saw this error and I don't recall
> what caused it then.
>
> The message "Invalid module format&
> source of the problem should be investigated.
> --
It's been several years since I last saw this error and I don't recall
what caused it then.
The message "Invalid module format" comes from either of modprobe and/or
insmod when the kernel returns ENOEXEC to a module (lo
On Fri, Mar 5, 2010 at 4:39 PM, Theodore Kilgore
wrote:
> This is to report the good news that none of the above suspicions have
> panned out. I still do not know the exact cause of the problem, but a local
> compile and install of the 2.6.33 kernel did solve the problem. Hence, it
> does seem tha
/gspca/gspca_hans_new3/gspca# modprobe
gspca_main
WARNING: Error inserting v4l1_compat
(/lib/modules/2.6.33-smp/kernel/drivers/media/video/v4l1-compat.ko): Invalid
module format
WARNING: Error inserting videodev
(/lib/modules/2.6.33-smp/kernel/drivers/media/video/videodev.ko): Invalid
module
WARNING: Error inserting v4l1_compat
(/lib/modules/2.6.33-smp/kernel/drivers/media/video/v4l1-compat.ko):
Invalid module format
WARNING: Error inserting videodev
(/lib/modules/2.6.33-smp/kernel/drivers/media/video/videodev.ko): Invalid
module format
FATAL: Error inserting gspca_main
(/lib
bugs in it which I've been told by
the manufacturer afterwards I do not recommend
to use it either it shortens the lifetime of most devices... Best is
to stick with windows unless the manufacturer and
chipdesigners support a driver.
WARNING: Error inserting videobuf_core (/lib/modules/2.6
On Wed, Sep 9, 2009 at 3:02 PM, Markus Rechberger wrote:
> this is not true my old driver which is not available anymore did not
> ship any other modules aside the em28xx driver itself.
> This is a video4linux issue and has nothing to do with it.
>
> Best Regards,
> Markus
>
Hello Marks,
While it
at is to say 2.6.30.5.
>>> The compilation of v4l-dvb works well (the kernel which is chosen is the
>>> right), but when I try to modprobe em28xx, I get this :
>>>
>>> WARNING: Error inserting videobuf_core (/lib/modules/2.6.30-tuxonice-
>>> r5/kernel
hosen is the
>> right), but when I try to modprobe em28xx, I get this :
>>
>> WARNING: Error inserting videobuf_core (/lib/modules/2.6.30-tuxonice-
>> r5/kernel/drivers/media/video/videobuf-core.ko): Invalid module format
>> WARNING: Error inserting videobuf_vmalloc
On Wed, Sep 9, 2009 at 2:34 PM, animatri...@gmail.com
wrote:
>
> I have this error, when I load the module :
> [ 2122.708062] em28xx: Unknown symbol v4l2_i2c_new_probed_subdev
> [ 2122.708402] em28xx: disagrees about version of symbol v4l2_i2c_subdev_addr
> [ 2122.708404] em28xx: Unknown symbol v4
On Wed, Sep 9, 2009 at 2:13 PM,
animatri...@gmail.com wrote:
> Without mrechberger version, I can't find support for my Pinnacle PCTV Usb
> stick.
> If I had it, (after having installed the mrec driver), I have this error :
>
> [ 909.128197] em28xx v4l2 driver version 0.0.1 loaded
> [ 909.128518]
;
> WARNING: Error inserting videobuf_core (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/videobuf-core.ko): Invalid module format
> WARNING: Error inserting videobuf_vmalloc (/lib/modules/2.6.30-tuxonice-
> r5/kernel/drivers/media/video/videobuf-vmalloc.ko): Invalid
23 matches
Mail list logo
