Conflicting results with usb memory sticks
Hello all,
I have conflicting results with 2 different usb memory sticks. One is a rather old fashioned 64 MB usb stick, the other is a 256 MB usb stick that sports an MP3 player. The manual of this latter states that when the battery is removed it can be used as an ordinary usb stick. The 64 MB is recognised by my linux box (Mepis 3.3) as sda1, so no problem. The 256 MB, battery removed, is not recognised. Unfortunately, that other O$ recognises it, with and without battery. I already tried to format it (FAT) but that didn't help. Can anyone shed some light ? Thanks in advance. |
if you insert it and type in lsusb, do you see any information? One first needs to assertain whether it is visible on the usb bus.
|
Thanks Gerardt,
Did just that and it must be the entry on bus 005. The brand of the stick is WMG but there is nothing else connected so Bus 005 Device 002: ID 10d6:1100 Actions Semiconductor Co., Ltd Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 002: ID 03f0:6004 Hewlett-Packard DeskJet 5550 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 Now what can I do ? Just need the memory stick function so I can pump over mp3's and/or data. |
Check out the thread below. Others are having the same problem with removable USB MSDs. So far an updated udev has made a difference but we are still not there yet.
http://www.linuxquestions.org/questi...5&goto=newpost The positive thing is its visible on the bus. |
2.4.x kernels give usb storage devices /dev nodes in the order they are connected. The first connected becomes sda, second sdb, third sdc and so on. So if you had first connected the 64 MB stick and after that connected the 256 MB stick, the latter is accessible as /dev/sdb1. 2.6.x kernels, I understand, are somewhat smarter with this, but I have no experince with them.
|
All times are GMT -5. The time now is 02:31 AM. |