At Mon, 25 May 2009 12:53:55 -0700 CentOS mailing list <centos@xxxxxxxxxx> wrote:
>
> On Mon, May 25, 2009 at 09:24:03PM +0200, Dag Wieers wrote:
> > On Mon, 25 May 2009, Dag Wieers wrote:
> >
> > > On Mon, 25 May 2009, Ray Van Dolson wrote:
> > >> On Mon, May 25, 2009 at 11:17:30AM -0700, Ray Van Dolson wrote:
> > >>
> > >>> Can anyone advise me on how I can tell my system the above device is a
> > >>> mass storage device? Do I need to write some udev rules?
> > >>
> > >> Sorry for replying to my own post, but upon further investigation, it
> > >> appears that perhaps the usb-storage module doesn't have the correct
> > >> matching pattern in place to detect this as a mass storage device:
> > >>
> > >> udevmonitor reports the device having a module alias of:
> > >>
> > >> usb:v0451p6250d0300dcFFdsc00dp00icFFisc00ip00
> > >>
> > >> And modinfo usb-storage shows:
> > >>
> > >> # modinfo usb-storage | grep v045
> > >> alias: usb:v045Ap5210d0101dc*dsc*dp*ic*isc*ip*
> > >> alias: usb:v0457p0151d0100dc*dsc*dp*ic*isc*ip*
> > >> alias: usb:v0457p0150d0100dc*dsc*dp*ic*isc*ip*
> > >> alias: usb:v0451p5416d0100dc*dsc*dp*ic*isc*ip*
> > >>
> > >> Which obviously won't match. So the question is, how do I add a new
> > >> alias to the module? And will the module even support my device?
> > >
> > > Just a wild an crazy idea, how about adding it to /etc/modprobe.conf ?
> > >
> > > alias usb:v0451p6250d0300dcFFdsc00dp00icFFisc00ip00 usb-storage
> > >
> > > Not sure if it makes sense, but it's worth trying :)
> >
> > After doing some research it seems that this is valid, if you perform:
> >
> > modprobe -c
> >
> > you get an identical list for all known devices. So adding yours should
> > definitely help.
> >
> > PS What kind of LaCie disk is it ? I recently bought a 500GB LaCie Little
> > Disk and that one worked fine.
>
> I actually did try adding the above alias line with no luck although
> the following command:
>
> modprobe -v -n --first-time usb:v0451p6250d0300dcFFdsc00dp00icFFisc00ip00
>
> Now shows a "match". I'm beginning to think the kernel doesn't support
> this device, or isn't properly exposing it to /sys as it should be.
>
> I added a udev rule:
>
> BUS=="usb",ACTION=="add",SYSFS{idVendor}=="0451",SYSFS{idProduct}=="6250",RUN+="/sbin/modprobe usb-storage",NAME="walter"
>
> And when I plug in my device, I get the following entry under /dev:
>
> crw------- 1 root root 189, 19 May 25 12:02 /dev/walter
>
> Obviously this isn't major type 8 which I would expect to see for a
> disk... also:
>
> With udevmonitor on my Fedora machine, I see a device created with
> major type 189, but then later, a SCSI device is detected and a device
> of major type 8 is set up. This doesn't happen on CentOS, only the 189
> device is created.
>
> Also, on my Fedora system the vendor id and Product ID's are different.
>
> Fedora:
>
> 059f:0527 LaCie, Ltd
>
> Cent:
>
> 0451:6250 Texas Instruments, Inc.
What are the kernel versions?
>
> So I'm beginning to think that the kernel is sending "incorrect" or
> dated information into /sys and the event sent to udev is either
> misleading or incomplete somehow.
>
> It's a 500GB "Big Disk".
>
> I'll keep poking around... thanks for the reponse. :)
>
> Ray
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
>
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Download the Model Railroad System
http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows
heller@xxxxxxxxxxxx -- http://www.deepsoft.com/ModelRailroadSystem/
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
