Firewire CD-RW...
Bill Fink
yellowdog-general@lists.terrasoftsolutions.com
Wed Jun 4 20:11:01 2003
Hi bruce,
On Wed Jun 4 2003, bruce woller wrote:
> I got the proper directory from linux1394.org. Modules built fine.
> Little or no change from my current 1394 quandery though. I have tried
> all the little tricks and tips (i.e. booting with device unplugged,
> rmmod-insmod sbp2 , mounting /dev/sg0) that I have seen in this list to
> no avail. One interesting observation is: with gscanbus displaying
> it's little diagram when the device is unplugged the device leg
> disappears in the picture - when plugged back in it re-appears. Cool!
> This means that hot-plug is working (I think. Unless gscanbus polls?).
> My dmesg output still indicates an error(which may or may not be an
> error according to ieee1394.org?):
I noticed something in your dmesg output. The highest node number
(in your case node 2) should normally be the Linux OHCI-1394 node.
When you run gscanbus, is the Linux OHCI-1394 node at the top of the
graph. If it's not things won't work right. My graph looks like:
S400
Linux OHCI-1394
/ \
/ \
/ \
/ \
S400 S100
LaCie Group SA Sony
If the Linux OHCI-1394 node isn't at the top of the graph, try doing
a Force Bus Reset under the Control menu in gscanbus. The older
ieee1394 code had an "attempt_root=1" option for ohci1394 but this
is no longer available and supposedly not needed if you're running
the latest SVN code.
I thought all the sbp2 "login timed-out" problems were fixed with
the latest SVN code (you did do a "make modules_install" I assume).
If all else fails, you can try the sbp2_force_inquiry_hack=1 option
to sbp2.
Don't give up yet. I think there may still be some hope.
-Bill