Posted: Thu May 02, 2013 9:44 Post subject: Can't get it working am I missing something??
Hi,
Does anyone have this LTE MF821 usb modem from telstra working with dd-wrt?
If so how do you have it configured? ie dial string, connection type, apn etc etc I've tried everything and no joy.
I've been through all the forum threads on it and I can't for the life of me work out why it doesn't work. I'm running DD-WRT v24-sp2 (04/15/13) giga - build 21286 on an Asus RT-AC66U.
I've worked out that when I plug it in, it connects in storage mode, so I found the command to fix that.
and I get this in dmesg, which I think means it's working to some extent.
sb 1-1.2: usbfs: process 17677 (usb_modeswitch) did not claim interface 0 before use
usb 1-1.2: USB disconnect, device number 6
usb 1-1.2: new high-speed USB device number 7 using ehci-pci
option 1-1.2:1.0: GSM modem (1-port) converter detected
usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
option 1-1.2:1.1: GSM modem (1-port) converter detected
usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
option 1-1.2:1.2: GSM modem (1-port) converter detected
usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
qmi_wwan 1-1.2:1.3: cdc-wdm0: USB WDM device
qmi_wwan 1-1.2:1.3 wwan0: register 'qmi_wwan' at usb-0000:00:04.1-1.2, WWAN/QMI device, 1e:79:55:c0:bc:90
I still have my old Asus RT-N56U which is running the custom asus firmware (ie not supported by dd-wrt) and the usb modem works fine on that. So I know the modem definitely works.
Any assistance would be really appreciated as tearing my hair out with this now!
You shouldn't have to do a manual modeswitch, it should be done automatically when plugging in the dongle and 3G is selected in WAN setting.
If that doesn't happen then it may be due to a recently discovered and now fixed bug for the Broadcom platform.
Your other attempts to rmmod and insmod are just plain wrong and will not get the dongle working, the option driver has bound to the right interfaces so trying to load the crappy usbserial driver is only a step backwards, it is something we used a year ago when this dongle was not supported in the option driver.
Thanks for the reply, yeah I kind of assumed from all the threads I've read and their age that it was all done and dusted a while ago. But then wasn't sure as when I plug it in it connects in storage mode, so wondered if maybe it was still a manual workaround needed.
Anyway, I'll post output tonight as soon as I get home. Can you just clarify what you mean by WAN mode set to 3G please? I have the WAN set as follows:
Mobile Broadband
dial string *99#
apn telstra.internet
auto 4g/3g/2g
Do you mean the "auto 4g/3g/2g" needs to be set to force 3g or something?
I have tried all of the settings with no joy, modem still shows up in storage mode when it is first connected.
Setup as mobile broadband with force 3g and settings as per previous post. Plugged in modem and get following results. As you can see it just connects in storage mode only.
(Below these results are the results after issuing the modeswitch command)
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 003 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached
SCSI inquiry data (for identification)
-------------------------
Vendor String: L_T_E
Model String: USB SCSI CD-ROM
Revision String: USB
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: ZTE,Incorporated
Product: ZTE LTE Technologies MSM
Serial No.: MF821_TLSS000000
-------------------------
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.
root@DD-WRT:~# dmesg
pci 0000:01:01.0: reg 10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:01:01.0: supports D1 D2
PCI: Fixing up bus 1
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
PCI/PCIe coreunit 1 is set to bus 2.
pci 0000:02:00.0: [14e4:5300] type 00 class 0x060000
pci 0000:02:00.0: reg 10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:00.0: reg 18: [mem 0x00000000-0x07ffffff 64bit]
PCI: Fixing up bridge
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.1: [14e4:0000] type 00 class 0x060000
pci 0000:02:00.1: reg 10: [mem 0x00000000-0x00003fff 64bit]
pci 0000:02:00.1: reg 18: [mem 0x00000000-0x07ffffff 64bit]
PCI: Fixing up bridge
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
pci 0000:02:00.1: supports D1 D2
pci 0000:02:01.0: [14e4:4360] type 00 class 0x028000
pci 0000:02:01.0: reg 10: [mem 0x00000000-0x00007fff 64bit]
pci 0000:02:01.0: supports D1 D2
pci 0000:02:01.0: PME# supported from D3cold
PCI: Fixing up bus 2
pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
Switching to clocksource MIPS
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
PCI: CLS 0 bytes, default 32
Asus-RT-AC66U init
bounce pool size: 64 pages
squashfs: version 3.0 (2006/03/15) Phillip Lougher
msgmni has been set to 211
alg: No test for stdrng (krng)
io scheduler noop registered (default)
HDLC line discipline maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = is a U6_16550A
serial8250: ttyS1 at MMIO 0x0 (irq = is a U6_16550A
brd: module loaded
pflash: found no supported devices
try to find cfe size up to 2097152
no filesys. assume nflash devices
bootloader size: 2097152
nvram size: 65536
Creating 3 MTD partitions on "bcmsflash":
0x000000000000-0x000000200000 : "cfe"
0x0000001f0000-0x000000200000 : "nvram"
0x0000001f0000-0x000000200000 : "nvram_cfe"
Found a Esmt NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0x92, Chip ID: 0xf1 (Eon NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65408, version 0x01
Bad block table found at page 65344, version 0x01
nand_read_bbt: bad block at 0x000007fe0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =18436096
scan filesys at 140C00
nflash: squash filesystem with lzma found at offset 0
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000000140c00-0x000002000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
Broadcom Watchdog Timer: 0.07 initialized.
GACT probability NOT on
Mirror/redirect action on
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3737 buckets, 14948 max)
nf_conntrack_rtsp v0.6.21 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.6.21 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: bic registered
TCP: cubic registered
TCP: westwood registered
TCP: highspeed registered
TCP: hybla registered
TCP: htcp registered
TCP: vegas registered
TCP: veno registered
TCP: scalable registered
TCP: lp registered
TCP: yeah registered
TCP: illinois registered
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
startup nvram driver
found nvram
found cfe nvram
VFS: Mounted root (squashfs filesystem) readonly on device 31:6.
Freeing unused kernel memory: 296k freed
et: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
et_module_init: passivemode set to 0x0
et_module_init: et_txq_thresh set to 0x0
et 0000:00:01.0: setting latency timer to 64
bcm_robo_enable_switch: EEE is disabled
et0: online cpus 1
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.30.163.2002 (r382208)
roboswitch: Probing device 'eth0'
roboswitch: trying a 53125! at eth0
roboswitch: found a 53125! at eth0
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device vlan1 left promiscuous mode
br0: port 1(vlan1) entered disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entered disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entered disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
device vlan2 entered promiscuous mode
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
br0: port 1(vlan1) entered forwarding state
ehci-pci: EHCI PCI platform driver
ehci-pci 0000:00:04.1: setting latency timer to 64
ehci-pci 0000:00:04.1: EHCI Host Controller
ehci-pci 0000:00:04.1: new USB bus registered, assigned bus number 1
ehci-pci 0000:00:04.1: irq 6, io mem 0x18004000
ehci-pci 0000:00:04.1: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
br0: port 2(eth1) entered forwarding state
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd 0000:00:04.0: setting latency timer to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:04.0: irq 6, io mem 0x18009000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-1: new high-speed USB device number 2 using ehci-pci
br0: port 3(eth2) entered forwarding state
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.2: new high-speed USB device number 3 using ehci-pci
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver cdc_wdm
usbcore: registered new interface driver qmi_wwan
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver sierra
usbserial: USB Serial support registered for Sierra USB modem
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
device vlan1 left promiscuous mode
br0: port 1(vlan1) entered disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entered disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entered disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
br0: port 1(vlan1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 3(eth2) entered forwarding state
usb 1-1.2: usbfs: process 4738 (usb_modeswitch) did not claim interface 0 before use
usb 1-1.2: USB disconnect, device number 3
usb 1-1.2: new high-speed USB device number 4 using ehci-pci
option 1-1.2:1.0: GSM modem (1-port) converter detected
usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
option 1-1.2:1.1: GSM modem (1-port) converter detected
usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
option 1-1.2:1.2: GSM modem (1-port) converter detected
usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
qmi_wwan 1-1.2:1.3: cdc-wdm0: USB WDM device
qmi_wwan 1-1.2:1.3 wwan0: register 'qmi_wwan' at usb-0000:00:04.1-1.2, WWAN/QMI device, b2:dc:5c:1b:01:b5
device vlan1 left promiscuous mode
br0: port 1(vlan1) entered disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entered disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entered disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
br0: port 1(vlan1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 3(eth2) entered forwarding state
Posted: Fri Dec 20, 2013 6:21 Post subject: Re: Not working USB modem HW with latest build
pete.magnusson wrote:
usb vendor id: 19d2
product id (vid:pid): 0166
interface list from: cat /proc/bus/usb/devices
USB modem ZTE MF880 is getting recognized but i am not getting a proper connection.
Satus > WAN > And Connect isnt working.
dmesg is showing GSM modem on 1-port driver 0.7.1.1
Anf ifconfig is going me a 169.254.255.1 ip for br0:0
Any advice is greatly appriciated!
Thanks
What router and which dd-wrt build number?
19d2:0166 is the Windows install id before the dongle is getting mode switched into a modem.
This is obviously done for you since you got the GSM modem driver loading.
Show output from cat /proc/bus/usb/devices after the dongle has switched its mode and got a new usb id. _________________ Kernel panic: Aiee, killing interrupt handler!