<div>
<div>Hey David,</div>
<div> </div>
<div>Thanks for your reply.</div>
<div> </div>
<div>I am glad I could provide a chuckle ?!?.</div>
<div> </div>
<div>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?
</div>
<div> </div>
<div>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...</div>
<div> </div>
<div>Hey, you don't learn unless you ask..:)</div>
<div> </div>
<div>Jason</div>
<div> </div><br><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">------------------------------<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</blockquote></div>