Re: sbp2 problem

On 3 Feb, Behdad Esfahbod wrote:
[...]
> With module inserted and turning device on, it takes a few
> seconds again to report the failure. The HD is spinning up in
> this time.
>
> Then I disconnected the device, turned on, and connected firewire
> cable. This way works some times and not all the times.
>
> Then I found another way around it: I connect both USB and
> FireWire cables to enclosure and turn it on. It's immediately
> recognized as a USB storage. [...] Now if I disconnet the USB cable,
> it's immediately recognized as FireWire storage without failure.
>
> Hope it helps someone improve the drivers.

Interesting. Seems like your device presents itself as an SBP-2
capable device early but is not immediately ready to accept the
login attempt of the sbp2 driver. (Or more precisely: It rejects
the packet(s) which carry the request from sbp2 during a brief
period after bus initialization.)

Maybe the sbp2 driver should launch a second login atempt after
the first login failure.

As a work-around you could try a "sleep 5" or similar in
/etc/hotplug/ieee1394.agent immediately after the "add)" label.
That would leave a pause before modprobe sbp2 is executed by this
script. It won't help in situations where the sbp2 module is
already loaded when the drive is connected, of course.

-- 
Stefan Richter
-=====-=-=-- --=- --=--
http://arcgraph.de/sr/
-------------------------------------------------------
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
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user