Firewire CD-RW...

[bruce woller]

Hi Bill:
Thanks for your encouragement.  My machine is chronicalogically 
challenged (an old G3 B&W).  It has the TI PCILynx firewire chip 
controlled across an I2C bus.  So I need to use the pcilynx driver 
module (as opposed to the OHCI1394).  Perhaps the timeout problem that 
was fixed in OHCI1394 didn't get ported to the pcilynx?
On Wednesday, June 4, 2003, at 08:11  PM, Bill Fink wrote:

> Hi bruce,
>
> 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

My pictogram looks like this (leg is down - this is goodness especially 
if you are a fire hydrant!)
                                 S400
                                 TEXAS INSTRUMENTS
                                    |
                                    |
                                    ? <====don't know what the ? means 
I2c bus?
                                 S400 Unknown
                                    |
                                 S400
                                 NOLOGIESINC.
>
> 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.
I checked the dates on my installed modules just to be sure I didn't 
forget to install.
mellow:/etc>modprobe -d sbp2
=============================================
Module ieee1394
kname ieee1394
objkey ieee1394
names: ieee1394
mode: NORMAL
Module matching ieee1394: 
/lib/modules/2.4.20-8dfirewire/kernel/drivers/ieee1394/ieee1394.o
=============================================
=============================================
Module sbp2
kname sbp2
objkey sbp2
names: sbp2
options: sbp2_force_inquiry_hack=1<====hack is enabled
mode: NORMAL
Module matching sbp2: 
/lib/modules/2.4.20-8dfirewire/kernel/drivers/ieee1394/sbp2.o
=============================================
mellow:/etc>ll 
/lib/modules/2.4.20-8dfirewire/kernel/drivers/ieee1394/ieee1394.o
-rw-rw-r--    1 root     adm         85669 Jun  3 09:41 
/lib/modules/2.4.20-8dfirewire/kernel/drivers/ieee1394/ieee1394.o

June 3 9AM is the time I rebuilt modules so I guess I remembered.
>
> Don't give up yet.  I think there may still be some hope.
>
> 						-Bill
> _______________________________________________
>
I'll keep trying -- in a few days.
Thanks again,
bruce