Firewire enclosure doesn't work in 3.0.1 [kinda solved]

[Michael George]

On Jan 14, 2004, at 8:52 PM, Gavin Hemphill wrote:
> Well I'm running YDL (bootable) on three enclosures based on the 
> Oxford chip set (some with the firmware updated to work with Panther) 
> so its unlikely to be the chip set.  you fail to mention your kernel 
> version, the hardware you're running on, the enclosure type etc. so I 
> can't offer specific help, but if you search for the firewire howto on 
> the yellowdog site you can probably figure out what you need.

Oops, I did forget that stuff.  Sorry.  It's good to know that it's not 
a chipset problem, though.

I solved the issue, but I'm still not sure what you think...

I used my firewire cable from my DVD+-RW drive.  I still got the error, 
but that didn't seem to be the show-stopper.  When I plugged the 
enclosure in with that cable I got the size error, but the system 
recognized the device and loaded the sbp2 kernel module on its own.  A 
rescan of the scsi bus saw the drive and I'm off & runnin'.

This happened when I used the Glyph enclosure, too.  But that enclosure 
was older, so I suspected a defective cable.  Now I'm wondering if it's 
not that the Glyph's cable was bad, but that my own cable is so good.

So, now my question is "How much variation is there in Firewire 
cables?"  IOW, are the ones that don't work cheap cables but the one 
that works is a better quality one?  Or is there something more subtle 
going on?

> Michael George wrote:
>
>> I just got a firewire enclosure for a 20Gb HDD I have.  I've use the 
>> HDD several times and never had trouble with it.
>> When I plug the firewire beastie into my system running OSX, it 
>> complains that it doesn't recognize the format and asks if I want to 
>> initialize it.  Fine, but I don't want to...
>> So I boot into YDL 3.0.1 (where I *do* plan to use it) and plug it in 
>> and... nothing.
>> I boot w/o it turned on and then fire it up when the system is 
>> booted.  I then manually load the ieee1394, ohci1394, and sbp2 kernel 
>> modules.  They all load fine, but I get a complaint about 
>> "non-standard ROM format" and the drive is never connected to my 
>> system (as scsi1) like my Glyph enclosed drives were.
>> The enclosure had an Oxford OSFW911 1394a-to-IDE link controller and 
>> a TI TSB41AB2 1394a PHY (whatever that is).  Is either of these 
>> chipsets known to be bad?
>> I remember that there's a jumper (set for Master, I'd guess) on the 
>> drive still...  would that make a difference?  I'm trying to 
>> determine if I have a legitimate complaint to return the enclosure...
>> If anyone has any info, I'd sure appreciate it!
>> Thanks!
>> -Michael
>> _______________________________________________
>> yellowdog-general mailing list
>> yellowdog-general@lists.terrasoftsolutions.com
>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
>
-Michael