<html><body><div style="color:#000; background-color:#fff; font-family:tahoma, new york, times, serif;font-size:10pt"><div><span style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: normal;"><span style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;">On 11/07/13 01:43, Jason Hiller wrote:</span><br></div><div style="font-family: tahoma, 'new york', times, serif; font-size: 10pt;"><div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"><div class="y_msg_container">><br>> On 08/07/13 10:05, John Pilkington wrote:<br>> > On 08/07/13 02:12, Jason Hiller wrote:<br>> >><br>> >> On 7/7/2013 3:46 PM, Jason Hiller wrote:<br>> >>
><br>> >> > Hi Jason,<br>> >> ><br>> >> > On 7/6/2013 8:07 PM, Jason Hiller wrote:<br>> >> > > I am having trouble with mythtv recognizing my Hauppauge HVR-1600<br>> >> card. Myth setup fails to probe my card but everything I have found in<br>> >> my system logs indicates the OS sees the card and it is functioning. I<br>> >> opened a ticket for this but thought I would try to help it along by<br>> >> doing some troubleshooting.<br>> ><br>> > I wasn't able to identify your ticket, but the symptoms sounded<br>> > familiar. In fact I didn't have this problem before kernel 3.4.2-1;<br>> > 3.3.7-1 and earlier were fine. I'm now running 3.9.8-100.fc17.x86_64<br>> > and a quick check yesterday looked hopeful but
not entirely convincing.<br>> > I'll try again when the schedule is clear.<br>> ><br>> > <a href="http://code.mythtv.org/trac/ticket/11058" target="_blank">http://code.mythtv.org/trac/ticket/11058</a><br>> ><br>> > You might try this workaround:<br>> ><br>> > <a href="http://code.mythtv.org/trac/ticket/10830#comment:13" target="_blank">http://code.mythtv.org/trac/ticket/10830#comment:13</a><br>><br>> I've just done a partial mythtvsetup again, under 3.9.8-100.fc17.x86_64,<br>> and the tuner card recognition, for both PCI and USB DVB-T devices,<br>> worked without the femon workaround. But it took several tens of<br>> seconds to do so, with nothing visible happening - and, as recently<br>> reported elsewhere, the tuner delay setting seems to be stuck at zero.<br>><br><snip><br>><br>> MythTV Version : 0.26.0-8.fc17
(v0.26.0-149-g5f45c0b) from rpmfusion<br>><br>> ><br>> > John P<br>><br>> John, Thanks for the information. Do you have any tips/instructions for<br>> upgrading the kernel? After some searches I was going to follow the<br>> instructions from this post:<br>> http://askubuntu.com/questions/119080/how-to-update-kernel-to-the-latest-mainline-version-without-any-distro-upgrade.<br>> Do they look reasonable?<br>><br><br>I can't comment on that. Did you try the femon workaround? It's only <br>needed while mythtvsetup is trying to identify the card. And it may <br>only be relevant if the IOCTL error is reported. Otherwise your problem <br>may be something else.<br><br>My test was aimed at seeing if the fix had been applied, and would work, <br>in the new kernel. I don't know how it might be applied in your distro.<br><br>John<br><br>John, I have not seen the IOCTL
error but I am trying to get the analog side of my tuner card working. Not sure if that makes a difference. Even though I am not using it, I tried running the femon command and configuring the DVB side of the tuner and I still get an "Unknown error" in myth setup. That is the same thing I see without the femon command running.</div><div class="y_msg_container"><br></div><div class="y_msg_container">Anyway, I haven't found any other solutions for my problem so that is why I was considering giving the kernel upgrade a shot. I'd rather not but I haven't found any other options. If the install totally breaks after the upgrade I guess I'll have to wipe the entire OS and start over.</div><div class="y_msg_container"><br></div> </div> </div> </div></body></html>