Hi!
I installed OpenSUSE 11.3 64 bit version on my Dell Laptop Studio XPS 16. My USB mouse is working nicely. However, as I inserted MTS USB MODEM, I found that device is not mounted. “dmesg” shows USB modem in sdb emulating as scsi10 drive. I tried with 'fdisk -l" which does not show the device. ‘lsusb’ shows the device ID. Itried to mount /dev/sdb to /media/disk after creating a directory /media/disk, but of no use. Please suggest me how to handle it.
Thanks
Hi there,
maybe you could post the dmesg and lsusb output here?
vegaonline wrote:
> Hi!
>
> I inserted MTS USB MODEM, I found that device is not mounted.
i believe disks and other storage devices must be mounted to be
used…modems are not mounted, but rather HAL will see them and
“connect” it to the system as a modem… (if the MTS brand presents
itself as a modem…that, i don’t know)
once inserted you should be able to open YaST go > network devices >
modem and configure it…if not some of these may help
http://www.google.com/search?q=site%3Aopensuse.org+“usb+modem”
additionally, you will probably find some useful information on your
carrier’s web site…
or, maybe search for Linux wide (outside opensuse.org) info, like:
http://www.google.com/search?q=linux+“MTS+usb+modem”
CAREFUL if you try to follow (say) *buntu directions directly you will
probably have a lot of trouble if you run across an “apt get”
command…and, i’d suggest you read a wide variety of found posts to
get the flavor of the solution prior to beginning…
if none of those help i suggest you post again to the “wireless” forum
after you have worked carefully through the three stickies at the top
of: http://forums.opensuse.org/english/get-help-here/wireless/
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
Why do you think a modem can be mounted? Mounting is an action to make a mass storage device available somewhere inside the one and only directory tree (starting at /) so that all the directories and files can be used as such. What files do you think that are on the modem to be accessed from /media/whatever (or any other place inside your mass storage).
A modem is NOT a mass storage device (as are sound cards, key boards, printers, etc). When you want to use such a device try the applicable section of YaST.
Firstly, I like to reply to Henk’s question. Basically MTS USB modem has advantage that it is also a USB storage device beside MODEM. It would be clear in later part of my reply.
Next, Johest, I am pasting here the following info.
A. “hal-device” command in root prompt:
0: udi = ‘/org/freedesktop/Hal/devices/storage_serial_ZTE_USB_Storage_FFF1_0_0’
linux.hotplug_type = 3 (0x3) (int)
storage.partitioning_scheme = ‘’ (string)
info.interfaces = { ‘org.freedesktop.Hal.Device.Storage.Removable’ } (string list)
info.product = ‘USB Storage FFF1’ (string)
info.udi = ‘/org/freedesktop/Hal/devices/storage_serial_ZTE_USB_Storage_FFF1_0_0’ (string)
block.device = ‘/dev/sdb’ (string)
block.major = 8 (0x8) (int)
block.minor = 16 (0x10) (int)
block.is_volume = false (bool)
storage.bus = ‘usb’ (string)
storage.no_partitions_hint = false (bool)
storage.media_check_enabled = true (bool)
storage.automount_enabled_hint = true (bool)
storage.drive_type = ‘disk’ (string)
storage.model = ‘USB Storage FFF1’ (string)
storage.vendor = ‘ZTE’ (string)
storage.serial = ‘ZTE_USB_Storage_FFF1-0:0’ (string)
block.storage_device = ‘/org/freedesktop/Hal/devices/storage_serial_ZTE_USB_Storage_FFF1_0_0’ (string)
storage.firmware_version = ‘2.31’ (string)
storage.originating_device = ‘/org/freedesktop/Hal/devices/usb_device_19d2_fff1_noserial_if5’ (string)
storage.removable.media_available = false (bool)
storage.removable = true (bool)
storage.size = 0 (0x0) (uint64)
storage.hotpluggable = true (bool)
storage.requires_eject = false (bool)
storage.removable.support_async_notification = false (bool)
storage.lun = 0 (0x0) (int)
info.addons = { ‘hald-addon-storage’ } (string list)
linux.sysfs_path = ‘/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.5/host6/target6:0:0/6:0:0:0/block/sdb’ (string)
info.parent = ‘/org/freedesktop/Hal/devices/usb_device_19d2_fff1_noserial_if5_scsi_host_0_scsi_device_lun0’ (string)
info.category = ‘storage’ (string)
info.capabilities = { ‘storage’, ‘block’ } (string list)
info.vendor = ‘ZTE’ (string)
I have only pasted concerned info. It clears doubt why I need to mount storage. Beside this the device contains installation RPM for use in SUSE linux.
Next I am inserting dmesg info:
1528.364849] usb 2-1.2: new full speed USB device using ehci_hcd and address 10
1528.458444] usb 2-1.2: New USB device found, idVendor=19d2, idProduct=fff5
1528.458451] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
1528.458456] usb 2-1.2: Product: USB Storage
1528.458459] usb 2-1.2: Manufacturer: ZTE, Incorporated
1528.458463] usb 2-1.2: SerialNumber: 000000000002
1528.459262] scsi7 : usb-storage 2-1.2:1.0
1529.186995] usb 2-1.2: USB disconnect, address 10
1530.410773] usb 2-1.2: new full speed USB device using ehci_hcd and address 11
1530.505382] usb 2-1.2: New USB device found, idVendor=19d2, idProduct=fff1
1530.505389] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
1530.505394] usb 2-1.2: Product: ZTE CDMA Tech
1530.505397] usb 2-1.2: Manufacturer: ZTE, Incorporated
1530.506425] option 2-1.2:1.0: GSM modem (1-port) converter detected
1530.506561] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
1530.506985] option 2-1.2:1.1: GSM modem (1-port) converter detected
1530.507113] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB1
1530.507619] option 2-1.2:1.2: GSM modem (1-port) converter detected
1530.507733] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB2
1530.508107] option 2-1.2:1.3: GSM modem (1-port) converter detected
1530.508213] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB3
1530.508598] option 2-1.2:1.4: GSM modem (1-port) converter detected
1530.508709] usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB4
1530.509048] scsi8 : usb-storage 2-1.2:1.5
1531.509840] scsi 8:0:0:0: Direct-Access ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
1531.510004] sd 8:0:0:0: Attached scsi generic sg2 type 0
1531.515945] sd 8:0:0:0: [sdb] Attached SCSI removable disk
This clearly shows existence of modem and disk.
Now lastly I am pasting the info obtained from “lsusb”:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020
Bus 001 Device 003: ID 0c45:640f Microdia
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0020
Bus 002 Device 003: ID 04fc:0538 Sunplus Technology Co., Ltd
Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick
Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card
Bus 002 Device 009: ID 19d2:fff1 ONDA Communication S.p.A.
Here 19d2:fff1 is the required USB device.
I hope I have established valid points to consider MTS USB MODEM as a storage device too. I tried with /dev/modem, but in vain.
“This clearly shows existence of modem and disk.” Yes it does. But when you say it is a modem, I assume you mean modem. When it is two devices, why don’t you say so? And no, the disk part of the device will not be usable via /dev/modem. May be the modem part is.
With the device attached can you show the output of
fdisk -l
And please put computer output between CODE tags (Go Advanced for the reply and use the # button in the toolbar) to keep it readable.
You could also look in the several* /dev/disk/by-** directories if you find a name associated with the device.
Hi again,
so first of all, the disk, as dmesg shows there is a disk device.
You should see it via cfdisk /dev/sdb but you will not be able to mount sdb. Is there any partition? So any /dev/sdbX (X=[1…9])? This would be a volume you can mount.
After that, i can see that there are several USB tty devices.
You should be able to connect to this devices with ans software that supports your device or for any kind of testing the terminal program minicom should be able to connect to the device and send commands to it.
Everything is just a hint 
vegaonline wrote:
> Firstly, I like to reply to Henk’s question. Basically MTS USB modem has
> advantage that it is also a USB storage device beside MODEM. It would be
> clear in later part of my reply.
would have nice if you had told us that the first time you posted…
because it remains impossible to ‘mount’ a modem…
> I hope I have established valid points to consider MTS USB MODEM as a
> storage device too. I tried with /dev/modem, but in vain.
then you have to mount the storage device and connect to the modem
through the same, single USB port…personally i have no idea how you
are gonna do both of those things at the same time…
i’m not sure, but you may have bought a device usable only with a
driver made only for MS-Windows to do both of those things at the
same time…
however, you might be able to use it in Linux as a connected modem
OR as a mounted storage device…then disconnect it (correctly, not
just pull it out) and reinsert it and use it as the other device…
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
sudo fdisk -l
root's password:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb8000000
Device Boot Start End Blocks Id System
/dev/sda1 1 17 136521 de Dell Utility
/dev/sda2 18 1272 10078208 7 HPFS/NTFS
/dev/sda3 1272 31471 242568192 7 HPFS/NTFS
/dev/sda4 * 31472 60801 235593225 f W95 Ext'd (LBA)
/dev/sda5 31472 31536 522081 82 Linux swap / Solaris
/dev/sda6 31537 35452 31455238+ 83 Linux
/dev/sda7 35453 39392 31648018+ 83 Linux
/dev/sda8 39393 42132 22009018+ 83 Linux
/dev/sda9 42133 52575 83883366 83 Linux
/dev/sda10 52576 60801 66073600 7 HPFS/NTFS
This is the usual fdisk info. The manual of this MTS USB modem has linux part where it asks to install one RPM file stored in the storage space. The modem can by default store 2 GB data while it has another micro SD card socket to put extra storage space.
The fdisk output shows that udev did not generate any device files for the new disk device. You having “normally” only one disk (/dev/sda) it should have show as /dev/sdb.
The strange thing here is that you HAL output shows that it is about sdb.
Are you still looking at* /dev/disk/by-**? Because I asked, but you did not report until now. To make it easy, do
ls -l /dev/disk/by*
You could also give the output of
ls -l /dev/sd*
to make sure if sdb is there or not.
Henk, I am sorry and grateful for your concern to this problem.
ls -l /dev/disk/by*
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root 9 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF -> ../../sda
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part10 -> ../../sda10
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 ata-ST9500325AS_5VE8RKKF-part9 -> ../../sda9
lrwxrwxrwx 1 root root 9 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF -> ../../sda
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part10 -> ../../sda10
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 scsi-SATA_ST9500325AS_5VE8RKKF-part9 -> ../../sda9
lrwxrwxrwx 1 root root 9 2010-07-30 00:28 usb-ZTE_USB_Storage_FFF1-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 2010-07-30 00:21 wwn-0x5000c50020b19f70 -> ../../sda
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 2010-07-30 00:21 wwn-0x5000c50020b19f70-part10 -> ../../sda10
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 wwn-0x5000c50020b19f70-part9 -> ../../sda9
/dev/disk/by-label:
total 0
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 DellUtility -> ../../sda1
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 OS -> ../../sda3
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 RECOVERY -> ../../sda2
lrwxrwxrwx 1 root root 11 2010-07-30 00:21 Store -> ../../sda10
/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 9 2010-07-30 00:28 pci-0000:00:1d.0-usb-0:1.2:1.5-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part10 -> ../../sda10
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 pci-0000:00:1f.2-scsi-0:0:0:0-part9 -> ../../sda9
lrwxrwxrwx 1 root root 9 2010-07-30 00:21 pci-0000:00:1f.2-scsi-1:0:0:0 -> ../../sr0
/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 06b7870e-4558-4452-9c97-d53712dc443f -> ../../sda8
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 07DA-0213 -> ../../sda1
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 0C6046C26046B26E -> ../../sda3
lrwxrwxrwx 1 root root 11 2010-07-30 00:21 0EEAC01DEAC00347 -> ../../sda10
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 463C42F83C42E293 -> ../../sda2
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 916b3165-10ba-4f3c-bbbd-167b7f8943a4 -> ../../sda5
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 c1cbabe1-1bbb-4bfe-8b85-db939f9d8b62 -> ../../sda7
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 e95c4264-cc9a-4460-84f8-3bb6441f6e62 -> ../../sda6
lrwxrwxrwx 1 root root 10 2010-07-30 00:21 f3bf1848-efde-4d14-9f38-4243cbabbdcf -> ../../sda9
And
ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 2010-07-30 00:21 /dev/sda
brw-rw---- 1 root disk 8, 1 2010-07-30 00:21 /dev/sda1
brw-rw---- 1 root disk 8, 10 2010-07-30 00:21 /dev/sda10
brw-rw---- 1 root disk 8, 2 2010-07-30 00:21 /dev/sda2
brw-rw---- 1 root disk 8, 3 2010-07-30 00:21 /dev/sda3
brw-rw---- 1 root disk 8, 4 2010-07-30 00:21 /dev/sda4
brw-rw---- 1 root disk 8, 5 2010-07-30 00:21 /dev/sda5
brw-rw---- 1 root disk 8, 6 2010-07-30 00:21 /dev/sda6
brw-rw---- 1 root disk 8, 7 2010-07-30 00:21 /dev/sda7
brw-rw---- 1 root disk 8, 8 2010-07-30 00:21 /dev/sda8
brw-rw---- 1 root disk 8, 9 2010-07-30 00:21 /dev/sda9
brw-rw---- 1 root disk 8, 16 2010-07-30 00:28 /dev/sdb
Thanks for all the output! It is illuminating!
What we see is that the kernel detected the mass storage device (as you allready showed in the logging output) and udev created a device file for it and the related ones :
/dev/sdb
/dev/disk-by-id/usb-ZTE_USB_Storage_FFF1-0:0 -> ../../sdb
(only in the* by-id*, that is not much).
BUT we also see that no device files for partitions were created (that should have been /dev/sda1, etc. and the related* /dev/disk/by-** entries). That means that there is no partition table. Now while partitioned disk are by far the majority in such a majority that many people think a disk must be partitioned, this is not the case. Thus it could be that there is a file system on the whole disk. We do not know which type of file system, but we can guess that it is a MS type like VFAT or NTFS. The mount command is usualy able to detect that. Thus we can try the following as root:
cd /mnt
mkdir sillymts
mount /dev/sdb sillymts
Look for any errors (and report back here). When no errors, you can do
ls -l sillymts
to see if there is something there.
Please try, I am very curious (but nevertheless will go sleeping in about an hour 
)
I tried this option already but in vain. However, again I am posting the result
mount /dev/sdb SillyMTS
mount: /dev/sdb: unknown device
Neither I am able to see the disk content nor I am able to use MODEM. By the by, I tested with Windows 7 Pro again and found it working nicely as modem. Thanks
We were only discussing the mass storage device. Not the modem, which is a complete different device with complete different way of working. Let not lure you by the fact that both device are in the same case. They are different things.
The error is a strange one. But alas, eeror messages are not often very good from ancient tools like mount. HHm, I am a bit out of ideas. Sorry about that. The only think I would think here is that the device is not containing something “understandable”.
You might find some of interest and use here:
Draisberghof - Software - USB_ModeSwitch
You could try this for example:
Some ZTE devices can be switched by issueing the "eject" command to the "CD-ROM" device as well.
Please read the last paragraph in Troubleshooting!
Just as a hint again,
/dev/sdb in this case is the whole medium which cant be mounted,
there must be partition sets such as sdb1 as hcvv already told.
This partitions could be mounted the way you want.
As you could have seen from the above listiings of /dev/sd*, there is no /dev/sdb1 (or any other partition number), thus your advice has no value.
And I did not say that a whole device can not be mounted. I did say it is possible to create a file system on a whole, unpartitioned device (though this is not common usage). And when that is the case, it is possible to mount it.
Please read carefully. else we are running in circles and that is not to the benifit of anybody.
@vegaonline: hank_se’s link looks as a promising start to me. From your description it seems to me tthat you have such a device. And, as usual, the maker did not bother to make it for anybody else but MS adicted.