From: Manu Abraham <abraham.manu@gmail.com>
To: darav@gmx.de
Cc: linux-media@vger.kernel.org
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
Date: Wed, 28 Jan 2009 19:17:52 +0400 [thread overview]
Message-ID: <49807720.2020808@gmail.com> (raw)
In-Reply-To: <158C8110-E256-44A4-9418-E45A94855F62@gmx.de>
darav@gmx.de wrote:
> Hi again,
>
> has anybody an idea what's going wrong here?
> I'm still having this problem.
> Is there anything I can do to help here?
>
> Thanks in advance,
> darav
>
> P.S.: now posting on the new mailinglist. Sorry for double-post.
>
> Jan 28 12:03:09 vdr ttusb2: i2c transfer failed.
> Jan 28 12:03:11 vdr dvb-usb: bulk message failed: -110 (9/0)
> Jan 28 12:03:11 vdr ttusb2: there might have been an error during
> control message transfer. (rlen = 3, was 0)
> Jan 28 12:03:11 vdr ttusb2: i2c transfer failed.
> Jan 28 12:03:13 vdr dvb-usb: bulk message failed: -110 (9/0)
> Jan 28 12:03:13 vdr ttusb2: there might have been an error during
> control message transfer. (rlen = 3, was 0)
> Jan 28 12:03:13 vdr ttusb2: i2c transfer failed.
Looks like the demodulator did not respond at all, maybe it went
bad. Does your device work in a windows environment ?
Regards,
Manu
next prev parent reply other threads:[~2009-01-28 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 13:02 [linux-dvb] S2API (pctv452e) artefacts in video stream Jens Krehbiel-Gräther
2009-01-05 13:07 ` Artem Makhutov
2009-01-05 13:20 ` gimli
2009-01-05 18:53 ` dbox2alpha
2009-01-12 12:16 ` Jens Krehbiel-Gräther
2009-01-12 18:10 ` darav
2009-01-28 11:18 ` darav
2009-01-28 11:26 ` darav
2009-01-28 13:44 ` darav
2009-01-28 15:17 ` Manu Abraham [this message]
[not found] ` <A2511C63-B74D-4E71-807C-BD8FCACCAFFF@gmx.de>
[not found] ` <498226ED.6000409@gmail.com>
[not found] ` <7E87D995-F966-46C9-8023-1743B18BD4C1@gmx.de>
2009-01-30 13:51 ` Rietzschel Carsten
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=49807720.2020808@gmail.com \
--to=abraham.manu@gmail.com \
--cc=darav@gmx.de \
--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