[mythtv] DVB-T with trunk and Hauppauge HVR-4000, no channels found

[Terjesen Jens Peder]

________________________________________
Fra: mythtv-dev-bounces at mythtv.org [mythtv-dev-bounces at mythtv.org] på vegne av Marc Randolph [mrand at pobox.com]
Sendt: 30. september 2009 17:51
Til: Development of mythtv
Emne: Re: [mythtv] DVB-T with trunk and Hauppauge HVR-4000, no channels  found

On Wed, Sep 30, 2009 at 9:10 AM, Terjesen Jens Peder
<Jens.Peder.Terjesen at devoteam.com> wrote:
> Hi.
>
> I have been a little uncertain if this belongs on the dev or user list.

I believe the devs prefer the first pass of these type of "does it
work" type questions to happen on -user first.

> For quite some time I have been trying unsuccessfully to get DVB-T to work in MythTV with my three HVR-4000.
> [...]
> With MythTV trunk from yesterday (22121) I am not able to get any channels when scanning. I have tried both tuned scanning
> and importing a channels.conf created by scan, which works. The channel scanner in MythTV indicates reasonably good signal
> strenght and quality but no lock.
>
> I ran mythtvsetup -v channelscan which did not give much information about the problem.
>
> Is there anything I can do to provide more information?
>
> The first part of the log is trunkated output from a DVB-S/S2 scan that works, the last bit is from the DVB-T scan I did afterwards:

A Ubuntu-based user is also having trouble with DVB-T channel scanning
(https://bugs.launchpad.net/mythbuntu/+bug/439163).  If we get logs, I
was planning on opening a ticket.  I don't know if more options
(channelscan,siparser,channel,record,extra) would shed more light on
it, but I think that something approaching what the devs would ask for
and is worth attaching that output to a new ticket.

Have fun,

   Marc
_______________________________________________

Hi.

The extra verbose printout gives the same information as for the Ubuntu-based user you are refering to.

But I noticed that when I was changing the timeout in mythtv-setup it took about 15-17 seconds from I selected it until the information for it was displayed. At this time the following was output in the terminal:
=====
2009-09-30 23:13:30.633 Klarte ikke leite etter inndata.
                        eno: Operation not supported (95)
2009-09-30 23:13:30.644 Klarte ikke leite etter inndata.
                        eno: Operation not supported (95)
2009-09-30 23:13:30.652 Klarte ikke leite etter inndata.
                        eno: Operation not supported (95)
2009-09-30 23:13:30.652 ProbeAudioInputs(/dev/dvb/adapter0/frontend1,HDPVR)
2009-09-30 23:13:30.653 ProbeV4LAudioInputs(/dev/dvb/adapter0/frontend1)
2009-09-30 23:13:39.448 DiSEqCDevTree, Warning: No device tree for cardid 3
2009-09-30 23:13:39.474 Klarte ikke leite etter inndata.
                        eno: Operation not supported (95)
2009-09-30 23:13:39.485 Klarte ikke leite etter inndata.
                        eno: Operation not supported (95)
2009-09-30 23:13:39.493 Klarte ikke leite etter inndata.
                        eno: Operation not supported (95)
2009-09-30 23:13:39.493 ProbeAudioInputs(/dev/dvb/adapter0/frontend1,HDPVR)
2009-09-30 23:13:39.493 ProbeV4LAudioInputs(/dev/dvb/adapter0/frontend1)
2009-09-30 23:13:50.828 DiSEqCDevTree, Warning: No device tree for cardid 3
=====

I get the same behaviuor and printout when selecting the DVB-S2 part of this card.
Not sure it's related but thought I should mention it.

Jens