Re: Invalid sat cable number errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 17.04.2014 16:09, Ville Skyttä wrote:
On Thu, Apr 17, 2014 at 4:23 PM, Klaus Schmidinger
<Klaus.Schmidinger@xxxxxxx> wrote:
On 17.04.2014 15:13, Ville Skyttä wrote:

On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger
<Klaus.Schmidinger@xxxxxxx> wrote:

 From your log:

Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter0/frontend0
Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice
Apr 17 16:03:21 vdr[16019]: [16019] new device number 1
Apr 17 16:03:21 vdr[16019]: [16019] frontend 0/0 provides DVB-C with
QAM16,QAM32,QAM64,QAM128,QAM256 ("ST STV0297 DVB-C")
Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter1/frontend0
Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice
Apr 17 16:03:21 vdr[16019]: [16019] new device number 2
Apr 17 16:03:21 vdr[16019]: [16019] frontend 1/0 provides DVB-C with
QAM16,QAM32,QAM64,QAM128,QAM256 ("ST STV0297 DVB-C")
Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter2/frontend0
Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice
Apr 17 16:03:21 vdr[16019]: [16019] new device number 3
Apr 17 16:03:21 vdr[16019]: [16019] frontend 2/0 provides DVB-C with
QAM16,QAM32,QAM64,QAM128,QAM256 ("VLSI VES1820 DVB-C")
Apr 17 16:03:21 vdr[16019]: [16019] found 3 DVB devices
Apr 17 16:03:21 vdr[16019]: [16019] initializing plugin: softhddevice
(0.6.1rc1): A software and GPU emulated HD device
Apr 17 16:03:21 vdr[16019]: [16019] new device number 9

What looks a little strange here is the gap between device number 3 and 9.
Maybe this causes some misbehavior in handling device bonding?

Dunno. I haven't told softhddevice to use any particular device number
nor do I know if it's possible to do that. I've just configured it to
set itself as the primary device.

But are "sat cable" and "device bonding" valid concepts on DVB-C in
the first place? The "sat" smells like DVB-S to me...

These are purely sat related.
I don't believe that the errors come from any tuning code, since actual
device bonding is only done for DVB-S devices (see cDvbDevice::Bond()).

Does this error occur if you make any changes to the setup?
Like changing the OSD language or anything else that would cause the
setup.conf file to be written.

Klaus

_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr





[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux