From: M G Berberich <berberic@fmi.uni-passau.de>
To: linux-kernel@vger.kernel.org
Subject: usbnet 2.5/2.6.6-rc1
Date: Mon, 19 Apr 2004 21:38:07 +0200 [thread overview]
Message-ID: <20040419193807.GA1864@avaloon.intern> (raw)
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
Hello,
the usbnet module from 2.6.5 and 2.6.6-rc1 is not working with my
zaurus. 2.6.3 worked fine.
The log-messages are exactly the same in all three cases:
usb 2-2: new full speed USB device using address 3
usb0: register usbnet at usb-0000:00:0c.0-2, Sharp Zaurus SL-5x00
and the usb0 device is configured the same, but with kernel 2.6.3 the
connection works, with 2.6.5 and 2.6.6.-rc1 nothing happens. Trying to
ping the zaurus times out and trying to remove the usbnet module
hangs.
BTW: I'm not subscribed to this list.
MfG
bmg
--
"Des is völlig wurscht, was heut beschlos- | M G Berberich
sen wird: I bin sowieso dagegn!" | berberic@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg) | www.fmi.uni-passau.de/~berberic
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-04-19 19:40 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=20040419193807.GA1864@avaloon.intern \
--to=berberic@fmi.uni-passau.de \
--cc=linux-kernel@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