All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Maciej Nowak <tmn505@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Sean Young" <sean@mess.org>, "Gon Solo" <gonsolo@gmail.com>,
	"Antti Palosaari" <crope@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: Logilink DVB-T2 stick VG0022A
Date: Sat, 12 Jun 2021 10:35:40 +0200	[thread overview]
Message-ID: <6934ee17-9dd7-fdc2-9629-cfff286a8031@gmail.com> (raw)
In-Reply-To: <20210611144917.26rvhietmpbuuo5p@pengutronix.de>

W dniu 11.06.2021 o 16:49, Uwe Kleine-König pisze:
> Hello,

Hi Uwe.

> 
> I have a Logilink VG0022A stick and when I plug it in I get:
> 
> [  426.019171] usb 1-1.3: new high-speed USB device number 5 using xhci-hcd
> [  426.171443] usb 1-1.3: New USB device found, idVendor=1d19, idProduct=0100, bcdDevice= 1.00
> [  426.172184] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [  426.172822] usb 1-1.3: Product: TS Aggregator
> [  426.173205] usb 1-1.3: Manufacturer: ITE Tech., Inc.
> [  426.173641] usb 1-1.3: SerialNumber: AF0102020700001
> [  426.180314] dvb_usb_af9035 1-1.3:1.0: prechip_version=83 chip_version=01 chip_type=9306
> [  426.181324] usb 1-1.3: dvb_usb_v2: found a 'Logilink VG0022A' in cold state
> [  426.182034] usb 1-1.3: firmware: direct-loading firmware dvb-usb-it9303-01.fw
> [  426.182666] usb 1-1.3: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9303-01.fw'
> [  426.221915] dvb_usb_af9035 1-1.3:1.0: firmware version=1.4.0.0
> [  426.222456] usb 1-1.3: dvb_usb_v2: found a 'Logilink VG0022A' in warm state
> [  426.224991] usb 1-1.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
> [  426.225998] dvbdev: DVB: registering new adapter (Logilink VG0022A)
> [  426.226551] usb 1-1.3: media controller created
> [  426.229845] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
> [  426.454279] i2c i2c-9: Added multiplexed i2c bus 10
> [  426.454726] si2168 9-0067: Silicon Labs Si2168-B40 successfully identified
> [  426.455377] si2168 9-0067: firmware version: B 4.0.2
> [  426.458522] usb 1-1.3: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
> [  426.460236] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
> [  426.469300] si2157 10-0063: Silicon Labs Si2147/2148/2157/2158 successfully attached
> [  426.489642] usb 1-1.3: dvb_usb_v2: 'Logilink VG0022A' successfully initialized and connected
> 
> which looks fine. But when I try to use it (using mumudvb2) I get:
> 
> [  479.915150] si2168 9-0067: firmware: direct-loading firmware dvb-demod-si2168-b40-01.fw
> [  479.915871] si2168 9-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
> [  480.436016] si2168 9-0067: firmware version: B 4.0.11
> [  480.444089] si2157 10-0063: device is buggy, skipping firmware download
> [  480.496756] si2157 10-0063: firmware version: �.�.255

That is to be expected, the device provides its own (patched?) firmware. This output is very
similar to what I have and it works fine. Tested reception on both DVB-T standards with
kaffeine, mumudvb2 tip and t2scan. You'll see the second part of dmesg message each time
You'll switch the channel or start tuning.

> 
> and it fails to tune.
> 
> Do you have a hint?

What differentiates between Your configuration and mine is I tested the stick in USB 2.0
port. Also what I'm missing from Your log is loading of dvb-demod-si2168-02.fw, I assume
it's present, since the driver doesn't complain.
I don't know if it's enough of a hint, since I'm not 100% sure if my TerraTec TC2 Stick is
exactly the same as VG0022A, but hope it helps

> 
> Best regards
> Uwe
> 

Regards, Tomek.

-- 
TMN

  reply	other threads:[~2021-06-12  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 14:49 Logilink DVB-T2 stick VG0022A Uwe Kleine-König
2021-06-12  8:35 ` Tomasz Maciej Nowak [this message]
2021-06-12  8:41 ` Uwe Kleine-König
2021-06-12 21:20   ` Frantisek Rysanek

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=6934ee17-9dd7-fdc2-9629-cfff286a8031@gmail.com \
    --to=tmn505@gmail.com \
    --cc=crope@iki.fi \
    --cc=gonsolo@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sean@mess.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.