Activation Codes and Methods, Hardware Details, Sniffing
Post Reply
maxipad
Posts: 2
Joined: 11 Mar 2010, 23:27

ZTE AC2726

Post by maxipad » 11 Mar 2010, 23:41

Hi All-

great forum! I've got a ZTE Ac2726 and can't seem to get it working with usb-modeswitch 1.1.0.

in /etc/usb_modeswitch.conf i commented out:
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5

TargetVendor= 0x19d2
TargetProduct= 0xfff1

# only for reference and 0.x versions
MessageEndpoint=0x0a

MessageContent="5553424312345678c00000008000069f010000000000000000000000000000"



when i run sudo usb_modeswitch it seems to hang here:

Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found default devices (1)
Accessing device 002 on bus 002 ...
Using endpoints 0x0a (out) and 0x89 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached

dmesg looks like this:
[ 712.315716] usb 2-1: new full speed USB device using uhci_hcd and address 3
[ 712.479080] usb 2-1: configuration #1 chosen from 1 choice
[ 712.484957] scsi5 : SCSI emulation for USB Mass Storage devices
[ 712.487837] usb-storage: device found at 3
[ 712.487849] usb-storage: waiting for device to settle before scanning
[ 717.487977] usb-storage: device scan complete
[ 717.490977] scsi 5:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
[ 717.533895] sr0: scsi-1 drive
[ 717.534087] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 717.534180] sr 5:0:0:0: Attached scsi generic sg2 type 5

lsusb looks like this:
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 19d2:fff5
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

i am using kernel 2.6.24-22-generic, if that makes a difference.

I am stumped, any ideas on what else to check for? This model seems to be supported so I am not sure what else to look for.

Thanks for any help!

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 11 Mar 2010, 23:56

I've seen this before when the storage part (the pseudo CD-ROM) was discovered and mounted by the system. If you start the switch manually, try to unmount anything suspicious that showed up on the desktop or in a file manager.

The automatic switch did not work on your system? It usually kicks in before anything can be mounted and thus prevents any storage troubles from happening.

The old kernel has the disadvantage of not having a facility to add device IDs to the GSM modem driver. You might end up with the device switched but without a driver; unless you add your target ID to the "option" driver code in the kernel.


maxipad
Posts: 2
Joined: 11 Mar 2010, 23:27

Post by maxipad » 12 Mar 2010, 06:24

Thanks for the reply. Unfortuntely, I am using a server version so there is no desktop to unmount anything. It is an old kernel so I will try to add target id's the to the kernel. What's the best way to do that?

Just some more trial and error....when I plug the modem in and run usb_modeswitch a few times, I do get the following output, but still nothing in lsusb or dmesg:

Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found default devices (1)
Accessing device 005 on bus 002 ...
Using endpoints 0x0a (out) and 0x89 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached

SCSI inquiry data (for identification)
-------------------------
Vendor String: ZTE
Model String: USB Storage FFF1
Revision String: 2.31
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x0a ...
OK, message successfully sent
-> Run lsusb to note any changes. Bye.

Seems like there are no drivers, right?

Thanks again!

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 12 Mar 2010, 12:44

As I said, with your kernel there is only the way of adding your device ID (target) to the kernel code of the GSM modem driver ("option"); or you use the generic serial driver which is discouraged by the kernel USB developers. You can give this module ("usbserial") new device IDs as options. See output of "modinfo usbserial" for details.

Post Reply