Hey David,
Thanks for your reply.
I am glad I could provide a chuckle ?!?.
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?
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...
Hey, you don't learn unless you ask..:)
Jason
------------------------------
Message: 19
Date: Wed, 23 Nov 2005 23:14:17 -0500
From: "David Ellis" < [EMAIL PROTECTED]>
Subject: RE: [mythtv-users] FC4 and HD-3000 DVB vs.QAM Issue in latest
kernel
To: "'Discussion about mythtv'" < mythtv-users@mythtv.org>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
<chuckle>
For each capture card there is a tuner chip that actually tunes to the
correct channel, and an encoder that actually encodes the content received
into MPEG or V4l raw stream (this is a beginners interpretation but more or
less correct)
In this case you have a Oren Encoder (or more likely Oren Compatible
Encoder), and a Thompson Tuner that is combined into an HD 3000 card.
David
_____
From: [EMAIL PROTECTED]
[mailto: [EMAIL PROTECTED]] On Behalf Of Jason Sharpe
Sent: Wednesday, November 23, 2005 10:02 PM
To: mythtv-users@mythtv.org
Subject: [mythtv-users] FC4 and HD-3000 DVB vs.QAM Issue in latest kernel
Hello All,
As soon as I start to trick myself into believing that I am actually
starting to get the hang of this (Been tinkering with Linux for about 3
months or so, Myth about a month) something comes along and makes me think I
couldn't pour water out of a boot if there were instructions written on the
bottom of it.
Anyway, here is my hardware (however I think it is a software issue):
AMD64 3200+ (Dual Core)
2 Gig Ram
MSI K8N Neo4 Mobo
Nvidia 6600 256Meg
HD-3000 (for OTA HD)
1 Terabyte of HD Space
I had this hardware up and running with Myth for the past week or two just
tinkering to learn/play and it was working pretty well. Because I did so
much "playing" with it, along with getting a DCT-6208 yesterday I wanted to
add (I know you don't have to wipe clean to add a source), plus I just
wanted more experience with Linux and Myth. I reinstalled FD4 this afternoon
from scratch.
I followed Jarod's guide the first time and it went pretty smooth. The
HD-3000 was recognized and worked pretty much as close to "out of the box"
as you can get.
Now I am having an issue with FC4 and the latest kernel. I use the DVD ISO
to install FC4 x86 choosing the packages that Jarod lists. This installs
kernel 2.6.11-1.1369smp. When I finish the initial boot setup (enabling NTP
and setting up a user, etc) I log into X and look at the dmesg. (ie. NOTHING
has been done to configure/customize anything)
Here is what it says:
**************************************************************
<snip>
cx2388x dvb driver version 0.0.4 loaded
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
ACPI: PCI Interrupt 0000:01: 07.2[A] -> Link [APC2] -> GSI 17 (level, low) ->
IRQ 233
cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 233, latency: 32, mmio:
0xfc000000
cx88[0]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[0]).
DVB: registering frontend 0 (pcHDTV HD3000 HDTV)...
cx2388x v4l2 driver version 0.0.4 loaded
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, low) ->
IRQ 233
cx88[0]/0: found at 0000:01: 07.0, rev: 5, irq: 233, latency: 32, mmio:
0xfb000000
tuner 2-0061: chip found @ 0xc2 (cx88[0])
tuner 2-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC))
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
<snip>
****************************************************************
So it sees the pcHDTV HD3000 and creates /dev/dvb like it should.
then I run "yum upgrade kernel kernel-smp kernel-smp-dev"
It downloads and installs kernel 2.6.14-1.1637. I reboot into that new SMP
kernel and again look at dmesg after logging into X.
It reads:
****************************************************************
<snip>
cx2388x dvb driver version 0.0.5 loaded
CORE cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
ACPI: PCI Interrupt 0000:01:07.2[A] -> Link [APC2] -> GSI 17 (level, low) ->
IRQ 233
cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 233, latency: 32, mmio:
0xfc000000
cx88[0]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[0]).
DVB: registering frontend 0 (Oren OR51132 VSB/QAM Frontend)...
cx2388x v4l2 driver version 0.0.5 loaded
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, low) ->
IRQ 233
cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 233, latency: 32, mmio:
0xfb000000
tuner 2-0061: chip found @ 0xc2 (cx88[0])
tuner 2-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC))
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
<snip>
************************************************************
My question is, why does it detect the board as a "Oren OR51132 VSB/QAM
Frontend"? It does still create /dev/dvb. The new kernel appears to be using
the 0.0.5 DVB drivers so I am going to guess that is what is causing the
difference in naming. Is there any issues with that? I plan to use it for
OTA HD only.
Also, what in the heck is a "Thomson DDT 7610 (ATSC/NTSC)"? It lists that on
both kernels. I am going to guess that it is something on the HD-3000 card
since there are no other cards/tuners in the box.
I just wanted to understand what was going on instead of continuing to
configure Myth and find out I need to do something now to save myself some
headaches down the road.
BTW, Happy Thanksgiving Everyone!
Thanks in advance,
Jason
_______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
