Using 3G modem on Asus N13U B1

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
mehulved
DD-WRT Novice


Joined: 17 Dec 2008
Posts: 26

PostPosted: Sat Mar 24, 2012 18:21    Post subject: Reply with quote
Tried again with the new message content. Still the same result.

Code:

# usb_modeswitch -v 0x1c9e -p 0xf000 -V 0x1c9e -P 0x9605 -M "55534243123456788000000080000606f50402
527000000000000000000000"

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 007 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.

root@DD-WRT:~# cat /proc/bus/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=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 3.02
S:  Manufacturer=Linux 3.2.12-rc1-svn18774 dwc_otg_hcd
S:  Product=DWC OTG Controller
S:  SerialNumber=lm0
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=1c9e ProdID=f000 Rev= 0.00
S:  Manufacturer=USB Modem
S:  Product=USB Modem
S:  SerialNumber=1234567890ABCDEF
C:* #Ifs= 1 Cfg#= 1 Atr=e0 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
Sponsor
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7165

PostPosted: Sat Mar 24, 2012 18:35    Post subject: Reply with quote
Ok, I have already opened a bug ticket about 3G problem on 18777 so this is something Brainslayer has to look into.

Just a final question about the usb_modeswitch entries in your dmesg a couple of posts back.
Are they from your attempt to switch manually?
Are there any signs of output from usb_modeswitch in the dmesg log if you reboot and don't send the manual cmds?

_________________
I'm on a whiskey diet, lost 3 days already
mehulved
DD-WRT Novice


Joined: 17 Dec 2008
Posts: 26

PostPosted: Sat Mar 24, 2012 18:52    Post subject: Reply with quote
LOM wrote:
Ok, I have already opened a bug ticket about 3G problem on 18777 so this is something Brainslayer has to look into.

That's great. Thank you.

LOM wrote:

Just a final question about the usb_modeswitch entries in your dmesg a couple of posts back.
Are they from your attempt to switch manually?
Are there any signs of output from usb_modeswitch in the dmesg log if you reboot and don't send the manual cmds?

There is an automatic attempt. I just rebooted my router and plugged in the 3G stick.
I see a line
Code:

<4>usb 1-1: usbfs: process 1740 (usb_modeswitch) did not claim interface 0 before use

in dmesg.
And here's the /tmp/usb_modeswitch.conf after that. I haven't run any manual commands after the reboot.
Code:

DefaultVendor=0x1c9e
DefaultProduct=0xf000
TargetVendor=0x1c9e
TargetProductList=0x9000,0x9603,0x9605,0x9607
CheckSuccess=20
MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
AZERTY123
DD-WRT User


Joined: 07 Mar 2012
Posts: 57

PostPosted: Sun Mar 25, 2012 10:06    Post subject: Reply with quote
To my simple mind it looks like the driver gets attached to a wrong interface. Once we reset that - the router takes care of modeswitching.. It worked for me.
Why not give a try:

Using Telnet wrote:
Code:
usb_modeswitch -v 0x1c9e -p 0xf000 -V 0x1c9e -P 0x9605 -P 140b -R -i 1
sleep 10
usb_modeswitch -v 0x1c9e -p 0xf000 -V 0x1c9e -P 0x9605 -P 140b -R -i 1
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7165

PostPosted: Sun Mar 25, 2012 12:16    Post subject: Reply with quote
AZERTY123 wrote:
To my simple mind it looks like the driver gets attached to a wrong interface. Once we reset that - the router takes care of modeswitching.. It worked for me.
Why not give a try:

Using Telnet wrote:
Code:
usb_modeswitch -v 0x1c9e -p 0xf000 -V 0x1c9e -P 0x9605 -P 140b -R -i 1
sleep 10
usb_modeswitch -v 0x1c9e -p 0xf000 -V 0x1c9e -P 0x9605 -P 140b -R -i 1


the -i switch does not specify which interface the driver should connect to, it specifies which interface number the modeswitch command should be sent to.
Connecting a driver to a certain interface comes later when the stick has entered modem mode.

-i
Select initial USB interface (default: 0). Only for testing purposes.

As you can see from:

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=1c9e ProdID=f000 Rev= 0.00
S: Manufacturer=USB Modem
S: Product=USB Modem
S: SerialNumber=1234567890ABCDEF
C:* #Ifs= 1 Cfg#= 1 Atr=e0 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

there is only one interface in cd-rom mode (#Ifs=1) and that interface is number 0 (If# = 0).

_________________
I'm on a whiskey diet, lost 3 days already
AZERTY123
DD-WRT User


Joined: 07 Mar 2012
Posts: 57

PostPosted: Sun Mar 25, 2012 14:28    Post subject: Reply with quote
LOM wrote:

the -i switch does not specify which interface the driver should connect to, it specifies which interface number the modeswitch command should be sent to.
Connecting a driver to a certain interface comes later when the stick has entered modem mode.
-i
Select initial USB interface (default: 0). Only for testing purposes.

Hmmm.. that makes sense, but I can vouch that sending to this non-existent* interface is a sure-shot one here [tried various other combinations to torture the router Evil or Very Mad].
(*apparently.. I think it is there but console does not refresh to show us? OR that inducing an error forces SCSI driver refresh).
mehulved
DD-WRT Novice


Joined: 17 Dec 2008
Posts: 26

PostPosted: Thu Apr 26, 2012 22:24    Post subject: Reply with quote
Hey, any updates on this?
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7165

PostPosted: Fri Apr 27, 2012 8:13    Post subject: Reply with quote
mehulved wrote:
Hey, any updates on this?


No, I would really need a comparison of the stick on another platform than Ralink in order to understand where the problem is.

Your 2 manual modeswitch commands doesn't make any sense to me and is not the right solution - they are btw incorrect in syntax since there is an extra -P belonging to a Huawei stick..

The basic attributes 0xe0 means that the stick is Self Powered and not Bus Powered and this is commonly used for sticks that consumes more than 500mA which then has to be powered by external power adapter.
There are sometimes switching problems if a stick takes more than the 500mA a USB port can provide, the voltage drops and the stick gets reset, gets back to cd-rom mode.

There is an indication of something like this in your feedback, normally your built in USB hub will be Dev#1, the stick in cd-rom mode will be Dev#2 and the stick in modem mode will be Dev#3.
The device numbers should stay stable and Dev#2 disappears after switching when the new Dev#3 is found so your devices file should contain the 2 devices Dev#1 (hub) and Dev#3 (modem)

You don't have stable device numbers, yours are up to 6 and 7 and that is a clear indication that the stick is switching (old Dev# is gone, gets a new Dev#) but the stick returns in cd-rom mode instead of modem mode.

The modeswitch message is the correct one, it is taken from the data file provided by the author of usbmodeswitch and is tested by users before supported by him.

The Dev# would not had changed either if the modeswitch message wasn't correct, the stick would had ignored it, done nothing, and the Dev# would be the same as before.

_________________
I'm on a whiskey diet, lost 3 days already
mehulved
DD-WRT Novice


Joined: 17 Dec 2008
Posts: 26

PostPosted: Wed Jun 13, 2012 7:59    Post subject: Reply with quote
So, I got a new USB modem 2 days back. This time it's a well supported Huawei E1752.
At first when I connected it to the modem, usb_modeswitch was again failing to work while the PC was connecting without any problem.
Then a friend suggested to disable everything besides the modem interface by sending a few AT commands.
After doing that, I connected the usb modem back to the router and voila this time it worked flawlessly.
So, it makes me wonder if there's something I am missing or wrong with usb_modeswitch on the router?
I am still on the firmware 18777.
rufadzo
DD-WRT Novice


Joined: 17 Jun 2012
Posts: 5

PostPosted: Tue Jun 19, 2012 1:53    Post subject: please give details Reply with quote
hi hope you can helo. Have asus rt n13u b and it will not dial my cdma modem. You said in your post you sent some AT commands and yours now connects. Can you give mote info. I am a noob

Where do i enter all these codes
mehulved
DD-WRT Novice


Joined: 17 Dec 2008
Posts: 26

PostPosted: Tue Jun 19, 2012 4:09    Post subject: Re: please give details Reply with quote
rufadzo wrote:
hi hope you can helo. Have asus rt n13u b and it will not dial my cdma modem. You said in your post you sent some AT commands and yours now connects. Can you give mote info. I am a noob

Where do i enter all these codes

These are the ones that work with supported Huawei modems http://3g-modem.wetpaint.com/page/Huawei+AT-commands
rufadzo
DD-WRT Novice


Joined: 17 Jun 2012
Posts: 5

PostPosted: Tue Jun 19, 2012 5:21    Post subject: AT Commands Reply with quote
thank you for the speedy reply. I am trying to connect a zte 2746 which is supported under the.original firmware.from asus. it however never connects under asus firm ware either. Hoping you can help.

How do i probe to see if the dd wrt firmware can even see my device. Thank yoi in advance
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7165

PostPosted: Tue Jun 19, 2012 6:02    Post subject: Reply with quote
http://www.dd-wrt.com/wiki/index.php/Mobile_Broadband#Not_Supported_Modems_or_Not_Working_Modems
_________________
I'm on a whiskey diet, lost 3 days already
rufadzo
DD-WRT Novice


Joined: 17 Jun 2012
Posts: 5

PostPosted: Tue Jun 19, 2012 15:04    Post subject: More help still AC2747 on RT N13U B Reply with quote
I have moved to build 18777 and the following is my dmesg output

I have gone to usbmodeswitch and the following details are given: "########################################################
# ZTE AC8710
# ZTE AC2726
# and others
#
# Many new ZTE devices use this sequence. There are
# several ID combinations; check your default
#
# Contributor: Michael Khurtsiya, Amit Pundir and others

DefaultVendor= 0x19d2
DefaultProduct= 0xfff5

TargetVendor= 0x19d2
TargetProduct= 0xffff

# No. 2

DefaultVendor= 0x19d2
DefaultProduct= 0xfff6

TargetVendor= 0x19d2
TargetProduct= 0xfff1

# No. 3

DefaultVendor= 0x19d2
DefaultProduct= 0xfff5

TargetVendor= 0x19d2
TargetProduct= 0xfff1

MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"


########################################################
# ZTE AC2710 (EVDO)
#
# Contributor: Wasim Baig

DefaultVendor= 0x19d2
DefaultProduct= 0xfff5

TargetVendor= 0x19d2
TargetProduct= 0xffff

MessageContent="5553424312345678c00000008000069f010000000000000000000000000000"

# Just for information: try it with the message from the AC8710 ..."

What command should i issue to make manual modeswtich?


DMESG output:
"<5>Linux version 3.2.12-rc1-svn18774 (root@dd-wrt) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #396 Mon Mar 19 14:22:05 CET 2012
<7>prom: fw_arg0=00000001, fw_arg1=0372bfb0, fw_arg2=0372c3b0, fw_arg3=00000000
<7>argv[0]= (null) is invalid, skipping
<7>env[0]: memsize=64
<7>env[1]: initrd_start=0x00000000
<7>env[2]: initrd_size=0x0
<7>env[3]: flash_start=0xBF000000
<7>env[4]: flash_size=0x800000
<7>env[0]: memsize=64
<7>env[1]: initrd_start=0x00000000
<7>env[2]: initrd_size=0x0
<7>env[3]: flash_start=0xBF000000
<7>env[4]: flash_size=0x800000
<6>bootconsole [early0] enabled
<6>CPU revision is: 0001964c (MIPS 24KEc)
<6>Ralink RT3052 id:1 rev:3 running at 384.00 MHz
<6>Determined physical RAM map:
<6> memory: 04000000 @ 00000000 (usable)
<4>Zone PFN ranges:
<4> Normal 0x00000000 -> 0x00004000
<4>Movable zone start PFN for each node
<4>early_node_map[1] active PFN ranges
<4> 0: 0x00000000 -> 0x00004000
<7>On node 0 totalpages: 16384
<7>free_area_init_node: node 0, pgdat 802a3200, node_mem_map 81000000
<7> Normal zone: 128 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 16256 pages, LIFO batch:3
<7>pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
<7>pcpu-alloc: [0] 0
<4>Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
<5>Kernel command line: console=ttyS1,57600n8 root=/dev/mtdblock4 rootfstype=squashfs noinitrd
<6>PID hash table entries: 256 (order: -2, 1024 bytes)
<6>Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
<4>Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
<4>Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
<6>Writing ErrCtl register=00000004
<6>Readback ErrCtl register=00000004
<6>Memory: 61796k/65536k available (2296k kernel code, 3740k reserved, 405k data, 164k init, 0k highmem)
<6>NR_IRQS:48
<6>console [ttyS1] enabled, bootconsole disabled
<6>Calibrating delay loop... 255.59 BogoMIPS (lpj=1277952)
<6>pid_max: default: 32768 minimum: 301
<6>Mount-cache hash table entries: 512
<6>NET: Registered protocol family 16
<6>bio: create slab at 0
<5>SCSI subsystem initialized
<6>Switching to clocksource MIPS
<6>NET: Registered protocol family 2
<6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP established hash table entries: 2048 (order: 2, 16384 bytes)
<6>TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
<6>TCP: Hash tables configured (established 2048 bind 2048)
<6>TCP reno registered
<6>UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>NET: Registered protocol family 1
<6>squashfs: version 3.0 (2006/03/15) Phillip Lougher
<6>msgmni has been set to 120
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<6>Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
<6>serial8250: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
<6>serial8250: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
<4>Ralink gpio driver initialized
<6>system type: RT3052
<6>boot type: 0
<5>ralink flash device: 0x1000000 at 0xbf000000
<6>Ralink SoC physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x0022cb
<7>Ralink SoC physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
<6>Amd/Fujitsu Extended Query Table at 0x0040
<6> Amd/Fujitsu Extended Query version 1.1.
<5>number of CFI chips: 1
<0>
<0>found squashfs at 141000
<5>Creating 6 MTD partitions on "Ralink SoC physically mapped flash":
<5>0x000000000000-0x000000030000 : "uboot"
<5>0x000000030000-0x000000040000 : "uboot-config"
<5>0x000000040000-0x000000050000 : "factory-defaults"
<5>0x000000050000-0x0000007f0000 : "linux"
<5>0x000000141000-0x0000007f0000 : "rootfs"
<4>mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
<5>0x0000007f0000-0x000000800000 : "nvram"
<6>tun: Universal TUN/TAP device driver, 1.6
<6>tun: (C) 1999-2004 Max Krasnyansky
<6>PPP generic driver version 2.4.2
<6>PPP BSD Compression module registered
<6>PPP Deflate Compression module registered
<6>NET: Registered protocol family 24
<6>Ralink APSoC Hardware Watchdog Timer
<6>u32 classifier
<6> Actions configured
<6>Netfilter messages via NETLINK v0.30.
<6>nf_conntrack version 0.5.0 (965 buckets, 3860 max)
<6>ctnetlink v0.93: registering with nfnetlink.
<6>IPv4 over IPv4 tunneling driver
<6>ip_tables: (C) 2000-2006 Netfilter Core Team
<6>IPP2P v0.8.2 loading
<6>ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
<6>TCP bic registered
<6>TCP cubic registered
<6>TCP westwood registered
<6>TCP highspeed registered
<6>TCP hybla registered
<6>TCP htcp registered
<6>TCP vegas registered
<6>TCP scalable registered
<6>NET: Registered protocol family 17
<6>8021q: 802.1Q VLAN Support v1.8
<6>searching for nvram
<6>nvram size = 0
<4>MAC_ADRH -- : 0x00000000
<4>MAC_ADRL -- : 0x00000000
<4>Ralink APSoC Ethernet Driver Initilization. v2.0 256 rx/tx descriptors allocated, mtu = 1500!
<4>NAPI enable, Tx Ring = 256, Rx Ring = 256
<4>MAC_ADRH -- : 0x0000000c
<4>MAC_ADRL -- : 0x43414632
<4>rt3052 access driver initialization.
<6>VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
<6>Freeing unused kernel memory: 164k freed
<4>rt2860v2_ap: module license 'unspecified' taints kernel.
<4>Disabling lock debugging due to kernel taint
<4>
<4>phy_tx_ring = 0x03566000, tx_ring = 0xa3566000
<4>
<4>phy_rx_ring0 = 0x03567000, rx_ring0 = 0xa3567000
<4>RT305x_ESW: Link Status Changed
<4>CDMA_CSG_CFG = 81000007
<4>GDMA1_FWD_CFG = 710000
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>dwc_otg: version 2.72a 24-JUN-2008
<6>DWC_otg: Core Release: 2.66a
<6>DWC_otg: Periodic Transfer Interrupt Enhancement - disabled
<6>DWC_otg: Multiprocessor Interrupt Enhancement - disabled
<6>DWC_otg: Using DMA mode
<6>DWC_otg: Device using Buffer DMA mode
<6>dwc_otg lm0: DWC OTG Controller
<6>dwc_otg lm0: new USB bus registered, assigned bus number 1
<6>dwc_otg lm0: irq 26, io mem 0x00000000
<6>DWC_otg: Init: Port Power? op_state=1
<6>DWC_otg: Init: Power Port (0)
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
<6>usbcore: registered new interface driver libusual
<6>usb 1-1: new full-speed USB device number 2 using dwc_otg
<6>device vlan1 entered promiscuous mode
<6>device eth2 entered promiscuous mode
<6>device vlan2 entered promiscuous mode
<6>br0: port 2(vlan2) entering forwarding state
<6>br0: port 2(vlan2) entering forwarding state
<6>br0: port 1(vlan1) entering forwarding state
<6>br0: port 1(vlan1) entering forwarding state
<4>RtmpOSNetDevDetach(): RtmpOSNetDeviceDetach(), dev->name=ra0!
<4>0x1300 = 00064380
<4>0x1300 = 00064380
<6>device ra0 entered promiscuous mode
<6>br0: port 3(ra0) entering forwarding state
<6>br0: port 3(ra0) entering forwarding state
<6>br0: port 2(vlan2) entering forwarding state
<6>br0: port 1(vlan1) entering forwarding state
<6>usbcore: registered new interface driver usbserial
<6>usbserial: USB Serial Driver core
<6>USB Serial support registered for GSM modem (1-port)
<6>usbcore: registered new interface driver option
<6>option: v0.7.2:USB Driver for GSM modems
<6>br0: port 3(ra0) entering forwarding state
<4>usb 1-1: usbfs: process 784 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1104 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1185 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1264 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1369 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1450 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1529 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1627 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1706 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1787 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1868 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 1964 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2045 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2126 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2205 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2303 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2382 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2463 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2561 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2640 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2721 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2802 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2898 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 2979 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3060 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3156 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3237 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3318 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3397 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3495 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3576 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3655 (usb_modeswitch) did not claim interface 0 before use
<4>RT305x_ESW: Link Status Changed
<4>usb 1-1: usbfs: process 3751 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3818 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3885 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 3952 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4036 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4103 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4170 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4254 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4321 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4388 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4455 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4539 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4606 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4673 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4740 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4824 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4891 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 4958 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5042 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5109 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5176 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5243 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5327 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5394 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5463 (usb_modeswitch) did not claim interface 0 before use
<4>usb 1-1: usbfs: process 5574 (usb_modeswitch) did not claim interface 0 before use
<6>device vlan1 left promiscuous mode
<6>br0: port 1(vlan1) entering forwarding state
<6>device vlan2 left promiscuous mode
<6>device eth2 left promiscuous mode
<6>br0: port 2(vlan2) entering forwarding state
<6>device ra0 left promiscuous mode
<6>br0: port 3(ra0) entering forwarding state
<6>device vlan1 entered promiscuous mode
<6>device eth2 entered promiscuous mode
<6>br0: port 1(vlan1) entering forwarding state
<6>br0: port 1(vlan1) entering forwarding state
<6>device vlan2 entered promiscuous mode
<6>br0: port 2(vlan2) entering forwarding state
<6>br0: port 2(vlan2) entering forwarding state
<4>0x1300 = 00064380
<4>0x1300 = 00064380
<6>device ra0 entered promiscuous mode
<6>br0: port 3(ra0) entering forwarding state
<6>br0: port 3(ra0) entering forwarding state
<6>br0: port 3(ra0) entering forwarding state
<6>br0: port 1(vlan1) entering forwarding state
<6>br0: port 2(vlan2) entering forwarding state
<4>RtmpOSNetDevDetach(): RtmpOSNetDeviceDetach(), dev->name=ra0!
<6>device ra0 left promiscuous mode
<6>br0: port 3(ra0) entering disabled state
<4>0x1300 = 00064380
<4>0x1300 = 00064380
<6>device ra0 entered promiscuous mode
<6>br0: port 3(ra0) entering forwarding state
<6>br0: port 3(ra0) entering forwarding state
<4>usb 1-1: usbfs: process 6294 (usb_modeswitch) did not claim interface 0 before use
<6>br0: port 3(ra0) entering forwarding state
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7165

PostPosted: Tue Jun 19, 2012 15:15    Post subject: Reply with quote
I don't see any usb vid:pid or interface list.

It is not that difficult to read this thread and see what info other users has provided.

_________________
I'm on a whiskey diet, lost 3 days already
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink SoC 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