From: Glen Harris <astfgl@iamnota.org>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] New AverTV A800 hardware revision fails
Date: Sun, 30 Mar 2008 10:17:12 +1000 [thread overview]
Message-ID: <47EEDC08.6060402@iamnota.org> (raw)
I've been recommending the A800 to friends here, as it "just works".
Well, that confidence has come back to bite me, as two friends just
bought units and they don't work with the existing firmware and driver.
Differences are:
Board A800-D A800-F
DiBcom chip DiB3000P-C112a DiB3000P-2122a-G
Cypress chip CY7C68013-56PVC CY7C68013A-56PVXC
Panasonic yuner ENV57H12D5 ENV57H12D5F
I've tested with several kernels from 2.6.18 to 2.6.24 on known working
systems, ie I've unplugged my units and plugged theirs in, and the
syslog shows the firmware being sent, but that's it.
Here's the syslog lines:
Mar 30 09:35:11 m1210 kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 48
Mar 30 09:35:11 m1210 kernel: usb 5-1: configuration #1 chosen from 1 choice
Mar 30 09:35:11 m1210 kernel: dvb-usb: found a 'AVerMedia AverTV DVB-T
USB 2.0 (A800)' in cold state, will try to load a firmware
Mar 30 09:35:11 m1210 kernel: dvb-usb: downloading firmware from file
'dvb-usb-avertv-a800-02.fw'
Mar 30 09:35:11 m1210 kernel: usbcore: registered new driver dvb_usb_a800
The driver never gets to the disconnect-reconnect stage, and the blue
light never comes on. I've plugged in my device immediately after trying
the new one, and it loads perfectly, so the kernel driver hasn't hung or
anything. I suspect that there's a new firmware revision to go with the
new board revision.
I've tried USBsnoop on a W2K host and get about 130K of data, but it's
mostly an English description of the protocol, the actual hex data
captured is less than 1kb. This is the problem we had last time getting
the firmware. I've also tried via a VMWare W2K host, but the driver
won't install correctly. I have the windows driver isolated, but I can't
find any chunk that bears a resemblance to the existing v02 firmware
file we're using.
The syslog above was generated after loading dvb-usb with debug=127, but
it's no different than without the debug. Is there a trick to getting
debug logs?
I'm not sure what to try next, can anyone suggest where I go from here?
Thanks, glen.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
reply other threads:[~2008-03-30 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47EEDC08.6060402@iamnota.org \
--to=astfgl@iamnota.org \
--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