From: "P. van Gaans" <w3ird_n3rd@gmx.net>
To: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Technisat Airstar USB round two
Date: Mon, 16 Jun 2008 20:07:37 +0200 [thread overview]
Message-ID: <4856ABE9.30609@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0806160949440.3677@pub3.ifh.de>
On 06/16/2008 09:54 AM, Patrick Boettcher wrote:
> Hi,
>
> Ignore the conexant error. The driver cannot know which device you
> exactly have other than trying to guess. And guessing works, by trying
> every possible frontend-driver. The CX24123 says wrong revision. OK,
> that is correct, there is no CX24123.
>
> The following line says the truth:
>
> [ 3083.612219] b2c2-flexcop: found 'Zarlink MT352 DVB-T' .
>
>> From the init point of view everything looks correct here.
>
> The error messages when unplugging are strange, but should not prevent
> you from using it.
>
> However. Maybe it is better to sell the device at Ebay and buy another
> (better) one. Yours is only USB1.1, you cannot receive a complete
> transport stream with it.
>
> Did you try the device in Windows using the same antenna?
>
> Patrick.
>
>
> On Mon, 16 Jun 2008, P. van Gaans wrote:
>
>> On 06/13/2008 08:57 PM, P. van Gaans wrote:
>>> Approximately a year ago I tried to make this USB DVB-T box work. But it
>>> wouldn't. With a little more knowledge today I tried again with v4l-dvb
>>> from hg, but it still won't go. I get this when I plug it in:
>>>
>>> [ 3083.152125] usb 1-2: new full speed USB device using ohci_hcd and
>>> address 4
>>> [ 3083.253055] usb 1-2: configuration #1 chosen from 1 choice
>>> [ 3083.258204] flexcop_usb: running at FULL speed.
>>> [ 3083.501399] DVB: registering new adapter (FlexCop Digital TV device)
>>> [ 3083.502758] b2c2-flexcop: MAC address = 00:d0:d7:09:e7:70
>>> [ 3083.516842] CX24123: wrong demod revision: 0
>>> [ 3083.612219] b2c2-flexcop: found 'Zarlink MT352 DVB-T' .
>>> [ 3083.612226] DVB: registering frontend 1 (Zarlink MT352 DVB-T)...
>>> [ 3083.612261] b2c2-flexcop: initialization of 'Air2PC/AirStar 2 DVB-T'
>>> at the 'USB' bus controlled by a 'FlexCopIII' complete
>>> [ 3083.621757] flexcop_usb: Technisat/B2C2 FlexCop II/IIb/III Digital TV
>>> USB Driver successfully initialized and connected.
>>>
>>> Note the "CX24123: wrong demod revision: 0". What's with that? It looks
>>> like something is wrong.
>>>
>>> I get this when I unplug it:
>>>
>>> [ 3081.464885] flexcop_usb: iso frame descriptor 0 has an error: -62
>>> [ 3081.464887]
>>> [ 3081.464892] flexcop_usb: iso frame descriptor 1 has an error: -62
>>> [ 3081.464893]
>>> [ 3081.464895] flexcop_usb: iso frame descriptor 2 has an error: -62
>>> [ 3081.464896]
>>> [ 3081.464897] flexcop_usb: iso frame descriptor 3 has an error: -62
>>> [ 3081.464898]
>>> [ 3081.468884] flexcop_usb: iso frame descriptor 0 has an error: -62
>>> [ 3081.468886]
>>> [ 3081.468891] flexcop_usb: iso frame descriptor 1 has an error: -62
>>> [ 3081.468892]
>>> [ 3081.468894] flexcop_usb: iso frame descriptor 2 has an error: -62
>>> [ 3081.468895]
>>> [ 3081.468896] flexcop_usb: iso frame descriptor 3 has an error: -62
>>> [ 3081.468897]
>>> [ 3081.472876] flexcop_usb: iso frame descriptor 0 has an error: -62
>>> [ 3081.472877]
>>> [ 3081.472879] flexcop_usb: iso frame descriptor 1 has an error: -62
>>> [ 3081.472880]
>>> [ 3081.472881] flexcop_usb: iso frame descriptor 2 has an error: -62
>>> [ 3081.472882]
>>> [ 3081.472883] flexcop_usb: iso frame descriptor 3 has an error: -62
>>> [ 3081.472885]
>>> [ 3081.475209] usb 1-2: USB disconnect, address 3
>>> [ 3081.479869] flexcop_usb: iso frame descriptor 0 has an error: -62
>>> [ 3081.479871]
>>> [ 3081.479873] flexcop_usb: iso frame descriptor 1 has an error: -62
>>> [ 3081.479874]
>>> [ 3081.479875] flexcop_usb: iso frame descriptor 2 has an error: -62
>>> [ 3081.479876]
>>> [ 3081.479877] flexcop_usb: iso frame descriptor 3 has an error: -18
>>> [ 3081.479878]
>>> [ 3081.479880] flexcop_usb: iso frame descriptor 0 has an error: -18
>>> [ 3081.479881]
>>> [ 3081.479883] flexcop_usb: iso frame descriptor 1 has an error: -18
>>> [ 3081.479884]
>>> [ 3081.479885] flexcop_usb: iso frame descriptor 2 has an error: -18
>>> [ 3081.479886]
>>> [ 3081.479887] flexcop_usb: iso frame descriptor 3 has an error: -18
>>> [ 3081.479888]
>>> [ 3081.479890] flexcop_usb: iso frame descriptor 0 has an error: -18
>>> [ 3081.479891]
>>> [ 3081.479892] flexcop_usb: iso frame descriptor 1 has an error: -18
>>> [ 3081.479893]
>>> [ 3081.479895] flexcop_usb: iso frame descriptor 2 has an error: -18
>>> [ 3081.479896]
>>> [ 3081.479897] flexcop_usb: iso frame descriptor 3 has an error: -18
>>> [ 3081.479898]
>>> [ 3081.479900] flexcop_usb: iso frame descriptor 0 has an error: -18
>>> [ 3081.479901]
>>> [ 3081.479902] flexcop_usb: iso frame descriptor 1 has an error: -18
>>> [ 3081.479903]
>>> [ 3081.479904] flexcop_usb: iso frame descriptor 2 has an error: -18
>>> [ 3081.479905]
>>> [ 3081.479906] flexcop_usb: iso frame descriptor 3 has an error: -18
>>> [ 3081.479907]
>>> [ 3081.480307] flexcop_usb: Technisat/B2C2 FlexCop II/IIb/III Digital TV
>>> USB Driver successfully deinitialized and disconnected.
>>>
>>> I think it doesn't like being unplugged. The problem is still the same:
>>> I see the device in /dev/dvb and in Kaffeine, when I try to watch a
>>> channel I see the ACT LED on the device blink a bit, but the LOCK LED
>>> will never light up and I never get to watch anything. Using Ubuntu
>>> 8.04.
>>>
>>> P.
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@linuxtv.org
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>
>> Doesn't anyone have any idea, or even care about this device? I can't
>> find any Conexant chip in there, unless it would be inside the tuner.
>>
>> If nobody cares about it (I see only one secondhand Airstar USB on eBay
>> and it looks different from mine), I'll sell mine and forget about it.
>> Otherwise.. Please post.
>>
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>
>
Hi,
I already have some other USB DVB-T devices that are supported, so if
anyone is going to fix the support for this one it would be for other
people who own it. But if nobody does, there's no point.
Yes, it does work on Windows. Antenna is fine. It's a revision 2.1
according to the PCB btw.
The chips in mine are the Zarlink MT352 and B2C2 Flexcop III. That's normal.
The tuner is a Samsung TDTC9251DH01C(B). The sticker on the tuner also
says "040722 JAT.". I see this tuner is listed in flexcop-fe-tuner.c
for the MT352 so that seems to be normal as well. Only thing I can think
of is Technisat changing register addresses or something, and I think
it's beyond my capability to fix that.
I made a log with usbsnoop on Windows, tuning and locking. It's 17,1MB
compressed and 89,1MB unzipped and can be found here:
http://megaupload.com/?d=VEBBWOO3
If anyone can do anything with it (even if it's only telling me
Technisat messed up the entire device and it's never going to be
supported), it would be interesting to hear.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-06-16 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 18:57 [linux-dvb] Technisat Airstar USB round two P. van Gaans
2008-06-16 1:53 ` P. van Gaans
2008-06-16 7:54 ` Patrick Boettcher
2008-06-16 18:07 ` P. van Gaans [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=4856ABE9.30609@gmx.net \
--to=w3ird_n3rd@gmx.net \
--cc=linux-dvb@linuxtv.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