Open GoogleCodeExporter opened 9 years ago
I can also confirm that I am not using any pin numbers etc on my modem. I have
tested internet connected works fine through the USB of my Ubuntu laptop.
Original comment by adrian.m...@gmail.com
on 29 Nov 2013 at 12:20
Images of the modem config screen:
http://oi43.tinypic.com/f09c7t.jpg
http://oi44.tinypic.com/rjpe2u.jpg
Original comment by adrian.m...@gmail.com
on 29 Nov 2013 at 12:30
Is the anything I can do to get someone to look into this?
Many thanks,
Adrian
Original comment by adrian.m...@gmail.com
on 3 Dec 2013 at 9:54
-072 build has bug with get symbol # via WebUI. Bug already fixed in git.
Original comment by andy.pad...@gmail.com
on 4 Dec 2013 at 1:23
Has it been compiled anywhere? Is there a link where I can test it out?
Thanks in advance for the great alternative software.
Original comment by adrian.m...@gmail.com
on 4 Dec 2013 at 1:46
You can fix bug manually, input commands from terminal:
nvram set modem_dialnum=*99#
restart_wan
After this do not save settings on page USB Application - Modem, because "*99#"
saved to nvram as *99_
You can always build firmware (with any configurations) from git:
http://code.google.com/p/rt-n56u/wiki/HowToMakeFirmware
Original comment by andy.pad...@gmail.com
on 4 Dec 2013 at 2:32
Thanks, I will check the web page you described. However the problem has not
yet been resolved- I still get a 'script failed' message.
I noticed that when trying to change the Interface, the log keeps stating its
usb0. Is there a terminal command to change this as well? I noticed on a few
other tickets that this can be a problem why the modem is not recognised.
Many thanks for the help
Jan 6 03:59:59 pppd[31843]: Connect script failed
Jan 6 04:00:14 comgt: ERROR: CONNECT ERROR!
Jan 6 04:00:14 pppd[31843]: Connect script failed
Jan 6 04:00:18 login[5570]: root login on 'pts/0'
Jan 6 04:00:29 comgt: ERROR: CONNECT ERROR!
Jan 6 04:00:30 pppd[31843]: Connect script failed
Jan 6 04:00:44 comgt: ERROR: CONNECT ERROR!
Jan 6 04:00:45 pppd[31843]: Connect script failed
Jan 6 04:01:00 pppd[31843]: Serial connection established.
Jan 6 04:01:00 pppd[31843]: Using interface ppp2
Jan 6 04:01:00 pppd[31843]: Connect: ppp2 <--> /dev/ttyUSB0
Jan 6 04:01:07 wan: perform manual connect
Jan 6 04:01:08 pppd[31843]: Terminating on signal 15
Jan 6 04:01:14 pppd[31843]: Connection terminated.
Jan 6 04:01:14 pppd[31843]: Serial link disconnected.
Jan 6 04:01:16 kernel: eth3: ===> VirtualIF_close
Jan 6 04:01:16 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload
[WAN]<->[LAN/WLAN]
Jan 6 04:01:16 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Jan 6 04:01:16 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Jan 6 04:01:16 kernel: eth3: ===> VirtualIF_open
Jan 6 04:01:16 RT-N56U: select RAS modem interface ttyUSB0 to pppd
Jan 6 04:01:16 pppd[5786]: pppd 2.4.5 started by admin, uid 0
Jan 6 04:01:28 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:01:28 pppd[5786]: Connect script failed
Jan 6 04:01:51 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:01:51 pppd[5786]: Connect script failed
Jan 6 04:02:14 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:02:14 pppd[5786]: Connect script failed
Jan 6 04:02:37 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:02:37 pppd[5786]: Connect script failed
Jan 6 04:02:43 pppd[5786]: Terminating on signal 15
Jan 6 04:02:43 pppd[5786]: Exit.
Jan 6 04:02:43 kernel: eth3: ===> VirtualIF_close
Jan 6 04:02:43 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload
[WAN]<->[LAN/WLAN]
Jan 6 04:02:43 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Jan 6 04:02:43 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Jan 6 04:02:43 kernel: eth3: ===> VirtualIF_open
Jan 6 04:02:43 RT-N56U: select RAS modem interface ttyUSB0 to pppd
Jan 6 04:02:43 pppd[6000]: pppd 2.4.5 started by admin, uid 0
Jan 6 04:02:55 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:02:55 pppd[6000]: Connect script failed
Jan 6 04:03:18 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:03:18 pppd[6000]: Connect script failed
Jan 6 04:03:31 pppd[6000]: Child process /bin/comgt -d /dev/ttyUSB0 -s
/etc_ro/ppp/3g/Generic_conn.scr (pid 6054) terminated with signal 15
Jan 6 04:03:31 pppd[6000]: Connect script failed
Jan 6 04:03:32 pppd[6000]: Exit.
Jan 6 04:03:33 kernel: eth3: ===> VirtualIF_close
Jan 6 04:03:33 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload
[WAN]<->[LAN/WLAN]
Jan 6 04:03:33 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Jan 6 04:03:33 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Jan 6 04:03:33 kernel: eth3: ===> VirtualIF_open
Jan 6 04:03:33 RT-N56U: select RAS modem interface ttyUSB0 to pppd
Jan 6 04:03:33 pppd[6151]: pppd 2.4.5 started by admin, uid 0
Jan 6 04:03:45 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:03:45 pppd[6151]: Connect script failed
Jan 6 04:03:46 wan: perform manual connect
Jan 6 04:03:46 pppd[6151]: Terminating on signal 15
Jan 6 04:03:46 pppd[6151]: Exit.
Jan 6 04:03:46 kernel: eth3: ===> VirtualIF_close
Jan 6 04:03:46 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload
[WAN]<->[LAN/WLAN]
Jan 6 04:03:46 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Jan 6 04:03:46 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Jan 6 04:03:46 kernel: eth3: ===> VirtualIF_open
Jan 6 04:03:47 RT-N56U: select RAS modem interface ttyUSB0 to pppd
Jan 6 04:03:47 pppd[6254]: pppd 2.4.5 started by admin, uid 0
Jan 6 04:03:58 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:03:58 pppd[6254]: Connect script failed
Jan 6 04:04:21 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:04:21 pppd[6254]: Connect script failed
Jan 6 04:04:44 comgt: ERROR: CONNECT TIMEOUT!
Jan 6 04:04:44 pppd[6254]: Connect script failed
Original comment by adrian.m...@gmail.com
on 4 Dec 2013 at 4:11
I tried this, but no joy:
/home/root # /bin/comgt -d /dev/ttyUSB1 -s /etc_ro/ppp/3g/Generic_conn.scr
Can't open device /dev/ttyUSB1.
/home/root # /bin/comgt -d /dev/ttyUSB2 -s /etc_ro/ppp/3g/Generic_conn.scr
Can't open device /dev/ttyUSB2.
/home/root # /bin/comgt -d /dev/ttyUSB3 -s /etc_ro/ppp/3g/Generic_conn.scr
Can't open device /dev/ttyUSB3.
/home/root # /bin/comgt -d /dev/ttyUSB0 -s /etc_ro/ppp/3g/Generic_conn.scr
ERROR: CONNECT TIMEOUT!
Original comment by adrian.m...@gmail.com
on 4 Dec 2013 at 4:15
Here are the results of a couple of the commands within the Generic_conn.scr:
/home/root # cat /etc_ro/ppp/3g/Generic_conn.scr |grep nvram
let $x=$rpipe("nvram get modem_pin")
let $x=$rpipe("nvram get modem_cmd")
let $x=$rpipe("nvram get modem_apn")
let $x=$rpipe("nvram get modem_dialnum")
/home/root # nvram get modem_pin
/home/root # nvram get modem_cmd
/home/root # nvram get modem_apn
3ireland.ie
/home/root # nvram get modem_dialnum
*99#
No pin number is associated with the modem. Have confirmed this. As indicated
earlier, the modem works on Ubuntu without any settings defined.
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 8:24
I am trying to get anything coming back from the modem, and it just seems dead
to any of the scripts:
/etc_ro/ppp/3g # /bin/comgt -d /dev/ttyUSB0 -s /etc_ro/ppp/3g/getinfo
Timeout
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 8:37
When I run the rogers.scr, I get a connected message. Does this help?
/etc_ro/ppp/3g # /bin/comgt -d /dev/ttyUSB0 -s /etc_ro/ppp/3g/Sierra_conn.scr
ERROR: CONNECT TIMEOUT!
/etc_ro/ppp/3g # /bin/comgt -d /dev/ttyUSB0 -s /etc_ro/ppp/3g/rogers_conn.scr
CONNECTED
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 8:41
I am trying to backup the Generic_conn.scr and replace it with the
rogers_conn.scr to see if that will help, but the system is telling me its a ro
filesystem. Can I change this? If so, how?
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 8:50
/etc_ro/ppp/3g # cat /proc/bus/usb/devices
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 3.04
S: Manufacturer=Linux 3.4.68 ohci_hcd
S: Product=Ralink RT3xxx OHCI Controller
S: SerialNumber=rt3xxx-ohci
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= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2
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.04
S: Manufacturer=Linux 3.4.68 ehci_hcd
S: Product=Ralink EHCI Host Controller
S: SerialNumber=rt3xxx-ehci
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=01 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1c1f Rev= 1.02
S: Manufacturer=HUAWEI
S: Product=HUAWEI Mobile
C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=02(comm.) Sub=02 Prot=ff Driver=option
E: Ad=81(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=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0d Prot=00 Driver=(none)
E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=2ms
I: If#= 2 Alt= 1 #EPs= 3 Cls=02(comm.) Sub=0d Prot=00 Driver=(none)
E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=2ms
E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 8:59
/etc_ro/ppp/3g # nvram get modem_type
1
/etc_ro/ppp/3g # nvram set modem_type=2
/etc_ro/ppp/3g # nvram get modem_type
2
/etc_ro/ppp/3g # restart_wan
/etc_ro/ppp/3g # /bin/comgt -d /dev/ttyUSB0 -s /etc_ro/ppp/3g/Generic_conn.scr
ERROR: CONNECT TIMEOUT!
/etc_ro/ppp/3g # nvram set modem_type=3
/etc_ro/ppp/3g # nvram get modem_type
3
/etc_ro/ppp/3g # restart_wan
/etc_ro/ppp/3g # /bin/comgt -d /dev/ttyUSB0 -s /etc_ro/ppp/3g/Generic_conn.scr
ERROR: CONNECT TIMEOUT!
/etc_ro/ppp/3g # nvram set modem_type=4
/etc_ro/ppp/3g # nvram get modem_type
4
/etc_ro/ppp/3g # /bin/comgt -d /dev/ttyUSB0 -s /etc_ro/ppp/3g/Generic_conn.scr
ERROR: CONNECT TIMEOUT!
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 9:10
/etc # nvram show | grep modem
modem_zcd=0
modem_type=1
modem_pass=
modem_arun=1
modem_apn=3internet
modem_cmd=
modem_user=
modem_nets=0
modem_dialnum=*99#
modem_isp=other
modem_mtu=1500
modem_dnsa=1
wan0_modem_dev=4
modem_node=0
modem_rule=1
modem_country=Ireland
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 10:05
Here is the syslog of my Ubuntu laptop when the e5331 is connected via usb:
Dec 5 10:38:33 adrian-eM350 kernel: [12522.568187] usb 1-1: new high-speed USB
device number 3 using ehci-pci
Dec 5 10:38:34 adrian-eM350 kernel: [12522.701254] usb 1-1: New USB device
found, idVendor=12d1, idProduct=14fe
Dec 5 10:38:34 adrian-eM350 kernel: [12522.701270] usb 1-1: New USB device
strings: Mfr=2, Product=1, SerialNumber=0
Dec 5 10:38:34 adrian-eM350 kernel: [12522.701281] usb 1-1: Product: HUAWEI
Mobile
Dec 5 10:38:34 adrian-eM350 kernel: [12522.701291] usb 1-1: Manufacturer:
HUAWEI
Dec 5 10:38:34 adrian-eM350 mtp-probe: checking bus 1, device 3:
"/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1"
Dec 5 10:38:34 adrian-eM350 mtp-probe: bus: 1, device: 3 was not an MTP device
Dec 5 10:38:34 adrian-eM350 kernel: [12523.433387] Initializing USB Mass
Storage driver...
Dec 5 10:38:34 adrian-eM350 kernel: [12523.433829] scsi4 : usb-storage 1-1:1.0
Dec 5 10:38:34 adrian-eM350 kernel: [12523.434136] usbcore: registered new
interface driver usb-storage
Dec 5 10:38:34 adrian-eM350 kernel: [12523.434144] USB Mass Storage support
registered.
Dec 5 10:38:35 adrian-eM350 kernel: [12524.433216] scsi 4:0:0:0: CD-ROM
HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Dec 5 10:38:35 adrian-eM350 kernel: [12524.437444] sr0: scsi-1 drive
Dec 5 10:38:35 adrian-eM350 kernel: [12524.437461] cdrom: Uniform CD-ROM
driver Revision: 3.20
Dec 5 10:38:35 adrian-eM350 kernel: [12524.438123] sr 4:0:0:0: Attached scsi
CD-ROM sr0
Dec 5 10:38:35 adrian-eM350 kernel: [12524.438699] sr 4:0:0:0: Attached scsi
generic sg1 type 5
Dec 5 10:38:36 adrian-eM350 usb_modeswitch: switching device 12d1:14fe on
001/003
Dec 5 10:38:36 adrian-eM350 kernel: [12525.376865] usb 1-1: USB disconnect,
device number 3
Dec 5 10:38:39 adrian-eM350 kernel: [12527.712185] usb 1-1: new high-speed USB
device number 4 using ehci-pci
Dec 5 10:38:39 adrian-eM350 kernel: [12527.845638] usb 1-1: New USB device
found, idVendor=12d1, idProduct=1c1f
Dec 5 10:38:39 adrian-eM350 kernel: [12527.845655] usb 1-1: New USB device
strings: Mfr=2, Product=1, SerialNumber=0
Dec 5 10:38:39 adrian-eM350 kernel: [12527.845666] usb 1-1: Product: HUAWEI
Mobile
Dec 5 10:38:39 adrian-eM350 kernel: [12527.845676] usb 1-1: Manufacturer:
HUAWEI
Dec 5 10:38:39 adrian-eM350 kernel: [12527.849770] scsi5 : usb-storage 1-1:1.1
Dec 5 10:38:39 adrian-eM350 mtp-probe: checking bus 1, device 4:
"/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1"
Dec 5 10:38:39 adrian-eM350 mtp-probe: bus: 1, device: 4 was not an MTP device
Dec 5 10:38:39 adrian-eM350 kernel: [12528.042009] usb 1-1: MAC-Address:
58:2c:80:13:92:63
Dec 5 10:38:39 adrian-eM350 kernel: [12528.042626] cdc_ncm 1-1:1.2 usb0:
register 'cdc_ncm' at usb-0000:00:1d.7-1, CDC NCM, 58:2c:80:13:92:63
Dec 5 10:38:39 adrian-eM350 kernel: [12528.043057] usbcore: registered new
interface driver cdc_ncm
Dec 5 10:38:39 adrian-eM350 kernel: [12528.059001] usbcore: registered new
interface driver cdc_ether
Dec 5 10:38:39 adrian-eM350 kernel: [12528.133131] usb 1-1: bad CDC descriptors
Dec 5 10:38:39 adrian-eM350 kernel: [12528.133301] usbcore: registered new
interface driver rndis_host
Dec 5 10:38:39 adrian-eM350 kernel: [12528.152858] usbcore: registered new
interface driver cdc_wdm
Dec 5 10:38:39 adrian-eM350 kernel: [12528.172397] usbcore: registered new
interface driver cdc_mbim
Dec 5 10:38:39 adrian-eM350 kernel: [12528.187194] usb 1-1: bad CDC descriptors
Dec 5 10:38:39 adrian-eM350 kernel: [12528.187363] usbcore: registered new
interface driver rndis_wlan
Dec 5 10:38:39 adrian-eM350 kernel: [12528.242014] usbcore: registered new
interface driver usbserial
Dec 5 10:38:39 adrian-eM350 kernel: [12528.243215] usbcore: registered new
interface driver usbserial_generic
Dec 5 10:38:39 adrian-eM350 kernel: [12528.244973] usbserial: USB Serial
support registered for generic
Dec 5 10:38:39 adrian-eM350 kernel: [12528.337385] usbcore: registered new
interface driver option
Dec 5 10:38:39 adrian-eM350 kernel: [12528.337459] usbserial: USB Serial
support registered for GSM modem (1-port)
Dec 5 10:38:39 adrian-eM350 kernel: [12528.338780] option 1-1:1.0: GSM modem
(1-port) converter detected
Dec 5 10:38:39 adrian-eM350 kernel: [12528.339403] usb 1-1: GSM modem (1-port)
converter now attached to ttyUSB0
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: SCPlugin-Ifupdown: devices
added (path: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.2/net/usb0,
iface: usb0)
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: SCPlugin-Ifupdown: device
added (path: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.2/net/usb0,
iface: usb0): no ifupdown configuration found.
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <warn> failed to allocate
link cache: (-10) Operation not supported
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <info> (usb0): carrier is OFF
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <error> [1386239919.933560]
[nm-device-ethernet.c:443] update_permanent_hw_address(): (usb0): unable to
read permanent MAC address (error 0)
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <info> (usb0): new Ethernet
device (driver: 'cdc_ncm' ifindex: 4)
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <info> (usb0): exported as
/org/freedesktop/NetworkManager/Devices/2
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <info> (usb0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <info> (usb0): bringing up
device.
Dec 5 10:38:39 adrian-eM350 kernel: [12528.598704] IPv6: ADDRCONF(NETDEV_UP):
usb0: link is not ready
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <info> (usb0): preparing
device.
Dec 5 10:38:39 adrian-eM350 NetworkManager[890]: <info> (usb0): deactivating
device (reason 'managed') [2]
Dec 5 10:38:39 adrian-eM350 kernel: [12528.602915] IPv6: ADDRCONF(NETDEV_UP):
usb0: link is not ready
Dec 5 10:38:39 adrian-eM350 kernel: [12528.605220] cdc_ncm: usb0: network
connection: connected
Dec 5 10:38:39 adrian-eM350 kernel: [12528.606875] IPv6:
ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
Dec 5 10:38:39 adrian-eM350 kernel: [12528.613242] cdc_ncm: usb0: 21 mbit/s
downlink 21 mbit/s uplink
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Added default wired
connection 'Wired connection 2' for
/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.2/net/usb0
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> (usb0): carrier now ON
(device state 20)
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> (usb0): device state
change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Auto-activating
connection 'Wired connection 2'.
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
starting connection 'Wired connection 2'
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> (usb0): device state
change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 1 of 5 (Device Prepare) scheduled...
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 1 of 5 (Device Prepare) started...
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 2 of 5 (Device Configure) scheduled...
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 1 of 5 (Device Prepare) complete.
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 2 of 5 (Device Configure) starting...
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> (usb0): device state
change: prepare -> config (reason 'none') [40 50 0]
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 2 of 5 (Device Configure) successful.
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 3 of 5 (IP Configure Start) scheduled.
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 2 of 5 (Device Configure) complete.
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 3 of 5 (IP Configure Start) started...
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> (usb0): device state
change: config -> ip-config (reason 'none') [50 70 0]
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Beginning DHCPv4 transaction (timeout in 45 seconds)
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> dhclient started with
pid 8632
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Beginning IP6 addrconf.
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 3 of 5 (IP Configure Start) complete.
Dec 5 10:38:40 adrian-eM350 dhclient: Internet Systems Consortium DHCP Client
4.2.4
Dec 5 10:38:40 adrian-eM350 dhclient: Copyright 2004-2012 Internet Systems
Consortium.
Dec 5 10:38:40 adrian-eM350 dhclient: All rights reserved.
Dec 5 10:38:40 adrian-eM350 dhclient: For info, please visit
https://www.isc.org/software/dhcp/
Dec 5 10:38:40 adrian-eM350 dhclient:
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> (usb0): DHCPv4 state
changed nbi -> preinit
Dec 5 10:38:40 adrian-eM350 dhclient: Listening on LPF/usb0/58:2c:80:13:92:63
Dec 5 10:38:40 adrian-eM350 dhclient: Sending on LPF/usb0/58:2c:80:13:92:63
Dec 5 10:38:40 adrian-eM350 dhclient: Sending on Socket/fallback
Dec 5 10:38:40 adrian-eM350 dhclient: DHCPDISCOVER on usb0 to 255.255.255.255
port 67 interval 3 (xid=0x4d49aa18)
Dec 5 10:38:40 adrian-eM350 kernel: [12528.849201] scsi 5:0:0:0: CD-ROM
HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Dec 5 10:38:40 adrian-eM350 kernel: [12528.857556] sr0: scsi-1 drive
Dec 5 10:38:40 adrian-eM350 kernel: [12528.858014] sr 5:0:0:0: Attached scsi
CD-ROM sr0
Dec 5 10:38:40 adrian-eM350 kernel: [12528.858515] sr 5:0:0:0: Attached scsi
generic sg1 type 5
Dec 5 10:38:40 adrian-eM350 modem-manager[799]: <info> (ttyUSB0) opening
serial port...
Dec 5 10:38:40 adrian-eM350 modem-manager[799]: <warn> (ttyUSB0): port
attributes not fully set
Dec 5 10:38:40 adrian-eM350 dhclient: DHCPREQUEST of 192.168.1.101 on usb0 to
255.255.255.255 port 67 (xid=0x4d49aa18)
Dec 5 10:38:40 adrian-eM350 dhclient: DHCPOFFER of 192.168.1.101 from
192.168.1.1
Dec 5 10:38:40 adrian-eM350 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Dec 5 10:38:40 adrian-eM350 dhclient: bound to 192.168.1.101 -- renewal in
40291 seconds.
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> (usb0): DHCPv4 state
changed preinit -> bound
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> address 192.168.1.101
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> prefix 24
(255.255.255.0)
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> gateway 192.168.1.1
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> nameserver
'192.168.1.1'
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> nameserver
'192.168.1.1'
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec 5 10:38:40 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 5 of 5 (IPv4 Commit) started...
Dec 5 10:38:40 adrian-eM350 avahi-daemon[831]: Joining mDNS multicast group on
interface usb0.IPv4 with address 192.168.1.101.
Dec 5 10:38:40 adrian-eM350 avahi-daemon[831]: New relevant interface
usb0.IPv4 for mDNS.
Dec 5 10:38:40 adrian-eM350 avahi-daemon[831]: Registering new address record
for 192.168.1.101 on usb0.IPv4.
Dec 5 10:38:41 adrian-eM350 avahi-daemon[831]: Joining mDNS multicast group on
interface usb0.IPv6 with address fe80::5a2c:80ff:fe13:9263.
Dec 5 10:38:41 adrian-eM350 avahi-daemon[831]: New relevant interface
usb0.IPv6 for mDNS.
Dec 5 10:38:41 adrian-eM350 avahi-daemon[831]: Registering new address record
for fe80::5a2c:80ff:fe13:9263 on usb0.*.
Dec 5 10:38:41 adrian-eM350 kernel: [12529.829906] ISO 9660 Extensions:
Microsoft Joliet Level 1
Dec 5 10:38:41 adrian-eM350 kernel: [12529.900454] ISOFS: changing to
secondary root
Dec 5 10:38:41 adrian-eM350 udisksd[1691]: Mounted /dev/sr0 at
/media/adrian/3MobileWiFi on behalf of uid 1000
Dec 5 10:38:41 adrian-eM350 NetworkManager[890]: <info> (usb0): device state
change: ip-config -> secondaries (reason 'none') [70 90 0]
Dec 5 10:38:41 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 5 of 5 (IPv4 Commit) complete.
Dec 5 10:38:41 adrian-eM350 NetworkManager[890]: <info> (usb0): device state
change: secondaries -> activated (reason 'none') [90 100 0]
Dec 5 10:38:41 adrian-eM350 NetworkManager[890]: <info> Policy set 'Wired
connection 2' (usb0) as default for IPv4 routing and DNS.
Dec 5 10:38:41 adrian-eM350 NetworkManager[890]: <info> Writing DNS
information to /sbin/resolvconf
Dec 5 10:38:41 adrian-eM350 dnsmasq[1393]: setting upstream servers from DBus
Dec 5 10:38:41 adrian-eM350 dnsmasq[1393]: using nameserver 192.168.1.1#53
Dec 5 10:38:42 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
successful, device activated.
Dec 5 10:38:42 adrian-eM350 dbus[772]: [system] Activating service
name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 5 10:38:42 adrian-eM350 dbus[772]: [system] Successfully activated service
'org.freedesktop.nm_dispatcher'
Dec 5 10:38:51 adrian-eM350 ntpdate[8733]: adjust time server 91.189.94.4
offset 0.002796 sec
Dec 5 10:39:00 adrian-eM350 NetworkManager[890]: <info> (usb0): IP6 addrconf
timed out or failed.
Dec 5 10:39:00 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Dec 5 10:39:00 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 4 of 5 (IPv6 Configure Timeout) started...
Dec 5 10:39:00 adrian-eM350 NetworkManager[890]: <info> Activation (usb0)
Stage 4 of 5 (IPv6 Configure Timeout) complete.
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 10:48
I have done some googling about the e5331 and I have found something
interesting:
"I have a Huawei E5331 which is a Wi-Fi dongle with a USB port as well. The
device works ok in Wi-fi mode, but I want to use it with some Linux systems in
USB mode as well.
Using the current versions of USB_ModeSwitch and the data package, I can mode
switch this device just fine, but it always mode switches into a Ethernet over
USB mode with id 12d1:1c1f.
However if you look here, http://ubuntuforums.org/showthread.php?t=2098728 you
will see this poster starts out with this device mode switching into 12d1:1506
and the dmesg output shows it as a GSM modem in that mode.
Given the other issues in that thread with Ethernet over USB (which I have also
experienced with my non-Ubuntu based distribution) I would like to run the
device in GSM modem mode using option or usbserial."
The full post can be found here:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1322
I can see the following on the router:
/etc # lsusb -v
Bus 001 Device 009: ID 12d1:1c1f
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
so, perhaps if I can modeswitch the device to 12d1:1506, I might have some
better luck.
Although on ubuntu, I get another mode(14fe)
Dec 5 10:38:36 adrian-eM350 usb_modeswitch: switching device 12d1:14fe on
001/003
I am way out of my depth here, I do not know how to modeswitch a device and
would like some help here....... :-)
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 11:32
Update to my modeswitch knowledge:
/etc_ro/usb_modeswitch.d # usb_modeswitch -c 12d1\:14fe -W --default-vendor
12d1 --default-product 1c1f
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x1c1f
TargetVendor= 0x12d1
TargetProduct= not set
TargetClass= not set
TargetProductList="1506,151d"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice enabled (default)
Success check disabled
System integration mode disabled
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 009 on 001
skipped 4 class/vendor specific interface descriptors
skipped 4 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
Looking for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 12d1:1c1f
found matching vendor ID
searching devices, found USB ID 1d6b:0002
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 12d1:1c1f
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0002
Found device in default mode, class or configuration (1)
Accessing device 009 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using interface number 0
Error: can't use storage command in MessageContent with interface 0;
interface class is 2, should be 8. Aborting.
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 12:04
Could this be significant:
Jan 1 00:00:08 usb_modeswitch: no rule for device 12d1:1c1f
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 12:21
I'm attempting to follow the steps to creating a custom firmware with the Huwai
driver.
Hopefully that will resolve the issue, if I can make it work....
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 2:22
I am getting lots of 'unknowns', 'clobbered', 'warnings' and other errors at
the './build_toolchain' script. Is that normal?
And is there an escape hatch, should I load a faulty firmware image onto my
router? Wish these things had a console connection...
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 5:36
Wow, completely lost now. How would I go about adding the Huwei driver to the
yet to be built firmware? I have no idea how to customise after
./build_toolchain.
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 6:06
Finally!
I managed to get the thing working, and without too much bother, unless you
consider a day of intensive analysis a bother.
Its just a matter of setting the modem type to NDIS!!!!!
I have internet via my Asus, Yipee!
Original comment by adrian.m...@gmail.com
on 5 Dec 2013 at 10:06
Original issue reported on code.google.com by
adrian.m...@gmail.com
on 29 Nov 2013 at 12:14