You are not logged in.
Pages: 1
hi...
i got a new phone - Sony Ericsson k660i.
here is teh output when i'm trying mount his memory stick card.
bash-3.2# fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00042b77
Device Boot Start End Blocks Id System
/dev/sda1 1 3657 29366820 7 HPFS/NTFS
/dev/sda2 3657 3779 979965 83 Linux
/dev/sda3 * 3779 9729 47801376 83 Linux
Disk /dev/sdb: 33 MB, 33475072 bytes
1 heads, 11 sectors/track, 5943 cylinders
Units = cylinders of 11 * 512 = 5632 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 5936 32640+ 4 FAT16 <32M
Disk /dev/sdc: 491 MB, 491782144 bytes
32 heads, 32 sectors/track, 938 cylinders
Units = cylinders of 1024 * 512 = 524288 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 937 479499+ 6 FAT16bash-3.2# mount -t vfat /dev/sdc /media/mp3
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or sobash-3.2# dmesg | tail
sd 6:0:0:1: [sdc] Test WP failed, assume Write Enabled
sd 6:0:0:1: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 6:0:0:1: [sdc] Attached SCSI removable disk
sd 6:0:0:1: Attached scsi generic sg3 type 0
usb-storage: device scan complete
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sdb.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sdc.Help?
Last edited by SmarterChild (2008-08-31 21:08:38)
Offline
You should mount a partition (sdc1), not a disk (sdc).
Offline
Thanks dude, but i have another problem...
when i m mounting the part the partition [sdc1]...
or another mp3 player, i can't delete/edit files...
the permissions are for root only.
i need asolution... it's anoying to konqueror in root mode.
Offline
man mount, the whole first part and the filesystem specifics for fat and vfat. Mandatory reading.
I hate sigs. This one only exists to remind myself to get an avatar.
Offline
the problem isn't solved.
someone can tell me how can i mount a memory stick with normal permissions?
Thanks.
Offline
Doesn't HAL take care of mounting for you?
mount -t vfat -o gid=users,umask=0002 /dev/sdc1 /media/mp3Last edited by lucke (2008-09-01 10:19:28)
Offline
Big Thanks Dude!
Offline
I have a similar problem trying to mount my Sony Ericsson k750i. I used to plug it in using its usb cable and it was auto mounted.
Now I get the following message from dmesg:
usb 5-2: new full speed USB device using uhci_hcd and address 7
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 8
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 9
usb 5-2: device not accepting address 9, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 10
usb 5-2: device not accepting address 10, error -71
hub 5-0:1.0: unable to enumerate USB device on port 2I tried rmmod uhci_hcd && modprobe uhci_hcd which I 've found in google but with no result.
I think it has to do with the kernel upgrade.. Any ideas how to solve it?
Offline
I tried rmmod uhci_hcd && modprobe uhci_hcd which I 've found in google but with no result.
I was dealing with a similar issue just yesterday... the trick I found was to rmmod ehci_hcd, but don't reload it afterwards--just leave it unloaded. Then reinsert the thumb drive and see if it gets detected properly. The downside to this is that it will only operate at USB 1.0 speeds. I do think it's a regression within the kernel and from what I've seen plenty of people are complaining about it.
thayer williams ~ cinderwick.ca
Offline
axel wrote:I tried rmmod uhci_hcd && modprobe uhci_hcd which I 've found in google but with no result.
I was dealing with a similar issue just yesterday... the trick I found was to rmmod ehci_hcd, but don't reload it afterwards--just leave it unloaded. Then reinsert the thumb drive and see if it gets detected properly. The downside to this is that it will only operate at USB 1.0 speeds. I do think it's a regression within the kernel and from what I've seen plenty of people are complaining about it.
I tried rmmod ehci_hcd but again I get the same error message.
usb 5-2: new full speed USB device using uhci_hcd and address 3
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 4
usb 5-2: device descriptor read/64, error -71
usb 5-2: device descriptor read/64, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 5
usb 5-2: device not accepting address 5, error -71
usb 5-2: new full speed USB device using uhci_hcd and address 6
usb 5-2: device not accepting address 6, error -71
hub 5-0:1.0: unable to enumerate USB device on port 2It must have been a month ago when I last connected my phone to the usb port and at that time it was working fine. If not the kernel something else broke it. ![]()
Offline
Pages: 1