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
On Sun, 7 Mar 2010, Randy Dunlap wrote:
On 03/05/10 22:48, Theodore Kilgore wrote:
On Sat, 6 Mar 2010, Mauro Carvalho Chehab wrote:
Randy Dunlap wrote:
On 03/05/10 16:51, VDR User wrote:
On Fri, Mar 5, 2010 at 4:39 PM, Theodore Kilgore
wrote:
This is to report the good news that none
On 03/05/10 22:48, Theodore Kilgore wrote:
>
>
> On Sat, 6 Mar 2010, Mauro Carvalho Chehab wrote:
>
>> Randy Dunlap wrote:
>>> On 03/05/10 16:51, VDR User wrote:
On Fri, Mar 5, 2010 at 4:39 PM, Theodore Kilgore
wrote:
> This is to report the good news that none of the above suspic
On Sun, 7 Mar 2010, Mauro Carvalho Chehab wrote:
Theodore Kilgore wrote:
On Sat, 6 Mar 2010, Mauro Carvalho Chehab wrote:
Randy Dunlap wrote:
On 03/05/10 16:51, VDR User wrote:
On Fri, Mar 5, 2010 at 4:39 PM, Theodore Kilgore
wrote:
This is to report the good news that none of the abo
Theodore Kilgore wrote:
>
>
> On Sat, 6 Mar 2010, Mauro Carvalho Chehab wrote:
>
>> Randy Dunlap wrote:
>>> On 03/05/10 16:51, VDR User wrote:
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
> pan
On Sat, 6 Mar 2010, Mauro Carvalho Chehab wrote:
Randy Dunlap wrote:
On 03/05/10 16:51, VDR User wrote:
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 prob
On Sat, 6 Mar 2010, Mauro Carvalho Chehab wrote:
Randy Dunlap wrote:
On 03/05/10 16:51, VDR User wrote:
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 prob
Randy Dunlap wrote:
> On 03/05/10 16:51, VDR User wrote:
>> 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
On 03/05/10 16:51, VDR User wrote:
> 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 so
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
On Thu, 4 Mar 2010, Theodore Kilgore wrote:
Hi,
I just upgraded to the stock 2.6.33 kernel in Slackware-current. Also after
having the troubles described below I cloned a completely new copy of the
gspca tree from http://linuxtv.org/hg/~hgoede/gspca, intending to get some
work done on a p
On Wed, Sep 9, 2009 at 9:09 PM, Devin
Heitmueller wrote:
> 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
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
On Wed, Sep 9, 2009 at 9:02 PM, Markus Rechberger wrote:
> On Wed, Sep 9, 2009 at 6:19 PM, Devin
> Heitmueller wrote:
>> On Wed, Sep 9, 2009 at 12:14 PM, Edouard Marquez
>> wrote:
>>> Hello,
>>>
>>> I am using Gentoo with tuxonice-sources-2.6.3.0-r5 that is to say 2.6.30.5.
>>> The compilation of
On Wed, Sep 9, 2009 at 6:19 PM, Devin
Heitmueller wrote:
> On Wed, Sep 9, 2009 at 12:14 PM, Edouard Marquez wrote:
>> Hello,
>>
>> I am using Gentoo with tuxonice-sources-2.6.3.0-r5 that is to say 2.6.30.5.
>> The compilation of v4l-dvb works well (the kernel which is chosen is the
>> right), but w
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]
On Wed, Sep 9, 2009 at 12:14 PM, Edouard Marquez wrote:
> Hello,
>
> I am using Gentoo with tuxonice-sources-2.6.3.0-r5 that 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 in
22 matches
Mail list logo
