[mythtvnz] Mythtv setup problems: Unrecognised DVB-T

[Stephen Worthington]

On Sat, 10 Aug 2013 12:34:06 +1200, you wrote:

>Mythtv was running reasonably well (some signal strength problems but I
>can handle those I think).
>
>But then it stopped recognising my DVB-T sticks.
>
>The mythtv-setup log says:
>
>Aug 10 12:25:32 rahel mythtv-setup[19700]: E CoreContext
>cardutil.cpp:414 (ProbeDVBType) FE_GET_INFO ioctl failed
>(/dev/dvb/adapter0/frontend0)#012#011#011#011eno: No such device (19)
>
>But dmesg says (as I unplug and plug in my stick)
>
>[ 5670.968422] usb 2-1.2: USB disconnect, device number 9
>[ 5670.976923] dvb-usb: Hauppauge Nova-T Stick successfully
>deinitialized and disconnected.
>[ 5673.725137] usb 2-1.2: new high-speed USB device number 10 using ehci_hcd
>[ 5673.818515] usb 2-1.2: New USB device found, idVendor=2040,
>idProduct=7070
>[ 5673.818526] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
>SerialNumber=3
>[ 5673.818532] usb 2-1.2: Product: Nova-T Stick
>[ 5673.818537] usb 2-1.2: Manufacturer: Hauppauge
>[ 5673.818541] usb 2-1.2: SerialNumber: 4034149033
>[ 5673.819579] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state,
>will try to load a firmware
>[ 5673.824099] dvb-usb: downloading firmware from file
>'dvb-usb-dib0700-1.20.fw'
>[ 5674.026187] dib0700: firmware started successfully.
>[ 5674.528370] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
>[ 5674.528501] dvb-usb: will pass the complete MPEG2 transport stream to
>the software demuxer.
>[ 5674.528713] DVB: registering new adapter (Hauppauge Nova-T Stick)
>[ 5674.762500] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
>[ 5674.991242] DiB0070: successfully identified
>[ 5674.991266] Registered IR keymap rc-dib0700-rc5
>[ 5674.991608] input: IR-receiver inside an USB DVB receiver as
>/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/rc/rc5/input11
>[ 5674.991802] rc5: IR-receiver inside an USB DVB receiver as
>/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/rc/rc5
>[ 5674.992067] dvb-usb: schedule remote query interval to 50 msecs.
>[ 5674.992081] dvb-usb: Hauppauge Nova-T Stick successfully initialized
>and connected.
>
>
>Looks to me like the stick is ready and recognised.
>
>I am running Ubuntu 12.04.2 LTS and Version:
>2:0.25.2+fixes.20120802.46cab93-0ubuntu1 of mythtv.
>
>I think the problems started after I did a aptitude dist-upgrade, but I
>cannot be sure.
>
>Can somebody please recommend the next step in diagnosing the problem?
>
>cheers
>W

That certainly looks like what I would expect to see from an
unplug/plug sequence.  It might be an idea to check against old log
files from before the problem (if you still have any) to see if there
are any messages that are different.

The first thing I would try is a complete reboot.  Shut down, turn the
power off at the wall and leave the PC off for long enough for the
motherboard and power supply to completely discharge their capacitors
- a minute or so should do.  If you can see the LED on the motherboard
that is on when the backup supply is on, it should go out and then
leave it for another 10 seconds.  Light from that LED is often visible
through cracks in the case or behind the fans.

After it reboots, do you see the /dev/dvb entry for the Nova-T device?
What devices does mythtv-setup see?  If you have multiple different
devices, they can move around on each boot and be matched against the
wrong setup entries in mythtv-setup, unless you have tied them down to
a specific adapter number.  I do this using a file options-dvb.conf in
/etc/modprobe.d/.  On my box I have three DIB0700 tuners (2 x Pinnacle
Nano Sticks and 1 x AverTV Volar).  They all use the same DIB0700
driver as your Nova-T Stick, and this line makes them always be
assigned as /dev/dvb/adapter0, /dev/dvb/adapter1 and
/dev/dvb/adapter2:

options dvb_usb_dib0700 adapter_nr=0,1,2

I am not worried which of them is assigned to a specific adapter
number as they all perform pretty much the same, but if I wanted to
tie them down completely, I think it would be possible using udev.

Then I assign my two DVB-S2 tuners to the next two adapter numbers:

#Set adapter number for TurboSight TBS5922 QBOX S2 DVB-S2 USB tuner.
options dvb-usb-tbsqbox22 adapter_nr=3

#Set adapter number for TeVii S470 DVB-S2 PCIe x1 card.
options cx23885 adapter_nr=4

And then I have another two virtual adapters for decrypting the Sky
channels from the DVB-S2 adaptors:

#Set number of loopback adapters for use with sasc-ng card decryption
software, and set the adapter numbers to use.
options dvbloopback num_adapters=2 adapter_nr=5,6

If that is not the problem, try booting using the older kernel from
before the dist-upgrade and see if that helps.  I have a problem at
the moment that causes my box to crash if I boot any 3.2 kernel later
than 3.2.0-43-generic.  I have not bothered to diagnose the problem
yet, but the entire box locks up around the time mythfrontend should
be starting and often there are not even any log entries to tell me
what happened.  So kernel updates can cause some problems and you
always need to have some known-good older kernels to run when
mysterious things happen.