<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 10/19/2014 09:11 AM, Ken Truesdale
wrote:<br>
</div>
<blockquote
cite="mid:CABEEE45-A117-4674-892C-E67AD5928502@gmail.com"
type="cite">
<div>
<div>On Oct 19, 2014, at 1:51 AM, Martin Compton wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/18/2014 03:19 PM, Ken
Truesdale wrote:<br>
</div>
<blockquote
cite="mid:001b01cfeb10$dec832e0$9c5898a0$@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14
(filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
.MsoPapDefault
        {mso-style-type:export-only;
        margin-bottom:6.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">I’m new to the HD-PVR and have
recently installed it on my working backend. It is
mostly working now – I can tune live TV using it and
recordings fire off a channel change. I’ve got a
problem with my channel change script when starting a
recording (which doesn’t happen with live TV) but I
should be able to figure that out on my own. But I
also see that the HD-PVR sometimes doesn’t stop
recording. The show it tried to record (but recorded
a different program instead due to the aforementioned
script issue) lasted a half hour and MythTV seems to
have correctly stopped recording at the half hour mark
even though the HD-PVR didn’t get the notification to
stop recording. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To try and debug it, I thought
about looking into a script to reload the hdpvr
module. Seemed simple enough and there are script
examples out there. But when I try typing the
following in the command line: <o:p></o:p></p>
<p class="MsoNormal"> sudo modprobe -r -v hdpvr<o:p></o:p></p>
<p class="MsoNormal">the command just hangs there
indefinitely showing:<o:p></o:p></p>
<p class="MsoNormal"> rmmod hdpvr<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> I can kill the sudo process that
kicked off the modprobe but I can’t kill the modprobe
process. The only way I have found to clear the
problem is a reboot and even then, during shutdown,
the process won’t die and hangs the computer on the
waiting for processes to end step requiring me to push
and hold the power button. Nasty. Clearly something
is very wrong somewhere. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is what I see in dmesg before
trying the modprobe –r:<o:p></o:p></p>
<p class="MsoNormal"> [ 15.456135] hdpvr 1-3:1.0:
firmware version 0x1e dated Mar 7 2012 08:25:15<o:p></o:p></p>
<p class="MsoNormal"> [ 15.966780] hdpvr 1-3:1.0:
device now attached to video0<o:p></o:p></p>
<p class="MsoNormal"> [ 15.966841] usbcore:
registered new interface driver hdpvr<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And this is what I see from dmesg
after the modprobe –r starts (and then hangs):<o:p></o:p></p>
<p class="MsoNormal"> [ 15.456135] hdpvr 1-3:1.0:
firmware version 0x1e dated Mar 7 2012 08:25:15<o:p></o:p></p>
<p class="MsoNormal"> [ 15.966780] hdpvr 1-3:1.0:
device now attached to video0<o:p></o:p></p>
<p class="MsoNormal"> [ 15.966841] usbcore:
registered new interface driver hdpvr<o:p></o:p></p>
<p class="MsoNormal"> [ 846.134280] usbcore:
deregistering interface driver hdpvr<o:p></o:p></p>
<p class="MsoNormal"> [ 846.134308] hdpvr 1-3:1.0:
device video0 disconnected<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If I don’t plug in the USB
connection to the HD-PVR when I boot up, the hdpvr
module doesn’t get loaded, of course. So I can
modprobe hdpvr and it loads fine. Then I can modprobe
–r no problem. The inability to remove the hdpvr
module could be related to the way the device keeps
recording sometimes. So I’m hopeful that fixing one
will fix the other. But I’m out of ideas about what
to check or what could be the source of the problem.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am running Mythbuntu so my setup
for the HD-PVR was pretty easy. Mostly just plugged
it in and set it up in the Backend setup. A few extra
steps to enable the IR flashing. And I did start with
updating the firmware to the latest using a Windows
computer. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have checked my BIOS settings for
USB settings. I don’t have much in there for options
(6 year-old ASUS BYO) and what is there seems to
things set appropriately, at least as far I can tell.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anybody have suggestions on where
to look to chase down a problem like this (or these,
as the case may be)? Thanks!! </p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000"><br>
</div>
</blockquote>
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000"><br>
</div>
</blockquote>
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">Occasionally one of my 2
HD-PVRs look like they are still recording when they aren't,
but the recording itself is valid.<br>
In those cases, cycling the on/off button with a 10 second
delay corrects the problem.<br>
If you are using the HD-PVR IR blaster, a reset does require
a reload of a lirc daemon if needed.<br>
<br>
I am using MythTV 0.27.3 on Ubuntu 12, and HD-PVR firmware
0x1e, the most recent and preferred firmware as it corrects
some issues. I would definitely not mess with your
firmware.<br>
<br>
Check your computer's USB port: should be rev2.</div>
</blockquote>
<br>
</div>
<div><br>
</div>
<div>Martin, when you say USB port should be rev2, you mean the
USB port should be a USB 2.0 connector, right? I don't have USB
3.0 on this Mobo (P5N7A-VM) so that shouldn't be an issue here.
And I have confirmed that I have the USB 2.0 enabled in the
BIOS and with "HiSpeed (480Mbps)". The BIOS also has a choice
for "Legacy USB Support" which I have tried disabling but that's
had no impact on the HD-PVR situation. </div>
<div><br>
</div>
<div>Also, Martin, you may be seeing something similar to me when
you describe that the HD-PVR looks like it is still recording.
In other words, the HD-PVR is still streaming the data through
USB but Myth has just stopped storing the stream. My concern is
that this behavior would cause a recording failure on a future
recording and that I wouldn't be aware of the problem to do the
power cycling. Martin, can you try doing the "<span
class="Apple-style-span" style="font-family: Calibri,
sans-serif; font-size: 15px; ">sudo modprobe -r -v hdpvr" and
see if you can unload it successfully? </span></div>
<div><br>
</div>
<div>From Greg, it seems that an older firmware is working for him
(Greg, what Myth version and what distro and kernel version?).
But for Martin, the newest firmware (which is the one I have -
see above dmesg output) is working for him with Ubuntu 12. I am
using Ubuntu 14 (with the same version of Myth, 0.27.3, but I
don't think the Myth version has much to do with this issue).
Is there anybody reading this using Ubuntu 14.04 (kernel
3.13.0-35) and HD-PVR firmware 0x1e? And if so, how are things
working for you? Or perhaps, more generically, how is the
HD-PVR working for people with Ubuntu 14? </div>
<div><br>
</div>
<div><br>
</div>
<div>Ken.</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
<a class="moz-txt-link-freetext" href="http://wiki.mythtv.org/Mailing_List_etiquette">http://wiki.mythtv.org/Mailing_List_etiquette</a>
MythTV Forums: <a class="moz-txt-link-freetext" href="https://forum.mythtv.org">https://forum.mythtv.org</a>
</pre>
</blockquote>
I am using pre 0.28 and Ubuntu 14.04 with kernel version
3.13.0-37-generic.. I have been using a HD-PVR since they first
came on the scene,and never had any issues except for one driver
version caused the video to wash out.. <br>
</body>
</html>