Posted: Fri Oct 03, 2014 12:30 Post subject: DIR-868L / DWM-157 HW:B1 can't connect to Internet
Hi,
I am using latest beta on my DIR-868L (built 24461) and the DWM-157 HW:B1 as USB modem. The DIR-868L seems to detect the DWA-157, but I can't connect to Internet. I have discarded configuration problem or SIM fault, because I could make it work with other USB modems.
These are the results of cat /proc/bus/usb/devices command, in case it might help to fix the problem.
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 002 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)
USB description data (for identification)
-------------------------
Manufacturer: D-Link,Inc
Product: D-Link DWM-157
Serial No.: 536502509143130
-------------------------
Looking for active driver ...
No driver found. Either detached before or never attached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.
That doesn't look very good.
Did you take out the dongle before doing the cat cmd of devices after you had run usb_modeswitch?
Your cat of devices shows a host controller on bus 01 and it is device #1 on this bus.
usb_modeswitch finds your dongle on bus 01, device #2 and does a successful modeswitch ("Device is gone....)
Device #2 will therefore disappear from the bus and when the dongle has switched mode and reappears on the bus it should get next unused device number, it should come back as device #3.
Your cat of devices shows it as device #4 which indicates one of following two possibilities:
You replugged the dongle before doing the cat of devices
or
the usb voltage dropped right after the dongle switched mode. The voltage drop caused the dongle to reset.
If it is a matter of not enough power on the usb bus then you can try with a separately powered usb hub.
Another way of switching the dongle from install mode into usable mode is to enable usb storage in the dd-wrt gui tab for USB.
You will then see in dmesg a read-only (cd-rom) device being created, most likely sr1.
You can eject this virtual cd-rom with the cmd:
eject /dev/sr1
which actually is what usb_modeswitch does with its two cmd strings. _________________ Kernel panic: Aiee, killing interrupt handler!
keep track of the dongles device# on the bus before and after switching, it should only increment by 1.
Set your WAN type to anything but not Mobile Broadband when you run these manual cmds. We want to make sure that dd-wrt doesn't try to handle the device whih could conflict with your manual cmds.
First thing, I set WAN type to DHCP as per your suggestion, but no matter which I try of the last usb_modesswitch commands you sent me, the USB dongle always keeps on Bus=01 position (before and after executing any of the commands),
Forget about my previous post. The device# changes anytime I execute usb_modesswitch command, but none of the commands solves the issue. I mean, I can't get online using this dongle.
First thing, I set WAN type to DHCP as per your suggestion, but no matter which I try of the last usb_modesswitch commands you sent me, the USB dongle always keeps on Bus=01 position (before and after executing any of the commands)
Yes the bus number will not change, it is the device number that will change each time a new device is detected on the usb bus
Well you got it to switch from 2001:a707 (device #2)
into 2001:7d02 (device #3) and it did not fall off the bus and return as device #4 this time.
Now please unplug the dongle, plug it back, and see if it switches with the switch cmd containing 2 strings.
It should become 2001:7d02 as above, check with cat
Then unplug, plug it back, and see if it switches with the shorter switch cmd containing a single string.
Check again with cat.
I want to know why you were sucessful this time, was it due to the switch cmd?
I see from your cat of the device that you had usbstorage enabled, is that what it needs in order for the switch cmd to work? _________________ Kernel panic: Aiee, killing interrupt handler!
Sorry for being OT, I noticed that you have a rev B unit. What are the differences from rev A ? I see on dlink website that there is a different firmware for rev B, so something must be there.
Thanks for the reply. I am tempted to try the rev B fw on my
rev A, but i'm afraid i'll get myself a brick
I searched the web for any info on the rev B hardware info, no luck so far. Rev A native ipv6 is not working properly, tried all dlink firmwares i could find with no luck. I don't use ddwrt on it becouse it can't do more than 350 mbps on a pppoe gigabit connection.
Posted: Tue Nov 04, 2014 21:39 Post subject: DWM-157 HW:B1 same problem with Asus RT-AC68U
Hi,
I am having the same problem.
Asus RT-AC68U H/W:A1, DD-WRT v24-sp2 (04/22/14) std
(SVN revision 23940).
USB 3G adapter D-Link DWM-157 H/W:B1, F/W:2.0.1EU.
Adapter connects internet by ASUS F/W and also its latest Merlin version without any problems.
DDWRT is not able to make a connection, I also tried the latest beta, no success. Been re-setting to factory defaults between the FW changes.
I am using iPhone tethering at the moment on DDWRT as not been able to figure out how to connect this 3G adapter, that works perfectly.
Would like to know if I could do anything extra other than above mentioned checks?
Posted: Wed Nov 05, 2014 7:55 Post subject: Re: DWM-157 HW:B1 same problem with Asus RT-AC68U
mfineng wrote:
Hi,
I am having the same problem.
Asus RT-AC68U H/W:A1, DD-WRT v24-sp2 (04/22/14) std
(SVN revision 23940).
USB 3G adapter D-Link DWM-157 H/W:B1, F/W:2.0.1EU.
Adapter connects internet by ASUS F/W and also its latest Merlin version without any problems.
DDWRT is not able to make a connection, I also tried the latest beta, no success. Been re-setting to factory defaults between the FW changes.
I am using iPhone tethering at the moment on DDWRT as not been able to figure out how to connect this 3G adapter, that works perfectly.
Would like to know if I could do anything extra other than above mentioned checks?
Posted: Wed Nov 05, 2014 8:12 Post subject: Re: DWM-157 HW:B1 same problem with Asus RT-AC68U
mfineng wrote:
mfineng wrote:
Hi,
I am having the same problem.
Asus RT-AC68U H/W:A1, DD-WRT v24-sp2 (04/22/14) std
(SVN revision 23940).
USB 3G adapter D-Link DWM-157 H/W:B1, F/W:2.0.1EU.
Adapter connects internet by ASUS F/W and also its latest Merlin version without any problems.
DDWRT is not able to make a connection, I also tried the latest beta, no success. Been re-setting to factory defaults between the FW changes.
I am using iPhone tethering at the moment on DDWRT as not been able to figure out how to connect this 3G adapter, that works perfectly.
Would like to know if I could do anything extra other than above mentioned checks?
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)
USB description data (for identification)
-------------------------
Manufacturer: D-Link,Inc
Product: D-Link DWM-157
Serial No.: 536502509174910
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.