Problem installing USB modem ZTE MF626 under openSuSE 11.1

mister_dbk · November 10, 2009, 3:49am

Hello boys & girls,

I’ve tried connecting a ZTE MF626 (HSDPA USB modem) to a Linux box (openSuSE 11.1) but quickly ran into problems. I’ve read countless forum threads on the subject in english, spanish, french and russian but every single one was designed on the same silly principle: this is what you should do and that is what should happen.

In short, none of these contributors had considered the possibility that things may not always happen the way they’re supposed to happen and that some explanation might help those in trouble. I’m therefore addressing those who know how to install such a modem and, more to the point, who could explain why I fail miserably to install it when following instructions found on various websites.

The others, whose input is limited to giving advice (do this, try that, install this, read that post, etc.) are kindly asked to stay out of this discussion. I wish to understand how to install this modem properly and why I’ve failed until now, not merely follow instructions which, for the most part, are without effect. Let’s hear it from the experts for a change.

That said, allow me to describe the problem at hand.

My understanding is that the ZTE MF626 is a dual-mode device, initially preset to function as a virtual storage device (USB virtual CD), that may be switched to function as a 3G modem.

The tool available in openSuSE to switch its mode of operation is usb_modeswitch and it’s necessary to correctly configure usb_modeswitch by editing /etc/usb_modeswitch.conf in order to provide a description of said modem. Here’s what I end up with, after commenting out the default (topmost) model and un-commenting the ZTE MF828+ entry (which I used as a compatible model, as advised on many forums):

########################################################
ZTE MF628+ (tested version from Telia / Sweden)
ZTE MF626

Contributor: Joakim Wennergren

DefaultVendor= 0x19d2
DefaultProduct= 0x2000

TargetVendor= 0x19d2
TargetProduct= 0x0031

MessageEndpoint=0x01
MessageContent=“55534243123456782000000080000c85010101180101010101000000000000”

Good. Next I plug the modem in a USB 2.0 port and wait a few seconds for the red light to appear, meaning it’s done shaking hands with Linux. To check that everything looks as it should, I run lsusb and obtain the expected output (other irrelevant entries trimmed):

Bus 004 Device 029: ID 19d2:2000 ONDA Communication S.p.A.

According to forum lore, product id 0x2000 means the device is in storage mode, as expected. Next I run usb_modeswitch in order to switch it to modem mode. This produces the following output:

- usb_modeswitch: tool for controlling “flip flop” mode USB devices
Version 0.9.5 (C) Josua Dietze 2008
Works with libusb 0.1.12 and probably other versions

Looking for target devices
No target device found
Looking for default devices
Found default devices (1)
Prepare switching, accessing latest device
Looking for active default driver to detach it
No driver found. Device probably not initialized. Trying to continue …
Setting up communication with device
Trying to send the message
OK, message successfully sent.
→ See /proc/bus/usb/devices (or call lsusb) for changes. Bye
*
Now is when things get interesting. According to the optimistic contributers on all forums attempting to deal with this issue, the next run of lsusb should show this:

Bus 004 Device 030: ID 19d2:0031 ONDA Communication S.p.A.

Well… in my case (and I’m apparently not the only one), the output is:

Bus 004 Device 030: ID 19d2:0066 ONDA Communication S.p.A.

Finally, here are my questions to the gurus out there:

What does product id 0x0066 mean?
Why does the device switch to product id 0x0066 instead of 0x0031?
What are the required steps to make it switch to product id 0x0031?

One may find a trizillion answers to question 3 in various forums, all absolutely useless as far as I’m concerned, but nobody has addressed questions 1 & 2 which, in my opinion, are key to dealing with the last one. You’ll probably want to know many details about my Linux configuration, which I haven’t provided in this post for lack of knowing what’s needed. Just ask and I shall provide it.

Many thanks in advance on behalf of all those who share the same problem.

mister_dbk · November 10, 2009, 5:48am

For those among you who pay attention to detail, you may have noticed that the output of lsusb shows Device 029 before the call to usb_modeswitch and 030 after. The device number also increments each time I unplug/replug the device. Dunno if that helps in solving the problem but rest assured it’s not there as the result of a botched cut’n paste operation.

pdc_2 · November 10, 2009, 6:10am

hi mister_dbk; sorry to hear of your problems;

you seem to be well briefed on the background; there seem to be at least two programmes to “flip” the device from CD-ROM state to USB modem state;

usbmodeswitch is one; the other is called ozerocdoff (turning off the zerocd state)

you can read about ozerocdoff and its associated forums here

HSO - Packet Driver

a vodafone group write software for linux; their VMC: vodafone mobile connect programme is a package; it contains ozerocdoff and wvdial I believe and python necessities and other things:

if it worked, it would automate the flipping of your device, and then offer you networks to log into, without needing Network Manager;

I could only suggest you install the OpenSuse specific rpm that they make available: and see if it will do all the needed stuff:

Betavine - SuSE Linux Drivers

is the link; as an rpm package, it can be cleanly removed if you do not wish it to remain;

it seems to be operator-agnostic: ie you don’t have to be with vodafone: when I installed it on your Eee (running Xandros linux) it picked up the available 3G networks for me to choose which I wanted to log into

I offer the above, as an alternative to a more protracted course

mister_dbk · November 13, 2009, 11:44pm

Thanks for the tip pdc_2. Unfortunately ozerocdoff outputs “No Zero-CD device found”, which seems to be a no-goer unless I failed to configure something. Having no crystal ball at hand for this purpose, I’ll call on those who’ve used it to provide some help, if indeed help’s needed to make ozerocdoff work correctly.

On the usb_modeswitch front, I’ve tailed /var/log/messages in the hope it would provide more info.
This is what shows up when I plug the device:

*usb 7-2: new high speed USB device using ehci_hcd and address 27
usb 7-2: configuration #1 chosen from 1 choice
usb-storage: device ignored
usb 7-2: New USB device found, idVendor=19d2, idProduct=2000
usb 7-2: New USB device strings: Mfr=2, Product=1, SerialNumber=3
usb 7-2: Product: ZTE CDMA Technologies MSM
usb 7-2: Manufacturer: ZTE,Incorporated
usb 7-2: SerialNumber: TMEP673M3MassSto

And after running usb_modeswitch:

*usb 7-2: USB disconnect, address 27
usb 7-2: new high speed USB device using ehci_hcd and address 28
usb 7-2: configuration #1 chosen from 1 choice
scsi30 : SCSI emulation for USB Mass Storage devices
usb 7-2: New USB device found, idVendor=19d2, idProduct=0066
usb 7-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 7-2: Product: ZTE CDMA Technologies MSM
usb 7-2: Manufacturer: ZTE,Incorporated
usb-storage: device found at 28
usb-storage: waiting for device to settle before scanning
scsi 30:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
sd 30:0:0:0: [sdb] Attached SCSI removable disk
sd 30:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
*

Apparently the device is disconnected, then reconnected as USB mass storage, which probably is the meaning of product id 0x0066. That’s a tiny step forward in the resolution of this problem, in that I now may (safely?) assume that 0x0066 is a valid product id and not some sentinel value (e.g. unknown or undefined product id).

“configuration #1 chosen from 1 choice” seems to indicate that the device could’ve been configured differently… which brings me to /etc/usb_modeswitch.conf. This is what it contains at present:

*########################################################

ZTE MF628+ (tested version from Telia / Sweden)

ZTE MF626

ZTE MF636 (aka “Telstra / BigPond 7.2 Mobile Card”)

Contributor: Joakim Wennergren

DefaultVendor= 0x19d2
DefaultProduct= 0x2000

TargetVendor= 0x19d2
TargetProduct= 0x0031

only for reference

MessageEndpoint=0x01

MessageContent=“55534243123456782000000080000c85010101180101010101000000000000”

if that command doesn’t work, try the other (“eject”)

;MessageContent=“5553424312345678000000000000061b000000030000000000000000000000”
*

I’ve checked /etc/usb_modeswitch.conf for an occurrence of 0x0066, just in case… there’s no such string and, besides, all other device configurations are commented out. All this is starting to make me think that usb_modeswitch does not take configuration changes into account for 2 reasons: it doesn’t acknowledge the addition of product id 0x0031 and it pulls product id 0x0066 out of a hat. Could someone provide some insight in the matter?

Don’t be shy, please. Any help, however important it may seem, would be greatly appreciated.

pdc_2 · November 14, 2009, 5:27am

welcome back; I was wondering how you were getting along; you very diligently check things out; whilst you were working on things, I did some googling on the vendor ID: Product of your modem; and all I could get was a spanish reference on Ubuntu;
the person there edited the usb_modeswitch to take into account the different product ID;

ID 19d2: 0066

Google Translate

but that didn’t seem to work for them

hope I have copied and pasted the full link

I can only suggest editing the file and entering the ID that the computer now sees: ie ID 19d2: 0066; I suggest that to try to get usb_modeswitch working

(The third way to “flip” a zeroCD device is to “eject” it issuing the command (ways 1 and 2 being ozerocdoff and usb_modeswitch)

So:

sudo eject /dev/sr0
assuming the computer sees it as sr0

(that is why there is the commented remark in the usbmodeswitch file

#* if that command doesn’t work, try the other (“eject”)*

whilst your usb_modeswitch shows a new ID, it should show a comment that does not still talk about storage device

… a working script ends …

message successfully sent; run lsusb to note any changes; bye

certainly their website

Draisberghof - Software - USB_ModeSwitch

feels it works fine: you might profit by subscribing to their website

USB_ModeSwitch ~ Index

they actively help folks

Suggestions:

see if the eject works
sudo modprobe usbserial vendor=0x19d2 product=0x0066
ls ttyUSB*

and see if any ttyUSB is present; a positive should mean you can now configure

as adapted from post #2 in this Ubuntu post

[ubuntu] Vodafone 3g dongle not working on Karmic - Ubuntu Forums]([ubuntu] Vodafone 3g dongle not working on Karmic)

By the way, which provider did you get this modem from?

mister_dbk · November 14, 2009, 7:54am

pdc_2, many thanks for your participation and suggestions.

I did some googling on the vendor ID: Product of your modem; and all I could get was a spanish reference on Ubuntu; the person there edited the usb_modeswitch.conf] to take into account the different product ID; …] but that didn’t seem to work for them.

I’ve read that post a few days ago. It is my opinion that the author was clutching at straws without a complete understanding of how that device is supposed to work. Mind you, I don’t claim full understanding either, far from it, but according to every authoritative post on the subject, the ZTE MF626 is supposed to switch to modem mode when its product id changes from 0x2000 to 0x0031. Product id 0x0066, according to the contents of /var/log/messages, merely shows its capability to function as an external storage device. It’s the fact that no website makes mention of the latter operating mode that worries me, not to mention the fact that its original product id 0x2000 is already supposed to represent such operating mode.

Sure, every “expert” posting about this device could be wrong about the target product id, particularly in the absence of serious technical specifications, but I’d need a solid argument to accept such a reversal of situation.

see if the eject works
sudo modprobe usbserial vendor=0x19d2 product=0x0066
ls ttyUSB* and see if any ttyUSB is present

Ejecting the external disk (product id 0x2000) with usb_modeswitch works flawlessly, as shown in /var/log/messages. Loading a module to handle an external disk (0x0066) is unfortunately not what I’m trying to achieve, the device already functions as such(0x2000) by default. As to any ttyUSB-like device, no such luck… usb_modeswitch doesn’t create them. But thanks for trying anyway.

Speaking of which… I had a look at the relevant rules in /etc/udev/rules.d and found something quite intriguing in 45-vmc-zte.rules, a file installed with the Vodafone-Mobile-Connect package: it mentions various product ids for this vendor but not 0x2000, 0x0031 or 0x0066. And when one’s aware that the rules contained in 45-vmc-zte.rules tell udev to call **usb_modeswitch, **it’s no wonder ozerocdoff fails to eject the device.

Another possible lead… /usr/sbin/vmc-zte.sh, a script created during the installation of VMC which does little more than call modprobe -a option, contains a cryptic comment:

“It may not use this driver if the product id is already compiled into another driver, it’s best to blacklist pl2303 and onda”
Rings a bell? Here’s the output of lsusb once the device is plugged in: Bus 004 Device 029: ID 19d2:2000 ONDA Communication S.p.A.

Does it mean that somehow, somewhere, hidden in the recesses of the kernel, some devices are blacklisted? I’ve read something about it on a forum dedicated to Ubuntu in connection to a new kernel release which seemed to directly handle hotplug devices, as opposed to letting udev do that in userspace. Sorry, I can’t place that post, having read so many on this topic in the past ten days. But perhaps someone will have some insight to share in the matter.

Indeed, I’m also clutching at straws and following every possible lead in order to determine whether this device can function as a modem under openSuSE 11.1 or, quite possibly, cannot be used as such until some future release. Ubuntu displays the same symptoms about that device: it works fine with an older version but not with one more recent, due to evolutions in the kernel. In short, I might very well be wasting your time and that device was possibly never meant to function under openSuSE 11.1. Time will tell.

By the way, which provider did you get this modem from?

Movistar, Spain. They’re infamous for their incapacity to provide any form of support, technical or emotional, whether they’d want to or not. Spain is a couple centuries behind, when it comes to computer technology, and definitely not a place to look for help. :\

As you have suggested, the correct way to handle this problem is to subscribe to the usb_modeswitch forum at Draisberghof. There I should find someone with an intimate knowledge of flippable USB devices, although there’s also the possibility that openSuSE 11.1 is to blame, hence my posting in this forum. I just wish those busy kernel developers would make their presence felt once in a while.

pdc_2 · November 14, 2009, 9:08am

thanks for this prompt reply: I felt there was a spanish connection, with the product ID;

I think your modem is different:

if you go here,

http://cateee.net/lkddb/web-lkddb/USB_SERIAL_OPTION.html

the 0066 is a recognised device, and different to the 0031: the only other post mentioning it is Ubuntu spain; and you are with a Spanish provider, so my hypothesis is that this is real: the lads in Spain have got a delivery of a different device;

it is said, that if you plug the device into a windows computer, that after the device has delivered up its windows software that it is then recognised as a usb modem;

so:

on a posting I remember seeing that one plugs the modem into a windows computer; interrogates it for the before and after of the two IDs:

seems to me the file usb_modeswitch has two specific identities: (and happy to be told I am wrong):

vendor ID product ID: and the

MessageContent=“55534243123456782000000080000c8501 0101180101010101000000000000”

that long line of numbers comes out of a windows computer; I think; if you interrogate it;

so I wonder if your modem has a different message content (with an ID of 0066) to that with an ID of 0031

so if you were asking me to construct a theory: it is that your device is slightly different from the 0031; that usb_modeswitch does not flip it correctly; (as I don’t see the message trail in your script that others get)

so I wonder about plugging it into a windows computer and interrogating for the before and after ID;

(sorry, don’t know the gui of windows to do that);

checking for differing message content script;

and beyond that, joining the usb_modeswitch forum, as those guys would be keen to get to grips with your modem;

(and beyond that: pick up a second hand Huawei E220 modem, as they are honeys and work in anything)

OpenSuse 11.2 is out; I notice its configuration for mobile broadband is different from Ubuntu: they ask you to distinguish between CDMA and GSM; and manually configure your APN etc: not as user friendly as Ubuntu); but that’s another topic, for another day

mister_dbk · November 14, 2009, 9:31am

Hey pdc_2. It looks like we’ve been reading the same post on the usb_modeswitch forum. For the benefit of those reading this thread, there are 2 potential leads:

This %#@&$£! device may require hotplugging on Windoze in order to activate its modem functionality, i.e. drivers stored on the virtual CDROM (pid 0x2000) get installed upon first plug-in.
The message content defined in /etc/usb_modeswitch.conf could be incorrect for the ZTE MF626 (since it was originally suggested for the MF628+ and later for the MF636). There’s only one way to find out, that is to sniff the dialog between OS and device under Windoze.

I’ll try to find a Windoze box over the week-end, since my 3 PCs all run under openSuSE, and will post the results. Again pdc_2, many thanks for your help, efforts, and suggestions.

pdc_2 · November 14, 2009, 9:39am

sounds like a good trail you are on to; gotta be some renegade running windows will help you; good luck; let us know how it goes

pdc_2 · November 15, 2009, 12:34am

hi mister_dbk;

we are agreed you need to flip the MF626 from CD-Rom to USB modem;

if you plug it in, does an icon appear on your desktop for it?

I guess lsusb then gives the result 19d2:2000

If you right-click on the icon; and go down to “Eject” in the options;

and then lsusb in a terminal: do you get 19d2:0066

and if you type

sudo modprobe usbserial vendor=0x19d2 product=0x0066

and then

ls ttyUSB*

what do you get?

mister_dbk · November 18, 2009, 3:42pm

Hi pdc_2. I’ve finally connected the MF626 on a PC under Windows and discovered that it is a required step for this device to function properly under Linux… Hotplugging on Windows triggers the installation of pilots stored on the USB storage (mode 0x2000). The installation process prompts for the SIM PIN and eventually activates the device.

I then plugged it on my Linux PC where it was again recognized as USB storage and, after calling usb_modeswitch, the device flipped again to CDROM mode (0x0066) but with a difference. Now, rather than emitting a steady red light as before, the MF626 shows a blinking blue light, which means that it senses the GSM network.

Unfortunately that’s all it does. Calling modprobe usbserial vendor=0x19d2 product=0x0066 (or 0x0031 for that matter) does NOT create any ttyUSB* device on /dev. There is another step missing in the various howto’s published on the web.

Since I was given that USB modem by a friend with the mission to make it work within one month (after which trial period he loses the option to return it and must enter a 1-year contract with his provider) and, after 2 weeks of constant research, was not able to flip it to modem mode, it was decided to stop wasting time and return it to his provider.

Moral of the story: do not believe what you read in forums concerning the ZTE MF626. Even the so-called “experts” forget to mention that it must first be activated under Windows. The funny thing is that they apparently performed this necessary step themselves but without realizing its importance as a pre-requisite, nor its effect on the device, and strangely omitted to mention it in their installation checklist, thus misleading readers and spreading misinformation on a grand scale.

The sad part is that, according to many posts I’ve read on the subject, users who had made the courageous effort to move to Linux have decided to go back to Windows in order to be able to use their ZTE MF626. In other words, by posting misleading articles on forums dedicated to this topic, some Linux fans have successfully acted as embassadors for Microsoft. It simply makes me sick to realize that the spreading of Linux is better sabotaged by the incapacity of its own user community to communicate than by its competition…

pdc_2 · November 19, 2009, 8:47am

thanks for your very careful documentation; sorry to hear it didn’t work out; there seem to be two different versions of the MF626, with differing product IDs

user · November 20, 2009, 12:51am

I am not an OpenSuze user, I use Ubuntu, but I have successfully set the ZTE MF626 to work with Movistar GSM in Venezuela. Still I believe that as it is the case with Ubuntu 9.10, OpenSuze 11.1 has a kernel above 2.6.30 (2.6.31 in Ubuntu 9.10). If this is the case you can forget all about usb_mode switch and modprobe, kernels 2.6.30 and above support the usb modem directly with no need of installing anything. I translate here may instructions for Movistar Venezuela, here it goes:

1- Upgrade to a Linux version with kernel equal to or above 2.6.30 (for sure it works with 2.6.31 the one I use).

2-Plug your ZTE MD626 in a USB port. After a few second a Movistar (or your SP’s) icon should appear on your desktop, the modem will show a blue light if you are in a 3 or 3.5G zone, or bright green if only EDGE (very bad luck) is available. Your modem is operatin as a pen drive now. Ignore the pen drive content completely, it is only needed unde MS Windoze.

3-Click with the right mouse switch (if you mouse is for right handed persons) an select “eject” in the pop up window. The Movistar (or your SPś provider) icon will desapear from the desktop, the blinking blue light will go off for a while and will become red and the blue again (bright green if you are an unlucky EDGE service zone user).

4- In the process you may get a popup window asking you to set your connection or you may have to open it by clicking on you NetworkManager icon. On its 1st page a window will appear with the message “ZTE Incorporated ZTE CDMA Technologies MSM” ignor it and click on “Forward”.

5-The window will change to another one where you should choose your country, “Venezuela” inm y case and now click “Forward” again.

6- e provider will be listed, mine, Movistar, is not. If you are lucky you can skip the rest of these instructions. If you are unlucky go on and click on a smal button which selects other options besides “I can’t find my provider and I wish to enter my provider manually” and write your SP in the small window that becomes active marked “Provider” something like “Movistar” and go to the next page.

7- In the small window refering to the “APN (Access point name)” I wrote “mms.movistar.com.ve” you will have to find yours. Go to the next page.

8- go to the next page or click the right mouse button on on the NetworkManager icon on you panel, and select “Edit Connections” and “Mobile Broadband”, then “Movistar” (or whatever you called your SP above) and “Edit”. In the widow that opens add after *99# your MODEM’s PHONE NUMBER, it looks like *99#+58414ddddddd in my case (58 is Venezuelas’s code, 414 is my SP’s code and ddddddd replaces the las 7 digits of my modem), in the USA it probably will be like *99#+1cccddddddd where ccc is your SP code.

9- In the same window (the following works for Movistar, it may change between countries and SPs you will have to find out yours, sorry) click “IPv4 Settings” and in “Method” change “Automatic (PPP) address only”. And finally on the window which activates) labeled “DNS servers” I wrote “200.35.65.3, 200.35.65.4”, the IP numbers of my provirer’s dns servers.

10- After a few seconds in the NetworkManager’s icon you will be able to select “Movistar” (or whatever) and on a 3 or 3.5G zone the ZTE will be yellow-green (or bright green if you are unlucky) and you will be on line.

The next time you onli will need to repeat steps 2, 3 and 10 to navigate. Good luck.

brigs · November 20, 2009, 5:02am

hi mister_dbk…

i have some problem too to configure work in zte ac2726 cdma evdo, rightnow i’m using the new suse 11.2 for my device.

the first plugin and lsusb tell…

Bus 003 Device 005: ID 19d2:fff5 ONDA Communication S.p.A.

My device recognize as cd-rom device

After googling, i found the way from ubuntu user
Google Translate He tell to use usb_modeswitch to flip device to usb serial modem mode. But unfortunetely his advise don’t work in opensuse cause the device doesn’t make node in /dev/ttyUSB* for wvdial dialup.

There is dmesg log


  873.881009] usb 3-1: new full speed USB device using ohci_hcd and address 5
  874.073967] usb 3-1: New USB device found, idVendor=19d2, idProduct=fff5
  874.073980] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  874.073986] usb 3-1: Product: USB Storage
  874.073990] usb 3-1: Manufacturer: ZTE, Incorporated
  874.073994] usb 3-1: SerialNumber: 000000000002
  874.074401] usb 3-1: configuration #1 chosen from 1 choice
  874.077168] scsi9 : SCSI emulation for USB Mass Storage devices
  874.077332] usb-storage: device found at 5
  874.077334] usb-storage: waiting for device to settle before scanning
  875.085958] scsi 9:0:0:0: CD-ROM            ZTE      USB Storage FFF1 2.31 PQ: 0 ANSI: 2
  875.153960] sr2: scsi-1 drive
  875.154737] sr 9:0:0:0: Attached scsi CD-ROM sr2
  875.155973] sr 9:0:0:0: Attached scsi generic sg4 type 5
  875.157081] usb-storage: device scan complete
  878.254877] sr2: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00
  878.254897] sr: Sense Key : Hardware Error [current] 
  878.254903] sr: Add. Sense: No additional sense information
  878.547868] sr2: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00
  878.547889] sr: Sense Key : Hardware Error [current] 
  878.547895] sr: Add. Sense: No additional sense information
  938.861018] usb 3-1: reset full speed USB device using ohci_hcd and address 5
  939.514316] sr2: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00
  939.514336] sr: Sense Key : Hardware Error [current] 
  939.514341] sr: Add. Sense: No additional sense information
  939.788294] sr2: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00
  939.788315] sr: Sense Key : Hardware Error [current] 
  939.788320] sr: Add. Sense: No additional sense information
  939.880290] sr2: CDROM (ioctl) error, command: Get configuration 46 00 00 28 00 00 00 00 10 00
  939.880309] sr: Sense Key : Hardware Error [current] 
  939.880315] sr: Add. Sense: No additional sense information
  939.972285] sr2: CDROM (ioctl) error, command: Get configuration 46 00 00 20 00 00 00 00 18 00
  939.972297] sr: Sense Key : Hardware Error [current] 
  939.972302] sr: Add. Sense: No additional sense information
  940.094289] sr2: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00
  940.094310] sr: Sense Key : Hardware Error [current] 
  940.094315] sr: Add. Sense: No additional sense information
  940.112282] ISO 9660 Extensions: Microsoft Joliet Level 3
  940.120284] ISOFS: changing to secondary root

Why i must choose jaunty for my distro ? i love opensuse so well. Anyone can help me to fix it ?

pdc_2 · November 20, 2009, 9:01am

so you:

installed usb_modeswitch and
edited the /etc/usb_modeswitch.conf file to uncomment the reference to your zte device?

the default file has this entry

ZTE AC8710

Two ID variants known; check your default

Contributor: Michael Khurtsiya

;DefaultVendor= 0x19d2
;DefaultProduct= 0xfff5

;TargetVendor= 0x19d2
;TargetProduct= 0xffff

No. 2

;DefaultVendor= 0x19d2
;DefaultProduct= 0xfff6

;TargetVendor= 0x19d2
;TargetProduct= 0xfff1

only for reference and 0.x versions

MessageEndpoint=0x05

;MessageContent=“5553424312345678c00000008000069f030000000000000000000000000000”

########################################################

ZTE AC2710 (EVDO)

Contributor: Wasim Baig

;DefaultVendor= 0x19d2
;DefaultProduct= 0xfff5

;TargetVendor= 0x19d2
;TargetProduct= 0xffff

;MessageContent=“5553424312345678c00000008000069f010000000000000000000000000000”

Just for information: try it with the message from the AC8710 …

so the default CD-ROM entry covers a couple of devices; yours is not listed but may be covered

if you are using 11.2; and you insert your modem; and get an icon on the desktop; and you then right-click on the icon; select “eject” and you will get a new window opening with a device of about 125M?? If you close that window, and instead open a terminal, and type

lsusb

what new numbers do you get for the modem please?

… hopefully it is 0xffff

brigs · November 21, 2009, 2:46am

Thanks for reply pdc2, my edited usb_modeswitch.conf is…


########################################################
# /etc/usb_modeswitch.conf
#
# Smart ZTE AC2726 (EVDO) 
#

DefaultVendor=  0x19d2
DefaultProduct= 0xfff5

TargetVendor=   0x19d2
TargetProduct=  0xfff1

MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"

and with 2710 config from yours


################################################## ######
# ZTE AC2710 (EVDO)
#
# Contributor: Wasim Baig

DefaultVendor= 0x19d2
DefaultProduct= 0xfff5

TargetVendor= 0x19d2
TargetProduct= 0xffff

MessageContent="5553424312345678c00000008000069f0 10000000000000000000000000000"

# Just for information: try it with the message from the AC8710 ...

The result was same, icon cdrom appears in my desktop and when i ejected the device, popup message “can’t ejected device…bla. invalid argument”

my lsusb output is same with before, 0xfff5.

I heard about kernel patch for fixing recognize ac2726 cdma modem… [006/136] USB: option.c Add support for ZTE AC2726 EVDO modem - Patchwork](http://patchwork.kernel.org/patch/51269/)

How to patching step those kernel ?

brigs · November 22, 2009, 2:45pm

problem solved…
just installing new usb_modeswitch newer than repository stock. The problem was from usb_modeswitch itself. The newer revision can handle this cdma modem.

pdc_2 · November 24, 2009, 8:55am

thanks;

which version did you install?

lemperkeju · February 11, 2010, 10:55pm

hi mister_dbk…

i have some problem too to configure work in zte ac2726 cdma evdo, rightnow i’m using the new suse 11.2 for my device.

I did have same problem with you here with AC2726, the usual method have never worked for this device (usb_modeswitch method).

I’ll try repeat the steps I’ve done to make this device working smoothly. But, please, do not follow my instructions blindly, make sure you know what each instruction is, and the risk they could do to your box.

Okay. First, you’ll need the following:

Kernel-development package (source, syms, make, etc.)
Support Software from zte, download it here ZTEMT-Download. It’s BNSL Dialer 8700 for linux.
libaudio2, you’ll find it at packman repository.
Coffee…

While spending my nightly coffee, I found ZTE site, there you can find support software for the device. Here’s the link ZTEMT-Download. Make sure you download the correct app, it’s “BSNL 8700 Dialer for linux”.

It’ll be named some kind like 1257081294661.zip. Extract the contents, you’ll find bunchs of rpm including opensuse package :). But before you install this package, you’ll need kernel-source and kernel-syms package for your running kernel (default is “2.6.31.5-0.1-default”), because we’ll do some module compiling here.

Okay, now get some coffee, we’ll get down to business soon. First, install the package with this rpm:

rpm -ivh CrossPlatformUI-V1.0.27-BSNL-i586-openSUSE103.rpm

You should have error message there (at time I wrote this, the rpm still need some tweaking) while the module is being built.
Now, we’ll build the module manually. Go to the module source location, and build the module:


$ cd /usr/local/bin/ztemtApp/zteusbserial/2.6.31/
$ su
Password:
# make -C /lib/modules/$(uname -r)/build M=$(pwd)

You should have no problem here. When the build finish, install the module:


# make -C /lib/modules/$(uname -r)/build M=$(pwd) modules_install

Done, we got the driver installed. Now, plug your AC2726 and pray. Go to menu->Application->Internet->More Programs->ZTEMT UI. Well, the interface looks familiar huh. Fill in your dial number, username, and password. Enjoy.

That’s all, good luck brother.

zeduardu · July 29, 2010, 9:56am

I’m using OpenSuse 11.2 and had the same problem. Just installed the “usb_modeswitch” from the repository and then immediately reboot my machine. Pronto! Enough to detect and work perfectly.