From: Greg KH <greg@kroah.com>
To: Dylan Egan <crack_me@bigpond.com.au>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.4.17 - hanging due to usb
Date: Mon, 7 Jan 2002 10:39:48 -0800 [thread overview]
Message-ID: <20020107183948.GJ7378@kroah.com> (raw)
In-Reply-To: <5.1.0.14.0.20020107132332.00b564a8@mail.bigpond.com> <5.1.0.14.0.20020107121314.00ba4258@mail.bigpond.com> <5.1.0.14.0.20020107121314.00ba4258@mail.bigpond.com> <5.1.0.14.0.20020107132332.00b564a8@mail.bigpond.com> <5.1.0.14.0.20020107163253.00b48790@mail.bigpond.com>
In-Reply-To: <5.1.0.14.0.20020107163253.00b48790@mail.bigpond.com>
On Mon, Jan 07, 2002 at 04:43:47PM +1100, Dylan Egan wrote:
>
> >Can you not load the usb-storage driver, load the usbcore module, and
> >the USB host driver that you are using, and point hotplug to somewhere
> >else:
> > echo /bin/true > /proc/sys/kernel/hotplug
> >
> >Then plug in your device, and send the output of /proc/bus/usb/devices
> >to the list (and the linux-usb-devel list, which is a better place for
> >this :)
>
> I only got this extra bit of infomation from the way you said for me to do
> it.
> When i loaded usbcore this time it said cant get major 180 for usb....
> Ok i loaded it as you said it all went find but it never gave me anything
> when i went to do "cat /proc/bus/usb/devices".
Oops, forgot to tell you to mount usbdevfs. Try these steps then:
insmod usbcore
mount -t usbdevfs none /proc/bus/usb
insmod usb-uhci
{plug in device}
cat /proc/bus/usb/devices
thanks,
greg k-h
next prev parent reply other threads:[~2002-01-07 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 1:13 2.4.17 - hanging due to usb Dylan Egan
2002-01-07 1:33 ` Greg KH
[not found] ` <5.1.0.14.0.20020107132332.00b564a8@mail.bigpond.com>
2002-01-07 2:50 ` Greg KH
2002-01-07 5:43 ` Dylan Egan
2002-01-07 18:39 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 18:55 Leif Sawyer
2002-01-07 7:11 Dylan Egan
2002-01-07 0:53 Dylan Egan
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=20020107183948.GJ7378@kroah.com \
--to=greg@kroah.com \
--cc=crack_me@bigpond.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.