| Author |
Message |
< Device Information ~ LTE4G ZTE MF821D 2G/3G/4G surfstick (O2/telefonica germany) |
|
thomasschaefer
|
Posted: Sat Jul 07, 2012 3:29 pm |
|
|
| Posts: 33Joined: Sun Jul 17, 2011 12:08 pm
|
Since this week O2 is selling an new surfstick.
It has the IDs 19d2:0325 and 19d2:0326.
The ID change is easy made by "eject /dev/sr0" , but I don't know at the moment how to automate this. May be somebody gives me a hint for the right FAQ.
The working ID is 19d2:0326.
The linux-kernel does not know the ID yet, but the option-driver works.
modprobe option
echo "19d2 0326" > /sys/bus/usb-serial/drivers/option1/new_id
After that you can use /dev/ttyUSB2 as serialmodem, at least for 2G and 3G-connections.
At windows this modem provides also an ndis-mode, may be we get it in linux too. (for better performance, 4G and hopefully IPv6-capable)
Regards,
Thomas
|
|
Top
|
|
|
thomasschaefer
|
Posted: Sun Jul 08, 2012 11:56 am |
|
|
| Posts: 33Joined: Sun Jul 17, 2011 12:08 pm
|
UsbSnoop is a fine tool.
/lib/udev/rules.d/40-usb_modeswitch.rules
Code: # ZTE MF821DO2 ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0325", RUN+="usb_modeswitch '%b/%k'"
/usr/share/usb_modeswitch/19d2:0325 Code: # ZTE MF821DO2
DefaultVendor= 0x19d2 DefaultProduct= 0x0325
TargetVendor= 0x12d1 TargetProduct= 0x0326
MessageContent="5553424302000000000000000000061b000000020000000000000000000000"
The result is the same as with "eject /dev/srX" .
Thomas
|
|
Top
|
|
|
Josh
|
Posted: Sun Jul 08, 2012 9:26 pm |
|
|
| Site AdminPosts: 3686Joined: Sat Nov 03, 2007 12:30 am
|
Thanks a lot!
The MessageContent you posted is essentially the SCSI "eject" command. In fact, many modems may also be mode-switched with the "eject" tool. The downside is that it expects a fully discovered storage device, ready to be mounted in Linux. usb_modeswitch does not have to wait for that and will also prevent any automatic mounting of the "pseudo CD-ROM" containing the Windows software.
One more thing: could you post the full output of "lsusb -v -d 19d2:0326" (preferably formatted as "Code")? I would like to have a look at the interface structure ...
Thanks again!
|
|
Top
|
|
|
thomasschaefer
|
Posted: Sun Jul 08, 2012 9:45 pm |
|
|
| Posts: 33Joined: Sun Jul 17, 2011 12:08 pm
|
Josh wrote: The MessageContent you posted is essentially the SCSI "eject" command.
I was so happy to find a working sequence and now it was only the normal SCSI "eject". Josh wrote: One more thing: could you post the full output of "lsusb -v -d 19d2:0326" (preferably formatted as "Code")? I would like to have a look at the interface structure ...
Here it is:
http://www.spinics.net/lists/linux-usb/msg66855.html
Code: Bus 001 Device 003: ID 19d2:0326 ONDA Communication S.p.A. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x19d2 ONDA Communication S.p.A. idProduct 0x0326 bcdDevice 0.00 iManufacturer 3 ZTE,Corporated iProduct 2 ZTE LTE Technologies MSM iSerial 4 MF821DO2_S020000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 161 bNumInterfaces 6 bConfigurationValue 1 iConfiguration 1 ZTE Configuration bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 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 32 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 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 3 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 4 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x87 EP 7 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 5 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x06 EP 6 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 0x88 EP 8 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)
Regards,
Thomas
|
|
Top
|
|
|
lingxyy
|
Posted: Tue Aug 21, 2012 3:33 am |
|
|
| Posts: 1Joined: Tue Aug 21, 2012 3:26 am
|
What's the difference between MF820D and ZTE MF821D? I have a MF820D which is also a 4G LTE Stick
|
|
Top
|
|
|
thomasschaefer
|
Posted: Tue Aug 21, 2012 8:36 am |
|
|
| Posts: 33Joined: Sun Jul 17, 2011 12:08 pm
|
lingxyy wrote: What's the difference between MF820D and ZTE MF821D? I have a MF820D which is also a 4G LTE Stick
Different ID? Different Device? I don't own a MF820D.
|
|
Top
|
|
|
|