From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev/hotplug success story
Date: Mon, 09 Feb 2004 23:12:03 +0000 [thread overview]
Message-ID: <20040209151202.A5874@beaverton.ibm.com> (raw)
In-Reply-To: <4026A5F4.1000901@reactivated.net>
On Mon, Feb 09, 2004 at 12:50:50AM +0100, Måns Rullgård wrote:
> Daniel Drake <dan@reactivated.net> writes:
>
> > Hotplug is doing a good job of managing my usb modules. When I plug my
> > camera in, it loads usb-storage as expected. However, it doesnt load
> > sd_mod, meaning that no /dev/sda1 is created, and I can't access my
> > pictures.
>
> It used to load sd-mod automatically for me, but stopped some time
> around 2.6.2-rc1.
We could race looking for the sys attribute type in scsi.agent.
That is scsi attributes are added after the hotplug is invoked.
Is there anything in your log file from scsi.agent? Like this one:
mesg "how to add device type=$TYPE at $DEVPATH ??"
If so, try adding a sleep 1 in scsi.agent just before the cat of type,
i.e.:
sleep 1
TYPE=$(cat /sys/$DEVPATH/type)
-- Patrick Mansfield
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
next prev parent reply other threads:[~2004-02-09 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 21:11 udev/hotplug success story Daniel Drake
2004-02-08 23:50 ` Måns Rullgård
2004-02-09 23:12 ` Patrick Mansfield [this message]
2004-02-13 1:38 ` Greg KH
2004-03-03 21:48 ` Greg KH
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=20040209151202.A5874@beaverton.ibm.com \
--to=patmans@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).