One of my friends solved the problem by formatting my USB-2.0 drive on his Fedora Core 3 as FAT32 FS type. Now my USB drive gets mounted properly on kernel ver 2.4.x too. Although it throws some error messages, it WORKS. Looks like support for USB-2.0 in 2.4.x kernels in broken as I tried mounting my drive on other 2.4.x kernels too and the behaviour was same.
Hope this helps many others facing similar problem. Thanks. Medha On Wed, 1 Dec 2004 15:24:59 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote: > > > On Wed, 1 Dec 2004, Medha Atre wrote: > > > Hi, > > I am posting all relevant details below. > > -------------------------------------------------------- > > relevant section of /proc/bus/usb/devices when memory stick was plugged in > > -------------------------------------------------------- > > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 > > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > > P: Vendor=0ea0 ProdID=2168 Rev= 2.00 > > S: Manufacturer=USB > > S: Product=Flash Disk > > S: SerialNumber=61100741561A5B6B > > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA > > I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 > > Driver=usb-storage > > E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms > > E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms > > E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=125us > > ---------------------------------------------------------- > > relevant o/p of dmesg after just plugging in memory stick > > ---------------------------------------------------------- > > hub.c: new USB device 00:1d.7-1, assigned address 2 > > usb.c: USB device 2 (vend/prod 0xea0/0x2168) is not claimed by any > > active driver. > > SCSI subsystem driver Revision: 1.00 > > Initializing USB Mass Storage driver... > > usb.c: registered new driver usb-storage > > scsi0 : SCSI emulation for USB Mass Storage devices > > Vendor: JetFlash Model: TS512MJF2B Rev: 2.00 > > Type: Direct-Access ANSI SCSI revision: 02 > > WARNING: USB Mass Storage data integrity not assured > > USB Mass Storage device found at 2 > > USB Mass Storage support registered. > > -------------------------------------------------------------- > > o/p of dmesg after giving mount /dev/sda1 /mnt/usb command > > -------------------------------------------------------------- > > Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 > > sda : READ CAPACITY failed. > > sda : status = 1, message = 00, host = 0, driver = 08 > > Current sd00:00: sense key Unit Attention > > Additional sense indicates Not ready to ready change,medium may have > > changed > > sda : block size assumed to be 512 bytes, disk size 1GB. > > sda: I/O error: dev 08:00, sector 0 > > I/O error: dev 08:00, sector 0 > > unable to read partition table > > SCSI device sda: 1024000 512-byte hdwr sectors (524 MB) > > sda: Write Protect is off > > sda: sda1 sda2 sda3 sda4 > > usb.c: USB disconnect on device 00:1d.7-1 address 2 > > hub.c: new USB device 00:1d.7-1, assigned address 3 > > WARNING: USB Mass Storage data integrity not assured > > USB Mass Storage device found at 3 > > memory : cdef2400 > > memory : cdef2600 > > memory : cdef2180 > > mtrr: base(0xf0020000) is not aligned on a size(0x300000) boundary > > memory : cdef2700 > > memory : cdef2480 > > memory : cdef2780 > > memory : cdef2f00 > > memory : cdef2e00 > > PCI: Found IRQ 11 for device 00:02.0 > > PCI: Sharing IRQ 11 with 00:1d.0 > > usb.c: USB disconnect on device 00:1d.7-1 address 3 > > --------------------------------------------------------------------------------- > > > > The thing to note is that this drive is working properly on my Win2k > > system. Also I had tried mounting some other USB meory sticks of my > > friends (may be of different make but USB2.0 standard only) and they > > worked properly. > > Note: the fact that the device works compatibly with Windows does > _not_ guarantee that the device is operating in compliance with the > appropriate specifications. > > > Please help, getting my memory stick accessed in Linux is only of > > crucial importance to me :( > > Unfortunately I can't tell from this exactly what the problem is. You > will have to get more information, by rebuilding the usb-storage driver > with the verbose debugging option turned on in the kernel configuration. > > By the way, how come you're still using kernel 2.4.20? That's very old by > now; you won't get much support for it. > > Alan Stern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
