From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ey-out-2122.google.com ([74.125.78.27]:7547 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751068AbZIKFqJ (ORCPT ); Fri, 11 Sep 2009 01:46:09 -0400 Received: by ey-out-2122.google.com with SMTP id 4so10430eyf.5 for ; Thu, 10 Sep 2009 22:46:11 -0700 (PDT) Message-ID: <4AA9E41B.4010102@gmail.com> Date: Fri, 11 Sep 2009 07:46:03 +0200 From: Claes Lindblom MIME-Version: 1.0 To: Magnus Nilsson CC: MartinG , linux-media@vger.kernel.org Subject: Re: Azurewave AD-CP400 (Twinhan VP-2040 DVB-C) References: <4A953E52.4020300@upcore.net> <4A956124.5070902@upcore.net> <4AA4D4F1.4060308@upcore.net> In-Reply-To: <4AA4D4F1.4060308@upcore.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Magnus Nilsson wrote: > MartinG wrote: >> On Wed, Aug 26, 2009 at 6:21 PM, Magnus Nilsson >> wrote: >>> Nevermind this for the time being...all is pointing to open-sasc-ng >>> being >>> the culprit here... >> >> Just to add a datapoint - I have the same problem: I can't seem to >> successfully scan for channels. I've taken open-sasc-ng out of the >> equation by simply not loading the loopback device and scan directly >> on the true frontend. >> These are my bits: >> Terratec Cinergy C HD PCI >> kernel 2.6.29.6-217.2.16.fc11.x86_64 >> s2-liplianin from http://mercurial.intuxication.org/hg/s2-liplianin >> Currently: >> changeset: 12465:096aa4559b71 >> tag: tip >> user: Igor M. Liplianin >> date: Sat Sep 05 20:26:33 2009 +0300 >> >> dmesg when "modprobe mantis" >> Sep 6 22:33:52 localhost kernel: Mantis 0000:04:00.0: PCI INT A -> >> GSI 16 (level, low) -> IRQ 16 >> Sep 6 22:33:52 localhost kernel: irq: 16, latency: 64 >> Sep 6 22:33:52 localhost kernel: memory: 0xfdfff000, mmio: >> 0xffffc20023906000 >> Sep 6 22:33:52 localhost kernel: found a VP-2040 PCI DVB-C device on >> (04:00.0), >> Sep 6 22:33:52 localhost kernel: Mantis Rev 1 [153b:1178], irq: >> 16, latency: 64 >> Sep 6 22:33:52 localhost kernel: memory: 0xfdfff000, mmio: >> 0xffffc20023906000 >> Sep 6 22:33:52 localhost kernel: MAC Address=[00:08:ca:1d:bd:a6] >> Sep 6 22:33:52 localhost kernel: mantis_alloc_buffers (0): >> DMA=0xcc0d0000 cpu=0xffff8800cc0d0000 size=65536 >> Sep 6 22:33:52 localhost kernel: mantis_alloc_buffers (0): >> RISC=0xa85ce000 cpu=0xffff8800a85ce000 size=1000 >> Sep 6 22:33:52 localhost kernel: DVB: registering new adapter (Mantis >> dvb adapter) >> Sep 6 22:33:52 localhost kernel: mantis_frontend_init (0): Probing >> for CU1216 (DVB-C) >> Sep 6 22:33:52 localhost kernel: TDA10023: i2c-addr = 0x0c, id = 0x7d >> Sep 6 22:33:52 localhost kernel: mantis_frontend_init (0): found >> Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c >> Sep 6 22:33:52 localhost kernel: mantis_frontend_init (0): Mantis >> DVB-C Philips CU1216 frontend attach success >> Sep 6 22:33:52 localhost kernel: DVB: registering adapter 0 frontend >> 0 (Philips TDA10023 DVB-C)... >> Sep 6 22:33:52 localhost kernel: mantis_ca_init (0): Registering >> EN50221 device >> Sep 6 22:33:52 localhost kernel: mantis_ca_init (0): Registered >> EN50221 device >> Sep 6 22:33:52 localhost kernel: mantis_hif_init (0): Adapter(0) >> Initializing Mantis Host Interface >> Sep 6 22:33:52 localhost kernel: input: Mantis VP-2040 IR Receiver as >> /devices/virtual/input/input11 >> Sep 6 22:33:53 localhost kernel: Mantis VP-2040 IR Receiver: unknown >> key: key=0x00 raw=0x00 down=1 >> Sep 6 22:33:53 localhost kernel: Mantis VP-2040 IR Receiver: unknown >> key: key=0x00 raw=0x00 down=0 >> >> lspci -v >> 04:00.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV >> PCI Bridge Controller [Ver 1.0] (rev 01) >> Subsystem: TERRATEC Electronic GmbH Device 1178 >> Flags: bus master, medium devsel, latency 64, IRQ 16 >> Memory at fdfff000 (32-bit, prefetchable) [size=4K] >> Kernel driver in use: Mantis >> Kernel modules: mantis >> >> I have also tried the mantis module from v4l-dvb without success. The >> card is then recognized as TDA10021 instead of TDA10023, just as you >> describe. >> >> Typically, I have to do "modprobe -r mantis;modprobe mantis" right >> before I try to scan (with w_scan, scandvb og mythtv) in order to get >> any channels at all. But the joy doesn't last for long, and I get >> stuff like >> kernel: mantis_ack_wait (0): Slave RACK Fail ! >> in /var/log/messages. >> >> I guess the problems mentioned in the following post are related: >> Subject: Terratec Cinergy C HD tuning problems >> Date: 2009-08-19 21:10:56 GMT >> >> Hope we can find a solution to this! >> >> best, >> MartinG > > I actually found what my problem was. It seems that open-sasc-ng has a > weird bug, which means you can't tell it to log to a logfile by using > the --log argument. > > If I remove the '--log /var/log/open-sasc-ng.log' argument and instead > lets it log directly to syslog, it works fine. I'm using syslog-ng, so > it's not a problem directing all open-sasc-ng log traffic to a > specific logfile anyway. > > //Magnus > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@vger.kernel.org > 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