From: David <david@unsolicited.net>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Technotrend TT-connect S-2400 - worked in only one kernel release (2.6.26)
Date: Mon, 16 Feb 2009 19:37:12 +0000 [thread overview]
Message-ID: <4999C068.6060400@unsolicited.net> (raw)
There is a bug report in bugzilla about this one, but I'm wondering if
anyone else is seeing problems with this (USB) device. I see the
following timeout in kernel versions beyond 2.6.26
[ 3086.636035] usb 3-10: new high speed USB device using ehci_hcd and
address 7
[ 3086.769507] usb 3-10: configuration #1 chosen from 1 choice
[ 3087.066065] dvb-usb: found a 'Technotrend TT-connect S-2400' in cold
state, will try to load a firmware
[ 3087.066073] usb 3-10: firmware: requesting dvb-usb-tt-s2400-01.fw
[ 3087.102717] dvb-usb: downloading firmware from file
'dvb-usb-tt-s2400-01.fw'
[ 3087.165343] usbcore: registered new interface driver dvb_usb_ttusb2
[ 3087.166071] usb 3-10: USB disconnect, address 7
[ 3087.169039] dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
[ 3088.928027] usb 3-10: new high speed USB device using ehci_hcd and
address 8
[ 3089.061927] usb 3-10: configuration #1 chosen from 1 choice
[ 3089.062504] dvb-usb: found a 'Technotrend TT-connect S-2400' in warm
state.
[ 3089.063148] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 3089.063404] DVB: registering new adapter (Technotrend TT-connect S-2400)
[ 3089.074375] DVB: registering adapter 0 frontend 0 (Philips TDA10086
DVB-S)...
[ 3091.076106] dvb-usb: recv bulk message failed: -110
[ 3091.076113] ttusb2: there might have been an error during control
message transfer. (rlen = 0, was 0)
[ 3091.076349] dvb-usb: Technotrend TT-connect S-2400 successfully
initialized and connected.
the 2.6.26 trace looks normal.
usb 1-3: new high speed USB device using ehci_hcd and address 14
usb 1-3: configuration #1 chosen from 1 choice
dvb-usb: found a 'Technotrend TT-connect S-2400' in cold state, will try
to load a firmware
firmware: requesting dvb-usb-tt-s2400-01.fw
dvb-usb: downloading firmware from file 'dvb-usb-tt-s2400-01.fw'
usb 1-3: USB disconnect, address 14
dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
usb 1-3: new high speed USB device using ehci_hcd and address 15
usb 1-3: configuration #1 chosen from 1 choice
dvb-usb: found a 'Technotrend TT-connect S-2400' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
DVB: registering new adapter (Technotrend TT-connect S-2400)
DVB: registering frontend 3 (Philips TDA10086 DVB-S)...
dvb-usb: Technotrend TT-connect S-2400 successfully initialized and
connected.
Cheers
David
reply other threads:[~2009-02-16 20:03 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=4999C068.6060400@unsolicited.net \
--to=david@unsolicited.net \
--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