On Sunday 18 July 2004 12:20am, Marr wrote:
> On Saturday 17 July 2004 04:47pm, Xander Hsia wrote:
> > Good to know I'm not the only one seeing this.
>
> Well, it gets even weirder, for me anyway.
>
> I tried plugging my Cruzer Mini into a couple of other machines to see if I
> could duplicate the 'hangs up for a long time on mount' problem, but I
> wound up with something ever weirder going on!
>
> My Cruzer Mini (256MB) has always reported Vendor/Product ID of 0781:8185.
>
> ---------------
> Aside: In fact, I even provided a patch to Vojtech Pavlik to upgrade the
> 'usb.ids' file since that particular Product ID was missing. I assumed that
> Sandisk used the same PID for all capacities, so I used 'SDCZ2-nnn' in the
> first part of the description (nnn=256 for me). It appears as if your
> Cruzer Mini is reporting VID/PID of 0781:7101, so maybe my assumption was
> wrong. What capacity is your Cruzer Mini?
> ---------------
>
> Now, for reasons unknown, this same Sandisk Cruzer Mini seems to be
> reporting VID/PID of 05E3:07A0 ('Genesys Logic, Inc.', 'Pen Flash')! How
> in the world could that be?!?!? I thought I was losing my sanity at first,
> but I tried plugging it into 2 other PCs and all 3 reported the same thing!
>
> As stated previously, I've re-partitioned the Cruzer Mini a few times, but
> I've never noticed the VID/PID being altered -- I didn't think that was
> possible, since it should be coming from [E][P]ROM.
>
> Back on the subject of slow mounts, I have not noticed it occurring in my
> recent testing. The closest I came was a long delay (probably a couple of
> minutes, but I wasn't timing it) when I powered up my Shuttle SN41G2
> (nForce2 chipset), plugged in the Sandisk Cruzer Mini, and tried to just
> 'cat /proc/ bus/usb/devices'. I don't think I've ever seen it hang up for a
> long time at _that_ step before! It eventually recovered and reported the
> results, but, as stated earlier, with the oddball VID/PID.
>
> I guess I'm more confused than ever. 8*]
>
> Can anyone explain how such a simple USB device could start reporting a
> different VID/PID?
>
> Bill Marr
Hello all,
Replying to my own (rather old) post here....
Way back then (Jul 2004), it was a big mystery why my SanDisk 'Cruzer Mini'
was reporting a different VID/PID than what it reported when I bought it. At
that point, the drive was still working as a data storage device.
However, the mystery became clearer a few months later when the Cruzer Mini
stopped working entirely -- it wouldn't accept any writes and could no longer
be read from either! Even a reformatting (in both GNU/Linux and W98se) failed
to make it work.
I waited until now to post this reply because I wanted to report on the
quality (good, bad, or otherwise) of SanDisk's customer support, for the good
of future users.
The device was still covered under the 2-year warranty. I had to create what
SanDisk calls an 'eBox' account and register my Cruzer Mini with date/place
of purchase, etc. Since I use GNU/Linux full-time, I registered 'Linux' under
'Please choose your operating system'.
My description of the problem led to a few email exchanges where I had to
demonstrate to them that the device was really broken, by following their
suggestions (via Windows of course, which required examinations of the
Windows Registry -- yuk! -- and some driver installation and drive-formatting
tests).
To their credit, they pretty quickly realized that the device was truly broken
and accepted my request for an RMA (Return Materials Authorization) number to
get them to replace the broken device. Although it took 7 days before the RMA
approval came through, it came in the form of a link to a website to print a
FedEx shipping label on my printer. Once my device was shipped back
(pre-paid) via FedEx, it took another 7 days from the day they received my
broken device before I got the new device via UPS.
The new device still has a 2-year warranty and it's the newer slimmer version,
despite the fact that the model number is the same (SDCZ2-256). It does
report a different VID/PID (0781:5150, for which I'll soon be submitting a
patch to Vojtech for the 'usb.ids' file) than the old thick one (0781:8185).
Bottom Line: I'm happy with SanDisk's service and customer support, despite
the fact that they seem to cling to the old Windows-only school of thought.
Other than the time, it cost me nothing to get the device replaced. Only time
will tell if the new Cruzer Mini holds up better than the old one.
Sorry for the long report, but I wanted to report my experience with SanDisk's
customer service with the hope that it's useful for someone.
P.S. Early and brief testing with this newer, slimmer 'Cruzer Mini' seems to
show no evidence of the annoying, long mount times -- the subject of this
thread originally -- or of any wackiness/slowness with 'cat /proc/bus/usb/
devices', but I haven't done any reformatting of the drive yet. More to
follow if/when it's appropriate (i.e. if/when I can reproduce any of the
problems with the previous Cruzer Mini).
Bill Marr
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
