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.
good, please let us know when you can find out more what register setting exactly causes this problem.
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.
arrgh, then there is something more broken in the SU1278 support in stv0299.c. Could you please compare register-by-register the settings programmed by the Metzler and the LinuxTV driver? Just add a printk in the writereg/readreg function to get the log.
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?
yes, the Metzler tarball does not has (yet) the changes Ralph announced and explained months ago, see his posting in the dec2000 thread for details.
:)
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:
Can you please analyze the register settings of this driver a bit more in detail if this one is working reliably?
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?
it's an unexpected irq message in old drivers.
Another question that I have, is it possible to turn off CRC checksum?
yes, just don't pass the DMX_CHECK_CRC flag when starting a section filter.
Holger
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
