From: Greg KH <greg@kroah.com>
To: jlnance@unity.ncsu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB does not work after 2.4.18 to 2.5.44-ac2 upgrade
Date: Fri, 25 Oct 2002 13:10:12 -0700 [thread overview]
Message-ID: <20021025201012.GK29874@kroah.com> (raw)
In-Reply-To: <20021025024906.GA18214@ncsu.edu>
On Thu, Oct 24, 2002 at 10:49:06PM -0400, jlnance@unity.ncsu.edu wrote:
> Hello All,
> I decided to do what Linus asked, and try out a 2.5.X kernel.
> The machine boots fine with the 2.5.44-ac2 kernel I installed, however
> I am having some problems with USB. The usb-uhci module seems to be
> gone. I read Documentation/usb/uhci.txt and it appears that the
> uhci module has been rewritten. I assume the module named uhci-hcd.o
> is the replacement, but I could not find that written down anywhere.
> I did an insmod of this module and I can now see the hub in
> /proc/bus/usb/devices. I dont see any of my other USB devices in that
> file, even after I insmod the drivers.
Are your devices plugged in? :)
What does the kernel log say when you plug them in?
thanks,
greg k-h
prev parent reply other threads:[~2002-10-25 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 2:49 jlnance
2002-10-25 8:45 ` Duncan Sands
2002-10-25 20:10 ` Greg KH [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=20021025201012.GK29874@kroah.com \
--to=greg@kroah.com \
--cc=jlnance@unity.ncsu.edu \
--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
Powered by JetHome