Linux Syncs Great With Droids
|
|
Comments (9)
I haven't played with a Droid yet (I don't have the need or money for one, and work is a Blackberry outfit), but If it's like the Blackberry's I've seen, you may have to enable mass storage mode in the settings on the phone.
Maybe in a couple of years, when the price and the data plans drop some.
Maybe in a couple of years, when the price and the data plans drop some.
Well, she said it "just showed up" on Windows, which kind of stung.
Does it show up in /proc/partitions?
Ooooo, that's a location I hadn't heard of before. Let's see.
====== [16376.248065] usb 4-1: new high speed USB device using ehci_hcd and address 3 [16376.380947] usb 4-1: New USB device found, idVendor=22b8, idProduct=4285 [16376.380957] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [16376.380964] usb 4-1: Product: MB810 [16376.380969] usb 4-1: Manufacturer: Motorola [16376.380974] usb 4-1: SerialNumber: 015A935C0702E01C [16376.381142] usb 4-1: configuration #1 chosen from 1 choice [16376.598957] Initializing USB Mass Storage driver... [16376.599961] scsi4 : SCSI emulation for USB Mass Storage devices [16376.600097] usb-storage: device found at 3 [16376.600103] usb-storage: waiting for device to settle before scanning [16376.600116] usbcore: registered new interface driver usb-storage [16376.600124] USB Mass Storage support registered. [16381.596670] usb-storage: device scan complete [16381.597486] scsi 4:0:0:0: Direct-Access Motorola MB810 0001 PQ: 0 ANSI: 2 [16381.600003] sd 4:0:0:0: [sdb] Attached SCSI removable disk =====
# cat /proc/partitions major minor #blocks name
8 0 488386584 sda 8 1 485733276 sda1 8 2 1 sda2 8 5 2650693 sda5
Nope. No sdb.
Isn't that the same information I get this way?
# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 478111580 330988040 122836880 73% / tmpfs 1687640 0 1687640 0% /lib/init/rw udev 10240 800 9440 8% /dev tmpfs 1687640 0 1687640 0% /dev/shm
Anyway, the system certainly "sees" it, but whatever it is that automounts isn't grabbing it.
====== [16376.248065] usb 4-1: new high speed USB device using ehci_hcd and address 3 [16376.380947] usb 4-1: New USB device found, idVendor=22b8, idProduct=4285 [16376.380957] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [16376.380964] usb 4-1: Product: MB810 [16376.380969] usb 4-1: Manufacturer: Motorola [16376.380974] usb 4-1: SerialNumber: 015A935C0702E01C [16376.381142] usb 4-1: configuration #1 chosen from 1 choice [16376.598957] Initializing USB Mass Storage driver... [16376.599961] scsi4 : SCSI emulation for USB Mass Storage devices [16376.600097] usb-storage: device found at 3 [16376.600103] usb-storage: waiting for device to settle before scanning [16376.600116] usbcore: registered new interface driver usb-storage [16376.600124] USB Mass Storage support registered. [16381.596670] usb-storage: device scan complete [16381.597486] scsi 4:0:0:0: Direct-Access Motorola MB810 0001 PQ: 0 ANSI: 2 [16381.600003] sd 4:0:0:0: [sdb] Attached SCSI removable disk =====
# cat /proc/partitions major minor #blocks name
8 0 488386584 sda 8 1 485733276 sda1 8 2 1 sda2 8 5 2650693 sda5
Nope. No sdb.
Isn't that the same information I get this way?
# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 478111580 330988040 122836880 73% / tmpfs 1687640 0 1687640 0% /lib/init/rw udev 10240 800 9440 8% /dev tmpfs 1687640 0 1687640 0% /dev/shm
Anyway, the system certainly "sees" it, but whatever it is that automounts isn't grabbing it.
No, "df" only reports on mounted partitions/volumes/slices.
If it doesn't show up in /proc/partitions, it can't be mounted. The exception to this rule is CD-ROM's and DVD-ROM's.
After the USB bus settles, does the device remain in a "connected" state? Plug it in, wait a minute or so, then check "dmesg" for recurring error messages.
If it doesn't show up in /proc/partitions, it can't be mounted. The exception to this rule is CD-ROM's and DVD-ROM's.
After the USB bus settles, does the device remain in a "connected" state? Plug it in, wait a minute or so, then check "dmesg" for recurring error messages.
> ...she said it "just showed up" on Windows..
Well, that lets out the mass storage setting. Of course, Windows may have downloaded the drivers it needs to access it in something other than mass storage mode.
Hmm. It's seeing sdb, but not listing any partitions. What does fdisk show for sdb?
The latest Blackberries we've received won't let you see them unless there's a sd card installed. The internal memory is completely inaccessible from the USB port. The older ones would let you see both the device and the sd card as two separate devices.
Well, that lets out the mass storage setting. Of course, Windows may have downloaded the drivers it needs to access it in something other than mass storage mode.
Hmm. It's seeing sdb, but not listing any partitions. What does fdisk show for sdb?
The latest Blackberries we've received won't let you see them unless there's a sd card installed. The internal memory is completely inaccessible from the USB port. The older ones would let you see both the device and the sd card as two separate devices.
I always use '/usr/sbin/lsusb'.
With or without the -v switch it gives decent info.
With or without the -v switch it gives decent info.
Yes, it stays connected. No other messages until I pull out the cable no matter how long.
I'll try fdisk this evening after she gets home.
'lsusb' got it, new command.
...I love all you guys, you're so _smart_!
I'll try fdisk this evening after she gets home.
'lsusb' got it, new command.
...I love all you guys, you're so _smart_!
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

I have auto-open enabled, if I put a thumb drive in it opens Konqueror as a file browser.
Is there a minimum kernel version?