<div dir="ltr">Hi Stephen I tried V4L as suggested in the 4.8.5 kernel but no files generated in /dev/dvb/* and board not recognized in myth setup. <div><br></div><div>I have now re-built this box with 0.28 ISO mythbuntu-16.04.1-desktop-<wbr>amd64 to get a clean system with kernel 4.4.0-47.</div><div><br></div><div>The quad board is not recognized, the lspci -v output is the same as before ie:</div><div><div><quote></div><div>1a:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 03)</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Subsystem: Hauppauge computer works Inc. CX23885 PCI Video and Audio Decoder</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Flags: bus master, fast devsel, latency 0, IRQ 17</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Memory at f0800000 (64-bit, non-prefetchable) [size=2M]</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Capabilities: <access denied></div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Kernel driver in use: cx23885</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Kernel modules: cx23885</div><div><br></div><div>1b:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 03)</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Subsystem: Hauppauge computer works Inc. CX23885 PCI Video and Audio Decoder</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Flags: bus master, fast devsel, latency 0, IRQ 18</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Memory at f0600000 (64-bit, non-prefetchable) [size=2M]</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Capabilities: <access denied></div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Kernel driver in use: cx23885</div><div><span class="gmail-m_-6340180200586665533gmail-Apple-tab-span" style="white-space:pre-wrap"> </span>Kernel modules: cx23885</div><div></quote></div><div><br></div><div>I then tried V4L on clean 4.4 setup, the result was the same no /dev/dvb/* and the board not recognized by myth.</div><div><br></div><div>I think we may be going down the wrong track. I ordered model 1609 which was supported by <a href="https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-quadHD_(DVB-T/T2/C)" target="_blank">https://www.linuxtv.org/wiki/<wbr>index.php/Hauppauge_WinTV-<wbr>quadHD_(DVB-T/T2/C)</a>. Three months later I received model 1628. The most active response came when I installed kernel 4.8 refered to at the start of this conversation. <br></div><div><br></div><div>PS (For the family I have now re-built another box with 0.27-14.04-4.2.0-42 generic and a DigitaNow Quad tuner. We originally had multi failures when upgrading to 0.28.)</div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 11, 2016 at 12:18 PM, Stephen Worthington <span dir="ltr"><<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, 10 Nov 2016 15:23:49 +1300, you wrote:<br>
<br>
>On Thu, 10 Nov 2016 08:36:19 +1100, you wrote:<br>
><br>
>>On Tue, Nov 1, 2016 at 5:21 PM, Glen Adamson <<a href="mailto:glengilesa@gmail.com">glengilesa@gmail.com</a>> wrote:<br>
>><br>
>>> Thank you, I have emailed Hauppauge and enclosed the kern.log file to them<br>
>>> and to you.<br>
>>><br>
>>> The kernel log has a line that includes "warning: unknown hauppauge model<br>
>>> #166201". The one I ordered was #01609.<br>
>>><br>
>>> Glen<br>
>>><br>
>>> I emailed Hauppauge with the following:<br>
>><<<<<<<<<<< QUOTE >>>>>>>>>>><br>
>><br>
>>...<br>
>><br>
>>Computer: HP i5 Compaq 8100 64bit.<br>
>><br>
>>OS: mythbuntu 16.04.<br>
>><br>
>>Kernel: 4.8.5-040805-generic.<br>
>><br>
>>Application: MythTV 0.28.<br>
>><br>
>>Country: Australia DVB/T2/C.<br>
>><br>
>><br>
>><br>
>>Installed the PCIe board.<br>
>><br>
>>Copied the firmware dvb-demod-si2168-b40-01.fw to /lib/firmware/ and<br>
>>installed kernel 4.8 to get the required driver.<br>
>><br>
>><br>
>>Your Linux Support shows the lspci output to be as follows:<br>
>><br>
>><quote><br>
>>lspci -v<br>
>>04:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe<br>
>>Broadcast Audio and Video Decoder with 3D Comb (rev 04)<br>
>>Subsystem: Hauppauge computer works Inc. Device 6a18<br>
>>Flags: bus master, fast devsel, latency 0, IRQ 19<br>
>>Memory at fd200000 (64-bit, non-prefetchable) [size=2M]<br>
>>Capabilities: <access denied><br>
>>Kernel driver in use: cx23885<br>
>>05:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe<br>
>>Broadcast Audio and Video Decoder with 3D Comb (rev 04)<br>
>>Subsystem: Hauppauge computer works Inc. Device 6a18<br>
>>Flags: bus master, fast devsel, latency 0, IRQ 16<br>
>>Memory at fd000000 (64-bit, non-prefetchable) [size=2M]<br>
>>Capabilities: <access denied><br>
>>Kernel driver in use: cx23885<br>
>><br>
>></quote><br>
>><br>
>>But my lspci system output is:<br>
>><quote><br>
>>lspci -v<br>
>><br>
>>1a:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI<br>
>>Video and Audio Decoder (rev 03)<br>
>><br>
>> Subsystem: Hauppauge computer works Inc. CX23885 PCI Video and Audio<br>
>>Decoder<br>
>><br>
>> Flags: bus master, fast devsel, latency 0, IRQ 17<br>
>><br>
>> Memory at f0800000 (64-bit, non-prefetchable) [size=2M]<br>
>><br>
>> Capabilities: <access denied><br>
>><br>
>> Kernel driver in use: cx23885<br>
>><br>
>> Kernel modules: cx23885<br>
>><br>
>>1b:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI<br>
>>Video and Audio Decoder (rev 03)<br>
>><br>
>> Subsystem: Hauppauge computer works Inc. CX23885 PCI Video and Audio<br>
>>Decoder<br>
>><br>
>> Flags: bus master, fast devsel, latency 0, IRQ 18<br>
>><br>
>> Memory at f0600000 (64-bit, non-prefetchable) [size=2M]<br>
>><br>
>> Capabilities: <access denied><br>
>><br>
>> Kernel driver in use: cx23885<br>
>><br>
>> Kernel modules: cx23885<br>
>><br>
>></quote><br>
>><br>
>>I expected version (rev 04) but I got (rev 03) above and note that<br>
>>Linux Support<br>
>>chip PI7C9X2G304 is NOT listed below:<br>
>><quote><br>
>><br>
>>lsmod<br>
>>Module Size Used by<br>
>>si2157 16384 4<br>
>>si2168 20480 4<br>
>>cx23885 176128 1<br>
>>...<br>
>></quote><br>
>><br>
>>...<br>
>><br>
>><<<<<<<<<<< /QUOTE >>>>>>>>>>><br>
>><br>
>><br>
>>and have received the following one line reply:<br>
>><br>
>>"At this time we have only tested kernel 4.4. Have you tried the patch<br>
>>attached? "<br>
>><br>
>><br>
>>The patch is attached.<br>
>><br>
>><br>
>>Installing the patch is well outside my understanding of Linux, I need<br>
>>explicit step by step help to achieve a change to the kernel.<br>
>><br>
>>Should I revert back to kernel 4.4 as the very first action?<br>
>><br>
>><br>
>>Glen<br>
><br>
>The patch looks pretty straightforward - it just adds the new code for<br>
>your card (ATSC and DVB-T version), rather than changing any old code.<br>
>So it is not unlikely to work with later kernels. It would certainly<br>
>be worth trying with your current kernel's source code. If that does<br>
>not work, then you can change to the 4.4.15 kernel that patch file was<br>
>made for.<br>
><br>
>The patch is not really on the kernel itself, it is for the Video for<br>
>Linux code (V4L), which is also available as a separate set of source<br>
>code and can be compiled (and patched) and installed on top of an<br>
>existing kernel - all the V4L drivers installed by the original kernel<br>
>install are deleted and replaced by the new V4L drivers. It is<br>
>possible that the patch has already been incorporated into the later<br>
>V4L code, so it would be worth downloading a recent version and<br>
>checking that. The instructions for V4L are here:<br>
><br>
><a href="https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers" rel="noreferrer" target="_blank">https://www.linuxtv.org/wiki/<wbr>index.php/How_to_Obtain,_<wbr>Build_and_Install_V4L-DVB_<wbr>Device_Drivers</a><br>
><br>
>The first thing I would try would be seeing if the recent V4L code has<br>
>the patch already, and if it does not, seeing if the patch can be<br>
>applied to that and then compiling and installing just the new V4L,<br>
>rather than doing a complete kernel compile. It takes long enough to<br>
>do a V4L compile - a complete kernel takes ages, even when doing it on<br>
>a fast SSD with a fast multicore CPU.<br>
><br>
>If just patching V4L is not possible, then you can try patching a full<br>
>kernel. There are various guides for applying patches to kernels. For<br>
>Ubuntu, the "official" guide to building a kernel is here:<br>
><br>
><a href="https://help.ubuntu.com/community/Kernel/Compile" rel="noreferrer" target="_blank">https://help.ubuntu.com/<wbr>community/Kernel/Compile</a><br>
><br>
>You will need to apply the patch file to the source code before<br>
>building it (kernel or V4L). That is done with a patch command like<br>
>this:<br>
><br>
>cd /the/correct/directory<br>
>patch <quad_atsc_dvbt_4.4.15.patch<br>
><br>
>You may need to use a -p option on the patch command to get the levels<br>
>of directory to match (see man patch). In which case it would look<br>
>something like this:<br>
><br>
>cd /the/correct/directory<br>
>patch -p1 <quad_atsc_dvbt_4.4.15.patch<br>
><br>
>The patch command will tell you if it has any problems applying the<br>
>patch. If it says the patch is OK, it is still best to check the file<br>
>locations where the patch was done to see if it looks OK, the first<br>
>time you try the patch. Then go on with the build and install<br>
>procedure.<br>
<br>
</div></div>It looks like you are in luck. I just pulled down a copy of the V4L<br>
drivers and checked the patch against it. It has already been<br>
applied, although in slightly different form. So all you need to do<br>
is to do the "basic" build and install procedure:<br>
<br>
git clone --depth=1 git://<a href="http://linuxtv.org/media_build.git" rel="noreferrer" target="_blank">linuxtv.org/media_build.<wbr>git</a><br>
cd media_build<br>
./build<br>
make install<br>
<br>
That also means that at some future point, the drivers should be built<br>
into the standard kernels.<br>
<br>
Note that installing the V4L drivers will completely overwrite your<br>
old driver set from the installed kernel with the new V4L backport<br>
driver set. Sometimes this can cause problems with cards other than<br>
the one you are trying to get going, as there has been some change<br>
that affects them. So if your system has other V4L cards in it, you<br>
need to check that they still work properly with the new drivers<br>
installed.<br>
<br>
Also, every time you install a new kernel (eg via the normal updates),<br>
you need to re-install the V4L drivers using the same procedure.<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/<wbr>mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/<wbr>Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a><br>
</div></div></blockquote></div><br></div>