usb drive not recognized, maybe timing?

[Kay Sievers]

On Tue, Sep 13, 2005 at 12:09:19AM +0400, Eugene Crosser wrote:
> Gentlemen,
> I had problems subscribing to this list, and tried to send this being
> not subscribed, and it apparently was dropped by moderator.  I am trying
> again:
> 
> Now that CDROM gets successfully recognized by HAL thanks to Kay's
> advice, I start investigating why usb drive is not recognized.
> 
> I have hal 5.0.4 running (with --retain-privileges) on kernel 2.6.13,
> with udev 0.64. When a usb drive is inserted, hald recognizes is as
> "usb_noserial", not as a block device with a filesystem.  I suspect that
> it has something to do with "Cannot open" messages in the HAL debug
> output (attached).  If I start hald when the USB drive is already
> unserted, it *is* recognized and appears in `lshal' output.
> 
> Now, the interesting part.  When I manually cat the sys files that hald
> could not open, a few seconds later, most of them are in place and
> perfectly readable.  On the other hand, if I watch dmesg, I can see that
> there is a several seconds' pause between "usb-storage: device found at
> 20" and final "usb-storage: device scan complete" message.  Maybe hald
> is trying to open sysfs files while the kernel did not create them yet?

That should be covered by udev managing the whole hotplug process.
Does:
  cat /proc/sys/kernel/hotplug
print /sbin/udevsend?

Kay