Hi,

I setup a nslu2 with openwrt (tried 8.09.1 and trunk, squashfs) and want to use a Huawei E160 for a 3g connection. Device shows up fine as ttyUSB0, I can talk with the modem with minicom without any problem. I followed all the tutorials around, but I'm hitting a wall with comgt/gcom: Whenever I call it, I get this:

(should ask for the PIN):
------------------
root@OpenWrt:~# gcom -d /dev/ttyUSB0
comgt 23:09:44 -> -- Error Report --
comgt 23:09:44 -> ---->                       ^
comgt 23:09:44 -> Error @74, line 4, Could not write to COM device. (1)
root@OpenWrt:~#
----------------------
The dmesg output is very weird (see below)
I tried all the command switches, no default script etc.

I removed all the references to gcom in /lib/modules/3g.sh, but then I have to setup the PIN with minicom and the connection is slow.

Any hints? Thanks.

----------
dmesg (any more, too much for the ringbuffer btw!):
------------[ cut here ]------------
WARNING: at drivers/usb/serial/usb-serial.c:327 ()
Modules linked in: option usb_storage usbserial ohci_hcd ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ehci_hcd sd_mod pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ext2 ext3 jbd ppp_async ppp_generic slhc usbcore scsi_mod crc_ccitt
Function entered at [<c01d024c>] from [<c00310a8>]
Function entered at [<c0031060>] from [<bf132778>]
r6:c1dfa800 r5:c1dfa800 r4:c10d3800
Function entered at [<bf132724>] from [<c01148ec>]
r5:00000054 r4:c1dfa800
Function entered at [<c01148c4>] from [<c01121d4>]
Function entered at [<c01121b8>] from [<c01123e0>]
r5:c1dfa800 r4:00000054
Function entered at [<c0112370>] from [<c0113914>]
r5:00000054 r4:c1068800
Function entered at [<c0113638>] from [<c011696c>]
Function entered at [<c0116878>] from [<c0116a50>]
Function entered at [<c0116a10>] from [<bf152e94>]
Function entered at [<bf152de0>] from [<bf01cf0c>]
r8:c1072960 r7:00000000 r6:ffc021e0 r5:00000000 r4:c1072960
Function entered at [<bf01ce90>] from [<bf0dc1b0>]
r5:c1e90600 r4:ffc01080
Function entered at [<bf0dc0c4>] from [<bf0dcb70>]
r9:ffffff8d r8:c10729e0 r7:c1e906c0 r6:ffc021e0 r5:ffc023c0
r4:ffc01080
Function entered at [<bf0dca98>] from [<bf0df9e4>]
Function entered at [<bf0df8ec>] from [<bf0e152c>]
Function entered at [<bf0e12f4>] from [<bf01cc9c>]
Function entered at [<bf01cc58>] from [<c0055884>]
r5:00000000 r4:c1058720
Function entered at [<c0055840>] from [<c0056ed0>]
r7:000003ff r6:00000000 r5:0000001a r4:c0223f58
Function entered at [<c0056e3c>] from [<c0020064>]
r5:c023cc20 r4:0000001a
Function entered at [<c0020000>] from [<c00209b0>]
Exception stack(0xc1e29ab8 to 0xc1e29b00)
9aa0:                                                       000f4229 000003e8
9ac0: 00000000 00000017 000f4240 c1e29f70 c1c9e92c 000003ff be9fa89c c1e29f70
9ae0: 00000000 c1e29b24 3b9a70c5 c1e29b00 c008b1b0 c00eef80 20000013 ffffffff
r7:000003ff r6:04000000 r5:0000001f r4:ffffffff
Function entered at [<c008b0d4>] from [<c008bc5c>]
r5:00000000 r4:fffffffc
Function entered at [<c008b7e4>] from [<c008beb0>]
Function entered at [<c008bc68>] from [<c008c138>]
Function entered at [<c008bf68>] from [<c0020da0>]
---[ end trace acad35f743645df7 ]---

Hi,

I have the same problem here. I am running 8.09.1 on an NSLU2 and using an Huawei E169 UMTS stick.

After bootup, I "activate" the full functionality of the stick using

usb_modeswitch -v 12d1 -p 1001 -H 1

and get /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2 and /dev/ttyUSB3.

However, if I try

gcom -d /dev/ttyUSB0

,

I get

comgt 10:26:08 -> -- Error Report --
comgt 10:26:08 -> ---->                       ^
comgt 10:26:08 -> Error @74, line 4, Could not write to COM device. (1)

.

Now, here is the strange part: As soon as I use minicom to "talk" to the stick, comgt will work subsequently.

I'm now looking for a way to automate my workaround...

Ok, seems like I am not the only one who discovered this workaround:

http://nuwiki.openwrt.org/oldwiki/openw … dware/umts

Wow, didn't see this. Thanks for the workaround.

I found a way to perform this automatically, using stty [1]:

stty -F /dev/ttyUSB0 1:0:8bd:0:3:1c:7f:15:1:5:1:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0

works for me.  If it doesn't work for you, here is the trick:

Find a working state, e.g., using minicom. As soon as you can connect using comgt/gcom, save your configuration with "stty -F /dev/ttyUSB0 -g". The output string can then be used as seen above in order to configure /dev/ttyUSB*.

[1] To get stty, see https://forum.openwrt.org/viewtopic.php … 23#p100923
[2] For a full automation, see https://forum.openwrt.org/viewtopic.php … 21#p100921

Thanks a lot!