From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: <ps00de@yahoo.de>
Cc: <linux-media@vger.kernel.org>
Subject: Re: em28xx WinTV dualHD in Raspbian
Date: Wed, 19 Oct 2016 17:14:19 -0200 [thread overview]
Message-ID: <20161019171419.3343cdd5@vento.lan> (raw)
In-Reply-To: <000901d22a39$9de21e70$d9a65b50$@yahoo.de>
Em Wed, 19 Oct 2016 20:50:09 +0200
<ps00de@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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Thanks,
Mauro
next prev parent reply other threads:[~2016-10-19 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 18:50 em28xx WinTV dualHD in Raspbian ps00de
2016-10-19 19:14 ` Mauro Carvalho Chehab [this message]
2016-10-22 17:36 ` AW: " ps00de
2016-10-23 10:03 ` Andrey Utkin
2016-10-23 10:14 ` Olli Salonen
2016-10-23 12:02 ` AW: " ps00de
2016-11-03 20:45 ` Christian Steiner
2016-11-07 20:02 ` AW: " ps00de
-- strict thread matches above, loose matches on Subject: below --
2016-10-18 21:55 ps00de
2016-10-19 15:35 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161019171419.3343cdd5@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-media@vger.kernel.org \
--cc=ps00de@yahoo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).