public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Myatt <steve.myatt.2009@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: No video0, /dev/dvb/adapter0 present
Date: Sat, 21 Jan 2012 12:38:42 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120121T132944-762@post.gmane.org> (raw)
In-Reply-To: 4BEE6B30.30303@ii.net

Cliffe <cliffe <at> ii.net> writes:

> 
> Hello I would really appreciate some help.
> 
[...cropped...]
> [    9.079590] af9013: found a 'Afatech AF9013 DVB-T' in warm state.
> [    9.082319] af9013: firmware version:4.95.0
> [    9.094043] DVB: registering adapter 1 frontend 0 (Afatech AF9013 
> DVB-T)...
> [    9.094211] tda18271 1-00c0: creating new instance
> [    9.096393] af9015: command failed:2
> [    9.098032] tda18271_read_regs: [1-00c0|M] ERROR: i2c_transfer 
> returned: -1
> [    9.098046] Unknown device detected @ 1-00c0, device not supported.
> [    9.100368] af9015: command failed:2
[...cropped...]
> Thanks,
> 
> Cliffe.
> 
> 


Hi Cliffe

Have you checked to see if there's a different report after a completely cold
(power plug out) boot, compared to a warm reboot?

I'm chasing what appears to me to be a similar problem, different card, same
chips (by the look of it) and I found the same report in my syslog:

Unknown device detected @ 1-00c0, device not supported.

I see you haven't had any responses here; did you get any further with this?

Symptoms in my system: got a dual tuner card (PEAK 221544AGPK PCI) which,
following warm boot, doesn't see the second tuner. Suspect firmware not being
loaded due to warm state. I'm documenting this at

http://www.slm.dnsdojo.net/content/tech/myth/index.php#begin_peak.html

Cheers
Steve Myatt


      parent reply	other threads:[~2012-01-21 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15  9:36 No video0, /dev/dvb/adapter0 present Cliffe
2010-05-15 15:46 ` CityK
2010-05-19  8:37   ` Cliffe
2012-01-21 12:38 ` Steve Myatt [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=loom.20120121T132944-762@post.gmane.org \
    --to=steve.myatt.2009@gmail.com \
    --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