LTE Modem Huawei E3276 on TL-WR842NDv2 #28647 won't connect

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Author Message
checho
DD-WRT Guru


Joined: 27 Feb 2007
Posts: 527
Location: Bulgaria

PostPosted: Sat Jan 09, 2016 12:53    Post subject: LTE Modem Huawei E3276 on TL-WR842NDv2 #28647 won't connect Reply with quote
Hello everybody,

I am trying in several days to run a LTE modem E3276 on TL-WR842NDv2 #28647 but no success yet.

That's what I have discovered:

Before modeswitch (nvram set wan_proto=static)
Code:
root@DD-WRT:~# cat /sys/kernel/debug/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 3.10
S:  Manufacturer=Linux 3.10.94 ehci_hcd
S:  Product=Atheros AR91xx built-in EHCI controller
S:  SerialNumber=platform
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=14fe Rev= 1.02
S:  Manufacturer=HUAWEI Technology
S:  Product=HUAWEI Mobile
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms


After modeswitch (nvram set wan_proto=3g)
Code:
root@DD-WRT:/proc/bus/pci# cat /sys/kernel/debug/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 3.10
S:  Manufacturer=Linux 3.10.94 ehci_hcd
S:  Product=Atheros AR91xx built-in EHCI controller
S:  SerialNumber=platform
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  7 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1506 Rev= 1.02
S:  Manufacturer=HUAWEI Technology
S:  Product=HUAWEI Mobile
C:* #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=10 Driver=option
E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=12 Driver=option
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 2 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=(none)
E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
I:  If#= 2 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=(none)
E:  Ad=84(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms



I have a strong belief that everything on modeswitch or driver level is correct. Because comgt -d does show the modem connected to its network:

Code:
root@DD-WRT:/etc/comgt# comgt -d /dev/ttyUSB0
SIM ready
Waiting for Registration..(120 sec max)
Registered on Home network: MAX 4G LTE",7
Signal Quality:31,99


3gdata is always pointing to /dev/ttySB0, but I have also tried to point it to /dev/ttyUSB1 without any success. A comgt -d gives me back the status of the network either with -d /dev/ttyUSB0 or with /dev/ttyUSB1.

However when it's wan_proto=3g it does not connect. No ppp0 is created at all. I don't know how to diagnose further.

Code:
root@DD-WRT:~# uname -a
Linux DD-WRT 3.10.94 #14516 Sat Jan 2 03:27:05 CET 2016 mips DD-WRT

root@DD-WRT:~# lsmod
Module                  Size  Used by
option                 27008  0
qmi_wwan               10096  0
usbnet                 14896  1 qmi_wwan
cdc_wdm                 7440  1 qmi_wwan
usb_wwan                4032  1 option
usbserial              16672  2 option,usb_wwan
nf_nat_h323             4576  0
nf_conntrack_h323      34112  1 nf_nat_h323
ehci_hcd               32336  0
usbcore               103008  7 option,qmi_wwan,usbnet,cdc_wdm,usb_wwan,usbserial,ehci_hcd
usb_common              1008  1 usbcore
nls_base                4656  1 usbcore
ath9k                  76672  0
ath9k_common           27424  1 ath9k
ath9k_hw              329472  2 ath9k,ath9k_common
ath                    15040  3 ath9k,ath9k_common,ath9k_hw
mac80211              292224  2 ath9k,ath9k_hw
cfg80211              197072  4 ath9k,ath9k_common,ath,mac80211
compat                 12320  5 ath9k,ath9k_common,ath9k_hw,mac80211,cfg80211
ag71xx                 22416  0


Any help would be appreciated.
Thank you.
Sponsor
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7647

PostPosted: Sat Jan 09, 2016 13:18    Post subject: Reply with quote
r25760 is the last working build for most of ppp dialup dongles.
_________________
Kernel panic: Aiee, killing interrupt handler!
checho
DD-WRT Guru


Joined: 27 Feb 2007
Posts: 527
Location: Bulgaria

PostPosted: Sat Jan 09, 2016 13:27    Post subject: Reply with quote
Unfortunately yes. I just read the ticket on the trac and tried to flash that. It immediately worked... do you know if that's being worked on for a fix?
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7647

PostPosted: Sat Jan 09, 2016 13:50    Post subject: Reply with quote
checho wrote:
Unfortunately yes. I just read the ticket on the trac and tried to flash that. It immediately worked... do you know if that's being worked on for a fix?


No, not being worked on, Brainslayer is not interested in fixing it.

_________________
Kernel panic: Aiee, killing interrupt handler!
GreyDoc
DD-WRT User


Joined: 04 Jun 2015
Posts: 392

PostPosted: Sat Jan 09, 2016 14:39    Post subject: Reply with quote
LOM wrote:
checho wrote:
Unfortunately yes. I just read the ticket on the trac and tried to flash that. It immediately worked... do you know if that's being worked on for a fix?


No, not being worked on, Brainslayer is not interested in fixing it.

is this the mentioned ticket ? http://svn.dd-wrt.com/ticket/4745 why hasn't anybody reopened it for more than 4 months ? maybe Brainslayer doesn't know that this is a problem..
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7647

PostPosted: Sat Jan 09, 2016 18:44    Post subject: Reply with quote
GreyDoc wrote:
LOM wrote:
checho wrote:
Unfortunately yes. I just read the ticket on the trac and tried to flash that. It immediately worked... do you know if that's being worked on for a fix?


No, not being worked on, Brainslayer is not interested in fixing it.

is this the mentioned ticket ? http://svn.dd-wrt.com/ticket/4745 why hasn't anybody reopened it for more than 4 months ? maybe Brainslayer doesn't know that this is a problem..


He knows.

_________________
Kernel panic: Aiee, killing interrupt handler!
GreyDoc
DD-WRT User


Joined: 04 Jun 2015
Posts: 392

PostPosted: Sat Jan 09, 2016 18:49    Post subject: Reply with quote
LOM wrote:
GreyDoc wrote:
LOM wrote:
No, not being worked on, Brainslayer is not interested in fixing it.

is this the mentioned ticket ? http://svn.dd-wrt.com/ticket/4745 why hasn't anybody reopened it for more than 4 months ? maybe Brainslayer doesn't know that this is a problem..

He knows.

how do you know? the ticket has been dormant for more than 4 months, seems like everyone forgot about it (including the developers).. I've just reopened the ticket, hopefully someone lays another eye on this issue... it would be very useful to fix it.
Slafko
DD-WRT Novice


Joined: 02 Sep 2011
Posts: 32
Location: Radenci, Slovenia

PostPosted: Sun Jan 10, 2016 11:28    Post subject: Reply with quote
Hi.

I have the same modem (E3276), however it is connected to broadcom based E4200 v1 with r26866M firmware. It works without problems.
jagster936
DD-WRT Novice


Joined: 17 Apr 2018
Posts: 36

PostPosted: Wed Apr 18, 2018 14:26    Post subject: Reply with quote
So I'm trying to use USB dongle, is this still current? last working build as mentioned above?

Thx
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum