or51132 module for ATSC vs tvtime/kdetv

[R. G. Newbury]

Date: Fri, 15 Dec 2006 11:36:30 -0500
From: Gene Heskett <gene.heskett at verizon.net>
Subject: or51132 module for ATSC vs tvtime/kdetv
To: For users of Fedora <fedora-list at redhat.com>
Message-ID: <200612151136.30492.gene.heskett at verizon.net>
Content-Type: text/plain; charset=us-ascii

Greetings;

I have built and loaded the or51132 module which supposedly enables the
reception of north american ATSC signals on a pcHDTV-3000 card.

Unfortunately, neither tvtime nor kdetv acknowledge the capability, or its
not properly installed with a simple 'modprobe or51132' statement.  They
both seem to work just fine with analog NTSC however.

Presently I've been loading all those modules in my rc.local file, like
this, since about 2.6.11 when all this was suddenly broken and it took
this to get it working again:
----
modprobe -r cx88-dvb cx8802 cx8800 cx88-alsa cx88xx
modprobe cx88xx tuner=60
modprobe cx8800
modprobe cx8802
modprobe cx88-dvb
----

And I've loaded the or51132 module from the cli since booting, but before
calling either tvtime or kdetv.

Do I need to modify the order of this, or if this isn't the correct
methodology, what is the approved method?
**********************************

I have no idea about tvtime or kdetv, but the usual place for the 
firmware drivers is in /lib/firmware. I have an HD3000 card and the 
dvb-fe-or51132-qam.fw file is in that folder. I understand that the use 
of /lib/hotplug/firmware is now deprecated.

If the firmware is there, it is automagically found and you should not 
have to load it from the command line. Read you dmesg output. It 
presently should report its failure to load the firmware on the bootup 
section. If may later report 'initialized' when you have loaded the 
firmware...

Geoff
Geoff