My new cellphone charges thru USB cable, dmesg says, "usb 1-10: new full speed USB device using ohci_hcd and address 9" when it is connected. What is this telling me about how I might access the linux file system on the phone? How do I discover the/a device name to use? Thanks for guidance to the confused. Richard
Richard wrote:
My new cellphone charges thru USB cable, dmesg says, "usb 1-10: new full speed USB device using ohci_hcd and address 9" when it is connected. What is this telling me about how I might access the linux file system on the phone? How do I discover the/a device name to use? Thanks for guidance to the confused.
If your cellphone does indeed have a filesystem that's readable by Linux, you'll probably need to use the usb-storage module which turns a USB storage device into a SCSI device to Linux. You can then use this device to access the cellphone. What does "lsusb" say? /Per Jessen, Zürich
On Wed March 22 2006 6:35 am, Per Jessen wrote:
Richard wrote:
My new cellphone charges thru USB cable, dmesg says, "usb 1-10: new full speed USB device using ohci_hcd and address 9" when it is connected. What is this telling me about how I might access the linux file system on the phone? How do I discover the/a device name to use? Thanks for guidance to the confused.
If your cellphone does indeed have a filesystem that's readable by Linux, you'll probably need to use the usb-storage module which turns a USB storage device into a SCSI device to Linux. You can then use this device to access the cellphone.
What does "lsusb" say?
/Per Jessen, Zürich
Thanks for your response. Pertinent line from lsusb is, "Bus 001 Device 011: ID 22b8:a732 Motorola PCS". This is the correct phone so apparently it is seen on the usb bus. It seems that once in the hoary past I had created a device for some thing or other, back in SuSE 6x or Mandrake 4.2 era, but darned if I have any idea where to go now. Age is a criminal thing to inflict on the already feeble-minded. Richard
Richard wrote:
Thanks for your response. Pertinent line from lsusb is, "Bus 001 Device 011: ID 22b8:a732 Motorola PCS". This is the correct phone so apparently it is seen on the usb bus.
Yep, so far so good. It communicates with the USB bus, and the USB database knows about it. Well, partially anyway.
From /usr/share/usb.ids:
22b8 Motorola PCS 0005 V.60c/V.60i GSM Phone 1005 T280e GSM/GPRS Phone 2821 T720 GSM Phone 2822 V.120e GSM Phone 3002 A835 GSM Phone 3802 C330/A780 GSM Phone 4002 A920/A925 UMTS Phone 4810 E398 Storage 4902 E398 GSM Phone 600c A768i GSM Phone 604c A780 GSM Phone (storage) 6631 CDC Modem 6604 Washington CDMA Phone You will note that there is no entry for a732, so the model isn't recognised. Check out http://www.linux-usb.org/ for how to add a new USB identifier.
It seems that once in the hoary past I had created a device for some thing or other, back in SuSE 6x or Mandrake 4.2 era, but darned if I have any idea where to go now.
Well, if you check this: http://www.qbik.ch/usb/devices/search_res.php?pattern=motorola your phone doesn't seem to be listed - are you certain you have had this working in the past? I can't find any mention of the USB identifiers in the usb-storage module, but try loading it anyway - "modprobe usb-storage", and see what happens. When I hook up my Sony camera, I've got something like this in the dmesg output: usb 3-1: new full speed USB device using uhci_hcd and address 5 usb 3-1: new device found, idVendor=054c, idProduct=0010 usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: Sony DSC usb 3-1: Manufacturer: Sony usb 3-1: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi4 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning usbcore: registered new driver usb-storage USB Mass Storage support registered. Vendor: Sony Model: Sony DSC Rev: 2.10 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sda: 126848 512-byte hdwr sectors (65 MB) sda: assuming Write Enabled sda: assuming drive cache: write through SCSI device sda: 126848 512-byte hdwr sectors (65 MB) sda: assuming Write Enabled sda: assuming drive cache: write through sda: sda1 sd 4:0:0:0: Attached scsi removable disk sda sd 4:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete /Per Jessen, Zürich
On Thu March 23 2006 12:34 am, Per Jessen wrote:
Richard wrote:
Thanks for your response. Pertinent line from lsusb is, "Bus 001 Device 011: ID 22b8:a732 Motorola PCS". This is the correct phone so apparently it is seen on the usb bus.
Yep, so far so good. It communicates with the USB bus, and the USB database knows about it. Well, partially anyway.
From /usr/share/usb.ids:
22b8 Motorola PCS 0005 V.60c/V.60i GSM Phone 1005 T280e GSM/GPRS Phone 2821 T720 GSM Phone 2822 V.120e GSM Phone 3002 A835 GSM Phone 3802 C330/A780 GSM Phone 4002 A920/A925 UMTS Phone 4810 E398 Storage 4902 E398 GSM Phone 600c A768i GSM Phone 604c A780 GSM Phone (storage) 6631 CDC Modem 6604 Washington CDMA Phone
You will note that there is no entry for a732, so the model isn't recognised. Check out http://www.linux-usb.org/ for how to add a new USB identifier.
It seems that once in the hoary past I had created a device for some thing or other, back in SuSE 6x or Mandrake 4.2 era, but darned if I have any idea where to go now.
Well, if you check this:
http://www.qbik.ch/usb/devices/search_res.php?pattern=motorola
your phone doesn't seem to be listed - are you certain you have had this working in the past?
That was misleading. I have just gotten this phone, never had it working before. That referred to some "linux learning" I had done in the past with some other devices.
I can't find any mention of the USB identifiers in the usb-storage module, but try loading it anyway - "modprobe usb-storage", and see what happens.
No response on loading that module. I think now the phone is just not supported, hopefully, "yet". I was also unable to find it listed at tuxmobile.org last night, where there must be a dozen Motorola phones listed, but as you point out, no A732. Bummer.
When I hook up my Sony camera, I've got something like this in the dmesg output:
usb 3-1: new full speed USB device using uhci_hcd and address 5 usb 3-1: new device found, idVendor=054c, idProduct=0010 usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: Sony DSC usb 3-1: Manufacturer: Sony usb 3-1: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi4 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning usbcore: registered new driver usb-storage USB Mass Storage support registered. Vendor: Sony Model: Sony DSC Rev: 2.10 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sda: 126848 512-byte hdwr sectors (65 MB) sda: assuming Write Enabled sda: assuming drive cache: write through SCSI device sda: 126848 512-byte hdwr sectors (65 MB) sda: assuming Write Enabled sda: assuming drive cache: write through sda: sda1 sd 4:0:0:0: Attached scsi removable disk sda sd 4:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete
/Per Jessen, Zürich
I will follow your linux-usb.org link above and see what I can figure out. Thanks for your guidance. Richard
Richard wrote:
I can't find any mention of the USB identifiers in the usb-storage module, but try loading it anyway - "modprobe usb-storage", and see what happens.
No response on loading that module. I think now the phone is just not supported, hopefully, "yet". I was also unable to find it listed at tuxmobile.org last night, where there must be a dozen Motorola phones listed, but as you point out, no A732. Bummer.
Did you check the output from "dmesg"? Try unloading then reloading that module, then run "dmesg". If you're fairly certain that phone has a storage device, I think(!) it *should* report those characteristics to the USB bus, which *should* enable usb-storage to work with it. /Per Jessen, Zürich
On Thu March 23 2006 9:09 am, Per Jessen wrote:
Richard wrote:
I can't find any mention of the USB identifiers in the usb-storage module, but try loading it anyway - "modprobe usb-storage", and see what happens.
No response on loading that module. I think now the phone is just not supported, hopefully, "yet". I was also unable to find it listed at tuxmobile.org last night, where there must be a dozen Motorola phones listed, but as you point out, no A732. Bummer.
Did you check the output from "dmesg"? Try unloading then reloading that module, then run "dmesg". If you're fairly certain that phone has a storage device, I think(!) it *should* report those characteristics to the USB bus, which *should* enable usb-storage to work with it.
/Per Jessen, Zürich
Just did that and nothing more useful than before. Does there have to be a driver or file for the specific phone either in the kernel or somewhere in the distro? I assume the answer to that would be, "Well duh, yeah," that devices must be recognized rather than created on the fly. I do notice that there is no sync program of any kind nor any mention of it in the phone manual so perhaps, even though the OS of the phone is linux-based, it is not intended for access. It has programs like a calendar and so on, but makes no mention of sync-ing with a desktop for either backup or file copy or just ease of entering info into either and sync-ing with both. The phone does have Bluetooth capability and perhaps I should investigate access in that way. Time for more manual reading. Output of dmesg follows: usbcore: deregistering driver usb-storage Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usb 2-10: new full speed USB device using ohci_hcd and address 11 usb 2-10: new full speed USB device using ohci_hcd and address 12 I am taking "registered" here to mean recognize or see, rather than create a major and minor number and assign a device name for access, since those are not part of the log. Thanks for your continued interest and suggestions. Richard
Richard wrote:
Just did that and nothing more useful than before. Does there have to be a driver or file for the specific phone either in the kernel or somewhere in the distro? I assume the answer to that would be, "Well duh, yeah," that devices must be recognized rather than created on the fly.
Not quite "duh, yeah" - sometimes devices don't need specific drivers, but can be supported by drivers that support the _type_ of device.
I do notice that there is no sync program of any kind nor any mention of it in the phone manual so perhaps, even though the OS of the phone is linux-based, it is not intended for access. It has programs like a calendar and so on, but makes no mention of sync-ing with a desktop for either backup or file copy or just ease of entering info into either and sync-ing with both.
Though the fact that it has a USB interface would seem to suggest something like that.
I am taking "registered" here to mean recognize or see, rather than create a major and minor number and assign a device name for access, since those are not part of the log.
Correct - it basically means the device is working on the USB bus.
Thanks for your continued interest and suggestions.
My pleasure - these cases are always good fun. Bit of a challenge to take ones mind of things and such. I'm off to go check out the usb-storage driver. /Per Jessen, Zürich
On Fri March 24 2006 10:04 am, Per Jessen wrote:
Richard wrote:
Just did that and nothing more useful than before. Does there have to be a driver or file for the specific phone either in the kernel or somewhere in the distro? I assume the answer to that would be, "Well duh, yeah," that devices must be recognized rather than created on the fly.
Not quite "duh, yeah" - sometimes devices don't need specific drivers, but can be supported by drivers that support the _type_ of device.
I do notice that there is no sync program of any kind nor any mention of it in the phone manual so perhaps, even though the OS of the phone is linux-based, it is not intended for access. It has programs like a calendar and so on, but makes no mention of sync-ing with a desktop for either backup or file copy or just ease of entering info into either and sync-ing with both.
Though the fact that it has a USB interface would seem to suggest something like that.
I am taking "registered" here to mean recognize or see, rather than create a major and minor number and assign a device name for access, since those are not part of the log.
Correct - it basically means the device is working on the USB bus.
Thanks for your continued interest and suggestions.
My pleasure - these cases are always good fun. Bit of a challenge to take ones mind of things and such. I'm off to go check out the usb-storage driver.
I found something: had to configure the phone from USB as modem device to USB as storage, to access the micro-SD card. This seemed to work (and will probably allow me to access a card when I get one and install it) and identified the card as scsi removable device sde. Also found a generic device sg4. How do I try to access this device? Mounting does not work as it is not a block device. I have a feeling this is simple because I used to have to access a scsi scanner as a sg-generic device. Richard
Richard wrote:
I found something: had to configure the phone from USB as modem device to USB as storage, to access the micro-SD card. This seemed to work (and will probably allow me to access a card when I get one and install it) and identified the card as scsi removable device sde. Also found a generic device sg4. How do I try to access this device?
The generic device is probably some sort of control - not sure what it might be for. As an example - a tape-library usually has a generic device to controlling the loading and unloading of tapes. Your reconfiguration from modem to storage device sounds like thr right thing do to, especially as it made the card come up as sde.
Mounting does not work as it is not a block device. I have a feeling this is simple because I used to have to access a scsi scanner as a sg-generic device.
It is to do with what your phone presents as options to the USB driver. What does "lsusb" say now? /Per Jessen, Zürich
On Thu April 6 2006 12:09 am, Per Jessen wrote:
Richard wrote:
I found something: had to configure the phone from USB as modem device to USB as storage, to access the micro-SD card. This seemed to work (and will probably allow me to access a card when I get one and install it) and identified the card as scsi removable device sde. Also found a generic device sg4. How do I try to access this device?
The generic device is probably some sort of control - not sure what it might be for. As an example - a tape-library usually has a generic device to controlling the loading and unloading of tapes. Your reconfiguration from modem to storage device sounds like thr right thing do to, especially as it made the card come up as sde.
Mounting does not work as it is not a block device. I have a feeling this is simple because I used to have to access a scsi scanner as a sg-generic device.
It is to do with what your phone presents as options to the USB driver. What does "lsusb" say now?
Does not specifically identify it, or does not recognize any vendor or product ID. Output: Bus 002 Device 001: ID 0000:0000 Bus 001 Device 012: ID 5678:1050 Bus 001 Device 002: ID 041e:401c Creative Technology, Ltd WebCam NX [PD1110] Bus 001 Device 001: ID 0000:0000 Dmesg says device found at 12, so I assume the second line is the phone, but this may come back to it not being a listed device in the first place. I will probably simply have to wait until a future kernel includes the device. And perhaps this is all to the better: I am questioning whether I should have access to something I understand so little of and whether I really want to "tinker" with it anyway. I may get bitten by the "a little knowledge..." thing, a common occurrance in the past but which also often resulted in a little more knowledge. Richard
Richard wrote:
This is the correct phone so apparently it is seen on the usb bus. It seems that once in the hoary past I had created a device for some thing or other, back in SuSE 6x or Mandrake 4.2 era, but darned if I have any idea where to go now. Age is a criminal thing to inflict on the already feeble-minded.
We can tell you where to go. ;-) I also have a Motorola phone, with a USB connector. In addition to the usual cell phone sync etc., it also emulates a modem, using GPRS data.
On Thu March 23 2006 2:43 am, James Knott wrote:
Richard wrote:
This is the correct phone so apparently it is seen on the usb bus. It seems that once in the hoary past I had created a device for some thing or other, back in SuSE 6x or Mandrake 4.2 era, but darned if I have any idea where to go now. Age is a criminal thing to inflict on the already feeble-minded.
We can tell you where to go. ;-)
I also have a Motorola phone, with a USB connector. In addition to the usual cell phone sync etc., it also emulates a modem, using GPRS data.
...and you would not be the first. In fact, just last night...never mind. Looks like mine is not supported yet, or at least has no device numbers assigned to it, is not listed in supported phone lists. If this one can also emulate a modem (I think it can but would have to go back to the manual to be certain), would that allow access to file system? Seems it would not, would only allow phone to be used to pass through data, not work on it. Richard
Richard wrote:
On Thu March 23 2006 2:43 am, James Knott wrote:
Richard wrote:
This is the correct phone so apparently it is seen on the usb bus. It seems that once in the hoary past I had created a device for some thing or other, back in SuSE 6x or Mandrake 4.2 era, but darned if I have any idea where to go now. Age is a criminal thing to inflict on the already feeble-minded. We can tell you where to go. ;-)
I also have a Motorola phone, with a USB connector. In addition to the usual cell phone sync etc., it also emulates a modem, using GPRS data.
...and you would not be the first. In fact, just last night...never mind. Looks like mine is not supported yet, or at least has no device numbers assigned to it, is not listed in supported phone lists. If this one can also emulate a modem (I think it can but would have to go back to the manual to be certain), would that allow access to file system? Seems it would not, would only allow phone to be used to pass through data, not work on it.
Mine's a V180, from the business line. In addition to the modem, it's also 4 band.
On Wed, 22 Mar 2006 05:33:43 -0800, you wrote:
My new cellphone charges thru USB cable, dmesg says, "usb 1-10: new full speed USB device using ohci_hcd and address 9" when it is connected. What is this telling me about how I might access the linux file system on the phone? How do I discover the/a device name to use? Thanks for guidance to the confused.
Richard
I'm coming in late and I don't actually have an answer to your question, but I do have a cell-phone/linux oddness that might help you get a handle on the idea. I have an LG-VX4500 phone with the USB data cable. If I boot linux with the phone plugged in, it actually tries to use the phone as my boot volume. Needless to say, it doesn't work... If I plug the phone in after boot, I can use the phone as a modem with no drivers (aside from mgetty) required. It handles like a standard AT modem, at least to an extent. Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
participants (4)
-
James Knott -
Michael W Cocke -
Per Jessen -
Richard