Mailing List Archive: MythTV: Dev

DVB scanning problems

Index | Next | Previous | View Threaded

pc-mythtv05a at crowcastle

Jul 20, 2005, 7:39 PM

Post #1 of 12 (3216 views)
Permalink

DVB scanning problems

I'm running 2.6.12.2 with the built-in DVB drivers for my HD-2000 card,
and it all works from the command line. When I do a scan, it finds the
transports, but no channels. The console from where I launched
mythtv-setup displays:

2005-07-20 21:52:06.456 DVB#0 DVB signal 2f1a | snr ad | ber ffffffda | unc ffffffda
2005-07-20 21:52:06.456 DVB#0 Status: LOCK.
2005-07-20 21:52:06.456 DVB#0 ERROR - Getting Frontend tuning parameters failed.
(95) Operation not supported
2005-07-20 21:52:07.993 DVB#0 DVB signal 2f1a | snr 8e | ber ffffffda | unc ffffffda
2005-07-20 21:52:07.994 DVB#0 Status: LOCK.
2005-07-20 21:52:07.995 DVB#0 ERROR - Getting Frontend tuning parameters failed.
(95) Operation not supported

Looking in the code, I see dvbchannel.cpp:

bool DVBChannel::GetTuningParams(DVBTuning& tuning) const
{
if (fd_frontend < 0)
{
ERROR("Card not open!");
return false;
}

if (ioctl(fd_frontend, FE_GET_FRONTEND, &tuning.params) < 0)
{
ERRNO("Getting Frontend tuning parameters failed.");
return false;
}
return true;
}

Looking in the kernel, FE_GET_FRONTEND isn't defined for or51132 (or
or51211, for that matter).

Is there a different version of the DVB drivers that I should be using,
or is a workaround in Myth practical?

danielk at cuymedia

Jul 21, 2005, 4:56 AM

Post #2 of 12 (3094 views)
Permalink

Re: DVB scanning problems [In reply to]

On Wed, 2005-07-20 at 22:39 -0400, Preston Crow wrote:
> I'm running 2.6.12.2 with the built-in DVB drivers for my HD-2000 card,
> and it all works from the command line. When I do a scan, it finds the
> transports, but no channels. The console from where I launched
> mythtv-setup displays:
>
> Looking in the code, I see dvbchannel.cpp:
> bool DVBChannel::GetTuningParams(DVBTuning& tuning) const
> Is there a different version of the DVB drivers that I should be using,
> or is a workaround in Myth practical?
Nope, this isn't your problem, the scanner has a fallback if
GetTuningParams() fails.

Are you scanning OTA or Cable?

What revision did you use, does a newer one work?

-- Daniel

pc-mythtv05a at crowcastle

Jul 21, 2005, 6:45 AM

Post #3 of 12 (3050 views)
Permalink

Re: DVB scanning problems [In reply to]

On Thu, 2005-07-21 at 07:56 -0400, Daniel Kristjansson wrote:
> On Wed, 2005-07-20 at 22:39 -0400, Preston Crow wrote:
> > I'm running 2.6.12.2 with the built-in DVB drivers for my HD-2000 card,
> > and it all works from the command line. When I do a scan, it finds the
> > transports, but no channels. The console from where I launched
> > mythtv-setup displays:
> >
> > Looking in the code, I see dvbchannel.cpp:
> > bool DVBChannel::GetTuningParams(DVBTuning& tuning) const
> > Is there a different version of the DVB drivers that I should be using,
> > or is a workaround in Myth practical?
> Nope, this isn't your problem, the scanner has a fallback if
> GetTuningParams() fails.
>
> Are you scanning OTA or Cable?
>
> What revision did you use, does a newer one work?

I'm scanning OTA.
Kernel 2.6.12.2 with compiled-in drivers
MythTV subversion sources from yesterday
Everything else updated to latest Gentoo packages

Any suggested version changes?

This is an HD-2000, not an HD-3000.

pgm0203 at comcast

Jul 21, 2005, 7:43 AM

Post #4 of 12 (3084 views)
Permalink

Re: DVB scanning problems [In reply to]

If it is cable, it is possible that your transports are missing crucial
PSIP data. Try shutting down MythTV and using one of the available
standalone TS scanners on one of the transports. I usually dump a
portion of the stream using "test_dvr" from the dvb-apps suite, and then
feed the output to TSReaderLite.

When I use one of my HD-3000 cards in QAM-256 mode to tune my local
cable provider (Comcast of Woburn, MA), I see only PATs and PMTs; no
other tables at all. I manually analyzed all the transports, found the
FTA programs, and added them to my database. Unfortunately, the programs
move around from time to time.

About six weeks ago I spent a little time trying to modify the Myth SI
scanner so that if it had found no SI data by the time the scan timed
out, but it had found programs without CA flags, it would make up names
for them and add them anyway. Then I could simply watch the channels,
identify them, and manually update the database with the correct channel
number and callsign. Unfortunately, I was unable to get my modifications
to work in the limited time I had available, so for now I'm just using
the FireWire port on the cable box.

- Paul

>Daniel Kristjansson <danielk [at] cuymedia> wrote:
>
>On Wed, 2005-07-20 at 22:39 -0400, Preston Crow wrote:
>
>
>>I'm running 2.6.12.2 with the built-in DVB drivers for my HD-2000 card,
>>and it all works from the command line. When I do a scan, it finds the
>>transports, but no channels. The console from where I launched
>>mythtv-setup displays:
>>
>>Looking in the code, I see dvbchannel.cpp:
>>bool DVBChannel::GetTuningParams(DVBTuning& tuning) const
>>Is there a different version of the DVB drivers that I should be using,
>>or is a workaround in Myth practical?
>>
>>
>Nope, this isn't your problem, the scanner has a fallback if
>GetTuningParams() fails.
>
>Are you scanning OTA or Cable?
>
>What revision did you use, does a newer one work?
>
>-- Daniel
>
>
>
>------------------------------
>
>_______________________________________________
>mythtv-dev mailing list
>mythtv-dev [at] mythtv
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>End of mythtv-dev Digest, Vol 30, Issue 30
>******************************************
>
>
>

pc-mythtv05a at crowcastle

Jul 21, 2005, 8:18 AM

Post #5 of 12 (3075 views)
Permalink

Re: DVB scanning problems [In reply to]

danielk at cuymedia

Jul 21, 2005, 1:16 PM

Post #6 of 12 (3079 views)
Permalink

Re: DVB scanning problems [In reply to]

On Thu, 2005-07-21 at 09:45 -0400, Preston Crow wrote:
> I'm scanning OTA.
> Kernel 2.6.12.2 with compiled-in drivers
> MythTV subversion sources from yesterday
> Everything else updated to latest Gentoo packages
>
> Any suggested version changes?
Yep try revisions 6888, 6883, and 6871.
Let me know the highest revision number that works.
BTW:
svn co http://cvs.mythtv.org/svn/trunk/mythtv --revision 6888 mythtv

> This is an HD-2000, not an HD-3000.
Make sure you are using the first input during scanning.

-- Daniel

pc-mythtv05a at crowcastle

Jul 21, 2005, 7:17 PM

Post #7 of 12 (3072 views)
Permalink

Re: DVB scanning problems [In reply to]

On Thu, 2005-07-21 at 16:16, Daniel Kristjansson wrote:
> On Thu, 2005-07-21 at 09:45 -0400, Preston Crow wrote:
> > I'm scanning OTA.
> > Kernel 2.6.12.2 with compiled-in drivers
> > MythTV subversion sources from yesterday
> > Everything else updated to latest Gentoo packages
> >
> > Any suggested version changes?
> Yep try revisions 6888, 6883, and 6871.
> Let me know the highest revision number that works.
> BTW:
> svn co http://cvs.mythtv.org/svn/trunk/mythtv --revision 6888 mythtv
>
> > This is an HD-2000, not an HD-3000.
> Make sure you are using the first input during scanning.

I don't see any option for selecting the input, but since it finds the
signal on the channels, I should have the right one. (There wasn't any
option for the command-line tools, either.)

Same behavior with all those versions, and 6860 for good measure.

The scan finds the transports as expected, but then doesn't find any
channels. If I rescan on the existing transports it tells me:

2005-07-21 22:13:17.190 DVB#0 ERROR - Could not find capture card for transport 77
2005-07-21 22:13:17.190 DVB#0 ERROR - Could not find capture card for transport 78
2005-07-21 22:13:17.191 DVB#0 ERROR - Could not find capture card for transport 79
2005-07-21 22:13:17.191 DVB#0 ERROR - Could not find capture card for transport 80
2005-07-21 22:13:17.192 DVB#0 ERROR - Could not find capture card for transport 81
...

danielk at cuymedia

Jul 21, 2005, 8:25 PM

Post #8 of 12 (3061 views)
Permalink

Re: DVB scanning problems [In reply to]

On Thu, 2005-07-21 at 22:17 -0400, Preston Crow wrote:
> > > This is an HD-2000, not an HD-3000.
> > Make sure you are using the first input during scanning.
> I don't see any option for selecting the input, but since it finds the
> signal on the channels, I should have the right one. (There wasn't any
> option for the command-line tools, either.)
I meant physically plug the cable into the first input, which I believe
is the one closer to the LEDs. As far as I know the DVB drivers for the
HD-2000 only support one input.

> Same behavior with all those versions, and 6860 for good measure.
If it isn't a regression then there isn't anything I can do to help
you right now. There would be little point in debugging a scanner
that will be obsolete so soon.

Wait until the new scanner is in CVS and then file a bug report with
all the info sent to the command line, and everything in the scanner
pane along with the info about your setup, such as the card HD-2000,
the transport OTA, the drivers DVB from kernel x.x.x.

Until then I recommend you use the v4l drivers and either manually
input the channels or use the new scanner in the patch at:
http://www.cuymedia.net/patch/

-- Daniel

pc-mythtv05a at crowcastle

Jul 23, 2005, 10:30 AM

Post #9 of 12 (3049 views)
Permalink

Re: DVB scanning problems [In reply to]

On Thu, 2005-07-21 at 22:17, Preston Crow wrote:
> The scan finds the transports as expected, but then doesn't find any
> channels. If I rescan on the existing transports it tells me:
>
> 2005-07-21 22:13:17.190 DVB#0 ERROR - Could not find capture card for transport 77
> 2005-07-21 22:13:17.190 DVB#0 ERROR - Could not find capture card for transport 78
> 2005-07-21 22:13:17.191 DVB#0 ERROR - Could not find capture card for transport 79
> 2005-07-21 22:13:17.191 DVB#0 ERROR - Could not find capture card for transport 80
> 2005-07-21 22:13:17.192 DVB#0 ERROR - Could not find capture card for transport 81
> ...

I found what's causing that.

In the database, capturecard.videodevice is "/dev/dvb/adapter0/dvr0" but
in the code, it is querying for it by '0' in dvbchannel.cpp.

#ifdef PRESTON
QString thequery =
QString("SELECT cardid FROM capturecard "
"WHERE videodevice = '%1'").arg(dvbdevice(DVB_DEV_DVR, cardnum));
#else
QString thequery =
QString("SELECT cardid FROM capturecard "
"WHERE videodevice = '%1'").arg(cardnum);
#endif

That gets it past my immediate problem. It is still not working
correctly, but I need to dig further.

So the question is, is the query broken, or should my database just have
a number in that field? (And shouldn't the query also check that
cardtype='DVB')

tom at compton

Jul 23, 2005, 10:34 AM

Post #10 of 12 (3063 views)
Permalink

Re: DVB scanning problems [In reply to]

In message <1122139837.6041.7.camel [at] haw>
Preston Crow <pc-mythtv05a [at] crowcastle> wrote:

> In the database, capturecard.videodevice is "/dev/dvb/adapter0/dvr0" but
> in the code, it is querying for it by '0' in dvbchannel.cpp.

[ snipped ]

> So the question is, is the query broken, or should my database just have
> a number in that field? (And shouldn't the query also check that
> cardtype='DVB')

Mine just has numbers:

mysql> select cardid, videodevice from capturecard;
+--------+-------------+
| cardid | videodevice |
+--------+-------------+
| 1 | 0 |
| 2 | 1 |
+--------+-------------+
2 rows in set (0.01 sec)

Tom

--
Tom Hughes (tom [at] compton)
http://www.compton.nu/

danielk at cuymedia

Jul 23, 2005, 10:43 AM

Post #11 of 12 (3043 views)
Permalink

Re: DVB scanning problems [In reply to]

On Sat, 2005-07-23 at 18:34 +0100, Tom Hughes wrote:
> In message <1122139837.6041.7.camel [at] haw>
> Preston Crow <pc-mythtv05a [at] crowcastle> wrote:
>
> > In the database, capturecard.videodevice is "/dev/dvb/adapter0/dvr0" but
> > in the code, it is querying for it by '0' in dvbchannel.cpp.
>
> [ snipped ]
>
> > So the question is, is the query broken, or should my database just have
> > a number in that field? (And shouldn't the query also check that
> > cardtype='DVB')
>
> Mine just has numbers:
>
> mysql> select cardid, videodevice from capturecard;
> +--------+-------------+
> | cardid | videodevice |
> +--------+-------------+
> | 1 | 0 |
> | 2 | 1 |
> +--------+-------------+

This is how it should look for DVB.

Preston, can you set the videodevice to "0" and try again?
With and, if it doesn't work, without the jp1.patch.

Can you also provide some info on the steps you took to configure
the DVB device so we can figure out how the videodevice got set to
"/dev/dvb/adapter0/dvr0"?

-- Daniel

pc-mythtv05a at crowcastle

Jul 23, 2005, 11:07 AM

Post #12 of 12 (3060 views)
Permalink

Re: DVB scanning problems [In reply to]

On Sat, 2005-07-23 at 13:43, Daniel Kristjansson wrote:
> Can you also provide some info on the steps you took to configure
> the DVB device so we can figure out how the videodevice got set to
> "/dev/dvb/adapter0/dvr0"?

The card was originally using the Video4Linux drivers. I see that my
PVR-250 card uses /dev/v4l/video1 as it's videodevice, so it probably is
some misstep that I took in reconfiguring the card.

--PC

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads