Mailing List Archive

1 2 3  View All
Re: HDPVR intermittent failure [ In reply to ]
On Wed, Jul 29, 2020 at 1:53 PM Will Dormann <wdormann@gmail.com> wrote:

> On 7/29/20 2:27 PM, DryHeat122 wrote:
> > I wasn't sure exactly what John P was referring to re fixes/31. I did
> > not apply any fixes, just installed latest distro of 18.04. I actually
> > started with xubuntu 20.04 but had problems with screen-timeouts that I
> > couldn't resolve. Tried ubuntu 20.04 but it crashed right after install
> > during the update process. My mobo is like 10 years old so I suspect
> > there may have been some hardware incompatibilities. Went to 18.04 and
> > it installed smoothly.
>
> Interesting. So if you're running the Ubuntu-provided MythTV, I'd say
> that you're running 29.1+fixes, if I'm reading
> https://packages.ubuntu.com/bionic/mythtv right?
>
> I'm running 29.1+fixes myself on 16.04, as my Mythbuntu PPA:
>
> https://launchpad.net/~mythbuntu/+archive/ubuntu/0.29/+sourcepub/10541501/+listing-archive-extra
> as my current MythTV machine's origins can be traced to MythBuntu rather
> than Ubuntu + the MythTV package.
>
> If you are indeed on 29.1+fixes from Ubuntu and your HD PVR 2 works,
> then I suspect it may be fair to say that the statement in the github
> page of "If you want to use this with MythTV, you will want fixes/31 or
> later." may be incorrect?
>
> John P: Can you share your motivations for this requirement?
>

I just pushed a change to the README to be more clear. I hope that helps
avoid the confusion.

John
Re: HDPVR intermittent failure [ In reply to ]
>
> 1) Ubuntu 16.04 reaches EOL on April 2021, which hasn't arrived yet. So
> it seems odd that the upload to support 16.04 wouldn't be allowed for
> that reason.
>

I guess I misremembered why I wasn't supporting 16.04. It was either I
elected to support the latest Ubuntu LTS version available when John Poet
initially released the code (2018), I ran out of space on launchpad (I was
rolling my own mythbuntu variant at the time) or I was already using a more
modern version of ubuntu (most likely reason). Possibly even a combination
of all of the above :)

At any rate, I just tried pushing a 16.04 version to launchpad and it took
it. Unfortunately, it's unable to build due to the xxd dependency not
being available in Xenial. If I get bored, I may configure pbuilder
for xenial and try to hunt down a ppa to link into the build to resolve the
dependency. If anyone else has solved the dependency issues for Xenial or
has created a patch file to patch the code (again for xenial) let me know
as copying someone else's work will get me to a working solution faster.
Re: HDPVR intermittent failure [ In reply to ]
>
> At any rate, I just tried pushing a 16.04 version to launchpad and it took
> it. Unfortunately, it's unable to build due to the xxd dependency not
> being available in Xenial. If I get bored, I may configure pbuilder
> for xenial and try to hunt down a ppa to link into the build to resolve the
> dependency. If anyone else has solved the dependency issues for Xenial or
> has created a patch file to patch the code (again for xenial) let me know
> as copying someone else's work will get me to a working solution faster.
>

Well, I got through the dependency issues and even a debbuilder version
snag then got stymied by a compile error (the same one that kicked off
Steve's upgrade adventure). Unfortunately, this means you really need a
Xenial system to sort out how to get the drivers to compile and generate
the .dsc file necessary to automate the build with launchpad.

If anyone does sort out the required dependencies and gets this to build
(in Xenial), please post your build adventure to the mailing list (...and
if you choose to your .dsc file from debuild...). With that info I can
probably get a version posted to my ppa.
Re: HDPVR intermittent failure [ In reply to ]
>
> If anyone does sort out the required dependencies and gets this to build
> (in Xenial), please post your build adventure to the mailing list (...and
> if you choose to your .dsc file from debuild...). With that info I can
> probably get a version posted to my ppa.
>

So after staring at this for a few more minutes, I now have a version that
compiles with pbuilder and is also posted to my ppa (
https://launchpad.net/~john-hoyt/+archive/ubuntu/hauppaugeusb/+packages).

The big issues with compiling were

1. replacing the xxd package with vim-common as that's where Xenial
hides the xxd executable.
2. modifying the source in "Common/Rx/audio_CS8416.cpp" to add an
include statement to cstring and changing the call to memcpy to be
std::memcpy

Here's the diff for a patch file for "Common/Rx/audio_CS8416.cpp:

--- Common/Rx/audio_CS8416.cpp 2016-09-26 16:35:49.000000000 -0400
+++ Common/Rx/audio_CS8416.cpp 2020-07-31 18:11:02.281056836 -0400
@@ -17,6 +17,7 @@
#include <cstdint>
#include <map>
#include <stdexcept>
+#include <cstring>

#include "audio_CS8416.h"

@@ -170,7 +171,7 @@
else {
sendbuff = static_cast<uint8_t*>(malloc(len + 1));
*sendbuff = static_cast<uint8_t>(reg);
- memcpy(sendbuff + 1, data, len);
+ std::memcpy(sendbuff + 1, data, len);
}

result = m_fx2.I2CWrite(CS8416_DEVICE_ADDR, sendbuff, len + 1);


@John Poet - it may be worth appending some instructions to your
gitrepo Readme.md noting Ubuntu Xenial users will need to install
dependencies with

"sudo apt-get install libboost-log-dev libboost-program-options-dev
libusb-1.0-0-dev build-essential"


As well as apply the patch.

~John
Re: HDPVR intermittent failure [ In reply to ]
>
> @John Poet - it may be worth appending some instructions to your
> gitrepo Readme.md noting Ubuntu Xenial users will need to install
> dependencies with
>
> "sudo apt-get install libboost-log-dev libboost-program-options-dev
> libusb-1.0-0-dev build-essential"
>
>
Sorry that should have read

"sudo apt-get install libboost-log-dev libboost-program-options-dev
libusb-1.0-0-dev build-essential vim-common"
Re: HDPVR intermittent failure [ In reply to ]
On Tue, Jul 28, 2020 at 9:10 PM DryHeat122 <dryheat122@gmail.com> wrote:

>
> [snip]
>
> Just to report...I was sitting here watching a recorded program on Myth,
> when I saw an unfamiliar flash over by the equipment. It was HDPVR2 firing
> up to record something. Unfortunately I don't yet have a channel change
> solution (my FireWire seems to have crapped out) but at least the recorder
> looks to be in good working order. Thank you all so much for the input and
> especially John P for writing then sharing his software.
>
>
Well guys, I spoke a little too soon. Today after solving my
firewire/channel-change problem, I decided to do a test recording via
myth. It failed. I went and tried to do a test recording via command line
and got:

$ /opt/Hauppauge/bin/hauppauge2 -s E524-00-00ABAE4A -i 1 -a 1 -o
/tmp/test.ts
2020-07-31T17:16:38.480742 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
Changing loglevel to NOTC
2020-07-31T17:16:38.480920 CRIT <main> hauppauge2.cpp:347 (main) Starting up
Failed to open dev.
2020-07-31T17:16:38.489129 CRIT <main> hauppauge2.cpp:355 (main) Device
E524-00-00ABAE4A not found on USB bus.

I rebooted and tried again. Same result. But lsusb finds it:

Bus 001 Device 002: ID 2040:e524 Hauppauge

Tried the steps under "troubleshooting" on JohnP's the git page. I
couldn't find the suggested log entry in syslog or mythbackend.log (not
sure what log it's referring to). So I used the bus 1 as given in lsusb.
Still won't do a test recording.

Before I tried the myth test recording I had gone into setup to make sure
the tuning timeout was 15 sec as suggested. I found this in
mythtv-setup.log

/var/log/mythtv/mythtv-setup.log:Jul 31 16:57:21 steve-EP45-UD3P
mythtv-setup.real: mythtv-setup[589]: E ScreenLoad v4l2util.cpp:42 (Open)
V4L2(): Could not open '/opt/Hauppauge/bin/hauppauge2 -c
/opt/Hauppauge/etc/hdpvr2-1.conf': #012#011#011#011eno: No such file or
directory (2)

But both files are there and seem to have the necessary permissions. The
right serial number is in hdpvr2-1.conf:

-rwxr-xr-x 1 root root 1707408 Jul 25 10:57 hauppauge2
-rwxr-xr-x 1 root root 1940 Jul 27 12:50 hdpvr2-1.conf


How to proceed?
Re: HDPVR intermittent failure [ In reply to ]
On Fri, Jul 31, 2020 at 6:43 PM DryHeat122 <dryheat122@gmail.com> wrote:

>
>
> On Tue, Jul 28, 2020 at 9:10 PM DryHeat122 <dryheat122@gmail.com> wrote:
>
>>
>> [snip]
>>
>> Just to report...I was sitting here watching a recorded program on Myth,
>> when I saw an unfamiliar flash over by the equipment. It was HDPVR2 firing
>> up to record something. Unfortunately I don't yet have a channel change
>> solution (my FireWire seems to have crapped out) but at least the recorder
>> looks to be in good working order. Thank you all so much for the input and
>> especially John P for writing then sharing his software.
>>
>>
> Well guys, I spoke a little too soon. Today after solving my
> firewire/channel-change problem, I decided to do a test recording via
> myth. It failed. I went and tried to do a test recording via command line
> and got:
>
> $ /opt/Hauppauge/bin/hauppauge2 -s E524-00-00ABAE4A -i 1 -a 1 -o
> /tmp/test.ts
> 2020-07-31T17:16:38.480742 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
> Changing loglevel to NOTC
> 2020-07-31T17:16:38.480920 CRIT <main> hauppauge2.cpp:347 (main) Starting
> up
> Failed to open dev.
> 2020-07-31T17:16:38.489129 CRIT <main> hauppauge2.cpp:355 (main) Device
> E524-00-00ABAE4A not found on USB bus.
>
> I rebooted and tried again. Same result. But lsusb finds it:
>
> Bus 001 Device 002: ID 2040:e524 Hauppauge
>
> Tried the steps under "troubleshooting" on JohnP's the git page. I
> couldn't find the suggested log entry in syslog or mythbackend.log (not
> sure what log it's referring to). So I used the bus 1 as given in lsusb.
> Still won't do a test recording.
>
> Before I tried the myth test recording I had gone into setup to make sure
> the tuning timeout was 15 sec as suggested. I found this in
> mythtv-setup.log
>
> /var/log/mythtv/mythtv-setup.log:Jul 31 16:57:21 steve-EP45-UD3P
> mythtv-setup.real: mythtv-setup[589]: E ScreenLoad v4l2util.cpp:42 (Open)
> V4L2(): Could not open '/opt/Hauppauge/bin/hauppauge2 -c
> /opt/Hauppauge/etc/hdpvr2-1.conf': #012#011#011#011eno: No such file or
> directory (2)
>
> But both files are there and seem to have the necessary permissions. The
> right serial number is in hdpvr2-1.conf:
>
> -rwxr-xr-x 1 root root 1707408 Jul 25 10:57 hauppauge2
> -rwxr-xr-x 1 root root 1940 Jul 27 12:50 hdpvr2-1.conf
>
>
> How to proceed?
>

V4L2() is wrong. Somehow you have it setup with the wrong tuner "type".
That should say Extern, since you are using an External Recorder. Try
deleting that capture device and set it up again.

John
Re: HDPVR intermittent failure [ In reply to ]
On Fri, Jul 31, 2020 at 5:58 PM John P Poet <jppoet@gmail.com> wrote:

>
>
> On Fri, Jul 31, 2020 at 6:43 PM DryHeat122 <dryheat122@gmail.com> wrote:
>
>>
>>
>> On Tue, Jul 28, 2020 at 9:10 PM DryHeat122 <dryheat122@gmail.com> wrote:
>>
>>>
>>> [snip]
>>>
>>> Just to report...I was sitting here watching a recorded program on Myth,
>>> when I saw an unfamiliar flash over by the equipment. It was HDPVR2 firing
>>> up to record something. Unfortunately I don't yet have a channel change
>>> solution (my FireWire seems to have crapped out) but at least the recorder
>>> looks to be in good working order. Thank you all so much for the input and
>>> especially John P for writing then sharing his software.
>>>
>>>
>> Well guys, I spoke a little too soon. Today after solving my
>> firewire/channel-change problem, I decided to do a test recording via
>> myth. It failed. I went and tried to do a test recording via command line
>> and got:
>>
>> $ /opt/Hauppauge/bin/hauppauge2 -s E524-00-00ABAE4A -i 1 -a 1 -o
>> /tmp/test.ts
>> 2020-07-31T17:16:38.480742 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
>> Changing loglevel to NOTC
>> 2020-07-31T17:16:38.480920 CRIT <main> hauppauge2.cpp:347 (main) Starting
>> up
>> Failed to open dev.
>> 2020-07-31T17:16:38.489129 CRIT <main> hauppauge2.cpp:355 (main) Device
>> E524-00-00ABAE4A not found on USB bus.
>>
>> I rebooted and tried again. Same result. But lsusb finds it:
>>
>> Bus 001 Device 002: ID 2040:e524 Hauppauge
>>
>> Tried the steps under "troubleshooting" on JohnP's the git page. I
>> couldn't find the suggested log entry in syslog or mythbackend.log (not
>> sure what log it's referring to). So I used the bus 1 as given in lsusb.
>> Still won't do a test recording.
>>
>> Before I tried the myth test recording I had gone into setup to make sure
>> the tuning timeout was 15 sec as suggested. I found this in
>> mythtv-setup.log
>>
>> /var/log/mythtv/mythtv-setup.log:Jul 31 16:57:21 steve-EP45-UD3P
>> mythtv-setup.real: mythtv-setup[589]: E ScreenLoad v4l2util.cpp:42 (Open)
>> V4L2(): Could not open '/opt/Hauppauge/bin/hauppauge2 -c
>> /opt/Hauppauge/etc/hdpvr2-1.conf': #012#011#011#011eno: No such file or
>> directory (2)
>>
>> But both files are there and seem to have the necessary permissions. The
>> right serial number is in hdpvr2-1.conf:
>>
>> -rwxr-xr-x 1 root root 1707408 Jul 25 10:57 hauppauge2
>> -rwxr-xr-x 1 root root 1940 Jul 27 12:50 hdpvr2-1.conf
>>
>>
>> How to proceed?
>>
>
> V4L2() is wrong. Somehow you have it setup with the wrong tuner "type".
> That should say Extern, since you are using an External Recorder. Try
> deleting that capture device and set it up again.
>
> John
>

I did set it up as an external recorder, but I will delete and try again.
Before that, though, I would like to be sure I can make a command line
test recording. Any idea why it's saying it can't open
/opt/Hauppauge/bin/hauppauge2 when it is there and is executable?
Re: HDPVR intermittent failure [ In reply to ]
On Sat, 1 Aug 2020 at 17:26, DryHeat122 <dryheat122@gmail.com> wrote:

> Any idea why it's saying it can't open /opt/Hauppauge/bin/hauppauge2 when
> it is there and is executable?
>

Just a thought - have you checked the permissions along the whole path?

--
Cheers, Ian
Re: HDPVR intermittent failure [ In reply to ]
On Wed, Jul 29, 2020, 12:52 PM Will Dormann <wdormann@gmail.com> wrote:

> [Snip]
>
> Which perhaps brings us to what I intended to be my original point:
> Is there any guide (e.g. a wiki where people could contribute) that may
> serve as a single source of the information that one might need before
> attempting an upgrade of a MythTV system? Which might include things
> that change on the OS level (e.g. lirc) or things that change on the
> MythTV level (e.g. XMLTV)
>

Not that I know of. You just have to slog through it.

>
Re: HDPVR intermittent failure [ In reply to ]
On Sat, Aug 1, 2020 at 9:25 AM DryHeat122 <dryheat122@gmail.com> wrote:

>
>
> On Fri, Jul 31, 2020 at 5:58 PM John P Poet <jppoet@gmail.com> wrote:
>
>>
>>
>> On Fri, Jul 31, 2020 at 6:43 PM DryHeat122 <dryheat122@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, Jul 28, 2020 at 9:10 PM DryHeat122 <dryheat122@gmail.com> wrote:
>>>
>>>>
>>>> [snip]
>>>>
>>>> Just to report...I was sitting here watching a recorded program on
>>>> Myth, when I saw an unfamiliar flash over by the equipment. It was HDPVR2
>>>> firing up to record something. Unfortunately I don't yet have a channel
>>>> change solution (my FireWire seems to have crapped out) but at least the
>>>> recorder looks to be in good working order. Thank you all so much for the
>>>> input and especially John P for writing then sharing his software.
>>>>
>>>>
>>> Well guys, I spoke a little too soon. Today after solving my
>>> firewire/channel-change problem, I decided to do a test recording via
>>> myth. It failed. I went and tried to do a test recording via command line
>>> and got:
>>>
>>> $ /opt/Hauppauge/bin/hauppauge2 -s E524-00-00ABAE4A -i 1 -a 1 -o
>>> /tmp/test.ts
>>> 2020-07-31T17:16:38.480742 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
>>> Changing loglevel to NOTC
>>> 2020-07-31T17:16:38.480920 CRIT <main> hauppauge2.cpp:347 (main)
>>> Starting up
>>> Failed to open dev.
>>> 2020-07-31T17:16:38.489129 CRIT <main> hauppauge2.cpp:355 (main) Device
>>> E524-00-00ABAE4A not found on USB bus.
>>>
>>> I rebooted and tried again. Same result. But lsusb finds it:
>>>
>>> Bus 001 Device 002: ID 2040:e524 Hauppauge
>>>
>>> Tried the steps under "troubleshooting" on JohnP's the git page. I
>>> couldn't find the suggested log entry in syslog or mythbackend.log (not
>>> sure what log it's referring to). So I used the bus 1 as given in lsusb.
>>> Still won't do a test recording.
>>>
>>> Before I tried the myth test recording I had gone into setup to make
>>> sure the tuning timeout was 15 sec as suggested. I found this in
>>> mythtv-setup.log
>>>
>>> /var/log/mythtv/mythtv-setup.log:Jul 31 16:57:21 steve-EP45-UD3P
>>> mythtv-setup.real: mythtv-setup[589]: E ScreenLoad v4l2util.cpp:42 (Open)
>>> V4L2(): Could not open '/opt/Hauppauge/bin/hauppauge2 -c
>>> /opt/Hauppauge/etc/hdpvr2-1.conf': #012#011#011#011eno: No such file or
>>> directory (2)
>>>
>>> But both files are there and seem to have the necessary permissions.
>>> The right serial number is in hdpvr2-1.conf:
>>>
>>> -rwxr-xr-x 1 root root 1707408 Jul 25 10:57 hauppauge2
>>> -rwxr-xr-x 1 root root 1940 Jul 27 12:50 hdpvr2-1.conf
>>>
>>>
>>> How to proceed?
>>>
>>
>> V4L2() is wrong. Somehow you have it setup with the wrong tuner "type".
>> That should say Extern, since you are using an External Recorder. Try
>> deleting that capture device and set it up again.
>>
>> John
>>
>
> I did set it up as an external recorder, but I will delete and try again.
> Before that, though, I would like to be sure I can make a command line
> test recording. Any idea why it's saying it can't open
> /opt/Hauppauge/bin/hauppauge2 when it is there and is executable?
>

It's because I was not running the command as sudo. I did so, and can now
get a test recording.

I went through the suggested procedure of deleting the hdpvr2 card and
recreating the capture card. I made sure to use the "external (black box)"
card, and the card description says "external." I am still getting the
same entry in mythtv-setup.log (i.e. with V4L2) ; however, now myth can
tune/record the hdpvr2. Hopefully it will stay that way.
Re: HDPVR intermittent failure [ In reply to ]
>
> It's because I was not running the command as sudo. I did so, and can now
> get a test recording.
>
> I went through the suggested procedure of deleting the hdpvr2 card and
> recreating the capture card. I made sure to use the "external (black box)"
> card, and the card description says "external." I am still getting the
> same entry in mythtv-setup.log (i.e. with V4L2) ; however, now myth can
> tune/record the hdpvr2. Hopefully it will stay that way.
>
>
You shouldn't need to run with sudo. Have you created the custom udev rule
(per jpoet's instructions on his github page) and added the mythtv user to
the video user group?
Re: HDPVR intermittent failure [ In reply to ]
On Sat, Aug 1, 2020 at 10:47 AM John Hoyt <john.hoyt@gmail.com> wrote:

>
>
>> It's because I was not running the command as sudo. I did so, and can
>> now get a test recording.
>>
>> I went through the suggested procedure of deleting the hdpvr2 card and
>> recreating the capture card. I made sure to use the "external (black box)"
>> card, and the card description says "external." I am still getting the
>> same entry in mythtv-setup.log (i.e. with V4L2) ; however, now myth can
>> tune/record the hdpvr2. Hopefully it will stay that way.
>>
>>
> You shouldn't need to run with sudo. Have you created the custom udev
> rule (per jpoet's instructions on his github page) and added the mythtv
> user to the video user group?
>

I did create /etc/udev/rules.d/99-Hauppauge.rules

/etc/udev/rules.d$ ls -la
total 72
drwxr-xr-x 2 root root 4096 Aug 1 09:21 .
drwxr-xr-x 4 root root 4096 Jul 26 10:49 ..
-rw-r--r-- 1 root root 58549 Jul 26 10:22 70-snap.core.rules
-rw-r--r-- 1 root root 208 Jul 26 14:28 99-Hauppauge.rules


Mythtv is a member of group video

video:x:44:mythtv


steve is not a member of video, though. Maybe that's why it wouldn't run
except as sudo?
Re: HDPVR intermittent failure [ In reply to ]
>
> steve is not a member of video, though. Maybe that's why it wouldn't run
> except as sudo?
>
> Correct - you'll want to add steve to that group

1 2 3  View All