<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Sorry for the late reply – I was out
kinda late last night.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>As I mentioned earlier – I went thru
the same thing, so I’ll try to answer (which is why I chuckled).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I suspect the DVB maintainers (who have
been doing a lot of updates to this driver as demand increases) started
including more detailed information for the hardware on the card. This was
probably done to help debug some obscure bug that effected a single
individual/group and it helped the maintainer determine if the hardware on the
card was different than what they were running. Some capture card vendors
(Hauppauge in particular) are known to change tuners and encoders on a pretty
regular basis. I have two PVR 250’s each with a different tuner –
although they were bought at the same time.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The good news in all this is that the card
does continue to work in Myth, and works quite well.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>David<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
mythtv-users-bounces@mythtv.org [mailto:mythtv-users-bounces@mythtv.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Jason Sharpe<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, November 24, 2005
12:23 AM<br>
<b><span style='font-weight:bold'>To:</span></b> mythtv-users@mythtv.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [mythtv-users] Re: FC4
and HD-3000 DVB vs.QAM Issue in latest kernel</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hey David,<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Thanks for your reply.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I am glad I could provide a chuckle ?!?.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Anyway, the first time I installed FC4 it always referred to it as a
HD3000 when it loaded the frontend even with the latest kernel. Any reason why
that might have changed? Should I just go ahead and proceed with Myth like
usual? <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I am just trying to understand what would have changed in the kernel
from a month ago that now it is being referred to differently...<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hey, you don't learn unless you ask..:)<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Jason<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>------------------------------<br>
<br>
Message: 19<br>
Date: Wed, 23 Nov 2005 23:14:17 -0500<br>
From: "David Ellis" < <a href="mailto:david@ellisonline.ca">david@ellisonline.ca</a>><br>
Subject: RE: [mythtv-users] FC4 and HD-3000 DVB vs.QAM Issue in latest<br>
kernel<br>
To: "'Discussion about mythtv'" <<a
href="mailto:mythtv-users@mythtv.org"> mythtv-users@mythtv.org</a>><br>
Message-ID: <03ec01c5f0ad$89b92d70$6501a8c0@asuslap><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
<chuckle><br>
<br>
<br>
<br>
For each capture card there is a tuner chip that actually tunes to the <br>
correct channel, and an encoder that actually encodes the content received<br>
into MPEG or V4l raw stream (this is a beginners interpretation but more or<br>
less correct)<br>
<br>
<br>
<br>
In this case you have a Oren Encoder (or more likely Oren Compatible <br>
Encoder), and a Thompson Tuner that is combined into an HD 3000 card.<br>
<br>
<br>
<br>
David<br>
<br>
<br>
<br>
_____<br>
<br>
From: <a href="mailto:mythtv-users-bounces@mythtv.org">mythtv-users-bounces@mythtv.org</a><br>
[mailto: <a href="mailto:mythtv-users-bounces@mythtv.org">mythtv-users-bounces@mythtv.org</a>]
On Behalf Of Jason Sharpe<br>
Sent: Wednesday, November 23, 2005 10:02 PM<br>
To: <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org </a><br>
Subject: [mythtv-users] FC4 and HD-3000 DVB vs.QAM Issue in latest kernel<br>
<br>
<br>
<br>
Hello All,<br>
<br>
As soon as I start to trick myself into believing that I am actually<br>
starting to get the hang of this (Been tinkering with Linux for about 3 <br>
months or so, Myth about a month) something comes along and makes me think I<br>
couldn't pour water out of a boot if there were instructions written on the<br>
bottom of it.<br>
<br>
Anyway, here is my hardware (however I think it is a software issue): <br>
<br>
AMD64 3200+ (Dual Core)<br>
2 Gig Ram<br>
MSI K8N Neo4 Mobo<br>
Nvidia 6600 256Meg<br>
HD-3000 (for OTA HD)<br>
1 Terabyte of HD Space<br>
<br>
I had this hardware up and running with Myth for the past week or two just<br>
tinkering to learn/play and it was working pretty well. Because I
did so<br>
much "playing" with it, along with getting a DCT-6208 yesterday I
wanted to<br>
add (I know you don't have to wipe clean to add a source), plus I just <br>
wanted more experience with Linux and Myth. I reinstalled FD4 this afternoon<br>
from scratch.<br>
<br>
I followed Jarod's guide the first time and it went pretty smooth. The<br>
HD-3000 was recognized and worked pretty much as close to "out of the
box" <br>
as you can get.<br>
<br>
Now I am having an issue with FC4 and the latest kernel. I use the DVD ISO<br>
to install FC4 x86 choosing the packages that Jarod lists. This installs<br>
kernel 2.6.11-1.1369smp. When I finish the initial boot setup (enabling NTP <br>
and setting up a user, etc) I log into X and look at the dmesg. (ie. NOTHING<br>
has been done to configure/customize anything)<br>
<br>
<br>
<br>
Here is what it says:<br>
<br>
<br>
<br>
************************************************************** <br>
<br>
<snip><br>
<br>
<br>
<br>
cx2388x dvb driver version 0.0.4 loaded<br>
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV<br>
[card=22,autodetected]<br>
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17<br>
ACPI: PCI Interrupt 0000:01: 07.2[A] -> Link [APC2] -> GSI 17 (level,
low) -><br>
IRQ 233<br>
cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 233, latency: 32, mmio:<br>
0xfc000000<br>
cx88[0]/2: cx2388x based dvb card<br>
DVB: registering new adapter (cx88[0]). <br>
DVB: registering frontend 0 (pcHDTV HD3000 HDTV)...<br>
cx2388x v4l2 driver version 0.0.4 loaded<br>
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, low)
-><br>
IRQ 233<br>
cx88[0]/0: found at 0000:01: 07.0, rev: 5, irq: 233, latency: 32, mmio:<br>
0xfb000000<br>
tuner 2-0061: chip found @ 0xc2 (cx88[0])<br>
tuner 2-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC))<br>
cx88[0]/0: registered device video0 [v4l2]<br>
cx88[0]/0: registered device vbi0 <br>
cx88[0]/0: registered device radio0<br>
<br>
<br>
<br>
<snip><br>
<br>
****************************************************************<br>
<br>
<br>
<br>
So it sees the pcHDTV HD3000 and creates /dev/dvb like it should.<br>
<br>
<br>
<br>
then I run "yum upgrade kernel kernel-smp kernel-smp-dev"<br>
<br>
<br>
<br>
It downloads and installs kernel 2.6.14-1.1637. I reboot into that
new SMP<br>
kernel and again look at dmesg after logging into X. <br>
<br>
<br>
<br>
It reads:<br>
<br>
<br>
<br>
****************************************************************<br>
<br>
<snip><br>
<br>
<br>
cx2388x dvb driver version 0.0.5 loaded<br>
CORE cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV <br>
[card=22,autodetected]<br>
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe<br>
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17<br>
ACPI: PCI Interrupt 0000:01:07.2[A] -> Link [APC2] -> GSI 17 (level, low)
-><br>
IRQ 233<br>
cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 233, latency: 32, mmio:<br>
0xfc000000<br>
cx88[0]/2: cx2388x based dvb card<br>
DVB: registering new adapter (cx88[0]).<br>
DVB: registering frontend 0 (Oren OR51132 VSB/QAM Frontend)... <br>
cx2388x v4l2 driver version 0.0.5 loaded<br>
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, low)
-><br>
IRQ 233<br>
cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 233, latency: 32, mmio:<br>
0xfb000000<br>
tuner 2-0061: chip found @ 0xc2 (cx88[0])<br>
tuner 2-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC))<br>
cx88[0]/0: registered device video0 [v4l2]<br>
cx88[0]/0: registered device vbi0<br>
cx88[0]/0: registered device radio0 <br>
<br>
<br>
<br>
<snip><br>
<br>
************************************************************<br>
<br>
<br>
<br>
My question is, why does it detect the board as a "Oren OR51132 VSB/QAM<br>
Frontend"? It does still create /dev/dvb. The new kernel appears to be
using <br>
the 0.0.5 DVB drivers so I am going to guess that is what is causing the<br>
difference in naming. Is there any issues with that? I plan to use it for<br>
OTA HD only.<br>
<br>
<br>
<br>
Also, what in the heck is a "Thomson DDT 7610 (ATSC/NTSC)"? It lists
that on <br>
both kernels. I am going to guess that it is something on the HD-3000 card<br>
since there are no other cards/tuners in the box.<br>
<br>
<br>
<br>
I just wanted to understand what was going on instead of continuing to<br>
configure Myth and find out I need to do something now to save myself some<br>
headaches down the road.<br>
<br>
<br>
<br>
BTW, Happy Thanksgiving Everyone!<br>
<br>
<br>
<br>
Thanks in advance,<br>
<br>
<br>
<br>
Jason<o:p></o:p></span></font></p>
</blockquote>
</div>
</div>
</body>
</html>