http://bugzilla.novell.com/show_bug.cgi?id=503397 Zheng Chen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zchen@novell.com AssignedTo|bnc-team-screening@forge.pr |tambet@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c2 Tamás Németh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #2 from Tamás Németh 2009-05-18 07:10:34 MDT --- (In reply to comment #1)

Does it work better with new ModemManager package from

http://download.opensuse.org/repositories/home://tambet://branches://openSUS...

It bypasses HAL for modem detection and does it's own thing.

I must sadly inform you that it's even worse - if possible. I was unable to connect using it, moreover I'm just having a stuck modem-manager process consuming 100% CPU time, just because I pulled the 3G stick out. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c4 --- Comment #4 from Tamás Németh 2009-06-17 02:53:55 MDT --- (In reply to comment #3)

Created an attachment (id=298590) --> (http://bugzilla.novell.com/attachment.cgi?id=298590) [details] Proposed fixed package

Please try this package.

OK, I'm testing it. Please wait for more details, but my first experiences are: OK the positive site it seems to handle (and thus present to NetworkManager) only /dev/ttyHS0, which is the working one for me. It omits /dev/ttyHS1, which is good for me, since I won't be confused by the two, virtually identical connections, amongst which only one works. This is good, but that one port still works just as unreliable as before. I suspect that this unreliability somehow may be related to the quality of the network, but the windows web'n'walk client almost always connects succesfully for the first time, while I have to fiddle 5-15 minutes with Linux in order to get connected to the net. A typical scenario: I plug in the stick, and in a few seconds, two options appear in gnome's nm-applet: the name of a preconfigured (by me) connection, and "properties" for the virtual serial port it will use to connect. (With earlyer versions there were two conection and two properties options, and I used the properties do discover which is the appropriate port for me, to scn available networks, and to initiate registering to the network before actually connecting). Now, when I click onto the connection option, the first attemt to connect is ALWAYS unsuccessful. However, properties won't work at all until this first attemt, so I have to attempt connecting first. Then I may attemt to connect again, but it almost always fails. At this point I usually use the "properties" option, which registers to the network, but not connects. I have to wait approximately one minute in this registered state which makes it much more probable that I will be able to connect (however, I mustn't close the properties window during using the net, because that would immediately break my connection). However, sometimes it's impossible to connect even despite being registered for a few time before attempting connection, and I have to restart everthing. A almost always have to restart this whole procedure, and ModemManager mostly stucks in, still showing the virtual serial port to networkmanager (in spite of the fact that the USB stick is already pulled out), and consuming 100% CPU time, so I have to restart everything like this: /etc/init.d/network stop ; killall modem-manager ; modprobe -r hso ; /etc/init.d/network start So, there seems to be no improvement in this area yet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c6 --- Comment #6 from Tamás Németh 2009-06-17 04:04:12 MDT --- (In reply to comment #5)

Next issue: Connection is very rarely successful in Linux, works often (always?) in Windows.

Not always, but in ~95% of the attempts, while it works in ~10 for Linux%.

So yes, this does sound a lot like a problem due to poor reception.

Maybe, but Windows doesn't need that long time between registration and conection. In the case of windows the registration and connection phases are separated more clearly. (After plugging in the stick I have to type in my PIN code which makes that client software to registrate but not connect, and I have to connect separately. However, even when I attempt to connect almost immediately after the registration, the connection will succeed virtually always, and I don't even have to wait! The connection finishes in a few seconds!)

ModemManager waits for one minute to finish registration + activating connection, so it sounds like it's not enough for you. There's nothing ModemManager can do more if it tells the modem to register (and then connect) to make it do it faster.

See above. I suspect that the windows client software may use a different method to handle the stick, since it's so much faster and more reliable. Earlier, under Linux I used a shell script (made by the author of the hso driver) to handle my 3G stick, but that was almost as unreliable as ModemManager. However, later I tried th HSOConnect utility (also made by the author of the hso driver), which proved to be approximately as fast and reliable as the windows client, but it's not integrated with NetworkManager and doesn't run on openSUSE 11.1 (because it needs python 2.5, at least it's last version seen by me). you should take a allok at HSOConnect, in order to get some ideas, or try my windows client on a windows machine (I can extract it from my USB stcik, and send to you). To make activation faster, we could (and should) try

to implement what you're already trying to use, that is, to get the modem registered before the start of connection. I have been wanting to write that, but it will take significant amount of time, and we simply don't have resources for that right now.

Networkmanager also has to be changed, right? Sorry, I can't help since I'm not a programmer, but it was one of my advices too. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c8 --- Comment #8 from Tamás Németh 2009-06-17 05:42:15 MDT --- (In reply to comment #7)

...

However, later I tried th HSOConnect utility (also made by the author of the hso driver), which proved to be approximately as fast and reliable as the windows client,

Can you get the log of AT command and responses it sends?

I have no idea how to do that. Maybe I shoud relay the traffic of the serial port through some scripts? Anyway, I started to fiddle with the settings of the connection, and it seems to me that it can be improved only this way. For example, I was able to connect to the network on the VERY FIRST ATTEMPTION, two times!!! I will summarize my experiences in one or two days. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User tambet@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c10 --- Comment #10 from Tambet Ingo 2009-06-17 06:00:29 MDT --- AFAIK, there is no generic port monitoring tool for serial port. It depends on application on how to do it. For ModemManager, you can do it by: # Become root, shut down NetworkManager and ModemManager su - killall NetworkManager killall modem-manager # Now run ModemManager with debugging enabled /usr/sbin/modem-manager --debug # Open a new terminal, become root and restart NetworkManager su - /usr/sbin/NetworkManager That will print out all AT commands ModemManager sends to your modem and also what it receives. No idea how to do it for HSOConnect. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c12 --- Comment #12 from Tamás Németh 2009-08-07 12:21:15 MDT --- So, my experiences are the following: I can make registering and connecting much faster/more reliable by changing the username and password (maybe I've used a wrong one so far?) but this way the connection becomes very unreliable. It disconnect in every then minutes and I even have to reboot the entire system in order to be able to reconnect. However, I realized that upgrading the hso driver to 1.9 improves reliability very much. I never have to do a full reboot after a hso driver upgrade. Please encourage your colleagues to upgrade this driver in the official openSUSE / SLES kernel: https://bugzilla.novell.com/show_bug.cgi?id=496401 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c14 --- Comment #14 from Tamás Németh 2009-08-07 12:34:48 MDT --- Created an attachment (id=311415) --> (http://bugzilla.novell.com/attachment.cgi?id=311415) Hsoconnect module for BackTrack 3 I had to commit these experiments on BackTrack 3 Linux, since HSOConnect doesn't work with python 2.6 of openSUSE 11.1. If you want to try it too, please download the attached BT3 image and simply copy in the /bt3/modules directory of a bootable BackTrack3 media. The HSOconnect icon will appear in BT3's KDE menu by doing this. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=503397 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=503397#c16 --- Comment #16 from Tamás Németh 2009-08-08 01:09:20 MDT --- One more serious problem of ModemManager: it cannot handle if I unplug the modem before it closes the port. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.