Hi, for now, just post the contents of lsusb.

It will be much shorter and we will tell you what to do next.

Regards Glenn

Allright, here it is.

Without the stick plugged in:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 064e:a101 Suyin Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

With the stick plugged in:

Bus 002 Device 002: ID 19d2:2000
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 064e:a101 Suyin Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Thanks again for helping a girl in need

that's ok.

the system recognises that the device is connected.
Now, if you do,

lsusb -v | grep "Bus 002 Device 002"

that may reveal more info the other poster was asking about.

(grep will only display any lines with the quoted text.)

So, lsmod is next to see if a module is loaded for the device....

We'll cross reference with the output of lsusb -v above.

Your turn....

lsmod alone brings up all the modules I have installed right? That is a long list as well, but here it is:

Module Size Used by
usb_storage 82880 0
i915 65540 2
drm 96296 3 i915
binfmt_misc 16776 1
ppdev 15620 0
bridge 56340 0
stp 10500 1 bridge
bnep 20224 2
input_polldev 11912 0
joydev 18368 0
lp 17156 0
parport 42220 2 ppdev,lp
snd_hda_intel 435636 3
snd_pcm_oss 46336 0
snd_mixer_oss 22656 1 snd_pcm_oss
snd_pcm 82948 2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy 10756 0
snd_seq_oss 37760 0
snd_seq_midi 14336 0
snd_rawmidi 29696 1 snd_seq_midi
snd_seq_midi_event 15104 2 snd_seq_oss,snd_seq_midi
snd_seq 56880 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 29704 2 snd_pcm,snd_seq
arc4 9856 2
snd_seq_device 14988 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
ecb 10752 2
snd 62628 15 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_de vice
iwlagn 100228 0
psmouse 61972 0
sdhci_pci 15232 0
uvcvideo 63240 0
iwlcore 93184 1 iwlagn
acer_wmi 24260 0
serio_raw 13316 0
sdhci 23940 1 sdhci_pci
compat_ioctl32 9344 1 uvcvideo
videodev 41600 1 uvcvideo
soundcore 15200 1 snd
led_class 12036 2 iwlcore,acer_wmi
mac80211 217208 2 iwlagn,iwlcore
intel_agp 34108 1
ricoh_mmc 11904 0
v4l1_compat 21764 2 uvcvideo,videodev
iTCO_wdt 19108 0
snd_page_alloc 16904 2 snd_hda_intel,snd_pcm
pcspkr 10496 0
agpgart 42696 3 drm,intel_agp
iTCO_vendor_support 11652 1 iTCO_wdt
cfg80211 38032 3 iwlagn,iwlcore,mac80211
video 25360 0
output 11008 1 video
ohci1394 38576 0
ieee1394 94660 1 ohci1394
tg3 131204 0
fbcon 46112 0
tileblit 10752 1 fbcon
font 16384 1 fbcon
bitblit 13824 1 fbcon
softcursor 9984 1 bitblit

now the lsusb -v | grep "Bus 002 Device 002" command gave me only that

So I ran lsusb -v again, with the stick plugged in and searched for that specific device and here is what I think you are looking for:

Bus 002 Device 002: ID 19d2:2000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x19d2
idProduct 0x2000
bcdDevice 0.00
iManufacturer 2 ZTE, Incorporated
iProduct 1 ZTE CDMA Technologies MSM
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 5 SFF-8070i
bInterfaceProtocol 80
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)


Well, it sure looks like it IS detected... That's a start!

try that command as root. (sudo or su [enter password])

this is the info we need....
"usb-serial" is not listed in modules.

the "option" module is not listed in modules.

what is the kernel version.....?

uname -a

I am running all commands as root :/ and I still come up with the same:

Kernel version:
Linux guy-rene-laptop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

(Thanks for your patience)

This is a ZeroCD device...you need to first remove usb_storage kernel module to prevent it from being detected as storage...

the correct reading of lsusb should be 'ID 19d2:0001'


NB: you need USB mode switch to change ZeroCD storage to USB modem, etc.

That's OK.
<edit> Hurry_hui has a tip!
Have you tried to start the system with the modem plugged in?

I just wonder whether the kernel has a module for it, or not.

I'm not familiar with your distribution.

But the kernel is the kernel, right.

The system recognises the usb device.

Have you been able to set it up with the network-manager?

I noticed binfmt module is listed as installed, I thought it was responsible for serial conversion.

Your kernel is not too ald, but there may be a newer one that might have the modules you need.

Is it a customised kernel? Did you "make" it?

Let me know.

hurry_hui, I understand what you mean, I have read about that over at the Ubuntu forums. But if I remove that module, won't that cause problems if I have to use an actual usb storage device such as a camera, a flash drive or external HD?

Sorry, about that. I have edited my last post to include USB_modeswitch to ease [de]installation.

The serial thing is just for now.

You should be able to plug everything back in after the modem is setup.

The system keeps track via the device numbers.

so the camera and hd will have their own unique numbers.

Glenn, I got Mint fresh off a mirror last night, burned and installed it. I didn't change anything at all, except that once it was finished I got 232 updates to install.

I'm tinkering with the Network Connections as we speak. On the Mint forums someone says to try and grab the drivers from the device on a win pc.

I agree with you that the system does recognize the device, and there are two things I think I need to try to make any kind of progress.

First I will try and look on the device to see if it holds any kind of drivers. Apparently if there are I should be able to do something. BUt it looks touch and go from the posts I've read.

Second, I can go on my win partition, plug in the device and run an AT command through hyperterminal to have it detected as modem and not storage (AT+ZCDRUN=8, this command actually disables the autorun function). And then a whole lot of things, as decribed in post #8 of that thread: http://ubuntuforums.org/showthread.php?t=1065934

But I am going to try and boot with the stick plugged in right now and I will report back in a few

Phew... I have my work cut out for me :/

Oh and hurry_hui, yes usb_modeswitch I will have to try that as well.

Thank you for the tip and clarification

You are welcome...

I'll say!

the modem probably contains windows drivers, little help here I assume.

there is a wrapper, ndiswrapper, for windows drivers.