Mailing List Archive

UPDATE: Re: WinTV-dualHD TV Tuner not found.
On Mon, Sep 04, 2017 at 11:22:08PM -0400, I wrote:
> ...
> > Ian
>
> Thank you very much! At least now there's light at the end of the
> tunnel. First, I'll see if the tuner is visible to kernel 4.11,

I can report partial good news. I installed kernel 4.11 from backports
on a test machine running stretch and one tuner became visible (one
green led on the tuner). Mythtv-setup (0.28 from deb-multimedia) after
proper configuration, detected 60 channels after a channel scan.
Unfortunately, that computer has issues with the display (possibly
config issues) so using myth there is not possible until I track that
down.

> then I'll decide if I want to go the patch route or wait for the

Next, I decided to install the sources for kernel 3.16 on the myth
box that's running jessie, and apply the patch.

The excellent instructions here made it easy:

https://linuxconfig.org/building-kernels-the-debian-way

/usr/src/linux-source-3.16# patch -p1 < /tmp/hvr-9x5-19x5-22x5-kernel-3.16-2015-05-21.patch
patching file drivers/media/common/tveeprom.c
patching file drivers/media/dvb-frontends/Kconfig
patching file drivers/media/dvb-frontends/Makefile
patching file drivers/media/dvb-frontends/lgdt3306a.c
patching file drivers/media/dvb-frontends/lgdt3306a.h
patching file drivers/media/dvb-frontends/si2168b.c
patching file drivers/media/dvb-frontends/si2168b.h
patching file drivers/media/dvb-frontends/si2168b_priv.h
patching file drivers/media/dvb-frontends/silg.c
patching file drivers/media/dvb-frontends/silg.h
patching file drivers/media/pci/saa7164/Kconfig
patching file drivers/media/pci/saa7164/saa7164-api.c
patching file drivers/media/pci/saa7164/saa7164-cards.c
patching file drivers/media/pci/saa7164/saa7164-core.c
patching file drivers/media/pci/saa7164/saa7164-dvb.c
patching file drivers/media/pci/saa7164/saa7164-encoder.c
patching file drivers/media/pci/saa7164/saa7164-fw.c
patching file drivers/media/pci/saa7164/saa7164-i2c.c
patching file drivers/media/pci/saa7164/saa7164-reg.h
patching file drivers/media/pci/saa7164/saa7164-vbi.c
patching file drivers/media/pci/saa7164/saa7164.h
patching file drivers/media/tuners/Kconfig
patching file drivers/media/tuners/Makefile
patching file drivers/media/tuners/silabs_tercab.c
patching file drivers/media/tuners/silabs_tercab.h
patching file drivers/media/tuners/silabs_tercab_priv.h
patching file drivers/media/tuners/tuner-types.c
patching file drivers/media/usb/cx231xx/Kconfig
patching file drivers/media/usb/cx231xx/cx231xx-avcore.c
Hunk #6 succeeded at 1727 (offset 3 lines).
Hunk #7 succeeded at 2129 (offset 3 lines).
Hunk #8 succeeded at 2397 (offset 3 lines).
patching file drivers/media/usb/cx231xx/cx231xx-cards.c
patching file drivers/media/usb/cx231xx/cx231xx-core.c
Hunk #1 succeeded at 727 (offset 1 line).
Hunk #2 succeeded at 748 (offset 1 line).
Hunk #3 succeeded at 1386 (offset 1 line).
patching file drivers/media/usb/cx231xx/cx231xx-dvb.c
patching file drivers/media/usb/cx231xx/cx231xx-video.c
patching file drivers/media/usb/cx231xx/cx231xx.h
patching file drivers/media/usb/pvrusb2/Kconfig
patching file drivers/media/usb/pvrusb2/pvrusb2-cx2584x-v4l.c
patching file drivers/media/usb/pvrusb2/pvrusb2-devattr.c
patching file drivers/media/usb/pvrusb2/pvrusb2-devattr.h
patching file drivers/media/usb/pvrusb2/pvrusb2-dvb.c
patching file drivers/media/usb/pvrusb2/pvrusb2-fx2-cmd.h
patching file drivers/media/usb/pvrusb2/pvrusb2-hdw-internal.h
patching file drivers/media/usb/pvrusb2/pvrusb2-hdw.c
Hunk #2 succeeded at 2096 (offset -23 lines).
Hunk #3 succeeded at 2149 (offset -23 lines).
Hunk #4 succeeded at 2231 (offset -23 lines).
Hunk #5 succeeded at 4056 (offset -23 lines).
patching file drivers/media/v4l2-core/tuner-core.c
patching file include/media/tuner.h

After applying the patch:

cp /boot/config-3.16.0-4-amd64 .config
make-kpkg --rootcmd fakeroot --initrd --us --uc kernel_image

After the compilation ended:

# cd ..
# dpkg -i linux-image-3.16.43_3.16.43-10.00.Custom_amd64.deb

and reboot. Tuner not recognized. No green led and mythtv-setup
doesn't see it. Not sure what's missing. Maybe this is not the only
patch that's needed, or it's possibly the wrong patch. Does anyone
know?

> After that, I'll have to upgrade the myth machine (liva X) that is still
> running jessie.

Since the above didn't work, I'm now upgrading the myth machine to
stretch. After changing all "jessie" to "stretch" in /etc/apt/soures.list:

apt-get update
apt-get dist-upgrade.

Then I'll install the backports kernel 4.11 and I'll have at least one
tuner.

Does anyone know what Debian kernel has the 2-tuner patch/addition?

Augustine

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: UPDATE: Re: WinTV-dualHD TV Tuner not found. [ In reply to ]
On 09/09/17 23:40, A. F. Cano wrote:
> On Mon, Sep 04, 2017 at 11:22:08PM -0400, I wrote:
>> ...
>>> Ian
>> Thank you very much! At least now there's light at the end of the
>> tunnel. First, I'll see if the tuner is visible to kernel 4.11,
> I can report partial good news. I installed kernel 4.11 from backports
> on a test machine running stretch and one tuner became visible (one
> green led on the tuner). Mythtv-setup (0.28 from deb-multimedia) after
> proper configuration, detected 60 channels after a channel scan.
> Unfortunately, that computer has issues with the display (possibly
> config issues) so using myth there is not possible until I track that
> down.
>
>> then I'll decide if I want to go the patch route or wait for the
> Next, I decided to install the sources for kernel 3.16 on the myth
> box that's running jessie, and apply the patch.
>
> The excellent instructions here made it easy:
>
> https://linuxconfig.org/building-kernels-the-debian-way
>
> /usr/src/linux-source-3.16# patch -p1 < /tmp/hvr-9x5-19x5-22x5-kernel-3.16-2015-05-21.patch
> patching file drivers/media/common/tveeprom.c
> patching file drivers/media/dvb-frontends/Kconfig
> patching file drivers/media/dvb-frontends/Makefile
> patching file drivers/media/dvb-frontends/lgdt3306a.c
> patching file drivers/media/dvb-frontends/lgdt3306a.h
> patching file drivers/media/dvb-frontends/si2168b.c
> patching file drivers/media/dvb-frontends/si2168b.h
> patching file drivers/media/dvb-frontends/si2168b_priv.h
> patching file drivers/media/dvb-frontends/silg.c
> patching file drivers/media/dvb-frontends/silg.h
> patching file drivers/media/pci/saa7164/Kconfig
> patching file drivers/media/pci/saa7164/saa7164-api.c
> patching file drivers/media/pci/saa7164/saa7164-cards.c
> patching file drivers/media/pci/saa7164/saa7164-core.c
> patching file drivers/media/pci/saa7164/saa7164-dvb.c
> patching file drivers/media/pci/saa7164/saa7164-encoder.c
> patching file drivers/media/pci/saa7164/saa7164-fw.c
> patching file drivers/media/pci/saa7164/saa7164-i2c.c
> patching file drivers/media/pci/saa7164/saa7164-reg.h
> patching file drivers/media/pci/saa7164/saa7164-vbi.c
> patching file drivers/media/pci/saa7164/saa7164.h
> patching file drivers/media/tuners/Kconfig
> patching file drivers/media/tuners/Makefile
> patching file drivers/media/tuners/silabs_tercab.c
> patching file drivers/media/tuners/silabs_tercab.h
> patching file drivers/media/tuners/silabs_tercab_priv.h
> patching file drivers/media/tuners/tuner-types.c
> patching file drivers/media/usb/cx231xx/Kconfig
> patching file drivers/media/usb/cx231xx/cx231xx-avcore.c
> Hunk #6 succeeded at 1727 (offset 3 lines).
> Hunk #7 succeeded at 2129 (offset 3 lines).
> Hunk #8 succeeded at 2397 (offset 3 lines).
> patching file drivers/media/usb/cx231xx/cx231xx-cards.c
> patching file drivers/media/usb/cx231xx/cx231xx-core.c
> Hunk #1 succeeded at 727 (offset 1 line).
> Hunk #2 succeeded at 748 (offset 1 line).
> Hunk #3 succeeded at 1386 (offset 1 line).
> patching file drivers/media/usb/cx231xx/cx231xx-dvb.c
> patching file drivers/media/usb/cx231xx/cx231xx-video.c
> patching file drivers/media/usb/cx231xx/cx231xx.h
> patching file drivers/media/usb/pvrusb2/Kconfig
> patching file drivers/media/usb/pvrusb2/pvrusb2-cx2584x-v4l.c
> patching file drivers/media/usb/pvrusb2/pvrusb2-devattr.c
> patching file drivers/media/usb/pvrusb2/pvrusb2-devattr.h
> patching file drivers/media/usb/pvrusb2/pvrusb2-dvb.c
> patching file drivers/media/usb/pvrusb2/pvrusb2-fx2-cmd.h
> patching file drivers/media/usb/pvrusb2/pvrusb2-hdw-internal.h
> patching file drivers/media/usb/pvrusb2/pvrusb2-hdw.c
> Hunk #2 succeeded at 2096 (offset -23 lines).
> Hunk #3 succeeded at 2149 (offset -23 lines).
> Hunk #4 succeeded at 2231 (offset -23 lines).
> Hunk #5 succeeded at 4056 (offset -23 lines).
> patching file drivers/media/v4l2-core/tuner-core.c
> patching file include/media/tuner.h
>
> After applying the patch:
>
> cp /boot/config-3.16.0-4-amd64 .config
> make-kpkg --rootcmd fakeroot --initrd --us --uc kernel_image
>
> After the compilation ended:
>
> # cd ..
> # dpkg -i linux-image-3.16.43_3.16.43-10.00.Custom_amd64.deb
>
> and reboot. Tuner not recognized. No green led and mythtv-setup
> doesn't see it. Not sure what's missing. Maybe this is not the only
> patch that's needed, or it's possibly the wrong patch. Does anyone
> know?
>
>> After that, I'll have to upgrade the myth machine (liva X) that is still
>> running jessie.
> Since the above didn't work, I'm now upgrading the myth machine to
> stretch. After changing all "jessie" to "stretch" in /etc/apt/soures.list:
>
> apt-get update
> apt-get dist-upgrade.
>
> Then I'll install the backports kernel 4.11 and I'll have at least one
> tuner.
>
> Does anyone know what Debian kernel has the 2-tuner patch/addition?
>
> Augustine
>
Don't know about any kernel supporting 2 tuner patch on Ubuntu or Debian.
As far as I can tell such patches are not yet in upstream.

I recently purchased a Hauppauge WinTV QuadHD DVB-T/T/C tuner which does
work in Ubuntu 16.04 LTS (series 4.10 kernel) and Debian Stretch
(series 4.9 kernel).
output of dmesg shows some errors like unrecognised card version
[ 12.419603] cx23885: cx23885[0]: warning: unknown hauppauge model #166200
[ 12.795285] cx23885: cx23885[1]: warning: unknown hauppauge model #166201

The Hauppauge repo does contain patches for this card and for 2-tuner patch.

You could try applying these Hauppauge patches to latest V4L media stack
and see if it solves your problem.
The following outlines how do this, it works on my Ubuntu 16.04 LTS
system and tested with my card ( and does build ok on Debian Stretch -
not actually tested with my card)

# This uses Developer's Approach at
https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
#create new directory e.g
mkdir -p v4l_rebuild
cd v4l_rebuild
#clone v4l repo
git clone --depth=1 git://linuxtv.org/media_build.git
# clone hauppauge repo
git clone https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder.git
# build v4l for the first time
cd media_build
./build --main-git --depth 1
#now apply patches from hauppauge repo ubuntu-artful-4.12.0/extra/
cd media
for i in
../../Ubuntu-media-tree-kernel-builder/patches/ubuntu-artful-4.12.0/extra/*.patch
; do patch -p1 <$i; done
# make sure patches apply cleanly - ignore offset changes, do not go
any further if you get rejects, the rest is not going to work
make -C ../v4l
sudo make -C ../ install
sudo reboot
# check output of dmesg command for errors

To purge the new media stack reinstall your kernel and reboot.

Mike


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: UPDATE: Re: WinTV-dualHD TV Tuner not found. [ In reply to ]
On Sun, 2017-09-10 at 16:09 +0100, Mike Bibbings wrote:
> > Does anyone know what Debian kernel has the 2-tuner patch/addition?
>
> Don't know about any kernel supporting 2 tuner patch on Ubuntu or Debian.
> As far as I can tell such patches are not yet in upstream.

This is relevant because Debian's policy is to only accept patches
which are upstream. Once they are in upstream they might be backported
if there is demand, or else one has to be patient and wait for the
newer kernel version to filter through the various release systems.

Linux has a merge window open now, so fingers crossed for this patch
going in for v4.14!

Ian.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: UPDATE 2: Re: WinTV-dualHD TV Tuner now found (1 tuner) [ In reply to ]
On Sun, Sep 10, 2017 at 07:03:59PM +0100, Ian Campbell wrote:
> On Sun, 2017-09-10 at 16:09 +0100, Mike Bibbings wrote:
> > > Does anyone know what Debian kernel has the 2-tuner patch/addition?
> >
> > Don't know about any kernel supporting 2 tuner patch on Ubuntu or Debian.
> > As far as I can tell such patches are not yet in upstream.
>
> This is relevant because Debian's policy is to only accept patches
> which are upstream. Once they are in upstream they might be backported
> if there is demand, or else one has to be patient and wait for the
> newer kernel version to filter through the various release systems.
>
> Linux has a merge window open now, so fingers crossed for this patch
> going in for v4.14!

I hope it makes it into stretch-backports soon!

I have now finished upgrading the myth box from Debian Jessie to
Stretch. It was a long process with some hickups. I had to clean up
some broken packages and old dependencies with apt-get and dpkg since
aptitude became unusable at some point. The worse part though is that
the differences between kde 4 (jessie) and kde 5 (stretch) are so big
and incompatible that I'll be trying to recover my favorite look and
feel for weeks to come. Just about all my favorite applets are gone
and the configuration didn't carry though at all. This computer doesn't
just display myth on the tv.

Then I installed the stretch-backports kernel (now 4.12) and upon
reboot, the tuner was recognized. I now have 1 tuner, so I'm back
to where I was before the old OnAir Creator died.

In contrast to that, the upgrede of myth 0.27 (jessie) to 0.28
(stretch), packaged by deb-multimedia, was super easy. Mythtv-setup
recognized the tuner and the configuration was straightforward. Upon
first start I was asked to confirm the upgrade of schema and the
database was soon filling up with EIT data.

I have noticed one improvement/bug fix: in 0.27 I used to have to start
the frontend that displayed on the TV (hdmi connection) with

mythfrontend -w -geometry +1920+0

as Debian puts the HDMI display to the right of the primary VGA display
and the -w was necessary or the playback wouldn't start on the same
screen as the front end interface was.

This has now been fixed (in 0.28) and only

mythfrontend -geometry +1920+0

is needed. I still get overscan, which doesn't happen when I start
mythfronend on the primary screen. I usually have 2 front-ends running,
one on each screen.

Xrandr reports this:

Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 880mm x 490mm
1920x1080 60.00*+
1680x1050 59.95
1440x900 59.89
1360x768 60.02
1024x768 60.00
800x600 60.32
640x480 59.94
720x400 70.08
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 1209mm x 680mm
1920x1080 60.00*+ 50.00 59.94 30.00 25.00 24.00 29.97 23.98
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.90
1366x768 59.79
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32
720x576 50.00
720x576i 50.00
720x480 60.00 59.94
720x480i 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08

I don't understand why I'm getting myth displayed too big on the TV.
All 4 edges are cut off, the clock and date on the bottom edge are cut off
in half and only the top half is visible. The same happens with video.

Is there anything I can do in myth to tell it to conform to the display
size that xrandr reports? (1920x1080) Or do I have to set some
parameter in some X config file? Keep in mind that this has to be
specific to the HDMI screen. Like I said, when running on the
primary screen (VGA-1) it works like it should.

Thanks for all the help so far!

> Ian.

Augustine

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: UPDATE 2: Re: WinTV-dualHD TV Tuner now found (1 tuner) [ In reply to ]
On 09/17/2017 04:57 PM, A. F. Cano wrote:
> I don't understand why I'm getting myth displayed too big on the TV.
> All 4 edges are cut off, the clock and date on the bottom edge are cut off
> in half and only the top half is visible. The same happens with video.
>
> Is there anything I can do in myth to tell it to conform to the display
> size that xrandr reports? (1920x1080) Or do I have to set some
> parameter in some X config file? Keep in mind that this has to be
> specific to the HDMI screen. Like I said, when running on the
> primary screen (VGA-1) it works like it should.

What I do with TVs with overscan is use the Frontend setup, appearance,
to set the GUI size and x and y coordinates. It is a trial-and-error
process, changing the settings a bit at a time until it looks right.
Also use the "Use GUI size for TV playback" setting to ensure the video
playback conforms as well.

If you have two different type screens on the same computer then I
suggest you set a different name for one of them so that the screen size
adjustments only apply to the correct screen. If your two screens are
logged onto different user ids, then in the user id for the second
screen .mythtv/config.xml, change the setting
<LocalHostName>my-unique-identifier-goes-here</LocalHostName> . This
normally defaults to the machine name, set a different name for the
second screen for example your machine name with a 1 at the end.


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org