public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Magnus Nilsson <magnus@upcore.net>
To: Claes Lindblom <claesl@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Azurewave AD-CP400 (Twinhan VP-2040 DVB-C)
Date: Fri, 11 Sep 2009 10:31:51 +0200	[thread overview]
Message-ID: <4AAA0AF7.8060201@upcore.net> (raw)
In-Reply-To: <4AA9E41B.4010102@gmail.com>

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

      reply	other threads:[~2009-09-11  8:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 13:53 Azurewave AD-CP400 (Twinhan VP-2040 DVB-C) Magnus Nilsson
2009-08-26 16:21 ` Magnus Nilsson
2009-09-06 20:52   ` MartinG
2009-09-07  9:40     ` Magnus Nilsson
2009-09-11  5:46       ` Claes Lindblom
2009-09-11  8:31         ` Magnus Nilsson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AAA0AF7.8060201@upcore.net \
    --to=magnus@upcore.net \
    --cc=claesl@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox