[CentOS] lacie drive and CentOS 5.3 question...

Mon May 25 23:23:39 UTC 2009
Ray Van Dolson <rayvd at bludgeon.org>

On Tue, May 26, 2009 at 01:15:56AM +0200, Dag Wieers wrote:
> On Mon, 25 May 2009, Ray Van Dolson wrote:
> 
> > On Mon, May 25, 2009 at 06:05:44PM -0400, Robert Heller wrote:
> >> At Mon, 25 May 2009 14:25:18 -0700 CentOS mailing list <centos at centos.org> wrote:
> >>> On Mon, May 25, 2009 at 05:20:25PM -0400, Robert Heller wrote:
> >>>
> >>>> What are the kernel versions?
> >>>
> >>> CentOS kernel:
> >>>
> >>>   2.6.18-128.1.6.el5.centos.plus
> >>>
> >>> Fedora 10 kernel:
> >>>
> >>>   2.6.27.21-170.2.56.fc10.i686
> >>
> >> It could just be a kernel bug that RedHat didn't back port (or one that
> >> can't be backported easily).  Or just a driver update (eg adding a few
> >> lines to a driver scan structure) that has not been backported yet.
> >>
> >> You could get the kernel sources for both kernels and compare the
> >> relevant .c and .h files and possibly patch the centos.plus kernel and
> >> rebuild it.  Probably not for the faint hearted...
> >>
> >> It might also be possible to install the FC10 kernel itself...
> >
> > Actually, looks like I got it working.  And I was way off on a wild
> > goose chase.  Turns out that after performing this[1] procedure, the
> > drive is recognized correctly by CentOS.
> >
> > Well I learned a little bit more about how udev works at least. :-)
> >
> > Now my lsusb looks like the following:
> >
> >  Bus 001 Device 024: ID 059f:0527 LaCie, Ltd
> >  Bus 001 Device 016: ID 0451:6250 Texas Instruments, Inc.
> >
> > (One drive I still need to "reset").
> >
> > Sorry for the noise all.
> 
> And what was that Texas Instruments device that does not show up on Fedora ?
> 
> I am intrigued ;-)

I can only guess it's the device presented to the OS when it hasn't
been unmounted properly... 

  http://focus.ti.com/docs/prod/folders/print/tusb6250.html

Shows it to be a USB/ATA bridge of some sort -- Texas Instruments.  Why
Fedora seemed more adept at seeing the device may have been purely
coincidence.  I'd assume I could get the drive in a funky state so that
Fedora only sees this TI device as well... though so far I've been
unable to reproduce (on Fedora). :)

Ray