From: Roland Hieber <rohieb@rohieb.name>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Problems with af9013/5: I2C read failed reg:d417, bulk message failed:-22
Date: Sun, 27 Sep 2009 23:02:24 +0200 [thread overview]
Message-ID: <4ABFD2E0.7000103@rohieb.name> (raw)
Hello,
I am having problems with my DIGITTRADE DVB-T USB Stick with af9015 chipset
since a few weeks. It works for a while (sometimes about 3 minutes, sometimes
half an hour) but suddenly the video stream freezes and dmesg says:
> [ 155.924040] usb 1-6: new high speed USB device using ehci_hcd and address 4
> [ 156.091151] usb 1-6: configuration #1 chosen from 1 choice
> [ 156.096560] Afatech DVB-T: Fixing fullspeed to highspeed interval: 16 -> 8
> [ 156.096985] input: Afatech DVB-T as /devices/pci0000:00/0000:00:10.3/usb1/1-6/1-6:1.1/input/input7
> [ 156.138858] generic-usb 0003:15A4:9016.0002: input,hidraw1: USB HID v1.01 Keyboard [Afatech DVB-T] on usb-0000:00:10.3-6/input1
> [ 156.262580] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
> [ 156.262591] usb 1-6: firmware: requesting dvb-usb-af9015.fw
> [ 156.313938] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
> [ 156.382340] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
> [ 156.382441] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> [ 156.382984] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick)
> [ 156.906560] af9013: firmware version:4.95.0
> [ 156.911056] DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
> [ 156.995283] MT2060: successfully identified (IF1 = 1220)
> [ 157.471840] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
> [ 157.551768] usbcore: registered new interface driver dvb_usb_af9015
> [ 239.765547] usb 1-6: USB disconnect, address 4
> [ 239.769954] af9015: bulk message failed:-22 (8/-224805168)
> [ 239.769961] af9013: I2C read failed reg:d417
> [ 239.769965] af9015: bulk message failed:-22 (8/-1067461161)
> [ 239.769968] af9013: I2C read failed reg:d417
> [ 239.769971] af9015: bulk message failed:-22 (9/54295)
> [ 239.769973] mt2060 I2C write failed
> [ 239.769975] af9015: bulk message failed:-22 (8/134)
> [ 239.769977] af9013: I2C read failed reg:d417
> [ 239.769980] af9015: bulk message failed:-22 (8/15)
> [ 239.769982] af9013: I2C read failed reg:d417
> [ 239.769986] af9015: bulk message failed:-22 (8/-1065361500)
> [ 239.769988] af9013: I2C read failed reg:d730
I am not even able to rmmod the dvb_usb_af9015 driver, the process hangs.
I already tried a more recent firmware and driver, so I am now working with
firmware v4.95.0 and changeset 71dec186cdae of the v4l-dvb repository. My
system is running on a 2.6.28-15-generic #49-Ubuntu SMP kernel.
What do these error messages mean? What meaning do the numbers have? Could it
be that my hardware is broken? It has now been working for over a year now
without major problems (and even better than on Windows, thanks to v4l-dvb ;-))
Thanks in advantage,
Roland Hieber
_______________________________________________
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
reply other threads:[~2009-09-27 21:02 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=4ABFD2E0.7000103@rohieb.name \
--to=rohieb@rohieb.name \
--cc=linux-dvb@linuxtv.org \
--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