AW: em28xx WinTV dualHD in Raspbian

2016-11-07 Thread ps00de 
Wow, interesting offer from this guy! Hopefully this is a motivation for Olli. 
Maybe I also can offer beer or sth. else or help to test a new version of the 
driver.

With single tuner support it works great since june 24/7 (except my last 
upgrade of the rpi with mismatched modules...)

Cheers,
Patrick

-Ursprüngliche Nachricht-
Von: Christian Steiner [mailto:christian.stei...@outlook.de] 
Gesendet: Donnerstag, 3. November 2016 21:46
An: Olli Salonen
Cc: Andrey Utkin; ps0...@yahoo.de; Mauro Carvalho Chehab; linux-media
Betreff: Re: em28xx WinTV dualHD in Raspbian

Hi Olli,

On 23.10.2016 12:14, Olli Salonen wrote:
> When I submitted the original patch to add support for this device I 
> stated that it only supports the first tuner. The em28xx driver is not 
> built with dual-tuner support in mind and I had not enough interest to 
> start changing it (the driver supports like 100 devices and is quite 
> massive).

have you seen http://www.spinics.net/lists/linux-media/msg105939.html?
The guy is offering USD$200 for working dual tuner support of the ATSC version. 
The ATSC version has different tuners, but maybe it is no big deal. Would that 
be a little motivation for you? Or what could motivate you? Do you like German 
beer? ;-)

Dual tuner support would be awesome. The device is perfect for building a 
low-power VDR client or streaming server using a Raspberry Pi/Banana Pi.

Best,
Christian

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: em28xx WinTV dualHD in Raspbian

2016-11-03 Thread Christian Steiner 
Hi Olli,

On 23.10.2016 12:14, Olli Salonen wrote:
> When I submitted the original patch to add support for this device I
> stated that it only supports the first tuner. The em28xx driver is not
> built with dual-tuner support in mind and I had not enough interest to
> start changing it (the driver supports like 100 devices and is quite
> massive).

have you seen http://www.spinics.net/lists/linux-media/msg105939.html?
The guy is offering USD$200 for working dual tuner support of the ATSC
version. The ATSC version has different tuners, but maybe it is no big
deal. Would that be a little motivation for you? Or what could motivate
you? Do you like German beer? ;-)

Dual tuner support would be awesome. The device is perfect for building
a low-power VDR client or streaming server using a Raspberry Pi/Banana Pi.

Best,
Christian

AW: em28xx WinTV dualHD in Raspbian

2016-10-23 Thread ps00de 
Hi Andrey and Olli,

sorry, didn't described that, it's written down in the patch (here: 
https://patchwork.linuxtv.org/patch/33811/).

I never have written drivers before so I think I shouldn't start with it now 
because I have to ask too many questions... So hopefully olli or someone else 
can rewrite the driver to support this device. If I can help with anything, 
just ask.

The dualHD is a great device to insert dvb signals in home environments because 
it's small and not very expensive. E.g. together with and RPI and SATPI you can 
put it in a wall-mounted media box if you have such one for your home network.



-Ursprüngliche Nachricht-
Von: linux-media-ow...@vger.kernel.org 
[mailto:linux-media-ow...@vger.kernel.org] Im Auftrag von Olli Salonen
Gesendet: Sonntag, 23. Oktober 2016 12:14
An: Andrey Utkin
Cc: ps0...@yahoo.de; Mauro Carvalho Chehab; linux-media
Betreff: Re: em28xx WinTV dualHD in Raspbian

Hi Andrey,

When I submitted the original patch to add support for this device I stated 
that it only supports the first tuner. The em28xx driver is not built with 
dual-tuner support in mind and I had not enough interest to start changing it 
(the driver supports like 100 devices and is quite massive). There should not 
be many issues in using the second tuner itself on this device, it's just 
another I2C bus...

Cheers,
-olli


On 23 October 2016 at 13:03, Andrey Utkin <andrey_ut...@fastmail.com> wrote:
> On Sat, Oct 22, 2016 at 07:36:13PM +0200, ps0...@yahoo.de wrote:
>> Hopefully some driver expert can get the second tuner working, that 
>> would be awesome
>
> What's the problem? I don't see it described in this discussion thread.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" 
> in the body of a message to majord...@vger.kernel.org More majordomo 
> info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the 
body of a message to majord...@vger.kernel.org More majordomo info at  
http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: em28xx WinTV dualHD in Raspbian

2016-10-23 Thread Olli Salonen 
Hi Andrey,

When I submitted the original patch to add support for this device I
stated that it only supports the first tuner. The em28xx driver is not
built with dual-tuner support in mind and I had not enough interest to
start changing it (the driver supports like 100 devices and is quite
massive). There should not be many issues in using the second tuner
itself on this device, it's just another I2C bus...

Cheers,
-olli


On 23 October 2016 at 13:03, Andrey Utkin  wrote:
> On Sat, Oct 22, 2016 at 07:36:13PM +0200, ps0...@yahoo.de wrote:
>> Hopefully some driver expert can get the second tuner working, that would be
>> awesome
>
> What's the problem? I don't see it described in this discussion thread.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: em28xx WinTV dualHD in Raspbian

2016-10-23 Thread Andrey Utkin 
On Sat, Oct 22, 2016 at 07:36:13PM +0200, ps0...@yahoo.de wrote:
> Hopefully some driver expert can get the second tuner working, that would be
> awesome

What's the problem? I don't see it described in this discussion thread.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

AW: em28xx WinTV dualHD in Raspbian

2016-10-22 Thread ps00de 
I gave up and compiled an 4.7 Kernel (Option 3) - now it works out of the
box.

Hopefully some driver expert can get the second tuner working, that would be
awesome

Thanks,
Patrick

-Ursprüngliche Nachricht-
Von: linux-media-ow...@vger.kernel.org
[mailto:linux-media-ow...@vger.kernel.org] Im Auftrag von Mauro Carvalho
Chehab
Gesendet: Mittwoch, 19. Oktober 2016 21:14
An: ps0...@yahoo.de
Cc: linux-media@vger.kernel.org
Betreff: Re: em28xx WinTV dualHD in Raspbian

Em Wed, 19 Oct 2016 20:50:09 +0200
<ps0...@yahoo.de> escreveu:

> > Based on this log:
> > 
> > Oct 18 23:08:01 mediapi kernel: [ 7590.369200] em28xx_dvb: disagrees 
> > about version of symbol dvb_dmxdev_init Oct 18 23:08:01 mediapi 
> > kernel: [ 7590.369228] em28xx_dvb: Unknown symbol dvb_dmxdev_init 
> > (err -22)
> > 
> > it seems you messed the modules install or you have the V4L2 stack
compiled builtin with a different version.   
> 
> How to fix this?
> 
> - I reinstalled the current firmware and kernel on the raspberry.
> - I installed the headers with sudo apt-get install 
> raspberrypi-kernel-headers
> - Then I have cloned, build and installed the modules:
> 
> git clone git://linuxtv.org/media_build.git cd media_build ./build 
> sudo make install
> 
> But the same errors appear again.

There are 3 options:

1) If the V4L core is builtin on your Kernel [1], then you'll need recompile
the Kernel yourself and be sure that V4L will be disabled. Then, you can
build V4L2 using the media_build tree.
You'll likely need to fix the DRM driver dependencies through, by modifying
the Kernel source code (actually, some Kconfig file).

2) To use the em28xx driver that came at the RPi Kernel, instead of using
media_build.git. You'll also need to recompile the RPi proprietary Kernel
from its sources;

3) use the upstream Kernel. If I remember correctly, the VC4 driver (needed
for GPU support) was added on Kernel 4.7. If you're not using a camera
sensor connected to your RPi, the VC4 driver should be enough for your
needs.

[1] If you're using the RPi proprietary Kernel, I bet you have the
V4L2 core built in. I remember I found the same issue last year, while
playing with RPi proprietary Kernel - part of their GPU driver was depending
on CONFIG_MEDIA - I think - for no good reason. I used to have a patch
fixing it somewhere, but I was unable to find it.

> 
> Thanks,
> Patrick
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" 
> in the body of a message to majord...@vger.kernel.org More majordomo 
> info at  http://vger.kernel.org/majordomo-info.html



Thanks,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: em28xx WinTV dualHD in Raspbian

2016-10-19 Thread Mauro Carvalho Chehab 
Em Wed, 19 Oct 2016 20:50:09 +0200
 escreveu:

> > Based on this log:
> > 
> > Oct 18 23:08:01 mediapi kernel: [ 7590.369200] em28xx_dvb: disagrees about 
> > version of symbol dvb_dmxdev_init Oct 18 23:08:01 mediapi kernel: [ 
> > 7590.369228] em28xx_dvb: Unknown symbol dvb_dmxdev_init (err -22)
> > 
> > it seems you messed the modules install or you have the V4L2 stack compiled 
> > builtin with a different version.   
> 
> How to fix this?
> 
> - I reinstalled the current firmware and kernel on the raspberry.
> - I installed the headers with sudo apt-get install raspberrypi-kernel-headers
> - Then I have cloned, build and installed the modules:
> 
> git clone git://linuxtv.org/media_build.git
> cd media_build 
> ./build
> sudo make install
> 
> But the same errors appear again.

There are 3 options:

1) If the V4L core is builtin on your Kernel [1], then you'll
need recompile the Kernel yourself and be sure that V4L will be
disabled. Then, you can build V4L2 using the media_build tree.
You'll likely need to fix the DRM driver dependencies through,
by modifying the Kernel source code (actually, some Kconfig file).

2) To use the em28xx driver that came at the RPi Kernel,
instead of using media_build.git. You'll also need to recompile
the RPi proprietary Kernel from its sources;

3) use the upstream Kernel. If I remember correctly, the VC4 driver
(needed for GPU support) was added on Kernel 4.7. If you're not using
a camera sensor connected to your RPi, the VC4 driver should be enough
for your needs.

[1] If you're using the RPi proprietary Kernel, I bet you have the
V4L2 core built in. I remember I found the same issue last year, while
playing with RPi proprietary Kernel - part of their GPU driver was
depending  on CONFIG_MEDIA - I think - for no good reason. I used to 
have a patch fixing it somewhere, but I was unable to find it.

> 
> Thanks,
> Patrick
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



Thanks,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

AW: em28xx WinTV dualHD in Raspbian

2016-10-19 Thread ps00de 
> Based on this log:
> 
> Oct 18 23:08:01 mediapi kernel: [ 7590.369200] em28xx_dvb: disagrees about 
> version of symbol dvb_dmxdev_init Oct 18 23:08:01 mediapi kernel: [ 
> 7590.369228] em28xx_dvb: Unknown symbol dvb_dmxdev_init (err -22)
>
> It seems you messed the modules install or you have the V4L2 stack compiled 
> builtin with a different version. 

I've done a cleanup: sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/media/
And reinstalled v4l (make install) again.

Same result (no /dev/dvb), but other log:
Oct 19 20:59:54 mediapi kernel: [7.515009] media: Linux media interface: 
v0.10
Oct 19 20:59:54 mediapi kernel: [7.537922] Linux video capture interface: 
v2.00
Oct 19 20:59:54 mediapi kernel: [7.554643] em28xx: New device HCW dualHD @ 
480 Mbps (2040:0265, interface 0, class 0)
Oct 19 20:59:54 mediapi kernel: [7.554666] em28xx: DVB interface 0 found: 
isoc
Oct 19 20:59:54 mediapi kernel: [7.554959] em28xx: chip ID is em28174
Oct 19 20:59:54 mediapi kernel: [8.752360] em28174 #0: EEPROM ID = 26 00 01 
00, EEPROM hash = 0x7ee3cbc8
Oct 19 20:59:54 mediapi kernel: [8.752378] em28174 #0: EEPROM info:
Oct 19 20:59:54 mediapi kernel: [8.752387] em28174 #0:  microcode start 
address = 0x0004, boot configuration = 0x01
Oct 19 20:59:54 mediapi kernel: [8.758923] em28174 #0:  AC97 audio (5 
sample rates)
Oct 19 20:59:54 mediapi kernel: [8.758936] em28174 #0:  500mA max power
Oct 19 20:59:54 mediapi kernel: [8.758946] em28174 #0:  Table at offset 
0x27, strings=0x0e6a, 0x1888, 0x087e
Oct 19 20:59:54 mediapi kernel: [8.759389] em28174 #0: Identified as 
Hauppauge WinTV-dualHD DVB (card=99)
Oct 19 20:59:54 mediapi kernel: [8.764360] tveeprom 4-0050: Hauppauge model 
204109, rev B2I6, serial# 11540068
Oct 19 20:59:54 mediapi kernel: [8.764381] tveeprom 4-0050: tuner model is 
SiLabs Si2157 (idx 186, type 4)
Oct 19 20:59:54 mediapi kernel: [8.764394] tveeprom 4-0050: TV standards 
PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
Oct 19 20:59:54 mediapi kernel: [8.764404] tveeprom 4-0050: audio processor 
is None (idx 0)
Oct 19 20:59:54 mediapi kernel: [8.764414] tveeprom 4-0050: has no radio, 
has IR receiver, has no IR transmitter
Oct 19 20:59:54 mediapi kernel: [8.764424] em28174 #0: dvb set to isoc mode.
Oct 19 20:59:54 mediapi kernel: [8.764854] usbcore: registered new 
interface driver em28xx
Oct 19 20:59:54 mediapi kernel: [8.800215] em28174 #0: Registering input 
extension
Oct 19 20:59:54 mediapi kernel: [8.835377] Registered IR keymap rc-hauppauge
Oct 19 20:59:54 mediapi kernel: [8.836063] input: em28xx IR (em28174 #0) as 
/devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0/input0
Oct 19 20:59:54 mediapi kernel: [8.836345] rc rc0: em28xx IR (em28174 #0) 
as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0
Oct 19 20:59:54 mediapi kernel: [8.838384] em28174 #0: Input extension 
successfully initalized
Oct 19 20:59:54 mediapi kernel: [8.838406] em28xx: Registered (Em28xx Input 
Extension) extension
Oct 19 20:59:54 mediapi kernel: [9.612549] Adding 102396k swap on 
/var/swap.  Priority:-1 extents:3 across:200700k SSFS

Any idea?

Thanks,
Patrick

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: em28xx WinTV dualHD in Raspbian

2016-10-19 Thread ps00de 
> Based on this log:
> 
> Oct 18 23:08:01 mediapi kernel: [ 7590.369200] em28xx_dvb: disagrees about 
> version of symbol dvb_dmxdev_init Oct 18 23:08:01 mediapi kernel: [ 
> 7590.369228] em28xx_dvb: Unknown symbol dvb_dmxdev_init (err -22)
> 
> it seems you messed the modules install or you have the V4L2 stack compiled 
> builtin with a different version. 

How to fix this?

- I reinstalled the current firmware and kernel on the raspberry.
- I installed the headers with sudo apt-get install raspberrypi-kernel-headers
- Then I have cloned, build and installed the modules:

git clone git://linuxtv.org/media_build.git
cd media_build 
./build
sudo make install

But the same errors appear again.

Thanks,
Patrick

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: em28xx WinTV dualHD in Raspbian

2016-10-19 Thread Mauro Carvalho Chehab 
Em Tue, 18 Oct 2016 23:55:04 +0200
 escreveu:

> Hi there,
> 
> I am running an updated raspbian image with kernel 4.4.23-v7+, matching
> linux-headers-4.4.23-v7+_4.4.23-v7+-2_armhf from here:
> https://www.niksula.hut.fi/~mhiienka/Rpi/linux-headers-rpi/ and
> dvb-demod-si2168-b40-01.fw (see linuxtv-wiki).
> 
> Before the last apt-get upgrade this works great, but now, it ends up in
> recognizing the device but not create /dev/dvb.
> 
> Log: 
> Oct 18 23:07:59 mediapi kernel: [ 7587.975803] usb 1-1.3: new high-speed USB
> device number 6 using dwc_otg
> Oct 18 23:07:59 mediapi kernel: [ 7588.076796] usb 1-1.3: New USB device
> found, idVendor=2040, idProduct=0265
> Oct 18 23:07:59 mediapi kernel: [ 7588.076817] usb 1-1.3: New USB device
> strings: Mfr=3, Product=1, SerialNumber=2
> Oct 18 23:07:59 mediapi kernel: [ 7588.076842] usb 1-1.3: Product: dualHD
> Oct 18 23:07:59 mediapi kernel: [ 7588.076853] usb 1-1.3: Manufacturer: HCW
> Oct 18 23:07:59 mediapi kernel: [ 7588.076864] usb 1-1.3: SerialNumber:
> 0011540068
> Oct 18 23:08:00 mediapi kernel: [ 7589.111483] media: Linux media interface:
> v0.10
> Oct 18 23:08:00 mediapi kernel: [ 7589.121622] Linux video capture
> interface: v2.00
> Oct 18 23:08:00 mediapi kernel: [ 7589.126137] em28xx: New device HCW dualHD
> @ 480 Mbps (2040:0265, interface 0, class 0)
> Oct 18 23:08:00 mediapi kernel: [ 7589.126157] em28xx: DVB interface 0
> found: isoc
> Oct 18 23:08:00 mediapi kernel: [ 7589.127012] em28xx: chip ID is em28174
> Oct 18 23:08:01 mediapi kernel: [ 7590.338459] em28174 #0: EEPROM ID = 26 00
> 01 00, EEPROM hash = 0x7ee3cbc8
> Oct 18 23:08:01 mediapi kernel: [ 7590.338482] em28174 #0: EEPROM info:
> Oct 18 23:08:01 mediapi kernel: [ 7590.338496] em28174 #0:     microcode
> start address = 0x0004, boot configuration = 0x01
> Oct 18 23:08:01 mediapi kernel: [ 7590.346046] em28174 #0:     AC97 audio (5
> sample rates)
> Oct 18 23:08:01 mediapi kernel: [ 7590.346064] em28174 #0:     500mA max
> power
> Oct 18 23:08:01 mediapi kernel: [ 7590.346079] em28174 #0:     Table at
> offset 0x27, strings=0x0e6a, 0x1888, 0x087e
> Oct 18 23:08:01 mediapi kernel: [ 7590.347683] em28174 #0: Identified as
> Hauppauge WinTV-dualHD DVB (card=99)
> Oct 18 23:08:01 mediapi kernel: [ 7590.355143] tveeprom 4-0050: Hauppauge
> model 204109, rev B2I6, serial# 11540068
> Oct 18 23:08:01 mediapi kernel: [ 7590.355170] tveeprom 4-0050: tuner model
> is SiLabs Si2157 (idx 186, type 4)
> Oct 18 23:08:01 mediapi kernel: [ 7590.355188] tveeprom 4-0050: TV standards
> PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom
> 0xfc)
> Oct 18 23:08:01 mediapi kernel: [ 7590.355204] tveeprom 4-0050: audio
> processor is None (idx 0)
> Oct 18 23:08:01 mediapi kernel: [ 7590.355219] tveeprom 4-0050: has no
> radio, has IR receiver, has no IR transmitter
> Oct 18 23:08:01 mediapi kernel: [ 7590.355233] em28174 #0: dvb set to isoc
> mode.
> Oct 18 23:08:01 mediapi rsyslogd-2007: action 'action 17' suspended, next
> retry is Tue Oct 18 23:08:31 2016 [try http://www.rsyslog.com/e/2007 ]
> Oct 18 23:08:01 mediapi kernel: [ 7590.357918] usbcore: registered new
> interface driver em28xx
> Oct 18 23:08:01 mediapi kernel: [ 7590.369200] em28xx_dvb: disagrees about
> version of symbol dvb_dmxdev_init
> Oct 18 23:08:01 mediapi kernel: [ 7590.369228] em28xx_dvb: Unknown symbol
> dvb_dmxdev_init (err -22)
> […] (multiple „disagrees“ and „unknown symbol“)
> ct 18 23:08:01 mediapi kernel: [ 7590.417607] em28174 #0: Registering input
> extension
> Oct 18 23:08:01 mediapi kernel: [ 7590.455841] Registered IR keymap
> rc-hauppauge
> Oct 18 23:08:01 mediapi kernel: [ 7590.456798] input: em28xx IR (em28174 #0)
> as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0/input0
> Oct 18 23:08:01 mediapi kernel: [ 7590.457059] rc rc0: em28xx IR (em28174
> #0) as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0
> Oct 18 23:08:01 mediapi kernel: [ 7590.457715] em28174 #0: Input extension
> successfully initalized
> Oct 18 23:08:01 mediapi kernel: [ 7590.457734] em28xx: Registered (Em28xx
> Input Extension) extension
> 
> 
> Before it stopped working, I have executed the apt upgrade, installed the
> new kernel header and run 
> git clone git://linuxtv.org/media_build.git
> cd media_build 
> ./build
> sudo make install
> 
> No errors appeared.
> 
> What I am doing wrong? The last git clone was approx. in August.

Based on this log:

Oct 18 23:08:01 mediapi kernel: [ 7590.369200] em28xx_dvb: disagrees about 
version of symbol dvb_dmxdev_init
Oct 18 23:08:01 mediapi kernel: [ 7590.369228] em28xx_dvb: Unknown symbol 
dvb_dmxdev_init (err -22)

it seems you messed the modules install or you have the V4L2 stack
compiled builtin with a different version. 


Thanks,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

em28xx WinTV dualHD in Raspbian

2016-10-18 Thread ps00de 
Hi there,

I am running an updated raspbian image with kernel 4.4.23-v7+, matching
linux-headers-4.4.23-v7+_4.4.23-v7+-2_armhf from here:
https://www.niksula.hut.fi/~mhiienka/Rpi/linux-headers-rpi/ and
dvb-demod-si2168-b40-01.fw (see linuxtv-wiki).

Before the last apt-get upgrade this works great, but now, it ends up in
recognizing the device but not create /dev/dvb.

Log: 
Oct 18 23:07:59 mediapi kernel: [ 7587.975803] usb 1-1.3: new high-speed USB
device number 6 using dwc_otg
Oct 18 23:07:59 mediapi kernel: [ 7588.076796] usb 1-1.3: New USB device
found, idVendor=2040, idProduct=0265
Oct 18 23:07:59 mediapi kernel: [ 7588.076817] usb 1-1.3: New USB device
strings: Mfr=3, Product=1, SerialNumber=2
Oct 18 23:07:59 mediapi kernel: [ 7588.076842] usb 1-1.3: Product: dualHD
Oct 18 23:07:59 mediapi kernel: [ 7588.076853] usb 1-1.3: Manufacturer: HCW
Oct 18 23:07:59 mediapi kernel: [ 7588.076864] usb 1-1.3: SerialNumber:
0011540068
Oct 18 23:08:00 mediapi kernel: [ 7589.111483] media: Linux media interface:
v0.10
Oct 18 23:08:00 mediapi kernel: [ 7589.121622] Linux video capture
interface: v2.00
Oct 18 23:08:00 mediapi kernel: [ 7589.126137] em28xx: New device HCW dualHD
@ 480 Mbps (2040:0265, interface 0, class 0)
Oct 18 23:08:00 mediapi kernel: [ 7589.126157] em28xx: DVB interface 0
found: isoc
Oct 18 23:08:00 mediapi kernel: [ 7589.127012] em28xx: chip ID is em28174
Oct 18 23:08:01 mediapi kernel: [ 7590.338459] em28174 #0: EEPROM ID = 26 00
01 00, EEPROM hash = 0x7ee3cbc8
Oct 18 23:08:01 mediapi kernel: [ 7590.338482] em28174 #0: EEPROM info:
Oct 18 23:08:01 mediapi kernel: [ 7590.338496] em28174 #0:     microcode
start address = 0x0004, boot configuration = 0x01
Oct 18 23:08:01 mediapi kernel: [ 7590.346046] em28174 #0:     AC97 audio (5
sample rates)
Oct 18 23:08:01 mediapi kernel: [ 7590.346064] em28174 #0:     500mA max
power
Oct 18 23:08:01 mediapi kernel: [ 7590.346079] em28174 #0:     Table at
offset 0x27, strings=0x0e6a, 0x1888, 0x087e
Oct 18 23:08:01 mediapi kernel: [ 7590.347683] em28174 #0: Identified as
Hauppauge WinTV-dualHD DVB (card=99)
Oct 18 23:08:01 mediapi kernel: [ 7590.355143] tveeprom 4-0050: Hauppauge
model 204109, rev B2I6, serial# 11540068
Oct 18 23:08:01 mediapi kernel: [ 7590.355170] tveeprom 4-0050: tuner model
is SiLabs Si2157 (idx 186, type 4)
Oct 18 23:08:01 mediapi kernel: [ 7590.355188] tveeprom 4-0050: TV standards
PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom
0xfc)
Oct 18 23:08:01 mediapi kernel: [ 7590.355204] tveeprom 4-0050: audio
processor is None (idx 0)
Oct 18 23:08:01 mediapi kernel: [ 7590.355219] tveeprom 4-0050: has no
radio, has IR receiver, has no IR transmitter
Oct 18 23:08:01 mediapi kernel: [ 7590.355233] em28174 #0: dvb set to isoc
mode.
Oct 18 23:08:01 mediapi rsyslogd-2007: action 'action 17' suspended, next
retry is Tue Oct 18 23:08:31 2016 [try http://www.rsyslog.com/e/2007 ]
Oct 18 23:08:01 mediapi kernel: [ 7590.357918] usbcore: registered new
interface driver em28xx
Oct 18 23:08:01 mediapi kernel: [ 7590.369200] em28xx_dvb: disagrees about
version of symbol dvb_dmxdev_init
Oct 18 23:08:01 mediapi kernel: [ 7590.369228] em28xx_dvb: Unknown symbol
dvb_dmxdev_init (err -22)
[…] (multiple „disagrees“ and „unknown symbol“)
ct 18 23:08:01 mediapi kernel: [ 7590.417607] em28174 #0: Registering input
extension
Oct 18 23:08:01 mediapi kernel: [ 7590.455841] Registered IR keymap
rc-hauppauge
Oct 18 23:08:01 mediapi kernel: [ 7590.456798] input: em28xx IR (em28174 #0)
as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0/input0
Oct 18 23:08:01 mediapi kernel: [ 7590.457059] rc rc0: em28xx IR (em28174
#0) as /devices/platform/soc/3f98.usb/usb1/1-1/1-1.3/rc/rc0
Oct 18 23:08:01 mediapi kernel: [ 7590.457715] em28174 #0: Input extension
successfully initalized
Oct 18 23:08:01 mediapi kernel: [ 7590.457734] em28xx: Registered (Em28xx
Input Extension) extension


Before it stopped working, I have executed the apt upgrade, installed the
new kernel header and run 
git clone git://linuxtv.org/media_build.git
cd media_build 
./build
sudo make install

No errors appeared.

What I am doing wrong? The last git clone was approx. in August.


2nd question: Is there anything new in supporting both tuners of the dualHD
stick?


Thanks,
Patrick


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html