Hi folks,
If I connect a USB memory stick to my laptop it access it fine, with it appearing in the 'Devices recently plugged in' and I can access the stick fine.
If I try this with my Samsung Galaxy S in Mass storage mode, it doesn't work.
If you look at the following extract from /var/log/messages, you can see that it gets as far as seeing the two devices (Phone memory and Micro SD card) but doesn't make them available. The Toshiba shown below is the memory stick that works.
Anyone know what I need to do to fix this?
Gary
[root@dcomp5 ~]# tail -f /var/log/messages Sep 22 17:11:08 dcomp5 kernel: usb 2-4: Manufacturer: SAMSUNG Sep 22 17:11:08 dcomp5 kernel: usb 2-4: SerialNumber: 90002a0767da Sep 22 17:11:09 dcomp5 kernel: scsi6 : usb-storage 2-4:2.0 Sep 22 17:11:10 dcomp5 kernel: scsi 6:0:0:0: Direct-Access SAMSUNG GT-I9000 Card 0000 PQ: 0 ANSI: 2 Sep 22 17:11:10 dcomp5 kernel: scsi 6:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2 Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:1: [sdc] Attached SCSI removable disk Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:1: Attached scsi generic sg3 type 0 Sep 22 17:14:25 dcomp5 kernel: usb 2-4: USB disconnect, address 7 Sep 22 17:16:38 dcomp5 kernel: usb 2-4: new high speed USB device using ehci_hcd and address 8 Sep 22 17:16:38 dcomp5 kernel: usb 2-4: New USB device found, idVendor=04e8, idProduct=681d Sep 22 17:16:38 dcomp5 kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 22 17:16:38 dcomp5 kernel: usb 2-4: Product: SAMSUNG_Android Sep 22 17:16:38 dcomp5 kernel: usb 2-4: Manufacturer: SAMSUNG Sep 22 17:16:38 dcomp5 kernel: usb 2-4: SerialNumber: 90002a0767da Sep 22 17:16:38 dcomp5 kernel: scsi7 : usb-storage 2-4:2.0 Sep 22 17:16:39 dcomp5 kernel: scsi 7:0:0:0: Direct-Access SAMSUNG GT-I9000 Card 0000 PQ: 0 ANSI: 2 Sep 22 17:16:39 dcomp5 kernel: scsi 7:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2 Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:0: Attached scsi generic sg2 type 0 Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:1: Attached scsi generic sg3 type 0 Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:0: [sdb] Attached SCSI removable disk Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:1: [sdc] Attached SCSI removable disk Sep 22 17:17:22 dcomp5 kernel: usb 2-4: USB disconnect, address 8 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: new high speed USB device using ehci_hcd and address 9 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: New USB device found, idVendor=0930, idProduct=6545 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: Product: TransMemory Sep 22 17:17:29 dcomp5 kernel: usb 2-4: Manufacturer: TOSHIBA Sep 22 17:17:29 dcomp5 kernel: usb 2-4: SerialNumber: 001D0F0C73BFB9805315028B Sep 22 17:17:29 dcomp5 kernel: scsi8 : usb-storage 2-4:1.0 Sep 22 17:17:30 dcomp5 kernel: scsi 8:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 0 CCS Sep 22 17:17:30 dcomp5 kernel: sd 8:0:0:0: Attached scsi generic sg2 type 0 Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] 31494144 512-byte logical blocks: (16.1 GB/15.0 GiB) Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Write Protect is off Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through Sep 22 17:17:32 dcomp5 kernel: sdb: sdb1 Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Attached SCSI removable disk Sep 22 17:18:09 dcomp5 hald: mounted /dev/sdb1 on behalf of uid 500 Sep 22 17:18:47 dcomp5 dhclient[2185]: DHCPREQUEST on wlan0 to 10.1.1.115 port 67 Sep 22 17:18:47 dcomp5 dhclient[2185]: DHCPACK from 10.1.1.115 Sep 22 17:18:47 dcomp5 dhclient[2185]: bound to 10.1.103.29 -- renewal in 8547 seconds. Sep 22 17:19:58 dcomp5 hald: unmounted /dev/sdb1 from '/media/TOSHIBA' on behalf of uid 500 ^C [root@dcomp5 ~]# uname -a Linux dcomp5.ringways.co.uk 2.6.34.6-47.fc13.i686 #1 SMP Fri Aug 27 09:48:44 UTC 2010 i686 i686 i386 GNU/Linux [root@dcomp5 ~]#
On Wed, 2010-09-22 at 17:53 +0100, Gary Stainburn wrote:
Hi folks,
If I connect a USB memory stick to my laptop it access it fine, with it appearing in the 'Devices recently plugged in' and I can access the stick fine.
If I try this with my Samsung Galaxy S in Mass storage mode, it doesn't work.
If you look at the following extract from /var/log/messages, you can see that it gets as far as seeing the two devices (Phone memory and Micro SD card) but doesn't make them available. The Toshiba shown below is the memory stick that works.
Anyone know what I need to do to fix this?
Gary
[root@dcomp5 ~]# tail -f /var/log/messages Sep 22 17:11:08 dcomp5 kernel: usb 2-4: Manufacturer: SAMSUNG Sep 22 17:11:08 dcomp5 kernel: usb 2-4: SerialNumber: 90002a0767da Sep 22 17:11:09 dcomp5 kernel: scsi6 : usb-storage 2-4:2.0 Sep 22 17:11:10 dcomp5 kernel: scsi 6:0:0:0: Direct-Access SAMSUNG GT-I9000 Card 0000 PQ: 0 ANSI: 2 Sep 22 17:11:10 dcomp5 kernel: scsi 6:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2 Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:1: [sdc] Attached SCSI removable disk Sep 22 17:11:10 dcomp5 kernel: sd 6:0:0:1: Attached scsi generic sg3 type 0 Sep 22 17:14:25 dcomp5 kernel: usb 2-4: USB disconnect, address 7 Sep 22 17:16:38 dcomp5 kernel: usb 2-4: new high speed USB device using ehci_hcd and address 8 Sep 22 17:16:38 dcomp5 kernel: usb 2-4: New USB device found, idVendor=04e8, idProduct=681d Sep 22 17:16:38 dcomp5 kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 22 17:16:38 dcomp5 kernel: usb 2-4: Product: SAMSUNG_Android Sep 22 17:16:38 dcomp5 kernel: usb 2-4: Manufacturer: SAMSUNG Sep 22 17:16:38 dcomp5 kernel: usb 2-4: SerialNumber: 90002a0767da Sep 22 17:16:38 dcomp5 kernel: scsi7 : usb-storage 2-4:2.0 Sep 22 17:16:39 dcomp5 kernel: scsi 7:0:0:0: Direct-Access SAMSUNG GT-I9000 Card 0000 PQ: 0 ANSI: 2 Sep 22 17:16:39 dcomp5 kernel: scsi 7:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2 Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:0: Attached scsi generic sg2 type 0 Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:1: Attached scsi generic sg3 type 0 Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:0: [sdb] Attached SCSI removable disk Sep 22 17:16:39 dcomp5 kernel: sd 7:0:0:1: [sdc] Attached SCSI removable disk Sep 22 17:17:22 dcomp5 kernel: usb 2-4: USB disconnect, address 8 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: new high speed USB device using ehci_hcd and address 9 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: New USB device found, idVendor=0930, idProduct=6545 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 22 17:17:29 dcomp5 kernel: usb 2-4: Product: TransMemory Sep 22 17:17:29 dcomp5 kernel: usb 2-4: Manufacturer: TOSHIBA Sep 22 17:17:29 dcomp5 kernel: usb 2-4: SerialNumber: 001D0F0C73BFB9805315028B Sep 22 17:17:29 dcomp5 kernel: scsi8 : usb-storage 2-4:1.0 Sep 22 17:17:30 dcomp5 kernel: scsi 8:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 0 CCS Sep 22 17:17:30 dcomp5 kernel: sd 8:0:0:0: Attached scsi generic sg2 type 0 Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] 31494144 512-byte logical blocks: (16.1 GB/15.0 GiB) Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Write Protect is off Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through Sep 22 17:17:32 dcomp5 kernel: sdb: sdb1 Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through Sep 22 17:17:32 dcomp5 kernel: sd 8:0:0:0: [sdb] Attached SCSI removable disk Sep 22 17:18:09 dcomp5 hald: mounted /dev/sdb1 on behalf of uid 500 Sep 22 17:18:47 dcomp5 dhclient[2185]: DHCPREQUEST on wlan0 to 10.1.1.115 port 67 Sep 22 17:18:47 dcomp5 dhclient[2185]: DHCPACK from 10.1.1.115 Sep 22 17:18:47 dcomp5 dhclient[2185]: bound to 10.1.103.29 -- renewal in 8547 seconds. Sep 22 17:19:58 dcomp5 hald: unmounted /dev/sdb1 from '/media/TOSHIBA' on behalf of uid 500 ^C [root@dcomp5 ~]# uname -a Linux dcomp5.ringways.co.uk 2.6.34.6-47.fc13.i686 #1 SMP Fri Aug 27 09:48:44 UTC 2010 i686 i686 i386 GNU/Linux [root@dcomp5 ~]#
---- On KDE, you have to 'mount' the disc using 'Device Notifier' widget - I have no idea what the similar effort is in GNOME.
Craig
On Thursday 23 September 2010 02:50:34 Craig White wrote:
On KDE, you have to 'mount' the disc using 'Device Notifier' widget - I have no idea what the similar effort is in GNOME.
Craig
Hi Craig,
Thanks for this, but that's my problem. With the memory stick, it appears in the device notifier. With the phone, it doesn't.
Gary
On Thu, 2010-09-23 at 12:35 +0100, Gary Stainburn wrote:
On Thursday 23 September 2010 02:50:34 Craig White wrote:
On KDE, you have to 'mount' the disc using 'Device Notifier' widget - I have no idea what the similar effort is in GNOME.
Craig
Hi Craig,
Thanks for this, but that's my problem. With the memory stick, it appears in the device notifier. With the phone, it doesn't.
---- Just stating the obvious... You MUST enable USB storage on the telephone after you plug it into a USB port on a computer for it to work.
Try plugging it into a Mac or Windows computer and see if it mounts automatically (after enabling USB storage of course). I don't think this is Linux/Fedora issue.
Also for what it's worth, the Galaxy S was Samsung's first foray into Android devices and the internal document leaked by Verizon listed a very large number of software issues that Samsung has to fix. I don't recall if USB connectivity was one of them. At least they apparently have fixed the GPS issues and software updates are starting to come out now.
Craig
Note also that it works perfectly fine as mtp device with rhythmbox. Perhaps amarok will work as well, I haven't tested that
Stefan
2010/9/23 Craig White craigwhite@azapple.com
On Thu, 2010-09-23 at 12:35 +0100, Gary Stainburn wrote:
On Thursday 23 September 2010 02:50:34 Craig White wrote:
On KDE, you have to 'mount' the disc using 'Device Notifier' widget - I have no idea what the similar effort is in GNOME.
Craig
Hi Craig,
Thanks for this, but that's my problem. With the memory stick, it appears
in
the device notifier. With the phone, it doesn't.
Just stating the obvious... You MUST enable USB storage on the telephone after you plug it into a USB port on a computer for it to work.
Try plugging it into a Mac or Windows computer and see if it mounts automatically (after enabling USB storage of course). I don't think this is Linux/Fedora issue.
Also for what it's worth, the Galaxy S was Samsung's first foray into Android devices and the internal document leaked by Verizon listed a very large number of software issues that Samsung has to fix. I don't recall if USB connectivity was one of them. At least they apparently have fixed the GPS issues and software updates are starting to come out now.
Craig
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
My laptop is dual boot with WinXP. In XP it works perfectly fine, but as Samsung Keis and as mass storage. I have completed a firmware update but it has made no difference.
It still doesn't work, with the /var/log/messages entry still being the same as my first post
On Wednesday, September 29, 2010 04:01:43 am Gary Stainburn wrote:
My laptop is dual boot with WinXP. In XP it works perfectly fine, but as Samsung Keis and as mass storage. I have completed a firmware update but it has made no difference.
It still doesn't work, with the /var/log/messages entry still being the same as my first post
I dont have access to windows at all so i have no idea how it works there. but my captivate ( at&t branded galaxy s) i select storage then i have to slide down the notification bar select the "USB connected select to copy files to/from your computer" then tell it yes mount. after that its automatically mounted for me. when done i need to redo that procedure and tell it to unmount. after ive unmounted from my laptop/desktop. I assume that you need to do the same thing for whatever galaxy s variant it is that you have.
Dennis
On Thursday 30 September 2010 04:23:44 Dennis Gilmore wrote:
I dont have access to windows at all so i have no idea how it works there. but my captivate ( at&t branded galaxy s) i select storage then i have to slide down the notification bar select the "USB connected select to copy files to/from your computer" then tell it yes mount. after that its automatically mounted for me. when done i need to redo that procedure and tell it to unmount. after ive unmounted from my laptop/desktop. I assume that you need to do the same thing for whatever galaxy s variant it is that you have.
Dennis
Spot on.
When you're in USB Debug mode, it pops a dialog box up in the middle of the screen asking if you want to mount the drives for USB. As I said before, this then works fine.
However, with USB Debugging turned off it doesn't do this. It just shows it in the notification window. If you don't know to look there, as I didn't, it never gives the drives over to the USB connection.
Problem solved, apart from wondering why it worked when I booted into WinXP?
I suppose we'll never know, but at least it's working now
Gary
-
Craig White -
Dennis Gilmore -
Gary Stainburn -
stefan riemens