From: Mark Healey <marklist@healeyonline.com>
To: linux-hotplug@vger.kernel.org
Subject: Resolved (sort of) No USB devices are being noticed
Date: Tue, 15 Mar 2005 06:15:28 +0000 [thread overview]
Message-ID: <42367D80.8090507@healeyonline.com> (raw)
David Brownell wrote:
> On Friday 11 March 2005 3:00 pm, Mark Healey wrote:
>
>>David Brownell wrote:
>>
>>>On Friday 11 March 2005 12:36 am, Mark Healey wrote:
>>>
>>>
>>>...
>>>
>>>>ohci_hcd 0000:00:01.2: remove, state 1
>>>>usb usb1: USB disconnect, address 1
>>>>ohci_hcd 0000:00:01.2: USB bus 1 deregistered
>>>>ohci_hcd 0000:00:01.3: remove, state 1
>>>>usb usb2: USB disconnect, address 1
>>>>usb 2-1: USB disconnect, address 2
>>>>ohci_hcd 0000:00:01.3: USB bus 2 deregistered
>>>>
>>>
>>>
>>>So your boot code is first loading the HCDs, then unloading them.
>>>The problem is your boot scripts doing something remarkably bogus.
>>
>>HCD?
>
>
> As in "ohci_hcd". "Host Controller Driver", as described
> in the USB spec.
>
>
>
>>How do I determine which script and fix it?
>
>
> You could replace "rmmod" with a shell script that logged the
> relevant stuff ... like maybe saving "ps -ax --forest" output
> when the parameter is an HCD. Then work backwards from there.
From what I read on another site I tried
modprobe ohci_hcd
in
/etc/rc.local
and it works.
It's an ugly fix and whatever is wrong needs fixing but this
will do for now.
--
Mark Healey
marklist@healeyonline.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2005-03-15 6:15 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=42367D80.8090507@healeyonline.com \
--to=marklist@healeyonline.com \
--cc=linux-hotplug@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 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.