Claes Lindblom wrote: >> More majordomo info at http://vger.kernel.org/majordomo-info.html > Hi, I have the same problem with Slave RACK Fail on my Azurewave > AP-SP400 (VP-1041). > Do you really mean that to don't get theese problems when turning off > the log from open-sasc-ng or was the problem on open-sasc-ng? > I have turned off the log completely for a long time since it was > problems in open-sasc-ng but I still have problems with Slave RACK Fail. > I'm using the same drivers with Ubuntu server x86_64 2.6.28-13-generic > kernel. > > Have you done anything else to work properly, like patching open-sasc-ng > or the driver? > From my experience it really starts to fail when using MythTV, otherwise > I can tune channels for several days straight without any problems. > But when doing a complete channels scan it can make the driver fail so I > would not blame mythtv to much but it's feels like something messes > it up. > Maybe it's getting better in Mythtv 0.22... > > I'm almost about to sell my tv-card if it does not start to work > properly. :( > > Best regards > /Claes > If you read the entire thread it was MartinG that had the problem with "Slave RACK Fail". My machine just completely locked up before I removed the logging in open-sasc-ng. I'm currently using a vanilla 2.6.30.5 kernel, with open-sasc-ng r77 and s2-liplianin-16e3dc6f2758, on a Debian system with MythTV 0.21 from the vanilla sources. The only thing I've had to do to get open-sasc-ng to compile was comment out the lines containing "owner", specifically lines 175,187,196,221 in dvbloopback/module/dvblb_proc.c I can remember seeing Slave RACK Fail errors when using the older mantis driver from Manu (not the mantis-v4l one). That was however only when booting up, since it paused for a few seconds while displaying 4 of those errors. I don't see it now with the newer drivers though. Keep in mind that we don't even have the same card, since I have the AD-CP400 (DVB-C version). Thanks, Magnus -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
