Re: Hauppauge ImpactVCB-e 01385

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

Hi Hans,

Well I'll confirm that tomorrow. To me it looks like 320x240 scaled with a corresponding loss of detail.

I'll see if I can find a nice test image to use to show the difference clearly in comparison to the stk1160 at the same resolution. The ImpactVCB-e should be better but it isn't. The stk1160 s-video at 640x480 is much better than the ImpactVCB-e on either composite or s-video.

Regards

Hans Verkuil <hverkuil@xs4all.nl> wrote:

>On 04/16/2014 07:11 PM, Steve Cookson wrote:
>> Hi Guys,
>> 
>> On 14/04/14 15:02, Hans Verkuil wrote:
>> 
>>  > I'd appreciate it if you can test this with a proper video feed.
>> 
>> Ok, here is the first issue:
>> 
>> 1) I have a 640x480 video feed which displays appropriately through 
>> stk1160, but only displays at 320x240 in ImpactVCBe.
>> 
>> In fact this is the same issue I had last year with:
>> 
>> echo cx23885 card=5 | sudo tee -a /etc/modules
>> 
>> Is your card giving you 640x480?
>
>For no good reason AFAICT the initial resolution is set to 320x240. But
>you can just set it to 640x480 (or more likely, 720x480 for NTSC or
>720x576 for PAL):
>
>v4l2-ctl -v width=640,height=480
>
>Regards,
>
>	Hans
>--
>To unsubscribe from this list: send the line "unsubscribe linux-media" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

On 16/04/14 19:15, Steve Cookson wrote:
> For no good reason AFAICT the initial resolution is set to 320x240. But
> >you can just set it to 640x480 (or more likely, 720x480 for NTSC or
> >720x576 for PAL):
> >
> >v4l2-ctl -v width=640,height=480
Hi Guys,

The attachments here are sent using tinypic.com.  It's the first time 
I've used it, so I hope it works OK.

I'm using the qv4l utility, but I did try it on v4l2-ctl and gst-launch 
and the results are the same as the one's I shall post here.

Firstly, here is stk1160 s-video for a baseline comparison.  Look at the 
word "File" in the file menu:

- http://tinypic.com/m/i50k8z/2

Now here is ImpactVCB-e composite.  Again look at the word "File" in the 
file menu:

- http://tinypic.com/m/i50k8n/2

The quality is a little worse, but maybe that is just 
Composite/S-Video.  Composite is not working on my stk1160, so I can't 
do a direct comparison.

Now let's look at ImpactVCB-e s-video:

- http://tinypic.com/m/i50k8w/2

It looks like every other line is missing.  I'd guess it's 640x240. I've 
tried v4l2-ctl -v width=640,height=480 etc, but no difference.

You can see it too with images but it's just not so obvious as with text.

Now when I switch back to ImpactVCB-e composite, I get the same problem, 
but after a restart it goes away.

What do you think?

Regards

Stev

Re: Hauppauge ImpactVCB-e 01385

[Hans Verkuil]

On 04/17/2014 11:18 AM, Steve Cookson wrote:
> 
> On 16/04/14 19:15, Steve Cookson wrote:
>> For no good reason AFAICT the initial resolution is set to 320x240. But
>>> you can just set it to 640x480 (or more likely, 720x480 for NTSC or
>>> 720x576 for PAL):
>>>
>>> v4l2-ctl -v width=640,height=480
> Hi Guys,
> 
> The attachments here are sent using tinypic.com.  It's the first time 
> I've used it, so I hope it works OK.
> 
> I'm using the qv4l utility, but I did try it on v4l2-ctl and gst-launch 
> and the results are the same as the one's I shall post here.
> 
> Firstly, here is stk1160 s-video for a baseline comparison.  Look at the 
> word "File" in the file menu:
> 
> - http://tinypic.com/m/i50k8z/2
> 
> Now here is ImpactVCB-e composite.  Again look at the word "File" in the 
> file menu:
> 
> - http://tinypic.com/m/i50k8n/2
> 
> The quality is a little worse, but maybe that is just 
> Composite/S-Video.  Composite is not working on my stk1160, so I can't 
> do a direct comparison.
> 
> Now let's look at ImpactVCB-e s-video:
> 
> - http://tinypic.com/m/i50k8w/2
> 
> It looks like every other line is missing.  I'd guess it's 640x240. I've 
> tried v4l2-ctl -v width=640,height=480 etc, but no difference.
> 
> You can see it too with images but it's just not so obvious as with text.
> 
> Now when I switch back to ImpactVCB-e composite, I get the same problem, 
> but after a restart it goes away.
> 
> What do you think?

Looks like a driver bug to me. This driver needs some TLC, which I plan on
giving, but I need to finish a bunch of other stuff first.

Just use composite in the meantime.

Regards,

	Hans

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

>The issue is nobody cares enough to 
>update the driver to support
>your card and make it work out of the box.

Hi Steve,

Thanks for your response.

Well not nobody because I do.  How do I do it? If you would guide me through, I will happily update it.

Regards

Steve.

Steven Toth <stoth@kernellabs.com> wrote:

>> When I plug in my 01385 I get the same old stuff in dmseg, ie:
>>
>> cx23885 driver version 0.0.3 loaded
>> [ 8.921390] cx23885[0]: Your board isn't known (yet) to the driver.
>> [ 8.921390] cx23885[0]: Try to pick one of the existing card configs via
>> [ 8.921390] cx23885[0]: card=<n> insmod option. Updating to the latest
>> [ 8.921390] cx23885[0]: version might help as well.
>> [ 8.921393] cx23885[0]: Here is a list of valid choices for the card=<n>
>> insmod option:
>>
>> Etc.
>>
>> Does anyone have any idea of the issue here?
>
>Sure. The issue is nobody cares enough to update the driver to support
>your card and make it work out of the box.
>
>- Steve
>
>-- 
>Steven Toth - Kernel Labs
>http://www.kernellabs.com

Re: Hauppauge ImpactVCB-e 01385

[Steven Toth]

Hi Steve,

> Well not nobody because I do.  How do I do it? If you would guide me through, I will happily update it.

I seem to recall Kernel Labs offered you some commercial help with
this product in the past and you declined, you apparently wanted to
tackle it on your own. How's it coming along?

The mailing list will welcome any patches you choose to submit.

Best,

- Steve

-- 
Steven Toth - Kernel Labs
http://www.kernellabs.com

Hauppauge ImpactVCB-e 01385

[Steve Cookson - IT]

Hi Guys,

Sorry to go on about the Hauppauge ImpactVCB-e 01385, but it's a couple 
of years and version 12.04, since I last asked.

This page:

http://linuxtv.org/wiki/index.php/Hauppauge

Now shows:

Table of analog-only devices sold by Hauppauge Model Standard Interface 
Supported Comments
ImpactVCB-e Video PCIe ✔ Yes No tuners, only video-in. S-Video Capture 
works with kernel 3.5.0 (Ubuntu 12.10).

As my distribution is 13.10 with kernel 3.11, I believe it should work.

uname -a gives:

3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 
x86_64 x86_64 GNU/Linux

When I plug in my 01385 I get the same old stuff in dmseg, ie:

cx23885 driver version 0.0.3 loaded
[ 8.921390] cx23885[0]: Your board isn't known (yet) to the driver.
[ 8.921390] cx23885[0]: Try to pick one of the existing card configs via
[ 8.921390] cx23885[0]: card=<n> insmod option. Updating to the latest
[ 8.921390] cx23885[0]: version might help as well.
[ 8.921393] cx23885[0]: Here is a list of valid choices for the card=<n> 
insmod option:

Etc.

Does anyone have any idea of the issue here?

Best regards

Steve

Re: Hauppauge ImpactVCB-e 01385

[Steven Toth]

> When I plug in my 01385 I get the same old stuff in dmseg, ie:
>
> cx23885 driver version 0.0.3 loaded
> [ 8.921390] cx23885[0]: Your board isn't known (yet) to the driver.
> [ 8.921390] cx23885[0]: Try to pick one of the existing card configs via
> [ 8.921390] cx23885[0]: card=<n> insmod option. Updating to the latest
> [ 8.921390] cx23885[0]: version might help as well.
> [ 8.921393] cx23885[0]: Here is a list of valid choices for the card=<n>
> insmod option:
>
> Etc.
>
> Does anyone have any idea of the issue here?

Sure. The issue is nobody cares enough to update the driver to support
your card and make it work out of the box.

- Steve

-- 
Steven Toth - Kernel Labs
http://www.kernellabs.com

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson - IT]

So I'm back to the Hauppauge ImpactVCB-e 01385.

Apparently it's fully supported by the current Linux kernel:

Model                 Standard Interface     Supported     Comments
ImpactVCB-e     Video PCIe                 ✔ Yes                 No 
tuners, only video-in. S-Video Capture works with kernel 3.5.0 (Ubuntu 
12.10).

http://linuxtv.org/wiki/index.php/Hauppauge.

So is this a typo or have I just encountered an install problem?

> When I plug in my 01385 I get the same old stuff in dmseg, ie:
>
> cx23885 driver version 0.0.3 loaded
> [ 8.921390] cx23885[0]: Your board isn't known (yet) to the driver.
> [ 8.921390] cx23885[0]: Try to pick one of the existing card configs via
> [ 8.921390] cx23885[0]: card=<n> insmod option. Updating to the latest
> [ 8.921390] cx23885[0]: version might help as well.
> [ 8.921393] cx23885[0]: Here is a list of valid choices for the 
> card=<n> insmod option:
>
> Etc.
Would the daily build resolve this?  I haven't installed it on this test 
system, but I'm never clear when I should install it or whether I should 
just download a single driver from somewhere.

Regards

Steve

Re: Hauppauge ImpactVCB-e 01385

[Hans Verkuil]

On 04/11/2014 11:09 AM, Steve Cookson - IT wrote:
> So I'm back to the Hauppauge ImpactVCB-e 01385.
> 
> Apparently it's fully supported by the current Linux kernel:
> 
> Model                 Standard Interface     Supported     Comments
> ImpactVCB-e     Video PCIe                 ✔ Yes                 No 
> tuners, only video-in. S-Video Capture works with kernel 3.5.0 (Ubuntu 
> 12.10).
> 
> http://linuxtv.org/wiki/index.php/Hauppauge.
> 
> So is this a typo or have I just encountered an install problem?

I have serious doubts whether this is actually supported. I see no mention of
that board in the cx23885 driver. I wonder if there is a mixup between the
ImpactVCB (which IS supported) and the ImpactVCB-e.

> 
>> When I plug in my 01385 I get the same old stuff in dmseg, ie:
>>
>> cx23885 driver version 0.0.3 loaded
>> [ 8.921390] cx23885[0]: Your board isn't known (yet) to the driver.
>> [ 8.921390] cx23885[0]: Try to pick one of the existing card configs via
>> [ 8.921390] cx23885[0]: card=<n> insmod option. Updating to the latest
>> [ 8.921390] cx23885[0]: version might help as well.
>> [ 8.921393] cx23885[0]: Here is a list of valid choices for the 
>> card=<n> insmod option:

You can try some of the existing cards: one  of 1, 2, 3, 6, 20, 24, 32 might
just work. Look in drivers/media/pci/cx23885/cx23885-cards.c.

Each card definition there defines the inputs that are supported by the card.
There is no perfect match, so you will have to change inputs to see which
input produces an image. You can also add a card definition yourself and
just fiddle around with the vmux/amux/gpio values to see which work. It is
probably something close to what is used by other Hauppauge cards.

>>
>> Etc.
> Would the daily build resolve this?  I haven't installed it on this test 
> system, but I'm never clear when I should install it or whether I should 
> just download a single driver from somewhere.

There is no point in using the daily build. The cx23885 driver hasn't been
updated in a long time.

Regards,

	Hans

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson - IT]

Hi Hans,

Thanks for this, I'll do as you suggested.

On 11/04/14 10:45, Hans Verkuil wrote:
> I have serious doubts whether this is actually supported. I see no mention of
> that board in the cx23885 driver. I wonder if there is a mixup between the
> ImpactVCB (which IS supported) and the ImpactVCB-e.
Do you think there is another internal card out there that would do the 
job of capturing raw SD video?

What would you recommend.

I'm currently using the Dazzle DVC100, stripping the case off and 
installing it internally with cable ties.   It's just a bit basic. I'd 
like something a bit more professional like a half-height PCIe board.  
Which is why I selected the ImpactVCB-e, but really I have no attachment 
to it.

Regards

Steve.

Re: Hauppauge ImpactVCB-e 01385

[Hans Verkuil]

On 04/11/2014 12:03 PM, Steve Cookson - IT wrote:
> Hi Hans,
> 
> Thanks for this, I'll do as you suggested.
> 
> On 11/04/14 10:45, Hans Verkuil wrote:
>> I have serious doubts whether this is actually supported. I see no mention of
>> that board in the cx23885 driver. I wonder if there is a mixup between the
>> ImpactVCB (which IS supported) and the ImpactVCB-e.
> Do you think there is another internal card out there that would do the 
> job of capturing raw SD video?
> 
> What would you recommend.

Actually, I would recommend that you try playing with the 'card=' option to
see if you can get something that works. I suspect that adding support for
this card isn't hard.

Alternatively, you can wait. I've ordered this card myself (it's about time I
start cleaning up the cx23885 driver, so some extra hardware to test with won't
hurt) so once I have it I'll work on adding support for it to the cx23885
driver. The problem is that it has to be ordered, so it may take some time
before it arrives.

There aren't all that many alternatives available for PCIe (PCI is easier). You
can look at the list of supported cards in cx23885-cards.c and see if you can
get any of those other cards.

Regards,

	Hans

> 
> I'm currently using the Dazzle DVC100, stripping the case off and 
> installing it internally with cable ties.   It's just a bit basic. I'd 
> like something a bit more professional like a half-height PCIe board.  
> Which is why I selected the ImpactVCB-e, but really I have no attachment 
> to it.
> 
> Regards
> 
> Steve.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson - IT]

Hi Hans,

On 11/04/14 11:35, Hans Verkuil wrote:
> Actually, I would recommend that you try playing with the 'card=' option to
> see if you can get something that works. I suspect that adding support for
> this card isn't hard.
Well I did try the card= option before and it worked in a way.  The 
raster was compressed though and the image was not really acceptable.
> Alternatively, you can wait. I've ordered this card myself (it's about time I
> start cleaning up the cx23885 driver, so some extra hardware to test with won't
> hurt) so once I have it I'll work on adding support for it to the cx23885
> driver. The problem is that it has to be ordered, so it may take some time
> before it arrives.
I'm happy to wait.

Is there something I can do in the mean time?  If I can download some 
code and start playing, I would do so if I knew where to look.

Tell me where to start and I will do.

Regards

Steve

PS  In fact I think I have 2 x ImpactVCB-e's, so if your card is very 
delayed, I could send you one.  If you're in the Netherlands it won't 
take long to get to you.

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson - IT]

  Hi Hans,
On 14/04/14 15:02, Hans Verkuil wrote:

 > I'd appreciate it if you can test this with a proper video feed.

Well, I've been installing the patch today.  I finished the compilation 
script and the card is not detected.  Here's what I did:

It's been a bit hard-going because my ISP has been on a go-slow and 
everything has taken much longer than it should.

1    I did a fresh build of linux tv.  Deleted ~/linuxtv/media_build and 
then typed:
2    user$ git clone git://linuxtv.org/media_build.git
3    user$ cd media_build
4    user$./build --main-git

     This seemed to be fine.

5    tried to apply the patch (patch -p1 cx23885) but had issues (only 
the main ...card.c was updated and ....h and ...video.c were not 
updated).  As it was only one line each, I applied the updates manually.
6    user$ cd media
7    user$ sudo -s
8    root$ make -C ../v4l  (it scrolled up quickly, but completed with 
no apparent errors
9    root$ make -C ../ install
10    root$ make -C .. rmmod (had a number of errors because of stk1160 
so unplugged EasyCap and re-ran, lots of errors - see below)
11    tried to modprobe cx23885, but got "invalid agrgument"
12    tried to reboot, but ls /dev/video* showed nothing.

Following are the errors from make -C .. rmmo.

The ImpactVCB-e card is installed.  Should I unplug it before doing 
point 11?

Thanks

Steve

PS There is some Portuguese in here, sorry.  It should be fairly self 
explanitory, Entrando is entering, saindo is exiting and diretório is 
err... directory.

make -C .. rmmod
make: Entrando no diretório `/home/image/linuxtv/media_build'
make -C /home/image/linuxtv/media_build/v4l rmmod
make[1]: Entrando no diretório `/home/image/linuxtv/media_build/v4l'
scripts/rmmod.pl unload
found 582 modules
/sbin/rmmod videodev
Pulseaudio is running with UUID(s): 1000
Error: Module videodev is in use by: cx2341x v4l2_common
/sbin/rmmod videobuf_dvb
/sbin/rmmod videobuf_dma_sg
/sbin/rmmod videobuf_core
/sbin/rmmod v4l2_common
Error: Module v4l2_common is in use by: cx2341x
/sbin/rmmod tveeprom
/sbin/rmmod altera_ci
/sbin/rmmod cx2341x
/sbin/rmmod btcx_risc
/sbin/rmmod dvb_core
/sbin/rmmod tda18271
/sbin/rmmod cx2341x
Error: Module cx2341x is not currently loaded
/sbin/rmmod v4l2_common
/sbin/rmmod altera_ci
Error: Module altera_ci is not currently loaded
/sbin/rmmod videodev
/sbin/rmmod videobuf_dma_sg
Error: Module videobuf_dma_sg is not currently loaded
/sbin/rmmod videobuf_dvb
Error: Module videobuf_dvb is not currently loaded
/sbin/rmmod media
/sbin/rmmod btcx_risc
Error: Module btcx_risc is not currently loaded
/sbin/rmmod tda18271
Error: Module tda18271 is not currently loaded
/sbin/rmmod dvb_core
Error: Module dvb_core is not currently loaded
/sbin/rmmod videobuf_core
Error: Module videobuf_core is not currently loaded
/sbin/rmmod tveeprom
Error: Module tveeprom is not currently loaded
/sbin/rmmod altera_stapl
/sbin/rmmod rc_core
/sbin/rmmod videodev
Error: Module videodev is not currently loaded
/sbin/rmmod v4l2_common
Error: Module v4l2_common is not currently loaded
/sbin/rmmod cx2341x
Error: Module cx2341x is not currently loaded
/sbin/rmmod altera_ci
Error: Module altera_ci is not currently loaded
/sbin/rmmod videobuf_dma_sg
Error: Module videobuf_dma_sg is not currently loaded
/sbin/rmmod videobuf_dvb
Error: Module videobuf_dvb is not currently loaded
/sbin/rmmod btcx_risc
Error: Module btcx_risc is not currently loaded
/sbin/rmmod tda18271
Error: Module tda18271 is not currently loaded
/sbin/rmmod dvb_core
Error: Module dvb_core is not currently loaded
/sbin/rmmod videobuf_core
Error: Module videobuf_core is not currently loaded
/sbin/rmmod tveeprom
Error: Module tveeprom is not currently loaded
Couldn't unload: tveeprom videobuf_core dvb_core tda18271 btcx_risc 
videobuf_dvb videobuf_dma_sg altera_ci cx2341x v4l2_common videodev
make[1]: Saindo do diretório `/home/image/linuxtv/media_build/v4l'
make: Saindo do diretório `/home/image/linuxtv/media_build'

root@image-H61M-DS2:~/linuxtv/media_build/media# modprobe cx23885
ERROR: could not insert 'cx23885': Invalid argument

Re: Hauppauge ImpactVCB-e 01385

[Hans Verkuil]

On 04/15/2014 06:45 PM, Steve Cookson - IT wrote:
>   Hi Hans,
> On 14/04/14 15:02, Hans Verkuil wrote:
> 
>  > I'd appreciate it if you can test this with a proper video feed.
> 
> Well, I've been installing the patch today.  I finished the compilation 
> script and the card is not detected.  Here's what I did:
> 
> It's been a bit hard-going because my ISP has been on a go-slow and 
> everything has taken much longer than it should.
> 
> 1    I did a fresh build of linux tv.  Deleted ~/linuxtv/media_build and 
> then typed:
> 2    user$ git clone git://linuxtv.org/media_build.git
> 3    user$ cd media_build
> 4    user$./build --main-git
> 
>      This seemed to be fine.
> 
> 5    tried to apply the patch (patch -p1 cx23885) but had issues (only 
> the main ...card.c was updated and ....h and ...video.c were not 
> updated).  As it was only one line each, I applied the updates manually.
> 6    user$ cd media
> 7    user$ sudo -s
> 8    root$ make -C ../v4l  (it scrolled up quickly, but completed with 
> no apparent errors
> 9    root$ make -C ../ install
> 10    root$ make -C .. rmmod (had a number of errors because of stk1160 
> so unplugged EasyCap and re-ran, lots of errors - see below)

You may have to do a 'depmod -a' here. Try that first.

> 11    tried to modprobe cx23885, but got "invalid agrgument"

Somewhat strange error message. Does 'dmesg' give you any useful info?

Regards,

	Hans

> 12    tried to reboot, but ls /dev/video* showed nothing.
> 
> Following are the errors from make -C .. rmmo.
> 
> The ImpactVCB-e card is installed.  Should I unplug it before doing 
> point 11?
> 

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

On 15/04/14 18:13, Hans Verkuil wrote:
> Somewhat strange error message. Does 'dmesg' give you any useful info?
I get this:

image@image-H61M-DS2:~$ dmesg | grep -i cx23885
[   13.237914] cx23885: disagrees about version of symbol altera_init
[   13.237917] cx23885: Unknown symbol altera_init (err -22)
image@image-H61M-DS2:~$

There were altera_init issue in the dump I gave you earlier too.

Regards,

Steve.

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

Hi Hans,

On 15/04/14 18:13, Hans Verkuil wrote:
> You may have to do a 'depmod -a' here. Try that first.
I tried that.  It worked fine.  No more error messages from

make -C .. rmmod

>> >11    tried to modprobe cx23885, but got "invalid agrgument"
> Somewhat strange error message. Does 'dmesg' give you any useful info?
However this error message is the same.  It actually:

ERROR: could not insert 'cx23885': Invalid argument
If I do a search for cx23885.ko, I find one that I have just created.  
If I cd to that directory and modprobe ./cx23885 I get no error messages.

However, lsmod | grep -i cx only finds cx2341x.

Dmesg continues to give:

[   13.237914] cx23885: disagrees about version of symbol altera_init
[   13.237917] cx23885: Unknown symbol altera_init (err -22)

altera_ci.ko is the only other file in 
/lib/modules/3.11.0-18-generic/kernel/drivers/media/pci/cx23885/*

Regards

Steve

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

On 15/04/14 19:44, Steve Cookson wrote:
> [ 13.237914] cx23885: disagrees about version of symbol altera_init
> [   13.237917] cx23885: Unknown symbol altera_init (err -22) 
Is it a regression issue?

https://github.com/ljalves/linux_media/issues/2#issuecomment-23365778

I'm on 3.11.0-18.

Regards

Steve.

Re: Hauppauge ImpactVCB-e 01385

[Hans Verkuil]

On 04/15/2014 08:44 PM, Steve Cookson wrote:
> Hi Hans,
> 
> On 15/04/14 18:13, Hans Verkuil wrote:
>> You may have to do a 'depmod -a' here. Try that first.
> I tried that.  It worked fine.  No more error messages from
> 
> make -C .. rmmod
> 
>>>> 11    tried to modprobe cx23885, but got "invalid agrgument"
>> Somewhat strange error message. Does 'dmesg' give you any useful info?
> However this error message is the same.  It actually:
> 
> ERROR: could not insert 'cx23885': Invalid argument
> If I do a search for cx23885.ko, I find one that I have just created.  
> If I cd to that directory and modprobe ./cx23885 I get no error messages.
> 
> However, lsmod | grep -i cx only finds cx2341x.
> 
> Dmesg continues to give:
> 
> [   13.237914] cx23885: disagrees about version of symbol altera_init
> [   13.237917] cx23885: Unknown symbol altera_init (err -22)
> 
> altera_ci.ko is the only other file in 
> /lib/modules/3.11.0-18-generic/kernel/drivers/media/pci/cx23885/*

Try this:

find /lib/modules/`uname -r`/|grep altera

If you have duplicate altera-stapl.ko files, then that might explain it.
In that case remove the older module.

It does install correctly for my 3.13 kernel.

Regards,

	Hans

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

  Hi Hans,

Thanks for this.
On 16/04/14 10:58, Hans Verkuil wrote:
 > find /lib/modules/`uname -r`/|grep altera
 >
 > If you have duplicate altera-stapl.ko files, then that might explain it.
 > In that case remove the older module.
There are indeed duplicates.  I removed the older one and dmesg went 
wild :)  Dump follows at end of email.

However looking at the tree structure I have to say I don't understand 
it.  Firstly there seem to be two equivalent branches in /lib/modules/:

1) drivers/linux/drivers/misc/altera-stapl/

and

2) drivers/misc/altera-stapl/

Before I do the patch and build, altera-stapl.ko is in 2) but the make 
install puts the new version in 1).

If I delete the version in 1), I delete the effects of the patch, if I 
delete the version in 2), I get the dump below.
 > It does install correctly for my 3.13 kernel.
I upgraded to 3.11.0.19 and reinstalled linux tv, but same effect.

Note that the dump here gives err 0, but the original error was err 
-22.  Is -22 significant, does anyone know what it means?

Also, there is an altera.h of size = 0 in 
lib/modules/...../include/config/spi but as it is not duplicated on 
linuxtv/media_build I imagine it doesn't affect the compile.

There has been quite a bit of discussion about this error in previous 
releases and patches have been applied (as I'm sure you saw).  It seems 
we still haven't quite got to the bottom of it as it is still 
reappearing.  I think it would be quite useful to put it to bed once and 
for all.

Thanks so much for your help.

Regards

Steve.

dmesg | grep -i cx
[    9.048582] cx23885: module verification failed: signature and/or 
required key missing - tainting kernel
[    9.048599] cx23885: Unknown symbol videobuf_streamoff (err 0)
[    9.048605] cx23885: Unknown symbol v4l2_norm_to_name (err 0)
[    9.048608] cx23885: Unknown symbol videobuf_poll_stream (err 0)
[    9.048611] cx23885: Unknown symbol video_ioctl2 (err 0)
[    9.048615] cx23885: Unknown symbol v4l2_get_timestamp (err 0)
[    9.048618] cx23885: Unknown symbol videobuf_read_stop (err 0)
[    9.048623] cx23885: Unknown symbol ir_raw_event_handle (err 0)
[    9.048626] cx23885: Unknown symbol videobuf_dma_map (err 0)
[    9.048632] cx23885: Unknown symbol dvb_ca_en50221_init (err 0)
[    9.048637] cx23885: Unknown symbol altera_init (err 0)
[    9.048641] cx23885: Unknown symbol snd_pcm_new (err 0)
[    9.048647] cx23885: Unknown symbol cx2341x_ext_ctrls (err 0)
[    9.048651] cx23885: Unknown symbol tda18271_attach (err 0)
[    9.048659] cx23885: Unknown symbol videobuf_dma_free (err 0)
[    9.048663] cx23885: Unknown symbol ir_raw_event_store (err 0)
[    9.048667] cx23885: Unknown symbol videobuf_reqbufs (err 0)
[    9.048674] cx23885: Unknown symbol videobuf_waiton (err 0)
[    9.048677] cx23885: Unknown symbol snd_pcm_format_physical_width (err 0)
[    9.048680] cx23885: Unknown symbol v4l2_subdev_init (err 0)
[    9.048684] cx23885: Unknown symbol videobuf_dqbuf (err 0)
[    9.048691] cx23885: Unknown symbol videobuf_dvb_alloc_frontend (err 0)
[    9.048695] cx23885: Unknown symbol v4l2_i2c_subdev_addr (err 0)
[    9.048698] cx23885: Unknown symbol v4l2_device_register_subdev (err 0)
[    9.048701] cx23885: Unknown symbol cx2341x_ctrl_query (err 0)
[    9.048706] cx23885: Unknown symbol video_devdata (err 0)
[    9.048710] cx23885: Unknown symbol v4l_bound_align_image (err 0)
[    9.048713] cx23885: Unknown symbol v4l2_type_names (err 0)
[    9.048716] cx23885: Unknown symbol v4l2_device_unregister_subdev (err 0)
[    9.048719] cx23885: Unknown symbol v4l2_ctrl_next (err 0)
[    9.048723] cx23885: Unknown symbol altera_ci_tuner_reset (err 0)
[    9.048727] cx23885: Unknown symbol btcx_riscmem_alloc (err 0)
[    9.048729] cx23885: Unknown symbol videobuf_dvb_get_frontend (err 0)
[    9.048732] cx23885: Unknown symbol snd_pcm_lib_ioctl (err 0)
[    9.048736] cx23885: Unknown symbol tveeprom_read (err 0)
[    9.048739] cx23885: Unknown symbol videobuf_queue_sg_init (err 0)
[    9.048741] cx23885: Unknown symbol btcx_riscmem_free (err 0)
[    9.048744] cx23885: Unknown symbol v4l2_ctrl_query_menu (err 0)
[    9.048747] cx23885: Unknown symbol videobuf_dma_unmap (err 0)
[    9.048749] cx23885: Unknown symbol videobuf_read_stream (err 0)
[    9.048753] cx23885: Unknown symbol dvb_ca_en50221_release (err 0)
[    9.048757] cx23885: Unknown symbol rc_register_device (err 0)
[    9.048761] cx23885: Unknown symbol videobuf_querybuf (err 0)
[    9.048763] cx23885: Unknown symbol snd_pcm_hw_constraint_pow2 (err 0)
[    9.048767] cx23885: Unknown symbol altera_ci_irq (err 0)
[    9.048769] cx23885: Unknown symbol snd_pcm_set_ops (err 0)
[    9.048772] cx23885: Unknown symbol video_unregister_device (err 0)
[    9.048775] cx23885: Unknown symbol videobuf_qbuf (err 0)
[    9.048779] cx23885: Unknown symbol altera_ci_release (err 0)
[    9.048782] cx23885: Unknown symbol cx2341x_update (err 0)
[    9.048785] cx23885: Unknown symbol video_device_alloc (err 0)
[    9.048789] cx23885: Unknown symbol videobuf_read_one (err 0)
[    9.048792] cx23885: Unknown symbol rc_free_device (err 0)
[    9.048794] cx23885: Unknown symbol videobuf_dma_init (err 0)
[    9.048799] cx23885: Unknown symbol dvb_ca_en50221_frda_irq (err 0)
[    9.048802] cx23885: Unknown symbol cx2341x_ctrl_get_menu (err 0)
[    9.048804] cx23885: Unknown symbol v4l2_device_register (err 0)
[    9.048807] cx23885: Unknown symbol videobuf_dvb_unregister_bus (err 0)
[    9.048812] cx23885: Unknown symbol dvb_ca_en50221_camready_irq (err 0)
[    9.048814] cx23885: Unknown symbol rc_allocate_device (err 0)
[    9.048817] cx23885: Unknown symbol cx2341x_log_status (err 0)
[    9.048821] cx23885: Unknown symbol videobuf_dma_init_kernel (err 0)
[    9.048824] cx23885: Unknown symbol cx2341x_fill_defaults (err 0)
[    9.048826] cx23885: Unknown symbol videobuf_dvb_register_bus (err 0)
[    9.048830] cx23885: Unknown symbol videobuf_iolock (err 0)
[    9.048834] cx23885: Unknown symbol __video_register_device (err 0)
[    9.048837] cx23885: Unknown symbol videobuf_streamon (err 0)
[    9.048839] cx23885: Unknown symbol videobuf_queue_cancel (err 0)
[    9.048842] cx23885: Unknown symbol videobuf_dvb_dealloc_frontends 
(err 0)
[    9.048844] cx23885: Unknown symbol v4l2_i2c_tuner_addrs (err 0)
[    9.048848] cx23885: Unknown symbol v4l2_device_unregister (err 0)
[    9.048851] cx23885: Unknown symbol tveeprom_hauppauge_analog (err 0)
[    9.048854] cx23885: Unknown symbol video_device_release (err 0)
[    9.048857] cx23885: Unknown symbol snd_pcm_period_elapsed (err 0)
[    9.048860] cx23885: Unknown symbol v4l2_i2c_new_subdev (err 0)
[    9.048863] cx23885: Unknown symbol videobuf_mmap_mapper (err 0)
[    9.048866] cx23885: Unknown symbol cx2341x_mpeg_ctrls (err 0)
[    9.048871] cx23885: Unknown symbol altera_ci_init (err 0)
[    9.048876] cx23885: Unknown symbol rc_unregister_device (err 0)
[    9.048880] cx23885: Unknown symbol videobuf_to_dma (err 0)
[    9.048883] cx23885: Unknown symbol videobuf_mmap_free (err 0)
image@image-H61M-DS2:~/media_build$

Re: Hauppauge ImpactVCB-e 01385

[Hans Verkuil]

On 04/16/2014 03:14 PM, Steve Cookson wrote:
>   Hi Hans,
> 
> Thanks for this.
> On 16/04/14 10:58, Hans Verkuil wrote:
>  > find /lib/modules/`uname -r`/|grep altera
>  >
>  > If you have duplicate altera-stapl.ko files, then that might explain it.
>  > In that case remove the older module.
> There are indeed duplicates.  I removed the older one and dmesg went 
> wild :)  Dump follows at end of email.
> 
> However looking at the tree structure I have to say I don't understand 
> it.  Firstly there seem to be two equivalent branches in /lib/modules/:
> 
> 1) drivers/linux/drivers/misc/altera-stapl/
> 
> and
> 
> 2) drivers/misc/altera-stapl/
> 
> Before I do the patch and build, altera-stapl.ko is in 2) but the make 
> install puts the new version in 1).

Weird. It looks like media_build misinstalls this. If altera-stapl is in
the wrong place, then I suspect the other modules are also in the wrong
place and thus duplicated, which will cause all the things you see below.

Which distro are you using?

Anyway, I would recommend that you make a safety copy of your modules
first (just in case :-) ), and then move all the newly install modules
to the right place.

Regards,

	Hans

> 
> If I delete the version in 1), I delete the effects of the patch, if I 
> delete the version in 2), I get the dump below.
>  > It does install correctly for my 3.13 kernel.
> I upgraded to 3.11.0.19 and reinstalled linux tv, but same effect.
> 
> Note that the dump here gives err 0, but the original error was err 
> -22.  Is -22 significant, does anyone know what it means?
> 
> Also, there is an altera.h of size = 0 in 
> lib/modules/...../include/config/spi but as it is not duplicated on 
> linuxtv/media_build I imagine it doesn't affect the compile.
> 
> There has been quite a bit of discussion about this error in previous 
> releases and patches have been applied (as I'm sure you saw).  It seems 
> we still haven't quite got to the bottom of it as it is still 
> reappearing.  I think it would be quite useful to put it to bed once and 
> for all.
> 
> Thanks so much for your help.
> 
> Regards
> 
> Steve.
> 
> dmesg | grep -i cx
> [    9.048582] cx23885: module verification failed: signature and/or 
> required key missing - tainting kernel
> [    9.048599] cx23885: Unknown symbol videobuf_streamoff (err 0)
> [    9.048605] cx23885: Unknown symbol v4l2_norm_to_name (err 0)
> [    9.048608] cx23885: Unknown symbol videobuf_poll_stream (err 0)
> [    9.048611] cx23885: Unknown symbol video_ioctl2 (err 0)
> [    9.048615] cx23885: Unknown symbol v4l2_get_timestamp (err 0)
> [    9.048618] cx23885: Unknown symbol videobuf_read_stop (err 0)
> [    9.048623] cx23885: Unknown symbol ir_raw_event_handle (err 0)
> [    9.048626] cx23885: Unknown symbol videobuf_dma_map (err 0)
> [    9.048632] cx23885: Unknown symbol dvb_ca_en50221_init (err 0)
> [    9.048637] cx23885: Unknown symbol altera_init (err 0)
> [    9.048641] cx23885: Unknown symbol snd_pcm_new (err 0)
> [    9.048647] cx23885: Unknown symbol cx2341x_ext_ctrls (err 0)
> [    9.048651] cx23885: Unknown symbol tda18271_attach (err 0)
> [    9.048659] cx23885: Unknown symbol videobuf_dma_free (err 0)
> [    9.048663] cx23885: Unknown symbol ir_raw_event_store (err 0)
> [    9.048667] cx23885: Unknown symbol videobuf_reqbufs (err 0)
> [    9.048674] cx23885: Unknown symbol videobuf_waiton (err 0)
> [    9.048677] cx23885: Unknown symbol snd_pcm_format_physical_width (err 0)
> [    9.048680] cx23885: Unknown symbol v4l2_subdev_init (err 0)
> [    9.048684] cx23885: Unknown symbol videobuf_dqbuf (err 0)
> [    9.048691] cx23885: Unknown symbol videobuf_dvb_alloc_frontend (err 0)
> [    9.048695] cx23885: Unknown symbol v4l2_i2c_subdev_addr (err 0)
> [    9.048698] cx23885: Unknown symbol v4l2_device_register_subdev (err 0)
> [    9.048701] cx23885: Unknown symbol cx2341x_ctrl_query (err 0)
> [    9.048706] cx23885: Unknown symbol video_devdata (err 0)
> [    9.048710] cx23885: Unknown symbol v4l_bound_align_image (err 0)
> [    9.048713] cx23885: Unknown symbol v4l2_type_names (err 0)
> [    9.048716] cx23885: Unknown symbol v4l2_device_unregister_subdev (err 0)
> [    9.048719] cx23885: Unknown symbol v4l2_ctrl_next (err 0)
> [    9.048723] cx23885: Unknown symbol altera_ci_tuner_reset (err 0)
> [    9.048727] cx23885: Unknown symbol btcx_riscmem_alloc (err 0)
> [    9.048729] cx23885: Unknown symbol videobuf_dvb_get_frontend (err 0)
> [    9.048732] cx23885: Unknown symbol snd_pcm_lib_ioctl (err 0)
> [    9.048736] cx23885: Unknown symbol tveeprom_read (err 0)
> [    9.048739] cx23885: Unknown symbol videobuf_queue_sg_init (err 0)
> [    9.048741] cx23885: Unknown symbol btcx_riscmem_free (err 0)
> [    9.048744] cx23885: Unknown symbol v4l2_ctrl_query_menu (err 0)
> [    9.048747] cx23885: Unknown symbol videobuf_dma_unmap (err 0)
> [    9.048749] cx23885: Unknown symbol videobuf_read_stream (err 0)
> [    9.048753] cx23885: Unknown symbol dvb_ca_en50221_release (err 0)
> [    9.048757] cx23885: Unknown symbol rc_register_device (err 0)
> [    9.048761] cx23885: Unknown symbol videobuf_querybuf (err 0)
> [    9.048763] cx23885: Unknown symbol snd_pcm_hw_constraint_pow2 (err 0)
> [    9.048767] cx23885: Unknown symbol altera_ci_irq (err 0)
> [    9.048769] cx23885: Unknown symbol snd_pcm_set_ops (err 0)
> [    9.048772] cx23885: Unknown symbol video_unregister_device (err 0)
> [    9.048775] cx23885: Unknown symbol videobuf_qbuf (err 0)
> [    9.048779] cx23885: Unknown symbol altera_ci_release (err 0)
> [    9.048782] cx23885: Unknown symbol cx2341x_update (err 0)
> [    9.048785] cx23885: Unknown symbol video_device_alloc (err 0)
> [    9.048789] cx23885: Unknown symbol videobuf_read_one (err 0)
> [    9.048792] cx23885: Unknown symbol rc_free_device (err 0)
> [    9.048794] cx23885: Unknown symbol videobuf_dma_init (err 0)
> [    9.048799] cx23885: Unknown symbol dvb_ca_en50221_frda_irq (err 0)
> [    9.048802] cx23885: Unknown symbol cx2341x_ctrl_get_menu (err 0)
> [    9.048804] cx23885: Unknown symbol v4l2_device_register (err 0)
> [    9.048807] cx23885: Unknown symbol videobuf_dvb_unregister_bus (err 0)
> [    9.048812] cx23885: Unknown symbol dvb_ca_en50221_camready_irq (err 0)
> [    9.048814] cx23885: Unknown symbol rc_allocate_device (err 0)
> [    9.048817] cx23885: Unknown symbol cx2341x_log_status (err 0)
> [    9.048821] cx23885: Unknown symbol videobuf_dma_init_kernel (err 0)
> [    9.048824] cx23885: Unknown symbol cx2341x_fill_defaults (err 0)
> [    9.048826] cx23885: Unknown symbol videobuf_dvb_register_bus (err 0)
> [    9.048830] cx23885: Unknown symbol videobuf_iolock (err 0)
> [    9.048834] cx23885: Unknown symbol __video_register_device (err 0)
> [    9.048837] cx23885: Unknown symbol videobuf_streamon (err 0)
> [    9.048839] cx23885: Unknown symbol videobuf_queue_cancel (err 0)
> [    9.048842] cx23885: Unknown symbol videobuf_dvb_dealloc_frontends 
> (err 0)
> [    9.048844] cx23885: Unknown symbol v4l2_i2c_tuner_addrs (err 0)
> [    9.048848] cx23885: Unknown symbol v4l2_device_unregister (err 0)
> [    9.048851] cx23885: Unknown symbol tveeprom_hauppauge_analog (err 0)
> [    9.048854] cx23885: Unknown symbol video_device_release (err 0)
> [    9.048857] cx23885: Unknown symbol snd_pcm_period_elapsed (err 0)
> [    9.048860] cx23885: Unknown symbol v4l2_i2c_new_subdev (err 0)
> [    9.048863] cx23885: Unknown symbol videobuf_mmap_mapper (err 0)
> [    9.048866] cx23885: Unknown symbol cx2341x_mpeg_ctrls (err 0)
> [    9.048871] cx23885: Unknown symbol altera_ci_init (err 0)
> [    9.048876] cx23885: Unknown symbol rc_unregister_device (err 0)
> [    9.048880] cx23885: Unknown symbol videobuf_to_dma (err 0)
> [    9.048883] cx23885: Unknown symbol videobuf_mmap_free (err 0)
> image@image-H61M-DS2:~/media_build$
> 

Re: Hauppauge ImpactVCB-e 01385

[Devin Heitmueller]

> Anyway, I would recommend that you make a safety copy of your modules
> first (just in case :-) ), and then move all the newly install modules
> to the right place.

Yeah, I generally recommend that in such cases you just "rm -rf
/lib/modules/`uname -r`/kernel/drivers/media" before running "make
install", so you know you're in a clean state (make a backup copy
first though, just in case).  This avoids having to figure out which
driver moved and the old version of which didn't get deleted.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

Hi Guys,
On 16/04/14 14:20, Hans Verkuil wrote:
 >> However looking at the tree structure I have to say I don't understand
 >> > it.  Firstly there seem to be two equivalent branches in 
/lib/modules/:
 >> >
 >> > 1) drivers/linux/drivers/misc/altera-stapl/
 >> >
 >> > and
 >> >
 >> > 2) drivers/misc/altera-stapl/
 >> >
 >> > Before I do the patch and build, altera-stapl.ko is in 2) but the 
make
 >> > install puts the new version in 1).
 > Weird. It looks like media_build misinstalls this. If altera-stapl is in
 > the wrong place, then I suspect the other modules are also in the wrong
 > place and thus duplicated, which will cause all the things you see below.
 >
 > Which distro are you using?
 >
 > Anyway, I would recommend that you make a safety copy of your modules
 > first (just in case  ), and then move all the newly install modules
 > to the right place.

Well after much soul-searching about how to find out how many files were 
in the wrong place, it turns out it was JUST one: altera-stapl.ko

It was the only one in drivers/linux/drivers/misc/altera-stapl/. When I 
moved it everything fell into place the card was detected.

So this is the solution to issue one.

My distribution is Debian (Kubuntu 13.10) and this appears to be the 
only file that goes in the wrong place.  How do I log this as a bug?

I set up a video feed and the video was detected.

Results follow in next email.

Regards

Steve.

Re: Hauppauge ImpactVCB-e 01385

[Steve Cookson]

Hi Guys,

On 14/04/14 15:02, Hans Verkuil wrote:

 > I'd appreciate it if you can test this with a proper video feed.

Ok, here is the first issue:

1) I have a 640x480 video feed which displays appropriately through 
stk1160, but only displays at 320x240 in ImpactVCBe.

In fact this is the same issue I had last year with:

echo cx23885 card=5 | sudo tee -a /etc/modules

Is your card giving you 640x480?

Thanks

Steve.

Re: Hauppauge ImpactVCB-e 01385

[Hans Verkuil]

On 04/16/2014 07:11 PM, Steve Cookson wrote:
> Hi Guys,
> 
> On 14/04/14 15:02, Hans Verkuil wrote:
> 
>  > I'd appreciate it if you can test this with a proper video feed.
> 
> Ok, here is the first issue:
> 
> 1) I have a 640x480 video feed which displays appropriately through 
> stk1160, but only displays at 320x240 in ImpactVCBe.
> 
> In fact this is the same issue I had last year with:
> 
> echo cx23885 card=5 | sudo tee -a /etc/modules
> 
> Is your card giving you 640x480?

For no good reason AFAICT the initial resolution is set to 320x240. But
you can just set it to 640x480 (or more likely, 720x480 for NTSC or
720x576 for PAL):

v4l2-ctl -v width=640,height=480

Regards,

	Hans