After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607817 - NetworkManger does not detect Huawei ETS1001
NetworkManger does not detect Huawei ETS1001
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: ModemManager
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-01-22 21:47 UTC by Kane Mason
Modified: 2010-11-23 05:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Compressed NetworkManager log (73.89 KB, application/x-gzip)
2010-01-22 21:47 UTC, Kane Mason
Details
Modem manager and network manager log (2.69 KB, text/x-log)
2010-01-26 17:22 UTC, Kane Mason
Details

Description Kane Mason 2010-01-22 21:47:55 UTC
Created attachment 152046 [details]
Compressed NetworkManager log

I have a Huawei ETS1001 Ver C.  Wvdial is able to successfully use this modem but network manager does not 'normally' detect it.  I say that it's not normally able to detect it because it has detected it before. 

An example out of the NetworkManger log....
Jan 21 18:07:03 linux-rsql NetworkManager: <info>  Found new CDMA modem device 'ttyUSB0' (driver: 'ti_usb_3410_5052_1').

It didn't actually connect then but i think that may have been a permissions issue.  I haven't had success in trying to get the interface to be seen by network manager again.  I've tried the obvious things like rebooting, removing the device, killing network manager and plugging it in and various combos of that.

I'm using opensuse 11.2 
output of uname is
Linux linux-rsql 2.6.31.8-0.1-default #1 SMP 2009-12-15 23:55:40 +0100 i686 i686 i386 GNU/Linux

Attached is the lsusb output and dmesg and the networkmanager log after i've connected and disconnected it.  I've compressed logs because the networkmanager one is huge.
Comment 1 Dan Williams 2010-01-22 22:23:04 UTC
Does the modem need to be modeswitched with usb_modeswitch?  What version of modem-manager do you have installed on your system?

Also, can you grab some modem-manager logs as described here:

http://live.gnome.org/NetworkManager/Debugging

in the "Debugging NetworkManager 0.8.x 3G connections" section.  Thanks!
Comment 2 Kane Mason 2010-01-26 12:20:42 UTC
Sorry it's taken me so long to respond, the network isn't exactly reliable where I am.

I'm not sure if usb_modeswitch is necessary, it certainly isn't for wvdial to work.  The documentation doesn't mention this modem specifically but I don't think that really means much. 

I've tried to use it but i've meet with pretty limited success, it doesn't exactly appear to be well documented.  just running usb_modeswitch as root doesn't do much at least.  I tried some switches but really, i have no idea what it wants from me.  This is network manager 0.7.1, do you still need the modem-manager logs?  I'll get them as soon as i get back to that hateful little modem.
Comment 3 Kane Mason 2010-01-26 17:22:28 UTC
Created attachment 152323 [details]
Modem manager and network manager log
Comment 4 Kane Mason 2010-01-26 17:32:24 UTC
Modem Manger appears to be version .2_20090810-2.1

Sorry about that, missed the question.
Comment 5 Dan Williams 2010-01-26 20:51:59 UTC
So it may not actually need usb_modeswitch.  But in any case, are you comfortable with a serial program like minicom?  I'd like to see what commands the device responds with.  It may just not respond to AT+GCAP, or it may not handle serial port control lines in the same way (since it's a different driver) as other devices do.  When wvdial connects, can you run this in a terminal too (as root)?

stty -F /dev/ttyUSB0 -a
Comment 6 Kane Mason 2010-01-26 22:46:45 UTC
I've never used minicom so I can't say that im comfortable with it.  I just installed it and pointed it the the mode, it seems to 'connect' but I don't really get much out of it.  I played with it but i'm pretty dim but with guidance i'm willing to try again.

Anyway this is the output of stty -F /dev/ttyUSB0 -a

speed 230400 baud; rows 0; columns 0; line = 3;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^A; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread -clocal crtscts
ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke
Comment 7 Dan Williams 2010-01-30 22:42:09 UTC
So on OpenSUSE 11.2 what is the NetworkManager version again?  I also forget if Novell hacked that version of NM up to talk to ModemManager or not; normally only NetworkManager 0.8.x uses ModemManager.

Also, is that stty output from during/after wvdial is able to connect?
Comment 8 Kane Mason 2010-01-31 22:17:45 UTC
It's 0.7.1 i believe.  My network is too too slow to pull up the package manager now.  I disconnected wvdial, disconnected the modem and connected the modem again to get those logs.
Comment 9 Dan Williams 2010-04-04 21:00:54 UTC
Do you have the 'modem-manager' process running at all here?

ps ax | grep modem

from a terminal should tell you.
Comment 10 Kane Mason 2010-04-04 21:15:08 UTC
Yes I do.
 
Also not to long ago it popped back into nm-applet, briefly.
 
Here are the relevant lines
 
Mar 25 18:43:55 linux-rsql NetworkManager: <info>  Found new CDMA modem  
device 'ttyUSB0' (driver: 'ti_usb_3410_5052_1').
Mar 25 18:43:55 linux-rsql NetworkManager: <info>  (ttyUSB0): exported as  
/org/freedesktop/ModemManager/Modems/0
Comment 11 Dan Williams 2010-08-03 16:48:22 UTC
Ok, seems like you do have ModemManager installed; SUSE patched NM 0.7.x to use modem-manager, but a fairly old version of modem-manager.  Could you do the following for me?

1) unplug the modem
2) stop NetworkManager
3) killall -TERM modem-manager
4) modem-manager --debug
5) plug the modem in

and the lets see what ModemManager says when trying to detect the modem.
Comment 12 Fabio Durán Verdugo 2010-11-23 05:22:12 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!