[linux-dvb] Re: Howto setup a multicast network connection?

[Holger Kiehl <Holger.Kiehl@dwd.de>]

On Sun, 15 Jun 2003, Holger Waechtler wrote:

> Holger Kiehl wrote:
> > 
> > I now remember that I did try this driver earlier and later switched
> > to linuxtv-dvb-1.0.0-pre3, since trying to use dvbtune did not work. I
> > do remember dvbtune did talk once with the card but then too it
> > would always return the error 'No such device' when trying to open
> > /dev/dvb/adapter0/frontend0. Looking back in /var/log/messages I see
> > that the frontend did load once but after a reboot never again:
> 
> After a soft or a hard reboot? I remember that the stv0299 sometimes 
> completely hangs when the i2c timing registers accidentally get 
> misconfigured by the probing code. Then you have to switch off your 
> computer comletely and remove the power cable for some minutes...
> 
> Please report if this behaviour is true -- if so we'll have to think 
> about the tuner probing code again.
> 
If I poweroff the machine and start it again I no longer get this error.
With a soft reboot I always get 'No such device' error. Someone else
also reported the same behaviour.

However I still do not manage to receive any multicast data with it.
With the linuxtv-dvb-1.0.0-pre3 I just see a process kdvb running
constantly eating 90% CPU time in top and do not receive any data.
With the driver from the Metzler brothers I had a bit more luck,
here the kdvb runs 'normally' and the software to receive the multicast
data does start but does not manage to connect.  In /var/log/messages
I get a lot of the following messages:

   Jun 16 15:12:02 dwdsat2 kernel: In interrupt, cannot set section filter
   Jun 16 15:12:02 dwdsat2 last message repeated 2 times
   Jun 16 15:14:02 dwdsat2 kernel: dvb0_0: set_mc_list, 1 entries
   Jun 16 15:14:02 dwdsat2 kernel: dvb0_0: no feed to stop
   Jun 16 15:14:02 dwdsat2 kernel: In interrupt, cannot set section filter
   Jun 16 15:14:02 dwdsat2 kernel: In interrupt, cannot set section filter
   Jun 16 15:14:02 dwdsat2 kernel: dvb0_0: set_mc_list, 2 entries
   Jun 16 15:14:02 dwdsat2 kernel: dvb0_0: no feed to stop
   Jun 16 15:14:02 dwdsat2 kernel: In interrupt, cannot set section filter
   Jun 16 15:14:02 dwdsat2 last message repeated 2 times
   Jun 16 15:16:02 dwdsat2 kernel: dvb0_0: set_mc_list, 1 entries
   Jun 16 15:16:02 dwdsat2 kernel: dvb0_0: no feed to stop
   Jun 16 15:16:02 dwdsat2 kernel: In interrupt, cannot set section filter
   Jun 16 15:16:02 dwdsat2 kernel: In interrupt, cannot set section filter
   Jun 16 15:16:02 dwdsat2 kernel: dvb0_0: set_mc_list, 2 entries
   Jun 16 15:16:02 dwdsat2 kernel: dvb0_0: no feed to stop

Anyone know what these messages mean?

In the meantime I have also tried the driver from the KNC1, which is
is a branch from the linuxtv driver and they call it DVB-ANDI. This does
not have the problem with soft reboots and I do manage to receive some
multicast packages, but I loose a lot. This time there are lots of
the following messages in /var/log/messages:

   Jun 16 12:44:31 dwdsat2 kernel: vpeirq 00017800
   Jun 16 12:44:31 dwdsat2 kernel: vpeirq 00000000
   Jun 16 12:44:32 dwdsat2 last message repeated 24 times
   Jun 16 12:44:32 dwdsat2 kernel: vpeirq 00017800
   Jun 16 12:44:32 dwdsat2 kernel: vpeirq 00000000
   Jun 16 12:44:34 dwdsat2 last message repeated 57 times
   Jun 16 12:44:34 dwdsat2 kernel: vpeirq 00017800
   Jun 16 12:44:34 dwdsat2 kernel: vpeirq 00000000
   Jun 16 12:44:36 dwdsat2 last message repeated 37 times

What do these messages mean?

Another question that I have, is it possible to turn off CRC checksum?

Regards,
Holger (Kiehl)



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.