On Sun, 7 Aug 2011, [ISO-8859-1] Torquil Macdonald S�en wrote: > Hi! > > My Linux 3.0.1 system seems to not automatically detect the partition table on > my Sony Ericsson T707 mobile phone USB mass storage devices. After connecting it > to the USB port on my computer, I get the following additional lines in the > kernel log: > > usb 1-1: new high speed USB device number 5 using ehci_hcd > usb 1-1: New USB device found, idVendor=0fce, idProduct=e11d > usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > usb 1-1: Product: Memory Card (MSC) > usb 1-1: Manufacturer: Sony Ericsson > usb 1-1: SerialNumber: 3545170352001900 > Initializing USB Mass Storage driver... > scsi6 : usb-storage 1-1:1.0 > usbcore: registered new interface driver usb-storage > USB Mass Storage support registered. > scsi 6:0:0:0: Direct-Access Sony Eri Memory Card 0000 PQ: 0 ANSI: 0 > scsi 6:0:0:1: Direct-Access Sony Eri Memory Card 0000 PQ: 0 ANSI: 0 > sd 6:0:0:0: Attached scsi generic sg2 type 0 > sd 6:0:0:1: Attached scsi generic sg3 type 0 > sd 6:0:0:0: [sdb] Attached SCSI removable disk > sd 6:0:0:1: [sdc] Attached SCSI removable disk > > There is /dev/sdb and /dev/sdc since the phone has two USB mass storage units. > One for the internal memory and one for the memory card. > > However, only /dev/sdb and /dev/sdc are created, not /dev/sdb1 and /dev/sdc1. > > If I (as root) run 'fdisk -l /dev/sdc', I get a proper list of partitions: > > Disk /dev/sdc: 8002 MB, 8002732032 bytes > 184 heads, 35 sectors/track, 2427 cylinders, total 15630336 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Device Boot Start End Blocks Id System > /dev/sdc1 * 4476 15618427 7806976 c W95 FAT32 (LBA) > > And after doing this, the /dev/sdc1 has been created, and I can mount the memory > card in the usual fashion. Simultaneously, I get the following in the kernel log: > > sd 6:0:0:1: [sdc] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB) > sd 6:0:0:1: [sdc] Test WP failed, assume Write Enabled > sd 6:0:0:1: [sdc] Asking for cache data failed > sd 6:0:0:1: [sdc] Assuming drive cache: write through > sd 6:0:0:1: [sdc] Test WP failed, assume Write Enabled > sd 6:0:0:1: [sdc] Asking for cache data failed > sd 6:0:0:1: [sdc] Assuming drive cache: write through > sdc: sdc1 > > But why is the partition /dev/sdc1 not detected automatically, as I am used to > from before. Why must I run the 'fdisk -l' command in order to get the kernel to > detect the existence of /dev/sdc1. Is it not reading the partition table before > I run fdisk? It's hard to answer these questions without more information. In partial answer to the last question: Naturally the computer _tries_ to read the partition table before you run fdisk. Evidently it doesn't succeed. > I don't use any kind of automounting. This is on a Debian Sid system on an Asus > X5DID amd64 laptop running the Linux 3.0.1 kernel. > > It does detect the partition automatically on both of my other two USB flash > memory sticks, however. To get more information you can collect a usbmon trace. See the instructions in the kernel source file Documentation/usb/usbmon.txt. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
