* Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
2009-01-12 18:10 ` darav
@ 2009-01-28 11:18 ` darav
2009-01-28 11:26 ` darav
2009-01-28 13:44 ` darav
2 siblings, 0 replies; 11+ messages in thread
From: darav @ 2009-01-28 11:18 UTC (permalink / raw)
To: linux-dvb
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
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.
Jan 28 12:03:15 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:15 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:15 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:17 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:17 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:17 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:19 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:19 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:19 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:21 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:21 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:21 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:23 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:23 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:23 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:25 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:25 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:25 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:27 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:27 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:27 vdr ttusb2: i2c transfer failed.
Am 12.01.2009 um 19:10 schrieb darav@gmx.de:
> Hi!
>
> The same problem exists with my PCTV 400e.
> It seems to be problem with the USB part.
> When I enable USB-Debug- in the kernel, I get this:
>
> ttusb2: i2c transfer failed.
> dvb-usb: bulk message failed: -22 (9/70)
> ttusb2: there might have been an error during control message
> transfer. (rlen = 3, was 0)
> ...
> ttusb2: i2c transfer failed.
> dvb-usb: bulk message failed: -22 (9/70)
> ttusb2: there might have been an error during control message
> transfer. (rlen = 3, was 0)
>
> It's the same with 2.6.28 in-kernel-drivers and with the Igor
> Liplianin's tree.
>
> (A also had this problem some years ago on a PPC-Mac-Mini. The
> workaround was to disable HIGHMEM. But it doesn't work now.
> I'm now on x86 32bit).
>
> I also want to help. But how?
>
> Best Regards,
> darav
>
> Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:
>
>> Hi!
>>
>> So this problem concerns more people and should be a general bug??
>> My device is working well in windows, so it could not be the dish,
>> the
>> cable or the device itself.
>>
>> Can I do anything for debugging this problem? Let me know!
>>
>> Jens
>>
>>
>> dbox2alpha@netscape.net schrieb:
>>>
>>> i can confirm the very same problem symptoms with a technotrend
>>> dvb-s2
>>> 3600 usb device.
>>>
>>> -----Original Message-----
>>> From: gimli <gimli@dark-green.com>
>>> To: Artem Makhutov <artem@makhutov.org>
>>> Cc: linux-dvb@linuxtv.org
>>> Sent: Mon, 5 Jan 2009 2:20 pm
>>> Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
>>>
>>> Artem Makhutov schrieb:
>>>
>>>> Hi,
>>>
>>>>
>>>
>>>> On Mon, Jan 05, 2009 at 02:02:16PM +0100, Jens Krehbiel-Gräther
>>>> wrote:
>>>
>>>>> Hi!
>>>
>>>>>
>>>
>>>>> I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is
>>>
>>>>> dvb-usb-pctv452e.
>>>
>>>>>
>>>
>>>>> I use the repository from Igor Liplianin (actual hg release).
>>>>> The module
>>>
>>>>> compiles and loads fine. The scanning with scan-s2 and zapping
>>>>> with
>>>
>>>>> szap-s2 also wirk fine.
>>>
>>>>> But when I record TV from the USB-device with "cat
>>>
>>>>> /dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the
>>>>> actual
>>>
>>>>> tv-station (zapped with "szap-s2 -r SAT.1" for example).
>>>
>>>>> This recorded video has artefacts, even missed frames.
>>>
>>>>>
>>>
>>>>> Anyone else having this problem? I remember that on multiproto
>>>>> there was
>>>
>>>>> a similar prob
>>> lem with the pctv452e until Dominik Kuhlen patched
>>>
>>>>> somthing since then the video was OK. Is it possible that the same
>>>
>>>>> "error" is in the S2API-driver?
>>>
>>>>
>>>
>>>> I have similar problems with my SkyStar HD (stb0899), but I
>>>
>>>> am still using the multiproto drivers.
>>>
>>>>
>>>
>>>> Regards, Artem
>>>
>>>>
>>>
>>>> _______________________________________________
>>>
>>>> linux-dvb mailing list
>>>
>>>> linux-dvb@linuxtv.org
>>>
>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>>
>>>
>>> Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD
>>>
>>> with the S2API drivers from the Liplianin tree.
>>>
>>>
>>>
>>> mfg
>>>
>>>
>>>
>>> Edgar (gimli) Hucek
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> linux-dvb mailing list
>>>
>>> linux-dvb@linuxtv.org
>>>
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>>
>>> ------------------------------------------------------------------------
>>> Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
>>> <http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020
>>> >.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@linuxtv.org
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>
>>
>> _______________________________________________
>> linux-dvb users mailing list
>> For V4L/DVB development, please use instead linux-media@vger.kernel.org
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
2009-01-12 18:10 ` darav
2009-01-28 11:18 ` darav
@ 2009-01-28 11:26 ` darav
2009-01-28 13:44 ` darav
2 siblings, 0 replies; 11+ messages in thread
From: darav @ 2009-01-28 11:26 UTC (permalink / raw)
To: linux-media
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.
Jan 28 12:03:15 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:15 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:15 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:17 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:17 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:17 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:19 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:19 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:19 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:21 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:21 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:21 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:23 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:23 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:23 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:25 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:25 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:25 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:27 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:27 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:27 vdr ttusb2: i2c transfer failed.
Am 12.01.2009 um 19:10 schrieb darav@gmx.de:
> Hi!
>
> The same problem exists with my PCTV 400e.
> It seems to be problem with the USB part.
> When I enable USB-Debug- in the kernel, I get this:
>
> ttusb2: i2c transfer failed.
> dvb-usb: bulk message failed: -22 (9/70)
> ttusb2: there might have been an error during control message
> transfer. (rlen = 3, was 0)
> ...
> ttusb2: i2c transfer failed.
> dvb-usb: bulk message failed: -22 (9/70)
> ttusb2: there might have been an error during control message
> transfer. (rlen = 3, was 0)
>
> It's the same with 2.6.28 in-kernel-drivers and with the Igor
> Liplianin's tree.
>
> (A also had this problem some years ago on a PPC-Mac-Mini. The
> workaround was to disable HIGHMEM. But it doesn't work now.
> I'm now on x86 32bit).
>
> I also want to help. But how?
>
> Best Regards,
> darav
>
> Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:
>
>> Hi!
>>
>> So this problem concerns more people and should be a general bug??
>> My device is working well in windows, so it could not be the dish,
>> the
>> cable or the device itself.
>>
>> Can I do anything for debugging this problem? Let me know!
>>
>> Jens
>>
>>
>> dbox2alpha@netscape.net schrieb:
>>>
>>> i can confirm the very same problem symptoms with a technotrend
>>> dvb-s2
>>> 3600 usb device.
>>>
>>> -----Original Message-----
>>> From: gimli <gimli@dark-green.com>
>>> To: Artem Makhutov <artem@makhutov.org>
>>> Cc: linux-dvb@linuxtv.org
>>> Sent: Mon, 5 Jan 2009 2:20 pm
>>> Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
>>>
>>> Artem Makhutov schrieb:
>>>
>>>> Hi,
>>>
>>>>
>>>
>>>> On Mon, Jan 05, 2009 at 02:02:16PM +0100, Jens Krehbiel-Gräther
>>>> wrote:
>>>
>>>>> Hi!
>>>
>>>>>
>>>
>>>>> I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is
>>>
>>>>> dvb-usb-pctv452e.
>>>
>>>>>
>>>
>>>>> I use the repository from Igor Liplianin (actual hg release).
>>>>> The module
>>>
>>>>> compiles and loads fine. The scanning with scan-s2 and zapping
>>>>> with
>>>
>>>>> szap-s2 also wirk fine.
>>>
>>>>> But when I record TV from the USB-device with "cat
>>>
>>>>> /dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the
>>>>> actual
>>>
>>>>> tv-station (zapped with "szap-s2 -r SAT.1" for example).
>>>
>>>>> This recorded video has artefacts, even missed frames.
>>>
>>>>>
>>>
>>>>> Anyone else having this problem? I remember that on multiproto
>>>>> there was
>>>
>>>>> a similar prob
>>> lem with the pctv452e until Dominik Kuhlen patched
>>>
>>>>> somthing since then the video was OK. Is it possible that the same
>>>
>>>>> "error" is in the S2API-driver?
>>>
>>>>
>>>
>>>> I have similar problems with my SkyStar HD (stb0899), but I
>>>
>>>> am still using the multiproto drivers.
>>>
>>>>
>>>
>>>> Regards, Artem
>>>
>>>>
>>>
>>>> _______________________________________________
>>>
>>>> linux-dvb mailing list
>>>
>>>> linux-dvb@linuxtv.org
>>>
>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>>
>>>
>>> Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD
>>>
>>> with the S2API drivers from the Liplianin tree.
>>>
>>>
>>>
>>> mfg
>>>
>>>
>>>
>>> Edgar (gimli) Hucek
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> linux-dvb mailing list
>>>
>>> linux-dvb@linuxtv.org
>>>
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>>
>>> ------------------------------------------------------------------------
>>> Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
>>> <http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020
>>> >.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@linuxtv.org
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>
>>
>> _______________________________________________
>> linux-dvb users mailing list
>> For V4L/DVB development, please use instead linux-media@vger.kernel.org
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
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
2 siblings, 1 reply; 11+ messages in thread
From: darav @ 2009-01-28 13:44 UTC (permalink / raw)
To: linux-media
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.
Jan 28 12:03:15 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:15 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:15 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:17 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:17 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:17 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:19 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:19 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:19 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:21 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:21 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:21 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:23 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:23 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:23 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:25 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:25 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 4, was 0)
Jan 28 12:03:25 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:27 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:27 vdr ttusb2: there might have been an error during
control message transfer. (rlen = 3, was 0)
Jan 28 12:03:27 vdr ttusb2: i2c transfer failed.
Am 12.01.2009 um 19:10 schrieb darav@gmx.de:
> Hi!
>
> The same problem exists with my PCTV 400e.
> It seems to be problem with the USB part.
> When I enable USB-Debug- in the kernel, I get this:
>
> ttusb2: i2c transfer failed.
> dvb-usb: bulk message failed: -22 (9/70)
> ttusb2: there might have been an error during control message
> transfer. (rlen = 3, was 0)
> ...
> ttusb2: i2c transfer failed.
> dvb-usb: bulk message failed: -22 (9/70)
> ttusb2: there might have been an error during control message
> transfer. (rlen = 3, was 0)
>
> It's the same with 2.6.28 in-kernel-drivers and with the Igor
> Liplianin's tree.
>
> (A also had this problem some years ago on a PPC-Mac-Mini. The
> workaround was to disable HIGHMEM. But it doesn't work now.
> I'm now on x86 32bit).
>
> I also want to help. But how?
>
> Best Regards,
> darav
>
> Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:
>
>> Hi!
>>
>> So this problem concerns more people and should be a general bug??
>> My device is working well in windows, so it could not be the dish,
>> the
>> cable or the device itself.
>>
>> Can I do anything for debugging this problem? Let me know!
>>
>> Jens
>>
>>
>> dbox2alpha@netscape.net schrieb:
>>>
>>> i can confirm the very same problem symptoms with a technotrend
>>> dvb-s2
>>> 3600 usb device.
>>>
>>> -----Original Message-----
>>> From: gimli <gimli@dark-green.com>
>>> To: Artem Makhutov <artem@makhutov.org>
>>> Cc: linux-dvb@linuxtv.org
>>> Sent: Mon, 5 Jan 2009 2:20 pm
>>> Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
>>>
>>> Artem Makhutov schrieb:
>>>
>>>> Hi,
>>>
>>>>
>>>
>>>> On Mon, Jan 05, 2009 at 02:02:16PM +0100, Jens Krehbiel-Gräther
>>>> wrote:
>>>
>>>>> Hi!
>>>
>>>>>
>>>
>>>>> I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is
>>>
>>>>> dvb-usb-pctv452e.
>>>
>>>>>
>>>
>>>>> I use the repository from Igor Liplianin (actual hg release).
>>>>> The module
>>>
>>>>> compiles and loads fine. The scanning with scan-s2 and zapping
>>>>> with
>>>
>>>>> szap-s2 also wirk fine.
>>>
>>>>> But when I record TV from the USB-device with "cat
>>>
>>>>> /dev/dvb/adapter0/dvr0 > (filename)" I got the TV-Stream of the
>>>>> actual
>>>
>>>>> tv-station (zapped with "szap-s2 -r SAT.1" for example).
>>>
>>>>> This recorded video has artefacts, even missed frames.
>>>
>>>>>
>>>
>>>>> Anyone else having this problem? I remember that on multiproto
>>>>> there was
>>>
>>>>> a similar prob
>>> lem with the pctv452e until Dominik Kuhlen patched
>>>
>>>>> somthing since then the video was OK. Is it possible that the same
>>>
>>>>> "error" is in the S2API-driver?
>>>
>>>>
>>>
>>>> I have similar problems with my SkyStar HD (stb0899), but I
>>>
>>>> am still using the multiproto drivers.
>>>
>>>>
>>>
>>>> Regards, Artem
>>>
>>>>
>>>
>>>> _______________________________________________
>>>
>>>> linux-dvb mailing list
>>>
>>>> linux-dvb@linuxtv.org
>>>
>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>>
>>>
>>> Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD
>>>
>>> with the S2API drivers from the Liplianin tree.
>>>
>>>
>>>
>>> mfg
>>>
>>>
>>>
>>> Edgar (gimli) Hucek
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> linux-dvb mailing list
>>>
>>> linux-dvb@linuxtv.org
>>>
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>>
>>> ------------------------------------------------------------------------
>>> Get a *free MP3* every day with the Spinner.com Toolbar. Get it Now
>>> <http://toolbar.aol.com/spinner/download.html?ncid=emlweusdown00000020
>>> >.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@linuxtv.org
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>
>>
>> _______________________________________________
>> linux-dvb users mailing list
>> For V4L/DVB development, please use instead linux-media@vger.kernel.org
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-dvb] S2API (pctv452e) artefacts in video stream
2009-01-28 13:44 ` darav
@ 2009-01-28 15:17 ` Manu Abraham
[not found] ` <A2511C63-B74D-4E71-807C-BD8FCACCAFFF@gmx.de>
0 siblings, 1 reply; 11+ messages in thread
From: Manu Abraham @ 2009-01-28 15:17 UTC (permalink / raw)
To: darav; +Cc: linux-media
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
^ permalink raw reply [flat|nested] 11+ messages in thread