Posted: Sun Feb 05, 2012 14:43 Post subject: Using 3G modem on Asus N13U B1
I recently bought a Lava 720G 3G modem. I have been able to use it on my PC running Linux, without any problem.
I tried running it on the router but it doesn't seem to connect at all.
I searched for possible how-to's and solutions but to no avail.
Can anyone guide me on how to get started with troubleshooting?
So, after going through some troubleshooting with friends, one of whom uses the same router model, same firmware, same connection but Huawei modem and is able to connect. Thus, it seems that the problem is that my 3G modem isn't supported.
In case it helps the devs here's is the required information about the modem
Vendor id - 0x1c9e
Product id - 0x9605
Code:
# dmesg | grep -i gsm
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
<6>drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1
Code:
# dmesg | grep usb
<7>usb-storage: device scan complete
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
<6>usbcore: registered new interface driver option
<6>drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1
<4>usb 1-1: usbfs: process 1087 (usb_modeswitch) did not claim interface 0 before use
<6>usb 1-1: USB disconnect, address 2
<6>usb 1-1: new high speed USB device using dwc_otg and address 3
<6>usb 1-1: configuration #1 chosen from 1 choice
<7>usb-storage: device found at 3
<7>usb-storage: waiting for device to settle before scanning
<7>usb-storage: device scan complete
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for Sierra USB modem
<6>usbcore: registered new interface driver sierra
<6>drivers/usb/serial/sierra.c: USB Driver for Sierra Wireless USB modems: v.1.7.0
<6>usb 1-1: USB disconnect, address 3
<6>usb 1-1: new high speed USB device using dwc_otg and address 4
<6>usb 1-1: configuration #1 chosen from 1 choice
<7>usb-storage: device found at 4
<7>usb-storage: waiting for device to settle before scanning
<7>usb-storage: device scan complete
<4>usb 1-1: usbfs: process 2599 (usb_modeswitch) did not claim interface 0 before use
<6>usb 1-1: USB disconnect, address 4
<6>usb 1-1: new high speed USB device using dwc_otg and address 5
<6>usb 1-1: configuration #1 chosen from 1 choice
<7>usb-storage: device found at 5
<7>usb-storage: waiting for device to settle before scanning
<7>usb-storage: device scan complete
In case it helps the devs here's is the required information about the modem
Vendor id - 0x1c9e
Product id - 0x9605
The vendor id is for the Chinese mfgr Longcheer/Longsung
who makes "white label" sticks and Lava is one of many re-branders.
The product id 0x9605 was included in the dd-wwrt build tree only 5 days ago so your stick should be supported in the next public dd-wrt release. _________________ Kernel panic: Aiee, killing interrupt handler!
The product id 0x9605 was included in the dd-wwrt build tree only 5 days ago so your stick should be supported in the next public dd-wrt release.
It's still not supported in the latest release? I flashed build 18777 today but I am still at the same point.
The product id is supported now so it must be a driver problem.
give me the output from cat /proc/bus/usb/devices or cat /sys/kernel/debug/usb/devices
and output from dmesg.
dmesg should show the stick first being detected with vid:pid 1c9e:f000, should show that a usb_modeswitch is done to switch the stick from cd-rom mode to modem mode, and finally show that the stick is re-detected with new vid:pid 1c9e:9605.
do also give me the output from lsmod so I can see what drivers has been loaded. _________________ Kernel panic: Aiee, killing interrupt handler!
and output from dmesg.
dmesg should show the stick first being detected with vid:pid 1c9e:f000, should show that a usb_modeswitch is done to switch the stick from cd-rom mode to modem mode, and finally show that the stick is re-detected with new vid:pid 1c9e:9605.
Only new line I see added to dmesg when I plug in the USB data card is
Code:
<6>usb 1-1: new high-speed USB device number 2 using dwc_otg
LOM wrote:
do also give me the output from lsmod so I can see what drivers has been loaded.
The 3G stick should had been there also, either with its cd-rom id 1c9e:f000 or its modem id 1c9e:9605
That is only the USB controller in the router.
mehulved wrote:
Only new line I see added to dmesg when I plug in the USB data card is
Code:
<6>usb 1-1: new high-speed USB device number 2 using dwc_otg
Can you please post the complete dmesg, there is something fishy here.
Do also check if the 3G modules still gets loaded when you reboot without the modem connected, the modules are option, sierra, usb_wwan, and usbserial, they get loaded when a 3G modem is detected but shouldn't be there otherwise. _________________ Kernel panic: Aiee, killing interrupt handler!
Do also check if the 3G modules still gets loaded when you reboot without the modem connected, the modules are option, sierra, usb_wwan, and usbserial, they get loaded when a 3G modem is detected but shouldn't be there otherwise.
The output was just after the modem was booted up. I didn't load any modules manually.
Another thing I tried is running usb_modeswitch myself. Here's what I did and results I got.
Code:
# usb_modeswitch -v 1c9e -p f000
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 003 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
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: USBModem
Model String: Disk
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: USB Modem
Product: USB Modem
Serial No.: 1234567890ABCDEF
-------------------------
Warning: no switching method given.
-> Run lsusb to note any changes. Bye.
Code:
# usb_modeswitch -v 1c9e -p f000 -V 1c9e -P 9605
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 003 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("dummy")
OK, driver "dummy" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String: USBModem
Model String: Disk
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: USB Modem
Product: USB Modem
Serial No.: 1234567890ABCDEF
-------------------------
Warning: no switching method given.
-> Run lsusb to note any changes. Bye.
I am not familiar with message string. Should I be giving the same one as you provided or is there a way to find out what is required for my 3G stick?
Here's what I get when I run the command provided by you, as-is.
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 004 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
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: USBModem
Model String: Disk
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: USB Modem
Product: USB Modem
Serial No.: 1234567890ABCDEF
-------------------------
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.
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.
[/code]
This should be a successful switch (Device is gone).
cat /proc/bus/usb/devices should now show you the device with its modem id and a much longer list of interfaces then previously. _________________ Kernel panic: Aiee, killing interrupt handler!
You can probably also find the modeswitch cmd which dd-wrt should had sent out in /tmp/usb_modeswitch.conf and it should be the same one as I gave you.
If so, then you can call usb_modeswitch with a config file option instead: