Closed GoogleCodeExporter closed 9 years ago
Identical behavior with Huawei E352 and E372 ... all UMTS 2G/3G USB dongles...
Original comment by karase...@gmail.com
on 30 Nov 2011 at 3:28
Thanks, I see the problem but it is not reproduced on Huawei e1820 at least
with r3523.
In your case the reason is following. The driver "option" instead of
"usb-storage" incorrectly connected to device endpoints:
I:* If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=option
E: Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 6 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=option
E: Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
Have you tested the release firmware r3497?
Original comment by rssdev10@gmail.com
on 30 Nov 2011 at 5:39
Actually this is long term bug/behavior:-( I can reproduce with any release on
this web. Of course at least version with modeswitch supporting the modem.
Nevertheless I see problem at different stage of booting process. It looks like
after SW reboot there is not necessity for modeswitch as modem is still/already
switched to modem mode. So far no problem, and looking to logs up to lines 45
logs are same. However, I see an issue at lines 49-53 respective 67-71.
Jan 1 01:00:07 kernel: SCSI subsystem initialized
Jan 1 01:00:08 kernel: Initializing USB Mass Storage driver...
Jan 1 01:00:08 kernel: usbcore: registered new interface driver usb-storage
Jan 1 01:00:08 kernel: USB Mass Storage support registered.
Jan 1 01:00:08 kernel: fuse init (API version 7.9)
When correct initialization is done USB Mass Storage driver is loaded before
modem detected, whereas in case improper initialization USB Mass Storage driver
is loaded after detection of the modem.
This seems to me root cause. USB Mass Storage driver is loaded too late or in other words modem is detected sooner then it should and for what ever reason USB5,6 serial ports are detected instead of USB mass storage because mass storage module is still not in memory...
Original comment by karase...@gmail.com
on 30 Nov 2011 at 6:24
[deleted comment]
Fixed in r3661 for modems that described in the driver "option".
Original comment by rssdev10@gmail.com
on 3 Dec 2011 at 8:20
It seems to solved an issue... I have tested with Huawei E1823 and WL500W only.
Three ttyUSB ports are detected now at all cases compare to 4 and 6 before.
Jan 1 01:00:11 kernel: option 1-2:1.0: GSM modem (1-port) converter detected
Jan 1 01:00:11 kernel: usb 1-2: GSM modem (1-port) converter now attached to
ttyUSB0
Jan 1 01:00:11 kernel: option 1-2:1.3: GSM modem (1-port) converter detected
Jan 1 01:00:11 kernel: usb 1-2: GSM modem (1-port) converter now attached to
ttyUSB1
Jan 1 01:00:11 kernel: option 1-2:1.4: GSM modem (1-port) converter detected
Jan 1 01:00:11 kernel: usb 1-2: GSM modem (1-port) converter now attached to
ttyUSB2
Jan 1 01:00:11 kernel: usbcore: registered new interface driver option
Jan 1 01:00:11 kernel: drivers/usb/serial/option.c: USB Driver for GSM modems:
v0.7.2
Jan 1 01:00:11 kernel: usbcore: registered new interface driver cdc_acm
Jan 1 01:00:11 kernel: drivers/usb/class/cdc-acm.c: v0.26:USB Abstract Control
Model driver for USB modems and ISDN adapters
USB devfs Devices
Device : Location : Info
/dev/ttyUSB0 : 2.0 : Manufacturer="Huawei Technologies" : Product="HUAWEI
Mobile"
/dev/ttyUSB1 : 2.3 : Manufacturer="Huawei Technologies" : Product="HUAWEI
Mobile"
/dev/ttyUSB2 : 2.4 : Manufacturer="Huawei Technologies" : Product="HUAWEI
Mobile"
2 12d1 14ac W 0 4 Huawei Technologies HUAWEI Mobile
BTW: USSD calls at Status&Log/USB PPP Log/USSD are executed faster. At least it
seems to me;-)
BTW2: I'll check other mentioned modems later next week as well with WL500gP
router...
Original comment by karase...@gmail.com
on 3 Dec 2011 at 3:10
Tested with Huawei E171 and issue is fixed in latest stable version 3702. Two
previous versions 3497 and 3300 were unusable because of this bug. Thanks for
fixing it!
Original comment by dmitriy.trt
on 26 Dec 2011 at 6:57
Original comment by lly.dev
on 26 Dec 2011 at 8:04
Original issue reported on code.google.com by
karase...@gmail.com
on 30 Nov 2011 at 2:55Attachments: